Hi Matt,<br><br>Thanks for looking into this.<br><br>I agree with your assessment of the cooling time issue, that the order should be 3, 2, 1 here. The number of ways that cooling can be done in Enzo alone is growing large enough that reconstructing all of that on our own in YT will be a major pain, and require updates every time someone modifies what is done in Enzo. That last part I definitely want to avoid. Option 2 is something that would be beneficial for many things, but is probably a little ways off. For now, I think it's fine to check whether the OutputCoolingTime parameter is set and profile that field based on that.<br>
<br>When you you would like 2D profiles of every field, I'm not sure what you mean. By default, we're doing radial profiles of halos. Would we have default x and y fields for the 2D profiles? If so, I guess maybe density and temperature.<br>
<br>Everything else you said I like a lot.<br><br>Britton<br><br><div class="gmail_quote">On Thu, Apr 14, 2011 at 11:45 AM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi all,<br>
<br>
I had an opportunity to speak yesterday with Greg Bryan (who's not<br>
subscribed to this list) and independent of this thread, he brought up<br>
replacing enzo_anyl with yt. The one thing that I think we may be<br>
missing is the cooling time. To get the cooling time in yt we have<br>
three options:<br>
<br>
1) Re-calculate from scratch, using all the items in the parameter<br>
file that govern the cooling time. This will also allow it to work<br>
for non-Enzo simulation outputs.<br>
2) Wrap the Enzo cooling time routines. This will require utilizing<br>
fortran/C interop, possibly with f2py. It also has a lot of moving<br>
parts. (These would be solved if some day there was some agreement on<br>
microphysical solver APIs.) This would work with non-Enzo datasets.<br>
3) Mandate that if you want the cooling time in your profiles, you run<br>
with OutputCoolingTime=1 in Enzo. This would not work with non-Enzo<br>
datasets, unless they too had an option to output the local cooling<br>
time in every cell.<br>
<br>
I think #3 is the fastest time to solution, and certainly the option<br>
that is the least error prone. (The list above, it seems to me, is<br>
actually in order of increasing reliability.)<br>
<br>
The remaining items that we would need to accomplish to make<br>
HaloProfiler a generalized replacement for enzo_anyl, I believe, are<br>
either implementing the remaining fields (there may be a handful) and<br>
actually coming up with a list of all the fields to profile. Ideally<br>
I think we should calculate 1- and 2-D profiles for every field, and<br>
an HDF5 file with all of the profiles in it. The final output could<br>
then *additionally* include image plots of phase plots of<br>
mass-distribution with the average 1D profile overplotted. And<br>
perhaps projections. If we did all this, then we could not only aim<br>
to replicate functionality, but to enhance it.<br>
<br>
Best,<br>
<br>
Matt<br>
<div><div></div><div class="h5"><br>
On Tue, Apr 12, 2011 at 1:50 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>> wrote:<br>
> Hi Rick, Cameron, everyone,<br>
><br>
> Cameron is correct. I'm not suggesting any changes to Enzo.<br>
><br>
> Back before yt, enzo_anyl was used to make radial profiles of halos. My<br>
> understanding is that it only works in serial and that it is relatively<br>
> difficult, or at least not straightforward, to add new fields for radial<br>
> profiles.<br>
><br>
> The HaloProfiler tool in yt makes radial profiles in the same way, only it<br>
> take user input to decide on what fields to profile. It also can run in<br>
> parallel and do fixed resolution projections around each halo. Personally,<br>
> I think this makes using the HaloProfiler a better choice moving forward.<br>
> However, I have heard suggestions that the HaloProfiler lacks some<br>
> functionality of enzo_anyl, preventing it from being a true replacement. I<br>
> don't think enzo_anyl should be gotten rid of if people are still using it.<br>
> I just want to know what's missing so people who would like to use yt for<br>
> their enzo_anyl needs don't feel like they are losing functionality by<br>
> switching.<br>
><br>
> Britton<br>
><br>
> On Tue, Apr 12, 2011 at 1:36 PM, Cameron Hummels<br>
> <<a href="mailto:chummels@astro.columbia.edu">chummels@astro.columbia.edu</a>> wrote:<br>
>><br>
>> Rick,<br>
>><br>
>> I don't think he's suggesting we change enzo. I think he simply wants<br>
>> to know what functionality is lacking from yt's haloprofiler that<br>
>> enzoanyl currently has. That said, I think when we get haloprofiler<br>
>> working up to spec with enzoanyl's capabilities, we should announce it<br>
>> to the enzo list, so people who use enzoanyl (there aren't many of us)<br>
>> will know that there is a better supported alternative in yt.<br>
>><br>
>> Cameron<br>
>><br>
>> On 04/12/2011 12:18 PM, Rick Wagner wrote:<br>
>> > Hi Britton,<br>
>> ><br>
>> > On Apr 12, 2011, at 9:04 AM, Britton Smith wrote:<br>
>> ><br>
>> >> Hey everyone,<br>
>> >><br>
>> >> There is a fair amount of discussion about the HaloProfiler being a<br>
>> >> replacement for enzo_anyl. I would definitely like to see this become<br>
>> >> official, since it seems to be keeping a number of people from making the<br>
>> >> switch to YT. Can somebody outline the things that enzo_anyl does that the<br>
>> >> HaloProfiler cannot? I have been under the impression that there wasn't<br>
>> >> anything, but I haven't used enzo_anyl in quite a while.<br>
>> > I think that the HaloProfiler could easily be wrapped to look at act<br>
>> > just like enzo_anyl, which makes this an attractive choice. But, I would<br>
>> > post this question also the enzo-dev mailing list, since you're asking about<br>
>> > changing Enzo, not YT.<br>
>> ><br>
>> > --Rick<br>
>> ><br>
>> > _______________________________________________<br>
>> > Yt-dev mailing list<br>
>> > <a href="mailto:Yt-dev@lists.spacepope.org">Yt-dev@lists.spacepope.org</a><br>
>> > <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>> ><br>
>><br>
>> --<br>
>> Cameron Hummels<br>
>> PhD Candidate, Astronomy Department of Columbia University<br>
>> Public Outreach Director, Astronomy Department of Columbia University<br>
>> NASA IYA New York State Student Ambassador<br>
>> <a href="http://outreach.astro.columbia.edu" target="_blank">http://outreach.astro.columbia.edu</a><br>
>> PGP: 0x06F886E3<br>
>><br>
>> _______________________________________________<br>
>> Yt-dev mailing list<br>
>> <a href="mailto:Yt-dev@lists.spacepope.org">Yt-dev@lists.spacepope.org</a><br>
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
><br>
> _______________________________________________<br>
> Yt-dev mailing list<br>
> <a href="mailto:Yt-dev@lists.spacepope.org">Yt-dev@lists.spacepope.org</a><br>
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
><br>
_______________________________________________<br>
Yt-dev mailing list<br>
<a href="mailto:Yt-dev@lists.spacepope.org">Yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br>