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 184
    • Merge requests 184
  • 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
  • !44011

The source project of this merge request has been removed.
Merged
Created May 31, 2021 by Johannes Junggeburth@jojunggeDeveloper

MdtDigitization - Use calibration tool by default

  • Overview 42
  • Changes 31

Hi,

as discussed in ATLASRECTS-6203, a potential reason for the low MDT efficiencies in the run IV layout could be the usage of the default drift-time relations instead of the proper ones in the calibration database. From this MR on, we use the calibration tool by default and remove the property to switch it off optionally. These developments have been made by @nkoehler. They are his last ones before moving on to other tasks outside ATLAS. Marking the end of an era @minions:

image

To continue the game philosopher of the day let me also mention: @goblirsc, @sroe, @npetters, @pgadow, @fsforza, @szambito, @sabidi, @gartoni, @mvanadia:

image

Edited Jun 03, 2021 by Johannes Junggeburth
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: LastDevByNico