mx/AareCommon
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 28 Wiki Activity
83 Commits 39 Branches 28 Tags
68ab034a5198f5345c26fb3bd9e295be5b100b5f
Commit Graph
4 Commits
Author SHA1 Message Date
GotthardGandClaude Fable 5 c095cb484e fix: transmission is a fraction of full beam everywhere
CI / lint (pull_request) Successful in 34s
Details
CI / test (3.12) (pull_request) Successful in 22s
Details
CI / test (3.13) (pull_request) Successful in 30s
Details
CI / test (3.11) (pull_request) Successful in 35s
Details
CI / lint (push) Canceled after 10s
Details
CI / test (3.11) (push) Canceled after 0s
Details
CI / test (3.12) (push) Canceled after 0s
Details
CI / test (3.13) (push) Canceled after 0s
Details
Build and Publish / release (push) Successful in 11s
Details 
DataCollectionParameters.transmission was the outlier: int percent 0-100
while BeamlineStatus / SimpleScanParameters / FluorescenceSpectrum already
used a 0-1 fraction. Per the DAQ/DB consensus it is now a strict
Annotated[float, Field(ge=0.0, le=1.0)] fraction (1.0 = full beam);
percent-scale values in (1.0, 100.0] fail validation by design instead of
being silently reinterpreted. RotationScanRequest / RasterGridRequest gain
the same constraint (production data is already fraction on those paths).

Human-facing surfaces (user spreadsheets, AareDB public API) stay percent;
their converters live in AareDB at the boundary.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HiGzkkuiZXei894cnJfgSg
 2026-09-07 23:58:44 +02:00
perl_d 7f74144615 ci: add more linting steps 2026-08-07 10:51:55 +02:00
perl_d dc6218e45f style: format to length 100 2026-07-02 12:52:45 +02:00
perl_d 3c27cbe75f refactor: extract common code from aaredaq 2026-07-02 09:56:37 +02:00