|
1 | 1 | # Calibration constants |
2 | 2 |
|
3 | 3 | The `extra.calibration` module helps you to find & load detector calibration |
4 | | -constants stored in the [Calibration Catalog](https://in.xfel.eu/calibration/). |
| 4 | +data stored in the [Calibration Catalog](https://in.xfel.eu/calibration/). |
| 5 | +This is used for most imaging detectors in use at European XFEL to record |
| 6 | +and track datasets called calibration constants derived from characterization |
| 7 | +measurements and used for data corrections. |
5 | 8 |
|
6 | 9 | To find constants by conditions for a particular point in time, create a |
7 | 10 | condition object for the relevant detector type and use |
@@ -69,6 +72,20 @@ agipd_cd.display_markdown_table() |
69 | 72 |
|
70 | 73 | ::: extra.calibration.ShimadzuHPVX2Conditions |
71 | 74 |
|
| 75 | +## Detectors and modules |
| 76 | + |
| 77 | +Calibration data is associated with physical detector units (PDUs), with an actual |
| 78 | +detector consisting of one or more of these PDUs then generally called modules. PDUs |
| 79 | +can freely move between detectors of the same type in a process called mapping, and |
| 80 | +take their calibration data alongside with them. |
| 81 | + |
| 82 | +This is automatically taken into account when using the `CalibrationData` APIs described |
| 83 | +here, but you can also obtain the detector metadata and mapping information explicitly: |
| 84 | + |
| 85 | +::: extra.calibration.DetectorData |
| 86 | + |
| 87 | +::: extra.calibration.DetectorModule |
| 88 | + |
72 | 89 | ## Bad pixel values |
73 | 90 |
|
74 | 91 | The calibration pipeline produces masks along with corrected data, in keys |
|
0 commit comments