Page History
...
| Code Block |
|---|
<path>/calib/
<dettype>/
cspad2x2/
pnccd/
epix100a/
cspad/
<calib-files>
<dettype>-<detid>.h5
<dettype>-<detid>.h5 |
Scheme of the calibration file
Calibration data hierarchical scheme
Access to calibration data is based on time stamp. Time stamp internally is presented in Unix time sec which can be easily converted forth and back to human readable format YYYY-MM-DDTHH:MM:SS+HH:MM
The scheme of the calibration data, which presumably will be implemented in <dettype>-<detid>.h5
| Code Block |
|---|
<dettype>-<detid>/ # root-level shows the unique detector name
tstamp_created (uint) # time stamp of creation of this structure
predecessor (str) # name of the previous detector if available or None
successor (str) # name of the next detector if available or None
tags (dict) # dictionary of tags, ex: comments
<ctype>/ # folder for calibration type
<tstamp>[-<tstamp-end>]/ # folder for validity range. If <tstamp-end> is not specified - then valid to the end
tstamp_begin (uint) # time stamp for the beginning of the validity range
tstamp_end (uint) # time stamp for the end of the validity range
default_version # reference to the default calibration, ex: <prod-tstamp2>
<tstamp1-prod>/ # tstamp1 - creation date
tstamp_prod (uint) # tstamp1 of production
calib (ndarray) # calibration data
tags (dict) # dictionary of tags,
# ex: array size, number of dimensions, shape, data type, experiment, run, comments, author
<tstamp2-prod>/ # tstamp2 - creation date for other version
tstamp_prod (uint) # tstamp2 of production
calib (ndarray)
tags (dict)
pedestals/ # folder for next calibration type, pedestals
rms/ # folder for next calibration type, rms
|
| Code Block |
|
Data flow
- who produces and supply constants
- who is allowed to submit constants
- whi is allowed to access constants
- ACL inside API or using OS
- ACL for all or particular detector/type/ etc.
...
Overview
Content Tools