[Yt-dev] HaloProfiler vs. enzo_anyl

[Matthew Turk]

Hi all,

I've updated the list of fields:

http://paste.enzotools.org/show/1583/

Some of these fields I don't know how to set up, but we either have
most or could directly implement them.  The tricky ones are the ones
that separate out DM/Star particles, which will require a bit more
touching of the data.  (That's where most of the "NotImplemented"
comes from.)  Some of these fields we even had before -- like the
inertial tensor -- and I think some people have a couple of these
fields already in private repos.  I pulled out all the disk analysis
fields.

It would probably be the work of an afternoon to wrap up replicating
all the functionality and putting it into a "yt analyze" command.

-Matt

On Thu, Apr 14, 2011 at 2:54 PM, John Wise <jwise at astro.princeton.edu> wrote:
>>> I agree with this.  After thinking about it and reading Britton's response, I think #3 would be the best option.  A possible solution to calculating the cooling time post-runtime would be to add a command line option to Enzo that adds the CoolingTime to the data, similar to the potential field output command line option.  The catch is that you'd have to make sure that you use the same version as you ran the simulation.
>>
>> I agree, that would be great.  Do you think this is straightforward?
>> I have looked before at the WritePotential stuff, but I'm not sure I'm
>> the best person to add this.
>
> I could add this pretty quickly.  I'll try to do it today.
>
> John
> _______________________________________________
> Yt-dev mailing list
> Yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>