1 / 5

G.Crosetti, M.Lo Vetere, E.Robutti

G.Crosetti, M.Lo Vetere, E.Robutti. IFR online calibrations status and plans. What we do now.

germane-gomez
Download Presentation

G.Crosetti, M.Lo Vetere, E.Robutti

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. G.Crosetti, M.Lo Vetere, E.Robutti IFR online calibrations status and plans

  2. What we do now • IFR is using the calibration cycle to pulse the front-end electronics with the purpose of figuring out dead and hot channels. This information is complementary to the one that can be obtained from datastream calibrations. • Hot channels are not masked online. There are no compelling reasons to do it now.The total event size wouldn’t be reduced much and the trasportation of the IFR data is fast enough. • As a consequence, no action is performed based on the result of a calibration run in normal situations. • A calibration run takes a minute or two to be performed. We would like to continue to perform a calibration run once per week and possibly once per day. • We store the xtc files to keep track of the performances of the electronics over time. • Plots of the perfomances are produced running offline on the xtc files.

  3. How we do it • We use a calibration cycle xtc file to drive the FSMs through the calibration sequence. The calibration cycle is registered with the configuration database. The calibration cycle xtc is loaded on the ROMS (for specific configuration keys) using the “ad interim” rdf system. • The calibration actions on the ROM are implemented using CalActions class and derived. The kind of cycle to perform is selected in CalMetaFactory according to the calibration cycle tc. • The L1 dataflow transitions are transported out of the ROMS. • At the Oep level runs the same code we use for datataking. For the time being this means we only want to log L1 actions to the xtc file. No special parameter has to be provided to OEP. • Xtc file are processed offline to produce histo/ps files that are inspected visually.

  4. Short term plan • We propose to automate (running by the DAQ shifter) the present IFR calibration. An xtc file should be produced. No validation step is required to the DAQ shifter. This will be done offline by IFR experts. • In case of failure during calibrations it may be necessary to reboot the IFR ROMS. No other actions are forseen. • For the time been no interaction with the Detector Control is necessary. We perform calibration at any High Voltage. Usually at the Injection set point. • Daq crates must be powered and Low Voltages, powering the front-end elements, must be on during calibration (as well in datataking). These DC parameters are not in the runnable flag yet.

  5. Medium term plan • We want to use CalChan and related structures and sink L1. • We will refine the calibration sequence with the aim of introducing other checks on the status of the electronics and prepare for TDC boards. • In the future we would like to change the HV during a calibration cycle between the two values corresponding to the Runnable set point and 0V. But this is not a priority nor mandatory. • When we will be confident, we would like to start writing into the condition database the results of the calibration process. • In the long run we will reload the data from the condition database to perform IFB/ITB noisy FECs suppression and ITB time offsets subtraction.

More Related