Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

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

Provide feedback

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

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Implement qgraf-comptatible keywords for FORM interface#744

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
jodavies wants to merge2 commits intoform-dev:master
base:master
Choose a base branch
Loading
fromjodavies:qgraf-keywords

Conversation

@jodavies
Copy link
Collaborator

@jodaviesjodavies commentedNov 21, 2025
edited
Loading

With this change, the diagram filtering is compatible with qgraf's output.

This passes many tests (to come, for the test suite) of single keywords.

Currently there is a difference, to be resolved, when specifying both of a "dual option". For example, specifying "onepi + onepr" in qgraf results in 0 diagrams. In FORM the options cancel each other, and everything is generated. A change to grcc is required to resolve this.

Also to discuss:

  • what shouldWITHSYMMETRIZE do? GRCC has bothGRCC_OPT_SymmInitial andGRCC_OPT_SymmFinal flags

2aba64b itself reverted diawrap.cc to an olderversion. Undo those changes.Additionally remove all diagrams tests, these will be replaced later. But fornow we need a commit which passes the test suite.
@jodavies
Copy link
CollaboratorAuthor

jodavies commentedNov 26, 2025
edited
Loading

Updated:

  • print an error and terminate, if conflicting options are specified, for eg`onepi_'+`onepr_'
  • "external" particles set the `CHECKEXTERN' flag (and it is not available as a pre-processor variable), the result passes some comparisons with qgraf

Still to do:

  • should`withsymmetrize_' enable bothGRCC_OPT_SymmInitial andGRCC_OPT_SymmFinal? Should we have two FORM keywords to control them separately?
  • testfloop
  • due to the way the options are passed, one has to be careful not to give, eg,`onepi_' + `onepi_' -- I am not sure there is an easy way to avoid this issue without changing how the options work completely.
  • `withonepisets_',`withblocks_' "work" in that they change the output, but I don't know if it is correct
  • `withedges_' presumably can be easily crosschecked against qgraf

I have validated against qgraf at 0,1,2,3 loops, with all pairs of non-conflicting filtering keywords, for:
Phi34:

  • phi - phi
  • phi - phi phi
  • phi phi - phi phi

Qcd:

  • qua - qua
  • glu - glu
  • gho - gho
  • qua - qua glu
  • glu - glu glu
  • glu glu - glu glu

@coveralls
Copy link

coveralls commentedNov 26, 2025
edited
Loading

Coverage Status

coverage: 53.163% (-4.0%) from 57.118%
when pulling11d6102 on jodavies:qgraf-keywords
intoa405343 on form-dev:master.

These pass a large number of comparisons with qgraf, using@tueda's "qgraf.frm" comparison procedures.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jodavies@coveralls

[8]ページ先頭

©2009-2025 Movatter.jp