UTC --:--:--
NOT CONNECTED
+ NEW PROJECT
CSV EVENT LOG INGESTION
[↑]
DROP EVENTS.CSV HERE OR CLICK TO BROWSE
Auto-detects timestamp · channel · transition columns
PARSED METRICS
Events
Sections
Relays
Movements
INFERRED TRACK CIRCUIT ADJACENCY — CONNECTS_TO EDGES no data
FLAG SUSPECT if transit gap > ms ⓘ AVG STRADDLE = A.clr − B.occ · positive = train spanned both circuits · typical range 2–20s · τ = ±20s/3s window
FROMTOHANDOVERSAVG STRADDLEC_ABCONFIDENCEPOINTS
Upload a CSV to infer topology.
RELAY STATE MATRIX
No events loaded — upload a CSV above.
MODE: 25%
PROPERTIES
Select a node or edge to edit its properties.
DIAGRAM SETTINGS
Min traversals:   Line spacing: 80px
DETECTED RUNNING LINES
Each connected group of sections is shown as a separate line. Set UP to reverse the display order (right→left). Set FAST to apply yellow (traditional fast-line colour). Signals are placed at the entry end of their section based on direction.
TRAIN MOVEMENT PLAYBACK
--:--:--.--- UTC
DIAGNOSTIC HUD — LIVE TRANSITIONS
Load CSV then press PLAY.
TELEMETRY
km/h
Section
Dist. m
Movement
RELAY CHAIN HEALTH MONITOR ● HEALTHY ● LATENT ● DEGRADED
METHODOLOGY: Flags relays where the burst-latency distribution is unusually wide or right-skewed — indicating some transitions are slower than expected. Only flags when spread > 2.5× AND skew > 1.5 simultaneously, to suppress traffic-pattern false positives. ↻ LOAD HISTORICAL BASELINE
RELAY CHAIN LATENCY
Load CSV to analyse relay chain latency.
POINT MACHINE OPERATION TIME (Δt: REQUEST → DETECTION)
Δt = time from (AD) K RX DN (route request) to NWKR/RWKR UP (point detected in position). Typical healthy range: 3–8s. Flagged at p50 > 10s or spread > 2×. ↻ LOAD BASELINE
Load CSV to analyse point machine timing.
INFERRED CONTROL TABLE BS 376 / NR/GN/SIG/11202 format · derived from event log
Each row = one observed route. Hard constraints (★) appear in >90% of observations. Variable entries indicate route variants (A/B). Confidence = fraction of route-set events that show this prerequisite. Click any row to see the full state snapshot detail.
ROUTE OBS. POINTS REQUIRED TRACKS CLEAR OVERLAP HOSTILE ROUTES REPLACEMENT APP. LOCK $t CONFIDENCE
Run topology engine to derive control table.
RECIPROCAL PROVING — RGPR / HGPR
SignalRGPRH/DGPRECPRStatus
No data.
POINT CORRESPONDENCE — NWKR / RWKR
PointsNWKRRWKRNKLPRWZRStatus
No data.
TRAIN GRAPH — TIME × DISTANCE (IBRY–MAREY FORMAT)
⟵ diagonal line = train in motion · steeper = faster ⟵ horizontal segment at station line = dwell (arrival → departure) ⚠ crossing lines = potential conflict on same section ━━ platform / stopping point
PLATFORM DWELL TIMES
SectionVisitsAvg DwellMinMaxType
No data.
GRAPH SETTINGS
Time axis:
Sections shown:
Journeys: complete paths · short fragments excluded
Section spacing: 38px
Highlight platforms:
Y-axis: sections ordered by topological route sequence, equally spaced (add section_length to edge properties for distance-proportional spacing). Platform sections are highlighted with prominent horizontal rules. Dwell time = time between last occupation event and first subsequent clear event at the same section.