Page History
...
Constants of the type pixel_status are defined in processing of dark runs. They may not cover all possible bad pixel cases. New options for bad pixel status are in progress of development and implementation. Currently we may consider to use light data (e.g. new command det_raw_pixel_status - generates status_data), charge injection for new epix detectors (status_ci), and user defined bad pixel status (status_user), and so on. To deal with more and more emerging bad pixel status_* information we are going to collect them in repository with types status_*.
Method save_constants_in_repository - allows to user save constants in repository with recognizable file name.save constants in repository with recognizable file name.
Command deploy_constants
- finds in repository all available status_* files associated with detector/panel and requested run time-stamp,
- merge them by bits, preserve merged file under status_merged type,
- deploy this file in calibration database with type status_extra.
| Code Block | ||||
|---|---|---|---|---|
| ||||
| Code Block | ||||
/reg/g/psdm/detector/calib/constants/<dettype>/<panel-or-detector-id>/<status_type>/<dettype>_<panel-alias>_<YYYYMMDDHHmmSS-of_run>_<expname>_r<runnum>_status_<status_type>.txt
example:
/reg/g/psdm/detector/calib/constants/epix100a/3925999616-0996579585-0553648138-1232098304-1221641739-2650251521-3976200215/status_user/epix100a_0001_20160318191036_xpptut15_r0260_status_user.txt
/reg/g/psdm/detector/calib/constants/epix100a/3925999616-0996579585-0553648138-1232098304-1221641739-2650251521-3976200215/status_extra/epix100a_0001_20160318191036_xpptut15_r0260_status_extra.txt
merged to:
/reg/g/psdm/detector/calib/constants/epix100a/3925999616-0996579585-0553648138-1232098304-1221641739-2650251521-3976200215/status_merged/epix100a_0001_20160318191036_xpptut15_r0260_status_merged.txt
deployed to:
/cds/data/psdm/XPP/xpptut15/calib/Epix100a::CalibV1/XcsEndstation.0:Epix100a.1/status_extra/0-end.data |
...
Due to algorithms evolution precise bad pixel bit assignment may be different from description above. The best source of true information about bad pixel content and statistics is the log file. Another option is to look at code. Tables of this note contain references to both sources of information for different type of commands/detectors.
LCLS
| Detector | Dark processing Processing command | Log files directory | Log file name | Code |
|---|---|---|---|---|
| epix10ka | epix10ka_pedestals_calibration | /reg/g/psdm/detector/gains/epix10k/panels/logs/<year>/ | <timestamp>_log_epix10ka_pedestals_calibration_<uid>.txt | UtilsEpix10kaCalib.py#L522 |
| jungfrau | jungfrau_dark_proc | /reg/g/psdm/detector/gains/jungfrau/panels/logs/<year>/ | <timestamp>_log_jungfrau_dark_proc_<uid>.txt | UtilsCalib.py#L727 |
| other detectors | calibrun → det_ndarr_dark_proc | /reg/g/psdm/logs/calibman/<year>/<month>/ | <time-stamp>-log-<login>-<job-id>.txt | det_ndarr_raw_proc#L337 |
| other detectors | NEW: det_raw_pixel_status deploy_constants | /reg/g/psdm/detector/calib/constants/<dettype>/logs/<year>/ /reg/g/psdm/detector/calib/constants/<dettype>/logs/<year>/ | <time-stamp>_log_det_raw_pixel_status_<uid>.txt <time-stamp>_log_deploy_constants_<uid>.txt |
...
- Calibration Scripts Repository and Logging
- calibrun - LCLS CLI for dark processing
- Dark processing for LCLS2 area detectors
- Jungfrau and Epix10ka Calibration
- save_constants_in_repository - user's helper to save constants in repository
- det_raw_pixel_status - generates status_data - new algorithms in development
- deploy_constants - deploys constants from repository to DB
Overview
Content Tools