LHC Beam Instrumentation Readiness

1

LHC Beam Instrumentation Readiness

Overall State (Organization - Production – Installation – HWC – SW) Details per Observables (Position – Losses – Intensity – Transverse Profiles – Q & Q’ – Luminosity) Conclusions

LHCCWG 19/06/07 BI Readiness [JJ Gras] 2

The new Baseline


Overall State: Organisation: Phase I List

The Phase I LHC Beam Instrumentation consists of Beam Position: ~1000 BPM (~15 types) Beam Losses: 4000 BLM (IC and SEM) Beam Intensity: 4 BCTDC, 4 BCTFR (fast ring), 4

BCTFD (fast dump), 2 BSRA (abort gap), 1000 BPM Beam Transverse Profile: 2 BSRT (sync rad

telesc.), 2 BWS (wire scanners), 4 BGI (Ionisation gas monitors)

Tune and Chromaticity: 14 BPL, 4 BQK (tune kickers), 4 BQS (Schottky)

Luminosity: 8 BRA (2 types)


Overall State: Organisation: BI Responsible


Overall State: Organisation: Commissioners


Overall State: Monitor Production/Installation

Sofar, we managed to produce and install our monitors on time with respect to the general machine schedule. Look this for today details.

It should also be the case for the remaining. But the 2 BGIs (H&V on Beam 2) installed in

LSSR4 have been burned during bake out. We may be able to rebuild one detector for the start-up. Please select the plane!


Overall State: Monitor Installation and INB

During installation, we identify via labels with code bars The functional slots The piece of equipments

We update the layout database through the HWC travelers

We will thus be Ok for INB issues


Overall State: HW Commissioning

All our instrument HWC procedure have been recorded and linked to the corresponding travelers accessible from: The LHC layout entry page The LHC HWC links


Overall State: SW specifications

Based on the LHC BI functional specifications, we are currently discussing/agreeing on the corresponding operational software interfaces of our front end server

We agree with the instrument commissioners the operational application developers The LHCCWG scenario builders



The following operational interfaces have been agreed Beam Position Beam Loss Beam Profiles (BWS, BSRT slow and fast,

BGI) Work is in progress on Intensity and

Q/Q’ The discussed interfaces are

documented in AB/BI/SW web pages


Overall State: SW Prototyping

Based on these specifications, AB/BI/SW will deploy servers on BI LHC FECs emulating

these interfaces (requested for November by Mike) We already have some BPM and BLM FEC

running. We’ll have BWS and BSRT beginning of July. The rest will follow during the Summer.

Transmit corresponding timing and logging requirements to AB/CO


Overall State: Commissioning with Beam

Except for BLM followed by the MPWG, the procedures for the beam instrument commissioning with beam will be defined by BI for the different instruments.

This work will start this Summer and could be presented this Autumn.


Details Per Instrument


Details per Observable: Position Status

Monitors, electronics and front end software will be ready for the start-up

We’ll basically have 5 types of acquisitions: Threading: For the first injections before RF capture

commissioning – Asynchronous – Ok for a few turns. And once beam is captured and our fine delays tuned

Orbit: latest orbit acquisition published at 1 Hz (note: orbit is acquired faster for RT)

Capture: On request, acquires the beam position for selected bunches over a selected number of consecutive turns (see details on BI Web)

XPOC: the position for the last turns prior to every beam-dump event will be available for XPOC

Post Mortem Buffers will be sent on PM events via the CO PM channel.


Details per Observable: Position Remaining Issues

Front End SW Calibration settings handling (first day and

following maintenance – tbd with AB/CO/DM) Trigger sensitivity swapping: necessary but slow

process (hundreds of ms) between pilot and nominal intensity (LSA is informed).

Impact of capture data request on RT data transmission (currently investigated with CO)

Development of the XPOC position interlock system in point 6 (to be defined with Brennan)


Details per Observable: Position Remaining Issues

HW HW commissioning (ongoing) Fine delays tuning (as soon as beam is

captured). Operational Applications:

Full scale test (64 crates) for concentrators (LSA and RT), logging…

RT Feed-back: BI-OP proposal start with a loop at 1Hz then try to increase speed to nominal 10 Hz (or ultimate 25Hz) – work in progress.

RT loop control Fixed displays definition and ad-hoc

developments (if necessary)


Details per Observable: Losses Status


We’ll basically have 4 (+1) acquisition modes: Max Losses: The highest loss observed at the monitor since the

last request (at 1Hz) over 12 different time periods (40uS, 80 uS, 320 uS, 640 uS, 2.54 mS, 10.24 mS, 81.92 mS, 655.36 mS, 1.31 S, 5.24 S, 20.97 S, 83.88 S)

Study Data: triggered as and when required, the granularity of this data will be per channel 1 data point every 40 microseconds covering the last 1.3 secs.

XPOC Data: Triggered every beam dump, will return for each channel 1 data point every 40 microseconds covering the last 100ms before the dump and the following 40ms.


Collimation Data: feed loss data into the collimation control system to ensure that losses don’t exceed set limits during motion. This data will be sent through a dedicated UDP layer and be triggered by the collimation system.


Details per Observable: Losses Remaining Issues

Front End SW Threshold handling (DB, Tools, procedures…

under discussion) Impact of MD data request on RT data

transmission (logging – under investigation with CO)

HW Threshold evaluation (work in progress in BI) Commissioning with Beam (procedures,

options… work in progress in MPWG) Operational Applications:

Full scale tests Fixed displays definition and ad-hoc



Details per Observable: Trans. Prof.

BWS: Status


It will be possible to scan the to beams at the same time but not the two planes on the same beam

2 wires per plane per beam will be installed, 1 operational + 1 hot spare.



BWS: Remaining Issues

Intensity Limitation Quench Limit on Beam Intensity (see details).

Current estimation is up to 1-6 10^12 protons in the circulating beam, ie. about 0.3-2% of the nominal intensity at 7 TeV

Wire Damage Limit on Intensity difficult to predict (new study in progress) but seems close to the Quench limit.

BWS are calibration devices They should be used asap to cross-calibrate

the BSRT and BGI.



Ionisation Gaz Mon.: Status

Beam 1 monitors, electronics and front end software will be ready for the start-up

Possibly one plan on Beam 2 (make your choice)

We’ll basically have 1 continuous acquisition mode: Acquisition of one image per plane obtained from the integration over 20ms of the rest gas ionization signal. The measurement provides beam profile, size and position at 1Hz. The signal quality will depend on the external systems, i.e. gas injection and B-field.



Ionisation Gaz Mon.: Remaining Issues

Front End SW Gas Injection Control (tbd with AT/VAC in

September) B-field control and correction (under

study – encouraging feed-back from Jorg) Operational Applications:

Integration and commissioning of Gas injection and B-Field control

Operational application to be started



Synchroton Light: Status


We’ll basically have 3 acquisition modes Non Gated: Full beam image (profile and sigmas)

integrated over 20 ms published at 1Hz Gated:

Physics mode: All bunches integrated over 1 turn published as fast as possible (every minutes for the 3564 buckets)

MD mode: gated part of the beam (down to one single bunch) over several (up to 3000) consecutive turns



Synchroton Light: Remaining Issues

Front End SW Ethernet link towards the fast camera (in

progress) Automatic gain setting implementation

commissioning HW

Commissioning with beam of the light sources (Onduleur and D3)

Calibration Beam with different energy and intensity conditions (as soon as possible!)

Reliability of the fast camera in tunnel conditions


Details per Observable: Intensity BCTDC: Status


We’ll have 2 DC monitors per beam. One operational, the second as spare (not ‘hot’) in case of problems and specialist monitoring.

We’ll basically have 3 (+1) acquisitions: Injection: beam current for each beam, before and

after an injection. Acquired and published every injection.

Standart: beam current for each beam acquired and published continuously at 1 Hz.

Safe Beam Flag: measured intensity will be transmitted at 10Hz through a dedicated HW link to the MP system.



Details per Observable: Intensity. BCTDC: Remaining Issues

HW Commissioning of the Intensity

transmission HW link Cross-Calibration (Injection lines, fast

ring BCT) No automatic arbitration between the 2

redundant monitors for the start-up Operational Applications:

Operational application to be started


Details per Observable: Intensity BCTF: Status


We’ll have 2 fast monitors per beam in the ring and 2 in the dump lines. One operational, the second as spare (not ‘hot’) in case of problems and specialist monitoring.

We’ll basically have 2 (+1) acquisitions: Capture: provides intensities of selected individual bunches (S)

over N consecutive turns. (S * N < 512K) The data-taking is started at reception of a dedicated central timing.

Standart: All individual bunch currents are averaged over 227 turns (20ms). This measurement is continuously repeated at 10Hz and published at 1Hz. Bunch and Beam lifetime will also be computed and transmitted.



Details per Observable: Intensity. BCTF: Remaining Issues

HW Calibration with Beam No automatic arbitration between the 2

redundant monitors for the start-up Development and Commissioning of the dI/dt

monitoring: to be done – BI agreed on the objective to have a prototype ready for Summer 2008.

Operational Applications: Operational application to be started Fixed displays definition and ad-hoc



Details per Observable: Intensity BSRA abort gap: Status


We’ll basically have 1 acquisition: Standart: The intensity values will be acquired at

10 Hz. ~ 30 intensity values will cover the abort gap period. The DAB card will cumulate these intensities over a pre-defined number of turns (ex: 1000). The acquisition result will thus be an array of 30 average intensities, which sum will represent the intensity in the gap



Details per Observable: Intensity. BSRA abort gap : Remaining Issues

HW Calibration with Beam This is just a monitoring. No action will

be triggered from the Front End computer itself.

Operational Application: Operational application to be started


Details per Observable: Intensity via BPM: Status


We’ll use the acquisition channel of beam 2 to read intensity of beam 1 (and vice versa), i.e. we lose beam position on the other beam


Details per Observable: Intensity. Via BPM : Remaining Issues

HW Commissioning with beam if and when

necessary (i.e. unexplained obstruction somewhere in the machine).

Operational applications This will remain an expert intervention.

No operational application is foreseen for this.


Details per Observable: Q & Q’ via BBQ: Status


We’ll basically start with single kick method and 1 acquisition we will return the raw data, the FFT and basic

peak detection for each measurement these acquisitions will be triggered by a central

timing event also triggering the selected kicker (tune kicker or damper).

PLL continuous measurement and RT monitoring will come later (will require a few MDs)


Details per Observable: Q & Q’. Via BBQ : Remaining Issues

HW Kicker selection (Tune Kicker or Damper)

and triggering?. (under discussion in ABCIS)

PLL commissioning (HW and FE SW will be ready but will need MD time)

Feed back loop and commissioning (will be based on BPM orbit feed-back infrastructure)



Details per Observable: Q & Q’ via Head Tail: Status

Monitors, scope and front end software will be ready for the start-up

We’ll start with a scope and basic FESA class transmitting the raw data like in the SPS.

We plan to use the exiting expert application to assess this system

No operational application is foreseen for the start-up.


Details per Observable: Q & Q’ via Schottky monitors: Status

Monitors marked for phase II but ready and installed. We’ll use the same electronics and front end software than for the BBQ system

This is not a priority. The corresponding operational application will be developed if time allows.


Details per Observable: Luminosity BRANA & BRANB: Status

Monitors will be ready for the start-up. 4 BRANA (left and right IP 1 and 5) developed by

Berkeley 4 BRANB (left and right IP 2 and 8) developed by

AB/BI] AB/BI electronics and front end software will be ready

for the start-up. So should be Berkely.

We’ll basically have 2 acquisitions per IP: Total relative luminosity at 1 Hz: this quantity is

proportional in an unknown but constant way to the actual luminosity; the proportionality constant may differ from IP to IP.

Bunch by bunch relative luminosity at 0.1 Hz:


Details per Observable: Luminosity BRANA & BRANB: Remaining Issues

HW Commissioning with Beam Signal level and quality.



Conclusions


A word on a hypothetic sector test

The new enlarged BPM (BPMWI) will be available soon.

We still have to HW commission the LSS8 BTV Get missing Ethernet connections in UJ76

We would install an ad-hoc system (not the final one) to measure intensity from the BPM close to the end.

So we could be ready if necessary.


Conclusions Except for the BGI on beam 2 (destroyed during bad

bake-out), our instruments will be available on time. The targeted performances (in terms of accuracy and

resolution) of these instruments are the one described in the LHC beam instrumentation functional specifications.

But we will need a lot of MD time with stable beam conditions to commission our instruments and reach this performance.

We will discuss and document these commissioning procedures during the coming months and come back to you to fit the result in ‘the 2 months for commissioning to 7TeV’

LHC Beam Instrumentation Readiness

Documents

Transcript of LHC Beam Instrumentation Readiness