simonsobs / simonsobs/sotodlib
Add obsdb collumn to flag observations that shouldn't be used
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 23
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 14
Description
From discussion with @kmharrington @jlashner and @mhasself
It would be useful to be able to mark bad observations in a way where they can be filtered out when querying the obsdb.
Matthews suggested implementation is:
- Add a column "dont_use" to the standard obsdb, have it "false" by default. Add more negatives, if double is not enough for you (e.g. dont_ignore, default=true)
- Have a ride-along config file (obsdb-bad-obs.yaml) for update-obsdb, where you can flag ranges of time, or individual obs, as bad.
- Whenever update-obsdb runs, it updates the dont_not_ignore column according to the obsdb-bad-obs.yaml.
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 standard obsdb schema and the update-obsdb entry point, then review the proposed obsdb-bad-obs.yaml configuration. Clarify the column name and default semantics before implementation. Done means bad observation ranges or individual observations from the configuration are reflected when update-obsdb runs and can be filtered during obsdb queries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100