-
Notifications
You must be signed in to change notification settings - Fork 241
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
BudgetOptimizer
does not seem to support time-varying intercept
#757
Comments
BudgetOptimizer
does not seem to support time-varying intercept
Hi @AlfredoJF, CC: @cetagostini |
It seems like a broadcasting issue right @wd60622 ? |
Hi @wd60622, no issues with the Out-of-sample posterior only with the y_test_pred = mmm.sample_posterior_predictive(X_pred=X_test, extend_idata=False, include_last_observations=True) |
Hi @AlfredoJF, |
Hi @wd60622, Yes, I'll post a reproducible example and leave the investigation to the experts for now. :) |
Great, sounds good. We a reproducible example, we can dig into it a bit better. |
Hi @wd60622 I used the mmm and tvp example data to see if I could create a reproducible example for further investigation but I did not get the same error as in my model. I cannot share my dataset as it contains client's data but will try to create another dataset for this purpose. Thanks for the patience! |
@wd60622 Yes, I'm using 0.7.0 and have overwritten the MMM class for now as I'm closer to the delivery date of my project. I'll upgrade to 0.8.0 once it's released in a future iteration of my model |
Sounds good. Well glad that it sorted itself out. I will leave this issue open for now |
Not quite sure if this will be fixed in the upcoming
0.7.0
release but noticed the re-written BudgetOptimizer does not work with time-varying intercept or there's a conflict withPyTensor
.I followed the mmm_budget_allocation_example.ipynb and in this cell was when I got the error.
Here is the error I got using an MMM with tvp that did not come up with another MMM without time-varying intercept:
The text was updated successfully, but these errors were encountered: