Plate Reader Modelling Update

dev discussion
3

So it is an arguably subjective prioritisation question:

  1. see temperature control & shaking as integral features of PlateReader → have PlateReader inherit from TemperatureController and Shaker, and then have the “big three” features (luminescence, absorbance, fluorescence) added directly in PlateReader.

  2. see temperature control & shaking as unique features that are not seen as common amongst all plate readers. As a result, they are not accessible via PlateReader but are accessible via specific PlateReader backends instead. (A clear example in this category: some CLARIOstar’s have injector modules → quite unique amongst plate readers and therefore should be accessible via the backend but not the frontend)

1 Like