Skip to content

Comments

test: track usage of hard-coded scaler clock frequencies#1128

Draft
c-dilks wants to merge 1 commit intodevelopmentfrom
magic-freq
Draft

test: track usage of hard-coded scaler clock frequencies#1128
c-dilks wants to merge 1 commit intodevelopmentfrom
magic-freq

Conversation

@c-dilks
Copy link
Member

@c-dilks c-dilks commented Feb 23, 2026

The DSC2 and STRUCK scaler clock frequencies are stored in CCDB, but they are also hard-coded. This branch adds a magic number to each of the hard-coded assignments, and checks for that magic number when they're (likely) used. Printouts to stderr starting with clockbug are used to investigate.

The DSC2 and STRUCK scaler clock frequencies are stored in CCDB, but
they are also hard-coded. This branch adds a magic number to each of the
hard-coded assignments, and checks for that magic number when they're
(likely) used. Printouts to `stderr` starting with `clockbug` are used
to investigate.
@baltzell
Copy link
Collaborator

What's the measured value of the hardware clock in question? This isn't affected by both DCS2 and Struck scalers.

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.

2 participants