muid status report

16
/MuID status report on behalf of the Moore/MuID group. Status in the releases ( Units Migrations DC1/G3 MuonGeoModel Migration DC2/G4) MuID updates Trig

Upload: shino

Post on 02-Feb-2016

44 views

Category:

Documents


0 download

DESCRIPTION

/MuID status report. on behalf of the Moore/MuID group. Status in the releases ( Units Migrations DC1/G3 MuonGeoModel Migration DC2/G4) MuID updates Trig. Status in the releases. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: MuID status report

/MuID status report

on behalf of the Moore/MuID group.

Status in the releases ( Units Migrations DC1/G3 MuonGeoModel Migration DC2/G4)MuID updatesTrig

Page 2: MuID status report

BNL, 25 May 2004

Status in the releases

Moore has completed the units migration in release 7.8.0. (MuonDetectorDescription DC1/G3 data)MuID has completed the units migration in release 8.0.0. (MuonDetectorDescription DC1/G3 data)Moore has migrated to MuonGeoModel in release 8.2.0. Given the fact that MuonGeoModel at present only works for DC2/G4 data, Moore in release 8.2.0 can only works on DC2/G4 data. Backward compatibility will soon be restored.

Page 3: MuID status report

BNL, 25 May 2004

Units Migration

Moore has completed the units migration in release 7.8.0.To validate the units migration single muons datasets from DC1 have been analysed. The datasets used are under:/castor/cern.ch/atlas/transfer/dc1/roma1

pT=6GeV/c 40000 eventspT=20GeV/c 40000 eventspT=100GeV/c 40000 eventspT=200GeV/c 40000 eventspT=300GeV/c 40000 eventspT=500GeV/c 40000 eventspT=1000GeV/c 20000 events

Page 4: MuID status report

BNL, 25 May 2004

Units Migration

Moore Reconstruction efficiency

as a function of

Example:

Release 7.8.0 has been used. Efficiency drop in the regions was present also in previous releases (partially known problem, and partially under investigation)

Nr Reconstructed TracksPT= 100GeV/c<N> ~ 1.

1/PT resolution

PT= 100GeV/cMean = 1.00Sigma= 0.045

Page 5: MuID status report

BNL, 25 May 2004

Units Migration

The complete set of results is available under web:http://www.fisica.unile.it/~cataldi/Moore/MooreMeeting25_03_04.html

The results show a full agreement with previous validation tests performed on DC1 (before the units migration): see for example the validation web page for 7.0.3 release version, although the shows a more evident deterioration that was not present in the previous releases.From a technical point of view during the validation test performed on 7.8.0 a set of scripts for running the single muon validation and provide the plots in a reference area has been setup (Nectarios Benekos). A set up of a standard Moore validation web page is foreseen (Nectarios Benekos and Stephane Willocq) as well as the setup of scripts for running on G4 data (DC2).

Page 6: MuID status report

BNL, 25 May 2004

and the MuonGeoModel

Moore has migrated to MuonGeoModel in release 8.2.0. Given the fact that MuonGeoModel at present only works for DC2/G4 data, Moore in release 8.2.0 can only works on DC2/G4 data. In the following a set of preliminary results is presented, running on a set of 100GeV/c muons simulated with release 8.0.0. No treatment for inert material has been taken into account in reconstruction.

G. Stavropoulos

Page 7: MuID status report

BNL, 25 May 2004

running on G4 data

Nr Reconstructed TracksPT= 100GeV/c<N> ~ 1.

1/PT resolution

PT= 100GeV/cMean = 0.97Sigma= 0.057

Moore Reconstruction efficiency

as a function of

Reconstructed Muon are expressed at the entrance of the MuonSpectrometer (first measured point), while the Generated Muons are expressed at the beam spot.

G. Stavropoulos

Page 8: MuID status report

BNL, 25 May 2004

MuID statusThe MuonIdentification package has been migrated to new units (migration completed in 8.0.0 release) The package has been reorganized (dividing Algorithmical classes and DataEvent classes into subpackages). The main motivation for the reorganization:

The work in progress on low energy Muon Identification (Natasha Panikashvili) needed to get into the repository release structure. The old structure containing 27 classes in MuonIdentification made it a rather large package.

Page 9: MuID status report

BNL, 25 May 2004

MuidTrackCandidateSelection of ID track

