VIB-1: confirmed

[decarlof]

Title (paste into the GitHub "Title" field)

VIB-1: confirmed — vibration / flat-field stability measurements use the same physical FLIR Oryx (model ORX-10G-51S5M, serial 19173710, EPICS prefix 2bmSP1:) that serves as the 2-BM-B microscope camera 0; run at high frame rate (~99 fps, 1000-frame HDF5 stream) for the vibration capture; no separate high-speed camera at 2-BM

VIB-1: Cora's provisional answer is correct. Same physical camera, same serial, same EPICS prefix; the "vibration measurement" capability is just a high-frame-rate operating mode on the existing microscope detector.

Same-camera evidence

Three independent doc citations triangulate the same hardware:

Source	Citation
ops/item_010.rst (camera IOC setup)	epicsEnvSet("CAMERA_NAME", "FLIR-Oryx ORX-10G-51S5M-19173710"); CAMERA_INFO: IP 169.254.0.51; prefix 2bmbSP1: ⇒ this is the 2-BM-B microscope camera 0.
ops/item_021.rst line 181 (DMM vibration / flat-field analysis)	"Camera: FLIR Oryx ORX-10G-51S5M (s/n 19173710)" ⇒ this is the vibration-measurement camera.
manual/item_020.rst MCTOptics block, camera-0 row	Manufacturer FLIR, model Oryx ORX-10G-51S5M, serial 19173710, prefix 2bmSP1:cam1:.

All three converge on the same serial number (19173710) and the same areaDetector prefix (2bmSP1:). The microscope detector and the vibration-measurement camera are the same physical unit.

Operating-mode difference

The same camera is operated in two distinct modes depending on the task:

Mode	Use case	Typical acquisition
Microscope mode	Tomography projections, scout images, alignment	Standard tomoscan acquisition; frame rate matches the rotation-stage cadence (typically 10–50 fps); 16-bit conversion via the ADSpinnaker ROI / Stats pipeline.
Vibration / flat-field stability mode	Per ops/item_021 Section "DMM-induced stripes": measure stripe pattern motion against S11-AHU505_1000frms_99fps_001.h5 reference	1000 frames at 99 fps, ~10 ms exposure, continuous HDF5 stream; freezes the DMM-induced stripe motion enough to characterise the vibration spectrum.

The mode switch is purely a software / scan configuration (AcquireTime, NumImages, file-plugin output), not a hardware change. Same camera, same lens (typically the 1.1× objective at 2-BM-B), same scintillator.

No separate high-speed camera

Cora's question explicitly asks for confirmation that there is no separate high-speed camera. Confirmed: at 2-BM-B today, the FLIR Oryx 5MP (serial 19173710) is the only camera used for vibration / flat-field stability work. The Oryx 31MP (camera 1, prefix 2bmSP2:, serial 22150530) is a separate physical unit but is operated only as the high-resolution microscope detect
or; it does not double as a high-frame-rate vibration camera.

(Historical note: the previously-installed PCO Dimax HS was a dedicated high-speed camera and has been decommissioned per the cora Decommissioned block on the 2-BM assets page, rationale "superseded by the FLIR Oryx detector chain" — cora #89. So while a separate high-speed camera USED to exist, it doesn't today.)

CORA-side application

Cora's provisional model — "the active FLIR Oryx (serial 19173710) run fast; no separate high-speed camera" — promotes to confirmed. To complete the model:

• One Camera Asset (the existing 2-BM-B microscope camera 0 registration), bound to serial 19173710. No separate Asset for the vibration role.
• Two operating modes on that Asset, possibly modelled as two cora Method options:
  • acquire_projections (microscope mode): standard frame rate, per-tomoscan configuration
  • acquire_vibration_stream (vibration / flat-field stability mode): 1000 frames × 99 fps + HDF5 stream
• Configuration Settings that differ between modes: AcquireTime, NumImages, FilePlugin output mode, possibly ROI enable. The hardware itself (lens, scintillator, port) is unchanged.
• Per-Run provenance: each Run can record which mode the camera was operated in; vibration Runs would also carry the per-Run reference dataset (e.g., flats_01 from 22-Feb-2026 per ops/item_021).

Downstream alignment

The MCTOptics block camera 0 entry in item_020.rst (latest commit pending) now carries an explicit "Dual-role" annotation flagging that the same physical camera (serial 19173710) serves as the vibration / flat-field stability measurement camera at ~99 fps; cross-references ops/item_021 (vibration an
alysis) and ops/item_070 (vibration-frequency / flat-field-stability measurement protocol).

Cross-references

• ops/item_010 — camera IOC setup with the serial / IP / model annotations.
• ops/item_021 — DMM ops page with the vibration / flat-field analysis section that documents the 99 fps operating mode.
• ops/item_070 — Vibration Frequency Measurement / Flat Field Stability Measurement procedure (cited from item_021).
• Cora docs(equipment): define TimingController family + fix 2-BM doc/descriptor drift #89 — Decommissioned PCO Dimax HS (the prior high-speed camera, now retired).

Net

VIB-1 answer: same physical FLIR Oryx ORX-10G-51S5M serial 19173710 (EPICS prefix 2bmSP1:) is used both as the microscope camera 0 AND as the vibration / flat-field stability measurement camera. Vibration mode = 99 fps × 1000 frames HDF5 stream. No separate high-speed camera at 2-BM today (PCO Dimax HS was the prior dedicated high-speed unit; decommissioned per cora #89
). Cora's provisional answer is confirmed; one Camera Asset with two operating-mode Methods is the right model.

[xmap]

Resolved by #299 (merged). VIB-1 folded: the vibration measurement uses the same physical FLIR Oryx (serial 19173710) in a high-frame-rate mode, recorded as a note on the Camera; no separate hardware.