Merge dark photon dimuon mass range lines
A cosmetic change merging the dimuon no IP lines that were split by mass range but had no difference in the cuts. Also addapting for the HLT1 changes. The rates are calculated wrt to properly filtered Minbias MC and provided the HLT1 changes this what we expect to happen.
cc: @acasaisv
Current bandwidth impact
For what matters to the current campaign, there is no change in the BW as there are no changes other than the filtering and the merge of the mass windows. We don't have sprucing lines.
Bandwidth change after update to HLT1
| Changes | Turbo Rate (kHz) | Turbo BW (MB/s) | Full Rate (kHz) | Full BW (MB/s) |
|---|---|---|---|---|
| OFF | 72.27 | 609.26 | 5.83 | 1836.71 |
| ON | 69.81 | 588.26 | 5.64 | 1788.46 |
We don't have sprucing lines.
Merge request reports
Activity
added qee label
added RTA label
added 265 commits
-
6e023f37...50acdd04 - 264 commits from branch
qee_upgrade - 8198cf88 - Merge branch 'qee_upgrade' into 'kaaricha_remove_mass_windows'
-
6e023f37...50acdd04 - 264 commits from branch
mentioned in issue #927 (closed)
mentioned in issue #936
Resolved by Ross John HunterLooks fine to me
- Last reply by Kate Abigail Richardson
-
Just two small queries here. In general this looks like a sensible change, thanks @kaaricha.
reset approvals from @ahabdelm by pushing to the branch
