Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • short-term goal - support in a single place for calibration data  calibration data for detectors moving across LCLS experiments.
  • long-term goal - calibration store for LCLS-II.

It is assumed that hardware Hardware configuration of modern detectors will detector can be associated with detector index coming from DAQunique index hardwired on detector controller chip. This index will be used to recognize detector and extract hardly retrievable calibration data such as parameters for geometry, gain factors, masks etc. in case of transition of the detector from one experiment to another.

Requirements

  • Instrument / Experiment independent - detector can be moved between experiments, hatches, and instruments.
  • Portability - calibration data for particular detector should be portable as a self consistent file or (part of) calibration directory.
  • Interfaces - API, Command Line (CL), GUI for central management; management can ONLY be done through the API/CL/GUI in order to prevent adding/removing unknown files without history.
  • Time stamp (sec) - is THE ONLY value for validity range check; the same rules are applied to the time stamp , like for to the run number in current calibration system.
  • File name - the <detname> in the calibration store is equivalent to <dettype>-<detid> and is THE ONLY choice for the file name in the calibration store.
  • Aliases to the calibration file names and specific data  data can be used to simplify access.
  • Versions - support for versions of calibration data versions.
  • Support links Links to predecessor and successor - support access to predecessor and successor if this info is available.

Architecture

To accommodate requirements Detector Calibration Store (DCS) suppose to be implemented as a combination of FS & DB file system (FS) and data base (DB) files (hdf5 for uniformity). Functionality of the DCS from low bottom to top level can be listed as follows.

  • All calibration constants for particular version detector id (detid - index of the detector version) will be kept in a single hdf5 file named as <dettype>-<detid>.h5
    • Schema of this file contains a few levels which accounts account for constant types, time stamp ranges, versions of constants.
    • Beside main functionality each level contains dictionary of tagged parameters and dictionary of history records.
  • These files are grouped in the directory for detector type; ex.: cspad, cspad2x2, pnccd, etc.
    • The same directory contains files with aliases <aliases1>.als which map human readable detector name-and-version with appropriate <dettype>-<detid>.h5 file.
  • All detector type folders in regular case are collected under calib directory, although it is assumed that calibration files can be used directly.
  • The calib directory may be nested in three locations;
    • repository - experiment-independent space with FS back-up, contains most complete calibration files in terms of time stamp and versions,
    • experimental work-space - experiment-dependent space, contains squeezed version of calibration files with time stamp and versions essential for particular experiment,
    • local work-space - experiment-independent arbitrary spaceany local directory, with squeezed files similar to experimental work-space.

 The repository and experimental works-pace have predictable location in the file system, local work-space may have an arbitrary path. Direct file access also pick up calibration file from any place.

  •  Two-level API, CL and GUIlevels of interaction with DCS:
    • interaction with calibration data in particular calibration file,
      • add/get/remove constants for type, time stamp, version, etc.
      • add/remove/edit metadata.
    • data exchange between files in between repository, experimental and local workspace work-spaces.
      • file difference
      • transfer constants for type, time stamp, version, etc.
      • use web-service mechanism
  • Access Control Lists (ACL) depends on file location and is assumed to be
    • repository - limited to dedicated persons
    • experimental work-spaces - members of experimental group
    • local work-spaces - all


Calibration directory and files

...

instrument and experiment-independent path to calibration directory and file

  • <PATH>//reg/g/psdm/detector/calib

...

  • /
                                              <dettype>/<dettype>-<detid>.h5

Experiment calibration directory

experiment-dependent path to calibration directory and file

  • <PATH>/reg<INS>/d<experiment>/psdmcalib/<INS>/<experiment>/calib

...


  •                                                              <dettype>/<dettype>-<detid>.h5

Local calibration directory

local calib path to calibration directory and file

  • <path-to-calib><path>/calib/
    assuming further structure of the calibration directory                     <dettype>/<dettype>-<detid>.h5

Direct path to calibration file

direct path to the detector calibration file

  • <path><path-to-calib>/<dettype>-<detid>.h5

Structure of calibration directory

Everything in lower case:

Code Block
<path><path-to-calib>/calib/                                   # top calib directory
             <dettype>/                         # detector type folders
             cspad2x2/
             pnccd/
             epix100a/
             cspad/
                       <files>                  # level of files
                       <aliases1>.als           # file with a map of aliases to detector names
                       ...
                       <aliasesN>.als           # one of these files can be used to map "sources" to detector names
                       <dettype>-<detid>.h5     # files with detector-dependent calibration data
                       <dettype>-<detid>.h5

 


  • The calib directory is a top level DCS directory.
  • Detector type <dettype>

