Detector Status - Revision history

Dtreffenstaedt: /* Possible detector status */

2021-07-30T11:19:44Z

Possible detector status

Dtreffenstaedt: /* Reliability */

2021-04-11T07:34:08Z

Reliability

Dtreffenstaedt: /* Possible reasons */

2021-04-11T07:32:30Z

Possible reasons

Dtreffenstaedt: /* Real-Time Analysis */

2021-04-11T07:08:47Z

Real-Time Analysis

Dtreffenstaedt: /* Reliability */

2021-04-01T15:15:45Z

Reliability

Dtreffenstaedt: Created page with "= Real-Time Analysis = The incoming data from all detectors is analysed in real-time before being written to the database. This analysis consists of the calculation of coinci..."

2021-04-01T15:15:23Z

Created page with "= Real-Time Analysis = The incoming data from all detectors is analysed in real-time before being written to the database. This analysis consists of the calculation of coinci..."

New page

= Real-Time Analysis =
The incoming data from all detectors is analysed in real-time before being written to the database.

This analysis consists of the calculation of coincidences between all possible detector pairs. Additionally each individual and total coincidence detection rate is determined.

In order to ensure the validity of the data at all times, each detectors reliability is judged.

=== Reliability ===

Determining factors include e.g. quality of GNSS signal, effective [https://en.wikipedia.org/wiki/Dilution_of_precision_(navigation) DOP] or the steadieness of detection rate.

For a detailed view, you can check out the relevant code at [https://github.com/MuonPi/muondetector-cluster/blob/929145e792dc84eb80b28bf62f8d37236fb681cf/src/detector.cpp#L139-L147 our github].

Additionally to the standard requirements, individual events can cause an instant unreliability mark due to exceptionally bad time resolution or no valid GNSS fix. Those events are automatically rejected.

Compare [https://github.com/MuonPi/muondetector-cluster/blob/929145e792dc84eb80b28bf62f8d37236fb681cf/src/detector.cpp#L107-L111] to see the detailed requirements.

=== Possible detector status ===

{| class="wikitable"
|-
! Status !! Data is processed !! Description
|-
| offline || no || The detector is not connected or experiences network problems
|-
| online || no || The detector is recently connected
|-
| reliable || yes || The detector is connected and all parameters are deemed good
|-
| unreliable || no || The detector is connected but experiences network problems or has sub-optimal runtime parameters
|}

@@ Line 47: / Line 47: @@
 | rate_unstable || The standard deviation of the event rate was too large compared to the mean
 |-
-| missed_log_interval || The detector missed a log interval (for unreliable. Three intervals for offline)
+| missed_log_interval || The detector missed a log interval (One for unreliable, Three intervals for offline)
 |}

@@ Line 21: / Line 21: @@
 |-
 ! Status !! Data is processed !! Description
 |-
 | offline || no || The detector is not connected or experiences network problems

@@ Line 10: / Line 10: @@
 Determining factors include e.g. quality of GNSS signal, effective [https://en.wikipedia.org/wiki/Dilution_of_precision_(navigation) DOP] or the steadieness of detection rate.
-For a detailed view, you can check out the relevant code at [https://github.com/MuonPi/muondetector-cluster/blob/929145e792dc84eb80b28bf62f8d37236fb681cf/src/detector.cpp#L139-L147 our github].
+For a detailed view, you can check out the relevant code at [https://github.com/MuonPi/muondetector-cluster/blob/3797637b2c475c91296d52ffc5f9debdd865369f/src/analysis/detectorstation.cpp#L148-L166 our github].
 Additionally to the standard requirements, individual events can cause an instant unreliability mark due to exceptionally bad time resolution or no valid GNSS fix. Those events are automatically rejected.
-Compare [https://github.com/MuonPi/muondetector-cluster/blob/929145e792dc84eb80b28bf62f8d37236fb681cf/src/detector.cpp#L107-L111 the code] to see the detailed requirements.
+Compare [https://github.com/MuonPi/muondetector-cluster/blob/3797637b2c475c91296d52ffc5f9debdd865369f/src/analysis/detectorstation.cpp#L116-L120 the code] to see the detailed requirements.
 === Possible detector status ===

@@ Line 29: / Line 29: @@
 |-
 | unreliable || no || The detector is connected but experiences network problems or has sub-optimal runtime parameters
 |}