Support for range in couplings restriction #37
Conversation
This file contains 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
…s when generating XS
…on generation, with the {} syntax, and allowed for the = sign for order specification, interpreted as ==
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Modified coupling restriction specification so as to be able to supply a valid range.
@lcnbr I have updated the python end and some of the rust part, you can take it off from:
(currently not compiling).
Then update the syntax in the python tests (
QCD=->QCD==andQED=->QED==) as well as add some for this new range options (for the case where you know how many diagrams you expect, or set it to whatever number you currently get when visual inspection looks good.Also update the wiki! Thanks!