28/05/2008Muon Combined Performance Meeting 1 Muon Detector Description and Simulation status and plans summary of contributions from Laurent Chevalier, Andrea Dell’Acqua, Alexander Khodinov, J.Francois Laporte, S.Spagnolo, Dennis Wright

28/05/2008Muon Combined Performance Meeting 2 Outline Detector Description –Geometry tags from Atlas-CSC (Bulk of CSC production) to Atlas-CSC and Atlas-CSC the FDR 2 tags Alignment Constants as Condition data –MDT deformations Atlas-Geo –XML to GeoModel translation of Inert Materials –Performance issues: Robustness: clash cleanup Memory allocation

28/05/2008Muon Combined Performance Meeting 3 Geometry tags ascii Amdb content: –structured description of active materials: station definition, internal structure of station components, station positions, corrections to station positions –XML description of dead materials –old fashioned structured description of some inert materials content of a generic MuonSpectrometer tag under a generic ATLAS geometry tag (for example ATLAS-CSC ) –full ascii Amdb as Blob –tables for the structured description of active materials –tables for some dead matter components computed from the XML or the old fashion inert materials description in ascii Amdb –MuonIdentifiers table – linking to the Offline Id dictionary –Muon System envelop used by MuonGeoModel in simulation and reconstruction

28/05/2008Muon Combined Performance Meeting 4 Geometry tags ATLAS-CSC ATLAS-CSC ACTIVE components –Detector and dead matter components based on Technical Drawings of Layout R (amdb version R01) –Station positions account for Egg shape global deformation (P- lines) default station position ≠ nominal layout –Additional random displacements (~1mm) and tilts (~1mrad) of the chambers described as Static Alignment Corrections A-lines loaded init time from the same source of P-lines (geomDB, no CondDB) but applied as corrections (Delta Transforms) on top of the default position and orientation of the station –MuonGeoModel implementation fully driven by primary numbers in the DB (Oracle tables filled from ascii AMDB) ascii Amdb is also in Oracle as a blob –Good validation of active materials

28/05/2008Muon Combined Performance Meeting 5 Geometry tags ATLAS-CSC ATLAS-CSC INERT components –Barrel Toroid, Endcap Toroids, Atlas Feet, Shielding (disk, forward and toroid) all implemented from the dead matter tables –very limited validation –measurement of radiation length seen along the path of geantinos in GEANT 4 in comparison with the expectations from XML description of dead matter + active components in Amdc (transient model of Amdb) is integral check of consistency (marginal, heavy, statistically limited) results ~ ok (showed some problems, fixed) –Missing inert materials in MuonGeoModel and simulation: Calorimeter Saddle TGC supports Big wheel supports … …others, some not even implemented in Amdb

28/05/2008Muon Combined Performance Meeting 6 RPC layout in R03.01 As shown also from hit residuals studies with cosmic ray data, the RPC layout in the small sectors does not correspond to the nominal layout Changes involve displacement in the radial directions of ~ 5 cm for most stations in the small sectors, for all stations with a single RPC unit covering the MDT multilayer; All cutouts in RPC chambers has been revisited; Layout of RPC chambers between the barrel coil ribs has been revisited.

28/05/2008Muon Combined Performance Meeting 7 Geometry tags for FDR2 ATLAS-CSC ATLAS-CSC –Layout R: as in ATLAS-CSC –Station positioning as in nominal layout ATLAS-CSC ATLAS-CSC –like ATLAS-CSC but –Station positioning account for global deformation (Egg shape) in P- lines (default position) and no random misalignments in A-lines (delta corrections) global deformation and misalignment effects as in ATLAS-CSC ATLAS-CSC ATLAS-CSC May in FDR 2, 2 out of 5 runs will be reconstructed with ATLAS-CSC with ATLAS-CSC simulated alignment data will be written in the cond DB (runtime during the FDR2 or later) for subsequent test of the IoV dependent correction of the geometry model – correcting perfectly and/or within ~100microns no muon data in Condition DB tags

