So, where does this leave us, Geoffrey, in your opinion? Are you going to make changes soon, later, or never? Shall we merge now, or wait for changes from you?
I think I want to make the changes soon, but I'm not sure if we should discuss some details off list on how to best integrate this stuff into YT. I was envisioning that the ellipsoid profiling, constructing the ellipsoid object can be integrated with your Halo profiling some how.
I'll be available again later in the afternoon after group meeting
From G.S.
Hi all,
(quoting GSO)
So I think it is best to have e1 and e2. Â Having e3 calculated on the fly will save 3 columns off of the data file, and if we don't store the center and A that's another 4 columns. Â And if we go with the rotation angle idea it will save another 2 out of 3 columns, replacing 3 e2 components with 1 angle.
So, where does this leave us, Geoffrey, in your opinion? Are you going to make changes soon, later, or never? Shall we merge now, or wait for changes from you?
(Quoting GSO)
Ultimately I'd want to analyze the DM and star particles in the ellipsoid separately, do I just use the derived field and particle ages to do that once the previous problem is solved?
(Quoting Matt's response)
I'll defer to someone else on this. Â The way stars are differentiated in Enzo -- although other codes seem to have gotten this right -- bugs me in its inconsistencies. Â (i.e., ages versus ParticleType. Â Not a fault of enzo, really, just inconsistent conventions for running simulations. Â :)
I agree with Matt on this confusion bit. But to answer your question, Geoffrey, yeah, you'll just do something like:
ct = Ell['creation_time'] select_stars = (ct > 0) star_masses = Ell['ParticleMassMsun'][select_stars]
or similarly with 'particle_type' in the first line.
-- Stephen Skory s@skory.us http://stephenskory.com/ 510.621.3687 (google voice) _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org