Scale ratios in convolute_eko#138
Conversation
Codecov Report
@@ Coverage Diff @@
## master #138 +/- ##
==========================================
+ Coverage 89.75% 89.80% +0.04%
==========================================
Files 45 45
Lines 6826 6858 +32
==========================================
+ Hits 6127 6159 +32
Misses 699 699
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
|
@felixhekhorn do you want an intermediate review? Or did you just forget to click "Ready for review" removing the "Draft" status? |
The workflow not failing means that at least on nightly is working. @cschwan will reply more precisely. However, which version of Rust do you have? |
yes, please!
no, this was intentional - as said it is untested |
|
Before nightly there are at least |
|
On |
|
Consider that Rust policy for releases is: "a new one every 6 weeks". And there are three channels: stable, beta, and nightly. Nightly is rather distant from where you are :) |
alecandido
left a comment
There was a problem hiding this comment.
For the time being it's pretty straightforward. Apart of the increased documentation (that is good), there is just the introduction of mu_r in the internals, and exposure of xi in the interface.
I'd say it is fine :)
What's the problem with DY? If you rerun and it goes away that's LHAPDF's fault: https://gitlab.com/hepcedar/lhapdf/-/merge_requests/27. |
Yes it is, but actually there are still a few failures: Version of Rust for reproducibility: |
Mmm ... I'm still failing: |
|
@felixhekhorn what is |
|
|
@felixhekhorn I see. Before testing you must first compile the CLI with the same features and ideally same build flags, for instance: in the main directory. I should document this somewhere. |
I see - I was hoping that compiling the CLI would be enough (which at least at the beginning I did - I'm not sure for the last run though) now, I'm down to two failures |
|
I still have more: |
|
@felixhekhorn @alecandido please upload your (updated) the test logs, I'm not telepathic yet 😄. |
|
Sorry, it was trivial, solved by myself. I was missing the PDF set, so the actual solution has been: ❯ lhapdf install NNPDF40_nnlo_as_01180P.S.: now there is only one ignored: |
Yes, this is intentional, because the global help command prints the CLI's version number, which would change every commit. That's something I have to fix. |
@felixhekhorn does that also solve your failed tests? |
Unfortunately, no: I'm still on LHAPDF |
|
@felixhekhorn thanks. This is a numerical problem, and caused by the fact that I'm printing the convoluted numbers with too many digits into the plot script. I think this is a good point to reduce them to 7 digits or even less. |
|
@felixhekhorn could you please try again with the most recent |
|
Not yet, still 1 test failing ... test.log there is something truly different ... |
|
This is likely yet another numerical problem. Could you try |
|
yes, it is still failing ... |
|
@felixhekhorn that's interesting, when I use LHAPDF 6.3.0 I can reproduce your failing test... |
|
(Note that this discussion is completely off-topic ;-) but okay already too late ... ) so I tried to upgrade to LHAPDF 6.4.0, but now I get a whole new bunch of new errors which I suspect are all related to LHAPDF: test.log still, I can run Moreover, looking at the ChangeLog I can't see an obvious change of interpolation (which we are seeing) (except maybe? the change on 2021-09-16) |
|
And outside the test I can run e.g. |
|
Just to be sure, try to cancel your Of course you tried to check with the CLI and Python package the LHAPDF version and they are actually telling |
|
On-topic: looks good to me. At this point we really need a test case... |
|
@felixhekhorn I'm OK with you merging this into |
|
@cschwan although scheme B is not fully solved yet - can we merge this branch? |
This should close #133
pineapplpinekocounter-partcargo testresults intest result: FAILED. 24 passed; 59 failed; 1 ignored; 0 measured; 0 filtered out; finished in 114.04s, but some of this stuff is not coming from my changes, but they fail because "INPUT" != "input" - do I have to use Rust nightly?if I may suggest further:
convolute_eko(so I don't have to run manually and usepineko) (already mentioned by @alecandido )convolute_eko- it is 370 non-trivial lines long ...