Background monitoring

[martin-rdz]

Quickly noting down the in-person discussion.

At some point we should implement a monitoring of the background in the pretrigger and the far range.
One suggestion was to have the functions as part of picassopy, but to have a separate script, that does the analysis and stores the results (maybe to a database or netcdf).

We decided for now to not prioritize that task very high.

[Ronny-TROPOS]

Yes, it turned out that sometimes the detectors behave strange. This could be observed by comparing the background over time and have a comparision of all channels, to see that the daily variation can be seen in all channels.
2nd point, the backgrounds of Pretrigger and Farrange might differ, due to, e.g., afterpulsing from strong signals. Here, we would need a plot like (FarBG-NearBG)/NearBG from an ?half/hourly average?. This should really be a zero line with no bias. A few % deviation are already crucial. Since the effect can be caused by afterpulsing, a Plot of the MaxCountRates should also be inline to analyze issues. I believe this could all go under the Monitoring Tab in at polly.de. Not sure if long or short term is a good way to plot. Maybe monthly?
As for priority: its something needed for the early detection of broken detectors and for data quality monitoring, allthough it is not required by CARs, yet.