Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

alphal00p / gammaloop Public

Notifications You must be signed in to change notification settings
Fork 1
Star 7

Code
Issues
Pull requests 1
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Support for range in couplings restriction#37

Open

ValentinHirschi wants to merge 6 commits intomainalphal00p/gammaloop:mainfrom couplings_restriction_rangealphal00p/gammaloop:couplings_restriction_rangeCopy head branch name to clipboard

Conversation Commits6 (6)Checks Files changed

Commits

Commits on Mar 11, 2025

Modified coupling restriction specification so as to be able to supply a range
ValentinHirschi
committed

Commits on Mar 12, 2025

update linnet and fix coupling order filter for amplitude level orders when generating XS
lcnbr
committed
fix coupling order range parsing
ValentinHirschi
committed

Commits on Mar 13, 2025

update linnet and do not add to coupling orders
lcnbr
committed
Add support for multiple set of possible final states for cross-section generation, with the {} syntax, and allowed for the = sign for order specification, interpreted as ==
ValentinHirschi
committed

Commits on Mar 17, 2025

add tadpole filter
lcnbr
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.