I am running into an issue extracting the position data from a surface of
some enzo data.
It gives an error about adding code_unit to cm. A minimal script to
generate the error can be seen here http://paste.yt-project.org/show/7136/
I have previously had weird results with argmax returning code_units but
labeling them as cm with another dataset, although this does not happen
with the public dataset.
I want to use yt for studying the Massive Black II Simulation of GADGET by
Khandai et al (2014) to make X-ray and SZ observations. But whenever I try
to load the files I get a bad message of Memory Error. I had talk with Mr.
Natahan Goldbaum long before on this matter.
Can I solve this after all the new yt updates that has arrived?
I see in the yt 3.3 change log that "ghost zone generation" is a thing,
but I can't seem to find anything else about this.
I would like to generate ghost zones for FLASH data. I tried
retrieve_ghost_zones() but that gives an error, and I can't find any
other ghost zone-related functions. Could I get some advice?
Could someone advise me how to compute SFR for halos?
I have a dataset for which I computed SFR:
ad = d.all_data()
sfr = StarFormationRate(d,data_source=ad)
I also know how to add stellar masses to halos:
sm = d.add_deposited_particle_field(("STAR","MASS"),"sum")
h = yt.load('/data/gnedin/REICMP/D/RT/CASE.REF2/HC/a=0.1/hc.0.h5')
hc.add_recipe("calculate_virial_quantities", ["radius", sm],
But how do I add sfr.Msol_yr field from sfr as a deposited particle
field for d?
Thank you so much,
Following up on the discussion from last month, yt has now finished moving
to GitHub. We'll be working with pull request authors to transition any
remaining pull requests on BitBucket to GitHub, but all of the
infrastructure is now in place, including documentation, install scripts,
issue tracking and continuous integration. Thanks to Nathan, Kacper, Alex,
John, Britton and everyone else who worked on this transition project.
The main repository is here:
I'd also like to thank BitBucket for many wonderful years of hosting, and
note that I'm not without a bit of sadness that we've made this move. That
being said, I think this is an exciting opportunity for broadening our