-
Type: Task
-
Status: Done (View Workflow)
-
Priority: Normal
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Sprint:EngRun17May_June
Please make a plan with priority for the data acquisition in May-Jun 2024 run (run17).
The calibration data we took in the previous two runs are:
https://sumire.pbworks.com/w/page/156330582/Calibration%20Data%20from%20Run%2015
https://sumire.pbworks.com/w/page/156874332/Calibration%20Data%20from%20Run%2016
The calibration data we regularly take
- masterBiases
- masterDarkes
- Bootstrap?
- Check detectorMap using IIS (see also
PIPE2D-1426)
- Check detectorMap using IIS (see also
- Arc/Trace to make detectorMap
-
- 5 frames but 3 frames are acceptable if we don't have time
- w/ brn, 10s Ar, 45s Xe, 10s Ne, 70s Kr, 45s HgCd, 45s Trace
w/ bmn, 10s Ar, 45s Xe, 10s Ne, 45s Kr, 45s Trace
The data for fiberProfiles (if weather permits)
- Take at least one ditheredFlat for mod4 group1, having mod16 trace.
- Using mod16 trace, check if extraction is reasonable
- Using ditheredFlat, make one profile and compare?
- If extraction is not good, take the other three groups.