1

MuonGeoModelMuonGeoModelstatus reportstatus report

focus on issues relevant to 13.0.10, 20focus on issues relevant to 13.0.10, 20

• Access to Condition DB with M. Verducci, R. Harrington

• MDT deformations with I. Logashenco

• Volume clashes

2

•An Alignment Tool and Service (already introduced at the last Muon Week) retrieve A-lines and B-lines from the cond DB (COOL with oracle), whenever appropriate, using the Interval Of Validity (IoV) Service, which takes adequate actions at any boundary of validity ranges in the ATLAS data

• alignment data are published in the detector store for generic applications (after un-packing)• in MuonGeoModel the transforms of all stations with updated alignment parameters are overridden • data preparation and reconstruction clients of MuonGeoModel access the most updated geometry representation available at each event

Alignment Constants as condition dataAlignment Constants as condition data

Tool/service integrated in 13.0.10 and successfully accessing the production DB in COOL2 – to be integrated with the std GeoModel scheme ( simulation by reading condition data)

3

Alignment Constants as condition dataAlignment Constants as condition data

Testing the software chain reading A-lines from the Condition Database• A-Lines corresponding to random misalignments in R_01_01_Egg_Rndm have been stored in the Condition DB;• Dump of the geometry (from MuonGeoModel) in 2 scenarios:

•Init from R’’ static •Init from R’ static + A-lines from COOL•Excellent agreement already reported at last Muon Week

• single muons with pT=20GeV/c, in the relevant IoV, simulated in R_01_01_Egg_Rndm have been reconstructed in three modes:

•black: MuonGeoModel initialised with R_01_01_Egg_Rndm•red: R_01_01_Egg loaded init time (no correction for misalignments)•blue: R_01_01_Egg loaded init time + A-lines read from the Condition Database

newnew

4

1/pT pull distribution

cot pull distribution

z0 pull distribution

rms=1.1 mm

rms=1.3 mm

rms=1.1 mm

rms=1.3 mm

•black: MuonGeoModel initialised with

R_01_01_Egg_Rndm•red: R_01_01_Egg

loaded init time (no correction for

misalignments)•blue: R_01_01_Egg

loaded init time + A-lines read from the Condition

Database

A comparison of positions of MDT hits associated to tracks (red - black modes) shows deviations consistent with random misalignments in R_01_01_Egg_Rndm (1mm, 1mrad in each direction)

5

DEFORMATION CONSTANTSDEFORMATION CONSTANTS• MDT deformations are not simulated in Geant4• Most effects can be described with rigid tubes tilted and shifted w.r.t. their

nominal location in the multilayer • Bent tubes and wire sagging are handled with other mechanisms and tools

• Deformations can be treated in Readout Geometry • a first implementation in place in MuonGeoModel (under test); - needs test of coherence

with Amdc • full MDT tube transform comes from (first to last):

– nominal (translations only) tube_to_multilayer – delta_deformation - add tilt and shift in the multilayer frame using B-line parameters– nominal multilayer_to_station– delta_station_alignment (A-lines)– nominal station_to_global (P-lines)

• Realistic chamber geometry available to all reconstruction applications • Deformations in digitization (ongoing and progressing work for

testing the implementation of B-lines)– simulate in the nominal geometry– convert the hit local coordinates into nominal global coordinates: i.e. compute a point

belonging to the track– convert the global position into local coordinates in the tilted and shifted tube (according

to B-lines)– use the new local coordinates to compute drift time

first plots available – very low statistics

6

Clash clean-up Clash clean-up active materialsactive materialsCSC small and large sectors: spacer overshooting the station mother volume

– fixed envelop shape

CSC large sectors: station mother

volume has no coffin shape – clash

with nearby stations:

use of assembly solves the problem

side consideration: visualization of Booleanscoffin shape shown chambers, for gas gaps not for G10+honeycomb support panels

7

Clash clean-up Clash clean-up active materialsactive materials

CRO and CHV longer than station envelop

overshootingshortened

Small problems common to all EC MDT chambers

LB clashing with CRO and CHVsimilar to the problem already solved in the barrel

solution

solved

MDT multilayer overshoots EC station envelop, due to the longest tubesfixed

8

Clash clean-up Clash clean-up active materialsactive materials

Small problems common to all EC MDT chambers

standard solution

does not work for EML1 and EML6LB too long in AMDB ?

had hoc solution

In BMF stations LB02 clash with CRO, CHV and one multilayer: LB02 too high for the room between the two multi-layers and the CRO1 and CHV1 height

should it be LB01 in AMDB ? had hoc solution

MuonGeoModel-00-04-11 to be collected for 13.0.20 should reduce substantially the number of clashes – recursive test submitted and running

some checks also needed on primary numbers

9

Clash clean-up Clash clean-up active-dead materialsactive-dead materials

• BOG and BOF clashing with the feet • some BMS clashing with nearby coil ribsProbably some problem in the dead material description

(detectors agree in MuonGeoModel and Amdc)

some refined code for dead matter from Andrei B. available for testing

10

Clash clean-up Clash clean-up active-dead materialsactive-dead materials

BMS with cutouts, not yet implemented, clashing with coil ribsReady to try the cutout tool from GeoModel

To simplify the implementation, stations with cutouts are assemblies