Conversation
Commit 79604bd had introduced a level of indirection on the inputs of groups_chi2_table to make sure that the data wasn't being reshuffled too much. This however was not propagated to the actions that internally made use of that functionality, of which there are three. Fix the simpler one to use the original action with the right grouping and add an additional collect over processes for the ones in the theory covariance matrix module.
|
I tried running the following runcard and it does not result in an error anymore. Anyway it looks like that the two tables of the output report (Experimental chi2 by dataset and Total chi2 by dataset) are grouped in a different way (the first by experiment and the second by process) despite the fact that they are generated by the same function (groups_chi2_table). Looking into that I noticed that the function is actually called twice but in the first case groups_data has three entries corresponding to the experiments and in the second case it has only one entry corresponding to the only process (DIS CC). Is this a bug or am I missing an entry in the runcard? @Zaharid |
I found that this problem is related to these three collect nnpdf/validphys2/src/validphys/results.py Line 184 in 3fa10e6 nnpdf/validphys2/src/validphys/results.py Line 663 in 3fa10e6 nnpdf/validphys2/src/validphys/results.py Line 803 in 3fa10e6 which groups data "by_metadata". However the theory+experimental table is done by the function which calls groups_chi2_table with other inputs. Changing "by_metadata" to "by_process" in the three collects above fixes the problem but I am not sure this is the right way of fixing it. @Zaharid |
|
@andreab1997 It should work so that actions used elsewhere such as |
@Zaharid yes, you're right. I've defined new collects for groups_data and groups_chi2 (but not for groups_each_dataset_chi2 because it is only used here). |
|
We have been looking at this functions and I wonder whether it doesn't make more sense to scratch them all and use what we use normally i.e., |
|
Is this good to merge? |
|
I would need to go through it, the server was down so I couldn't even run reports :_ I'll test it next week. |
There was a problem hiding this comment.
I think this is fine https://vp.nnpdf.science/UggLD0bKRouUZHnBOKsBfQ==/
other than the fact that the table header says group when it is actually datasets but that's not what this PR is fixing. Once it's merged we can open a new issue with that.
|
Great, thanks. |
Commit 79604bd had introduced a level of indirection on the inputs of
groups_chi2_table to make sure that the data wasn't being reshuffled too
much. This however was not propagated to the actions that internally
made use of that functionality, of which there are three.
Fix the simpler one to use the original action with the right grouping
and add an additional collect over processes for the ones in the theory
covariance matrix module.
Closes #1520.