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.

Sign up for GitHub

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

Jump to bottom

Maskrcnn - Different image sizes #165

Open
bitfort opened this issue Jan 10, 2019 · 3 comments
Open

Maskrcnn - Different image sizes #165

bitfort opened this issue Jan 10, 2019 · 3 comments
Labels
Backlog An issue to be discussed in a future Working Group, but not the immediate next one.

Comments

@bitfort
Copy link

bitfort commented Jan 10, 2019

Question: Can you scale the image sizes to all the same size for Maskrcnn?

This is being explored by Google.
@bitfort bitfort added the Next Meeting Item to be discussed in the next Working Group label Jan 10, 2019
@bitfort bitfort added the AI There is an action item here. label Jan 24, 2019
@bitfort
Copy link
Author

bitfort commented Jan 24, 2019

SWG Notes:

Google has early results that suggest this doesn't make a difference. We want to produce more data to support this claim.

@bitfort bitfort added Rec: Rules Change A recommendation has been issued by the Working Group. and removed AI There is an action item here. Next Meeting Item to be discussed in the next Working Group labels Apr 11, 2019
@bitfort
Copy link
Author

bitfort commented Apr 11, 2019

SWG Notes:

For v0.6 we will keep the same image sizes as v0.5. There is broader discussion for how to align this with inference; to be held in STWG.

@petermattson petermattson added Backlog An issue to be discussed in a future Working Group, but not the immediate next one. and removed Rec: Rules Change A recommendation has been issued by the Working Group. labels May 29, 2020
@petermattson
Copy link
Contributor

For 0.6 this was not a change. We should still consider doing it because we don't have a good use case for variable image size. Moving to backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Backlog An issue to be discussed in a future Working Group, but not the immediate next one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bitfort @petermattson