However, during optimization I was confronted with error messages:
...
TypeError: 'TensorSpec' object is not subscriptable
and I had a hard time to understand the reason for it. After a long debugging session I figured that the input shape was actually changed to [224, 224, 1] during the parsing stage and the error came due to a mismatch of shape of the data generator.
A decent error message (shape check?) would have been helpful here. You may consider that for future versions of the dataflow compiler.
It took me some time to become aware of this as there are just fuzzy error messages from framework internals being raised that I didn’t find helpful. Do with this note whatever suits you.
Hi @andre.koehler, your point is valid there are two approaches for the Tensor representation NHWC (N=batch, Height, Width, Channels) and NCHW. We use the first, while ONNX uses the first, so there is need for this switch.