-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change of formats to new DAQ Model version #18
Comments
Well...it seems that this only affects to runs from 20191206 because I could process runs from 20191209 without problems. So false alarm. I will keep this open in case this is useful for anyone else. |
It turns out that only run1720 is affected by this format change. |
I open this issue again. After discussing it with Isidro, we found out that run1720 was the only one with UCTS timestamps after the first ~1000 events without them. Whenever there is no UCTS data available (i.e. all other runs except for run1720) there is no problem. However, if UCTS data is present, the current data model is not valid, so it must be updated to the new CDTS version: DAQ37827 |
Hi @morcuended, |
Hi @FrancaCassol, remember that I already made the change for NectarCAM: |
Solved in #19 |
While trying to process run1720, I got these errors:
This seems to be due to the recent upgrade of DAQ data model (extraction of CDTS data). Now it should be changed according to this structure:
The text was updated successfully, but these errors were encountered: