preparation and checklist for the run over errors

Preparation and checklist for the Run

over Errors

• Full EOR/SOR run transition Configuration changes possible

o 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

o List of active DDLs remains the same Readout link not closed Much faster than full EOR/SOR transition

Overview

10/02/2014 Vasco Barroso 2

• Optimized ECS sequence More phases in parallel

• Faster individual phases DCS::SOR DAQ::SOR.COMMANDS (detector scripts) HLT::ENGAGE DAQ::START_PROCESSES

Run 2 Full SOR


• CTP

• HLT

• DAQ

Run 2 Full SOR


Phase Run 1 Target for Run 2 Promised for Run 2

CTP::INIT 5.2 s 1 s 2.2 s

CTP::START

3.0 s 1 s 1.0 s


HLT::ENGAGE

103.8 s 60 s 60 s (aim for less)

HLT::START 4.9 s

Phase Run 1 Target for Run 2

Promised for Run 2

DAQ::START_PROCESSES_LDC

12.7 s 5 s 5.0 s

• Detectors During Run 1

During Run 2

Run 2 Full SOR


DCS::SORDet A

Det B

Det C

DAQ::SORMCH

PMD

SOR.COMMANDS

Det A

Det B

Det C

Det

A

DCS::SOR

DAQ::SOR (includes SOR.COMMANDS)

Det

B

DCS::SOR

DAQ::SOR (includes SOR.COMMANDS)

• Detectors (cont.)

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

TPC

Run 2 Full SOR


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?


Run 2 Full SOR


DetectorRun 1

Target for Run 2

Promised for Run 2DCS::SOR DAQ::SOR SOR

COMMANDS

ACO 0.1 s 11.3 s 15 s

EMC 27.7 s 15 s 10 s

FMD 0.1 s 7.1 s 15 s

HMP 16.9 s 20.3 s 15 s 9.0 s + ?

MCH 20.5 s 31.7 s 15 s 10 s

MTR 2.5 s 15 s

PHS 13.1 s 15 s

PMD 7.3 s 19.0 s 4.1 s 15 s (same as MCH ?)

SDD 0.3 s 19.1 s 15 s


Run 2 Full SOR


DetectorRun 1

Target for Run 2

Promised for Run 2DCS::SOR DAQ::SOR SOR

COMMANDS

SPD 7.0 s 15 s

SSD 3.1 s 6.6 s 15 s

T00 6.3 s 15 s

TOF 3.9 s 15 s

TPC 5.5 s 8.3 s 15 s 5.5 + 10.0 s

TRD 49.5 s 15 s

V00 1.8 s 15 s

ZDC 9.3 s 15 s (same as MCH ?)

• Optimized ECS sequence Marginal gain

• Faster individual phases DCS::EOR HLT::STOP, HLT::DISENGAGE DAQ::EOR.COMMANDS (detector scripts) DAQ::STOPPING_LDCS STOPPING_DAS

Run 2 Full EOR


• CTP

• HLT

• DAQ

Run 2 Full EOR



CTP::STOP 2.0 s 1 s 1.0 s


HLT::STOP 15.0 s 10 s

HLT::DISENGAGE

25.8 s 20 s

Phase Run 1 Target for Run 2

Promised for Run 2

DAQ::STOPPING_LDCS (1) 32.8 s 20 s 20.0 s

(1) Without EOR.COMMANDS

• Detectors DCS::EOR

• Detectors EOR.COMMANDS

Run 2 Full EOR


Detector Run 1 Target for Run 2

Promised for Run 2

EMC 11.4 s 10 s 6.0 s

HMP 16.8 s 10 s

MCH 10.1 s 10 s

TPC 18.5 s 10 s 10.0 s

TRD 32.2 s 10 s


Promised for Run 2

PMD 3.3 s 5 s

SSD 8.3 s 5 s

TPC 5.0 s 5 s

• Detectors DAQ::EOR

• Detectors DAs

Run 2 Full EOR



Promised for Run 2

MCH 10.8 s 2.7 s

PMD 8.0 s (same as MCH ?)

DA Run 1 Target for Run 2

Promised for Run 2

DA-SPD-PHYS 22.9 s 10 s

DA-SPD-Vertex 13.9 s 10 s

DA-TPC-LASER 11.2 s 10 s

DA-TOF-PHYSICS 10.9 s 10 s

Run 2 Fast EOR


From 31.4 to 11.0

• Minimal ECS sequence TRG: stop as usual DCS: fast EOR (10s) HLT: fast STOP/DISENGAGE (10s) DAQ: fast stop LDCs (5s)

oReadout link remains open (see next slide)oNo/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)

Run 2 Fast EOR


Run 2 Fast EOR



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) ?

Run 2 Fast SOR


From 68.1 to 18.1

• Minimal ECS sequence TRG: start as usual DCS: fast SOR (10s) (can run on

background ?) HLT: fast ENGAGE (10s) DAQ: fast start LDCs (5s)

oReadout link already open DAQ: start GDCs as usual No/minimal DAQ::SOR

oNo/minimal SOR.COMMANDS (see next slide) DAs: start as usual

Run 2 Fast SOR


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) ?

Run 2 Fast EOR/SOR transition



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?

• Full SOR/EOR sequences optimized Individual phases have to speedup Must be tested once the full system is

back to oCheck for hidden dependenciesoProfile 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

Final Remarks


EXTRA SLIDES


Run 2 Full SOR


Run 2 Full EOR


preparation and checklist for the run over errors

Documents