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
In other words, we implicitly broadcast ~ statements when the RHS is of lesser tensor rank (scalar, vector, matrix, etc.) than the LHS. We only do this for observations, for assumptions we require the use of .~ for univariate distributions or loops for multivariate ones.
Are we sure we want to keep supporting this long-term? I find it confusing for the same reasons I described in #825 (comment), namely that it muddies the distinction between distributions of different tensor rank and goes against Julia's broadcasting conventions, such as disallowing things like [0.1, 0.2] + 1.0. Also, the univariate cases can trivially be changed to use .~ instead. The multivariate cases would require loops.
This issue is kinda the mirror image of #825. This arose originally from a question of why does tilde_observe call loglikelihood when tilde_assume calls logpdfhere.
The text was updated successfully, but these errors were encountered:
We currently allow this:
In other words, we implicitly broadcast
~
statements when the RHS is of lesser tensor rank (scalar, vector, matrix, etc.) than the LHS. We only do this for observations, for assumptions we require the use of.~
for univariate distributions or loops for multivariate ones.Are we sure we want to keep supporting this long-term? I find it confusing for the same reasons I described in #825 (comment), namely that it muddies the distinction between distributions of different tensor rank and goes against Julia's broadcasting conventions, such as disallowing things like
[0.1, 0.2] + 1.0
. Also, the univariate cases can trivially be changed to use.~
instead. The multivariate cases would require loops.This issue is kinda the mirror image of #825. This arose originally from a question of why does
tilde_observe
callloglikelihood
whentilde_assume
callslogpdf
here.The text was updated successfully, but these errors were encountered: