In what context is the Entropy field supposed to apply? If you're talking galaxy clusters, then it's typically the number density of electrons that is in the definition, not the number density of _everything_. 

In multispecies runs you should be able to define it using Abar and Zbar fields, but keep in mind that typically in these cases we also have a possibly spatially varying gamma.

I'd actually be -1 in retaining the field, since it seems that its definition could be very context-dependent. 

John

On Wed, Jul 25, 2012 at 4:53 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
FLASH has eos_singleSpeciesA, which is equivalent to Mu in enzo.  I'm not sure if there is an equivalent parameter in FLASH 2 and 3.

Of course in multispecies runs eos_singleSpeciesA is not defined so you would need to build the number density field as in the enzo frontend.  FLASH allows for an arbitrary species specification - I'm not sure how that is represented in the data dumps since I've never run a true multispecies simulation.

I can't speak to the other codes.

Cheers,

Nathan

On Jul 25, 2012, at 1:47 PM, Matthew Turk wrote:

> New build: http://yt-project.org/docs/2.4/
> The cookbook in particular is coming along:
> http://yt-project.org/docs/2.4/cookbook/index.html
>
> Thanks for taking on the making_plots.rst, Nathan.  Britton, don't
> worry about the testing stuff, we can push it off for now.  As for
> NumberDensity, is there a mu value we could use?  Otherwise, we can
> build it from the species fields as we do for Enzo.  I'm also in
> support of searching out problematic fields; I think the particle
> fields in particular may have a handful of issues.
>
> On Wed, Jul 25, 2012 at 2:28 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
>>> * Rewrite the remaining docs that use PlotCollection.  Specifically,
>>> orientation/making_plots.rst needs to be completely redone.  Can
>>> someone volunteer to rewrite this document?
>>
>> I can take care of that one.
>>
>>> https://bitbucket.org/yt_analysis/yt/issue/401/entropy-field-does-not-work-for-non-enzo
>>
>> This will require defining a NumberSpecies field, currently only defined in the enzo frontend.  Really, NumberDensity should be a univseral field but I guess its definition will be highly code-dependent with respect to how different codes handle multispecies simulations.  Each of the maintainers for the different codes will have to update their frontend to include the NumberDensity field.
>>
>> While we're thinking about this, are there any other universal fields that depend on enzo-only fields?
>>
>> Cheers,
>>
>> Nathan
>>
>> On Jul 25, 2012, at 11:19 AM, Matthew Turk wrote:
>>
>>> Hi all,
>>>
>>> There's been a flurry of activity on the docs this week.
>>>
>>> * All the cookbook recipes have been moved into the docs and the
>>> cookbook shut down.  We now have 45 cookbook recipes, and they're
>>> integrated much better into the docs.
>>> * Most of the docs have been rewritten to remove PlotCollection
>>> * The data index is now part of the website repo.  It's up, but the
>>> files are still copying.
>>>
>>> Here's my current draft of the changelog for 2.4.  Did I forget anything?
>>>
>>> https://bitbucket.org/MatthewTurk/yt-doc/src/b57d3621ff70/source/changelog.rst
>>>
>>> We're just about good to go.  These things still need to be done:
>>>
>>> * Rewrite the remaining docs that use PlotCollection.  Specifically,
>>> orientation/making_plots.rst needs to be completely redone.  Can
>>> someone volunteer to rewrite this document?
>>> * Volume rendering docs need to be rewritten en masse, as they are
>>> quite out of date and don't reflect best practices or new
>>> functionality (ticket #382).
>>> * Do we want to put answer testing docs in for this release, or
>>> should we push that off to a point release at a slightly later date?
>>> * Write docs about the Hub, which I will do.
>>> * Check to make sure that everything that SHOULD be documented in the
>>> API docs IS documented.
>>>
>>> In the past we've also talked about slides demonstrating new
>>> functionality, as well as the possibility of doing screencasts.  I'm
>>> going to throw together some HTML slides, but if anybody wants to do a
>>> screencast that would be outstanding.  We actually have gotten *many*
>>> views in the past of screencasts.
>>>
>>> I think that's about it.  There are two additional technical tickets
>>> that should be addressed:
>>>
>>> https://bitbucket.org/yt_analysis/yt/issue/401/entropy-field-does-not-work-for-non-enzo
>>> https://bitbucket.org/yt_analysis/yt/issue/390/transfer-function-bounds
>>>
>>> I can do the second, but I don't know what to do about the first.
>>>
>>> Thanks all,
>>>
>>> -Matt
>>> _______________________________________________
>>> yt-dev mailing list
>>> yt-dev@lists.spacepope.org
>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev@lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> _______________________________________________
> yt-dev mailing list
> yt-dev@lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

_______________________________________________
yt-dev mailing list
yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org



--
John ZuHone

Postdoctoral Researcher
NASA/Goddard Space Flight Center

jzuhone@gmail.com
john.zuhone@nasa.gov