Enable Interpolated prior saving
Right now Interped
is the only prior type that can not be consistently be saved and loaded. We should fix this eventually.
Maintenance will be performed on git.ligo.org, containers.ligo.org, and docs.ligo.org on Tuesday 22 April 2025 starting at approximately 9am PDT. It is expected to take around 30 minutes and there will be several periods of downtime throughout the maintenance. Please address any comments, concerns, or questions to the helpdesk. This maintenance will be upgrading the GitLab database in order to be ready for the migration.
Right now Interped
is the only prior type that can not be consistently be saved and loaded. We should fix this eventually.
mentioned in merge request !198 (merged)
marked this issue as related to #193 (closed)
Note, this is essentially the same issue (for interpolated priors) as for #193 (closed) - i.e., the __repr__
needs to be fixed so that the prior can be instantiated from it. Of course, for interpolated priors there is the additional complexity of storing the array somewhere.
As noted in the other issue, #193 (closed) is resolved in !196 (merged) along with many other repr issues. Interpolated priors are the only priors for which !196 (merged) is not the fix
added Bug label
changed milestone to %0.4.0
mentioned in commit 7c1cb86a
changed milestone to %Future
mentioned in merge request !500 (merged)
mentioned in issue #355 (closed)
Closing this as this is possible by using the json
prior format.
closed