CODA Summary

OPS Network

Mott DAQ Host:

         name      =>  opsmdaq0
         ip        =>   129.57.236.240

Mott DAQ IOC:

        name       =>  iocmdaq1
        ip         =>   129.57.236.241

Other network information:

        name       =>  opsnet
        number     =>  129.57.236.0
        mask       =>  255.255.252.0
        cidr       =>  22
        hexmask    =>  0Xfffffc00
        broadcast  =>  129.57.239.255
        gateway    =>  129.57.236.1
        domain     =>  acc.jlab.org
        vlan       =>  5
        comment    =>  OPS

Mott DAQ iocmdaq1

There are two ways to access the Mott DAQ ioc:

From an accelerator machine: telnet iocmdaq1
From an accelerator machine: ioc_concole iocmdaq1. Here you need to enter a password to this cannot be done with the idaq account.

The startup file: idaq@opsmdaq0:/cs/op/iocs/iocmdaq1/startup

The CODA boot file: idaq@opsmdaq0:/opt/coda/boot/mott_roc1.boot

CODA Files

CODA crl files are in: idaq@opsmdaq0: /opt/idaq/crl
Scalers.crl
Mott_Sample.crl
Mott_SemiInt.crl
PEPPo_Int.crl
To compile: makelist Mott_Sample.crl ppc

CODA scripts files are in: idaq@opsmdaq0: /opt/idaq/scripts

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
PEPPo_Int	INT FADC, S1, S2	PEPPo_Int_%d.dat	nT_Settle

Backup Data Files to SILO

Cron scripts are installed on the idaq account on opsmdaq0 to back up data and delete it from /data and /data1:

/opt/idaq/cron/cron_opsmdaq0

Do not attempted to copy, delete, move, or rename files. Never !

The scripts assume that data appears in /data*/DIR where DIR = "annihilation" or "compton" or "mott" Files must have the keywords "PEPPo" or "Scalers" or at least "dat". This avoids writing scratch files like root output. Do not start putting data in some new place or with new names. It won't be backed up to MSS if you do that.

The data are deleted from local disks if they have been written in duplicate with correct byte count to the MSS tape silo. The data stay on disk for an amount of time that is related to the amount of disk space is available. If lots of disk available, the data stay forever. If not much disk, the data are deleted aggressively.

 The data is copied to: /mss/accel/peppo/raw

The copying of data was disabled on January 3rd, 2014.
 - To list: crontab -l
 - To remove: crontab -r
 - Check again: crontab -l
 - To load: crontab cron_opsmdaq0 (in /opt/idaq/cron)

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

 CH1 - E LEFT     Range - 0.5 V  DAC_offset = 3300
 CH2 - E RIGHT          - 0.5 V  DAC_offset = 3300
 CH3 - E UP             - 0.5 V  DAC_offset = 3300
 CH4 - E DOWN           - 0.5 V  DAC_offset = 3300
 CH5 - dE LEFT          - 0.5 V  DAC_offset = 3300
 CH6 - dE RIGHT         - 0.5 V  DAC_offset = 3300
 CH7 - dE UP            - 0.5 V  DAC_offset = 3300
 CH8 - dE DOWN          - 0.5 V  DAC_offset = 3300
 CH9 - BFM              - 1.0 V  DAC_offset = 3300
 CH10 - Empty           - 1.0 V  DAC_offset = 3300
 CH11 - Mott Trigger    - 1.0 V  DAC_offset = 3300
 CH12 - Empty           - 1.0 V  DAC_offset = 3300
 CH13 - Delayed Hel     - 1.0 V  DAC_offset = 3300
 CH14 - T_Settle        - 1.0 V  DAC_offset = 3300
 CH15 - Pat Sync        - 1.0 V  DAC_offset = 3300
 CH16 - Pair Sync       - 1.0 V  DAC_offset = 3300

Reference: JLab Module Manuals [1]

Reference: Media:FADC250_V2_ADC_FPGA_V5.pdf

Reference: Media:Programming_FADCV2_3.pdf

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

Reference: Media:PEPPo-FADC.pdf

Reference: Media:PEPPpoHelicityFirmware.pdf Media:PEPPpoHelicityFirmware.docx

All the relevant files are at: M:\FE\PEPPo. These files also copied to opsmdaq0 at: /opt/idaq/HaiDong_PEPPo.

TDC

 CAEN v775
 const int V775_ADD    = 0x1190

Reference: Media:V775_manual.pdf

S1 and S2

 S1: SIS3801 at addr 0xa40000 
 S2: SIS3801 at addr 0xa50000

Reference: Media:SIS3801_manual.pdf

TID

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

Reference: Media:TImaster.pdf

cefdmp/xcefdmp

The event dump utility (cefdmp) can display, in a readable ASCII format, events from the data files.

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)

cedit and dbedit

Use cedit and/or dbedit to modify CODA database.

Issues and FAQ

RunNumber: if the run number in msql is different from the one in CODA cool database, coda doesn't work. Open dbedit => localhost => sessions and change the RunNumber to match the one in CODA cool database.