lincc-frameworks / lincc-frameworks/rubin-dash
Use left join during the nesting stage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
During DP2 an issue came up where we were missing rows in the object collection due to some objects having no forced sources. We want all objects in the lightcurve catlaog, even those with no light curves, so the join should use left join.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the nesting-stage join used for the DP2 lightcurve catalog and inspect how objects without forced sources are handled. Change the join so every object remains in the catalog, including objects with no light curves. Verify that objects with and without forced sources are both present in the resulting collection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100