Preparation and checklist for the run over errors
Download
1 / 23

Preparation and checklist for the Run over Errors - PowerPoint PPT Presentation


  • 78 Views
  • Uploaded on

Preparation and checklist for the Run over Errors. Overview. Full EOR/SOR run transition Configuration changes possible Change TRG config , add/remove detectors Much faster than during Run 1 Fast EOR/SOR run transition

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Preparation and checklist for the Run over Errors' - joyce


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

Overview
Overview

  • Full EOR/SOR run transition

    • Configuration changes possible

      • Change TRG config, add/remove detectors

    • Much faster than during Run 1

  • Fast EOR/SOR run transition

    • Close a run under stable conditions for Offline to handle the data recorded within

    • Configuration changes not possible

      • List of active DDLs remains the same

    • Readout link not closed

    • Much faster than full EOR/SOR transition

Vasco Barroso


Run 2 full sor
Run 2 Full SOR

  • Optimized ECS sequence

    • More phases in parallel

  • Faster individual phases

    • DCS::SOR

    • DAQ::SOR.COMMANDS (detector scripts)

    • HLT::ENGAGE

    • DAQ::START_PROCESSES

Vasco Barroso


Run 2 full sor1
Run 2 Full SOR

  • CTP

  • HLT

  • DAQ

Vasco Barroso


Run 2 full sor2
Run 2 Full SOR

  • Detectors

    • During Run 1

    • During Run 2

DCS::SOR

DAQ::SOR

SOR.COMMANDS

Det A

MCH

Det A

Det B

PMD

Det B

Det C

Det C

Det A

DAQ::SOR (includes SOR.COMMANDS)

DCS::SOR

Det B

DAQ::SOR (includes SOR.COMMANDS)

DCS::SOR

Vasco Barroso


Run 2 full sor3
Run 2 Full SOR

  • Detectors (cont.)

  • Concerns

    • ACO, FMD, HMP, PMD, SDD, SSD and TPC

  • Question to Detectors:

  • In a full SOR sequence, can the SOR.COMMANDS scripts be moved to the DAQ::SOR phase and therefore be executed independently from other detectors and immediately after the DCS::SOR phase of your detector?

Vasco Barroso


Run 2 full sor4
Run 2 Full SOR

  • Detectors (cont.)

Vasco Barroso


Run 2 full sor5
Run 2 Full SOR

  • Detectors (cont.)

Vasco Barroso


Run 2 full eor
Run 2 Full EOR

  • Optimized ECS sequence

    • Marginal gain

  • Faster individual phases

    • DCS::EOR

    • HLT::STOP, HLT::DISENGAGE

    • DAQ::EOR.COMMANDS (detector scripts)

    • DAQ::STOPPING_LDCS

    • STOPPING_DAS

Vasco Barroso


Run 2 full eor1
Run 2 Full EOR

  • CTP

  • HLT

  • DAQ

(1) Without EOR.COMMANDS

Vasco Barroso


Run 2 full eor2
Run 2 Full EOR

  • Detectors DCS::EOR

  • Detectors EOR.COMMANDS

Vasco Barroso


Run 2 full eor3
Run 2 Full EOR

  • Detectors DAQ::EOR

  • Detectors DAs

Vasco Barroso


Run 2 fast eor
Run 2 Fast EOR

From 31.4 to 11.0

Vasco Barroso


Run 2 fast e or
Run 2 Fast EOR

  • Minimal ECS sequence

    • TRG: stop as usual

    • DCS: fast EOR (10s)

    • HLT: fast STOP/DISENGAGE (10s)

    • DAQ: fast stop LDCs (5s)

      • Readout link remains open (see next slide)

      • No/minimal EOR.COMMANDS (see next slide)

    • DAQ: stop GDCs as usual (5s)

    • No DAQ::EOR (MCH and PMD)

    • DAs: stop as usual (10s, same target as full)

Vasco Barroso


Run 2 fast e or1
Run 2 Fast EOR

  • Question to Detectors:

  • In a fast SOR/EOR run transition, can your FEE cope with the fact that the DDL link will remain open?

  • Question to Detectors (HMP, SSD, TPC):

  • In a fast EOR sequence, what are the actions within the DAQ EOR.COMMANDS that still need to be executed (remember that the DDL link will remain open and therefore will be unavailable for any communication with the FEE) ?

Vasco Barroso


Run 2 fast sor
Run 2 Fast SOR

From 68.1 to 18.1

Vasco Barroso


Run 2 fast sor1
Run 2 Fast SOR

  • Minimal ECS sequence

    • TRG: start as usual

    • DCS: fast SOR (10s) (can run on background ?)

    • HLT: fast ENGAGE (10s)

    • DAQ: fast start LDCs (5s)

      • Readout link already open

    • DAQ: start GDCs as usual

    • No/minimal DAQ::SOR

      • No/minimal SOR.COMMANDS (see next slide)

    • DAs: start as usual

Vasco Barroso


Run 2 fast sor2
Run 2 Fast SOR

  • Question to Detectors (ACO, FMD, HMP, MCH, PMD, SDD, SSD, TPC):

  • In a fast SOR sequence, what are the actions within the DAQ SOR.COMMANDS that still need to be executed (remember that the DDL link will remain open and therefore will be unavailable for any communication with the FEE) ?

Vasco Barroso


Run 2 fast eor sor transition
Run 2 Fast EOR/SOR transition

  • Question to Detectors:

  • What will be the impact of:

    • DDL link remains open

    • No FEE reset

    • No/partial SOR/EOR COMMANDS

    • No/partial DCS SOR/EOR

  • on the Offline handling of the data coming from the two runs, the one of the fast EOR and the one of the fast SOR?

  • Vasco Barroso


    Final remarks
    Final Remarks

    • Full SOR/EOR sequences optimized

      • Individual phases have to speedup

      • Must be tested once the full system is back to

        • Check for hidden dependencies

        • Profile individual phases

    • Fast EOR/SOR run transition skeleton defined

      • Feedback from detectors is needed

      • New fast(er)/partial individual phases

      • Must be commissioned at P2

    Vasco Barroso


    Extra slides
    Extra slides

    Vasco Barroso


    Run 2 full sor6
    Run 2 Full SOR

    Vasco Barroso


    Run 2 full eor4
    Run 2 Full EOR

    Vasco Barroso


    ad