All upid values are -1 when using SubhaloPhaseSpace
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start at the SubhaloPhaseSpace entry point and reproduce the reported satellite-galaxy case. Compare halo_id, halo_hostid, and halo_upid for satellites to determine where upid becomes -1; done means satellite records retain their host halo ID while genuine host halos still use -1, with the behavior verified against a focused regression case.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Python
- Stars
- 120
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from astropy/halotools
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
halotools.test_installation() seems to be broken in some environmentsMay be free again @aphearin claimed this 616 days ago, and no pull request is open. Openbug installation
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Clean up package data and MANIFESTMay be free again @aphearin claimed this 761 days ago, and no pull request is open. Open
All issues in astropy/halotools
Similar issues
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 72/100
EclipseFdn/open-vsx.org#14043 ·
Maintainers usually reply within 1 day
-
netbox status: needs triage type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
netbox-community/netbox#23376 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
githubnext/gh-aw-workshop#4455 ·
Maintainers usually reply within 1 day
-
Triage 🩺
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
[BUG] Container scenario crashes without expected_recovery_time, kube DNS example uses retry_waitOpenneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
krkn-chaos/krkn#1627 · 1 comment ·
Maintainers usually reply within 1 day