You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The thing which is perhaps non-obvious from a user perspective is providing coords via the pm.MutableData, which is totally different from when you provide coords via pm.Model.
Currently, the API for doing out of sample inference with coords (that change dimensionality) is not the easiest. You have to specify the coords as mutable by adding as a kwarg within the pm.MutableData, which is a bit non-obvious and potentially a little clunky.
I don't propose that we remove this, but the API which is really begging to exist is to be able to provide a mutable_coords kwarg to pm.Model.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Before
The thing which is perhaps non-obvious from a user perspective is providing coords via the
pm.MutableData
, which is totally different from when you providecoords
viapm.Model
.After
Context for the issue:
Currently, the API for doing out of sample inference with coords (that change dimensionality) is not the easiest. You have to specify the coords as mutable by adding as a kwarg within the
pm.MutableData
, which is a bit non-obvious and potentially a little clunky.I don't propose that we remove this, but the API which is really begging to exist is to be able to provide a
mutable_coords
kwarg topm.Model
.The text was updated successfully, but these errors were encountered: