-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
increase beamspot alarmon thr 93X #20325
increase beamspot alarmon thr 93X #20325
Conversation
The code-checks are being triggered in jenkins. |
A new Pull Request was created by @sikler (Ferenc Siklér) for master. It involves the following packages: DQM/BeamMonitor @kmaeshima, @cmsbuild, @vanbesien, @vazzolini, @dmitrijus can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+code-checks |
@cmsbuild, please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready There are some workflows for which there are errors in the baseline: Comparison Summary:
|
The code-checks are being triggered in jenkins. |
Pull request #20325 was updated. @kmaeshima, @cmsbuild, @vanbesien, @vazzolini, @dmitrijus can you please check and sign again. |
+code-checks |
@cmsbuild, please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
Recently we started to have problems with the beamspot alarm at the beginning of fills when LHC does an emittance scan. Detailed analysis of such a situation can be found at
https://twiki.cern.ch/twiki/bin/viewauth/CMS/OnlineBeamSpot#23_Aug_2017_audio_alarm_in_run_3
The problem is that the beamspot moves a lot in z direction during this 10 LS-long operation (4 mins), and it is difficult to reconstruct tracks with the present cylinder of origin setting (optimized for stable beams and normal conditions).
It seems that there is no software-signal which could tell us that LHC does an emittance scan.
Since this issue persists, the only way is to increase the "limit of the number of consecutive LSs without beamspot" from 10 to 15. This disables the false alarms (an emittance scan usually lasts for just about 10 LSs, 4 minutes).