-
Notifications
You must be signed in to change notification settings - Fork 225
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
vi
should not work with Matrixvariate distributions
#1545
Conversation
Pull Request Test Coverage Report for Build 568545271Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
Codecov Report
@@ Coverage Diff @@
## master #1545 +/- ##
==========================================
- Coverage 82.21% 81.49% -0.73%
==========================================
Files 21 21
Lines 1406 1421 +15
==========================================
+ Hits 1156 1158 +2
- Misses 250 263 +13
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
@torfjelde is this related to the more general |
In a very indirect way, yeah. It's related because we want to drop the assumption that input and output are of the same shapes from Bijectors.jl, which we really need something like Batching.jl to do properly. |
CI is passing after using the most recent Bijector release. Let's merge this PR for now since it's taking quite a bit of time already; the code only affects |
Issue
TuringLang/Bijectors.jl#169
This happens because
Bijectors.Stacked
is only being compatible with 0- and 1-dimensional inputs. To "fix" this I've added aVec
bijector which wraps any higher-than-1-dimensional bijector with a "flattening" operation.Now works
Questions
Vec
bijector as it's a bit "hacky". Ideally we'd be able to specify both input- and output-dimensionality (in full generality, ideally spaces rather than just dimensionality, but this seems non-trivial), but we did not do this from the get-go due to additional complexity for both user and implementer. So should we keepVec
here as a way of only fixing this particular issue or should I move it to Bijectors.jl so it's available there to? I'm slightly in favour of the last option.