-
Notifications
You must be signed in to change notification settings - Fork 30
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
change defaults: @addlogprob! not included in PriorContext() #580
Comments
IMO (at first glance at least) the current default is reasonable since That being said I think the syntax could be improved: #390 |
what about setting up another macro (e.g. the request is triggered by the fact that some backends care about the context. I agree, from a user perspective that this should not be relevant. hence, my desire to have a simple one-line solution |
I think #390 would be cleaner than a separate macro - in Turing, every tilde statement is either an assumption ("prior") or an observation ("likelihood"), so stating explicitly to which category the custom log density calculation belongs would rule out any confusion (and could ideally be treated correctly then also when someone implements eg a custom prior context, which |
I'm very happy with adopting the syntax in #390 tbh. Shouldn't be too difficult to implement either? |
#390 is suggesting to have an option after the macro call, right? if so, sounds good to me |
Would it be possible to change the default behavior for
@addlogprob!
and not have it included in thePriorContext()
I understand the current solution is to do this:
as in the default is that it is included.
In my use case (see this issue) it would make the syntax much more user-friendly for end-users
The text was updated successfully, but these errors were encountered: