Skip to content

Show the generator dip measured from its load step (1.2.2) - #4

Merged
AddisonTech merged 4 commits into
mainfrom
claude/jolly-shannon-12vlay
Oct 16, 2026
Merged

AddisonTech merged 4 commits into
mainfrom
claude/jolly-shannon-12vlay

Conversation

@AddisonTech

@AddisonTech AddisonTech commented Oct 16, 2026 •

Copy link
Copy Markdown
Owner

The fault

The live outage card's "Generator frequency dip" consequence said "worst 20.00 Hz". The agent read the dip's evidence across the generator's run up from standstill, so the minimum was the crank, not the dip.

The fix

  • Agent 0.2.2, pinned to its merge commit 1c32b20. It measures the dip from the load step (the ATS transfer), only once the generator is at rated frequency; without a transfer, from the first rated sample; with neither, no number.
  • The Triage tab shows the dip on the consequence: worst frequency, how far below 60 Hz, and when it was back within 0.5 Hz and how long after the step, with times in the viewer's zone and labeled like everything else. With no measurement it says so and shows no number.
  • Triage fixtures regenerated from the simulator with the new agent.

Checked live

Simulated outage, New York browser: "Load step 16:45:38 EDT (at the transfer): worst 58.81 Hz, 1.19 Hz below the 60 Hz nominal, back within 0.5 Hz at 16:45:40 EDT, 2 s after the step."

Tests

  • Backend: 83 pass (82 before), including the simulator outage dip: anchored at the ATS transfer, after rated, 58 to 59.5 Hz, recovered within 6 s, never a crank value.
  • Front end: 38 pass (33 before): the dip text in New York and UTC, never a crank value, no number when nothing was measured, and a dip that never recovers.
  • Production build clean.

@AddisonTech
AddisonTech merged commit 4a8987b into main Oct 16, 2026
2 checks passed
@AddisonTech
AddisonTech deleted the claude/jolly-shannon-12vlay branch October 16, 2026 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant