You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Low priority issue, but confusing enough that I thought I'd submit an issue so it's documented.
When using SubhaloPhaseSpace (not sure it this also happens with others), the upid value for all of the satellite galaxies is -1. My understanding is that this upid == -1 indicates that the subhalo is a host halo (the highest in the halo hierarchy), basically a shorthand for saying halo_id == halo_hostid. However, all the satellites are getting upid == -1 even though their halo_id != halo_hostid.
Shortened version: Rather than getting the halo_id for their host halo in the halo_upid column, satellite galaxies are getting upid == -1 when using SubhaloPhaseSpace.
The text was updated successfully, but these errors were encountered:
Thanks for the reminder in the form of an issue @nvanalfen - this will be a simple fix, and I tagged this with next-release to make sure it makes it into v0.8.
Low priority issue, but confusing enough that I thought I'd submit an issue so it's documented.
When using SubhaloPhaseSpace (not sure it this also happens with others), the upid value for all of the satellite galaxies is -1. My understanding is that this upid == -1 indicates that the subhalo is a host halo (the highest in the halo hierarchy), basically a shorthand for saying halo_id == halo_hostid. However, all the satellites are getting upid == -1 even though their halo_id != halo_hostid.
Shortened version: Rather than getting the halo_id for their host halo in the halo_upid column, satellite galaxies are getting upid == -1 when using SubhaloPhaseSpace.
The text was updated successfully, but these errors were encountered: