-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Ordered bijector #7
Comments
Hi! If I am understanding this correctly, this wouldn't be a bijection. Consider the vectors [2.1, 3., 4.], [3., 2.1, 4.] and [4., 3., 2.1]. All of them would map to [2.1, 3., 4.]. However, bijectors has been extended to a certain subclass of non-bijective transformations (e.g. there is an AbsoluteValue bijector), so I could see the same treatment being done here (because given a vector of length k, every preimage set is of cardinality k, up to multiplicity.). |
I misspoke and meant to say the preimage set is of size k! (every permutation). |
To generate an ordered vector |
So I understand this is for the bijective "ordered transform" described in section 35.5 of the Stan reference manual v. 2.17.1? I might give this a try, though it might take a while. |
@mrosenkranz I actually just sent a PR implementing the ordered transformation tensorflow/tensorflow#18647. |
Thanks for the clarification Bob and Junpeng! Given that order statistics is also something that can be a valid bijector, I was a little confused :). @junpenglao, currently reviewing your PR. Apologies for any delays, since I am still familiarizing myself with the github review tools. |
Perhaps obvious, but this is only true for IID after the ~ |
Constrain a vector/tensor being ordered along a specific dimension.
The text was updated successfully, but these errors were encountered: