-
Notifications
You must be signed in to change notification settings - Fork 62
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
About vis_rpn_anchors #21
Comments
anchor_proposal is used to generate initial proposals for the network, before the rroi layer refines the (rotated) bounding boxes You would get two rotated bboxes on the same target if their IoU < IoU threshold. Try decreasing the ROI IoU threshold |
thanks. Then what does match_anchors mean |
Is it first match_anchor, then we have to try to train the regression as anchor_proposal |
It's been a long time since I last saw the code, but based on the naming, it probably means anchors that have IoU > RPN IoU threshold. These anchors are fed to the RPN regression layer |
I need help on my case The loss of my training is already very low, why is the result still so bad, is my parameter tuning bad, or is it not enough training |
From the image, the target objects are really small. My guess is that there is a class significant imbalance where there are a lot more invalid region proposals (rotated RPNs) than valid ones. A possible fix is to remove very large anchor sizes (i.e. 256) or really small ones (i.e. 20) that don't fit the objects in the dataset, and start with a simpler model (R-50-FPN). It's generally good to reduce the number of total anchors to i.e. 9-15 anchors. |
let me try |
@mrlooi Sometime, I got
why? |
The error looks to originate from pooling.py. My guess is that the number of initial proposals were small/empty, and after pooling none of the proposals met the passing criterion (could be IoU with ground truth) |
@mrlooi Thank you i understand. And I also want to ask a few questions about RRPN Faster
When I training RRPN Faster and it got stuck, is there anything I haven't changed? |
hmm not sure why but you've posted tensorflow logs |
@mrlooi Thank you. How can I solve @a5372935 problem when number of initial proposals are small/empty? I have got same error: |
I would recommend starting with good RPN anchors. Use the vis_rpn_anchors.py file to visualize the anchors for your dataset. |
@mrlooi I forgot to ask is the brackets after each loss refer to val_loss? |
If I remember correctly, it's the loss for that minibatch. Actually I had a look again into your log : https://drive.google.com/open?id=1HQfS0Fhqf-ABMcQfg9OOGeyOLTcQcett |
Yes, the loss for that minibatch is really high, but I think vis_rpn_anchors are all correct. Why is this? |
Possibly due to version differences. I used torch 1.0 - 1.1 |
❓ Questions and Help
Which one is the match_anchor or anchor_proposal that I should care about?
And, why image has more than two bboxes on the same target when using inference_demo.py prediction, how can I make him output only one bboxes
The text was updated successfully, but these errors were encountered: