simonsobs / simonsobs/scheduler
Prioritization loop needs to be able to distinguish between lower priorities
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 12h 45m
- Merged PRs (30d)
- 6
Description
Currently, the lower function is not aware of the difference in prioritization between blocks with lower priority than the one it is currently on. Therefore, things like wiregrid and planet scans must be the same prioritization as the pre and post sessions, which can cause problems if one of these runs into the end of the schedule. Can either upgrade lower to handle this or just cut these up front if they extend to within a minute or so of the post-session.
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 in src/schedlib/policies/stages/build_op.py around the lower function at line 590. Trace how lower-priority blocks are compared with the current block and inspect the handling of wiregrid, planet scans, and pre/post sessions. Done means distinct lower priorities are preserved, or those scans are cut off when they approach the post-session boundary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100