DiamondLightSource / DiamondLightSource/sm-bluesky
Add a scan progress bar with calculated time-to-completion based on motor speeds and count time etc.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 3m
- Merged PRs (30d)
- 8
Description
Part of https://github.com/DiamondLightSource/sm-bluesky/issues/373 Queue Management & Experiment Control
Implement visual progress feedback including dynamic progress bars and remaining duration calculations during scan execution
Goals
Acceptance criteria : What journeys should the user be able to complete to consider your feature done
Be as specific as you can, check them off once they work. Add more if you find more requirements during development. Issue should only be considered done after all of them are checked
- The user can view an active scan's execution progress bar with an estimated time remaining.
Tasks
base on the goals, deduce the tasks required. check them off once they're done
- Duration Estimator: Build a calculator using motor speed, acceleration, range, and scan resolution to compute estimated plan runtimes, this most likely will be done with Bluesky simulation or something build into plan direction, to allow estimate of the plan progression.
- Progress Updates API: Subscribe to BlueSky plan event milestones to update progress bar states dynamically.
Contributor guide
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 or tests; start with parent issue #373 and the linked Bluesky simulation documentation, then locate the existing scan execution and UI/API entry points. Trace how motor speed, acceleration, range, resolution, and plan milestones can provide progress and remaining-time data, and verify the active-scan journey meets the stated acceptance criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100