Differences

This shows you the differences between two versions of the page.

--- finding_the_source_of_a_grid_oscillation [2026/07/28 16:33] – [What the application does] wikiadmin
+++ finding_the_source_of_a_grid_oscillation [2026/07/28 16:37] (current) – [What the application does] wikiadmin
@@ Line 7: / Line 7: @@
 ===== The problem =====
-A generator's governor starts to misbehave. It doesn't trip, it doesn't alarm — it just pushes a small, steady oscillation into the grid. Within seconds every bus on the interconnection is swinging at exactly the same frequency, hundreds of miles from the cause.
+A generator's governor starts to misbehave. It doesn't trip, it doesn't alarm, it just pushes a small, steady oscillation into the grid. Within seconds every bus on the interconnection is swinging at exactly the same frequency, hundreds of miles from the cause.
 This is a **forced oscillation**, and it is one of the harder faults to chase.
-Frequency tells you nothing about location: the whole system rings in unison. The plant that is causing it looks, on a frequency plot, identical to a plant a thousand miles away that is merely responding. Operators have the data — every PMU on the system is reporting thirty times a second — and no obvious way to turn hundreds of simultaneous channels into an answer.
+Frequency tells you nothing about location: the whole system rings in unison. The plant that is causing it looks, on a frequency plot, identical to a plant a thousand miles away that is merely responding. Operators have the data.  Every PMU on the system is reporting thirty times a secondand no obvious way to turn hundreds of simultaneous channels into an answer.
 This demonstration turns 294 channels of synchrophasor data into one name, in under two seconds, using a configured MIStudio application.
@@ Line 27: / Line 27: @@
 | Cause | The governor of generator **7031 COLOEAST**, in the NORTH area |
-The cause is published with the data. It is used here only to check the answer — the application is told nothing about it.
+The cause is published with the data. It is used here only to check the answer. The application is told nothing about it.
-The data is also realistically imperfect. Roughly one frame in 2,000 on the voltage channels, and one in 125 on the current channels, arrives as a dropped sample. A dropped frame is a far larger excursion than the oscillation it sits in, so left alone it does not merely add noise — it decides the ranking.
+The data is also realistically imperfect. Roughly one frame in 2,000 on the voltage channels, and one in 125 on the current channels, arrives as a dropped sample. A dropped frame is a far larger excursion than the oscillation it sits in, so left alone it does not merely add noise, it decides the ranking.
 Run against the raw data, the top five buses are simply the five that caught a dropped frame, and the true source falls to **36th of 58**.
@@ Line 39: / Line 39: @@
 ===== What the application does =====
-{{ :pasted:20260728-163036.png?400|The PMUCharts application}}
+One button. The extractor reads every bus over the event window, computes a statistical and spectral profile for each, ranks all 58, and labels the winner — in a single database query and a single pass.
-''Figure 1 — The whole application. Six components, five connections.''
+{{:pasted:20260728-163036.png?400|The PMUCharts application}}
-One button. The extractor reads every bus over the event window, computes a statistical and spectral profile for each, ranks all 58, and labels the winner — in a single database query and a single pass.
+''Figure 1 — The whole application. Six components, five connections.''
 The chart then draws the located bus against the four quietest buses on the system, so the contrast is immediate.
@@ Line 66: / Line 66: @@
 **Rank 1 is the documented source.**
-Ranks 2 and 3 are its electrical neighbours — exactly what the physics predicts. The located bus swings **22 times harder** than the quietest bus on the system.
+Ranks 2 and 3 are its electrical neighbors, that's exactly what the physics predicts. The located bus swings **22 times harder** than the quietest bus on the system.
 Note the ''Dominant freq.'' column: **0.547 Hz on every row**, source and bystander alike. This is the heart of why forced oscillations are hard, and why frequency analysis alone does not locate them. The amplitude column is what carries the answer.
-The ''Inter-area band'' column is a second, independent line of evidence — the share of each bus's movement that falls in the 0.1–0.8 Hz inter-area band. At the source it is 96.9%: essentially everything that bus is doing is this oscillation. At SYLMARLA, ranked 5th, it is 29.9% — that bus is mostly moving for other reasons, and a ranking built on this column instead would push it down where it belongs.
+The ''Inter-area band'' column is a second, independent line of evidence, the share of each bus's movement that falls in the 0.1–0.8 Hz inter-area band. At the source it is 96.9%: essentially everything that bus is doing is this oscillation. At SYLMARLA, ranked 5th, it is 29.9%. That bus is mostly moving for other reasons, and a ranking built on this column instead would push it down where it belongs.
 ----
@@ Line 106: / Line 106: @@
 ===== Why this generalises =====
-The semiconductor version of this application ranks **wafer lots** by process stability and charts the golden lot against the rest. It is the same components, the same ranking mechanism, the same chart.
+A semiconductor version of this application ranks **wafer lots** by process stability and charts the golden lot against the rest. It is the same components, the same ranking mechanism, the same chart.
 What changed between the two is the connection string and the contents of one JSON property.