lhc systems providing post-mortem dataidentifying pm-like lhc data available from bi systems –bitb...

30
LHC Systems Providing Post-Mortem Data BI-TB 16/5/2019 Stephen Jackson Diogo Miguel Louro Alves Manuel Gonzalez Berges Enrico Bravin Marek Gasior Lars Jensen Ana Guerrero Ollacarizqueta Stephane Bart Pedersen Athanasios Topaloudis

Upload: others

Post on 09-Mar-2020

3 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

LHC Systems Providing Post-Mortem Data

BI-TB

16/5/2019

Stephen Jackson

Diogo Miguel Louro Alves

Manuel Gonzalez Berges

Enrico Bravin

Marek Gasior

Lars Jensen

Ana Guerrero Ollacarizqueta

Stephane Bart Pedersen

Athanasios Topaloudis

Page 2: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

Introduction (recap)

2

• Request from LMC and Evian for a “postmortem button”– For any reason at any time, be able to record all data

usually recorded in postmortem.– There should be a way to trigger this from the CCC, or

from timing event. – Are there drawbacks (acquisition dead-time, limited

storage)?– The idea is to provide a list of what is easy/difficult,

free/expensive to the management– Example of use cases:

• 10 Hz oscillations (BPMs, diamond BLMs, BLMs)• What happens at the beginning of the ramp• Storing of ADT kick signals (not yet in postmortem)

Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

Page 3: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

Introduction

3

• Task– Identify LHC data available from BI systems

– With the view to acquiring from an on-demand trigger (MTG or soft)

• Issued by an LHC Operator or another intelligent source

• Only a few systems with interesting data at the TxT level– So extended this presentation to include lower

resolution data as well

Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

Page 4: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

How to Classify Different BI Data?

4

• Number of Monitors• Number of Samples• Sample Rate• Approximate Data Size• Maximum Triggering Frequency • Ad-hoc Triggering Possible? • Ad-hoc Triggering Allowed? • Triggered by Internal Analysis in FESA class? • Accessible via (RDA, SDDS, PM server,…)? • Users of the data• Notes

Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

Page 5: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

Main LHC BI Observables

5

• BLM • BPM

– Standard, Interlock & DOROS

• BBQ• BSRT• Orbit Feedback• BCT

– F & DC

• BRASLHC

Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

Page 6: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BLM 1/5

6Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

PostMortemData

Number of Monitors ~4’000

Description Post Mortem Buffers

Number of Samples (Main data) 25’600

Sample Rate (Main data) 40uS

Other Data Last 512 values for running sum 1.31s

Data Size 27 x 28Mb = 756 Mb

Maximum Triggering Frequency Every 2 minutes

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? No

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users Post-Mortem Analysis

Notes Some limitations interacting with XPOC (shares buffers)

Page 7: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BLM 2/5

7Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

PostMortemExpertData

Number of Monitors ~4’000

Description Complete Post Mortem buffers

Number of Samples (Main data) 43’690

Sample Rate (Main data) 40uS

Other Data No

Data Size 27 x 43Mb = 1.1Gb

Maximum Triggering Frequency Every 2 minutes

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? No

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? NFS files

Users None

Notes Some limitations interacting with XPOC (shares buffers)

Page 8: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BLM 3/5

8Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

BeamDumpData1/2

Number of Monitors ~4’100

Description XPOC data

Number of Samples (Main data) 200

Sample Rate (Main data) 40uS

Other Data No

Data Size 27 x 220K = 6Mb

Maximum Triggering Frequency Every 2 minutes

Ad-hoc Triggering Possible? No

Ad-hoc Triggering Allowed? No

Triggered by Timing

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users LBDS

Notes Some limitations interacting with PM (shares buffers)

Page 9: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BLM 4/5

9Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

CaptureData (Study)

Number of Monitors ~4’000

Description On demand capture data

Number of Samples (Main data) 10’240 (Limited from a possible 43’690)

Sample Rate (Main data) 80us

Other Data No

Data Size 27 x 541K = 14.6Mb

Maximum Triggering Frequency Every 2 minutes

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? Yes unless being used by IQC

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and SDDS

Users UFO Buster

Notes Some limitations interacting with IQC (shares buffers)

Page 10: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BLM 5/5

10Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

CaptureData (IQC)

Number of Monitors ~4’000

Description On demand IQC data

Number of Samples (Main data) 512

Sample Rate (Main data) 40us

Other Data No

Data Size 27 x 10Mb = 270Mb

Maximum Triggering Frequency Every 30 seconds

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? Yes

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and SDDS

Users IQC

Notes Some limitations interacting with Study (shares buffers)

Page 11: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BPM 1/4

11Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

PostMortemData (turn by turn)

Number of Monitors ~1’000

Description Post Mortem buffer (turn by turn)

Number of Samples (Main data) 1024

Sample Rate (Main data) Turn

Other Data Last 1024 values for average orbit H/V

Data Size ?

Maximum Triggering Frequency Every 30 seconds

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? ?

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users Post-Mortem Analysis

Notes

Page 12: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BPM (2/4)

12Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

PostMortemData (orbit by orbit)

Number of Monitors ~1’000

Description Post Mortem buffers (orbit by orbit)

Number of Samples (Main data) 1024

Sample Rate (Main data) Orbits (spaced by 40msec)

Other Data Last 1024 values for average orbit H/V

Data Size ?

Maximum Triggering Frequency Every 30 seconds

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? ?

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users Post-Mortem Analysis

Notes

Page 13: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BPM (3/4)

13Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

XpocData

Number of Monitors ~1’000

Description XPOC data for LBDS

Number of Samples (Main data) 1024

Sample Rate (Main data) Turn

Other Data Last 1024 values for average orbit H/V

Data Size ?

Maximum Triggering Frequency Every 30 seconds

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? ?

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users Post-Mortem Analysis

Notes

Page 14: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BPM (4/4)

14Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

CapturedData

Number of Monitors ~1’000

Description Triggered capture data

Number of Samples (Main data) 512K

Sample Rate (Main data) Bunch by bunch

Other Data No

Data Size ?

Maximum Triggering Frequency Every minute

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? Yes

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA, files

Users First turns, optics

Notes

Page 15: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BPM DOROS 1/2

15Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

PostMortemData

Number of Monitors ~110

Description PostMortem data arrays. Acquired at 25 Hz in circular buffers covering 2 min before

Post-Mortem and 8 sec after.

Number of Samples (Main data) 3200 samples per parameter per BPM

Sample Rate (Main data) 25 Hz

Other Data .rawValP .rawValN .jawPosP .jawPosN .sisPositions .absolutePositions

Data Size (8+1+4+4+4+4+4+4) x 3200 x 110 = 11.08 MBytes

Maximum Triggering Frequency Every 3 seconds when triggered by timing (TBC)

Ad-hoc Triggering Possible? Yes (TBC)

Ad-hoc Triggering Allowed? Yes (TBC)

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users ?

Notes

Page 16: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BPM DOROS 2/2

16Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

CaptureData

Number of Monitors ~110

Description On demand capture data:

-Orbit & oscillation data

Number of Samples (Main data) Oscillation: 132072

Orbit: 132072

Sample Rate (Main data) 25 Hz

Other Data Some configuration & status data

Data Size (4+4+4+4+4+4+4+4) * 132072 * 110 = 443.37 MBytes for all BPMs

Maximum Triggering Frequency No limit (TBC)

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? Yes

Triggered by Timing or RDA

Internal FESA analysis? Only decimation

Accessible via? RDA ans SDDS (file created from Java application)

Users ?

Notes

Page 17: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BPM Interlock (1/5)

17Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

PostMortemData

Number of Monitors 8

Description Post Mortem Buffers (orbit and turn buffers)

Number of Samples (Main data) 4 x 1024

Sample Rate (Main data) Orbit and turn

Other Data Raw turn sum buffers

Data Size 2 x 160 Kb = 320 Kb

Maximum Triggering Frequency ??

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? No

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users Post-Mortem Analysis (LBDS --> BPMS)

Notes Needs to be reset manually

Page 18: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BPM Interlock (2/5)

18Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

XpocData

Number of Monitors 8

Description XPOC data

Number of Samples (Main data) 1024

Sample Rate (Main data) Turn

Other Data Raw XPOC buffers

Data Size 8 x 24K = 192K

Maximum Triggering Frequency Every 2 minutes

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? No

Triggered by Timing

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users LBDS

Notes

Page 19: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BPM Interlock (3/5)

19Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

InterlockData (turn by turn)

Number of Monitors 8

Description Interlock Data

Number of Samples (Main data) 1024

Sample Rate (Main data) Turn

Other Data internal counters (error, alarm, status)

Data Size 8 x 30 Kb = 240 Kb

Maximum Triggering Frequency ??

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? ?No

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users Experts (LBDS --> BPMSINT)

Notes The analysis of these data happen in the Expert GUI

Page 20: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BPM Interlock (4/5)

20Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

CaptureData

Number of Monitors 8

Description Raw Bunch by Bunch buffers (last 147 turns)

Number of Samples (Main data) 147 x 3564

Sample Rate (Main data) 25ns

Other Data debug info

Data Size 8 x 4 Mb = 32 Mb

Maximum Triggering Frequency ??

Ad-hoc Triggering Possible? ??

Ad-hoc Triggering Allowed? ??

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users Experts (LBDS --> BPMSDiag)

Notes The analysis of these data happen in the Expert GUI

Page 21: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BPM Interlock (5/5)

21Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

CaptureData

Number of Monitors 8

Description Bunch by Bunch diagnostics (last 147 turns)

