Difference between revisions of "General Calibration Procedures"

Revision as of 17:18, 8 August 2018

General Reference

Preparations

Check-out

Several data types stored in the data stream rely on shared-memory and other ancilliary processes to be running. So it's good to check these. Make sure that BOR records are being written early on in the raw data, that board configurations are being written into each event, and that EPICS events are showing up in the data stream
- Note that the first two events in a run are generally control events: Prestart and Go. Then usually the BOR event should show up
Make sure parameters are being reasonably propagated into the RCDB

Calibrations

Look at occupancy plots to find dead channels
Check firmware if there's new firmware.
- So far, this has only really been tested for the fADC250's
- hd_root -PPLUGINS=lowlevel_online -PLOWLEVEL:CHECKEMULATION=1 data.evio
  - This prints out cases where the emulated pulses don't match the measured pulses
- hd_dump -PSKIP_TO_EVENT=XXXXXX -PEVIO:VERBOSE=10 -DDf250PulseData data.evio
  - If you see bad pulses, you can look at the pulse data by running a command like this
Start the timing calibrations
- Start with the RF Calibration - for normal running, it's usually enough to just calibrate the fine timing offsets

@@ Line 19: / Line 19: @@
 ** So far, this has only really been tested for the fADC250's
 ** hd_root -PPLUGINS=lowlevel_online -PLOWLEVEL:CHECKEMULATION=1 data.evio
-*** This prints out cases
+*** This prints out cases where the emulated pulses don't match the measured pulses
-** hd_dump -PEVIO:VERBOSE=10 -DD
+** hd_dump -PSKIP_TO_EVENT=XXXXXX -PEVIO:VERBOSE=10 -DDf250PulseData data.evio
+*** If you see bad pulses, you can look at the pulse data by running a command like this
 * Start the timing calibrations
+** Start with the [[RF Calibration]] - for normal running, it's usually enough to just calibrate the fine timing offsets