km3db issueshttps://git.km3net.de/km3py/km3db/-/issues2024-01-26T09:16:49Zhttps://git.km3net.de/km3py/km3db/-/issues/17Change request for online purposes2024-01-26T09:16:49ZaveutroChange request for online purposesHi, I'm opening this issue in order to ask for a change in tools.py. Previous versions of km3db were reading only calibration information from the run table (i.e. PMT time offset, DOM position, DOM rotation), lacking other eventually exi...Hi, I'm opening this issue in order to ask for a change in tools.py. Previous versions of km3db were reading only calibration information from the run table (i.e. PMT time offset, DOM position, DOM rotation), lacking other eventually existing calibrations. However, since for online purposes we are interested on introducing also other calibrations (e.g., PMT status via scal string, that affect the quality of reconstructions as has been show during the last [astro ftf meeting](https://indico.cern.ch/event/1292550/contributions/5707019/attachments/2775315/4836481/F2F_december2023_Mastrodicasa.pdf)), we asked Tamas to adapt km3db such that the detector file returned by km3db automatically includes all calibration sets by extracting these information differently from before, i.e. from the Calibration Manager. To accomodate our request, new versions of km3db now use API v2 to determine the calibration sets (instead of using the run table). This is valid starting from km3db 0.13.0; see [here](https://git.km3net.de/km3py/km3db/-/commit/104dd650803414fc108e62ff7fb4f363e97cda62#72f04f5ffa1c62877691ec5dd4519ee6271d87cd_422_510) for the changes. However, calibration infos are accessible from the Calibration Manager only at the end of each run, which is not suitable in the context of an online framework, while in the run table pcal, rcal, tcal are available in real-time. For this reason, the best solution we have at the moment for the online system is to retrieve pcal, rcal, tcal from the run table and acal, ccal, scal from the previous run via the Calibration Manager. To this extent, we have created a modified version of tools.py which uses both the tools in km3db v0.12.0 and v0.13.x.
It would be useful, for this purpose, to have an updated version of km3db from which both the Calibration Manager and Run Table can be accessed, depending on the purpose, with two different functions.https://git.km3net.de/km3py/km3db/-/issues/5JSON schema validator for uploading data2022-05-02T07:46:09ZTamas Galtgal@km3net.deJSON schema validator for uploading dataWhen uploading data to the DB, the scheme for the JSON file can be obtained from the DB which can be used to validate the data before the actual upload process.
ping @cbozza @mdejong @kgrafWhen uploading data to the DB, the scheme for the JSON file can be obtained from the DB which can be used to validate the data before the actual upload process.
ping @cbozza @mdejong @kgrafTamas Galtgal@km3net.deTamas Galtgal@km3net.dehttps://git.km3net.de/km3py/km3db/-/issues/1Creating an upload and test suite for Calibration/Database interactions2020-11-12T13:07:06ZKay GrafCreating an upload and test suite for Calibration/Database interactionsWith reference to the calibration WG issue https://git.km3net.de/working_groups/calibration/-/issues/10 , an upload an test suite for calibration/database interactions should be created.
Requirements are
- [ ] upload XML and JSON calibr...With reference to the calibration WG issue https://git.km3net.de/working_groups/calibration/-/issues/10 , an upload an test suite for calibration/database interactions should be created.
Requirements are
- [ ] upload XML and JSON calibration (test) to DB
- [ ] tests on XML and JSON files for consistency with data format
- [ ] test upload (download results and compare to original)
- [ ] availability as small-scale project to be available from km3pipe and Jpp environments.Valentin PestelValentin Pestel