Hi all,
Mark Richardson wrote to the yt_analysis project with a problem with
clumps on FLASH datasets. Here's his email:
"Below includes my script and the output (it wouldn't let me attach
two files). I get some output in the clump file up until I'd expect to
see the Jeans Mass dumped. The output makes me think that it can't
calculate this point because Gamma is unknown, or some other essential
variable needed to get the number density. I've attempted to change
the data_structure.py frontend for Flash to alias Gamma to gamc and
game but I still get the 'cannot find Gamma' when loading my dataset."
The issue from the traceback is that JeansMassMsun requires
MeanMolecularWeight which needs NumberDensity. This can't be
generated for his data.
I am not an expert on FLASH, but it seems that this should be
straightforward to fix, I just don't know how. Anybody from the FLASH
or Clump side have any ideas?
-Matt

Hi all,
We're proud to release yt version 2.5.1. This is a scheduled point
release that includes all bug fixes identified and fixed since the
release of 2.5 on March 1.
Major changes include:
* The addition of a frontend for the Pluto code (Andrew Myers)
* The addition of an OBJ exporter to enable transparent and
multi-surface exports of surfaces to Blender and Sketchfab (Jill
Naiman)
There have also been a number of minor bugs fixed in this release.
Some highlights:
* load_uniform_grid can now decompose dims >= 1024. (#537)
* Axis unit setting works correctly for unit names (#534)
* ThermalEnergy is now calculated correctly for Enzo MHD simulations (#535)
* Radius fields had an asymmetry in periodicity calculation (#531)
* Boolean regions can now be pickled (#517)
If you are using the stable branch of yt from an installation script,
you can upgrade using "yt update". If you are using the development
branch, you may already have these fixes. An installation-ready
tarball with generated C code (i.e., no Cython) has been uploaded to
the Python Package Index (PyPI).
Thanks very much,
Matt, on behalf of the yt development team

New issue 535: Thermal Energy is incorrectly computed for enzo data with MHD and without DualEnergy
https://bitbucket.org/yt_analysis/yt/issue/535/thermal-energy-is-incorrec...
J.S. Oishi:
For enzo, in order to properly compute ThermalEnergy when MHD is on, one needs to subtract MagneticEnergy from TotalEnergy as wel las 0.5*v^2. This is only an issue if DualEnergy is off, since if it is on, ThermalEnergy is directly computed by Enzo.
Responsible: jsoishi
--
This is an issue notification from bitbucket.org. You are receiving
this either because you are the owner of the issue, or you are
following the issue.

--- you can reply above this line ---
New issue 533: Enzo-3.0 datasets that do not contain active particles cannot be read in.
https://bitbucket.org/yt_analysis/yt/issue/533/enzo-30-datasets-that-do-n...
Nathan Goldbaum:
Enzo-3.0 datasets that do not contain active particles do not have an AppendActiveParticleType entry in the parameter file (and they shouldn't, I think). This breaks the enzo frontend since it assumes all 3.0 datasets contain such a key.
Here's a traceback that exhibits this behavior: http://paste.yt-project.org/show/3270/
I can make this dataset available if it will be useful for debugging.
--
This is an issue notification from bitbucket.org. You are receiving
this either because you are the owner of the issue, or you are
following the issue.