What CORA needs the SYRMEP team to confirm before the model can be trusted.
SYRMEP was reverse-engineered from public material (the elettra.eu SYRMEP pages, the EPJ Plus 2024 SYRMEP review, and the J. Synchrotron Rad. 2023 large-FOV paper). The hardware facts are read from those sources, but the control handles are not in public source: the in-house DonkiOrchestra scan engine's source location is unconfirmed and the acquisition code lives in the private gitlab.elettra.eusyrmep_acquisition group. So unlike the ID32 BLISS scaffold, the device handles on the device pages are confirm-pending placeholders rather than read addresses. This is CORA's first Elettra Site and first Tango / DonkiOrchestra controls house-style. Each row below is a fact the beamline team owns, not a CORA modelling choice (those are on Model). It is a delete-on-answer queue. Priorities are Blocks-build, Blocks-go-live, and Nice-to-have.
The Elettra storage-ring state SYRMEP reads (the 2.0 GeV / 300 mA and 2.4 GeV modes; current, fill).
Observe-only machine state, a loose StorageRing; exact Tango handles pending.
The machine-state observation.
MONO-1
Blocks-go-live
The Si(111) DCM energy range and the authoritative bound: the EPJ Plus 2024 review states mono 10-40 keV, the elettra.eu spec still lists 9-40 keV. The Bragg / offset handles.
A Monochromator (Si(111), fixed-exit, 20 mm offset); energy a PseudoAxis; range 10-40 keV mono.
The monochromator and incident-energy Assets.
MODE-1
Blocks-go-live
The mono / white (pink) beam switch: how the beam bypasses the DCM, and the white-beam energy (~16-30 keV average).
The beam mode is a per-Asset setting on the Monochromator (the 2-BM DMM insert/retract precedent).
The beam-mode modelling.
OPT-1
Nice-to-have
The white-beam-defining mask dimensions and drawing.
A fixed Mask upstream of the optics.
The mask Asset detail.
OPT-2
Blocks-go-live
The laminar-beam slit blade-axis map and handles, and the beam dimensions (sources cite ~120 x 4 mm at 20 m and ~160 x 5 mm at 23 m).
Slits bound to Slit; a ~120-160 mm wide, ~4-5 mm tall laminar beam at 7 mrad acceptance.
The slit Asset detail and beam geometry.
FOIL-1
Nice-to-have
The absorption / beam-hardening filter foils and the selector handle.
The rotation stages: the heavy-payload rotator (up to 120 kg, 1-20 deg/s, 0.02 deg) is documented, but the standard sample rotation stage range / bearing / model and the rotator wobble spec are not.
A RotaryStage for the tomographic theta; a standard-stage variant and the wobble spec pending.
The rotation-stage modelling.
SAMPLE-1
Blocks-go-live
The five-axis sample-positioning stage: motor vendors, micro-positioning resolution, axes, and handles.
The technique scope: core tomography reuses catalog Methods, but helical CT, white-beam tomography, and phase retrieval are not yet catalog Methods.
The core tomography Practices reuse catalog Methods; the rest are pending and render unlinked.
Whether the new techniques enter the catalog (a CORA-scope call on Model).
COMPUTE-1
Nice-to-have
The reconstruction pipeline (the SYRMEP Tomo Project: phase retrieval, ring removal, FBP / iterative on ASTRA + TomoPy) and whether CORA records its invocation as Method / Compute provenance.
Post-acquisition compute CORA records as provenance, not data it owns.
The compute-provenance modelling.
SUP-1
Nice-to-have
The facility supplies a run draws on (cooling water for the optics, the vacuum extent of the white-beam path).
Every row above is a question about the real beamline, and any of them can be
answered by someone who knows the hardware. You do not need to edit this page
or know where it lives.
Open a short issue at
github.com/xmap/cora/issues, quote the
item ID, and write the answer in plain text. One answer is as welcome as
several. If you do not use GitHub, send the same thing to whoever shared this
page with you. If a row turns out to be a controls, network, or engineering
question, pass it to the right person or tell us who that is.
The priorities mean: Blocks-build, your answer changes the structure of the
description, so CORA cannot finalise it until you reply; Blocks-go-live, a
guess is fine for the description, but the real value is needed before CORA
controls or observes the hardware; Nice-to-have, extra detail for the record.
Once an item is confirmed we record the value and delete the row, so this page
always shows only what is still open.