mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-28 17:11:15 -07:00
ScottW514
4eb0932099
Under the FIRE-bit dose model the duty is pinned at full and the level is carried by how many ticks of each base period fire, so a rung's pulse is density x period - and the base period is the one parameter the host cannot settle. dladder walks 5 to 100 percent of dose on scrap at constant power, printing what each rung actually emits: density, mean on-ticks, and the pulse the tube sees in ticks and microseconds. Below one tick per period the pulse stays one tick and whole periods are skipped instead, which the table says outright rather than quoting a sub-tick average. Run it at 20, then 40, then 10 on the same material. At 20 percent dose that is 107-142 us, 249-284 us and 36-71 us respectively, which brackets the 100 us the factory never goes below. The material answers two questions: whether depth tracks density linearly, or the low end marks harder than its share because every burst restarts the discharge and carries the strike transient; and how short a burst still marks, which is the floor a given base period can reach. Preconditions are refusals, not warnings: laser_power_model must already be density and $35 must be 0, since a floor lifts every rung off the bottom of the range the drill exists to explore. The $35 message says a runtime write is not enough - the S to duty mapping is precomputed when the spindle is enabled. The drill writes laser_pulse_ticks itself when it can reach the machine config, preserving every other line, and refuses with instructions when run from a LAN host where it cannot.