5 may 98 1 jürgen knobloch computing planning for atlas atlas software week 5 may 1998 jürgen...

5 May 981 Jürgen Knobloch

Computing Planningfor ATLAS

ATLAS Software Week

5 May 1998

Jürgen Knobloch

Slides also on: http://nicewww.cern.ch/atlas/wwwslides/Plan980504/index.htm


ATLAS MoU - IntroductionThe ATLAS software will be developed in a defined process involving requirements, design and coding - each being reviewed for quality assurance. The ATLAS data will be stored in an object-oriented database. First estimates of the cost of the computing infrastructure necessary for data storage, reduction and analysis are also contained in the CTP. These costs are not included in the present MoU.

Final software planning including human resources andbetter understanding of computing model andthe role of regional centres --> during 1999


2 ye

ar m

ajor

cyc

le

8 w

ork

wee

k c

ycle

s

Software planning 1998 Initial version 0

– FORTRAN code further developed, interface to C++– Overall requirements formulated– Domain decomposition– Simulation and reconstruction framework

1999 - 2000 Version 1– Complete detector description in GEANT4, ODBMS

2001 - 2002 Version 2– Full functionality of OO software

2003 - 2004 Version 3 - Integration, performance 2005 Production version 4


Software Quality Functionality

– Experience, requirements, software process

Ease of entry for physicists– Documentation, clear architecture

Maintainability– Documentation, software process

Flexibility– changing environment, new requirements

Robustness Performance

– Few O(0) re-processings, CPU, memory, I/O


Current situation Last major release of FORTRAN simulation Still work on FORTRAN reconstruction First release of OO reconstruction imminent Simulation with GEANT4 - prototypes exist Difficult to get started Software process taken seriously Software release tools being implemented Platform/compiler/commercial_software

– few combinations work


Offline Software Plan1998 1999 2000 2001 2002 2003 2004 2005

FORTRAN simulation GEANT4 simulation ATLAS GEANT4 prototype Test beam simulations Detector description database FORTRAN reconstruction Object-Oriented Reconstruction ARVE Event display Event data in OO database Decide on database vendor Analysis environment

Ramp down: Ramp up: Development, maintenance, support Prototyping

No development, limited maintenance Development, users

Kept available “as is” Released


MilestonesA detailed list of milestones has been defined in the Computing Technical Proposal. In the following, the major milestones are summarised:

OO- Reconstruction framework April 1998Demonstrate ~1 Tbyte working prototype of event database December 1998 First release of ATLAS OO software End 1999Functional software for simulation, reconstruction and analysis End 20011% prototype of event-processing farm December 2002100% event database (disk + robots, not necessarily all tapes) December 2004Provide ~40% of final event processing and analysis farms

December 2004Provide full event processing and analysis farm April 2005


Software workshops– 1 week, 4 times / year, 1 CERN

ACOS (Computing steering group)– 6 meetings / year (4 during software workshops)

DIG (Domain interface group and support team)– 8 meetings / year (4 during software workshops)

Weekly software meetings– Videoconferenced– Tutorial session about OO issues

Working groups: database, graphics, WWCG, ...

Organisational items


TriggerTrigger

Domain Decomposition

GUIGUI

ControlControl

EventDisplayEvent

Display

MuonSystemMuon

System

MagneticField

MagneticField

CalorimetryCalorimetry

DetectorDescription

DetectorDescription

InnerDetector

InnerDetector

DataBaseDataBase

SimulationSimulation

EventEvent

GeometryGeometry

ToolsTools

SDESDE

DocumentationDocumentation

MuonReconst.Muon

Reconst.

e,e,

ReconstructionReconstruction

Organisation:

Domain architects

Domain interface group

Support team


Planning in terms of deliverables

Medium term (this year) Reconstruction framework

– Based on ARVE– “Ramped-up” to conform to the ATLAS software process– Event reading from ZEBRA tapes– Reconstruction algorithms

> IPATREC> MUON (DATCHA) reconstruction

First public version in “April” Many things to follow…

– Calorimeter prototype, full detector hierarchy, interface to GEANT4, reading from Object Database


How to go from here to there...

FORTRAN

FORTRANand C++

C++

CA

LO

RE

C

IPA

TR

EC

AB

CR

EC

MU

ON

BO

X

ATRECON

DICE 3

GEANT 3 GEANT 4

CA

LO

RE

C+

+

IPA

TR

EC

AB

CR

EC

MU

ON

BO

XATRECON

CA

LO

RE

C+

+

IPA

TR

EC

++

ARVE

Event DB

Detector DB


GEANT4 - ATLAS participation and implementation Test beam simulation and analysis ARVE - ATLAS Reconstruction and Visualisation

Environment Object-oriented pattern recognition TRT, IpatRec Muon reconstruction ODBMS (RD45) ATLAS participation

– Event storage GEANT3, GEANT4, test-beam– Detector database

LHC++ - ATLAS participation - Porting ATLFAST++ to Objectivity

Current OO projects


ATLAS and GEANT4

10 + (1 -> 6 GeV)

TGC for trigger studies


GEANT4 plans Alpha-05 is comparable to

GEANT3– Physics, tracking, geometry,

event persistency

Next steps– Produce beta version– Persistency for geometry– More visualization– Documentation– Extend physics models

Next steps for ATLAS– Detailed field map– produce HITs– detector parameters into DB– Full ATLAS geometry– Test beam geometries– Simulation mock-up– Get more detector people into

ATLAS working group


Database developments Detector database

– Muon geometry description existing in Objectivity– Understand best structure -> other detectors can follow– Possible common project on detector description db

Event storage database– GEANT3 data in Objectivity (Summer 98)– ATLAS testbeam– Event structure to be developed– Replication via network or via “tapes”???

Other experiments– NA45, Compass, BaBar, Star,... - Learn from experience


Next Tasks Reconstruction - ARVE

– Documentation– Read events from OODB– G3 events to objy– Event display– Magnetic field– Integrate more algorithms– Single particle from GEANT4– Components– User support

Simulation– Create ATLAS GEANT4 team– Detector description DB– Build ATLAS G4 Framework– Test beam simulations

General– Populate domains– Make ASP “user friendly”– Establish detailed plan– Analysis strategy- try LHC++– Regional centres


Conclusions of LCB workshop... Common vocabulary/glossary Consensus on need for more sharing

– e.g. detector description database tools

Technical forums on specific items– e.g. LHC++, RD45,...

Risk analysis Learning from experience

– Provide OO examples, tutorials, seminars


ATLAS Computing Model

RD45

RegionalCentres

HPSS

Networks

Media

Simulation

DataStructure

Cost

Manpower

Licenses

Companies

RiskAnalysis

Sharing

Architecture

Requirements

Technology

Flexibility

CollaborativeTools

SoftwareProcess


Operating Systems Current (FORTRAN)

– HP-UX 10.20– AIX– Digital UNIX– LINUX– NT– IRIX (SGI)– Solaris

FUTURE– (HP-UX 10.20) - not 11.xx!

> as long as old hardware exists

– LINUX> RedHat 4.2 --> 5.0

– NT 4.0

If supported by ATLAS institutes:– Digital UNIX– AIX– Solaris

5 may 98 1 jürgen knobloch computing planning for atlas atlas software week 5 may 1998 jürgen...

Documents