Page History
...
| Code Block | ||
|---|---|---|
| ||
raw data found/selected in 999 events [I] L0688 begin data summary stage [I] L0111 evaluate_limits RMS: ave=4.783 std=1.303 limits low=0.001 high=12.604 [I] L0111 evaluate_limits AVE: ave=14191.873 std=457.903 limits low=11444.455 high=16000.000 [I] L0733 bad pixel status: status 1: 244 pixel rms > 12.604 status 2: 550 pixel rms < 0.001 status 4: 418 pixel intensity > 16000 in more than 0.1 fraction of events status 8: 132 pixel intensity < 1 in more than 0.1 fraction of events status 16: 0 pixel average > 16000 status 32: 918 pixel average < 11444.5 [I] L0108 status 64: 139 pixel with bad gain mode switch for jungfrau only! |
Finding Bad Pixel status information
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
Status extra
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 (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.
| 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 |
Finding Bad Pixel status information
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 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 | |||||||||
| Detector | Dark processing command | Log files directory | Log file name | Code | ||||||
| epix10ka | epix10ka_pedestals_calibration | /reg/g/psdm/detectorlogs/gainscalibman/epix10k<year>/panels/logs/<year>/ | <timestamp>_log_epix10ka_pedestals_calibration_<uid>.txt | UtilsEpix10kaCalib.py#L522 | jungfrau | <month>/ | <time-stamp>-log-<login>-<job-id>.txt | det_ndarr_raw_proc#L337 | ||
| other detectors | NEW: det_raw_pixel_status deploy_constants jungfrau_dark_proc | /reg/g/psdm/detector/ gainscalib/ jungfrauconstants/ panels<dettype>/logs/<year>/ | <timestamp>_log_jungfrau_dark_proc_<uid>.txt | UtilsCalib.py#L727 | other detectors | calibrun → det_ndarr_dark_proc | /reg/g/psdm/detector/calib/constants/<dettype>/logs/ calibman/<year> /<month>/ | <time-stamp>_log_det_raw_pixel_status_<uid>.txt <time- | log-<login>-<job-id>stamp>_log_deploy_constants_<uid>.txt | ndarrrawproc#L337 |
Examples
| Code Block | ||||
|---|---|---|---|---|
| ||||
process panel:15 id:0000000002-0173621761-3221225494-1014046789-0019435010-0000000000-0000000000 [I] L0111 evaluate_limits RMS: ave=3.418 std=0.344 limits low=1.353 high=5.483 [I] L0111 evaluate_limits AVE: ave=3155.633 std=147.439 limits low=2271.000 high=4040.267 [I] L0528 Bad pixel status: status 1: 35 pixel rms > 5.483 status 2: 0 pixel rms < 1.353 status 4: 0 pixel intensity > 16000 in more than 0.1 fraction of events status 8: 0 pixel intensity < 1 in more than 0.1 fraction of events status 16: 13 pixel average > 4040.27 status 32: 354 pixel average < 2271 |
...
- 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
Overview
Content Tools