Instructions on how to run SDAQ
Troubleshooting a SDAQ run
For debugging you should monitor the messages of the front
Look up in the IOC mapping
which port the frontend processor is connected to.
Telnet to t-d0-mch2, user name
Type "connect PP" where PP
stands for the port number. Note that only one session at a time is allowed
Don't forget to log out (hit "Ctrl-]"
and then enter the command "quit") after the
In your frontend window you should see how the process starts.
An output file /online/data/smt/cal_0xnn_rrrrrr.dat
where nn denotes the geographical sector and rrrrrrr is the run number
(or a number close by) is written. It contains the calibration result
for each channel and an error summary.
In case the process ends with status "error"
without having procecessed a single event:
Type in the frontend command "<
Hit the "init SDAQ" button for
Hit the "begin SDAQ" button
for your crate.
The SDAQ procedure should restart.
In case a process hangs:
A DAQ status change (somebody starts/stops a run) can be
Try a sclinit.
Try a reinit VME.
If nothing helps, reboot the PPC. Start
/online/config/ctl/d0.ioc. Select SMT
and reboot for the PPC belonging to the crate
that hangs. A consequence of a reboot is that the PPC looses its connection
to the Data Merger. The Sdaq Supervisor will wait forever for the data
from this crate. No data will be written to the database. A manual transfer
from the output file is still possible.
A Stop from the taker will abort
the run. A reboot of the PPC involved in the run might be necessary.
Process a SDAQ run to produce new thresholds
A single crate contains about 50,000 channels. Everything
described in this chapter is slow.
Select a crate that was part of the SDAQ run. Select the
Select Process Pedestal Run.
A window with a selection of pedestal runs for this crate will pop up.
Select the run to be processed.
All pedestal data belonging to the selected run are processed,
also channel of other crates. A summary for every SVX chip containing the
number of channels below threshold, the number of noisy channels,
the average pedestal, the average sigma and the calculated new threshold
(pedestal + 3 * sigma) is calculated. Strips below threshold and noisy
strips are flagged.
Selecting Print Stat all Runs
writes the processing summary of the last calibration runs to /online/data/smt/runstat_0xnn.dat
where nn denotes the geographical sector of the crate.
To install new thresholds use Select
Each HDI in a crate is represented by the last SVX. For
this SVX the thresholds of the last SDAQ runs are displayed. The maximum
number of runs is 10. The presently valid threshold is printed next to
the SVX identifier. The run corresponding to this threshold is highlited
in light blue.
To update all thresholds of this crate to one SDAQ run select
the run button on top of the list. Thresholds with value 0 are omitted.
To update all SVX in one HDI to a new threshold select the corresponding
threshold button. A selected button will be highlighted light green.
To select different runs for the SVX within one HDI select
SVX Thresholds from the HDI menu of the details
GUI for one crate.
To manipulate the threshold value for a SVX select the SVX
GUI item from the same menu.
Visualization of SDAQ runs with ROOT
Due to licences this part has to be done on d0mino.
Start the program /projects/823d/com/fox/peddir/bin/IRIX6-KCC_3_4/rootFromRun
with the SDAQ run number as argument. A file SmtSdaqRun_rrrrrr.root
Copy all files *.C and *.h
out of /projects/823d/com/fox/sdaqAna
to your working directory.
Start root (after setup
Follow the load sequence described in doit.C:
Load the root file with the command SDAQ
s(rrrrrrr) where rrrrrr stands for the run number.
To display a particular HDI: s.analyzeHdi("F2-1-3")
To display the number of dead/noisy channels: s.createDeadHisto()
To compare 2 SDAQ runs issue the following commands:
reference r(mmmmmm) where mmmmmm
stands for the reference run number