Revisit fiberflatnight requirements
- Dominant language
- Python
- Stars
- 42
- Forks
- 26
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 18
Description
The current pipeline will happily submit a fiberflat job for e.g. 30 cameras, even if it only has psfnight inputs for fewer cameras. Historically we have been very strict about how recent psf's need to be in order to process flats effectively. We should revisit this policy and either update recommendations or update the code to be equally strict.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing fiberflat job submission and its psfnight input requirements; no files or tests are named. Clarify with maintainers the required camera coverage and PSF recency, and whether recommendations or enforcement should change. Done means the agreed policy is reflected in documentation or enforced by the pipeline, with validation for missing camera inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 22/100