-
Notifications
You must be signed in to change notification settings - Fork 21
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
Run2 Process Xsecs #26
Conversation
@Bogdan-Wiederspan What would need to be done for this PR to leave the WIP phase? |
Nothing needs to be added @riga. I simply forgot to switch the state to "ready to review" |
Actually not completely true, I am still including updated values using the GenXSecAnalyzer directly instead of cmsdb and there will be a few new processes to include once the run2 campaigns are merged (e.g. several multibosons decay channels like ZZ->QQ) |
Updated values are now fully included with the corresponding logs and some logs expected to be needed after the merge, only the additional values which will come with the processes added with the merge are missing. |
…cesses, need to be corrected in campaigns
Conflicts: cmsdb/processes/ewk.py cmsdb/processes/higgs.py cmsdb/processes/top.py
resolved Merge conflicts with master :) |
Nice, thanks for spotting these |
|
@nprouvost @mafrahm Are the two comments above resolved? |
This PR adds all xsecs for Run2