-
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
ekobox unittests #109
ekobox unittests #109
Conversation
felixhekhorn
commented
Mar 21, 2022
- moved some code from benchmarks back to tests (those unrelated to lhapdf)
Codecov Report
@@ Coverage Diff @@
## feature/composite-output #109 +/- ##
============================================================
+ Coverage 99.51% 99.60% +0.09%
============================================================
Files 39 51 +12
Lines 2684 3055 +371
============================================================
+ Hits 2671 3043 +372
+ Misses 13 12 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@andreab1997 please take a look to also I'm not really convinced of providing default runcards from banana: 1. are we really sure we want to do this? (instead of sticking to our default-less scheme - and in NNPDF we always have full runcards) and 2. if still, I don't think we should inherit from banana: our default theory there is FFNS3 which is good for debugging, but stupid in production ... |
Yes I'll take a look. Probably is only a matter of changing some names in evolven3fit.
I have not a strong opinion on that. I believe that for users having some defaults is good because most of them would only use a few of the runcards options. However maybe we can provide less and more "standard" defaults. |
Anyway, I really like the new names. The old ones were very confusing |
you know whom to blame 🤣 😇 |
yes, myself! xD |
I changed the names on evolven3fit and everything should work again |
Mmm that might have been premature ... you maybe want to stash that commit until this branch is released on main, which might take a while ... |
Oh I see. Yes I will do that |
@alecandido maybe consider to merge this PR first before continuing on #105 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed half, and never run. I'll do both, but for the time being I submit current comments.
For me this is fine, I'm going to merge and continue the development on the other branch. |