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

Run2 Process Xsecs #26

Merged
merged 32 commits into from
May 25, 2024
Merged

Run2 Process Xsecs #26

merged 32 commits into from
May 25, 2024

Conversation

Bogdan-Wiederspan
Copy link
Contributor

This PR adds all xsecs for Run2

@riga
Copy link
Member

riga commented Mar 12, 2024

@Bogdan-Wiederspan What would need to be done for this PR to leave the WIP phase?

@Bogdan-Wiederspan Bogdan-Wiederspan marked this pull request as ready for review March 12, 2024 12:58
@Bogdan-Wiederspan
Copy link
Contributor Author

Nothing needs to be added @riga. I simply forgot to switch the state to "ready to review"

@nprouvost
Copy link
Contributor

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)

@nprouvost
Copy link
Contributor

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.

@riga riga marked this pull request as draft March 26, 2024 10:24
@riga riga self-requested a review March 26, 2024 10:24
@riga riga self-assigned this Mar 26, 2024
@riga riga added the enhancement New feature or request label Mar 26, 2024
@nprouvost nprouvost marked this pull request as ready for review April 16, 2024 13:30
Conflicts:
	cmsdb/processes/ewk.py
	cmsdb/processes/higgs.py
	cmsdb/processes/top.py
@haddadanas
Copy link
Contributor

haddadanas commented Apr 24, 2024

resolved Merge conflicts with master :)
Question (resolved): If we have a $\pm 2$% uncert is it noted in the scinum version we use as uncert=2j or uncert=0.02j? A few xsecs use the first notation
I tested it in the latest version of scinum and the latter would be correct, but I wasn't sure if the notation was different in older scinum versions.
I made a commit to correct these and can push it if the second notation turns out to be correct 😅

@nprouvost
Copy link
Contributor

Nice, thanks for spotting these

@riga
Copy link
Member

riga commented May 24, 2024

Question (resolved): If we have a % uncert is it noted in the scinum version we use as uncert=2j or uncert=0.02j? A few xsecs use the first notation

0.02j is indeed the right way to do it 👍

@riga
Copy link
Member

riga commented May 24, 2024

@nprouvost @mafrahm Are the two comments above resolved?

@riga riga merged commit 52379b1 into master May 25, 2024
4 checks passed
@riga riga deleted the update_run2_xsecs branch May 25, 2024 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants