OVERVIEW
FACILITY
DETECTORS
DAQ
EXPERIMENTS
PUBLICATIONS
COLLABORATIONS
PEOPLE
LINKS

Scheduled Experiments l Special Events l Contacts


The NNSA DAQ-System

The present research requires us to cope with high count rates, to utilize a large number of high-density electronic modules, and to accomodate a number of experimental conditions and detector configurations. The NNSA group at TUNL is using Spectrodaq/SpecTCL data acquisition and analysis programs for use in readout of the TUNL segmented HPGe clover array and HPGe planar detectors. We are using the scripted readout package, which is easily configurable with CAEN 700 series digitizer. This package simplifies the software setup procedures for mid-to-high density detector configurations.

NRF

We extended the program's functionality by adding a new class of operations called CalibratedParameters that facilitates online analysis of HPGe detector gamma-ray spectra. Below we give an overview of the TUNL/NNSA Spectrodaq/SpecTCL acquisition system. There are essentially four parts of the acquisition and analysis system.

  • The system hardware (Computer, interface, and digitizers)
  • The data acquisition software (Spectrodaq), which interfaces
  • with the hardware (ADC, TDC, QDC and scaler modules) to read-out the data, and to create the data buffers,
  • The scaler display program
  • The data analysis package (SpecTCL), which reads the data buffers, and permits the user to constrain and display the data
  • Data acquisition hardware

    The data acquisition hardware/trigger setup is comprised of the computer (Dual XEON LINUX machine), a PCI-to-VME interface module (SBS bit-3 620), an I/O module (CAEN 262), a specialized latching gate module to create the system BUSY, and the VME digitizers (ADC's, TDC's, etc.). The trigger system functions such that when an event mastergate arrives in the system, if the system is not already BUSY a mastergate.live logic signal is created and two latching logic gates are set that each have a specific purpose. The first trigger latch gate is sent, via the I/O module (IN 0), to strobe the computer so that the readout of VME modules will be initiated. When the computer acknowledges a signal is returned on I/O (SHP 2) which releases the trigger latch. The time required for the computer to acknowledge the initiation of an event, known as the latency time, is typically on the order of 3 μs. The second latching gate that is set with a mastergate.live is the system BUSY latch. The system BUSY inhibits any subsequent mastergate.live's, and it remains latched throughout the processes of acquisition, conversion and readout of the VME modules. The time required for this phase depends on the temporal width of the ADC gates, the number of VME modules that are read in the event, and the number of channels that contain data. We typically observe times of approx 45 μs while taking data with the TUNL HPGe Clover detectors. When the computer has finished reading out an event, the system resets and then sends a signal on I/O (SHP 1) that releases the BUSY and permits the system to start processing new events.

    Software

  • NSCL Documentation web pages      
  • Report documentation errors            
  • NSCL DAQ Wiki      
  • NSCL DAQ defect reporting/tracking      
  • NSCL DAQ/SpecTcl enhancement requests      
  • Known Defect summary    
  • Software Distribution      
  •        
  • All things TCL                             
  • A brief summary of procedures followed at TUNL is given below.

    Data Acquisition - Spectrodaq

    Setup of the customized Readout part of Spectrodaq requires modification of a single file "~/config/hardware.tcl". This file configures the data acquisition software to read a specific set of VME modules when a Mastergate.live event triggers the system. Within the hardware.tcl file, it is advantageous to enable only ADC channels that will have signals connected; this prevents needless readout of channels that may have some spurious noise signal while the ADC gate is open. It is also necessary to specify ADC threshold values above the pedestals of the ADC channels. The CAEN 785 32-channel ADC's have a maximum input of 4 Volts, and our observations lead us to specify a pedestal of ~150 mV.

    for {set i 0} {\$i $<$ 32} \{incr i} (lappend enables 1)

    set thresholds 15

    for {set i 0\} {\$i $<$ 32} {incr i} { lappend thrlist $thresholds }

    Next in the hardware.tcl file is the setup of individual digitizer modules. Below is the description to setup an ADC and TDC for a typical NNSA detector configuration. On the first line, there is a description which specifies the module type, i.e. CAEN V785, and the electronic ``base'' address occupied by the module, i.e. 0xe6000000. Other setup commands are somewhat intuitive for setting the pedestal thresholds and enabled channels. An additional setup parameter waitloops specifies a relative time period that the system will wait for the module to convert data before moving on to the next module in the readout order.

    Parameter names, which are descriptive of the signals plugged into the digitizer channel, are given in the module setup and are automatically propagated throughout the rest of the scripted software. In our typical setup we specify parameters for each quadrant of the clover detectors, [1Q# and 2Q#], for two planar HPGe detectors [3EHPGE 4EHPGE] and for the energy and PSD signal from a neutron detector [5MON_E 5MON_PSD]. ADC channels that are unused must still have a name associated with the input. Setup for the TDC is similarly straight forward, and details can be found in the CAEN module user's manuals.

    module adc1 caenv785 slot 5 geo false base [expr 0xe6000000] adc1 config threshold $thrlist multievent false enable enables catch "adc1 config waitloops 10" adc1 config parameters {1Q1 1Q2 1Q3 1Q4 2Q1 2Q2 2Q3 2Q4 5MON_E 5MON_PSD blank01 blank02 blank03 blank04 3EHPGE 4EHPGE blank05 blank06 blank07 blank08 blank09 blank10 blank11 blank12 blank13 blank14 blank15 blank16 blank17 blank18 blank19 blank20

    noindent for {set i 0} {$i $<$ 32} {incr i} {lappend tnables 1}

    module tdc caenv775 slot 9 geo false base [expr 0xe3000000] tdc config threshold $thrlist multievent false enable $tnables catch "tdc config waitloops 10" catch "tdc config commonstart true keepoverflow false range 630" tdc config parameters {1Q1T 1Q2T 1Q3T 1Q4T 2TQ1 2TQ2 2TQ3 2TQ4 1SHLDT 2SHLDT 3SHLDT 4SHLDT TPKOFF 3HPGET 4HPGET 5MONT t1p17 t1p18 t1p19 t1p20 t1p21 t1p22 t1p23 t1p24 t1p25 t1p26 t1p27 t1p28 t1p29 t1p30 t1p31 t1p32

    Last is a command that determines the module readout order; in our case the TDC is readout first because it is the first to finish the analog-to-digital conversion process.

    set ModuleOrder {tdc adc1}

    Scaler Setup

    Scalar buffers are written to the event files on a fixable time interval, and a separate scaler application window can be opened while acquiring data. The scripted version of Spectrodaq supports use of the 32 channel CAEN V830 module. In the present configuration of the NNSA electronics, a series of coincidence logic modules permits the counting of scalars for individual detectors, with a counting of raw triggers from each detector as well as an accounting of the number of mastergate's and mastergate.live's for each detector. This ``over'' accounting of scaler channels is helpful in tracking the dead-times for the overall system (1- {$mg.live over mg$}), as well as the dead-times for each detector.

    scaler counters1 caenv830 base [expr 0xee000000] geo false header false trigger 1 counters config slot 11 packetize false autoreset false manualclear true counters config fpclearmeb false id 0x101 vmetrigger true wide true counters config header false counters config parameters {1_Q1 1_Q2 1_Q3 1_Q4 2_Q1 2_Q2 2_Q3 2_Q4 1SHIELD 2SHIELD 3SHIELD 4SHIELD 20HZ 3HPGE 4HPGE 5MON 0RAW 0MG 0MGLIVE BCI 1DRAW 1DMG 2DRAW 2DMG 1DMG.LIVE 2DMG.L 3DMG 4DMG 3DMG.L 4DMG.L 5MG 5MG.L }

    set ScalerOrder {counters1}

    Data Analysis - SpecTCL

    Lastly is the analysis software package SpecTCL. Using SpecTCL, it is possible to generate 1- and 2-Dimensional histograms, and one can generate pseudo parameters by manipulating raw ADC parameters. Simple gates on 1-D histograms or complex contour gates on 2-D histograms can be defined and used to sort data based in inclusion (or exclusion) in the gates, i.e. beam-pickoff time-of-flight requirements. New parameters and histograms can be created at anytime using the following commands.

    parameter parameterName parameter IDNumber bit-size spectrum spectrumName specType(i.e. 1=1-D) parameterName { displayedbit-size}

    A specific example summarizes creation of parameters and histograms for a neutron-monitor liquid-scintillator detector. More complex manipulations are possible, but the user is encouraged to consult the online user's manual for details.

    parameter MON_Anode parameter MON_PSD 2 12 parameter MON_beam_pkoff_time 3 12 spectrum MON_Anode 1 MON_Anode 12 spectrum MON_PSD 1 MON_PSD 12 spectrum MON_beam_pkoff_time 1 MON_beam_pkoff_time 12 spectrum MON_PSD vs. Anode 2 {MON_PSD MON_Anode} {9 9} spectrum MON_PSD vs. beam_pkoff_time 2 {MON_PSD MON_beam_pkoff_time} {9 9}

    The TUNL group has consulted with Ron Fox to create a new class of pseudo parameter, called Calibratedparameters. To use the calibrated parameters function, one creates a fit data set which gives the correlation between a raw parameter and know calibration values. A fit function is then created that corresponds to a linear least-squares fit to the data set. A CalibratedParameter can then be created, which references the new calibrated parameter name & number, the raw parameter name, the fit function and the units for the histogram. A spectrum can then be created.

    fit -create linear 1Q1_CALIB fit -add 1Q1_CALIB {1579.36 1173.228} {1777.94 1332.492} fit -perform 1Q1_CALIB calibparam} -create 1Q1_calibrated 101 1Q1 1Q1_CALIB keV spectrum 1Q1_calibrated 1 1Q1_calibrated 12 The new calibrated parameters are computed using the functional form,

    X'=m . (X+ran(iseed)) +b

    to eliminate spurious structures that would appear using other proceedures.

    Summary

    The NNSA group is using the TUNL HPGe segmented clover detectors to evaluate the Spectrodaq/SpecTCL data acquisition system. We have had two successful data taking weeks, running with event rates of 3kHz and deadtimes of around 15-20%. We consulted with Ron Fox to increase the functionality of SpecTCL by creating a new feature, CalibratedParameters, that permits the display of energy calibrated spectra. We may pursue further feasible developments that would incorporate new 14-bit ADC's from CAEN and Mesytec, and developments that would efficiently accommodate higher event rates.