mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-10-19 02:51:42 -07:00
ScottW514
80ddd53bcd
check_fire_gaps counted consecutive stepless ticks carrying FIRE and reset on any dark tick: the analog rendering of a fire state leaked into a cycle's idle pad (stepper_stream.c gf_stream_go_idle names it: a stationary dwell burn at every planner starve). Under the density model every tick goes through the dither mask, so the same leaked state renders as bursts of at most one period (80 ticks at S800) split by dark ticks, and the run never reaches the limit. With the analog churn session gone, density-churn was the only session on rule 9, and it could not see the leak it was there for. The check now reads rule 8 both ways: the run of lit stepless ticks as before, and for every FIRE tick its distance from the nearest step on either side, the one before it and the one after it. A cut's first FIRE tick leads its first step by the accel-from-rest interval (412 ticks at x32) and its last trails its last step by less, both inside the limit (1000); a FIRE tick with no step that near on either side is in a gap, and lit, however the dither spaced it. The distance is read from both sides because a stream opens dark on its lead-in pad and a cycle opens lit before its first step: depth into a stepless run alone flagged the m4 session's first lit tick, 22529 ticks of dark pad after the stream start and a few hundred before the first step. Proof: on synthetic streams, a legitimate 2253-tick dark gap between two cuts passes both readings; a continuous analog leak across it fails both; the same gap carrying a dithered leak at S800 (64 of 80 ticks lit) and at S200 (16 of 80) passed the old reading and fails the new. The whole harness passes against the native null-sink build (-DGFMCODE_WAIT_S=5.0), every session. Acceptance: none; the harness is grblHAL's CI's, and src/** of grblhal-glowforge keeps its covers.