New issue 858: Recently added particle fields don't put their deposit fields into the derived_field_list
When one creates a particle filter, it successfully adds the derived particle fields to the derived_field_list, but it does not add the "deposit" fields to the derived_field_list (despite creating the fields).
Are there any outstanding, code-not-documentation issues other than
existing pull requests that we need to get in before 3.0 goes out?
If not, I'd like to propose a code freeze on the yt-3.0 branch in
anticipation of the release, which I would like to shoot for happening
by the end of July.
Looking over Trello, the only thing that sticks out at me is boundary
conditions, which I think needs to wait for 3.1.
Hi all, I am in the process of adding some Maestro and Castro datasets to
the data webpage:
I am happy to take the opportunity to reorganize it a bit, if people are
In particular, there are 3 separate tables on that page -- two seem like
they could be merged: do we need a separate "yt sample data" and "yt 3.0
sample data" table still?
Also, I'd like to sort the datasets alphabetically by data (front end)
format, perhaps with a column-spanning header noting what frontend each is.
I think that this will make it easier for everyone to see which datasets
are available to exercise the various frontends.
Please let me know what you think. In any case, I'll be adding some new
Maestro and Castro datasets to the collection.
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY
Is there a timeline for the yt hub coming back up? I believe the hold up
had been the fee of hosting the hub, which I think was being covered by
Matt's personal funds. Is there ever any hope of getting some dedicated
funds to support this in the future? If not, I'm happy to chip in some
money to help this get back up. It seemed like a great resource both for
hosting datasets and projects tangentially related to yt. Also, I think it
was the location of the enzo test gold standard, right?
Anyway, I just wanted to see if there was a timeline for it coming back or
if was out for the foreseeable future, or if we could help.
University of Arizona
Caveat: I'm not that familiar with particle-based datasets/codes.
I'm unsuccessfully trying to help a summer student do some visualization of
someone else's Gadget binary data dump. What is the status of volume
rendering SPH/Gadget data in 3.0?
When I've tried what I know works for grid-based data, the returned image
is simply empty. Projections look okay (for some variables), and Slices
look worse as there are blank splotches, likely due to emptiness in the
Also, is there a list somewhere that describes/defines what the various
fluid types mean (e.g. 'all', 'gas', 'deposit', etc)? If not, it might be
nice to have somewhere in the docs.
For ART particle data yt returns incorrect mass values. I believe this
is something Matt had solved in March by dividing mass units by ng**3
for particle mass data.
Miguel Rocha brought this to my attention and I have been able to
reproduce the problem on the public ART dataset (D9p_500).
I thought we had included the following in art/frontends/fields.py,
but am unable to find it now.
def setup_particle_fields(self, ptype):
function=_particle_mass, units="code_mass", particle_type=True)
Why would this have been working at some point and now it is broken again?
All the best,
The yt-fido is going to go down on 07/16 1:00am EDT due to network
maintenance. Downtime may last even two working days, but I hope it will
Please keep that in mind while issuing PRs ;-)