-
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
Implementing input checks. #12
Conversation
@scarrazza can you link me the place where the input parsing is made in nnpdf, please? |
Sure, here the cuts example: https://github.com/NNPDF/nnpdf/blob/master/validphys2/src/validphys/cuts/filters.yaml |
Codecov Report
@@ Coverage Diff @@
## develop #12 +/- ##
============================================
+ Coverage 51.15% 66.81% +15.65%
============================================
Files 39 44 +5
Lines 1386 1600 +214
============================================
+ Hits 709 1069 +360
+ Misses 677 531 -146
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Task linked: CU-8jnv9d Input checks |
Maybe cross-constraints will be deferred to merge the domains. Tests still required (probably) before merging. Runner integration also. |
I will implement the input checks already made in APFEL (just as they are for the moment), hopefully in a more readable fashion.
Inspector
call in runnerUPDATE: defaults are not going to be implemented at all, because we prefer to provide examples and force the user to fully specify the input runcard