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
The nn.range_over_dim is too complicated just to get the running index i in the loop. In RETURNN, we have :i for that. Although that support of :i is a bit incomplete, so it might make sense to use a RangeInAxesLayer internally. But this could stay internally, and we could introduce sth like loop.i.
Note on i: Internally, we cannot always use nn.range_in_axis. This is only possible when the length is already known. If the length is not known, it has to be dynamic somehow. It's not clear what the best solution is.
This is maybe a collection of multiple issues.
Consider the example from the test case
test_loop_axis_indices
:There are multiple problems here:
nn.range_over_dim
is too complicated just to get the running indexi
in the loop. In RETURNN, we have:i
for that. Although that support of:i
is a bit incomplete, so it might make sense to use aRangeInAxesLayer
internally. But this could stay internally, and we could introduce sth likeloop.i
.loop.stack(i)
in the end is a workaround because there must be some stacked output. This is RecLayer without accumulated output but just last frame returnn#1029.The text was updated successfully, but these errors were encountered: