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

Weight persistence and hybrid seeding #85

New Issue
Closed
opened 2026-08-25 19:12:04 +02:00 by SirStone · 0 comments
SirStone commented 2026-08-25 19:12:04 +02:00
Owner
Copy Link
Copy Source

Parent

#80

What to build

Save and load champion weights so rematches start warm. Per-opponent weights keyed by enemy bot name (~6KB each, 745 floats). Global fallback file overwritten with latest match champion after every match.

Load order at bot startup: per-opponent → global fallback → random init.

Hybrid population seeding from loaded weights: ~25% of population initialized as mutated clones of loaded champion (exploitation), ~75% random (exploration).

Acceptance criteria

  • Champion weights saved per-opponent after each match, keyed by bot name
  • Global fallback weights overwritten with latest champion after every match
  • Load order: per-opponent → global fallback → random init
  • Hybrid seeding: ~25% cloned+mutated from loaded champion, ~75% random
  • Rematch against same opponent starts from saved weights — no re-evolution from scratch
  • Self-check: when isMainModule with doAssert validates save/load roundtrip (write + read back = identical weights)

Blocked by

## Parent https://git.fossellini.top/SirStone/SirRoboGarage/issues/80 ## What to build Save and load champion weights so rematches start warm. Per-opponent weights keyed by enemy bot name (~6KB each, 745 floats). Global fallback file overwritten with latest match champion after every match. Load order at bot startup: per-opponent → global fallback → random init. Hybrid population seeding from loaded weights: ~25% of population initialized as mutated clones of loaded champion (exploitation), ~75% random (exploration). ## Acceptance criteria - [ ] Champion weights saved per-opponent after each match, keyed by bot name - [ ] Global fallback weights overwritten with latest champion after every match - [ ] Load order: per-opponent → global fallback → random init - [ ] Hybrid seeding: ~25% cloned+mutated from loaded champion, ~75% random - [ ] Rematch against same opponent starts from saved weights — no re-evolution from scratch - [ ] Self-check: `when isMainModule` with `doAssert` validates save/load roundtrip (write + read back = identical weights) ## Blocked by - https://git.fossellini.top/SirStone/SirRoboGarage/issues/84
SirStone added the ready-for-agent label 2026-08-25 19:12:04 +02:00
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 ready-for-agent
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#85
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?