Fixing remaining ID inconsistencies in AHF handler #191
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @apontzen and @cphyc,
We realised with @gandhalij that the mapping between parent haloes and child sub haloes is currently broken by the differences between AHF
ID
andhalo_id
explained in #178.The current implementation assumes that
hostHalo
encodes thehalo_id
of the host, whereas it really encodes itsID
. This PR fixes this inconsistency, adding a mechanism to mapID
andhalo_id
for the general case in which they are non-trivially related.Comments welcome!
Martin