Follow up, ATLAS week ID EF results

Stefan:
Regarding the question about potential differencies from the fitter and ROTCreators ,as pointed out by Markus: After the e-mails about this (some (hopefully main) points summarized below) we saw that even if the default refitROT value was False in InDetTrigJobProperties.py (as pointed out by Wolfgang) this is later changed to True when using the GlobalChi2Fitter.

This means that all the 14.0.0 resutls were produced with (default) GlobalChi2Fitter and refitROT = True (see also JobProperties below). So the current questions are:

• Is there still differencies (between EF vs Offline) in the configuration you can spot/suspect ?
• How should the refitROT flag be used wrt different fitters (see Jiri's question below) ?

Slides: ID EF Tracking Slides, from ATLAS week
JobProperties: JobOptions from the Athena output

E-mail Reminders

Markus:
the other things are different settings of the fitter and ROTCreators, see your momentum resolution plot. we can have a coffee later.

Wolfgang:
14.0.0 InDetTrigRecExample/python/InDetTrigJobProperties.py
class refitROT(InDetTrigFlagsJobProperty):
""" control if refit is done from PRD or ROT """
statusOn = True
allowedTypes = ['bool']
StoredValue = False

Question, Jiri:
is one expected to change refitROT=False for trackFitterType=KalmanFitter or trackFitterType=DNA? It defaults to True and is set to true for globalchi2 later if (self.trackFitterType() is not 'KalmanFitter' and self.trackFitterType() is not 'KalmanDNAFitter') : self.refitROT = True Perhaps it could be complemented by else: self.refitROT = False or does it make sense to have it a user option and run Kalman either with one or another?

-- StefanAsk - 22 Apr 2008