1) Temperature check (high priority)
- Check the temperature on this page (local POCC) or on this one (CERN Server)
- Select the working TTCE side (A or B) and the M-crate working side (A or B), according to JMDC.
- Check the following conditions:
- The temperature of the Tracker (Sensor A and Sensor C) must be lower than 32°C.
- The temperature difference between the pump (Pt02_P) and the Accumulator-Set Point (Pt01_P) is alwasy more than 3°C
Example of TTCE B-side and M-Crate B-side on, tracker temperatures <32°C,
DeltaT >3°C between Set-point and Accumulator
- WARNING: if the web-interface displays no temperatures and monitoring data check the AMI scanner daemons:
ssh ami@pcposk0
cd AMI
CheckAmiDaemon.sh
- If the scanning programs are setted on the wrong HK directory you must:
StartScan.sh ssh <Blocks_dir> <starting_block>
(the script kills the old scanners and starts new ones)
Example of TTCE B-side and M-Crate B-side on, tracker temperatures <32°C,
DeltaT >3°C between Set-point and Accumulator
2) Check the Tracker Monitoring Tools Status
- Usual Tracker WorkStation is PCPOC08
- Login as user: tracker
- Go to directory
cd TrackerUser/Monitor
- Check if the data processing daemons are running using the command
./CheckMonitoringDaemons.sh
- Check that the directory used by the decoding daemon is the right one (ask DAQ shift for the active interface)
- If the directory is the right one you can kill the runnig daemons with the command: <\br>
./KillMonitoringDaemons.sh
- If the daemons are not running, you can launch them with the command:
./LaunchMonitoringDaemons.sh <Blocks_dir> <starting_block>
(example: ./LaunchMonitoringDaemons.sh /Data/BLOCKS/HRDL-A/ 0160/001)
3) Check Calibration
- Launch the Last Calibration Monitor with the command:
MonitorUI Output/LastCalDB.root
- Compare the calibration with the reference one (see below)
- When a new calibration is available press the "Update" button to get the new data
- Reference Calibration Summary:
4) Fast Data Quality Check
- Launch the block summary check:
WatchLastErrReport.sh
- If the block is a not-empty data block (Blocks!=0) please check:
- Low number of bad clusters
- Approximate Track Reconstruction Efficiency ~ 50%
- Average Tracker Event SIze > 300 words, < 5000 words (approx 1000 words in normal conditions, approx 2500 words for TAS runs)
- Average Number of Hits per Track: ~ 6
- Presence of TDR Boards Errors (the large amount of T018 errors is known)
5) Data Quality Check
- Launch the Last Run Monitor with the command:
MonitorUI Output/LastRunHmon.root