Repository navigation
Program Block Definition & Plan Composition #383
Description
Part of #373 Queue Management & Experiment Control:
Enables users to define, group, and save modular "Program Blocks"—reusable execution units that bundle scan plan/plan stub hardware configurations, and post-scan workflow triggers(?) into a single queueable block.
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
- BlueAPI Queue Connection: Connect the UI queue actions to the BlueAPI/RE queue endpoints.
- Panel UI: Build the Queue list layout displaying queued, active, and completed plan states.
Tasks
base on the goals, deduce the tasks required. check them off once they're done
Note
The level of detail in the mock worry me, it contain not just blueapi plan, it also contain data analysis summation which mean Queue has to be able to dispatch different task to different services which is not the current design of queue.
- Create Block UI builder and form schema design.
- BlueAPI plan block serialization into payloads for execution.
Screen shot
Activity
NKatti2011 commentedon Sep 16, 2026
Below include notes from meeting with @EmsArnold
Priority
Deprioritised for now as running a script is main priority.
Design notes for when it is picked up
Alternatively processing pipelines could be separated out into modals.
To flag
There is an open discussion about whether the UI should show two queues, one for
acquisition and one for processing jobs, rather than a single combined queue. This affects
#382 and the current UI mock, which shows a single queue. Worth settling before queue
layout work starts.