Use python CommonData#1650
Conversation
|
We are going to have a pr for the closure test data soon. |
|
Good. I guess is this branch? https://github.com/NNPDF/nnpdf/compare/python_closure_sampling If so there seem to be no overlap with the changes of this PR so when both are merged it should be possible to remove libNNPDF at last. |
|
Cc @comane |
|
Would be good if the export functions were more layered, providing ways to dump the individual files to any streams, mirroring what we have in commondataparser. Among other things, this help us to test easily that writing and reading roundtrip. These lower level things might go in commondata parser. |
|
I didn't check whether they were the same but are they not included in the #1651? Or those are yet something different which is closure test only? |
|
I guess that part does overlap. |
|
Yes, but it is not destructive overlap. When that one is merged the |
|
Greetings from your nice fit 🤖 !
Check the report carefully, and please buy me a ☕ , or better, a GPU 😉! |
|
This is now ready for review. As far as I can test there's nothing broken. Added @andreab1997 as a reviewer in case this touches the covmat in some way. I think it shouldn't because the thcovmat was freed from |
|
@Zaharid did you have a look at this? @andreab1997 please, have a look as well |
|
I'd like to merge this by the end of the week if there are no blocking issues with it. I'd create a tag before the merge as the last version that still uses |
alecandido
left a comment
There was a problem hiding this comment.
It is fine as it is, apart from LegacyCommonData still being used.
All the other comments are mainly to improve style and consistency, but do not consider them blocking.
Co-authored-by: Alessandro Candido <candido.ale@gmail.com>
|
RE If then there are functions that are just there and not being used (it wouldn't be the first time) I'll just remove them. |
|
I am inclined to merge this as is, provided various tests pass. |
|
Please give me this afternoon to have a look at it. Mainly just so I know exactly what this PR does, but might as well take the opportunity to provide some comments if I have any. |
|
Greetings from your nice fit 🤖 !
Check the report carefully, and please buy me a ☕ , or better, a GPU 😉! |
Co-authored-by: Roy Stegeman <roystegeman@live.nl>
There has been a half-finished, half-used
pythonversion of theCommonDataobject for a whilennpdf/validphys2/src/validphys/coredata.py
Line 202 in 9d57bb0
This PR completes so that it can be used everywhere.
This still doesn't allow to remove
libNNPDFbecause the generation of closure test data is still done fromlibNNPDF. Is there someone in Cambridge dealing with that at the moment @Zaharid ?If not I could also have a go at that after this is merged.
Note that I have not attempted to fix any possible design problems there could be with the python version of the
CommonDataor with how thelibNNPDFwas used. This is just a conversion so that when we move to the new commondata I only have to port one type ofCommonDatainstead of two.TODO