You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Integrate UI scan number tracking via numtracker or Tiled endpoints. #386
Part of #373 Queue Management & Experiment Control:
Fetch the active scan number and propagate it automatically to workflow pipeline fields, eliminating manual entry.
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
Auto-Populated of scan number and visit: The current scan number and visit displays automatically and populates downstream reconstruction triggers.
Tasks
base on the goals, deduce the tasks required. check them off once they're done
Numtracker Evaluation: Query the Numtracker endpoint to fetch active scan indices. ( This is also available from Blueapi once a task is summited)
UI Field Auto-fill Hook: Bind the retrieved scan number directly to Nathanael's processing pipeline input form ??
Query numtracker for the scan number and feed that into the queue.
We can query from Tiled instead - this is preferred architecture (if this is too slow then can query numtracker)
An equivalent issue already exists for i15-1: DiamondLightSource/atlas #184 worth aligning with it rather than solving twice.
Caveat
numtracker currently exists to keep GDA and other systems consistent, and is expected to be retired. We should put a thin abstraction in front of it so the replacement can be swapped in without touching UI code.
Activity
NKatti2011 commentedon Sep 16, 2026
Include notes from meeting with @EmsArnold
Approach
Caveat