# Presentation: 506533

## Introduction

- Release schedule
- Main deliverables for release 14
- FDR-2

## Releases

- 13.0.40 very soon, collect all corrections from 13.0.30.X + what is needed for FDR-1
- Currently validating 13.0.30 simulation
- CSC data (rel 12 simulation) being reconstructed with 13.0.30
- 13.0.35 for M5 reprocessing
- 13.1.0 last week, intermediate release towards release 14
- Release 14 (early 2008) could be the one used for the first data taking

## Deliverables for release 14

- Main emphasis is readiness for first data, all required infrastructure, improvement on CPU and memory usage

## Infrastructure / Calibration
Bad channel database (cf talk by Teddy this morning)
Then should be used at various steps (HLT, reconstruction, simulation)
Cleaning up HV tools and interfaces
What to do at cell level is ~ understood but should clarify where it is done and how to keep track of what has been done
Cf talk by Joe
Production of electronics calibration constants
Cf talk by Fabien on automatic processing Monday
Tools for data quality of calibration constants 
Complete missing database structure
For instance store measured noise in MeV from randoms, etc...
A lot of technical work on T/P split for conditions data, jobOptions, etc..

- Bad channel database (cf talk by Teddy this morning)
- Then should be used at various steps (HLT, reconstruction, simulation)
- Cleaning up HV tools and interfaces
- What to do at cell level is ~ understood but should clarify where it is done and how to keep track of what has been done
- Cf talk by Joe
- Production of electronics calibration constants
- Cf talk by Fabien on automatic processing Monday
- Tools for data quality of calibration constants
- Complete missing database structure
- For instance store measured noise in MeV from randoms, etc...
- A lot of technical work on T/P split for conditions data, jobOptions, etc..

## Robustness/consolidation 
Improve memory/CPU usage
Commissioning reconstruction with 32 samples + random phase is more challenging than “typical” Atlas reconstruction
Double vs float usage in reconstruction
Complete configurable migration
jobOptions better controlled
Merging “commissioning” and “Atlas MC reconstruction” configuration to prepare first reconstruction of collisions data
Also applies to trigger software

- Improve memory/CPU usage
- Commissioning reconstruction with 32 samples + random phase is more challenging than “typical” Atlas reconstruction
- Double vs float usage in reconstruction
- Complete configurable migration
- jobOptions better controlled
- Merging “commissioning” and “Atlas MC reconstruction” configuration to prepare first reconstruction of collisions data
- Also applies to trigger software

## Corrections for first data
With release 14 simulation
Calibration hits method for EM calibration
Detector description
“final” ID description (note that the amount of material has significantly changed compared to release 12 nominal geometry)
Description of dead material in barrel-endcap crack (cf talk by Moustapha)
Improvement in end-cap geometry description (cf talk by Magret)
G4 simulation
Define “best” G4 version / physics list /range cut for the full simulation
(frozen showers, Atlfast-2 on the simulation side for physics events => a lot of work for validation / improvement)

- With release 14 simulation
- Calibration hits method for EM calibration
- Detector description
- “final” ID description (note that the amount of material has significantly changed compared to release 12 nominal geometry)
- Description of dead material in barrel-endcap crack (cf talk by Moustapha)
- Improvement in end-cap geometry description (cf talk by Magret)
- G4 simulation
- Define “best” G4 version / physics list /range cut for the full simulation
- (frozen showers, Atlfast-2 on the simulation side for physics events => a lot of work for validation / improvement)

## FDR-2

- Try to “emulate” LAr calibration physics stream (5 samples from single electron).
- Produce MC samples with ADC data for cells above threshold
- Exercise calibration algorithms that could run “easily” on express stream
- Pedestal shift, Noise in MeV, autocorrelation from random events
- Exercise more refined in-situ calibration algorithms (maybe outside FDR-2)
- Z->ee intercalibration from AOD
- Position alignment ?
- In real life, will take some time to analyse together with many other things before understanding all effects (upstream material vs intercalibration, etc...)