-
Notifications
You must be signed in to change notification settings - Fork 199
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
parameter behavior during Prior.constrain
#1015
Comments
We should add a test :) |
Prior.constrain
doesn't work with preliz.maxent
Prior.constrain
Not documented anywhere either. Do you have any thoughts on behavior? We can go with whatever is most intuitive |
PreliZ's maxent does not need the user to specify an initial guess. This behaviour is documented in the docstring for |
Ah, was looking in the docstring. Would be good to add there or clarify in one of existing examples there The current error is pretty cryptic. Maybe a good check to add to the preliz BTW. Didn't know about that prior explorer linked. Very cool |
It is already in the docsring https://github.com/pymc-labs/pymc-marketing/blob/main/pymc_marketing/prior.py#L772-L780. Thanks for the kind comment about |
PreliZ will raise an error if the distribution passed to maxent is frozen, see arviz-devs/preliz#534 |
PreliZ 0.9.1 has been released. Thanks for offering feedback about PreliZ. |
Oh, nice. Thank you for quick adjustments. Will close this for now then |
Seems to be upstream from the
preliz.maxent
. Is there a version restriction required?Think there was a change of behavior, the previous parameters acted as the initial points
The text was updated successfully, but these errors were encountered: