Fix how the output tensor is created in CUDA SpaceDepth ops #11302
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
The SpaceDepth ops are just thin wrappers over Transpose in that they do some re-ordering of the input based on a "virtual input shape" of the regular NCHW image input. The output tensor in these ops were being created based on the "virtual otuput shape" of this Transpose operation and then finally reshaped into the NCHW shape before the operation exits. The execution frame has a check to ensure that the requested output shape of the output buffer of the op be the same as the "expected" shape if the op output is also a graph output and if it isn't it produces a warning -
onnxruntime/onnxruntime/core/framework/execution_frame.cc
Line 806 in 4d0214f
The existing op unit tests should keep this change covered.
Motivation and Context
Fix jarring warning seen by user in #11274