Page History
...
In LCLS-II calibration constants resides in the data bases. Access to the DB can be done through python API, CLI, and GUI. At regular deployment calibration constants goes in two databases designated for experiment and for detector. In regular request for calibration constants experimental DB is addressed first, then if constants not found, the detector DB is included in search. These features are sufficient for regular operations with detectors.
...
Calibration DB names
Calibration constant on MongoDB server are grouped in databases identified by their names
...
Constants can be deployed with commands cdb and epix10ka_deploy_constants, see for detail
- cdb -hcdb add <parameters> ...
- epix10ka_deploy_constants <parameters>... -h
for example
- cdb add -e rixx45619 -d epixhr2x2_000001 -t 2021-10-01T00:00:00-0800 -c pedestals -f mypeds
- cdb add -e rixx45619 -d epixhr2x2_000001 -t 2021-10-01T00:00:00-0800 -c geometry -f mygeo -i txt
- epix10ka_deploy_constants -e rixx45619 -d epixhr -r121 -D
Use constants
DB management tool
Browsing and management of calibration DB can be done with command
launching multipurpose GUI application.
Get corrected data
Example of Example script to get calibrated datacorrected data where usage of calibration constants is hidden in det.raw.calib/image methods,
| Code Block |
|---|
ds = DataSource(exp='rixx45619', run=121)
det = run.Detector('epixhr')
arr = det.raw.calib(evt)
img = det.raw.image(evt) |
Direct access to calibration constants
For details see Area Detector Interface - Calibration Constants
All detector calibration constants (np.array) and associated metadata (dict) are available through the dictionary det.calibconst with calibration type as a key. For example,
|
Possible calibration types: pedestals, pixel_status, pixel_rms, pixel_gain, pixel_mask, etc.
References
Overview
Content Tools