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

why using anchors but propoals when matchs proposals and gt? #125

Open
zimurui opened this issue Sep 7, 2022 · 3 comments
Open

why using anchors but propoals when matchs proposals and gt? #125

zimurui opened this issue Sep 7, 2022 · 3 comments

Comments

@zimurui
Copy link

zimurui commented Sep 7, 2022

I an confusing when matching proposals and gt, why laneatt using anchors match but not proposals that model inference.

image

@lucastabelini
Copy link
Owner

Because it results in more stable training. If you use the proposals to match with the labels, the target for the same image may change as the training progresses, which can make the convergence take longer.

@nhduong1203
Copy link

When I train, sometime the regression loss is too large (2000 or 3000) while the classification loss is about 0.5 (4 class). Then I check the code and have the same question. So when the model matching, it don't care about the proposal, so sometime, it's match the anchor with the nearest lane, but the offset corresponding to the anchor is too large or something that make the proposal is much different from the lane, it cause my regression loss is large, right?
Please give me your opinion, thanks you <3.
Sorry for my English not good

@ztianlin
Copy link

If you train from scratch, proposals are randomly distributed at the beginning, which means you may get the wrong match when using proposals to match targets, making it hard for convergence. Instead, if you fine-tune from a well-predicted model, I don't see problems in using proposals.

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

4 participants