simonsobs / simonsobs/scheduler
Add a smart ending to schedules
Nobody has claimed this yet.
- #152 by @mmccrackan — closed without merging
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 12h 45m
- Merged PRs (30d)
- 6
Description
Right now we give it a time and it ends by that time, but that's not ideal when a CMB scan could span that end and we don't feel all that strongly about the time +/-30 min.
We need an option to close out a scan or field if it's within some buffer time for an end time. This way we can optimize where the edges of schedules can be are improve our observation efficiency.
I think this should be implemented during or after https://github.com/simonsobs/scheduler/issues/78
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 #78 and reviewing the linked closed pull request #152, the only project references provided. Define completion as allowing a scan or field to close when it falls within the configured buffer around its scheduled end time, while confirming how this relates to the earlier scheduling work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100