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
I realised that because BMS requires both and that they must match. If we allow the user to input their own priors then we need to make sure there is a matching ops dictionary. The simplest way I can see this is to require the user to input both themselves
The text was updated successfully, but these errors were encountered:
Having worked with inputting custom functions, I now believe this change isn't necessary. This is because whenever the user wishes to add their own function to the primitives or to the priors, they would be required to point towards a callable function. Callable functions have the number of arguments as a built-in attribute so we wouldn't need to specify this.
I realised that because BMS requires both and that they must match. If we allow the user to input their own priors then we need to make sure there is a matching ops dictionary. The simplest way I can see this is to require the user to input both themselves
The text was updated successfully, but these errors were encountered: