You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Question: we're talking about test within nnpdf, right? i.e. on FK tables?
then maybe some basic things first:
check the thing is loadable
check it yields a number when convoluted with NNPDF40_qed
check it has a theory metadata key
EW parameters are compatible
now, this is a much more basic problem: do you really want to check theory compatibility? this has a non-trivial tail ... because it would extend to everything and that means backwards compatibility ... e.g. PTO, kThr, FNS, masses, etc.
same goes for the eko side: do we want to check that settings are compatible?
Question: we're talking about test within nnpdf, right? i.e. on FK tables?
No! Yes, within NNPDF but only on the XXX.yaml file. Downloading the theories in the CI and testing is not feasible so for that we just need to hope people is doing something sane.
because it would extend to everything and that means backwards compatibility
I would only do it for new theories, just making sure that newly added theories don't have incompatible values.
While it is too late for the ones we already have, we should check (as much as possible) that the theories are correct going forward.
The idea would be that theories here, when they have the new naming format (4xxxxxxx) are checked. Some possible tests, please suggest others:
theories_slim
with the same name and content*.*unless we get around to make pineko use the theories from here, but that needs the set of defaults / mandatory / etc
The text was updated successfully, but these errors were encountered: