24/06/03 atlas weekalexandre solodkov1 status of tilecal software

24/06/03 ATLAS Week Alexandre Solodkov 1

Alexandre SolodkovAlexandre Solodkov

Status of TileCal Status of TileCal

softwaresoftware


ATLAS offline softwareATLAS offline software

ATLAS offline software is organized in hierarchical ATLAS offline software is organized in hierarchical structure in ATLAS offline CVS repositorystructure in ATLAS offline CVS repository

There are 3 kind of packagesThere are 3 kind of packages Core packages like Database, Detector Description Non-core common packages like Simulation, Reconstruction Sub-system packages, like InnerDetector, TileCalorimeter

All top level packages are split in subpackages, All top level packages are split in subpackages, (TileCalorimeter package has ~20 subpackages)(TileCalorimeter package has ~20 subpackages)

Every sub package has a number of C++ source files, Every sub package has a number of C++ source files, which contain algorithms, services, converters, etc.which contain algorithms, services, converters, etc.

During build procedure every package makes one or During build procedure every package makes one or more shared librariesmore shared libraries

All the software is running in Athena framework, the All the software is running in Athena framework, the sequence of algorithms to run is set via jobOptions filesequence of algorithms to run is set via jobOptions file


ATLAS Tag CollectorATLAS Tag Collector


Software development Software development processprocess

Every package in offline repository has a coordinatorEvery package in offline repository has a coordinator From time to time coordinator decides to produce new From time to time coordinator decides to produce new

tag for the package (i.e. mark all files in the package tag for the package (i.e. mark all files in the package with special tag, like TileDetDescr-00-02-05) and put with special tag, like TileDetDescr-00-02-05) and put this tag in the Tag Collectorthis tag in the Tag Collector

Every night all packages listed in the Tag Collector are Every night all packages listed in the Tag Collector are checked out from CVS repository and nightly build is checked out from CVS repository and nightly build is producedproduced

build starts at 21:00 Geneva time It takes about 12 hours to build all ~600 packages

In the morning developers can see results of the build In the morning developers can see results of the build on the web and test new software in Athenaon the web and test new software in Athena

All the dependencies are clearly visible (if change in one package breaks build of another package)

7 last night builds are kept on the disk for tests


Nightly builds web pageNightly builds web page


Releases of ATLAS softwareReleases of ATLAS software

Every 3 weeks new release of ATLAS software is madeEvery 3 weeks new release of ATLAS software is made Last week release 6.3.0 was built

Although developers are trying to provide tested code for Although developers are trying to provide tested code for such a release, still some bugs are usually discovered such a release, still some bugs are usually discovered here and therehere and there

Special “Releases status” web page contains up to date information about all the releases

Every half a year a major release is producedEvery half a year a major release is produced Deadline for release 7.0.0 is 31th of July

If bugs are found in major release, the bug-fix release is If bugs are found in major release, the bug-fix release is made rapidlymade rapidly

Only last digit changed, e.g. release 7.0.1 Such a major (bug-fixed) release is distributed all over Such a major (bug-fixed) release is distributed all over

the world and it is used for simulation and reconstruction the world and it is used for simulation and reconstruction of big data samples (Data Challenges)of big data samples (Data Challenges)


TileCal Software developersTileCal Software developers

Software development in TileCal is done in 3 areas Software development in TileCal is done in 3 areas and is coordinated by 3 peopleand is coordinated by 3 people

Simulation and Detector Description (Vakhtang Tsulaia, JINR)

Reconstruction and Event Data Model (Frank Merritt, Chicago University)

Conditions database and database services (Tom LeCompte, ANL)

Members of TileCal collaboration are also Members of TileCal collaboration are also developers of the offline software outside developers of the offline software outside TileCalorimeter packageTileCalorimeter package

Jet finding in Reconstruction package (Ambreesh Gupta, Chicago University)

New people are coming this year: New people are coming this year: Adam Aurisano (Chicago), Gia Khoriauli (JINR), Karl Gellerstedt (Stokholm)


TileCal simulationTileCal simulation

Since long time we provided code for GEANT3 Since long time we provided code for GEANT3 simulation of TileCal (both testbeam and full ATLAS)simulation of TileCal (both testbeam and full ATLAS)

2 years ago we started to simulate our testbeam 2 years ago we started to simulate our testbeam setup with Geant4 (standalone program)setup with Geant4 (standalone program)

Now we are able to run Geant4 simulation in Now we are able to run Geant4 simulation in standalone mode and inside Athena, for all testbeam standalone mode and inside Athena, for all testbeam setups and for TileCal in ATLASsetups and for TileCal in ATLAS

Still need to persistfy Geant4 hits (only ntuple-based Still need to persistfy Geant4 hits (only ntuple-based persistency is available right now)persistency is available right now)

Will be done for release 7.0.0 There will be no difference between Geant3 and

Geant4 for reconstruction


TileCal G4 simulationTileCal G4 simulation

TileCal in ATLAS Testbeam setup


TileCal Detector DescriptionTileCal Detector Description

ATLAS Detector Description will be a unique source ATLAS Detector Description will be a unique source of information for simulation, reconstruction abd of information for simulation, reconstruction abd analysis stagesanalysis stages

ATLAS Detector Description uses NOVA database ATLAS Detector Description uses NOVA database (MySQL) to store all primary numbers(MySQL) to store all primary numbers

Since release 6.2.0 TileCal has interface to NOVA Since release 6.2.0 TileCal has interface to NOVA from Geant3 and Geant4; both simulations use from Geant3 and Geant4; both simulations use exactly the same numbersexactly the same numbers

