CombinedRunning

This page replaces the old Sr1Setup page, which is largely obsolete.

BuildingSctRodDaq is some tips for updating SctRodDaq

Partitions:

• SCT standalone running: /daqsoft/combined/partitions/part_SCT_withCorboTDCQDCSegment.xml
• Combined SCT/TRT running: /daqsoft/combined/partitions/part_Combined.xml

To start with SCT ONLY (no TRT):

• on srsctdaq1, login as 'sr1daq'
• cd ~
• source setup.SCT.sh
• ./start

To start with SCT+TRT:

• on srsctdaq1, login as 'sr1daq'
• cd ~
• source setup.sh
• ./start

ENSURE that the BOOKKEEPING is running (starts automatically by start, otherwise start by 'runBookKeeper &')

AFTER configuration but BEFORE start:

• Hard Reset All modules, then WAIT for the DDC script to finish
• Reconfigure modules
• set to cosmics mode (expanded, any hit mode, with thresholds set to the trim target) (SctGUI menu) Options -> Run Options -> 'Set Cosmics Mode'
• Start, and check we are taking events

Other things that might need doing between runs:

• kill old pt_main on idonline

If you reboot an SBC, you must:

[sr1daq@ctatsct01 sr1daq]$ su
Password:
[root@ctatsct01 sr1daq]# cp /home/sctroddq/examplefstab /etc/fstab
cp: overwrite `/etc/fstab'? y
[root@ctatsct01 sr1daq]# mount -a

The data is written to /data/combined

There are several ways to see what is in the data file:

• Dump the file in octal format by doing

 od -t x4 daq_SCTEB__0001009_file01.writing | less

• Use the tdaq event analysis tools:

StorageReader $filename
dump-eformat-in-data filename -o outputfile -f event_number

(above utility in tdaq-common-01-01-00)

• Use example executable from TDAQ:

 
SimpleTBA $filename

• Use the SctRodDaq tool in MiniUtils:

eventStreamDecoder $filename 

More practical for long runs:

eventStreamDecoder -t $filename | grep err

More on eventStreamDecoder

Here is a link for on-ROD histogramming: onRODhist

Multiple FILARs

more /proc/filar lists status of all FILARs in ROS

filar_slink_dst -o channel number (to run utility for channel number)

where

Card0  1  2  3  4 (physical middle)
Card1  5  6  7  8 (physical down)
Card2  9 10 11 12 (physical up)

Software map in oks database:

Card0  0  1  2  3
Card1  4  5  6  7
Card2  8  9 10 11

These are physically connected to BOCs in the following rod crate slots:

Card0 10 11 14 15 (physical middle)
Card1  6  7  8  9 (physical down)
Card2 16 17 18 20 (phsical top)

All FILAR Input Channels (0..11) should belong to the same FilarReadout Module

To run a test program, over Slink channel 2 (say):
on ROS, filar_slink_dst -o 2 -p
on BOC, SlinkTest -s11

Timing Scans

From beanshell:

.x expandedModeFormat.java
.x anyHitMode.java
.x physicsModeTimingScanCoarse.java

root file is created in /tmp on AnalysisService machine

root
new TFile("filename");
new TBrowser()

Combined TRT/SCT event Display

Instructions on running Stanislav's tool (from Mike):

• ssh sr1daq@pctrtonl01
• source ~trtdaq/setup_files/setup.0400.sh
• cd ~trtdaq/proj/working/bin
• ./trtviewer DAQ --config Sct.conf
• To run on a file name <file>, instead do:
• ./trtviewer --config Sct.conf <file>