Skip to content

Consistent use of line thickness #33

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

Closed
g3force opened this issue Mar 15, 2020 · 0 comments · Fixed by #40
Closed

Consistent use of line thickness #33

g3force opened this issue Mar 15, 2020 · 0 comments · Fixed by #40

Comments

@g3force
Copy link
Member

g3force commented Mar 15, 2020

It was brought up on Discord, that there is some confusion in regards of the line thickness:

  • How are distances between lines measured?
  • How is the line thickness taken into account when checking if object are inside an area?
  • When did the ball cross a line?

Current state:

  • ssl-rules
    • 2.1.3: > Lines belong to the areas of which they are boundaries.
  • ssl-vision
    • Distances between lines are measured from the line center
    • Line thickness is configurable and sent out in the Geometry message
    • Line thickness is only taken into account during calibration
  • ssl-game-controller
    • line thickness is not used and not needed
  • TIGERs autoRef
    • The line thickness is not used
  • ER-Force autoRef
    • The line thickness is most likely not used

Some relevant quotes from the rules:

  • "The ball is inside the field."
  • "allowed to be inside the whole center circle"
  • "the ball is inside a team’s defense area"
  • "while being partially or fully inside the opponent defense area"
  • "The robot is at least partially inside the field margin."

The line is usually 1cm thick. The precision of ssl-vision is also about 1cm. So in practice, it should not make a significant difference to take the thickness into account or not.

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

Successfully merging a pull request may close this issue.

1 participant