Smoking backend#597
Open
ChrisJChang wants to merge 16 commits into
Open
Conversation
Currently just called a test scenario on the example slha with a hard coded path
…on in gambit (now used in likelihood evaluation) - Still need to pass process xsecs. Should follow simply enough, but we have not actually used it in gambit yet I think
… (required for smoking)
…ts separate cpp file
To test the interface, I have a ColliderBit_TEST.yaml file
…ng it needs to weight Pythia events from smoking
ChrisJChang
added
ColliderBit
Backends
Add warning in event weighting so Pythia generating processes without correpsonding xsecs fails gracefully.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds in a new backend for calculating higher-order SUSY cross-sections (SMOKING). Currently this code is not publicly released, so the cmake entry currently prints a warning asking for the tarball to be added. I am creating a PR now, so that this can be merged into any project branches that need it.
It also adds in the ability to copy the initial cross-section estimates into the final ones. Normally two separate Pythia runs would happen, one with fewer events for an initial xsec estimate, and the full MC. This lets you use the smoking cross-section for both (only running smoking once). With the already present ColliderBit code to accept cross-section uncertainties, and also to weight events by process xsecs, this should allow the user to generate NLO xsecs, and weight the Pythia events accordingly.
Note: The current way it does this is to weight the events in ColliderBit, which means that the distribution of events generated by Pythia will not be altered by the xsecs. In order to affect the Pythia distribution of events based on the NLO xsecs, a userhook would need to be made (and potentially requires two initialisations of Pythia rather than one)
I have attached a yaml file for testing, which is the CMSSM yaml file adapted to run smoking.
ColliderBit_TEST.zip
I am setting @ahye as a reviewer since he is familiar with both ColliderBit and smoking.