Page History
...
Code Block |
---|
/reg/g/psdm/detector/alignment/epix10ka2m/calib/Epix10ka2M::CalibV1/NoDetector.0:Epix10ka2M.0/geometry/0-end.data /reg/g/psdm/detector/alignment/epix10kaquad/calib/Epix10kaQuad::CalibV1/NoDetector.0:Epix10kaQuad.0/geometry/0-end.data /reg/g/psdm/detector/alignment/epix10ka/calib/Epix10ka::CalibV1/MecTargetChamber.0:Epix10ka.1/geometry/0-end.data |
Gain
Code Block | ||||
---|---|---|---|---|
| ||||
Blaj, Gabriel 2018-12-04, 2:08 PMO'Grady, Paul Christopher;Nelson, Silke;Dubrovin, Mikhail;Hart, Philip Adam Hi, You could try to use the gain files obtained with the pulser. They are not great but might work. For a better gain calibration, we should use single photon data. There is sufficient 1 photon data taken during the first testing at XCS, but it will take me a few days to calculate the gains. I would actually advocate returning the number of photons (as we discussed in a meeting a few months ago). Even without a calibration it can be easily calculated from the (average) gains: High (FH and AHL): 132 ADU/9.5 keV Medium (FM and AML): 43 ADU/9.5 keV Low (FL, AHL, AML): 1.32 ADU/9.5 keV (Just a note, while the pulser is not great for calibrating gains, it works fine for offset calibration) Thanks, Gabriel |
...
- mbits = 1 - masks edges, +2 - masks central rows and columns.
- width - number of edge rows or columns to mask, def=1
- wcentral - number of central rows or columns to mask, def=1
plot for mask_geo + 1:
status_as_mask
...
plots for mask_status + 1 for mode=0 and 3:
References
...
Overview
Content Tools