initial setup for arbitrary shape handling #166
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
Hi @developer0hye 👋🏻 This looks like a pretty early version of the PR. I suggest keeping it as a draft until it's ready. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR introduces preliminary changes to prepare support for arbitrary-shaped inputs in the object detection pipeline. Although this change does not yet enable full support for arbitrary shapes, it sets up the necessary internal structure to make that transition possible in the future.
The motivation behind this is to allow more flexible input handling while optimizing computation. By preemptively restructuring certain modules, we aim to minimize redundant operations and reduce computational overhead once arbitrary shape support is enabled.
No external dependencies were introduced in this PR.
Type of change
Please delete options that are not relevant.
How has this change been tested, please provide a testcase or example of how you tested the change?
This PR does not change core logic or output, so existing unit tests were used to validate that the behavior remains consistent. No new test cases are required until arbitrary shape support is enabled.
Any specific deployment considerations
None at this stage.
Docs
(N/A – feature not yet exposed to users)