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 189
    • Merge requests 189
  • 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
  • !49067

Closed
Created Dec 12, 2021 by Masato Aoki@masatoDeveloper
  • Report abuse
Report abuse

switch off filling of TGC trigger data to TGC RDO

  • Overview 7
  • Commits 1
  • Pipelines 1
  • Changes 1

As reported in ATLASRECTS-6690, the TgcCoinData container has different data each time when we run with multi-thread mode. This is because the TrigT1TGC is not properly filling its data into TGC RDO (the origin of TgcCoinData) at the RDOtoRDOTrigger step. As we have a new EDM, "L1" TGC RDO container, for this specific trigger data for Run3 and we plan to re-write all the relevant codes in the near future (1-2 month time scale), and the use of old TGC RDO container is not relevant any longer for the trigger (this old RDO is only relevant for TGC hit data), I switch off this feature for now. Tagging @toshi @tnobe @junpei

Edited Dec 12, 2021 by Masato Aoki
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: master-22.0-mc20_ATLASRECTS-6690