Skip to content
Snippets Groups Projects
Commit 9cd74c7f authored by Karim Ahmed's avatar Karim Ahmed Committed by Karim Ahmed
Browse files

gh2 notebook description

parent 973a6137
No related branches found
No related tags found
1 merge request!820[Documentation] Introduce mkdocs and add new documentation pages
......@@ -155,12 +155,31 @@ Values shown in plots are saved in h5 files.
### Gotthard2 Offline Correction
Offline Correction for Gothard2 Detector
Offline Correction for Gotthard2 Detector.
This notebook is able to correct 25um and 50um GH2 detectors using the same correction steps:
- Convert 12bit raw data into 10bit, offset subtraction, then multiply with gain constant.
| Correction | constants | boolean to enable/disable |
|------------|-------------|-----------------------------|
| 12bit to 10bit | `LUTGotthard2` | |
| Offset | `OffsetGotthard2`|`offset_correction`|
| Relative gain | `RelativeGainGotthard2` + `BadPixelsFFGotthard2` |`gain_correction`|
Beside the corrected data, a mask is stored using the badpixels constant of the same parameter conditions and time.
- `BadPixelsDarkGotthard2`
- `BadPixelsFFGotthard2`, if relative gain correction is requested.
The correction is done per sequence file. If all selected sequence files have no images to correct the notebook will fail.
The same result would be reached in case the needed dark calibration constants were not retrieved for all modules and `offset_correction` is True.
In case one of the gain constants were not retrieved `gain_correction` is switched to False and gain correction is disabled.
### Gotthard2 Dark Image Characterization
The following is a processing for offset, noise, and Badpixels maps using dark images taken with Gotthard2 detector. All constants are evaluated per strip, per pulse, and per memory cell. The maps are calculated for each gain stage that is acquired in 3 separate runs.
The following is a processing for the dark constants (`Offset`, `Noise`, and `BadPixelsDark`) maps using dark images taken with Gotthard2 detector (GH2 50um or 25um).
All constants are evaluated per strip, per pulse, and per memory cell. The maps are calculated for each gain stage that is acquired in 3 separate runs.
The three maps (calibration constants) can be injected to the database and stored locally.
The three maps can be injected to the database and/or stored locally.
## JUNGFRAU
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment