[yt-dev] advice on implementing halo member particle loading
Britton Smith
brittonsmith at gmail.com
Thu May 7 07:57:18 PDT 2015
Hi everyone,
Myself and one other who should be joining this list soon are interested in
implementing some new functionality and I would like to solicit some advice.
What we have are halo catalog datasets that, for the most part, are already
loadable in yt. They are loadable in that each individual halo is a
particle such that querying the mass field returns the mass of each halo.
However, these datasets also store the particles from the simulation
snapshot that are the members of each halo. We currently do not have the
machinery to query them and this is what we would like to add.
It seems the most sensible idea is to create a halo data container such
that something like the following returns the mass of all the particles in
a halo:
my_halo = ds.halo(some_id)
my_halo["particle_mass"]
This is somewhat different from the existing data containers as it is not
geometric. The member particles are explicitly known. I don't have much
experience with making data containers so I can't tell if this makes things
easier or harder. Anyway, this is the plan.
If anyone has reasons this may be too difficult or simply not work, I would
appreciate hearing them. Any general advice or other ideas for making this
functionality work would also be welcome.
Thanks!
Britton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20150507/e53d695f/attachment.htm>
-------------- next part --------------
_______________________________________________
yt-dev mailing list
yt-dev at lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
More information about the yt-dev
mailing list