Extend logic of shared-cluster check in TrackListMerger

[missirol]

CMSHLT-3534 describes a use case where track collections based on different SiStrip clusters would need to be combined taking into account the removal/cleaning of duplicate tracks.

As pointed out by @slava77, this does not work correctly out-of-the-box and, quoting him from CMSHLT-3534,

It should be relatively straightforward to extend the shared input/cluster check in case clusters are from different collections and in that case to explicitly check if the firstStrip+size ranges overlap for clusters from the same detId. It will need some care to keep it computationally efficient (so that this doesn't slow down the offline code significantly in particular).

In principle, this feature could be used to implement the changes described in CMSHLT-3534, and that would lead to an increase of ~2% in HLT throughput for the latest Run-3 HLT menu.

Is this something that tracking experts (e.g. @cms-sw/tracking-pog-l2) could implement ? (the sooner, the better)

[cmsbuild]

cms-bot internal usage

[cmsbuild]

A new Issue was created by @missirol.

@Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[mmusich]

assign reconstruction, hlt

[mmusich]

type tracking

[cmsbuild]

New categories assigned: reconstruction,hlt

@jfernan2,@mandrenguyen,@Martin-Grunewald,@mmusich you have been requested to review this Pull request/Issue and eventually sign? Thanks

[missirol]

@cms-sw/tracking-pog-l2

What do you think ? (useful / not useful, easy / hard, will be done / will not be done)

[mmasciov]

@cms-sw/tracking-pog-l2

What do you think ? (useful / not useful, easy / hard, will be done / will not be done)

@missirol, we are looking into it. Will comment here and/or with a PR ASAP.

[missirol]

@mmasciov , any news on this front ?