2 Commits

Include renames

Author	SHA1	Message	Date
x01dcandClaude Sonnet 5	67769d5ff8	fix(flomni,lamni): use .get() in tomo_queue_show()'s job-line formatter ... A job's params dict only has whatever _TOMO_SCAN_PARAM_NAMES held when it was snapshotted by tomo_queue_add(); a job persisted before a key was added (e.g. fovx/fovy, tomo_circfov) raised KeyError on the hard p['key'] lookup, making the whole queue un-inspectable instead of just missing a field. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-17 15:47:51 +02:00
Mirko Holler	30b5119a2f	feat(flomni): add command jobs to the tomo queue ... Type-tags queue jobs with a "kind" field (back-compat: missing kind defaults to "tomo"), and adds "command" jobs that reconfigure the beamline (currently: absolute moves on an allow-listed device, plus an optimize_idgap stub) between tomograms instead of running a scan. Command jobs are added via tomo_queue_add_command() against a curated named-action registry (_TOMO_QUEUE_ACTIONS) - not arbitrary code - so every queued action is auditable and safe to persist across a kernel restart. Validation is two-layer: schema checks at add time, and each action re-checks its own arguments against live hardware at execution time, which is the actual safety boundary. Crash-resume for a command job re-runs the whole step sequence from the top if every step is idempotent, or prompts the operator otherwise. flomni_webpage_generator.py is guarded against command jobs, which have no "params" key. See AI_docs/TOMO_QUEUE_COMMAND_JOBS_PLAN.md for the full design.	2026-07-13 09:05:29 +02:00