Halo ID Matching in TNG-Cluster and LHaloTree Data
Qiaoyang Hao
24 May
Specifically, the target clusters in TNG-Cluster are associated with multiple Halo IDs (e.g., Original ID, Halo ID), but I have been unable to reliably match these to the corresponding IDs in the LHaloTree merger tree. As a result, I am unable to trace the merger histories of these clusters. I wonder how to properly link the target clusters to their merger histories within the LHaloTree framework, or which fields in the LHaloTree merger tree data can be used to figure out which cluster a specific tree belongs to?
Dylan Nelson
27 May
Both LHaloTree and SubLink are based on subhalos, not halos.
So you can load the tree of a given subhalo ID.
This is exactly the same, using illustris_python, between the two trees, i.e.
import illustris_python as il
basePath = 'sims.TNG/TNG-Cluster/output/'
tree1 = il.sublink.loadTree(basePath, snap, sub_id, onlyMPB=True)
tree2 = il.lhalotree.loadTree(basePath, snap, sub_id, onlyMPB=True)
You can see within the code of this function how the particular tree is identified, for a given subhalo ID.
Specifically, the target clusters in TNG-Cluster are associated with multiple Halo IDs (e.g., Original ID, Halo ID), but I have been unable to reliably match these to the corresponding IDs in the LHaloTree merger tree. As a result, I am unable to trace the merger histories of these clusters. I wonder how to properly link the target clusters to their merger histories within the LHaloTree framework, or which fields in the LHaloTree merger tree data can be used to figure out which cluster a specific tree belongs to?
Both LHaloTree and SubLink are based on subhalos, not halos.
So you can load the tree of a given subhalo ID.
This is exactly the same, using illustris_python, between the two trees, i.e.
You can see within the code of this function how the particular tree is identified, for a given subhalo ID.
Many thanks!