1. J/ψ μ+ μ-2. μ+ μ-3. Single μ

Output: container of iPatRec candidates

MuidDigitTrackAssociation

Association of ID tracks with MS digits (Simulated digits, digits from MOORE segments)

Output: vector of associated digits for each iPatRec candidate

Status:

• The low pt muon identification algorithm is implemented and it is in the CVS repository

• The algorithm was tuned at the analysis level and it is now under test in the C++ reconstruction environment.

Algorithm outline:

iPatRec candidate

MDT digits

CSC digits

RPC digits

TGC digits

TileCal information

Digits from MOORE segments

Output example:

Status of low pt identification

N. Panikashvili

MuidTrackCandidate

Page 10: MuID status report

BNL, 25 May 2004

TrigMoore is the online version (interface) of Moore. It evolves togheter with the offline packages Moore and MuId and depends on Moore/MuId code/developers.

TrigMoore allows the following steps:The reconstruction of tracks in the MuonSpectrometer (Moore)The extrapolation to the interaction Region (MuID standalone)The combination of the tracks with Inner Detector tracks, performing a global refit (MuID combined)

TrigMoore can be seeded by:LVL1 Trigger information LVL2 Trigger information (MuonFeature)

Trig current status (0)

M.Biglietti, G.Cataldi

Page 11: MuID status report

BNL, 25 May 2004

The full MuonSlice chain:L1 Transient ByteStream Fast TrigMoore

has been debugged in a 7.2.0+ release using a project area The code has been migrated under 8.0.0 and it is ready for commit/tag. It will be officially included in 8.3.0 release.

The priority of Moore migration to MuonGeoModel has provoked a broken Moore online package, that will be restored in the following release. Analysis studies on reconstruction performances with single muons sample in presence of cavern background are on-going, in the LVL1 seeded version of Moore (see next slides). The studies use DC1 data.

Trig current status (I)

M.Biglietti, G.Cataldi

Page 12: MuID status report

BNL, 25 May 2004

Trig studies(0)

M.Primavera, A.Ventura

“Seeded” (by the LVL1 ROIs) version of TrigMOORE applied to reconstruct 100 GeV single muon without and with cavern background addition

“nominal” background (x1) or a “safety” factor 5 (x5)

Track acceptance cut in || < 0.9 (driven by the RPC-LVL1)

Rel. 7.2.0 + new LVL1 trigger packages + bug fixed in the code (equivalent to release 7.6.0)LVL1 acceptance in the above h region: #ROI >0, thr#>0Moore efficiency (track 2 < 3.) and MUID eff. normalized to LVL1 (#ROI >0, thr#>0)

No bck x1 x5

LVL1 acc. 0.8160.016 0.8260.016 0.8670.014

<# ROI> 1.033 1.115 1.238

Moore eff. 0.9960.003 0.9850.006 0.9520.010

Muid eff. 0.9960.003 0.9800.007 0.9440.010

<track 2> 1.23 1.22 1.21

<Track mult./ev>

1.03 1.09 1.11

Compare with ~12 track segments/ev in MOORE offline for x5

Page 13: MuID status report

BNL, 25 May 2004

No bck

x5

x1

Pt resolution is slightly Pt resolution is slightly worse as bck increases worse as bck increases

MOORE Pt resolution

M.Primavera, A.VenturaM.Primavera, A.Ventura

Page 14: MuID status report

BNL, 25 May 2004

No bck

x5

x1

Pt resolution is slightly Pt resolution is slightly worse as bck increases worse as bck increases

MUID Pt resolution

M.Primavera, A.VenturaM.Primavera, A.Ventura

Page 15: MuID status report

BNL, 25 May 2004

MOORE:deterioration of the efficiency cutting @3,5,10 pt sigma

for good reconstructed

tracks (i.e. close in eta and phi to the

true track)

M.Primavera, A.VenturaM.Primavera, A.Ventura

Page 16: MuID status report

BNL, 25 May 2004

Conclusions and Future plans Migration to MuonGeoModel representation for the reconstruction has been accomplished in release 8.2.0

Validation of G4 data samples is ongoing.

Restoring the functionality for DC1/G3 data will follow (next release) Low pT algorithm are under test.TrigMoore will be restored in next release, hopefully for boths MuonDetDescr and MuonGeoModel representation.