Skip to content

Fix the ITS ramp-up shift rounding and the Pylint errors on master - #2491

Open
sawenzel wants to merge 1 commit into
AliceO2Group:masterfrom
sawenzel:rampup-shift-accuracy
Open

sawenzel wants to merge 1 commit into
AliceO2Group:masterfrom
sawenzel:rampup-shift-accuracy

Conversation

@sawenzel

@sawenzel sawenzel commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

This PR fixes the millisecond rounding of the TF-aligned ITS ramp-up shift from #2489, updates its test to the new signature and clears the remaining Pylint error.

  • The ramp-up is rounded up to whole milliseconds before it is rounded up to whole TFs. Before, a ramp ending just below a TF boundary gave a shifted timestamp up to 1 ms inside the ramp, for example 1149 ms for a 1149.616 ms ramp.
  • test_anchoring_rampup.py passes the TF length to shift_anchor_past_ITS_rampup, checks that the orbit shift is a multiple of the TF length, and has a regression test for the case above.
  • ccdb_cross_check in getCCDBTimeMachineTimestamp.py keeps the pinned object in a local variable, which Pylint can follow.

Assisted by Claude Code.

This fixes the millisecond rounding of the TF-aligned ITS ramp-up shift, updates the ramp-up test to the new signature and clears the remaining Pylint error.

- The ramp-up is now rounded up to whole milliseconds before it is rounded up to whole TFs, so the shifted timestamp can no longer lie inside the ramp.
- test_anchoring_rampup.py passes the TF length to shift_anchor_past_ITS_rampup and has a regression test for a ramp ending just below a TF boundary.
- ccdb_cross_check in getCCDBTimeMachineTimestamp.py keeps the pinned object in a local variable, which Pylint can follow.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@sawenzel
sawenzel requested a review from jackal1-66 as a code owner October 4, 2026 11:59
@github-actions

github-actions Bot commented Oct 4, 2026

Copy link
Copy Markdown

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant