Model¶
The developer's by-kind index: where each CORA aggregate's BMM content lives. It hosts no content of its own. Design-phase scaffold.
For the aggregate shapes see the architecture model and the per-BC modules.
| Aggregate (BC) | Where at BMM |
|---|---|
| Asset (Equipment) | Inventory (in this zone) |
| Computed / virtual axes (Equipment) | Inventory (EnergyAxis) |
| Capability, Method (Recipe) | Techniques |
| Enclosure (Enclosure) | The beamline (6-BM-A optics, 6-BM-B endstation) |
| Zone, Conduit, Policy (Trust); Actor (Access) | Governance |
| Procedure, Recipe, Caution, Supply, Subject, Run, Campaign, Dataset, Decision | deferred (design-phase; see below) |
Deliberately not here yet¶
This is a design-phase scaffold (descriptor + docs), mirroring HXN and the Diamond beamlines. Left out on purpose:
- The
energy_scanCapability. BMM is the first real consumer of the energy-scan sweep the catalog already anticipates (pending in code), but a Capability is coined when a conduct-path consumes it, not at scaffold time (see Techniques, ENERGY-1). This is the live earn-the-abstraction question BMM surfaces. - No new Family. BMM reuses existing catalog Families: the ion chambers reuse
FluxMonitor(graduated in #353), the fluorescence detector the catalogEnergyDispersiveSpectrometer, plus the looseScreen(held, FLAG-1) for the diagnostic screens. The sample wheel reusesRotaryStage; whether a sample-changer Family is earned across BMM and the Diamond robots is open (WHEEL-1). - Operations and experiment views, integration scenarios, vendor Models. A runbook and registered Assets for a beamline CORA does not yet drive would be invention; they land when the design firms and the team confirms. The 2-BM Model page shows the shape a fully-modelled deployment carries.