Skip to content

Testing CUTE File

In this tutorial, we will be showing you how to properly run BatNoise and BatRoot for a CUTE file. This specific file was used for testing purposes in the summer of 2021.

Again for this tutorial, we will assume that you have gone through the "General Running BatRoot and BatNoise" tutorial and we will build off of that experience.

Accessing Data

The CUTE file we will be processing in this tutorial has the series number: 23200913_221311. Input files for this series were stored on the Open Storage Network (OSN) for testing purposes.

We will be using rclone to download the raw data files. To setup and configure rclone refer to Downloading Data.

Once you have configured rclone, you can copy the input file from the path: /CDMSBats_testing/Cute/Raw/23200913_221311_F0001.mid.gz. We are interested in the first data dump, although you can access the following data dumps from the path given: F0001, F0127, F0348, F0508, F0700. You can use the following commands to check if the file is in the OSN and copy the file into your raw directory:

rclone ls OSN:/supercdms-data/CDMSBats_testing/Cute/Raw/23200913_221311_F0001.mid.gz

rclone copy OSN:/supercdms-data/CDMSBats_testing/Cute/Raw/23200913_221311_F0001.mid.gz $HOME/raw

BatNoise

Let's now start processing the raw data by running BatNoise. The corresponding processing file for series 23200913_221311 is: processingCUTEData.R15_ProdApr162021 and the configuration file is: configCUTEData.R15. As mentioned before it is important to specify the processing and configuration files we will use.

You can use the following command to run BatNoise for the acquired CUTE data while utilizing the proper processing and configuration files. Run it!

  $ BatNoise -s 23200913_221311 -d 1 --max_events 5000  --processing_config processingCUTEData.R15_ProdApr162021 --analysis_config configCUTEData.R15

For an explanation of arguments, run BatNoise --help.

After you run this command you will find that it will print some diagnostics and what it has found to the console session. Once finished, you should be able to use ls inside our chosen output directory, noise/.

  (base) [user noise]$ ls -alh
  ...
  -rw-r----- 1 user user  25M Jul 8 10:50 Test_Filter_23200913_221311.root

The output lets us know that it has written the cut distributions to Test_Filter_23200913_221311.root.

BatRoot

The next step in the toolchain is running the BatRoot program. It will use the same analysis and processing files that BatNoise did. Let's run it!

  $ BatRoot -s 23200913_221311 -d 1 --max_events 5000  --processing_config processingCUTEData.R15_ProdApr162021 --analysis_config configCUTEData.R15

For an explanation of arguments, run BatRoot --help.

After it's done, let's check our rq directory.

  (base) [user rq]$ ls -alh
  ...
  -rw-r----- 1 user user 355K Jul 8 11:00 Test_23200913_221311_F0001.root

Now, we can see a Test_23200913_221311_F0001.root file has been written out.

Processing CUTE files for Previous Versions of CDMSBats

The configuration file for this particular set of CUTE Data (as well as other CUTE data sets) used arguments that were new for the most recent commit of CDMSBats. Usually, this would not cause too many issues; however, in this most recent commit, there were changes in particular parameter names and parameter definitions.

You can change the configuration file if you wish to do processing for past versions of CDMSBats (past meaning preceding and including v5.9.8). The changes you should make are in the baseline calculation of configCUTEData.R15. You must switch:

  # Phonon Baseline Min/Max (in micro seconds)
  PARAMETER_DOUBLE    P_BASELINE_MIN_FROM_START_USEC DETECTOR 1-24  =    10
  PARAMETER_DOUBLE    P_BASELINE_MAX_TO_TRIG_USEC   DETECTOR 1-24  =    500
  PARAMETER_DOUBLE    P_POSTBASELINE_TO_END_USEC   DETECTOR 1-24  =    400

  # Charge Baseline Min/Max (in micro seconds)`
  PARAMETER_DOUBLE    Q_BASELINE_MIN_FROM_START_USEC DETECTOR 1-24  =    10
  PARAMETER_DOUBLE    Q_BASELINE_MAX_TO_TRIG_USEC   DETECTOR 1-24  =    500
  PARAMETER_DOUBLE    Q_POSTBASELINE_TO_END_USEC   DETECTOR 1-24  =    200

to:

  # Phonon Baseline Min/Max (in micro seconds)
  PARAMETER_INTEGER    P_BASELINE_MIN   DETECTOR 1-24  =    10
  PARAMETER_INTEGER    P_BASELINE_MAX   DETECTOR 1-24  =    500
  PARAMETER_INTEGER    P_POSTBASELINE   DETECTOR 1-24  =    400

  # Charge Baseline Min/Max (in micro seconds)
  PARAMETER_INTEGER    Q_BASELINE_MIN   DETECTOR 1-24  =    10
  PARAMETER_INTEGER    Q_BASELINE_MAX   DETECTOR 1-24  =    500
  PARAMETER_INTEGER    Q_POSTBASELINE   DETECTOR 1-24  =    200

Afterwards, BatNoise and BatRoot should run seamlessly for this CUTE dataset for past versions of CDMSBats.