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
New fragments with extended eta range /runThematrix updtaed accordingly #2706
Conversation
A new Pull Request was created by @boudoul (boudoul) for CMSSW_6_2_X_SLHC. New fragments with extended eta range /runThematrix updtaed accordingly It involves the following packages: Configuration/Generator @vciulli, @nclopezo, @vlimant, @cmsbuild, @franzoni, @bendavid, @Degano, @davidlange6 can you please review it and eventually sign? Thanks. |
Hi Mark , you can take abit later this PR at your convenance, as it might change your usual WF numbering : I have added new WFs so the numbering will be different after the merge. |
@@ -1245,7 +1245,7 @@ def genvalid(fragment,d,suffix='all',fi=''): | |||
if upgradeCustoms[k]!=None : upgradeStepDict['HARVESTFast'][k]['--customise']=upgradeCustoms[k] | |||
|
|||
|
|||
upgradeFragments=['FourMuPt_1_200_cfi','SingleElectronPt10_cfi', | |||
upgradeFragments=['FourMuPt_1_200_cfi','TenMuE_0_200_cfi','SingleElectronPt10_cfi', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does TenMuE_0_200_cfi need to be the second entry? It could be moved to the end and the numbering for the current tests won't change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perfect for me!
If the numbering does need to change, we might as well do it sooner rather later. We could move all the new fragments to after the current ones and the numbering won't change though. |
+1 |
New fragments with extended eta range /runThematrix updtaed accordingly
No description provided.