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
I've been examining the models/context_cluster.py file in your GitHub repository and observed that the ordering of the height (H) and width (W) dimensions in some tensor operations, such as adaptive pooling (nn.AdaptiveAvgPool2d) and data rearrangement (rearrange), seems unconventional. Although the input images are square, which might not cause practical issues, I am curious to know whether this ordering is intentional for algorithmic or optimization reasons, or if it was an error in implementation.
Thank you.
The text was updated successfully, but these errors were encountered:
Hi,
I've been examining the models/context_cluster.py file in your GitHub repository and observed that the ordering of the height (H) and width (W) dimensions in some tensor operations, such as adaptive pooling (nn.AdaptiveAvgPool2d) and data rearrangement (rearrange), seems unconventional. Although the input images are square, which might not cause practical issues, I am curious to know whether this ordering is intentional for algorithmic or optimization reasons, or if it was an error in implementation.
Thank you.
The text was updated successfully, but these errors were encountered: