-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Should Categorical broadcast? #2082
Comments
Here's another edge case. The output is all zeros with shape (10, 4). To me, this suggests the variable is just taking the first row and discarding the rest silently...
|
pymc2 definetely did assume normalization along a particular 2D array axis: |
IMHO, the following should also raise an exception but does not:
|
I agree that the |
I think we ought to have a dimension argument that distinguishes the dimension of the distribution from the number of variables. We've had this discussion in the past, but have failed to come to a consuensus. |
The most promising effort on this was done by @brandonwillard on #1125. |
The current status on this issue is that the last axis of |
What is the intended behavior when passing a 2D array into Categorical?
I was somewhat expecting to see [0, 1, 2, 3], assuming some sort of broadcast.
Also: do others find it alarming that the pymc3 Categorical automatically normalizes the input p vector to sum to 1.0? To me, having an exception on un-normalized input was an important sanity check in pymc2. This would be particularly true if 2D inputs are tolerated, in which case row vs. column normalization is always an issue.
The text was updated successfully, but these errors were encountered: