How aaryang21/micro-grid-planner works
Microgrid Feasibility Dashboard combines a React planning interface with a Flask API. Users can scan a clicked site for nearby buildings and demand, then continue into a microgrid plan; city analysis adds demand, population, industry, emissions, ranked candidate cells, and map layers. The graph separates site planning, city analysis, interface, and persistence. Several backend stages are represented from the README and source index, but their internal calls are not asserted where excerpts do not show them.
Main entry points: pipeline.py City analysis pipeline · App.jsx Planning dashboard · useCityScan.js City scan hook · api.py City scan routes
Components 24
User interface
- Landing experience
src/components/landing/Landing.jsx - Planning dashboard
src/App.jsx - City scan hook
src/hooks/useCityScan.js - City map layers
src/components/city/CityLayers.jsx - City summary
src/components/city/CitySummary.jsx
Site feasibility
- Building and load scan
site_scan.py - Demand shaping model
train_demand_model.py - System sizing
solar_sizing.py - Load forecasting
load_forecast.py
City analysis
- City analysis pipeline
city_scan/pipeline.py - City boundaries
city_scan/boundary.py - Spatial grid
city_scan/grid.py - Population layer
city_scan/population.py - Consumption estimates
city_scan/consumption.py - Utility calibration
city_scan/calibration.py - Karnataka utility data
city_scan/regional/karnataka.py - Industry layer
city_scan/industry.py - Emissions layer
city_scan/emissions.py - Night-light layer
city_scan/nightlights.py - Candidate scoring
city_scan/scoring.py
API and persistence
- City scan routes
city_scan/api.py - Flask application API
app.py - Application data store
models.py
Other components
- Planner
Connections 26
- Planner → Landing experience: opens
- Landing experience → Planning dashboard: enters planning
src/components/landing/Landing.jsx - Planner → Planning dashboard: selects site
- Planning dashboard → Building and load scan: requests site scan
- Building and load scan → Demand shaping model: uses load shape
site_scan.py - Planning dashboard → System sizing: requests system sizing
- Planning dashboard → Load forecasting: requests forecast
- Planning dashboard → City scan hook: starts city analysis
src/App.jsx - City scan hook → City scan routes: calls city endpoints
src/hooks/useCityScan.js - City scan routes → City analysis pipeline: runs analysis
city_scan/api.py - City scan routes → Application data store: reads and stores scans
city_scan/api.py - Flask application API → City scan routes: registers routes
app.py - Flask application API → Building and load scan: registers site routes
app.py - Flask application API → Application data store: uses persistence
app.py - City analysis pipeline → City boundaries: resolves city
city_scan/pipeline.py - City analysis pipeline → Spatial grid: builds cells
city_scan/pipeline.py - City analysis pipeline → Population layer: loads population
city_scan/pipeline.py - City analysis pipeline → Consumption estimates: estimates demand
city_scan/pipeline.py - City analysis pipeline → Utility calibration: calibrates demand
city_scan/pipeline.py - City analysis pipeline → Industry layer: loads industry
city_scan/pipeline.py - City analysis pipeline → Emissions layer: loads emissions
city_scan/pipeline.py - City analysis pipeline → Night-light layer: uses night lights
city_scan/pipeline.py - City analysis pipeline → Candidate scoring: ranks candidates
city_scan/pipeline.py - Utility calibration → Karnataka utility data: uses regional data
- City scan hook → City map layers: supplies layer data
src/App.jsx - City scan hook → City summary: supplies scan summary
src/App.jsx