Ordering of inputs to Scan nodes
#1173
alexander-camuto
started this conversation in
General
Replies: 1 comment 1 reply
-
|
You can get more out of the command line with a couple of flags: Source 0 is actually model input 1, while Source 2 is model input 0. The mapping is match in model input order, not the node ids. Hope it helps |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I currently have an RNN of the form:
If we inspect the Scan node more closely it is as such:
The two inputs to the scan node are
3/0>and2/0.Outlet 3/0 (not seen) is a
Constnode of shape[1,3]. Whereas (2/0) is of size[batch_size,1,3]. And theinput_mappingmakes sense to me in that it has order[State, Scan(ScanInfo { axis: 0, chunk: 1})]:3/0is the initial state node, and (2/0) is the input we slice over at each iteration of theScanloop.However once we look at the Scan node's subgraph the sources are in the following order:
It sort of seems like:
[batch_size,1,3]which when sliced is of size[1,1,3]).[1,3]and State).However the ordering of sources and inputs here seems to imply otherwise.
I was wondering if Claim A and B are correct here and if so where / how are the wrapping node's inputs matched to the corresponding Scan Subgraph's sources ?
Attached you'll find the RNN in question:
network.onnx.zip
Beta Was this translation helpful? Give feedback.
All reactions