en un clic
gridtokenx-smartmeter-simulator
gridtokenx-smartmeter-simulator contient 5 skills collectées depuis NakaSato, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Author, edit, and validate GridLAB-D .glm topology files for the smart meter simulator. Use when creating or modifying a grid topology (.glm), adding buses/lines/loads/PV, debugging "validate-topology" errors, fixing missing-bus / disconnected-graph / PV-not-mapped issues, or understanding which GLM object types and fields this backend's parser actually reads.
Run, drive, and test the simulator end-to-end — the uv entry points (app/cli), server vs standalone vs validate-topology modes, the FastAPI lifespan/autostart, hot-swapping topology and telemetry sources at runtime, the pytest suite (coverage, markers), and the Docker image. Use when starting the simulator, reproducing a scenario, switching grids/telemetry, or figuring out how to run a specific test.
Build and control the meter population — MeterGenerator (synthetic fleets, type-mix ratios, PV-per-bus, spreading meters across topology buses) and the meter registry (pinning real meters by id to physical buses for telemetry-driven runs). Use when changing how meters are created, how many there are, how meter types/solar are assigned, how meters map to buses, or wiring a CSV/JSON registry.
Develop the backend simulation — device models (PV/load/AMI), the per-tick feeder solver, reading generation, telemetry sources, and FastAPI routers. Use when adding or changing how meters generate readings, how the grid solver computes voltages/flows/losses, how real telemetry overrides synthetic models, or how a new measurement/field surfaces through the API. (For editing .glm topology files themselves, use glm-topology-authoring instead.)
Develop the Next.js 16 / React 19 simulator dashboard — pages (dashboard, map, topology, meter detail), components (Leaflet/Mapbox maps, Three.js 3D topology, Recharts), the backend API client, WebSocket/polling telemetry, and the React Context providers. Use when adding or changing UI, wiring a new backend endpoint into the frontend, touching the map/3D views, or debugging API-target / proxy issues. Read this BEFORE writing frontend code.