Diamond Light Source¶
Diamond Light Source is the synchrotron site its beamlines run at. This page is the home for the facility-level facts an experiment inherits but does not own: the techniques adapted here, the resources a run draws on, the safety envelope it clears, and the people and agents who act in it. The beamline links up to these rather than restating them.
Generated from the site descriptor
This page is generated from deployments/diamond/site.yaml. Edit the descriptor, not this page.
| Property | Value |
|---|---|
| Facility code | diamond |
| Kind | Site |
| Institution | Diamond Light Source Ltd, Harwell Campus, Didcot, UK |
| Beamlines | I03, I06, I10, I11, I13-1, I15-1, I19, I20-1, I22, I24 |
The techniques adapted here¶
A Practice is Diamond Light Source's facility-tuned form of a cross-facility Method: the ISA-88 Site Recipe layer. The Method names a technique abstractly in the Catalog; the Practice is how the beamline runs it here. Each row links up to the Method it adapts.
| Practice | Method |
|---|---|
Planned: I22_small_angle_scattering_practice, I22_wide_angle_scattering_practice, I22_simultaneous_saxs_waxs_practice, I03_mx_data_collection_practice, I03_grid_scan_practice, I03_autonomous_sample_exchange_practice, I15-1_total_scattering_practice, I11_powder_diffraction_practice, I24_serial_crystallography_practice, I06_xmcd_practice, I06_xmld_practice, I06_peem_practice, I06_resonant_diffraction_practice, I10_resonant_scattering_practice, I10_reflectivity_practice, I10_xmcd_practice, I10_xmld_practice, I20-1_ede_practice, I19_diffraction_practice, I13-1_ptychography_practice.
The resources you draw on¶
Supplies are the continuously-available facility resources a run needs present before it can start: beam, cooling, vacuum. The facility tracks their availability; a run's required supplies are checked at the pre-flight gate.
| Supply | Kind |
|---|---|
Planned: Storage-ring beam current, Cooling water, Beamline vacuum.
The safety envelope¶
Before an experiment runs, it clears the facility's safety forms (Clearances), and operators carry forward hazards and quirks as Cautions. Both gate or advise the work without being part of the measurement itself.
| Clearance | Kind | Binds |
|---|---|---|
Planned: Diamond personnel safety system.
Who acts here¶
Every action CORA records is attributed to a principal. At Diamond Light Source those are the people registered facility-wide (the operator on shift, safety reviewers, proposal PIs) and the autonomous agents. Human display names live in actor_profile (the editable, forgettable layer), not in the event-sourced Actor record, which carries only id and kind.
| Person or service | Kind |
|---|---|
Planned: Diamond beamline staff, Diamond safety review.
Agents are principals too. Each one's id is shared with an Access Actor (kind=agent) through a single cross-BC atomic write, so an agent's writes attribute the same way a person's do. The agents active here today are advisory: they observe and write Decisions, and never gate Run state. The planned agents are deterministic and rule-based; when enabled they act only by issuing a command the spine already exposes, through the same authorized path a person uses.
| Agent | Version | Model |
|---|---|---|
How Diamond Light Source is modeled¶
Diamond Light Source itself is not an Asset: it is a Federation Facility with FacilityKind = Site (facility_code = "diamond"). The beamlines it hosts are the root Assets (tier = Unit, parent_id = None), each bound to the Site directly by facility_code. See the CORA model for the aggregate shapes.
| Asset | Tier | facility_code | Hosts |
|---|---|---|---|
I03 |
Unit |
diamond |
I03 |
I06 |
Unit |
diamond |
I06 |
I10 |
Unit |
diamond |
I10 |
I11 |
Unit |
diamond |
I11 |
I13-1 |
Unit |
diamond |
I13-1 |
I15-1 |
Unit |
diamond |
I15-1 |
I19 |
Unit |
diamond |
I19 |
I20-1 |
Unit |
diamond |
I20-1 |
I22 |
Unit |
diamond |
I22 |
I24 |
Unit |
diamond |
I24 |
Sub-systems and devices nested under a beamline are Assets with tier = Component or tier = Device, linked via parent_id. Being non-root, they do not carry facility_code; they inherit facility scope through the parent_id tree.