simonsobs / simonsobs/sotodlib
Preprocess: Remove reliance on Peak-to-Peak cuts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 23
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 14
Description
Currently we are using a peak-to-peak cut that looks at the kurtosis of the distribution of the peak-to-peak of each TOD and cuts outlier detectors until the kurtosis is below some threshold. I see this as a bandaid that is mostly cutting detectors with jumps that aren't being properly flagged + fixed. Once we are more confident in our jump finding + fixing being tracked in issue #975 we need to re-evaluate the need for the peak-to-peak cuts and test if we can remove this step.
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 reading issue #975 and the preprocessing entry points that implement the peak-to-peak cut. Compare processing with and without the cut after jump finding and fixing are reliable, and document whether the cut can be removed without losing detector-quality safeguards.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100