Feat/lamni loop settings #360

Merged
holler merged 4 commits from feat/lamni-loop-settings into main 2026-11-19 17:04:06 +01:00
4 Commits
Author SHA1 Message Date
Mirko HollerandClaude Opus 5.5 68eb2721e5 ptycho_lamni.yaml: LaMNI web HMI API token for lamni_loop_settings (as flOMNI; plain text OK in the beamline network, Mirko 2026-11-19)
CI for csaxs_bec / test (pull_request) Successful in 4m7s
Read the Docs Deploy Trigger / trigger-rtd-webhook (push) Successful in 2s
CI for csaxs_bec / test (push) Successful in 3m56s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01M8zoDygkWk6LupmHh3tyET
2026-11-19 16:51:04 +01:00
Mirko HollerandClaude Opus 5.5 ba4e78e263 LamNI feedback_enable_with_reset: move lsamx and lsamy at the same time
CI for csaxs_bec / test (push) Failing after 1s
The coarse stages went to their centers one after the other (move(wait=True) each). Both moves are now started
with wait=False and then waited for; Ctrl-C stops both axes; J1 only after both are done. The same parallel move
on this Galil is already used by umv(dev.lsamx, ..., dev.lsamy, ...) in x_ray_eye_align. Requested by Mirko
2026-11-19. Test: tests/tests_devices/test_rt_lamni_reset.py (order of moves / waits / J1, Ctrl-C).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01M8zoDygkWk6LupmHh3tyET
2026-11-19 16:04:10 +01:00
Mirko HollerandClaude Opus 5.5 ea0ade0715 feat(lamni): loop settings - lamni.rt_settings, baseline device lamni_loop_settings, trigger source at scan start
CI for csaxs_bec / test (push) Successful in 8m43s
LaMNI web HMI loop settings (LamNI LAMNIcontrol/loopsettings/lamni.json on mpc-lamni, 2026-11-19) in BEC, as
flOMNI / OMNY:
- lamni.rt_settings (plugins/LamNI/lamni_realtime_system.py): the flOMNI client with the LaMNI device and texts;
  standard() / large_steps() apply the two profiles; tracker shortcuts refused (LaMNI has no laser tracker).
- lamni_loop_settings (devices/omny/lamni_loop_settings.py, copy of omny_loop_settings with the LaMNI settings):
  baseline device, every scan file holds the loop settings it ran with.
- LamniFermatScan.set_trigger_source() in prepare_setup (as the flOMNI scan): at the beamline (ddg1 real) the
  hardware trigger, else the soft trigger with exp_time x frames_per_trigger; at the beamline a failure aborts.
- ptycho_lamni.yaml: device lamni_loop_settings (host mpc-lamni.psi.ch); API token NOT filled in (to be entered,
  token or token_file ~/.lamni_webhmi_token).
Tests: device, client, scan trigger source (offline, local HTTP stand-in); all LaMNI tests pass (763).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01M8zoDygkWk6LupmHh3tyET
2026-11-19 13:33:19 +01:00
Mirko HollerandClaude Opus 5.5 37f25e45e8 refactor(flomni): rt_settings texts as class attributes (STAFF_ONLY, DOC, HELP_EXAMPLE) for subclasses
Same change as on fix/omny_commissioning (omny.rt_settings), taken over unchanged so both branches merge cleanly;
used by lamni.rt_settings.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01M8zoDygkWk6LupmHh3tyET
2026-11-19 13:33:18 +01:00