...

  • folders are used to organize files under the calib directory. In case of direct access to the hdf5 file the detector type is duplicated in the name of the file.
  • Unique part of the detector name <detid> is used to assign calibration file to the particular detector hardware configuration version. If the detector hardware configuration is changing

...

  • a new calibration file is created with new <detid>.
  • Information about predecessor and successor (if available) can be saved under the root level of the calibration file.
  • Current sources (ex: 'Camp.0:pnCCD.1' )

...

  • could be presented in the dictionary of aliases.

Calibration file structure

...

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 schemeschema (structure) of the DCS files <dettype>-<detid>.h5

Code Block
DCStore  DCType                   DCRange         DCVersion    

/                                                                   # top-root-level contains info for the unique detector version
 dettype (str)                                                      # detector type name, ex: cspad, pnccd, etc
 detid (str)                                                        # unique detector id, ex: 01234
 tscfile (float)                                                    # 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
 tagsdictpars (dict)                                                        # dictionary of tagsparameters associated with this version of detector
 history (dict)                                                     # dictionary of history records paired as (tstamp:record)
 <ctype>/                                                           # folder for calibration type, ex.: pedestals, rms, mask, etc
          ctype (str)                                               # calibration type name
          tagsdictpars (dict)                                               # dictionary of tagsparameters associated with calibration type
          history (dict)                                            # dictionary of history records paired as (tstamp:record)
          <tstamp-range>/                                           # folder for time stamp validity range
          <tstamp>[-<tstamp-end>]/                                  # folder for validity range. If <tstamp-end> is not specified - then valid to the end
                                  tsbegin (float)                   # time stamp for the beginning of the validity range
                                  tsend (float)                     # time stamp for the end of the validity range
                                  defaultv                          # reference to the default calibration, ex:  <vers-tstamp2>
                                  tagsdictpars (dict)                       # dictionary of tagsparameters associated with validity range
                                  history (dict)                    # dictionary of history records paired as (tstamp:record)
                                  <vers-tstamp1>/                   # folder for version created on tstamp1
                                                 tsvers (float)     # tstamp1 of this version production 
                                                 calib (ndarray)    # calibration data
                                                 history (dict)     # dictionary of history records paired as (tstamp:record)
                                                 tagsdictpars (dict)        # dictionary of tagsparameters, 
                                                                    #   ex: array size, number of dimensions, shape, data type, experiment, run, comments, author

                                  <vers-tstamp2>/                   # folder for version created on tstamp2
                                                 tsvers (float)
                                                 calib (ndarray)
                                                 history (dict)
                                                 tagsdictpars (dict)
           <tstamp2>[-<tstamp2-end>]/                               # folder for the next validity range.
 pedestals/                                                         # folder for the next calibration type, pedestals
 rms/                                                               # folder for the next calibration type, rms

...

Schema features

  • Detector name consists of a common part <dettype> and unique part <detid>.
  • Alias to the detector name should be kept in separate dictionary outside the file scheme.
  • Each detector may have optional predecessor, successor, and other tags parameters kept in the dictionary of parameters.
  • Calibration type folders contain info about calibrations of particular type, ex: pedestals, rms, status, mask, background, etc.
  • Each calibration type contains a set of time stamp ranges defining calibration validity range. If the second time stamp of the range is missing it is considered as infinity (by the end).
  • The time stamp range folder contains tstamp_begin, tstamp_end (int) values, dictionary of tags parameters associated with this folder, reference to the default calibration, and folders with calibration versions, distinguished by there production time stamp.
  • The number of calibration versions for each time stamp range is not limitedunlimited. Default calibration is defined by the reference default _ version defaultv.

Metadata in

...

dictpars

Below are the lists of metadata fields which potentially can be used to define detector configuration, calibration parameters etc.

Detector metadata

Field nameDescriptionMore details, example
dettypedetector typeCSPAD, CSPAD2X2, EPIX100A, etc.
detnamedetector unique name(if any) ex.: Camera1
detaliasalias nameif it is hard to memorize the entire name, ex.: 'cspad1'
detidxdetector indexinteger number which codes the hardware version
detidxaliassymbolic alias of the indexcan be used if it is hard to memorize the index integer number
detcompidx:001list of component indexesjust in case if we are going to retrieve calibration parameters for separate components
detidxprevdetector index for previous versiondetector index for previous version (if available) for the purpose of old calibration search
detidxnextdetector index for next versiondetector index for next version (if available) for the purpose of new calibration search
dettsectime-stamptime stamp associated with beginning of the validity range for new configuration
detcom:001comments for this hardware versionas it says {key:comment}
dettag
detpar:001other
tags
parametersjust in case if something is forgotten in this table

