I know in the original suite's merger catalogs, one could query "SubfindIDLastMajorMerger". That key does not seem to exist in the TNG merger tree data. Is it still recorded somewhere?
Dylan Nelson
23 Feb
I can't find any mention of this. Definitely it is not part of the SubLink trees themselves.
Perhaps it was in the "Stellar Assembly" supplementary catalog? But not documented.
Ekta Patel
23 Feb
It's possible it was a post-processing catalog Vicente had compiled. The file name for the z=0 snapshot was 'merger_history_135.hdf5', but alas, that is not the most indicative of its origin.
Do you know of any alternative way to determine the SUBFINDID of the last major merger progenitor? The reason I would like to trace this is to plot the progenitor's orbit and determine the location where it was last identified in the halo catalogs relative to the primary it merged into.
Thanks!
Dylan Nelson
22h
This is fairly easy from the trees, perhaps this thread is useful (either the code, or you can use the API functionality directly).
Ekta Patel
5h
Thanks for pointing me that way! It's been a while since I have dug through the trees.
I know in the original suite's merger catalogs, one could query "SubfindIDLastMajorMerger". That key does not seem to exist in the TNG merger tree data. Is it still recorded somewhere?
I can't find any mention of this. Definitely it is not part of the SubLink trees themselves.
Perhaps it was in the "Stellar Assembly" supplementary catalog? But not documented.
It's possible it was a post-processing catalog Vicente had compiled. The file name for the z=0 snapshot was 'merger_history_135.hdf5', but alas, that is not the most indicative of its origin.
Do you know of any alternative way to determine the SUBFINDID of the last major merger progenitor? The reason I would like to trace this is to plot the progenitor's orbit and determine the location where it was last identified in the halo catalogs relative to the primary it merged into.
Thanks!
This is fairly easy from the trees, perhaps this thread is useful (either the code, or you can use the API functionality directly).
Thanks for pointing me that way! It's been a while since I have dug through the trees.