TNG-Cluster profiles for < 5R200c (loadOriginalZoom)
Eddie Aljamal
21 Oct
Hey Dylan,
I recently completed an analysis comparing the gas, DM, and star profiles all the way out to 5R200c in TNG300-1 when loading all particles (by chunking simulation.hdf5) and using illustris_python.snapshots.loadHalo() and the differences are significant at large radii as we would expect.
We cannot do the same thing for TNG-Cluster when it comes to the simulation.hdf5 file due to the nature of zoom resimulations. I have two questions:
1) Is it reasonable to make profiles for TNG-Cluster out to 5R_200c since I know that the high resolution region around each halo may not go this far.
2) How would you load all particles around the halo (not just the ones that are loaded by illustris_python.snapshots.loadHalo()) around a specific halo that extends out to past R_200c. Do you use illustris_python.snapshot.loadOriginalZoom()
As a bonus question just because I am wondering this:
3) Does illustris_python.snapshots.loadHalo() act in the same way in both TNG300 and TNG-Cluster, i.e. does it load analogous particles? (I know it is a bit vague but I am just making sure you can use both to make a fair comparison within R_200c). And how is illustris_python.snapshots.loadHalo() and illustris_python.snapshots.loadOriginalZoom() different (this may be answered by question 2).
Sorry for the bother and thanks so much.
Best,
Eddie
Dylan Nelson
23 Oct
(1) It depends on the question. You can certainly do it, but the results are becoming more and more compromised the further you go.
(2) This is what loadOriginalZoom() is made for, yes. It loads all particles of the entire (original zoom) simulation, i.e. combining all FoF halos and all "outer fuzz" (outside of any halo).
(3) All TNG simulation snapshots are ordered by FoF halo, and loadHalo() loads all the particles that belong to a FoF halo. So yes this is identical between TNG300 and TNG-Cluster.
Hey Dylan,
I recently completed an analysis comparing the gas, DM, and star profiles all the way out to 5R200c in TNG300-1 when loading all particles (by chunking simulation.hdf5) and using illustris_python.snapshots.loadHalo() and the differences are significant at large radii as we would expect.
We cannot do the same thing for TNG-Cluster when it comes to the simulation.hdf5 file due to the nature of zoom resimulations. I have two questions:
1) Is it reasonable to make profiles for TNG-Cluster out to 5R_200c since I know that the high resolution region around each halo may not go this far.
2) How would you load all particles around the halo (not just the ones that are loaded by illustris_python.snapshots.loadHalo()) around a specific halo that extends out to past R_200c. Do you use illustris_python.snapshot.loadOriginalZoom()
As a bonus question just because I am wondering this:
3) Does illustris_python.snapshots.loadHalo() act in the same way in both TNG300 and TNG-Cluster, i.e. does it load analogous particles? (I know it is a bit vague but I am just making sure you can use both to make a fair comparison within R_200c). And how is illustris_python.snapshots.loadHalo() and illustris_python.snapshots.loadOriginalZoom() different (this may be answered by question 2).
Sorry for the bother and thanks so much.
Best,
Eddie
(1) It depends on the question. You can certainly do it, but the results are becoming more and more compromised the further you go.
(2) This is what
loadOriginalZoom()is made for, yes. It loads all particles of the entire (original zoom) simulation, i.e. combining all FoF halos and all "outer fuzz" (outside of any halo).(3) All TNG simulation snapshots are ordered by FoF halo, and
loadHalo()loads all the particles that belong to a FoF halo. So yes this is identical between TNG300 and TNG-Cluster.Thank you so much Dylan.