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

Change the way total cross section is computed in GenXSecAnalzyer and fix the print out in LHERunInfo.cc #7674

Closed
wants to merge 1 commit into from

Conversation

syuvivida
Copy link
Contributor

GenXSecAnalyzer: when computing the total cross section after jet matching, instead of multiplying the
jet matching efficiency with individual cross section first and adding up the cross section from each process
later, now we add the cross section before matching first and multiply this cross section with the total jet matching efficiency.

LHERunInfo.cc: previous version did not include the process that has zero jet matching efficiency when computing the total jet matching efficiency. It is fixed now.

The threshold of 1e-6 has been modified to zero too.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @syuvivida for CMSSW_7_4_X.

Change the way total cross section is computed in GenXSecAnalzyer and fix the print out in LHERunInfo.cc

It involves the following packages:

GeneratorInterface/Core
GeneratorInterface/LHEInterface

@vciulli, @covarell, @thuer, @cmsbuild, @nclopezo, @bendavid can you please review it and eventually sign? Thanks.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@Degano you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@davidlange6
Copy link
Contributor

closing in 74x - there is the same PR open in 75x (now the development release)

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