miniAOD for EXO tracking parts

[slava77]

Following the presentations in https://indico.cern.ch/event/1263032/timetable/
more specifically EXO
there is some need to add more information for tracks in miniAOD

• first hit in the lost tracks
  • add information on first hit from HitPattern to lostTracks #42681 in 13_3_X/master merged 2023.08.30
• extend a selection of tracks where dedx is available
  • however, a reduction may be needed pending discussion in a somewhat old issue review content saved in miniAOD in DeDxHitInfo to possibly reduce the size on file #36405

For both cases some motivation from EXO would be nice as well as a contact person.

@aehart @afrankenthal please comment on possibility for someone to investigate and prepare PRs

@cms-sw/xpog-l2
@mmusich @kskovpen

[cmsbuild]

A new Issue was created by @slava77 Slava Krutelyov.

@Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[makortel]

assign xpog

[cmsbuild]

New categories assigned: xpog

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

[slava77]

type tracking

[afrankenthal]

@slava77 to follow up, @tvami has agreed to serve as contact point for item 2 (extending selection of tracks where dE/dX is available) and Daniel Bloch and Paul Vaucelle agreed to serve as contact points for item 1 (adding first hit in lost tracks). @aehart and I will also follow closely. It will be very good if we can make this happen within the relevant constraints. Thanks!

[slava77]

#42681 has 13_3_X/master variant for lostTrack first hits

[mmusich]

Is there interest in backports (e.g. to 13.2.x) or earlier (for remini)?

[slava77]

Is there interest in backports (e.g. to 13.2.x) or earlier (for remini)?

I doubt about 13_2 use/needs (HI-specific), but here it will be least painful. So, why not.
For 13_0, a possible rereco, I suspect some configurable way to pass the no-change rules may be needed.

[mmusich]

I doubt about 13_2 use/needs (HI-specific), but here it will be least painful. So, why not.

here's a backport: #42688

For 13_0, a possible rereco, I suspect some configurable way to pass the no-change rules may be needed.

what's the preferred way about it? Create a new modifier and have the filling of the information happen only if the modifier is active / requested?

[slava77]

For 13_0, a possible rereco, I suspect some configurable way to pass the no-change rules may be needed.

what's the preferred way about it? Create a new modifier and have the filling of the information happen only if the modifier is active / requested?

In the past this was done with a run2_miniAOD_devel modifier.
OTOH, one could claim an exception to the no-change rule, since the variable is not filled at all in the baseline and is filled in this PR one could interpret this as a new variable. These are sometimes allowed.
I could suggest to just port verbatim and wait for comments.

@cms-sw/reconstruction-l2
please comment.

[mandrenguyen]

An exception in this case sounds reasonable to me, if ORP agrees.
MiniAOD is formally XPOG responsibility, so I let them also comment.

[mmusich]

An exception in this case sounds reasonable to me, if ORP agrees.

here are more backports:

• 13.1.X: [13.1.X] add information on first hit from HitPattern to LostTracks #42693
• 13.0.X: [13.0.X] add information on first hit from HitPattern to LostTracks #42694 (draft mode, pending @cms-sw/orp-l2 comments)

[mandrenguyen]

Can you please do 13.2.X as well? Not 100% obvious to me that it's useless there.

[mmusich]

Can you please do 13.2.X as well? Not 100% obvious to me that it's useless there.

I did it already this morning, see #42055 (comment)

[mandrenguyen]

right, sorry Marco