simonsobs / simonsobs/scheduler
Take stream shutdown time into account in schedules
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 12h 45m
- Merged PRs (30d)
- 6
Description
Telescope motions will continue until all streams are shut down. This can result in an extra 20 seconds or so of motion for observations for SATs (not yet measured for the LAT) which can eat into the next scan and possibly affect sun-safety. It might be useful to add an estimate of this to the schedules to make sure they are consistent with what we are running.
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
The issue names no files, tests, or entry points. Start by locating schedule generation and stream shutdown handling, then determine how shutdown duration differs for SATs and the LAT. Done means schedules account for the estimate and remain consistent with observed motion and sun-safety constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100