Inclusion of MTD in the tracking navigation

[parbol]

The MTD adds one barrel layer and two layers per endcap to the tracker. In the long-term, the MTD should be included within the tracking logic. The first step consists in the inclusion of the MTD in the tracker navigation. Initial discussion and some possible options have been discussed in:

https://indico.cern.ch/event/898980/contributions/3789239/attachments/2006874/3351890/RECO-Talk.pdf

Option 1 considers adding the MTD list of DetLayers to the TrackerGeometrySearch in such a case that the standard tracker navigation works already with a list of DetLayers that includes the tracker.

Option 2 considers creating superclasses that merge effectively the DetLayers but keeping separate the TrackerGeometrySearch and the MTDGeometrySearch.

A more detailed understanding of the implications of each of these choices and/or other new/intermediate ones is needed.

@pmeridian @fabiocos @mtosi @JanFSchulte @jalimena @slava77 @parbol @perrotta

[cmsbuild]

A new Issue was created by @parbol .

@Dr15Jones, @smuzaffar, @silviodonato, @makortel, @davidlange6, @fabiocos can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[makortel]

assign reconstruction

[cmsbuild]

New categories assigned: reconstruction

@slava77,@perrotta you have been requested to review this Pull request/Issue and eventually sign? Thanks

[slava77]

@VinInn @lgray @rovere
tagging a few more people [feel free to mute, in case the tag is by mistake]

[rovere]

@ebrondol since, to my recollection, she's been the last one using and training the Navigation School for Tracking.

[parbol]

Hi everyone,

I would like to revive this issue in order for us to continue working on the tracking navigation.

In May we presented a few ideas and a working implementation on the integration of the MTD on the navigation of the tracker. You can see the slides here:

https://indico.cern.ch/event/923095/contributions/3878403/attachments/2047579/3431258/RECO-Talk-For-MTDDPGMay29.pdf

The criteria behind this implementation was simply to make the minimum amount of changes in the code, but we thought it could be useful for discussion. It would be nice to have some feedback from the experts to understand the way to go.

Thank you!

Pablo

[kpedro88]

assign upgrade

[cmsbuild]

New categories assigned: upgrade

@kpedro88 you have been requested to review this Pull request/Issue and eventually sign? Thanks

[jpata]

type mtd

[jpata]

@fabiocos given your recent summary of the status of MTD tracking for the O&C R&D document, should we consider this issue as closed?

[fabiocos]

@jpata @parbol for the time being I would say so. The TrackExtenderWithMTD has been made faster, reducing computational issues. and we do not see possible sizeable physics improvements from further work on the short term. Of course this might be revisited in future, especially if compelling reasons to do so will emerge. But I agree that this issue could be closed.

[jpata]

+reconstruction

• completed in MTD reconstruction: time back-propagation accounting for variable speed along trajectory #36202, MTD reconstruction: speed up TrackExtenderWithMTD #36793, [MTD general / DPG Meeting (18 February 2022), https://indico.cern.ch/event/1130532/