GUI and Detector Operation - Revision history

Hgz: /* Finding the right threshold */

2022-01-01T17:28:38Z

Finding the right threshold

Hgz: /* Finding the right threshold */

2022-01-01T17:20:52Z

Finding the right threshold

Hgz: /* Finding the right threshold */

2022-01-01T17:14:11Z

Finding the right threshold

Hgz: /* Finding the right threshold */

2022-01-01T17:07:33Z

Finding the right threshold

Lnies: /* Finding the right threshold */

2022-01-01T16:24:56Z

Finding the right threshold

Lnies: Created page with "This article will explain to best operate the detector and how to use the GUI DISCLAIMER: Tutorial written based on [https://github.com/MuonPi/muondetector/releases/tag/v2.0...."

2022-01-01T15:38:19Z

Created page with "This article will explain to best operate the detector and how to use the GUI DISCLAIMER: Tutorial written based on [https://github.com/MuonPi/muondetector/releases/tag/v2.0...."

New page

This article will explain to best operate the detector and how to use the GUI

DISCLAIMER: Tutorial written based on [https://github.com/MuonPi/muondetector/releases/tag/v2.0.2 GUI version 2.0.2]
__TOC__

= Detector Operation =

== Finding the right threshold ==
There are several ways to find the right detector threshold. In general, one aims to minimize the amount of electronic noise while not sacrificing real detector counts.
Method 1
Using an oscilloscope
Method 2
Using the energy processor

Method 3
One way to accomplish this, and without having to use additional equipment, is a threshold scan using the GUI. Here, the software is automatically setting different threshold levels and measuring the number of counts measured per time interval. Thus, by creating a graph showing count rate versus threshold, one can make an informed decision on how to choose the right threshold level.
<gallery mode="packed-hover">
Telegram Cookies.png|Step 0: Varify and accept the Telegram cookies
Telegram Step 1.png|Step 1: Log in with Telegram
Telegram Step 2.png|Step 2: Enter credentials
Telegram Step 3.png|Step 3: Accept verification
Telegram Step 4.png|Step 4: Start chatting
Telegram Step 5.png|Step 5: Verify authentification
</gallery>

@@ Line 8: / Line 8: @@
 == Finding the right threshold ==
 There are several ways to find the right detector threshold. In general, one aims to minimize the amount of electronic noise while not sacrificing real detector counts.
-* Method 0: The choice of threshold should always be guided by the expected integrated muon flux per m2 and per second in the detector. For our large detector (25cm x 12.5 cm), this is roughly 3.5Hz. For our small hexagonal detector, this is roughly 1Hz. For a more in-depth choice of threshold, follow the other methods.
+* Method 0: The choice of threshold should always be guided by the expected integrated muon flux per m<sup>2</sup> and second in the detector. For our large detector (25cm x 12.5 cm), this is roughly 3.5Hz. For our small hexagonal detector, this is roughly 1Hz. For a more in-depth choice of threshold, follow the other methods.
 * Method 1: Using an oscilloscope (details to be added)
 * Method 2: Using the energy processor (details to be added)

@@ Line 17: / Line 17: @@
 # When the scan is done, right-click on the y-axis of the plot and select "Log Y" to show the plot in log scale.
 # Choosing the right threshold value. The result in your GUI should look similar to Screenshot 1 in the gallery below. A steep drop in count rate for very low thresholds turns into a less steep drop. At this point, the electronic background is effectively cut and only real detector signals are measured. To avoid measuring a great number of dark counts (signal-like events produced by the photosensors) one wants to set the threshold well above the point where the slope changes. In this example, we chose a value 20mV above that point. In screenshot 2 the data is fitted with an exponential decay function with three decay constants for reference. The data was taken with a large (25cm x 12.5 cm) detector.
-# The threshold that was found across the previous steps should be persisted to the non-volatile memory of the DAC device. This is achieved by clicking the "store DAC values" button on the left side bar of the GUI. In this way, the new threshold is automatically set after restart or after a power cycle.
+# The threshold that was found across the previous steps should be persisted to the non-volatile memory of the DAC device. This is achieved by clicking the "Store DAC settings" button on the left side bar of the GUI. In this way, the new threshold is automatically set after restart or after a power cycle.
 <gallery mode="packed-hover">

@@ Line 17: / Line 17: @@
 # When the scan is done, right-click on the y-axis of the plot and select "Log Y" to show the plot in log scale.
 # Choosing the right threshold value. The result in your GUI should look similar to Screenshot 1 in the gallery below. A steep drop in count rate for very low thresholds turns into a less steep drop. At this point, the electronic background is effectively cut and only real detector signals are measured. To avoid measuring a great number of dark counts (signal-like events produced by the photosensors) one wants to set the threshold well above the point where the slope changes. In this example, we chose a value 20mV above that point. In screenshot 2 the data is fitted with an exponential decay function with three decay constants for reference. The data was taken with a large (25cm x 12.5 cm) detector.
 <gallery mode="packed-hover">
 Threshold Scan Log.PNG|Screenshot 1: GUI Scan page with scan settings
 Threshold Scan Log fit.png|Screenshot 2: Fit of the plotted data. An exponential decay function with three decay constants was assumed.
 </gallery>

@@ Line 12: / Line 12: @@
 * Method 2: Using the energy processor (details to be added)
 * Method 3: Another way to accomplish this, and without having to use additional equipment, is a threshold scan using the GUI. Here, the software is automatically setting different threshold levels and measuring the number of counts measured per time interval. Thus, by creating a graph showing count rate versus threshold, one can make an informed decision on how to choose the right threshold level.
-# Step: Open GUI and navigate to the "Scans" page.
+# Open GUI and navigate to the "Scans" page.
-# Step: Set "UBXRATE" as observable and "THR1" (if using channel one of the board) or "THR2" (if using channel two). Select meaningful values for the scan range: test by hand (using the Threshold slider) to find a high count rate (blue LED on HAT board permanently on) and where the counts practically disappear (blue LED permanently off). Those to values can be set as "Scan range from" and "To". To get good statistics, choose 0.0025 as step size and 20s as "Meas. time interval".
+# Set "UBXRATE" as observable and "THR1" (if using channel one of the board) or "THR2" (if using channel two). Select meaningful values for the scan range: test by hand (using the Threshold slider) to find a high count rate (blue LED on HAT board permanently on) and where the counts practically disappear (blue LED permanently off). Those to values can be set as "Scan range from" and "To". To get good statistics, choose 0.0025 as step size and 20s as "Meas. time interval".
-# Step: Press "Start scan". The scan might take several minutes, depending on your effective scan range. The progress is displayed on the bottom of the page.
+# Press "Start scan". The scan might take several minutes, depending on your effective scan range. The progress is displayed on the bottom of the page.
-# Step: When the scan is done, right-click on the y-axis of the plot and select "Log Y" to show the plot in log scale.
+# When the scan is done, right-click on the y-axis of the plot and select "Log Y" to show the plot in log scale.
-# Step: Choosing the right threshold value. The result in your GUI should look similar to Screenshot 1 in the gallery below. A steep drop in count rate for very low thresholds turns into a less steep drop. At this point, the electronic background is effectively cut and only real detector signals are measured. To avoid measuring a great number of dark counts (signal-like events produced by the photosensors) one wants to set the threshold well above the point where the slope changes. In this example, we chose a value 20mV above that point. In screenshot 2 the data is fitted with an exponential decay function with three decay constants for reference. The data was taken with a large (25cm x 12.5 cm) detector.
+# Choosing the right threshold value. The result in your GUI should look similar to Screenshot 1 in the gallery below. A steep drop in count rate for very low thresholds turns into a less steep drop. At this point, the electronic background is effectively cut and only real detector signals are measured. To avoid measuring a great number of dark counts (signal-like events produced by the photosensors) one wants to set the threshold well above the point where the slope changes. In this example, we chose a value 20mV above that point. In screenshot 2 the data is fitted with an exponential decay function with three decay constants for reference. The data was taken with a large (25cm x 12.5 cm) detector.
 <gallery mode="packed-hover">
 Threshold Scan Log.PNG|Screenshot 1: GUI Scan page with scan settings
 Threshold Scan Log fit.png|Screenshot 2: Fit of the plotted data. An exponential decay function with three decay constants was assumed.
 </gallery>