Torii-SUMO

Use when planning, coding, debugging, auditing, comparing, or writing claims for Eclipse SUMO/TraCI traffic-signal experiments, including OSM/netconvert networks, TLS/NEMA, controllers, routes, demand, detectors, outputs, baselines, metrics, reproducibility, TDD changes, and reusable field lessons.

Use when planning, coding, debugging, auditing, comparing, or writing claims for Eclipse SUMO/TraCI traffic-signal experiments, including OSM/netconvert networks, TLS/NEMA, controllers, routes, demand, detectors, outputs, baselines, metrics, reproducibility, TDD changes, and reusable field lessons.

Use when turning a confusing simulation or controller experiment result into a precise prompt, plan, or next diagnostic step. Especially relevant when comparing variants, questioning why performance changed, inferring mechanisms from logs, building fair baselines, or preserving evidence boundaries around completion, backlog, action timing, trigger logic, and metrics.

Use when diagnosing Eclipse SUMO, TraCI, netconvert, duarouter, route, demand, detector, traffic-light, output, teleport, insertion, seed, performance, or reproducibility failures in traffic-simulation workflows.