-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Problems with pm.set_data() when predicting a single obs and shape of trace changes #3640
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
Comments
This is also discussed in an arviz issue I posted: arviz-devs/arviz#829 |
Thanks for bringing up the problem regarding single new observations @corriebar. I am having the same issue when trying to predict a single new data point stored as Versions and main components
|
These two issues are related |
Is this issue really still open? It sounds like it's been closed elsewhere, but it's difficult to confirm |
Yeah it sounds like it's been fixed, so I'll close this issue so it doesn't clutter our backlog. But if anyone encounters it again with the latest PyMC version definitely let us know! |
I encountered two problems when using
pm.Data()
/pm.set_data()
. (Not sure if they're actually related, or would warrant two issues)When trying to predict a single new observation, I instead get the predictions for the training data.
After I set new data, the trace seems to have changed its shape so that plotting with Arviz breaks. I would expect the original trace to remain unchanged when predicting.
Please provide a minimal, self-contained, and reproducible example.
Please provide the full traceback.
And for the prediction with one observation:
Expected output:
(1000,1)
. Inspecting the returned samples also confirms it is the predictions for the original training data.Versions and main components
The text was updated successfully, but these errors were encountered: