The August 2001 test run was taken parasitically with the CLAS G6 experiment. We used a totally independant data acquisition system which wrote events in the CODA format. This is a binary format which is described in the appendix of a coda manual available on the JLab CUE at /site/coda/1.4/coda.ps . Software has already been written to parse these data files so, saving any personal challenges you may have set for yourself, you should not need to look in this manual.
The run list and file locations can be found here.
The data was taken using a protable fastbus crate with the following modules and slot assignments:
1881M ADC slot 7
1877 TDC slot 6 (Y-coordinates)
1877 TDC slot 5 (X-coordinates and trigger logic)
The slot assignments are important since the analysis code cannot decipher them from the data itself. Also, there's a good chance the ADC slot may be changed to slot 8 in an attempt to decrease electronic noise.
The analysis code is stored in the PrimEx CVS repository on the JLab CUE (stop groaning). Here are instructions for obtaining the code from the repository. If you have trouble accessing the CVS repository, you can get a tarball here.
A number of directories exist in programs/aug_01. Here is a description of the important packages:
This directory contains code to make a library called libprimex.a. The routines in this library are ones generally used by more than one program. These include the routines to open and read coda formatted files. To make the library:
This program creates hbook files with histograms and Ntuples from the coda formatted files. It was modified to allow events to be read online via an ET system. This may cause linking problems. If you get link errors related to routines starting with "et_" then remove the "-let" argument from the LIBS definition at the top of the Makefile.
This program is the PrimEx single event viewer. It uses tcl/tk so you should have that installed before trying to compile it. It was also made to connect with the ET system so you may experience similar link problems as described above.
Once you have a coda2hist executable, run it with a "-h" argument to see the list of options.
primexdaq1_daq:coda2hist>coda2hist -h
Usage:
coda2hist [options] -Ssession | filename
options:
-Ssession read events from ET session "session"
-oOutputfile set output filename (default name is chosen)
based on input filename)
-v verbose (print LOTS of debugging information for
every event
-Gname Map pawc to global section name
-h print this usage statement
-Nnum only process "num" events
If no output file is specified, it will create one with the same name as the inputfile, but with a .hbook suffix. If you specify a -Gname option, the pawc common will be mapped to the global section name so you can begin looking at histograms with paw as they are being filled.
NOTE: when using the -G option, ntuples are filled in a ring buffer so only the last N events will be available. This also means the file Ntuple will not contain all events.
> coda2hist primcal_parasitic000100.dat
This software was basically developed as needed on specific accounts on specific machines. No attempt has been made to ensure it compiles and works everwhere so be patient. If you have any trouble, contact me and I'll be happy to help.