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

inference.py, eval.py, demo.py all buggy! #5

Closed
vinjohn opened this issue Oct 31, 2018 · 6 comments
Closed

inference.py, eval.py, demo.py all buggy! #5

vinjohn opened this issue Oct 31, 2018 · 6 comments

Comments

@vinjohn
Copy link

vinjohn commented Oct 31, 2018

Hi, the inference.py, eval.py and demo.py are all buggy in this repo, would you please update a version which can really work?
The train.py is fine.

@yangxue0827
Copy link
Member

can you give me the error information. @vinjohn

@vinjohn
Copy link
Author

vinjohn commented Nov 2, 2018

for R2CNN, everything is fine.
for RRPN, take inference.py for instance:

the build_whole_detection_network need 3 input and return 6 output.

det_net.build_whole_detection_network(input_img_batch=img_batch, gtboxes_h_batch=None, gtboxes_r_batch=None)

however, the implementation of build_whole_detection_network in libs/networks/build_whole_network.py:

build_whole_detection_network(self, input_img_batch, gtboxes_batch)
2 input and 4 return (final_boxes, final_scores, final_category, loss_dict)

the exact error message I get is:
TypeError: build_whole_detection_network() got an unexpected keyword argument 'gtboxes_h_batch'

@yangxue0827
Copy link
Member

please update your code and try again. @vinjohn

@vinjohn
Copy link
Author

vinjohn commented Nov 2, 2018

By the way, I have another question, please help.

The default config for DOTA with base anchor = 256, anchor scales = [0.0625, ..., 2.0], anchor ratios = [1, ... ,1/7]
I think this setting is meant for small and long objects in DOTA.
However, in my own dataset, the default anchor size in faster rcnn is fine (128, 256, 512). I know how to change anchor ratios list back to normal, but not sure about base_anchor_size_list, anchor_scales and roi_scale_factors.

Could you please give me some instructions on config these three parameters?

@vinjohn
Copy link
Author

vinjohn commented Nov 2, 2018

This time the inference is going well, but I think a nms process should be added, anyway, I add it myself.

The anchor scale question, please help, thanks a million!

@yangxue0827
Copy link
Member

base anchor * anchor scales = [16, 32, 64, 128, 256, 512] as the base_anchor_size_list. Anchor ratios = [1, ... ,1/7] controls the shape of the anchor under the same base. roi_scale_factors controls the value of predict offset in a small range. @vinjohn

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