Decide input encoding for enemy velocity #162
Reference in New Issue
Block a user
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?
Question
How should enemy velocity be encoded and fed to the SNN alongside the current bearing input?
Current input: 36 population-coded neurons for relative bearing (-180°..+180°, 10° bands).
Options for velocity:
Design constraint: the input interface must be structured so recurrent features can augment or replace velocity features in step 3 without rewriting the SNN core.
Blocked by: #160 (Research bullet mechanics — need to know what velocity info matters)
Resolution
Polar encoding: velocity direction (36 neurons) + speed (8 neurons), 1-tick delta, SNN smooths internally.
Input vector layout (80 neurons total)
Key decisions