-
Notifications
You must be signed in to change notification settings - Fork 222
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
Model syntax: provide automatically all random variables as argument? #792
Comments
Thanks for your proposal @scheidan and sorry for the late response; this issue somehow slipped through the cracks. I like your proposal of making all random variables potentially observed variables. With #972, it may be possible to support a feature like this quite neatly using an additional model constructor method. Follow #965 for progress on this idea. |
So I tried implementing this but I am not too happy about 3 things:
Given that the value added here is tiny compared to the inconvenience of automatically implementing an imperfect version of this feature, I don't think we should have it in Turing at all. I will close this issue for now. Later when we have Soss interop, perhaps we can borrow this feature from Soss. |
Following the discussion about sampling from the prior and
missing
s (#786), I put some thoughts together about the model syntax. Maybe this is helpful for your refactoring plans.Currently, when we define a model, we already have to decide in advance on which random variables (RV) we want to condition on later. It would be nice to decouple this steps:
This is already possible to a large degree, if we list manually all RV as arguments:
So
model1
andmodel2
are identical, but the later one is much more flexible. Therefore, I was wondering if it is a good idea, to generate something likemodel2
automatically. I could imagine a syntax like this:For vector RV this would need some additional thoughts on how to pass the dimensions.
Conceptually this seems neat, however I cannot judge how difficult such an implementation would be.
The text was updated successfully, but these errors were encountered: