pacman This is the GUI interface for the CAEN DT5740D / DT5730B digitizers, or a specially programmed Teensy 4.1 using FreeRTOS.

It is developed for the SBC collaboration and the SBC-Queens SiPM tester.

Compiling

Windows

If compiling this for windows make sure you have downloaded and installed:

• MSYS2 (with build-essentials, clang-tools-extra PREFERRED). Click MSYS2 for more instructions.
• Git for windows (to git clone the dependencies if not included)
• CMake (version 3.11 or higher)
• (optional) VULKAN-SDK (if using the vulkan backend)

Then clone the repository

git clone https://github.com/SBC-Collaboration/SBC-SIPM-Testing-Software

You do not need to install any of these dependencies directly, I just want to have a space to thanks all of these awesome people. Without them, this project would not have been possible!

• gl3w
• glfw
• imgui
• implot
• json
• serial
• spglog
• readerwriterqueue
• concurrentqueue
• tomlcplusplus

The dependencies can be installed (after calling git clone or downloading the rep) by calling:

git submodule init git submodule update

The compilation steps are (WINDOWS):

mkdir build cd build cmake ../ -G "MinGW Makefiles" mingw32-make -j8

LINUX

Have a working C++ compiler with C++17 features, cmake, and git. Then clone the repository:

git clone https://github.com/SBC-Collaboration/SBC-SIPM-Testing-Software

The dependencies can be installed by calling:

git submodule init git submodule update

The compilation steps are (Linux): mkdir build cd build cmake ../ make -j8

You will probably have some errors in the cmake running, most of them can be solved by googling the library that is required!

CAEN Libraries

If the intention is to use this software to run the CAEN digitizer functionalities. It is required to install CAEN libraries. For both linux and windows, this can be done by following the CAENVME, CAENComm and CAENDigitizer libraries installation instruction.

If they are installed in an unusual location, it is possible to add -DCAEN_DIR=dir\to\CAEN while runnin gcmake.

Developer instructions

If the intention is to develop the code:

1. Install Sublime text
2. Install the package manager in Sublime text.
3. Then, follow this link to install SublimeLinter, SublimeLinter-cpplint, and LSP.
4. Follow the Windows/Linux compiling instructions
5. WINDOWS ONLY: to make step 2 work and after installing MSYS2, it is required to install clang-tidy and clangd. For that, click this link.
6. During cmake add the option -DCMAKE_EXPORT_COMPILE_COMMANDS=ON
7. With all of this, Sublime Text should turn into a full IDE with code completion and error checking!

Common Problems:

LINUX:

• If you install CAEN libraries the way it tell you to install them, cmake wont find them. My proposed solution is to imitate the Windows installation structure: first, create a folder named CAEN. Then, copy all the files extracted directly from the tar file (for example CAENComm-1.5.0). Then, rename: CAENComm-X.X.X to CAENComm, CAENDigitizer-X.X.X to CAENDigitizer, CAENVMELib-X.X.X to CAENVME. Finally, install the libs by running the install_64 that are found in each lib. If you do not have this problem, ignore it.

WINDOWS:

• If during linking the compiler says "ld.exe: cannot find -lCAENVME", go where the library CAENVME was installed and rename all the files "CAENVMElib" to "CAENVME"

ALL:

• Do not forget to do "git submodule init" and "git submodule update" if it is possible not to find some dependencies.

Details about the binary save format (SBC preferred data format)

Here is the fields and their corresponding dimensions of the binary data that are being saved. The data can be read by the DataHandling/ReadBinary.py script in the SBC-Analysis repository. First here are the dimension definitions:

• n_triggers: number of triggers accepted by the digitizer
• n_channels: number of channels enabled for acquisition
• record_length: the number of samples digitized in a given trigger for a channel

These are the fields of saved data and their corresponding dimensions. Fields with n_triggers* mean the value is constant for all triggers. Fields with n_channels* mean the value is common within a group.

• sample_rate (n_triggers*): ADC clock frequency for the digitizer. For DT5740D it is 62.5MHz. Actual triggering clock is at the same frequency as the sampling clock.
• en_chs (n_triggers*, n_channels): A list of the channels enabled for acquisition. This is the name of the channels for which the data are saved. Only channels in enabled groups will be saved.
• trg_mask (n_triggers*): This is a 32bit mask of all of the channels enabled for generating self-triggers. The least significant bit corresponds to channel 0, and so forth. If a bit is set to 1, then the channel participates in self-triggering. If 0, then it does not. Only channels in enabled groups are saved. It is possible that channels enabled for acquisition and for triggering are different.
• thresholds (n_triggers*, n_channels*): A 12-bit value representing the threshold for self-triggering. The unit is in LSB, where 1LSB = InputDynamicRange/2^12bit and the input dynamic range is 2V for DT5740D. The value is common within each group.
• dc_offsets (n_triggers*, n_channels*): A 16-bit value in 16-bit DAC LSB unit. The 0-64k range in DAC corresponds to the ADC range, as DAC is slightly larger than ADC. This value is common within a group.
• dc_corrections (n_triggers*, n_channels): A 8-bit correction to each channel in addition to the offset above. The value is in 12-bit LSB, which is roughly the same as the threshold. Since thresholds cannot be changed individually for each channel, change this setting to make sure each channel has the same trigger efficiency.
• dc_range (n_triggers*, n_channels*): Input dynamic range. Equals to 2V for DT5740D.
• trg_source (n_triggers): Indicates the trigger source causing the event acquisiton:
  • Bit[10] = Software Trigger
  • Bit[9] = External Trigger
  • Bits[3:0] = Trigger requests from the groups.
• time_stamp (n_triggers): Time stamps for each trigger generated by the CAEN digitizer. This value is reset at start of acquisition, and increments every 1/2 ADC clock cycle (125MHz for DT5740D). It is a 32bit number, with the lower 31 bits being the time counter, and the 32nd bit is the roll-over flag.
• sipm_traces (n_triggers, n_channels, record_length): Waveforms digitized at 62.5MHz. Each waveform has the same record length, and only data from channels enabled for acquisition are saved.