28/05/2008Muon Combined Performance Meeting 8 MuonGeoModel uses a MuonAlignmentTool for accessing the condition DB (COOL) and unpacking the alignment data blob into A-lines parameters Access to the DB is driven by the IoV service via the Align method of MuonGeoModelTool (full standard GeoModel schema) At IoV transitions the alignment constants are loaded and stored in the Detector Store delta transforms (MuonGeoModel specific) are computed from A-lines applied  the whole cache (GeoModel specific) + Tracking related (surfaces, transforms, etc) is cleared for all stations with updated constants System tested in reconstruction ~1 year ago with old COOL versions and run/event based IoV definition Agreed definition and of B-lines for MDT deformations in place – waiting for testing Handling of Alignment Constants as condition data

28/05/2008Muon Combined Performance Meeting 9 Geometry tags MuonSpetrometer-R02.03 –Amdb version R02 –few fixes of active geometry: HV-RO side of some MDTs inverted internal structure (strip pitch/number) for some RPC fix position of a few chambers –CSC chambers installed are layer 2 not 1 (like in old description) –major upgrade of XML dead matter description TGC support / BOL support/ ID patch panel/ access platforms/ Feet struts/ Calorimeter Saddle not in MuonGeoModel MuonSpectrometer-R03.01 for ATLAS-GEO –Amdb version R03 –like R02 + major revision of RPC layout, following the station mounting conventions adopted in BB5 –delivered in ORACLE last Monday – needs extensive validation

28/05/2008Muon Combined Performance Meeting 10 Dead Matter in GeoModel/GEANT from XML Andrea Dell’Acqua developed a XML -> GeoModel parser for a transparent translation of Amdb dead matter in GeoModel –no more painful hand coding of the dead matter shape and positioning AGDD2Geo in (not active yet in any default configuration) Amdb blob (with XML dead matter) read from Oracle all components in Amdb are translated into GeoModel volumes, hence Geant4 volumes via Geo2G4 by job-option one can enable to built a selection; no changes needed for the moment in MuonGeoModel planning to start with MDT/TGC supports in the big wheels –if tests in simulation are OK add platforms, services at eta 0, calo saddle –presumably wait longer before replacing components already existing in MuonGeoModel

28/05/2008Muon Combined Performance Meeting 11 AGDD2Geo MDT supports

28/05/2008Muon Combined Performance Meeting 12 AGDD2Geo TGC supports

28/05/2008Muon Combined Performance Meeting 13 AGDD2Geo TO DO in material consistency checks: AGDD had extra materials with no correspondence in Oracle yet. geometry checks (mostly in simulation) check for unforeseen overlaps, for correct material distribution GEANT4 tracking performance maybe the most critical chapter (impact on simulation timing, memory) reconstruction checks make sure the whole chain from simulation to reconstruction works properly After these checks – we’ll freeze, as default, a configuration of default options for MuonGeoModel + AGDD2Geo to enable the tested components in simulation and reconstruction

28/05/2008Muon Combined Performance Meeting 14 Clash review – simulation robustness Dennis Wright working on a very carefull clash hunting and fixing fixes in –started from nominally aligned layouts, cured residual small active- active clashes due mostly to shared surfaces (introduced suitable tolerances on volume dimensions) –moved to misaligned layout: many clashes of tilted chamber corners (~100  m) cured by reshaping a tighter station envelop, by subtracting and adding half cylinder shapes to a minimal trapezoid event display becomes heavy solved by enabling(in MC)/disabling(in Reco) this fine clash fixing procedure by job option –simplified spacer beam description + fixes –fix BOG cutouts –attaching active-inert clashes fixed feet description to fix a clash with BOG chambers more to do … especially on still un-implemented cutouts

28/05/2008Muon Combined Performance Meeting 15 Memory issues MuonGeoModel budget ~ 130 MB (out of ~1GB allocated by simulation tasks, ~2GB allocated by reconstruction tasks) –50 MB are purely from GeoModel can be reduced to a minimum in reconstruction by forgetting all the internal details of detectors (i.e, components linked to readout geometry classes, used by reconstruction) –to be done –80 MB are a tracking related cache (used to be built run-time on demand, since is fully built init time) can be turned on in simulation –easy and done can be optimised (centrally, not in MuonGeoModel)