Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • 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 154
    • Merge requests 154
  • 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
  • !53424

Closed
Created May 18, 2022 by Riccardo Maria Bianchi@rbianchi☀Developer
  • Report abuse
Report abuse

Fix VP11 negative event numbers while creating new files, when event numbers reach the "int" limit

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

This MR fixes the negative event numbers observed while creating new files, when the event numbers are large enough to reach the "int" limit.

So, now I moved the event number in {{VP1FilesUtilities}} from {{int}} to {{unsigned long long}}.

That was fixed in several VP1 classes before, and in VP1AlgsEventProd recently (), but that new issue has been found by @lshi, only when enabling the single-event ESD production at P1:

https://atlasop.cern.ch/elisa/display/453544?logbook=ATLAS

This MR fixes that issue and solves ATLASVPONE-569.

NOTE: Hopefully, this MR can be merged into the new release for P1, we need this fix for the onlineEventDisplays single-event ESD production.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: master-fix-vp1-negativeEvtNumber