-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Parameters for smaller images #371
Comments
I am also interested in the proposal. From my viewpoint, you can resize the image to smaller size. RCNN actually accepts the image of 224 x 224. |
Hi,@haihaoshen |
Yes, but for scoring, no matter the image size is resized (to 224 x 224) or On Fri, Oct 28, 2016 at 9:23 AM, 小郭 notifications@github.com wrote:
|
I was with the same problem, but when I change the parameter of images sizes in config.py script inside lib/fastrcnn the detections were very high and solve my problem. |
Thanks for note. Which parameter in config.py did you change? I saw the
below two may relate to input image size.
…__C.TRAIN.SCALES = (600,)
__C.TRAIN.MAX_SIZE = 1000
On Wed, Nov 30, 2016 at 2:43 AM, acpn ***@***.***> wrote:
I was with the same problem, but when I change the parameter of images
sizes in config.py script inside lib/fastrcnn the detections were very high
and solve my problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#371 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB46ZMn08WIpsPId0gGynVyLcoXYFIAjks5rDHI2gaJpZM4KSWR4>
.
|
Exactly that, remember of change in test stage too in the same script. |
Thanks for your confirmation.
…On Tue, Dec 6, 2016 at 1:20 AM, acpn ***@***.***> wrote:
Exactly that, remember of change in test stage too in the same script.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#371 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB46ZHxlA3s4a_DDA5b7dHJ6MbDzvRACks5rFEftgaJpZM4KSWR4>
.
|
Did only changing the image input size work for detecting smaller objects ? |
@harjatinsingh I don't think only resize the input image would work a lot for detetecting small objects because key parameters of detection are anchor size and featstride in the region proposal networks. |
@absorbguo Thank you for the reply. I have understood the use of anchor size and fixed it, however i am not able to understand the use of feat_stride parameter. Can you point me in the right direction to learn about the meaning of feat_stride ? |
@harjatinsingh In short, smaller featstride represents denser anchor boxes, larger featstride represents sparser anchor boxes. Denser anchor boxes means predicting more proposal in the same area compared with sparser anchor boxes.You can review the generator.py for more details. |
@absorbguo Thank you. |
can not only change __C.TEST.SCALES = (1080,) __C.TEST.MAX_SIZE = 1920 what else should i change? @absorbguo |
Hi, so I'm trying to train Faster R-CNN on a dataset of pretty small images (85x29). As far as I'm aware, when given such an image, Faster R-CNN expands it to be 1000x600, then this image goes through the neural network. But with default parameters for stride and base anchor size, which are 16 pixels (on the expanded image), isn't it like producing 9 identicall 1x1 ancors for each pixel of the original image (since it is more than 200 times smaller, 16 pixels on the large image equals less than a pixel on the small one)?
Do I get it right? And if so, should I greatly increase stride and anchor size for it to work with smaller images? Or is it better to change those 1000x600 sizes and not expand the image so much? Thank you.
The text was updated successfully, but these errors were encountered: