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

Localisation fails to throw out wrong-side-of-field goalposts #62

Open
josiahw opened this issue Jun 14, 2013 · 4 comments
Open

Localisation fails to throw out wrong-side-of-field goalposts #62

josiahw opened this issue Jun 14, 2013 · 4 comments
Assignees
Milestone

Comments

@josiahw
Copy link
Member

josiahw commented Jun 14, 2013

This creates symmetric localisation problems. Is there a way to throw out wrong direction models based on error before they get dragged into symmetric positions?

@ghost ghost assigned StevenNicklin Jun 14, 2013
@josiahw
Copy link
Member Author

josiahw commented Jun 15, 2013

We have been testing the new behaviour and can confirm that this issue is bad enough to drag the robot to the wrong end of the field while stationary (ie we can't position ourselves sometimes). I think we need very tight throw out checks on goalposts as our distance estimates look like they're a bit all over the place.

@josiahw
Copy link
Member Author

josiahw commented Jun 15, 2013

we can still use bearing information for these objects as this isn't so noisy, but we definitely need to be cautious about distances

@StevenNicklin
Copy link
Member

Are you talking about symmetry on opposite halves of the field or on either side of the same half?

@josiahw
Copy link
Member Author

josiahw commented Jun 16, 2013

opposite halves.

On Sun, Jun 16, 2013 at 10:27 PM, snicklin notifications@github.com wrote:

Are you talking about symmetry on opposite halves of the field or on
either side of the same half?


Reply to this email directly or view it on GitHubhttps://github.com//issues/62#issuecomment-19511639
.

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

No branches or pull requests

2 participants