SirStone/SirRoboGarage
1
0
Fork 0
Code Issues 28 Pull Requests Actions Projects Releases Wiki Activity

Decide test adversary — wall bot or spinner for training #161

New Issue
Closed
opened 2026-09-13 20:27:55 +02:00 by SirStone · 1 comment
SirStone commented 2026-09-13 20:27:55 +02:00
Owner
Copy Link
Copy Source

Question

What test adversary should SNNBot train against for this map? Options:

  • Wall bot (drives to wall, reverses, repeat) — linear segments, predictable velocity
  • Spinner (turns in place) — circular motion, constant angular velocity
  • Both (train against one, validate against the other)

Does a suitable adversary already exist in common_libs/test_framework/adversaries/ or elsewhere in the repo? If not, what's the minimal bot to build?

Related: should the adversary fire back? (adds pressure but complicates evaluation)

## Question What test adversary should SNNBot train against for this map? Options: - Wall bot (drives to wall, reverses, repeat) — linear segments, predictable velocity - Spinner (turns in place) — circular motion, constant angular velocity - Both (train against one, validate against the other) Does a suitable adversary already exist in `common_libs/test_framework/adversaries/` or elsewhere in the repo? If not, what's the minimal bot to build? Related: should the adversary fire back? (adds pressure but complicates evaluation)
SirStone added the wayfinder:grilling label 2026-09-13 20:27:55 +02:00
SirStone commented 2026-09-13 20:40:37 +02:00
Author
Owner
Copy Link
Copy Source

Resolution

Adversary is chosen at runtime by the operator, not hardcoded or pre-selected. No new bot will be built for this map.

  • The existing adversary roster (SittingDuck, OscillatorBot, etc.) is used as-is
  • The adversary will fire back — non-firing bots are out of scope
  • Single adversary per training run
  • Operator picks the adversary when launching the test
## Resolution **Adversary is chosen at runtime by the operator**, not hardcoded or pre-selected. No new bot will be built for this map. - The existing adversary roster (SittingDuck, OscillatorBot, etc.) is used as-is - The adversary will fire back — non-firing bots are out of scope - Single adversary per training run - Operator picks the adversary when launching the test
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ready-for-agent
wayfinder:grilling
Wayfinder design question to grill
 wayfinder:map
Wayfinder map issue
 wayfinder:prototype
wayfinder:research
Wayfinder research question
 wayfinder:task
Wayfinder implementation task
No Label wayfinder:grilling
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
SirStone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SirStone/SirRoboGarage#161
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?