Number of Samples (Main data) 147 x 3564

Sample Rate (Main data) 25ns

Other Data thresholds in ADC and mm

Data Size 8 x 4 Mb = 32 Mb

Maximum Triggering Frequency ??

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? No

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users Post-Mortem Analysis (LBDS --> BPMSDiagPos)

Notes There is no anaylis implemented yet

Page 22: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BBQ

22Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

PostMortemData

Number of Monitors 8

Description Post Mortem Buffers (orbit and turn buffers)

Number of Samples (Main data) 256K

Sample Rate (Main data) Turn

Other Data None

Data Size ~32 Mb

Maximum Triggering Frequency 60 seconds

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? No

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA and PM Server

Users PM

Notes Raw Oscillation Data

Page 23: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

Orbit Feedback

23Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

IqcAcquisition

Number of Monitors ~1’150 * 2 (H/V)

Description Last position data from BPMs for IQC

Number of Samples (Main data) 1

Sample Rate (Main data) 1 per second

Other Data BPM Status info from last second

Data Size 74Kb

Maximum Triggering Frequency Every second

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? Yes

Triggered by Timing or RDA

Internal FESA analysis? No

Accessible via? RDA

Users IQC

Notes Also on logging DB

Page 24: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BCT (1/3) - BCTFVFC

24Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

PostMortemData

Number of Monitors 4

Description Post Mortem buffers

Number of Samples (Main data) 15000

Sample Rate (Main data) 11KHz

Other Data No

Data Size ~120Kb

Maximum Triggering Frequency >5s

Ad-hoc Triggering Possible? Yes

Ad-hoc Triggering Allowed? Yes

Triggered by Timing or RDA

Internal FESA analysis? no

Accessible via? RDA and PM Servers

Users PM

Notes

Page 25: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BCT (2/3) - BCTFVFC

25Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

XPocAcquisition

Number of Monitors 4

Description Post Mortem buffers

Number of Samples (Main data) 15000

Sample Rate (Main data) 11KHz

Other Data No

Data Size ~120Kb

Maximum Triggering Frequency >5s

Ad-hoc Triggering Possible? No

Ad-hoc Triggering Allowed? No

Triggered by Timing

Internal FESA analysis? no

Accessible via? XPOC server

Users XPOC

Notes

Page 26: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BCT (3/3) - BCTDCLHC2

26Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

PostMortemData

Number of Monitors 4

Description Post Mortem buffers

Number of Samples (Main data) 3000

Sample Rate (Main data) 50Hz

Other Data No

Data Size ~12Kb

Maximum Triggering Frequency >5

Ad-hoc Triggering Possible? No

Ad-hoc Triggering Allowed? No

Triggered by Timing

Internal FESA analysis? no

Accessible via? PM Server

Users PM

Notes

Page 27: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BRASC

27Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

PostMortemData

Number of Monitors 8

Description Post Mortem buffers

Number of Samples (Main data) 3564

Sample Rate (Main data) 40MHz

Other Data No

Data Size ~30Kb

Maximum Triggering Frequency >5

Ad-hoc Triggering Possible? No

Ad-hoc Triggering Allowed? No

Triggered by Timing

Internal FESA analysis? no

Accessible via? PM Server

Users PM

Notes

Page 28: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

BRASG

28Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

PostMortemData

Number of Monitors 4

Description Post Mortem buffers

Number of Samples (Main data) 10692

Sample Rate (Main data) 40MHz

Other Data No

Data Size ~90Kb

Maximum Triggering Frequency >5

Ad-hoc Triggering Possible? No

Ad-hoc Triggering Allowed? No

Triggered by Timing

Internal FESA analysis? no

Accessible via? PM Server

Users PM

Notes

Page 29: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

A Comment

29

• “The data is already in logging so not interesting”– Is there not an interest to identify a time of

interest and package the same data as an event?

• The could be used as input to future machine learning ?

• BRAN, BSRT, …

Identifying PM-like LHC data available from BI systems – BITB 16/5/2019

Page 30: LHC Systems Providing Post-Mortem DataIdentifying PM-like LHC data available from BI systems –BITB 16/5/2019 17 PostMortemData Number of Monitors 8 Description Post Mortem Buffers

Possible New Data for Run 3

30

• Orbit Feedback system– 25 Hz BPM data and status– Full frequency BBQ tunes (from all systems)– COD+QUAD deflection / status + current requests– As much history as you can consume

• BLM– 100 Hz data

• Already used in several cases (collimation feedback, loss-maps, …)

– Create a new Capture type (called CAPTURE)• Return all 43’690 80us samples

– Covering 3.4952 seconds – STUDY currently covers 0.8192 seconds

• With new f/w, MBLT means readout will be several times faster

• BBQ– Raw data for 10s of seconds on new MENA25 CPU?

Identifying PM-like LHC data available from BI systems – BITB 16/5/2019