DATE Run Control | DATE Information Logging | Configuring the DAQ | Online Filter | Monitoring | Auxiliary Software | Central Data Recording | FAQ to Lars
In case of hanging DAQ (more than 30 seconds without response) abort with
cleanDateIt will close the run control and all DATE processes. Start again with
Some more information about the system can be found in the DAQ tutorial 2006 (PDF).
You may browse the DATE logfiles online through a
via WWW. On the COMPASS run control machine you can also use
To see run statistics of recorded files use the DATE
Information on runs is logged via the electronic logbook.
You may monitor the status of online machines via netsaint, a network monitoring tool.
eventDump @pccoeb01: eventDump /scratch/cdr01001-00559.dat eventDump /shift/ccf011d/data01/objsrvvy/cdr/cdr01001-00559.dat eventDump pccoeb01:/scratch/cdr01001-00559.dat
Configuring the DAQ
COMPASS uses an online filter running in pipeline with the
eventbuilder processes on the eventbuilder computers to reject
bad events and reduce the rate to be recorded to disk.
Its state can be set through the run control:
DATE offers the possibility to sample data online using a monitoring
library. This library exists in two versions, a C library and a C++
library based on ROOT.
Sample codes with decoding facilities of COMPASS F1-TDC data (from
CATCH CMC or Hotlink) exist:
The DATASOURCE can either be a file name
as an example for online monitoring from an eventbuilder. Please use
different eventbuilders (05 to 08) as well to spread the load.
Author: Lars Schmitt
Last update: August 23 2000
Author: Fritz-Herbert Heinsius
eventDump @pccoeb01:where pccoeb01 is the name of the machine providing the monitoring data, e.g. an eventbuilder. Don't forget the ":" at the end.
eventDump /shift/ccf011d/data01/objsrvvy/cdr/cdr01001-00559.datIf the file is not in a directory tree as defined for the SHIFT service you have to specify
The TCS server controlling the TCS system sends a TCP/IP multicast
to announce some spill related information during data taking. A
client program to listen to these
multicasts is provided. The output of this program is the data line
transmitted by the multicasts, a string of 60 bytes length.
For each sub DAQ
prompt> spillclient 1f 004 1f 001 1f 0c9 00 000 00 000 00 000 00 000 00 000 1800 1f 004 1f 001 1f 0c9 00 000 00 000 00 000 00 000 00 000 800 1f 005 1f 002 1f 0ca 00 000 00 000 00 000 00 000 00 000 1800 1f 005 1f 002 1f 0ca 00 000 00 000 00 000 00 000 00 000 800 00 000 1f 003 1f 0cb 00 000 00 000 00 000 00 000 00 000 1800 00 000 1f 003 1f 0cb 00 000 00 000 00 000 00 000 00 000 800There is as well a simple program waiting for offspill included.
Frequently asked questions to Lars
Frequently asked questions on the operation of the COMPASS DAQ
will be posted here (with answers, of course). If you have a question
or are missing a piece of information which should appear here write
to Lars Schmitt.