The work on the so-called GeoModel is going onThe work on the so-called GeoModel is going on GeoModel builds detector tree similar to Geant4 tree This tree is available not only at simulation, but also ate the

reconstruction stage, i.e. reconstruction will use the same geometry as simulation

First prototype will be available in release 7.0.0, the work will be mostly finished in release 8.0.0


TileCal ReconstructionTileCal Reconstruction

Tile Data Objects Tile Algorithms

TileHit(signal seen by PMT)

TileDigits(25-ns time slices)

TileRawChannel(after optimal filtering)

TileCell(calibrated cell energy)

TileHitToDigits

TileDigitToRawChannel

TileRawChannelToCell

TileDigitsByteStream

RawChannelByteStream


TileCal ReconstructionTileCal Reconstruction

We have all the algorithms to go through full We have all the algorithms to go through full reconstruction chainreconstruction chain

We are able to generate noise, simulate signal We are able to generate noise, simulate signal shape, apply optimal filteringshape, apply optimal filtering

Noise is in the release since 5.3.0 Optimal filtering is in the release since 6.1.0 (code is

taken from Richard Teuscher) We are able to write ByteStream file with energy, We are able to write ByteStream file with energy,

time, time, 2 (output of the ROD) and read it back2 (output of the ROD) and read it back In the release since 4.6.0 Used by HLT group to study Trigger performance

We have code for TileCal Level 1 Trigger Towers We have code for TileCal Level 1 Trigger Towers simulationsimulation

Need to simulate Level 1 muon trigger (good task for the beginner!)


TileCal Reconstruction plansTileCal Reconstruction plans

In nearest future we are going to provide code for In nearest future we are going to provide code for pileup generation using Athena pileup servicepileup generation using Athena pileup service

We will extend our optimal filtering code to deal with We will extend our optimal filtering code to deal with out-of-time signalsout-of-time signals

We will continue to work on improvement of all our We will continue to work on improvement of all our algorithms, will take into account recommendations of algorithms, will take into account recommendations of RTFRTF

Separation of event and non-event (DetDescr) data Implementation of all corrections (calibrations) as

AlgTools, i.e. outside reconstruction algorithms, for easier replacement

First AlgTool was written by Gia Khoriauli just in 2 weeks! New hadronic energy calibration (with LAr)


TileCal IdentifiersTileCal Identifiers

Identifier is a special object for identification of every Identifier is a special object for identification of every sensitive element of ATLAS detectorsensitive element of ATLAS detector

There are 2 kind of IdentifiersThere are 2 kind of Identifiers Offline identifier in TileCal describes position of cell in (,,r) space Online identifier (hardware identifier) in TileCal describes one readout

channel: (drawer#,channel#) We are using offline identifiers for Geant hits and We are using offline identifiers for Geant hits and

CaloCells and online identifiers for our Digits and CaloCells and online identifiers for our Digits and RawChannelsRawChannels

For the moment all numbers for Tile Identifier are kept For the moment all numbers for Tile Identifier are kept inside C++ code, migration to Data Dictionary (i.e. external inside C++ code, migration to Data Dictionary (i.e. external XML file with all numbers) will be done for release 7.0.0XML file with all numbers) will be done for release 7.0.0

There is a new proposal now to provide identifiers to all There is a new proposal now to provide identifiers to all passive materials in ATLAS with 0.1 granularity in (passive materials in ATLAS with 0.1 granularity in (,,) ) space (can be implemented around release 7.5.0)space (can be implemented around release 7.5.0)

Energy deposits in passive material will use this identifier This will be used for fine-tuning of hadronic calibration algorithms


Testbeam analysis in AthenaTestbeam analysis in Athena

We almost at the point when we can read testbeam We almost at the point when we can read testbeam data in Athenadata in Athena

The ByteStream package in Athena needs to be The ByteStream package in Athena needs to be modified slightlymodified slightly

Will be done by expert (Hong Ma) soon

After that it’s TileCal responsibility to unpack After that it’s TileCal responsibility to unpack “digits” and to apply optimal filtering properly“digits” and to apply optimal filtering properly

Need to merge TileNtuple unpacking with ByteStream unpacking in Athena

Work will start in august by Karl Gellerstedt

Also need to provide interface to testbeam Also need to provide interface to testbeam calibration database in Athenacalibration database in Athena


TileCal DatabaseTileCal Database

Do not have too much in Athena nowDo not have too much in Athena now Waited for common ATLAS approach to Conditions database

We are reading ASCII files for the moment We are reading ASCII files for the moment Want to try new “Interval of Validity” service Want to try new “Interval of Validity” service

(IOVSvc) available in release 6.3.0 and to (IOVSvc) available in release 6.3.0 and to store/retrieve our conditions data (calibrations store/retrieve our conditions data (calibrations constants)constants)

After we understand how IOVSvc works, we might After we understand how IOVSvc works, we might use it for all our calibration constants, including use it for all our calibration constants, including constants for testbeam analysisconstants for testbeam analysis


ConclusionsConclusions

TileCal software development, although TileCal software development, although understaffed, is going not too bad understaffed, is going not too bad

In some areas we are quite advanced thanks to In some areas we are quite advanced thanks to efforts of our simulation / reconstruction / efforts of our simulation / reconstruction / database coordinatorsdatabase coordinators

The software development in Athena framework The software development in Athena framework is now at the stage when even non-experts can is now at the stage when even non-experts can do something do something

Many results already achieved …Many results already achieved … … … but still a lot of work to be done!but still a lot of work to be done!

24/06/03 atlas weekalexandre solodkov1 status of tilecal software

Documents

major release

new software

package breaks

new tag

bugfix release

major bugfixed release

madelast week release

offline repository