Skip to content
Snippets Groups Projects
Verified Commit 2d7d03e4 authored by Tamas Gal's avatar Tamas Gal :speech_balloon:
Browse files

Add submodule and some updates

parent 166b3f96
No related branches found
No related tags found
No related merge requests found
[submodule "km3net-dataformat"]
path = km3net-dataformat
url = ../../common/km3net-dataformat.git
Subproject commit e555efba2211945c5db3b4bb6a2b5de6ba5e2aa7
......@@ -241,7 +241,7 @@ for every PMT and comment lines at the beginning of the file to store meta data.
\datafield[int or float]{x, y, z}{The position of the PMT with reference to the UTM coordinate with x (y) defining the relative distance in Easting (Northing) in metres.}
\datafield[int or float]{dx, dy, dz}{The direction where the PMT is pointing at.}
\datafield[int or float]{t0}{The calibration time offset which has to be added to the detected hit times.}
\datafield[int]{PMT_STATUS}{MSB: default = 0 means PMT OK for analysis; 1 = PMT NOT OK for analysis; other status flags to be updated}
\datafield[int]{PMT_STATUS}{MSB: default = 0 means PMT OK for analysis; 1 = PMT NOT OK for analysis; other status flags to be updated. The status bit definitions can be found here (updated regularly): \url{https://git.km3net.de/common/km3net-dataformat/-/blob/master/definitions/module_status.csv}}
\end{fieldspecs}
\alertinfo{Within each DOM section, the PMTs are listed according to an ascending order of their DAQ channel ID, starting at 0.}
......@@ -306,7 +306,7 @@ for defining non-optical modules (like base modules).
\datafield[int or float]{p_x, p_y, p_z}{The position of the PMT with reference to the UTM coordinate with x (y) defining the relative distance in Easting (Northing) in metres.}
\datafield[int or float]{dx, dy, dz}{The direction where the PMT is pointing at.}
\datafield[int or float]{p_t0}{The calibration time offset which has to be added to the detected hit times.}
\datafield[int]{PMT_STATUS}{MSB: default = 0 means PMT OK for analysis; 1 = PMT NOT OK for analysis; other status flags to be updated}
\datafield[int]{PMT_STATUS}{MSB: default = 0 means PMT OK for analysis; 1 = PMT NOT OK for analysis; other status flags to be updated. The status bit definitions can be found here (updated regularly): \url{https://git.km3net.de/common/km3net-dataformat/-/blob/master/definitions/module_status.csv}}
\end{fieldspecs}
\alertinfo{Within each module section, the PMTs are listed according to an ascending order of their DAQ channel ID, starting at 0.}
......@@ -372,7 +372,7 @@ The main additions in the fifth version of the DETX format is the COMPONENTESTAT
\datafield[int or float]{p_x, p_y, p_z}{The position of the PMT with reference to the UTM coordinate with x (y) defining the relative distance in Easting (Northing) in metres.}
\datafield[int or float]{dx, dy, dz}{The direction where the PMT is pointing at.}
\datafield[int or float]{p_t0}{The calibration time offset which has to be added to the detected hit times.}
\datafield[int]{PMT_STATUS}{MSB: default = 0 means PMT OK for analysis; 1 = PMT NOT OK for analysis; other status flags to be updated}
\datafield[int]{PMT_STATUS}{MSB: default = 0 means PMT OK for analysis; 1 = PMT NOT OK for analysis; other status flags to be updated. The status bit definitions can be found here (updated regularly): \url{https://git.km3net.de/common/km3net-dataformat/-/blob/master/definitions/module_status.csv}}
\end{fieldspecs}
\alertinfo{Within each module section, the PMTs are listed according to an ascending order of their DAQ channel ID, starting at 0.}
......
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