-
Notifications
You must be signed in to change notification settings - Fork 130
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
Enforce dim tags to be unique in tensor #632
Comments
This obviously introduces new behavior. So it could be introduced via a new behavior version (#508). However, the question is whether this behavior should be enforced on everyone. A new behavior version usually implies for an easy transition of old code to new code. But this is a case where it might be a bit non-trivial in some cases. Instead, we could introduce this as a behavior flag. Some config option like |
We now stumbled upon a case where there is no clear obvious solution on how to avoid ambiguous tags in a tensor, namely for the weight matrix of linear transformations with This is also shown here: rwth-i6/returnn_common#17 (comment) One potential solution was to introduce some |
The order of axes should never matter.
But when a single dim tag can occur multiple times in a tensor (
Data
), it does matter. E.g. for operations likeSoftmaxOverSpatialLayer
on some input [B,T,T].You can get such tensor e.g. via
DotLayer
.We should disallow this, so that the order of axes will not matter.
The user explicitly would need to change one dim tag before to some new dim tag (e.g. via #633 or #589).
This would be helpful for #391.
The text was updated successfully, but these errors were encountered: