[BioCam]

The Problem

The v1 CLARIOstar reads absorbance and fluorescence, but not luminescence, although the reader reports a luminescence measurement channel. Luminescence assays (luciferase reporters, ATP viability, BRET) cannot run on it through PyLabRobot.

PR Content

• Luminescence.measure: a point read of each well from the top, with enhanced dynamic range, through one emission band of the emission monochromator.
• Its settings: emission_wavelength / emission_bandwidth (580 / 80 nm), gain (3500), focal_height (None: a quarter up the well, as for fluorescence), normalization_time (1.00 s), measurement_interval (0.80 s), plus MeasurementSettings (settling, corner, reading direction) and ShakeSettings as the other modes take them.
• The emission limit follows the photomultipliers, as for fluorescence but the other way round: the extended range (up to 840 nm) needs the extended-red photomultiplier on the luminescence path - fitted, and crossed over on a dual-photomultiplier reader; otherwise 740 nm.
• pylabrobot.lib.luminescence.LuminescenceResult, the same for every plate reader; CLARIOstarLuminescenceResult adds the gain.
• driver.luminescence / CLARIOstarDevice.luminescence, built at setup only when the reader reports a luminescence channel.
• FluorescenceConfiguration.maximum_chromatics is renamed maximum_fluorescence_channels.
• Comments, docstrings and test names across the CLARIOstar driver are reworded; nothing changes on the wire. The test data files are renamed *_ground_truth.json.gz.
• Until a luminescent sample has been read on hardware, measure warns that luminescence is untested.

🤖 Generated with Claude Code