R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

1

Is there any DIP variables update we should prepare for RUN II?

R. Alemany BE/OP/LHC

9/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

2

EXISTING VARIABLES INDIP/ACC/LHC

Review of what LHC sends via DIP to the experiments

9/15/2014

39/15/2014 R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

49/15/2014R. Alemany BE/OP/LHC

LHC Background Study Group: LBS #57

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

5

New variables for RUN II comming

9/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

69/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

79/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

8

Only for IP

5?

9/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

99/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

109/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

119/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

12

AUTOMATIC SCAN APPLICATIONNew variable for RUN II

9/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

13

Flag Name Source Type Values CommentSequence Exp string ENABLE

PAUSEABORT

Delay1 Exp integer Time on IDLETime_Stamp LHC string UTC time Step LHC integer Scan step as indicated in the sequence file. For

states IDLE and SUSPENDED a step value of 9999 will be broadcast. For the first STANDBY the broadcast step value will be 0, for the last STANDBY (corresponding to END_SEQUENCE) the broadcast step will be the one indicated in the sequence file.

Acquisition_Flag LHC boolean False=DISABLEDTrue=ENABLED

False = beam(s) may be movingTrue = beams are quiescent

LumiScan_Status LHC string STANDBYTRIMMINGIDLEACQUIRINGSUSPENDED

Indicates the state machine states as in Fig. 2.

Step_Progress LHC integer Countdown of T1 or of the time specified in the SECONDS_WAIT command; depends on the state.

9/15/2014

14

Flag Name Source Type Values CommentSet_Nominal_Displacement_B1_sepPlane

LHC double Integrated B1 displacement in the separation plane w.r.t. first position broadcast after the command INITIALIZE_TRIM (mm). Here the SET value as specified in (or inferred from) the sequence file is given.

Set_Nominal_Displacement_B2_sepPlane

LHC double Integrated B2 displacement in the separation plane w.r.t. first position broadcast after the command INITIALIZE_TRIM (mm). Here the SET value as specified in (or inferred from) the sequence file is given.

Set_Nominal_Displacement_B1_xingPlane

LHC double Integrated B1 displacement in the crossing plane w.r.t. first position broadcast after the command INITIALIZE_TRIM (mm). Here the SET value as specified in (or inferred from) the sequence file is given.

Set_Nominal_Displacement_B2_xingPlane

LHC double Integrated B2 displacement in the crossing plane w.r.t. first position broadcast after the command INITIALIZE_TRIM (mm). Here the SET value as specified in (or inferred from) the sequence file is given.

Read_Nominal_Displacement_B1_sepPlane

LHC double B1 displacement in the separation plane. Here the value READ from the TRIM controller will be given. Table 2 shows an example of the values read from a vertical luminosity optimization and Table 3 shows an example of the values read during a vertical vdM scan.

Read _Nominal_Displacement_B2_sepPlane

LHC double B2 displacement in the separation plane. Here the value READ from the TRIM controller will be given. Table 2 shows an example of the values read from a vertical luminosity optimization and Table 3 shows an example of the values read during a vertical vdM scan.

Read _Nominal_Displacement_B1_xingPlane

LHC double B1 displacement in the crossing plane. Here the value READ from the TRIM controller will be given. Table 2 shows an example of the values read from a vertical luminosity optimization and Table 3 shows an example of the values read during a vertical vdM scan.

Read _Nominal_Displacement_B2_xingPlane

LHC double B2 displacement in the crossing plane. Here the value READ from the TRIM controller will be given. Table 2 shows an example of the values read from a vertical luminosity optimization and Table 3 shows an example of the values read during a vertical vdM scan.

Nominal_Separation LHC double Integrated total separation (in the x-y plane) between B1 and B2, as inferred from the four Set_Nominal_Displacements above. Needed for backward compatibility with the existing vdM scan software.

9/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

15

Flag Name Source Type Values CommentPlane LHC string SEPARATION

CROSSINGMIXEDNONE

Used by the experiment to identify the scan plane of the whole sequence and not the plane in which the beam moved at each step. Identified by the algorithm during the syntax validation phase. It is fixed at the beginning. NONE is sent when there is no scan ongoing.

IP LHC integer 21+22+25+28 all IP being scanned.21+25 only IP1 and 5 being scanned

Used by the experiment to identify the IP(s) being scanned all along the whole sequence and not the IP(s) moved at each step. 0 when no scan is ongoing.

Beam LHC integer 1,2,3,0 3 = both beams scan; 0 = no beam scan.

2 NEW VARIABLES TO IMPLEMENT ON THE EXPERIMENT SIDEe.g. DIP/ALICE/LHC/…/LUMINOSITYAUTOSCAN

17 NEW VARIABLE TO IMPLEMENT ON THE LHC SIDE e.g. DIP/ACC/LHC/BEAM/LUMINOSITYAUTOSCAN

9/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

16

OTHER QUESTIONS

9/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

17

1. Background from experiments, IS IT WORTH HAVING A DEDICATED TALK ABOUT THIS DURING A NEXT MEETING? The aim being that LHC OP will like to understand those numbers2. Pile-up measurement, IS IT WORTH GETTING THIS INFORMATION IN THE LHC CCC or INSTANTANEOUS LUMI IS ENOUGH?

9/15/2014

R. Alemany BE/OP/LHC LHC Background Study Group: LBS #57

18

This is a presentation intended to open the discussion.

Please feel free to send us new variables to include when ever you are ready.

9/15/2014