Calibration parameters' metadata

Field nameDescriptionMore details, example
calibtypecalibration typeex.: geometry, pixel_status, pixel_gain, pedestals, common_mode, etc.
tsectime stampbeginning of the validity range
exporiginal experiment(if available) where calibration constants were obtained
runnumoriginal run number(if available) where calibration constants were obtained
runbeginbegin run number(if available) for validity range
runendend run number(if available) for validity range
sourceoriginal DAQ data sourcedata source from DAQ, ex.: 'CxiDs2.0:Cspad.0'
srcaliasdata source aliasex.: 'cspad'
calibversversion
tag
parin order to access using symbolic name or some alias
calibversaliasversion aliasif it is hard to memorize version
tag
par
com:001comments for this versionas it says {key:comment}
tag
par:001other
tags
parametersjust in case if something is forgotten in this table

In case of numpy array their metadata are stored with an object.
Text file needs in n-d array metadata

n-d array metadata

Field nameDescriptionMore details, example
DTYPE(str) data typeint, float, double, etc.
NDIMS(int) number of dimensions (N)ex.: 3
DIM:1(int) size of dim.1ex.: 185
DIM:2(int) size of dim.2ex.: 388
.........
DIM:N(int) size of dim.Nex.: 2

API

Parameters

dettype (str) - detector type: cspad, cspad2x2, pnccd, fccd, opal, epix100a, etc.

...

versind (int) - consecutive version index assigned/mapped to the version production time stamp.

 


Initialization

Code Block
# Import
from PSCalib.DCStore import DCStore       # inport DCStore (Detector Calibration Store) object 

# Initialization
CPATH_DEFREPO = '<PATH>/reg/g/psdm/detector/calib'  # default calib directory
cpath = '<path>/calib'                    # localdefault calib directory
cpath = '<path>/<dettype>-<detid>.h5'     # direct to file
cpathrepository

cdir = env.calibDir()                     # '<PATH>/reg<INS>/d/psdm/<INS>/<experiment>/calib<experiment>/calib' - accept current directory

detnamepath = cdir + <dettype>

fname = '[path/]pnccd-12345678'                # standard name includes detector type, dash, and n-digit id number
detnamefname = '[path/]Camera1'                       # alias

cs = DCStore(cpath, detname)fname)                       # creates a DCStore object.
""" get calibration store object
    Input parameters:
    cpathfname [str] - path tofile name/alias of the hdf5 file or calibration directory. 
                  If cpath is a path to hdf5 file - next parameter is ignored.
                  If cpath=None - default path is used.
    detector 
"""
  • If path is missing - use repository.
  • If calibration file is not found - throw raise IOError('File %s is not available' % fname)

UI acess methods

Code Block
ctype = pedestals # status, rms, mask, gain, bkgd, common_mode, geometry, etc
tsp = tstamp parameter to identify constants, which can be retrieved from evt.run() - run number, evt
vers = None # for default or versind or version time stamp.

# generic access method:
obj = cs.get(ctype, tsp, vers=None)

Base class DCBase

Is reserved to support common methods of all project classes. For now it stands for manipulations with dictpars but not limited to.

Code Block
o = DCBase()

