Hi Nathan,
Sorry to hear that you're having issues with the Pop III star formation routine. It's failing when it's trying to access the LW radiation field. It should only check this field when you have both radiation transport on and MultiSpecies > 1 (H2 cooling). Do you have both of these parameters set like this? Can you send your parameter file?
Thanks,
John
You don't often get email from natha...@gmail.com. Learn why this is important
--
You received this message because you are subscribed to the Google Groups "enzo-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enzo-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/enzo-dev/3f057ed3-263e-48bb-9fa1-c2c31bd6971fn%40googlegroups.com.
-- John Wise Director, Center for Relativistic Astrophysics Professor, School of Physics Georgia Institute of Technology http://cosmo.gatech.edu
--
Hi Nathan,
I made a few changes to your parameter file, and when I run it, one Pop III star particle forms at t ~ 1.71. The main problem was that you set the star particle creation density to the initial density of the cloud. In that case, all of the cells inside the cloud will trigger star particle creation, but there is a hard-coded safety check in the Pop III formation routine to prevent many star particles from forming within some radius.
I changed the SF density criterion from 1000 to 1e5, allowing the cloud to collapse before it forms stars, which is a more realistic setup. I also changed the Courant factor from 0.5 to 0.25, which is needed with feedback, and the StopTime to 2.5 and output cadence to 0.25. I'm attaching the modified parameter file, so you can test it out. The Pop III star particles will have its "particle_type" field equal to 5. When it forms, the stdout should give you the following information
"""
StarParticle[birth]: L3, r = 0.00625 pc, M = 1017, Z2/Z3 = 0/0
mass = 100 (100% cold) SolarMass,
rho = 9.77818e+06 g/cm3, tdyn = 0 Myr
vel = -0.000000 -0.000000 -0.000000 (-0.000000 -0.000000
-0.000000)
pos = 0.500000 0.500000 0.500000
"""
I hope this works for you, and let us know if you have any more questions.
Thanks,
John
To view this discussion on the web visit https://groups.google.com/d/msgid/enzo-dev/0a90aa86-6191-4d0d-a1f9-a4b322ea3c74n%40googlegroups.com.
Yes, you can use the CollapseTest to simulate a metal-free molecular cloud instead of a cosmological simulation. I'd suggest using a published setup and trying to reproduce their results. Most of the parameters are there to control the initial conditions of the cloud. The only thing that is lacking is a good turbulence generator. The one in CollapseTest only does local random motions, but the MHD CollapseTest generates turbulent conditions from some power spectrum. I'm not too familiar with the latter.
Thanks,
John
To view this discussion on the web visit https://groups.google.com/d/msgid/enzo-dev/db6f2648-5d55-4567-97c1-8320ba0392b5n%40googlegroups.com.
No worries. When Pop III star particles are created, it merges
any particles together within some radius in a given timestep.
Since the bookkeeping of particle IDs in Enzo makes it difficult
to delete particles, we just set the particle masses to a very
small number. The NumberOfStarParticles parameter is used to set
the star particle IDs, and we only increment it. This is why that
.hierarchy entry is larger than the actual star particles. You
should use the data provided with yt / .cpuXXXX files.
Thanks,
John
To view this discussion on the web visit https://groups.google.com/d/msgid/enzo-dev/d6aefb8f-5773-4e7c-a924-d6cb7b38a3e9n%40googlegroups.com.