duan_jandClaude Fable 5 6b34fd80bb
CI / lint (push) Skipped
CI / test (3.12) (push) Skipped
CI / test (3.13) (push) Skipped
CI / test-with-beamline-plugins (pxi_bec) (push) Skipped
CI / test-with-beamline-plugins (pxii_bec) (push) Skipped
CI / test-with-beamline-plugins (pxiii_bec) (push) Skipped
CI / lint (pull_request) Successful in 59s
CI / test (3.12) (pull_request) Successful in 1m15s
CI / test (3.14) (pull_request) Successful in 1m17s
CI / test (3.13) (pull_request) Successful in 1m21s
CI / test-with-beamline-plugins (pxi_bec) (pull_request) Successful in 1m22s
CI / test-with-beamline-plugins (pxii_bec) (pull_request) Successful in 1m25s
CI / test-with-beamline-plugins (pxiii_bec) (pull_request) Successful in 1m37s
CI / test-with-coverage (pull_request) Successful in 1m51s
CI / coverage-analysis (pull_request) Successful in 4s
refactor: transmission is a per-mode setting, placed in its section
The shared "Rotation transmission" row sat in the top rows of BOTH the
Gridscan and Rotation tabs, where it read as one setting for everything
(and as nonsense in the Gridscan tab). Now each tab places its own row:
Gridscan keeps "Transmission" with the shared resolution/distance rows,
and the Rotation tab moves "Rotation transmission" below the Screening
block and its Run button, as the first row of the Rotation section -
next to the fields it actually applies to. Screening keeps its separate
"Screening transmission". No behavior change: same field, same
spreadsheet/user-value handling, only the label and the placement.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-09-14 10:31:10 +02:00
2026-08-25 14:47:04 +02:00
2026-07-06 16:27:08 +02:00
2026-07-27 14:44:33 +02:00
2026-08-04 15:41:29 +02:00
2026-09-11 10:20:41 +00:00
2026-09-11 10:20:41 +00:00
2026-08-04 14:13:47 +02:00
2026-08-04 14:13:47 +02:00

AareDAQ

AareDAQ is the Data Acquisition system for MX beamlines at PSI.

S
Description
No description provided
Readme
32 MiB
v1.1.1
Latest
2026-09-18 16:39:53 +02:00
Languages
Python 100%