# acess methods
dictpars = o.dictpars()            # returns (dictpars) Ifdictionary cpathof isdictpars specifiedassociated aswith aeach pathobject
par to directory= (or defaulto.par(k) then detname can be an alias.  
    detname [str] - name/alias of the detector 
"""

UI acess methods

Code Block
ctype = pedestals # status,returns rms,par mask,value gain,for bkgd, common_mode, geometry, etc
tspkey k
log  = tstamp parameter to identify constants, which can be retrieved from evt.run() - run number, evt
vers = None # for default or versind or version time stamp.

# generic access method:
obj = cs.get(ctype, tsp, vers)

Base class DCBase

Is reserved to support common methods of all project classes. For now it stands for manipulations with tags but not limited to.

Code Block
o = DCBase()

# acess methods
tags = o.tagso.history(fmt)              # returns (str) history records preceded by the time stamp (default fmt='%Y-%m-%dT%H:%M:%S%Z') as a text 
d    = o.histdict()                    # returns (dict) history dictionary of tags associated with eachcurrent object
tag
# management = methods
o.tagset_dictpars(kd)                  # set #(d) returnsdictionary tagof valueparameters for key k
log  = object
o.history(fmtadd_par(k,v)              # returns (str) history records preceded by the time# stamp (default fmt='%Y-%m-%dT%H:%M:%S%Z') as a text 
d    = o.histdictadd (k,v) par to the dictionary of parameters for object
o.del_dictpars()                # returns (dict) history# dictionarydelete associatedall withparameters current object

# management methodsfrom the dictionary
o.setdel_tagspar(dk)                       # setdelete (dict)par dictionarywith of tags for objectkey k
o.addset_taghistory(k,vd)                     # addset (k,vdict) tagas toa thehistory dictionary of tagsthe forcurrent object
o.deladd_tagshistory(rec, ts)             # add (str) record with (float) time stamp to the #history delete all tags from the dictionary
o.del_tag(k)             dictionary (ts:rec). If ts is None - call current time is used as a key. 

Class DCStore

Code Block
cs = DCStore(cpath, detname)       # (str) path #to deletecalib tagdirectory withor key k
o.set_history(dfile, (str) detector name

# acess methods
nda   = cs.get(ctype, tsp, vers)   # (str) ctype - calibration type
   #     set (dict) as a history dictionary of the current object
o.add_history(rec, ts)             # add (str) record with# (float...) tsp time- stampparameter to theget historytime dictionarystamp (ts:rec). If ts is None - call current time is used as a key. 

Class DCStore

Code Block
cs = DCStore(cpath, detname)evt, runnum, ts_sec) 
                       # (str) path to calib directory or file, (str) detector name

# acess methods
nda   =# cs.get(ctype, tsp,(int) vers) - version # (str) ctypeof calibration, None - calibrationuse default type
tscfile     = cs.tscfile()         # (int) time stamp of the file creation
dettype     = cs.dettype()         # (...str) tspdetector -type
detid parameter to get time stamp (evt, runnum, ts_sec= cs.detid() 
          # (str) detector id
detname     = cs.detname()         # (str) detector name of self object
predecessor #= cs.predecessor(int) vers  - version of calibration, None - use default 
tscfile# (str) detname of predecessor or None
successor     = cs.tscfilesuccessor()         # (intstr) time stampdetname of thesuccessor fileor creationNone
dettypectypes      = cs.dettypectypes()          # (strlist) detector type
detid calibration types in the file
cto         = cs.detidctypeobj(ctype)   # (DCType ~ h5py.Group) calibration type object

#  # (strmanagement methods
cs.set_tscfile(ts) detector id
detname     = cs.detname()         # set (strint) detectortime namestamp of self object
predecessor = cs.predecessor(the file creation  
cs.set_dettype(dettype)     # (str) detname of predecessor or None
successor # set = (str) detector type
cs.successorset_detid(detid)       # (str) detname of successor or None
ctypes   # set (str) =detector id
cs.ctypesset_detname(detname)            # set (liststr) calibrationdetector typesname inof theself file
ctoobject
cs.set_predecessor(pred)          = cs.ctypeobj(ctype)   # (DCType ~ h5py.Group) calibration type object

# management methods # set (str) detname of predecessor or None
cs.set_tscfilesuccessor(tssucc)                 # set (intstr) timedetname stamp of thesuccessor fileor creation  None
cs.setadd_dettypectype(dettypectype)                # setadd (str) detectorcalibration type to the DCStore object
cs.setdel_detidctype(detidctype)                # delete setctype (str) detector id
cs.set_detname(detnamefrom the DCStore object
cs.save(path)            #   set (str) detector name of self object
cs.set_predecessor(pred)           # set (str) detname of predecessor or None
cs.set_successor(succ) # save current calibration in the file specified by path, if path is Null - update current file.

Class DCType

Code Block
cto = DCType(dettype)              # set (str) detname of successor or None
cs.add_ctype(ctype)detector type

# acess methods
ctype      = cto.ctype()           # add (str) calibration type to the DCStore object
cs.del_ctype(ctypeof ctype name
tsranges   = cto.ranges()          # (list) of time ranges for ctype
tsro # delete ctype (str) from the DCStore= object
cscto.saverangeobj(pathtsrange) # (DCRange ~ h5py.Group) time stamp validity range object

# management methods
cto.add_range(tsr)                 # save current calibration in the file specified by path, if path is Null - update current file.

Class DCType

 add (str) of time ranges for ctype
cto.del_range(tsr)                 # delete range from the DCType object

Class DCRange

Code Block
tsro = DCRange(tsrange)
Code Block
cto = DCType(dettype)              # (str) detector type

# acess methods
ctype      = cto.ctype(time stamp validity range
tsro = DCRange(tsbegin, tsend)     # (int,int) time stamp validity  range

# (str) of ctype name
tsrangesacess methods
tsbegin     = ctotsro.rangesbegin()          # (listint) oftime timestamp rangesbeginning forvalidity ctyperange
tsrotsend       = ctotsro.rangeobjend(tsrange)  #  (DCRange ~ h5py.Group) time stamp validity range object

# management methods
cto.add_range(tsr(int) time stamp ending validity range
versions    = tsro.versions()      # #(list addof (strfloat) versions of calibrations
versodef time  ranges for= ctype
cto.del_range(tsrtsro.versdef()       # (DCVersion ~ h5py.Group) reference to the default version  # delete range from the DCType object

Class DCRange

Code Block
tsro = DCRange(tsrangein the time-range object
verso       = tsro.versobj(vers)   # (DCVersion ~ h5py.Group) specified version in the time-range object

# management (strmethods
tsro.set_begin(tsbegin) time stamp validity range
tsro = DCRange(tsbegin, tsend)     # set (int,int) time stamp beginning validity range

# acess methods
tsbegintsro.set_end(tsend)       = tsro.begin()        # #set (int) time stamp beginningending validity range
tsendtsro.add_version(vers)        = tsro.end()    # set (DCVersion ~ h5py.Group) versions  # (int) time stamp ending validity range
versionsof calibrations
tsro.set_versdef(vers)      = tsro.versions()      # set (listDCVersion of~ floath5py.Group) versions of calibrations
versodef    = tsro.versdefdel_version(vers)       # (DCVersion ~ h5py.Group) reference to the# defaultdelete version in the time-range object
verso

Class DCVersion

Code Block
verso = DCVersion(vers)         = tsro.versobj(vers)   # (DCVersion ~ h5py.Group) specifiedstr) version in the time-range objectname

# managementacess methods
tsro.set_begin(tsbegin)tsvers      = verso.tsprod()       # set (int) time stamp of beginningthe validityversion range
tsro.set_end(tsend)production
calibdata   =  verso.calib()           # set (intnp.array) time stamp ending validity range
tsro.add_version(verscalibration array

# management methods
verso.set_tsprod(tsprod)             # set (DCVersion ~ h5py.Group) versions of calibrations
tsro.set_versdef(vers)int) time stamp of the version production
verso.add_calib(nda)               # set (DCVersion ~ h5py.Groupnp.array) versions of calibrations
tsro.del_version(vers)             # delete version

Class DCVersion

Code Block
verso = DCVersion(vers)            # (str) version name

# acess methods
tsvers      = verso.tsprod()       # (int) time stamp of the version production
calibdata   = verso.calib()        # (np.array) calibration array

# management methods
verso.set_tsprod(tsprod)           # set (int) time stamp of the version production
verso.add_calib(nda)               # set (np.array) calibration array

TBD

Open questions

  • What is included in the detector Id version?  FEE version, controller version, etc?
  • when constants are updated (file open to write) they are not available... Lock to resolve.

Data flow

  • who produces and supply constants
  • who is allowed to submit constants
  • who is allowed to access constants
  • ACL inside API or using OS
  • ACL for all or particular detector/type/ etc.

References

calibration array

TBD

Open questions

  • logic for default version
    • always last added constants
    • set specified version
    • what to do with default if new version is added?


  • when constants are updated (file open to write) they are not available... Lock to resolve.

Data flow

  • who produces and supply constants
  • who is allowed to submit constants
  • who is allowed to access constants
  • ACL inside API or using OS
  • ACL for all or particular detector/type/ etc.

2016-10-27 Mtg with cpo

  • table of aliases with records: <alias> <source> <begin> <end>
  • repository
  • <PATH>/detector/calib  "g" or "d"
  • epix100a full name  - 6 numbers of hardware versions, firmware version is a 7th number
  • time double to two integers or int64 (32bit-sec, 32-bit-nsec)
  • geometry needs to be saved as a text
  • repository file has geometry and pixel_gain - like constants
  • do not search in <experiment>/calib
  • access through network for AMI (cpo: TCP with hardwired IP addresses, m:web service/reddis)

References

...