Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[14_2_X] TICLv5a : Improve skeleton linking and parameters tuning #46822

Merged

Conversation

waredjeb
Copy link
Contributor

This is a backport of #46539

This PR improves the current Skeleton Linking

  • New Parameters: tuned parameters for hadronic reconstruction.

  • Code refactoring: simply code by refactoring pieces

  • Modified TICLGraph: modified logic for traversing the graph and build components

  • Small changes to TICLDumper: allow to run TICLDumper with TICLv4. It will consume SuperClusters (new with TICLv5) only in TICLv5

New parameters have been included also at HLT

The performance against TICLv4 can be found in the DPS approval talk https://indico.cern.ch/event/1462666/contributions/6158255/attachments/2940573/5170734/TICLv5_DPS_version3.pdf

Should be tested with a .203 workflow

E.g.

test parameters:

    - workflow_opts= -w upgrade
    - workflow = 29896.203, 29691.203, 29691.204
    - enable = profiling, hlt_p2_timing

Edit 06/11/2024:

  • hltTiclTracksterLinks_cfi and hltTiclTracksterLinksUnseeded_cfi, Both of them were Unseeded with no differences between them, for consistency I removed hltTiclTracksterLinksUnseeded_cfi fixing the Egamma sequence accordingly
  • I 've added the L1Seeded module and sequence for the Recovery Tracksters, it is not used but I added it for consistency with hltTiclTracksterLinksL1Seeded_cfi

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 28, 2024

A new Pull Request was created by @waredjeb for CMSSW_14_2_X.

It involves the following packages:

  • HLTrigger/Configuration (hlt)
  • RecoHGCal/TICL (reconstruction, upgrade)

@Martin-Grunewald, @Moanwar, @cmsbuild, @jfernan2, @mandrenguyen, @mmusich, @srimanob, @subirsarkar can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @SohamBhattacharya, @VourMa, @apsallid, @felicepantaleo, @forthommel, @hatakeyamak, @lecriste, @missirol, @mmusich, @rovere, @sameasy, @silviodonato, @sobhatta, @youyingli this is something you requested to watch as well.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 28, 2024

cms-bot internal usage

@mmusich
Copy link
Contributor

mmusich commented Nov 28, 2024

@waredjeb, can you clarify what's the purpose of the backport?

@mmusich
Copy link
Contributor

mmusich commented Nov 28, 2024

test parameters:

  • workflow_opts= -w upgrade
  • workflow = 29896.203, 29691.203, 29691.204
  • enable = hlt_p2_integration, hlt_p2_timing

@waredjeb
Copy link
Contributor Author

@waredjeb, can you clarify what's the purpose of the backport?

Hi @mmusich

Yes. So, in 14_2_X we have a procModifier to enable TICLv5. TICLv5a completes the implementation of TICLv5 and provides the final version of TICLv5. It would be nice to have in 14_2_X release the final TICL version instead of having the "incomplete" one in 14_2_X and a "complete" one in 15_0_X.

@mmusich
Copy link
Contributor

mmusich commented Nov 28, 2024

It would be nice to have in 14_2_X

is there any plan to use such feature in 14_2_0? Otherwise technically 14_2_X is closed for feature requests and only bug-fixes are acceptable.

@mmusich
Copy link
Contributor

mmusich commented Nov 28, 2024

@cmsbuild, please test

@waredjeb
Copy link
Contributor Author

It would be nice to have in 14_2_X

is there any plan to use such feature in 14_2_0? Otherwise technically 14_2_X is closed for feature requests and only bug-fixes are acceptable.

This is a bug-fix, the previous configuration was bugged because of tuning of the parameters done on a bugged geometry

@mmusich
Copy link
Contributor

mmusich commented Nov 28, 2024

This is a bug-fix, the previous configuration was bugged because of tuning of the parameters done on a bugged geometry

from the description this PR is also a bug-fix, but it also contains new features.
Having said that the actual scope of the changes remains unclear to me.

@cmsbuild
Copy link
Contributor

+1

Size: This PR adds an extra 12KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d8e99e/43135/summary.html
COMMIT: d112936
CMSSW: CMSSW_14_2_X_2024-11-28-1100/el8_amd64_gcc12
Additional Tests: HLT_P2_INTEGRATION,HLT_P2_TIMING
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/46822/43135/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 1423 differences found in the comparisons
  • DQMHistoTests: Total files compared: 49
  • DQMHistoTests: Total histograms compared: 3800267
  • DQMHistoTests: Total failures: 5515
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3794732
  • DQMHistoTests: Total skipped: 20
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 48 files compared)
  • Checked 216 log files, 184 edm output root files, 49 DQM output files
  • TriggerResults: found differences in 1 / 47 workflows

@jfernan2
Copy link
Contributor

jfernan2 commented Dec 2, 2024

+1

@mmusich
Copy link
Contributor

mmusich commented Dec 2, 2024

+hlt

@waredjeb
Copy link
Contributor Author

waredjeb commented Dec 2, 2024

This is a bug-fix, the previous configuration was bugged because of tuning of the parameters done on a bugged geometry

from the description this PR is also a bug-fix, but it also contains new features. Having said that the actual scope of the changes remains unclear to me.

Hi @mmusich, so if it is a problem merging the PR, I can close it and we will tell people to use TICLv5 only from 15_0_X.

@mmusich
Copy link
Contributor

mmusich commented Dec 2, 2024

so if it is a problem merging the PR, I can close it and we will tell people to use TICLv5 only from 15_0_X.

it is not a problem. If it's convenient to have it in 14.2.0 let it be there (PS. the PR is already signed).

@mmusich
Copy link
Contributor

mmusich commented Dec 2, 2024

backport of #46539

@mmusich
Copy link
Contributor

mmusich commented Dec 2, 2024

type bug-fix

@Moanwar
Copy link
Contributor

Moanwar commented Dec 2, 2024

+Upgrade

@cmsbuild
Copy link
Contributor

cmsbuild commented Dec 2, 2024

This pull request is fully signed and it will be integrated in one of the next CMSSW_14_2_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_15_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @rappoccio, @mandrenguyen, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2)

@mandrenguyen
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 632c62f into cms-sw:CMSSW_14_2_X Dec 4, 2024
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants