Calibration Data to Offline Analysis
Kay Graf
Vidyo, 4th of May 2017
General Scheme
Detector
- Acoustic system
- Orientation system
Offline Analysis/Reco
(could extent to quasionline)
Position Calibration
- Positions
- Orientation
- Combined fit (with line
shape) → future
- Other calibrations
Database
Comp&Soft WG — K. Graf — March 2017
2
What we currently have
● Position/orientation in detx –
derived from standard detector geometry
●
hard coded values
● no orientation at all
● T0 in detx – derived from in situ measurements + dark room (see time
calibration procedure)
● Detx format:
●
●
●
Human readable
Large overhead (4MB for a buidling block)– redundant information on
DOM geometry)
only contains position, orientation and T0
● Other calibration parameters (especially from K40 analysis)
●
As ASCII files
Comp&Soft WG — K. Graf — March 2017
3
What we need
● Possibility to stream all calibration data from the database to analysis
codes
●
Stream should be efficient (small, only necessary information)
● Unique identification of the “best” available calibration on an event basis
NB: ”best” could change in time
● possibility to use an intermediate data format for caching
● For now: position/orientation data, however: scheme should be
extendable also to other calibration data, e.g. from K40 analysis
Comp&Soft WG — K. Graf — March 2017
4
Proposal
● Store data in a dedicated DB table
1.
2.
3.
4.
5.
6.
7.
8.
Time info (UTC time)
Detector ID
Calibration tag (define e.g. online, offline v1, v2, v3 calibration sets)
(RUN)
DOM ID
Position (x,y,z)
Orientation (yaw, pitch, roll)
... Repeat 1-7 for all DOMs in detector or: repeat 5-7 for all DOMs in
detector?
● Detx provides the general setting (detector setup; DOM ID to position in
detector; DOM geometry; T0s)
● Position/orientation is streamed as ntuple
● ⇒ result: detector object in the individual analysis/reco code
Comp&Soft WG — K. Graf — March 2017
5