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

Use channelid in cudacpp (and fortran) helicity filtering? #975

Open
valassi opened this issue Aug 21, 2024 · 0 comments
Open

Use channelid in cudacpp (and fortran) helicity filtering? #975

valassi opened this issue Aug 21, 2024 · 0 comments

Comments

@valassi
Copy link
Member

valassi commented Aug 21, 2024

Use channelid in cudacpp helicity filtering?

Hi @oliviermattelaer this is another followup to our chat yesterday. You suggested that we should use channelid in helicity filtering in cudacpp, whicl no wwe do not. Essentially you suggest to remove the nochannel calls to ME calculations.

The point is that strictly speaking the list of good helicities depends on the channel. Rephrase: a channel has ME>0 only if the numerator (one individual feynman diagram) is greater than 0. So there may be helicities which are good for one diagram, but always give 0 for another diagram.

IIUC however this is something that is not yet done in fortran? Or rather, IIUC, you said that there is a single list of helicities common to all channels n fortran, which is computed by iterating over all channels, so that a "good helicity" is a helicity which gives ME>) for at least one channel. This is essentially what cuudacpp also does now.

This is a followup to #960 (where you noticed that there is a FBRIDGESEQUENCE_NOMULTICHANNEL call). Anyway we agreed to merge #960 as is, and then eventually work on LIMHEL>0 in cudacpp (#564) and on helicity filtering with channelid (this issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant