1 / 6

DQM SHIFT TODO REMINDER

DQM SHIFT TODO REMINDER. T. Sch örner-Sadenius Hamburg University CAL Meeting, 18 January 2005. RUN CONTROL PROBLEM and how to avoid it. Signature : cannot start runs, cannot select run type from “FILE” menue .. Solution:

castor-carney
Download Presentation

DQM SHIFT TODO REMINDER

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DQM SHIFT TODO REMINDER T. Schörner-Sadenius Hamburg University CAL Meeting, 18 January 2005

  2. RUN CONTROL PROBLEM and how to avoid it Signature: cannot start runs, cannot select run type from “FILE” menue .. Solution: • Always click several times on the “idle” button in the RC after the readout has been started; the “readout” field should show “DAQ” (or “CALIB”) and the button should be blue. • Then select a run type from the “FILE” menue. The “Run!” button should turn green. • If it does not turn green, click on “idle” again. The “Run!” button should then turn green. For safety select again the run type from the “FILE” menue that you want – even if its name is still shown in the “FILE” window.

  3. CAL POWER SERVER ALARM in Slow Control HC3CONTROL os9 machine in sixth floor has to be reset. Attention: Run does not have to be stopped for this! Some shift crews not aware of this! HC3CONTROL may be unreachable and still LV and HV probably there!

  4. SWITCHING ON BCAL MODULESand testing they are on • Decide together with the shift leader how urgent the action is. If no lumi (ahead) take your time and double-check. • Stop the ongoing ZEUS run. • Identify the module that failed using the “ping monitor” web page, the HIP “UNO new bad channels” histograms, the UNO online histos (in case of a physics run) or a locally taken UNO run. • Login as cal_user to ajax and start caw. • Type “bhvon NN”, where “NN” is the number of the module in question. • Takes time (5 minutes)! “Setting to 500V … 1100 V”. • Check for error messages in the caw output. • If you have time: take a UNO run to make sure module is on.

  5. THE STORY WITH THE GAFsand why we want to calibrate so often • Assumption: Number of bad channels increases with time, and we want to be conservative decide AT THE END of a given period about the final list of bad channels for that period ALWAYS update bad channels BEFORE doing an ADC-to-Volts calibration or an FEC. Otherwise we miss the bad channels of the period before the calibration and assume only the bad channels that we have after the calibration! • In order to keep number of bad channels as small as possible make calibration periods as short as possible  use every CAL_QUICK_CALIB run and each opportunity for manual BC update! • UNO scale factors: Offline scale factors are calculated for the future (in contrast to bad channel list) it is important to calibrate (CAL_QUICK_CALIB!) asap after a power glitch or a magnet quench. UNO GAFs BC GAFs BCupdate BCupdate BCupdate FEC BCupdate

  6. Additional check-lists for FEC and ADC-to-Volts will follow.

More Related