Fix compatibility with PyMC>=5.16#484
Merged
Merged
Conversation
Closed
This was
linked to
issues
Jul 10, 2024
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In PyMC>=5.16, which depends on pytensor>=2.23.0, the way to define
RandomVariableclass has changed to use asignatureclass property, which requires changes in HSSM codebase. In this PR, the following was changed:ndim_suppwhich is no longer supported in pytensorextra_fieldsis passed due to this change.extra_fields, once defined, can no longer be changed (we will remove support forextra_fieldsfor a different class for RL support in the future. This is just a temporary fix)