You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we make the teams do maths to work out weather markers are ones which they care about.
Filtering the list of returned markers seems to be something which is a challenge for GCSE teams. This is kind of us just having a dumb interface. If the game for a given year has the concept of "their markers" I believe that being able to write code like this would be a good idea:
ifmarker.zone==R.zone:
drive_to_marker(marker)
This would also let us clear up this hack in _draw_bounding_box to make the teams own markers thicker:
Currently we make the teams do maths to work out weather markers are ones which they care about.
Filtering the list of returned markers seems to be something which is a challenge for GCSE teams. This is kind of us just having a dumb interface. If the game for a given year has the concept of "their markers" I believe that being able to write code like this would be a good idea:
This would also let us clear up this hack in
_draw_bounding_box
to make the teams own markers thicker:robot/robot/vision.py
Line 388 in cc98b73
Not sure if this is doing the teams job for them
The text was updated successfully, but these errors were encountered: