Skip to content

Testing SuperCDMS Soudan File

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

We will assume that you have gone through the "General Running BatRoot and BatNoise" tutorial and we will build off of that experience. Although, there is one change to the environment variables we should specify first.

As mentioned previously, there are two environment variables only used for processing Soudan Data called BATROOT_GPIBFILES and BATROOT_AUXFILES. The BATROOT_GPIBFILES environment variable points to the GPIB log file, which should be placed in the gpib directory.

You should make sure the BATROOT_GPIBFILES and BATROOT_AUXFILES envoriment variables in your .bashrc file are set to:

  export BATROOT_AUXFILES=$HOME/aux
  export BATROOT_GPIBFILES=$HOME/gpib

Accessing Data

The SuperCDMS Soudan file we will attempt to access has the series number: 01140716_0726. This input file was 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: /supercdms-data/CDMS/Soudan/R134/Raw/01140716_0726/01140716_0726_F0001.gz. Again we are interested in the first data dump, F0001. This is because BatNoise needs to run on a dump that was taken with full readout, for Soudan data only the first and last dump is taken with full readout. You can use the following commands to check for the file and to copy the file onto your raw directory:

rclone ls OSN:/supercdms-data/CDMS/Soudan/R134/Raw/01140716_0726/01140716_0726_F0001.gz

rclone copy OSN:/supercdms-data/CDMS/Soudan/R134/Raw/01140716_0726/01140716_0726_F0001.gz $HOME/raw

And now you have successfully downloaded the input file to your raw directory (if you would like to process more data there are dumps 2-24 also available at this file path).

We must access one more file before we are completely done with this section. To run Soudan data there is a GPIB log file that is read during processing. We must acquire this log file from the OSN. The GPIB log file can be copied from the path: /supercdms-data/CDMS/Soudan/R134/01140716_0726/gpib_states_changed.log You can use the following commands to check for the file and to copy the file onto the gpib directory:

rclone ls OSN:/supercdms-data/CDMS/Soudan/R134/01140716_0726/gpib_states_changed.log

rclone copy OSN:/supercdms-data/CDMS/Soudan/R134/01140716_0726/gpib_states_changed.log $HOME/gpib

And now we are ready to start processing data!

BatNoise

We will begin the processing chain by first performing BatNoise. For this specific Soudan series we will use the following processing file: processingSoudanData.R134Grid.z14lite.bg_cfand configuration file: configSoudanData.R134.z14lite. As mentioned before it is important to specify the processing and configuration files we will use.

We want to make sure that we are not reading from the Database. In order to achieve this we will use the following processing file instead:

processingSoudanDataTutorialVersion.R134Grid.z14lite.bg_cf

The first difference between these two processing files is that, under the READ AUXILLIARY FILES subsection, the reading from database variable has been set to zero. 

  READ    DATABASE          =     0

The second difference between the two files is that the number of detectors that will be used has been reduced to decrease run time of BatNoise and BatRoot. 

  $ BatNoise -s 01140716_0726 -d 1 --max_events 200 --processing_config processingSoudanDataTutorialVersion.R134Grid.z14lite.bg_cf --analysis_config configSoudanData.R134.z14lite

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

As it is running, it will print some diagnostics and what it has found to the console session. Once it has been completed, you should be able to use ls inside our chosen output directory, noise/.

  (base) [user noise]$ ls -alh
  ...
  -rw-r----- 1 user user  69M Jul 6 17:24 Prodv5-3_Filter_01140716_0726.root

As the program output lets us know, it has written out the cut distributions to Prodv5-3_Filter_01140716_0726.root.

BatRoot

BatRoot is the next step in the toolchain.

It will use the same analysis and processing files that BatNoise did. Let's run it!

  $ BatRoot -s 01140716_0726 -d 1 --max_events 200 --processing_config processingSoudanDataTutorialVersion.R134Grid.z14lite.bg_cf --analysis_config configSoudanData.R134.z14lite

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

Note, seeing the following message repeatedly is expected and BatRoot should not be interrupted until the job finishes:

PulseFilter::FiltFilt WARNING!  sampleRate/freqCut exceeds limit where boundary conditions for filtering can be kept manageable.  
Filtered pulse may suffer from artifacts of filtering algorithm

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

  (base) [user rq]$ ls -alh
  ...
  -rw-r----- 1 user user 22M Jul 6 17:30 Prodv5-3_01140716_0726_F0001.root

Now, we can see a Prodv5-3_01140716_0726_F0001.root file has been written out.