You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bug where it is possible to define a coord name which is also the same name as a data variable. So we are missing a check for name collisions. This leads to easy to miss downstream errors.
Code snippet above should raise an exception, but does not.
PyMC version information:
pymc version: 5.22.0
Context for the issue:
The issue first showed up as a) correct sampling of random variables with pm.sample, b) re-sampling of random variables when calling pm.sample_posterior_predictive. So what was being returned was actually prior predictive samples, not posterior predictive samples. @ricardoV94 helped me track down that it was caused by a common label for a coord and a data node.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Describe the issue:
There is a bug where it is possible to define a coord name which is also the same name as a data variable. So we are missing a check for name collisions. This leads to easy to miss downstream errors.
Reproduceable code example:
Error message:
PyMC version information:
pymc version: 5.22.0
Context for the issue:
The issue first showed up as a) correct sampling of random variables with
pm.sample
, b) re-sampling of random variables when callingpm.sample_posterior_predictive
. So what was being returned was actually prior predictive samples, not posterior predictive samples. @ricardoV94 helped me track down that it was caused by a common label for a coord and a data node.The text was updated successfully, but these errors were encountered: