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

Is the stride or feature map size influence the NME? #44

Open
CPFelix opened this issue Feb 13, 2023 · 2 comments
Open

Is the stride or feature map size influence the NME? #44

CPFelix opened this issue Feb 13, 2023 · 2 comments

Comments

@CPFelix
Copy link

CPFelix commented Feb 13, 2023

I trained on my dataset and use the input size 64X80, and found the NME is larger than the regression method before used, and when I modified the input size to 256X256, NME is lower than before. @jhb86253817

@CPFelix
Copy link
Author

CPFelix commented Feb 13, 2023

And I'm also curious about the loss weight.Why cls_loss_weight is bigger than reg_loss_weight, according to my analysis, the cls is easier than reg, and reg loss should be important to the final NME.
Thanks for pointing out my mistake!

@jhb86253817
Copy link
Owner

Hi @CPFelix ,

  1. For PIPNet, if the input size is changed to 64x80, it may cause some problems.
    (a) E.g., 80 is not divisible by the power of 2 (the network stride), which may introduce error for localization.
    (b) Since ResNet has Stride 32, your heatmap has size 2x2, which is a bit meaningless for doing heatmap regression. You may need to reduce the stride of the backbone so that the size for heatmap regression and coordinate regression is balanced.
  2. I used larger weights for cls_loss so that its loss scale is comparable to reg_loss. Although cls is easier than reg, it is also important. Anyway, you may also try adjusting the weights see if improves.

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

2 participants