Permissions
All databases will be world-readable.
Table of write-permissions:
Configuration Database | Experiment Calibration Database | Global ("Cross-experiment") Calibration Database |
---|---|---|
OPR accounts | per-experiment logbook groups | expert groups |
expert groups | expert groups |
- expert groups means unix groups like ps-xpp, psdata
- there will be cross-hutch-expert protection: e.g. ps-xpp won't have permission to write to the TMO databases
- Murali has said experts may have to do an extra step (e.g. set an environment variable) in order use a different URL/end-point for expert-group access
Calibration Database Access Patterns
- detector-specific calibrations will access constants using detectorType_segmentSerialNumberString, where segmentSerialNumber is either read from the detector hardware by the daq (ideal, like epix) or managed administratively (more difficult)
- algorithm-specific calibrations (e.g. hexanode, "pop" electron image inversion algorithm) will access constants using algorithmType_serialNumberString, where both halves of that field are administratively managed.
- this means that multi-segment detectors will need to do multiple database fetches (bad) but that detector segments can be shuffled around without changing the calib database (good)
- calibration constants should not be exposed to ami, but only used internally by the detector interface or the algorithm
Overview
Content Tools