-
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
collect
resolves explicit_node
lazily
#1493
Comments
Although, I've just tried running this runcard using the |
I am confused. Funnily enough this works def patata(covariance_matrix):
log.error(covariance_matrix)
return None
x = collect("patata", ("dataspecs",)) dataspecs:
- pdf: NNPDF31_nnlo_as_0118
theoryid: 200
use_cuts: "internal"
dataset_input: {dataset: NMC}
actions_:
- x Could you come up with a minimal example? |
...not to mention that we have
and
and |
...If I had to bet, I'd say that it is some weirdness going on in config.py rather than a problem with reportengine, but not obvious to me so far either way. |
The runcard I posted in the initial post fails for you too right? |
Yes it does, but I couldn't readily understand why. |
This is probably more appropriate for reportengine, but the issue arises in validphys. Consider the following runcard:
This errors complaining that
covmat
is not an array. Taking a look, it's anexplicit_node
instance. If we look at why, it's becauseplot_fancy_dataspecs
takes as an argumentdataspecs_results
which is a collection ofresults
overdataspecs
:nnpdf/validphys2/src/validphys/results.py
Line 1225 in 7305848
and since #1477 was merged, the
covariance_matrix
is dispatched as anexplicit_node
and this is the root of the bug. Theexplicit_node
does not get resolved in time by reportengine and so theresults
objects in the collection don't have thecovariance_matrix
resolved by the time we hit this line:nnpdf/validphys2/src/validphys/dataplots.py
Line 476 in 7305848
The text was updated successfully, but these errors were encountered: