Skip to content
This repository has been archived by the owner on Sep 2, 2019. It is now read-only.

Need cleaner removal checks - currently in RobocupHacks #47

Open
shannonfenn opened this issue Jun 7, 2013 · 2 comments
Open

Need cleaner removal checks - currently in RobocupHacks #47

shannonfenn opened this issue Jun 7, 2013 · 2 comments
Assignees
Milestone

Comments

@shannonfenn
Copy link
Member

This is not urgent as the checks that are being done are valid (i.e. balls that are inside the quadrilateral found for a goal are being removed) but this should be done in a cleaner way, perhaps a post processing method that considers all detected object types as a collective rather than purely finding each one individually.

@ghost ghost assigned shannonfenn Jun 7, 2013
@josiahw
Copy link
Member

josiahw commented Jun 7, 2013

Maybe a good way to do it would be add a filter call at the end of vision which removes ridiculous objects?

Sent from my iPad

On 07/06/2013, at 4:51 PM, Shannon Fenn notifications@github.com wrote:

This is not urgent as the checks that are being done are valid (i.e. balls that are inside the quadrilateral found for a goal are being removed) but this should be done in a cleaner way, perhaps a post processing method that considers all detected object types as a collective rather than purely finding each one individually.


Reply to this email directly or view it on GitHub.

@shannonfenn
Copy link
Member Author

Probably, it essentially needs to be another small stage. Objects that are rediculous in and of themselves are removed during the detection process, but there also needs to be consideration for object type combinations that are rediculous, for example balls that are between the edges but above the base of a goal post etc.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants