[yt-dev] text halo supplementary data

[Christine Simpson]

I like this idea too.  I don't know what's the best way to organize the
data structure, but giving the user more flexibility over this sounds
great.  Making this more flexible will also give the code room to grow
as people want to experiment and do more sophisticated things.

On Tue, 2012-07-10 at 09:28 -0700, Matthew Turk wrote:
> If you look
> in halo_objects.py, you can se that the number of properties of a halo
> object has 1) exploded 2) no standardization.  Having a dictionary of
> properties, which can vary in name, fits more with the yt philosophy.
> I like this idea.  We could expand it to "derived properties" as well,
> and maybe reduce te number of by-default calculated properties of a
> halo.
> 
> If we start thinking of a future where we can load halos without
> necessarily affiliating them with simulation data, this could be kind
> of cool.  What do you think?