SirStone/SirRoboGarage
1
0
Fork 0
Code Issues 28 Pull Requests Actions Projects Releases Wiki Activity
Labels Milestones New Issue
12 Open 52 Closed
Label
Clear labels
ready-for-agent
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
Milestone
No milestone
Projects
Clear projects
Assignee
Clear assignees
No assignee
SirStone
Write ADR-0002 and update CONTEXT.md ready-for-agent wayfinder:task
#106 opened 2026-08-28 22:03:20 +02:00 by SirStone 0 / 5
Wire multi-gun system into EvoBot ready-for-agent wayfinder:task
#105 opened 2026-08-28 22:03:16 +02:00 by SirStone 0 / 8
1
Implement virtual guns selector ready-for-agent wayfinder:task
#104 opened 2026-08-28 22:03:12 +02:00 by SirStone 0 / 6
Implement GF_Gun — basic guess-factor histogram ready-for-agent wayfinder:task
#103 opened 2026-08-28 22:03:08 +02:00 by SirStone 0 / 5
Implement CMA-ES module ready-for-agent wayfinder:task
#102 opened 2026-08-28 22:03:02 +02:00 by SirStone 0 / 5
Upgrade ANN to 91→16→8→1 two hidden layers ready-for-agent wayfinder:task
#101 opened 2026-08-28 22:02:58 +02:00 by SirStone 0 / 6
Strip per-enemy persistence, go global-only ready-for-agent wayfinder:task
#100 opened 2026-08-28 22:02:54 +02:00 by SirStone 0 / 5
Should UTD=3 and batch=32 remain final, or define a trigger for re-evaluation (e.g., based on throughput metrics)? wayfinder:task
#73 opened 2026-08-25 09:47:09 +02:00 by SirStone
Should eval interval remain at 5, or define a metric to re-evaluate (e.g., "if eval variance > X, drop back to 3")? wayfinder:task
#72 opened 2026-08-25 09:47:01 +02:00 by SirStone
Is chunk size=10 final, or should we re-attempt 20 with the persistence fix (using a measurable criterion like 'no corpse stalls for 2h at chunk=10')? wayfinder:task
#71 opened 2026-08-25 09:46:53 +02:00 by SirStone
What explicit criteria should define 'verified' persistence fix (e.g., buf_size > 0 in first 3 metrics after restart AND training_state.bin rewritten within 2 min)? wayfinder:task
#70 opened 2026-08-25 09:46:48 +02:00 by SirStone
Should we configure ulimit -c unlimited + coredumpctl capture in the service unit, and treat core dump recurrence as a blocker (stop campaign) or data point (continue with monitoring)? wayfinder:task
#69 opened 2026-08-25 09:46:02 +02:00 by SirStone