• Make sure that the right SDAQ and SEQ parameters are used: Select SDAQ Parameter and SEQ Parameter from the global parameter menu of the download gui (smt_gui.py in directory ~d0smt/onl_smtnew):


• n_cal_events (in hexadecimal) denotes the number of events per calibration step (pedestal, one calibration voltage)
• sdaq_cal_pattern encodes the calibration pattern downloaded to the SVX. A number n means that every 2^(n-1) channel is calibrated at once. For n=4 the calibration is repeated 8 times for every 8th channel.




• ncalv denotes the number of calibration voltages that are used. 0 <= ncalv <= 5.
• The calibration voltages for both polarities (p-side and n-side readout) are listed below.
• Prepare the VME crates that you want to use
• Select the VRBs you want to calibrate.
• Hit "reinit VME".
• Open the SDAQ monitoring GUI:
• if required setup d0online
• As d0smt start onl_smtnew/util start ./smt_sdaq_gui.py
• Select the crates that you want to calibrate in the GUI by clicking the check button:

This GUI displays the status of the SDAQ process on the frontend. It is updated every 5 seconds. Most important is the Event number which should increase every update. The last line displays the Run Modus.
• Execute  setup onl_calib_sytem and run start_calib_manager_gui:


This GUI tells the status of the run from the point of view of the SDAQ supervisor and the calibration manager.  It also shows whether the data could be committed to the database.  It cannot display the status of the process on the frontend.
• Open a taker window and select a run configuration  "calibration/smt/calib-smt-0xNN-SCL-1.1" where NN stands for the geographical sector of the crate you want to calibrate. Crate 61 has a problem with VRB slot 17. If you disable this slot you might run crate 61 together with other crates. For example you have the following possibilities to calibrate the SMT:
• calib-smt-all-SCL-1.1    all crates at once
• calib-smt-north-1.1  north half of SMT
• calib-smt-63-65-67-69-6B-1.1  Crates 63, 65, 67, 69, 6B together (south half without 61)
• calib-smt-0x61-SCL-1.1  only crate 61
• Hit the "Start" button of the taker window.
• Follow the proceeding of the SDAQ run on the smt_sdaq_gui. Normal stages should be: init - ped - gain - DB commit - success. An occasional stalled is normal. The event number is updated every 5 seconds. If 800 events are configured the total number of events should be 8800: 800 for the pedestal and 2x5x800 for 5 calibration voltages with 5 polarities and 800 events each. To calculate new thresholds a pedestal run is enough. Set the SEQ Parameter ncalv to 0 to take a pedestal only run. The total error count is a sum of DMA and interrupt errors. This number should be low compared to the total number of events. These errors are not harmful but slow down the process. For the moment a rather large number of missing channels and order errors are normal.

When the run is finished the calibration_manager_gui should state that the commit to the database has been successfull.

---

• For debugging you should monitor the messages of the front end processor:
• Look up in the IOC mapping which port the frontend processor is connected to.
• Telnet to t-d0-mch2, user name ioc, password xxxxxxxx
• Type "connect PP" where PP stands for the port number. Note that only one session at a time is allowed per port.
• Don't forget to log out (hit "Ctrl-]" and then enter the command "quit") after the session.
• 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 "< ssdaqLoader".
• Hit the "init SDAQ" button for your crate.
• 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 the reason.
• 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 calibration button:


• 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 new threshold:


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 will be created.
• Copy all files *.C and *.h out of  /projects/823d/com/fox/sdaqAna to your working directory.
• Start root (after setup D0RunII t01.xx.00).
• Follow the load sequence described in doit.C:
• .L SdaqRootTuple.C
• .L SmtSdaqRootTuple.C
• .L hdiclass.C
• .L svxclass.C
• .L drawthreshold.C
• .L drawerror.C
• .L thistoanalysis.C
• .L sdaq.C
• .L reference.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
• THistoAnalysis cmp(s,r)
• cmp.drawThreshold()