Open tomkooij opened 4 years ago
It's always better to catch errors and log them, but since the Raspberry Pi at s9 will be replaced with a W10 PC it is very unlikely that we will encounter this problem again. Also, this problem hasn't occurred during the past few years, I think?
@davidfokkema : This problem (at other stations) has occured 4 times the past few weeks according to sentry.io.
However, we have encountered it quite frequently when adding new stations.
But I'll just fix the sapphire side and leave the publicdb jobs alone as long as these errors do not occur frequently. (If it ain't broken don't fix it)
I thought I opened this over at hisparc/publicdb ... oops. This is an publicdb.histogramjobs issue.
I'll create a new issue #192 to describe the problem in sapphire.
On Oct 30 (updatehistograms of oct 29 data) there was some error in sapphire while reconstructing events. (Due to s9 uploading an invalid config, it was fixed automatically when s9 uploaded a new config)
However this crashes/stops the entire
updatehistograms
job. Should we wrap these calls intry: except:
to prevent this? (Or solve this somewhere else??)The
IndexError
(list index out of range) was at: https://github.com/HiSPARC/sapphire/blob/master/sapphire/analysis/core_reconstruction.py#L69 Because s9 uploaded a config without slave data while the station has 4 detectors this errored.Log:
(ignore the sentry errors, it's the
IndexError
that caused this) also at sentry.io