-
Notifications
You must be signed in to change notification settings - Fork 2
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
Is matching_order
correctly determined?
#322
Comments
hmm? to me it seems the LHA benchmarks have passed, which should test the default - and also the N3LO benchmarks seemed alright, which should test the overwriting ... or do you mean we can no longer access the N3LO matching? |
Hi @giacomomagni and @felixhekhorn , but looking at
|
Indeed, we |
Okay, so you are worried about this line specifically: Line 93 in 10f0733
then maybe I agree with you, there is a bug - do you agree as well @niclaurenti ? When fixing this, we should provide also a unit test |
Ok @giacomomagni you are right. Sorry for doubting. The point in which it must be changed is: |
mmm wait, now I disagree. We should just adjust the lines modified in that PR. |
I agree with @giacomomagni:
|
Yes I agree, I've read Felix's comment after posting mine |
Actually here I think we have introduced a bug.
matching_order
followsPTO
(ie is 2 for NNLO) so here we should subtract one, once doing the default, no?Originally posted by @giacomomagni in #299 (comment)
The text was updated successfully, but these errors were encountered: