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

GMM-based GA warm-starting from battle history #125

New Issue
Closed
opened 2026-08-29 19:05:26 +02:00 by SirStone · 1 comment
SirStone commented 2026-08-29 19:05:26 +02:00
Owner
Copy Link
Copy Source

What to build

Store historical enemy movement patterns across battles and use them to initialize the GA population, so that the GA converges faster and reaches higher peak fitness.

Currently initPopulationSeeded uses 75% random vectors on every battle start, wasting generations rediscovering patterns the bot has already seen.

Acceptance criteria

  • Historical EnemyState snapshots are persisted across battles
  • On battle start, if history exists, initPopulationSeeded initializes PopSize/4 seeds as centroid + N(0, 0.1 * covariance) perturbations
  • Remaining seeds are initialized randomly (fallback when no history)
  • Cold start (no history) behaves identically to current implementation
  • Fitness improvement visible within first 10 generations vs cold start
  • Existing when isMainModule self-checks still pass

Blocked by

None - can start immediately

Parent

Closes part of #118

## What to build Store historical enemy movement patterns across battles and use them to initialize the GA population, so that the GA converges faster and reaches higher peak fitness. Currently initPopulationSeeded uses 75% random vectors on every battle start, wasting generations rediscovering patterns the bot has already seen. ## Acceptance criteria - Historical EnemyState snapshots are persisted across battles - On battle start, if history exists, initPopulationSeeded initializes PopSize/4 seeds as centroid + N(0, 0.1 * covariance) perturbations - Remaining seeds are initialized randomly (fallback when no history) - Cold start (no history) behaves identically to current implementation - Fitness improvement visible within first 10 generations vs cold start - Existing when isMainModule self-checks still pass ## Blocked by None - can start immediately ## Parent Closes part of #118
SirStone added the ready-for-agent label 2026-08-29 19:05:49 +02:00
SirStone commented 2026-08-29 20:17:46 +02:00
Author
Owner
Copy Link
Copy Source

Implemented in commit a730a9e

Summary: Added GMM-based GA warm-starting from battle history. initPopulationSeeded now seeds PopSize/4 individuals from historical enemy movement patterns (centroid + covariance-based perturbations). Remaining seeds are random. Cold start (no history) behaves identically to prior implementation.

Files:

  • vapourbot_garage/src/vapourbot/ga.nim - initPopulationSeeded(), history persistence logic
Implemented in commit a730a9e **Summary:** Added GMM-based GA warm-starting from battle history. initPopulationSeeded now seeds PopSize/4 individuals from historical enemy movement patterns (centroid + covariance-based perturbations). Remaining seeds are random. Cold start (no history) behaves identically to prior implementation. **Files:** - `vapourbot_garage/src/vapourbot/ga.nim` - initPopulationSeeded(), history persistence logic
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#125
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?