Trial metrics count a composite action and its steps as separate game writes #144
Loading…
Reference in a new issue
No description provided.
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?
cmonet.evaluation.extractcounts every action job whose operation is a game write. A composite (navigation.go_to,forces.strike_package, the library composites) is a game write in the registry, and so is each step it sends, which has an action record of its own. Every composite was therefore counted with its steps.Live 2026-10-17, trial tpl-subsurface-offensive-patrol.20261017T065733Z: four
navigation.go_tocalls to submarines out of comms were refused at theirnavigation.set_routestep. Each counted as one failed write (the go_to,composite_incomplete) and one invalid write (its step,validation_failed): 127 writes with 6 failed and 4 invalid, where 117 writes with 2 failed and 4 invalid happened. A verified go_to counted as three writes.Expected: a composite counts through its steps; one that stopped before any step went out counts once. Runs already recorded need their metrics derived again from the databases they kept.