-
Notifications
You must be signed in to change notification settings - Fork 6
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
Provide an unique truth for all theory cards #2028
Conversation
At the moment if you see |
Co-authored-by: Felix Hekhorn <[email protected]>
Thanks @andreab1997, let's have next week as the target to merge this With respect to the missing items:
I think this can be decoupled
I'll add this to #2037 (but I think it can also be decoupled) |
Ok agreed. Do you want me to do something before merging it? |
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.
Some comments.
Co-authored-by: Juan M. Cruz-Martinez <[email protected]>
Co-authored-by: Giacomo Magni <[email protected]>
Co-authored-by: Giacomo Magni <[email protected]>
Co-authored-by: Giacomo Magni <[email protected]>
Co-authored-by: Giacomo Magni <[email protected]>
Co-authored-by: Giacomo Magni <[email protected]>
Co-authored-by: Felix Hekhorn <[email protected]>
add nnpdf4.1 baseline theorycard
Since I believe this is almost final, don't forget to update (the |
One thing I just realised is that by having defaults we make it even harder to search within the theorydb based on theoryparameters. Of course I'll concede that since they are the defaults it's probably not particularly useful to use it as a filter |
Having defaults doesn't mean we should not fill in a value. The main goal of the defaults is for the old runcards not to fail and allow us to remove some keys going forward. So, even if some keys are added with a default we can decide that new theories must have a value defined (while leaving old theories alone). For now in #2062 |
But all old theories have an explicit entry for e.g. alphas (and all other values that are given defaults in this PR), so why would those not be made mandatory now. There is no need to give defaults for older theories |
The idea is that some of the values in the old theories were either redundant or not needed. But maybe we were overeager and there's some that have been moved to optional that shouldn't be. (if so, please mention which ones are those and we can make them mandatory again!) |
wrt to this PR I would not add defaults for MaxNfPdf, Q0, Qref, alphaqed, HQ |
Add (and use) a default for IterEv
Greetings from your nice fit 🤖 !
Check the report carefully, and please buy me a ☕ , or better, a GPU 😉! |
If nobody is explicitly against this, I'll merge this PR on Thursday. @RoyStegeman I'd appreciate a second look at the 41000000.yml file since I've made a few changes. |
As you know I'm happy with explicitly defining parameters in the runcard instead of relying on the defaults, so for me this is not a huge problem, but |
I also prefer having explicit values even if defaults are defined. |
Good, other than that 41000000.yml seems fine |
Here we address #2019.
dataclass
collecting all the possible parameters that can appear in a theory card, removing the ones that are not used anymorepineko
cc @scarlehoff