CERN-RRB-2009-101Marzio Nessi

CERN, 12th October 2009

ATLAS detector status (I)

1

Detector opening and closing

3 alternated periods of global cosmics runs-Oct-Nov ’08-Jun-Jul ’09-Oct-Nov ’09

All possible interventions on the detectors and infrastructure

Installation of new components for high Lumi

2

Shutdown activities summary

Opening has started in November 2008, closing has started in June 2009. All activities analyzed for ALARA compatibility (minimize radiation dose to people).

Large amount of infrastructure consolidation (electricity distribution, ventilation, safety, gas and fluid distribution, detector cooling system, vacuum system, cryogenics, magnet controls, bus-bars, …. ). Where possible, single point of failure identified and solved. Many control issues clarified and solved. The ID compressor plant has been fully mechanically retrofitted in order minimize aging due to fatigue. The distribution racks have been fully upgraded with new valves and pressure sensors.

All possible yearly maintenance done to be ready for a long 2010 run (cooling towers, cryogenics,..)

All possible active detector interventions to fix bugs, to anticipate future problems, to consolidate and to operate the subsystem. Enough to learn about all possible operation details

Work in UX15 organized via WPs which have been all analyzed and treated (~400 up to now). ~15 still active (mostly white lists for regular interventions)

RP infrastructure and methods used through the entire periods (traceability + RP measurements)

3

Summary of Atlas opening at the end of 2008

Opening of the 2 shafts + movement system installation + activate cranes : 1 week

On side A, opening went in good agreement with the plan : Foreseen duration : 19 days of workActual duration : 25 days of work (2 days off+3 days extra activities+1 day delay)

On side A, opening went in good agreement with the plan : Foreseen duration : 19 days of workActual duration : 25 days of work (2 days off+3 days extra activities+1 day delay)

On side C, opening went fine too : Foreseen duration : 19 days of workActual duration : 18 days of work, all sub-systems moved

On side C, opening went fine too : Foreseen duration : 19 days of workActual duration : 18 days of work, all sub-systems moved

All together 8.5 weeks

But the octagonal shielding had not been installed in 2008, it took about 3 weeks for the recent installation, including TAS alignment

4

Side ASide C Side ASide C

Atlas standard opening : optimization

The best estimate is to open fully the experiment in 7 to 8 weeks, this requires :To work in parallel (both sides) -> duplication of the movement system is planned for 2010To improve the access to the fixed points of the vacuum pipe

5

6

ATLAS caverns protection campaign

ATLAS caverns have been protected against accidental He release in the LHC machine.

All interfaces between the caverns and the tunnel have been redesigned and sealed according to the recommendations of the CERN task force on safety of Personnel in the LHC underground areas, following the 19th Sept. 2008 accident.

Survey gallery doors and wall Survey gallery servicesTAS region

Specific detector activities Refurbishing and retrofitting of the ID evaporative plan ( compressors +

distribution)

Retrofitting of a good fraction of the Calorimeters LVPSs LAr has dismounted, retrofitted and re-installed part of the front end boards Tiles has removed, fixed and reinstalled 30% of the 256 electronics drawers

ID has done some fixing of cooling loops, gas leaks, control electronics on the endplate of the barrel calorimeter. Pixel and SCT have installed new off-detector opto-transmitter plugs-in and have collected weeks of running with cooling on

TRT has done the first run with Xenon and CO2 cooling

Muon has fixed or replaced a few broken chambers (TGC, MDT). Many gas leaks have been found and fixed. On-chamber electronics boards (CSM) retrofitted. RPC has extended its coverage (electronics commissioning). The non rad-hard optical fibers in the MDT wheels have been exchanged. New (staged) chambers partially installed (EE). A lot more of operation experience collected

LUCID has fixed several gas problems, has installed in a more accessible place the front-end electronics and has understood possible B-field effects 7

Various activities

MDT fibers

New evaporative tank

EE chambers

Evaporative plant compressors

Distribution racks

8

Detectors status

9

Today’s status

All shielding elements installed, including for the first time the Octagonal shieldings

Big Wheels closed, in running position, with final gas filling Shaft closed, detector cleaned, access changed to restricted ready for

beam TAS collimator aligned, beam pipe on vacuum

Ready for the next global cosmics run (from 12 October to beam) In the mean time each system was tested individually

Control room manned with SLIMOS (2 shifts) since ~1.5 year, 365d/7d From 12 October control room fully manned : 3 shifts x 15 desks, 7d/24h Ongoing: pressure and CO2 final tests in UX15

Restoring temperature in the spectrometer aiming for a max temperature of 24C

Final tuning of the beam interlock system (beam injection permit, abort, ..)

10

Today’s major worries

LAr OTX : additional failure of the light emitting component (VCSEL) on optical transmitters (now ~1% level), backup solution under development

Keep the evaporative cooling plant operational (proximity compressor plant). A completely new plant is being R&D, it might be available for 2011

SCT heater pads failure (3 in the barrel) …. Prevent further from happening … 2010 strategy is in place, longer terms actions under evaluation

Follow up evolution of LVPS in the calorimeters (new devices or fixing in 2011) Follow up evolution of power supplies failures in the muon spectrometer Follow up evolution of fragile gas inlets (RPCs) Get acceptable temperature distribution for RPCs and TGCs (opposite

requirements) Get CSC ROD system to work at 75KHz data collection, 2010 plan under

evaluation

For more details see recent ATLAS Week reports

11

Worries

12

LAr Front-End-Board opto-transmitter plug-ins (OTx):

10 died last year replaced during shut-down 17 more failed since (~1.2% of EM channels): cannot be replaced without opening ATLAS reason not fully clear, correlation seen between bad VCSEL and shape of light spectrum back-up solutions being prepared (50

carefully-fabricated OTx, double- VCSEL layout)

CSC ROD:

lot of progress recently, after fixes/improvements to DSP software and FPGA firmware stability issues resolved. 1.5M cosmics events recorded in August rate capability at a few kHz. > 40 kHz estimated for firmware/code for first collisions further improvements expected to meet ATLAS-wide design spec of 75 kHz LVL1-trigger rate, full assessment after 40 kHz goal reached (Oct-Nov) UCI, SLAC experts joined in August 2008

Evaporative cooling performance (C3F8)

Filling of 100 kg

Smoke Alarm: DSS stopped Cooling System

the problem on End-cap Side C (35 loops stopped for the intervention)

Leak rate = 1.2 kg/day

Tank filling rate

# loops active

The M&O of this plant remains a major issue on the medium/short term

13

PR

thermalscreen

others

4 liquid lines

4 gas lines

condenser

liquidtank

pneumaticvalve

manualvalve

manualvalve

dummyload

Heater

BPR

pixel

6 X SCT

manualvalve

pneumaticvalve

Low temperatureChiller

UX15 USA15

A gravity driven circulation cooling system (thermosiphon) could be a solution to obtain:

• Reliability: no active component in the system• Cleanliness: no wear of components• Leaks: reduction of connection points and no

vibrations

14

ATLAS Run Schedule (next 3 months)

Final High Level Trigger

* 50kHz run with all sub-systems* High PT muon trigger* Inclusive barrel / endcap muon trigger* First beam trigger menu* Alignment studies (with different B field configs)* Trigger timing* Express stream* Data quality, physics monitoring* LHC dry run, beam protection* Stopless recovery & stability* Access management* ...

No Beam* Timing with single beam and splashes* Timing with collisions* First beam menu* Phase in of HLT, physics streaming* Validation of beam protection* Beam conditions, collision point monitoring* Luminosity monitoring* Luminosity scans* Data quality: physics objects* Reduce dead time, readout windows

First Beams / Collisions

15

Optimizing data taking efficiency

Good start! …. But we started analyzing our ~20-25% lost of efficiency

Good start! …. But we started analyzing our ~20-25% lost of efficiency

Miss the beginning of the fill ~13% efficiency loss, start late or stop too soon … will be solved!Infrastructure ,~4% efficiency loss, fileservers, power cuts/glitches affecting ATLAS but not LHC, network, database access, cooling, …..Run stopped in the middle of the fill, ~2% efficiency loss 16

What is next on the detector side !

The detector is ready for a long run in 2009/2010

We started collecting information/reasoning on hardware activities necessary to face the next 5 years, including readiness for LHC phase I upgrade scenarios (L=3*1034)

For phase I upgrade a first project is running and getting organized (TDR, MOU,…) : the insertable pixel b-layer (IBL)

Going to sLHC is the next big challenge and the collaboration is very active with R&Ds, first prototypes and making plans (LOI, interim MOU for the initial phase, … )

17

Luminosity road map in 2 phases (2008 CERN Man.)

sLHC

LHC

18

Hardware plans for the period 2010-2015 (beginning of phase 1)

We started collecting the hardware plans of the various systems and subsystems (first iteration bottom up) for the next 5 years

known bug fixing (optical links, LVPSs, ….) a plan for 2010 consolidation (items which we know we will need,…) a plan of medium term consolidation (id cooling, magnet MRcompressor, ….) a plan for spares annual replacement of computers, network, monitors, … (not just TDAQ) a plan for reaching nominal L (RP issues, consolidation of infrastructure, …) un-staging of some detectors or components new projects for 3 1034 (IBL, new shielding, more processing power, muon

forward?, warm calo forward?, LVL2 trigger processor?, …..

Next step is to internal review and prioritize the list and understand the resources status. A progress report will be presented in the April

RRB

Two critical items (insertable pixel b-layer and upgrade of the evaporative cooling plant) have been presented to the LHCC for a first feedback … which we got and was positive …. and have been scrutinize by the RRB scrutiny group

19

IBL project (first step choose sensors technology)

IBL sensor developments coming from ATLAS R&D efforts – IBL defines specifications and requirements for the sensors: ATLAS 3D Sensor R&D Collaboration (16 Institutes and

4 processing facilities):Bergen, Bonn, CERN, Cosenza, Freiburg, Genova, Glasgow, Hawaii, LBNL, Manchester, New Mexico, Oslo, Prague, SLAC, Stony Brook, Udine - Processing Facilities: CNM Barcelona, FBK-IRST (Trento), SINTEF/Stanford.

ATLAS Planar Pixel Sensor (PPS) R&D Collaboration (17 Institutes)

Bonn, Berlin, CETN, DESY, Dortmund, MPP & HLL Munich, Udine, KEK, CNM Barcelona, Liverpool, LBNL, LPNHE, New Mexico, Orsay, Prague, Santa Cruz

ATLAS Diamond R&D Collaboration (6 Institutes, 2 vendors):

Bonn, Carleton, CERN, Ljubljana, Ohio State, Toronto

Bring the 3 sensor technologies to the IBL prototype phase module prototypes with FE-I4 (second half 2010) – limit

options (≤3 options/technology)- Stave prototype tested with modules and cooling- Target time to finish qualification: 2010, early 2011

20

The IBL project structure The IBL (Insertable B-Layer) is an ATLAS Upgrade project:

o It will deliver a fourth pixel layer, including a new beam-pipe, to the Inner Detectoro When delivered, it will become a part of the Pixel Detector and of the Inner Detector

and the organization will be “absorbed” into the Pixel & ID

The organization structure has:

o Giovanni Darbo as Project Leader and Heinz Pernegger as technical Coordinatoro Arranged project into four workpackages

o IBL Management Board to execute the projecto IBL Institute Board, currently an extension of the existing Pixel IB and chaired by C.

Goessling

Module WG

Module WG

IBL MB(Management Board)

IBL MB(Management Board)

StaveWG

StaveWG

I&IWGI&IWG

Off-detWG

Off-detWG

Pixel extended IB(Institute Board)

Pixel extended IB(Institute Board)

ATLAS UPGRADE

IBL

IBL PLIBL TC

ATLASUPO

ATLASUPO

New Institutesin IBL

New Institutesin IBL

Pixel Institutesin IBL

Pixel Institutesin IBL

21

IBL project start up

ATLAS Institutes Participation

IBL Kick-off July 8th with Institute’s Leaders Large interest (~35÷40 institutes) Project cost evaluated and funding model proposed: 4.0 MCHF M&O-A, 4.4 MCHF M&O-B,

1.2 MCHF new project money

Technical Design Report (TDR) by spring 2010

Main editor / technical editor and chapter editors in charge

Memorandum of Understanding foreseen in “interim” form by the end of 2009:

Eager to get interim-MoU by the end of 2009

Complicated process that involves technology dependent options, requires to enlarge the interest of focus to strongly cover the whole project and to resolve over/un covered items.

Much progress in the last 3 months: many people moving from intentions to real work – this is the best way to see how to contribute and for the IBL management to understand how well the project is covered.

MoU should be signed after the TDR (spring 2010)

22

IBL project

23

Phase II (sLHC plans)

R&D projects follow up and monitoring

Prototype work (ID staves,…)

Prototype work (ID staves,…)

writing LOI and channeling engineering

writing LOI and channeling engineering

Follow up LHC machine plan (define environment)Follow up LHC machine

plan (define environment)

Prepare future organization and MOU

Prepare future organization and MOU

Upgrade Steering Groupand

Upgrade Project Office

24

Organisation and schedule ATLAS Phase-II Upgrade

LoI May 2010 Send to LHCC

TP 2012 Expect ATLAS Upgrade for sLHC approval based on this Date should be chosen when the sLHC schedule is better understood

TDR's when ready with technical choices; ID in 2013 if 2020 data taking

Status of LoI: Main editor and technical editor operational; editors also in place. Most recent version is available at https://edms.cern.ch/document/1020649/1 Many chapters have substantial content: ~50 pages written (target is ~150) First reasonably complete draft scheduled for end November

25

LoI Schedule

30-06-2009 : Launch process, kick off meeting

01-09-2009 : Definition of the chapters substructure (index, sub-editors, list of possible open scenarios, internal chapters milestones), summary presented by the main editors

24-11-2009 : Release of the first draft of the various chapters

16-02-2010 : Release of the second draft

06-04-2010 : Release of complete LOI, ready for a general distribution for comments

25-05-2010 : Release of the final version, approved by the collaboration

31-05-2010 : Printing and submission to the LHCC

26

ATLAS at sLHC

Major improvements in the determination of Quartic Gauge Boson Couplings, which allows to check on anomalies in the SM predictions.

Need to be able to trigger on 20-30 GeV leptons

Better determination of Higgs couplings by availability of rates in channels not open at LHC (Z-photon, , etc), as well as determination of ratios of fermions-to-vectors at 10% level.

Again leptons and photons

b tagging

Good lateral contain of forward shower for V-V fusion

Measurements of Higgs self coupling by the observation of double Higgs production.

Again leptons and b’s

If no Higgs, clear possibility to observe high mass resonance's (up to 2TeV) in V(L)-V(L) scattering.

Again leptons and Missing E(T)

Need sharpened MUON LV1 triggers thresholds (and maybe combine with rough ID LV1 track trigger)

Need low thresholds for e-γ triggers, using more sophisticated algorithms, and also some rough ID LV1 track trigger for E/P cut

Keep as much as possible the Missing E(t) resolution, which means keep the rapidity coverage in calorimetry

Needs improved forward calorimeter with high granularity to survive the high rates, but also to tag forward jets in V-V fusion

Needs a full new ID to cope with the high occupancy, while providing a good b-tagging (pixel layers) and some LV1 tracking

Extra logic layer at LVL1 to allow for topological combinations and isolation cuts at; needs increased latency. Increase bandwidth

Physics requirements at sLHCPhysics requirements at sLHC Consequences for ATLAS at sLHCConsequences for ATLAS at sLHC

27

ATLAS @ sLHC

New ID tracker:

More Pixel layers for b-tagging

L1 track trigger to combine with Calorimeter for E/P cut in e id.

Engineering studies/optimization continue

Dedicated task force operational to assess performance and layout

Calorimetry:

Front end electronics re-design

Define which components will need more radiation hardness (HEC cold elect.?,…)

Better particle ID at L1 reading out all data

Possibly new very forward LAr calo, or alternative: new warm Tungsten/Diamond calorimeter in front of current FCAL

28

ATLAS @ sLHC

Muon spectrometer:

Add extra doublet with mm resolution

Replace SW chambers for high rate tracking and triggering. Many R&D projects ongoing

Replace very forward chambers for higher resolution and rate capabilities

New LVL1 Trigger:

New element in front of the Combined Trigger Processor for topological combinations of:

– ID LVL1 tracks with electron calorimeter clusters, match E/p.

– ID LVL1 tracks with MUON candidates with P matching.

– Isolation requirements from jets for lepton candidates

Add extra shielding for n

29

Summary

The ATLAS detector is ready for a long run in 2009/2010. As of today, the detector is closed and is in the global cosmics run phase, waiting for beam.

We made the best use of the 2009 shutdown. Detector operational at the 98-99% level. Some potential problems to be monitored. Solutions are being prepared.

We are organizing the work over the next 5 years, to prepare for LHC phase I. The first project, the IBL, has been set up and is making good progress. A TDR is expected in Spring 2009.

The detector community is very active in planning and preparing the work for a sLHC detector. The process is going through the preparation of a LOI, which will be presented in early summer 2010. The LOI should cover all possible upgrade activities, should link the present R&D activities to the project and define the type of organization we will need.

30