CODA Summary

Summary of CODA Configurations

Name	Readout	Output	Trigger
Scalers	Scaler S1 (helicity gated), S2 (un-gated)	Scalers_%d.dat	Delayed nT_Settle
Mott_Sample	Mott FADC, S1, S2, TDC	Mott_Sample_%d.dat	Mott Detector
Mott_SemiInt	Mott FADC, S1, S2, TDC	Mott_SemiInt_%d.dat	Mott Detector
FADC_Int	INT FADC, S1, S2	Inj_Int_%d.dat	nT_Settle

Mott FADC

 const FADC_ADDR       = 0x680000  # 12 bit fADC MOTT - Slot 7
 const FADCMODE        = 1 (Mott_Sample)
 const FADCMODE        = 3 (Mott_SemiInt)
 const FADCSLOT_Mott   = 7
 const TRSPLIT         = 0xeb13   # Address of fADC Signal Distribution Module

INT FADC

 const FADC_ADDR       = 0xed0000  # 12 bit fADC Int - Slot 10         
 const FADCMODE        = 3 (Int_Int, special)
 const FADCSLOT_PEPPo3 = 10
 const TRSPLIT         = 0xea13   # Address of fADC Signal Distribution Module

TDC

 CAEN v775
 const int V775_ADD    = 0x1190

S1

 SIS3801 at addr 0xa40000 

S2

 SIS3801 at addr 0xa50000

TID

 A24 Address for TID Module (0x100000 for VME Slot 2)
 const TRIG_ADDR       = 0x100000

cefdmp/xcefdmp

The event dump utility (cefdmp) can display, in a readable ASCII format, events from the following sources:

• event files
• readout controllers (fragments)
• event builder output
• analysis program output

Syntax

% cefdmp [filename] [-o object] [-t tag] [-u uniquetag] [-s start] [-e end] [-d dictionary] [-x] 
% xcefdmp [same] 

Options

o specify the source object name (CODA component name) 
t select specified tag number or name (full path in event structure) 
u select specified unique tag, independent of location in the event 
s number of first record in file to dump 
e number of last record in file to dump 
d specify dictionary for obtaining tag names and titles 
x hex dump of integers (default is decimal) 

Description

The cefdmp utility can dump selected portions of particular events from either a file on disk or from special processes which comprise the data acquisition pipeline.

For file dumps, the filename is specified as an argument to cefdmp. One event is dumped, and then the utility waits for a carriage return before dumping the next event. If -s nnn is specified, (nnn-1) records are skipped before the dump starts. If -e mmm is specified, the dump continues without prompting until record mmm. Output is to stan- dard output, and so in this case can be piped to other programs or redirected to disk:

% cefdmp myfile -e 20 > dump20.lis 

Events are tree structured, and every node and leaf on the tree contains an identifier or tag. Any node or leaf may be specified either by a path (set of tags) starting at the root of the tree, or by a tag which only occurs at a single point on the tree. The -u option is used to specify a unique tag. (Using unique tags when defining event structures makes it easier to use this utility, but is not required.)

Tags are stored in the event as integers, but may be referenced by names stored in a tag dictionary (see Appendix E). The name of this dictionary file may be specified with the -d option, or defaulted to the value of the environment variable EVTAGS, or the file evTags in the directory pointed to by the environment variable RCDATABASE. The fol- lowing command dumps the drift chamber portion of physics events (events whose outermost identifier is not physics will be skipped):

% cefdmp myfile -t physics.drift 

Events may alternatively read from processes in the data acquisition pipeline. Currently, the readout controller (ROC), event builder (EB), and the analysis program (ANA) all will support this feature, allowing spying on the data stream at the crate level, prior to analysis, and after analysis. The data source is selected using the -o option followed by the name of the object as found in the run control database file. Assuming that the environment variable RCDATABASE is defined, the following example extracts physics events after analysis:

% cefdmp -o myana -t physics

Examples

For a guide on how to interpret the raw data see the following pages:

• Fastbus Raw Data Format

File:Xcefdmpgui.jpg