Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

class head for different backbone #50

Open
Tommy-Hsu opened this issue Dec 12, 2024 · 0 comments
Open

class head for different backbone #50

Tommy-Hsu opened this issue Dec 12, 2024 · 0 comments

Comments

@Tommy-Hsu
Copy link

Hi @Gengzigang,

Have you tried using different backbones with PCT?

I switched the backbone to HRNet, which produces features of size (batch_size, 72, 96, 48). This is different from the original SwinV2 backbone, which outputs (batch_size, 8, 8, 1024).

However, I noticed that the class head (link: pct_head.py#L175) only modifies the feature channels.

So, in my HRNet version of PCT (link: pct_base_classifier.py#L101), I adjusted the parameters to scale the input size from 2 to 72 * 96 * 2. This roughly matches the parameter count of the Swin backbone, which scales to 8 * 8 * 256.

Despite this, I still find my FPS is slower compared to heatmap-based methods.

Could you share your experience with this? I'd really appreciate your insights!

Thanks a lot!

截圖 2024-12-12 20 50 31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant