Skip to content
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

Updating SiStrip DQM TriggerBits for HIP monitoring (PR #15447) #15460

Merged
merged 1 commit into from Aug 14, 2016

Conversation

mmusich
Copy link
Contributor

@mmusich mmusich commented Aug 13, 2016

Summary of changes in Global Tags

RunII data

Updated content

  • RunI+ RunII-2015 IOV:
---+++++ *IOV*: 1-264291
| *TriggerBits list key* | *HLT paths* |
| 'SiStrip_HLT' | 'HLT_ZeroBias_v*', 'HLT_HIZeroBias_v*', 'HLT_BptxAnd_*' |
| 'SiStrip_L1' | 'L1_ZeroBias' |
| 'Tracking_HLT' | 'HLT_ZeroBias_v*', 'HLT_BptxAnd_*' |
  • RunII-2016 IOV:
---+++++ *IOV*: 264292-inf
| *TriggerBits list key* | *HLT paths* |
| 'SiStrip_HLT' | 'HLT_ZeroBias_v*', 'HLT_HIZeroBias_v*', 'HLT_BptxAnd_*' |
| 'SiStrip_L1' | 'L1Tech_BPTX_plus_AND_minus.v0', 'L1_ZeroBias', 'L1_ExtCond_032' |
| 'Tracking_HLT' | 'HLT_ZeroBias_v*', 'HLT_BptxAnd_*' |
| 'Tracking_HLT_HIP_OOT' | 'HLT_ZeroBias_FirstBXAfterTrain_v*' |
| 'Tracking_HLT_HIP_noOOT' | 'HLT_ZeroBias_FirstCollisionInTrain_v*' |
| 'Tracking_HLT_noHIP_noOOT' | 'HLT_ZeroBias_FirstCollisionAfterAbortGap_v*' |

attn: @mtosi @fioriNTU @arunhep

@mmusich
Copy link
Contributor Author

mmusich commented Aug 13, 2016

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 13, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/14517/console

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_8_1_X.

It involves the following packages:

Configuration/AlCa

@ghellwig, @cerminar, @cmsbuild, @franzoni, @mmusich, @davidlange6 can you please review it and eventually sign? Thanks.
@makortel, @Martin-Grunewald, @ghellwig, @tocheng this is something you requested to watch as well.
@slava77, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@cmsbuild
Copy link
Contributor

@mmusich
Copy link
Contributor Author

mmusich commented Aug 13, 2016

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar

@cmsbuild
Copy link
Contributor

@davidlange6
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 8cd6d9c into cms-sw:CMSSW_8_1_X Aug 14, 2016
@davidlange6
Copy link
Contributor

seems we either need to change

  1. the definition of workflow 1001 to be run2 and make sure this new DQM does not run for the Run1 processing
    or 2) change the GT to include these new keys

any preferences?
@mmusich

@mmusich
Copy link
Contributor Author

mmusich commented Aug 15, 2016

@davidlange6 we can introduce the new keys as well in the run1 run interval, but as far as I can tell will be for technical tests only.
For several other reasons we are working w/ @franzoni to create a new matrix workflow (the run2 version of 1001.0). Depending on the timescale, we can choose either one of the two (the former is faster).

@mmusich
Copy link
Contributor Author

mmusich commented Aug 18, 2016

@davidlange6 I addressed your comment in the cheapest way:
see at #15508

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

Successfully merging this pull request may close these issues.

None yet

3 participants