1 / 21

Status of the V0 - DCS

Status of the V0 - DCS. Teflon foil. connector. WLS fibres. PM. optical fibres. V0C. V0A. 2. 1. 3. secteur 0. 3. 2. 1. anneau 0. 4. 7. V0C. 5. 6. The V0 detector. Two scintillator hodoscopes at low angles trigger for the central detectors background filter for Muon

ulema
Download Presentation

Status of the V0 - DCS

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. Status of the V0 - DCS R.TIEULENT - DCS Workshop

  2. Teflon foil connector WLS fibres PM optical fibres V0C V0A 2 1 3 secteur 0 3 2 1 anneau 0 4 7 V0C 5 6 The V0 detector • Two scintillator hodoscopes at low angles • trigger for the central detectors • background filter for Muon • 2 x 32 channels (V0A et V0C) • 8 sectors of 4 channels per hodoscope R.TIEULENT - DCS Workshop

  3. -6V +6V ShoeBox Number of channels • 64 PMT Channels : • 1 HV Channel per PMT • 1 Amplifier channel per PMT • Amplifier box (shoebox) : • provides 8 amplifier channels • needs 2 LV per shoebox (6V) • 64 HV Channels (6 HV boards) • 16 LV Channels (4 LV boards) R.TIEULENT - DCS Workshop

  4. The V0-FSM Tree V0 V0A FEE V0C HV LV HV LV HV Quadrant0 Quadrant0 HV HV HV HV Quadrant0 Quadrant0 HV HV HV Quadrant0 Quadrant0 Sector Quadrant0 Quadrant0 Sector [0-7] [0-7] +6V -6V +6V -6V Ring Ring [0-3] [0-3] R.TIEULENT - DCS Workshop

  5. The common V0/T0 CAEN Crate 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 HV A1733P HV A1733P HV A1733P HV A1733P HV A1733P HV A1733P LV A1513B LV A1513B LV A1513B LV A1513B HV A1733N HV A1733N LV A1513B LV A1513B V0 T0 CAEN Main frame has been received last week. R.TIEULENT - DCS Workshop

  6. Proposition of CAEN crate control T0/V0 T0 V0 Crate T0A T0C V0A V0C HV/LV HV/LV HV/LV HV/LV Caen crate Channel Channel Channel Channel Interlock If ANY Channels are ON R.TIEULENT - DCS Workshop

  7. Development of the control R.TIEULENT - DCS Workshop

  8. Front End Electronics CCIU, pilot board - collects the CIU data - provides the final triggers - interface with the DAQ • PRR in February 10, 2006 • Final test at PS (May->July) • Final design (mid June ->…) • Manufacturing (mid July->…) • Setting (end of September->…) back-plane, connection board CIU, one board per ring R.TIEULENT - DCS Workshop

  9. Channel Interface Unit Board • Charge integration: dual programmable high speed integrator (the first works on even BC periods while the second one works on odd BC periods) • Time digitisation: HPTDC through a low threshold discriminator • Pre-processing for the generation of the various triggers. • Generation of the observation window system • Partial sum (per ring) of the charge integration and fired segments (FGPA function) • Data storage meanwhile a L0 and L1 trigger : Data are sent to the CCIU board through the backplane on a L1 trigger occurrence (FPGA function) Dual high speed integrator low threshold discriminator HPTDC Observation window generation Hit detection (through observation widows)

  10. Channel Concentrator Interface Unit Board L0, busy and triggers connectors SIU mezzanine EMCal interface • Following a L1 trigger, the CCIU board collects through the back plane the data stored on each CIU board while waiting for a L2 trigger. • Processing of the final trigger signals which consists in performing the final sum, then to compare it to a programmable threshold and then to select 5 triggers to be sent to CTP. • Provides an interface to the DAQ : All the data collected by the FEE are sent to the DAQ (through the DDL and via the SIU mezzanine) on a L2 trigger accept. • Provides an interface for the slow control : all the parameters of the FEE can be loaded, read, adjusted and modified through the DCS mezzanine. • Manage the clock distribution (from the LHC clock to the CIU cards). • Provides an interface with the EMCal. DCS mezzanine DCS Mezzanine Clock distribution management

  11. PVSS II (FED - Client) FED Server InterComLayer FEE Client FeeServer CCIU Front-End-Electronics in DCSControl and monitor channels Responsible person: C. Combaret Supervisory Layer Load configuration data from fileOR database Front-End Device Interface (FED) Config. File Control Layer Config. DB Front-End Electronics Interface (FEE) Cmd / ACK Channel Field Layer DCS board Service Channel Internal Bus Systems Message Channel R.TIEULENT - DCS Workshop

  12. Working principle • Control of the DCS board components : • TTCRx registers (example : TTC channel B data output for the CCIU board) • Control of the FEE boards (CCIU and CIU) components • HPTDCs • Modes • Pedestals • … • Collection and publication of monitoring data • DCS board • FEE R.TIEULENT - DCS Workshop

  13. Control panels proposal • Main panel with : • Configure (from configuration file or database configuration parameters?) • Reset • Child panel with status of the different components of the system controlled by the DCS board • HPTDC on DCS board • CCIU registers • CIU registers • Sub-child panels with individual access to registers and functions of the previous components R.TIEULENT - DCS Workshop

  14. Summary of calibration procedure Gains and pedestals computed by Online Monitoring using dedicated data (minimum bias and +/- 10 around the event of interest mini-events respectively)stored in the FEE and sent to the DAQ with theevents of interest. Note that this procedure is achieved by the FEE independently of theCentral Trigger Processor. These values will be written in the Calibration Data Base for later use by offliners and updated at each run change. Validity period will be run interval unless a hardware failure occurs. R.TIEULENT - DCS Workshop

  15. FEE Use case 6 Data flow DAQ SHUTTLE DA F.R. Publish agent DAQ FES C.C. T0 custodial storage DAQ Logbook DB AliEn FC F.R. SHUTTLE Config’tion DB DCS F.R. : Filimon Roukoutakis C.C. C.C. : Christophe Combaret R.TIEULENT - DCS Workshop

  16. Calibration excel file R.TIEULENT - DCS Workshop

  17. Installation Installation of the V0C (dimuon side) from 5 to 7 February R.TIEULENT - DCS Workshop

  18. Backup R.TIEULENT - DCS Workshop

  19. Online output data for DAQ and monitoring • An event as seen by the V0 Front End Electronics will be: • Charges (64). • Arrival times (64) and time response widths (64). • Beam-Beam (BB) and Beam-Gas (BG) flags (64). • States of the 5 triggers sent to the CTP (MinBias, BB, BG, Central,SemiCentral). • For each event triggered by a L2 signal coming from the CTP (called Event-Of-Interest), the following information will be sent to the DAQ: • 1. The event of interest itself with all the parameters listed above, for physics analysis • 2. The events between EoI-10 to EoI+10 (charges and BB/BG flags), for monitoring pedestals, pile-up… • 3. The 10 last V0 Minimum Bias events (charges and BB/BG flags), for monitoring gains R.TIEULENT - DCS Workshop

  20. Calibration procedure • Calibration parameters are computed online in the DAQ LDC from sampling dedicated data • Results are made available as ROOT files in the DAQ FES • DCS accesses the Root file in the DAQ FES, compares the parameter values to reference values stored in the DCS Configuration DB and updates the FEE values if needed. R.TIEULENT - DCS Workshop

  21. Calibration Calibration CDB file has been created and CDB reading implemented. Calibration parameters stored into CDB are : • 128 gains, 128 pedestal means, 128 pedestal sigmas (2 QDC per channel) • 64 time gains and 64 time offsets i.e. 512 floats, 4 kB All these parameters are accessible through class AliVZEROCalibData R.TIEULENT - DCS Workshop

More Related