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 220
    • Merge requests 220
  • 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
  • !29950

Merged
Created Jan 30, 2020 by Goetz Gaycken@goetzDeveloper

Create ROIInfoVec by algorithm rather than on demand by the tool.

  • Overview 53
  • Commits 2
  • Pipelines 7
  • Changes 11

Current The ROIInfo objects are created on demand by the scoring tool and stored via WriteHandle in StoreGate. If the objects alread exist (tested via ReadHandle) they are read via ReadHandle. None of the handles are declared and the handle keys are created on the spot. This may fail if the objects are needed by two algorithms which run in parallel. It also showed a visible lock contention.

The problem was addressed by creating the ROIInfoVec by a conditions algorithm rather than on demand by the tool.

Edited Feb 18, 2020 by Goetz Gaycken
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: InDetTrackScoringTools_master_create_ROIInfoVec_by_alg