Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • athena athena
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Jira
    • Jira
  • Merge requests 171
    • Merge requests 171
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • atlas
  • athenaathena
  • Merge requests
  • !42027

Closed
Created Mar 26, 2021 by Tomasz Bold@tboldDeveloper
  • Report abuse
Report abuse

Use FSNOSEED for jet chains

  • Overview 29
  • Commits 4
  • Pipelines 2
  • Changes 3

This MR changes L1 seeding for jet chains from L1J to FSNOSEED. However the counts change significantly:

chainComp INFO       HLT_j85_pf_ftf_L1J20:
chainComp INFO         stepCounts:
chainComp INFO           0: 5 -> 20
chainComp INFO         stepFeatures:
chainComp INFO           0: 5 -> 20

That may sound wrong, however it is in agreement with the counts of: HLT_noalg_L1J20 (and similarly for other threshold).

I believe the reason is that FSNOSEED seeding takes into account only CPT items whereas for HLTNav_L1J and even the "forceEnableAllChains" is not realy activating them. Now, what do we want? Tagging @hrussell @khoo @tamartin

Edited May 11, 2021 by Tomasz Bold
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: seed-single-jets-from-fs