-
Notifications
You must be signed in to change notification settings - Fork 7
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
Adding dataset_inputs namespace to old style fits as_input #1197
Conversation
@wilsonmr this seems a bit of a hack but seems like it simplifies things quite a bit down the line. |
At some point I did this in the data keyword PR, I can't remember why I reverted it but I agree it simlifies things. In particular you don't have to write I'm happy for this to go ahead, shall we also update the compfits runcard? Also shall we update the docs (the warning at the bottom of https://docs.nnpdf.science/vp/dataspecification.html for example - I think that's the only place which talks about this but perhaps double checking that doc page wouldn't hurt) Possibly the fit context production rule could also be updated to parse |
Yes, I think that could simplify a lot of this stuff and reduce exposure to "limitations" in reportengine. |
Good spot on the docs Mikey, it's been fixed now. With regards to the comp fits runcard are you referring to the warning around the |
I mean you can now change the compfits input to just take |
So I tried the following modification:
but this greets me with:
I'm probably doing something silly here... |
yeah you need to take the dataset inputs from the fit, not from those custom namespaces (which doesn't contain them if you look above at its definition)
|
but also since |
We happy to merge this chaps? |
could we just run a compfits report and double check the grouping isn't screwed up? |
or if you did that, can you link it here. Then I'm happy to merge |
Good idea, I'll replicate a random one off the vp server |
Thanks! |
Here is one Roy ran and here is the same report but on this branch. Looks identical |
LGTM! |
@wilsonmr I take it the behaviour is well defined and correct if we have both experiments and |
I think it's ok because in the bridging function |
Happy to merge this then? |
This is so that you can do things like:
even though the runcard has an
experiments
namespace instead ofdataset_inputs