Evidence
How was each claim checked?
Hosting capacity10
Generic 400 V model (sensitivity case; the headline is the Indian street model, E55): Phase-managed rural DTR (63 kVA, 700 m): P5 'Passes screening tests' solar is 34.4 kWp and its bootstrap 90% range is 30 to 36 kWp. The 50% cap is 31.5 kWp, so the range straddles the cap. 'Just past the cap' is NOT settled. P5 = 5th percentile over 30 random trials of the largest solar that passes the screening tests (see E40). P50 for the same case is 48.0 kWp.
How it was checked
Read hosting_p5_bootstrap_ci.csv row rural_long / phase_managed (boot_lo 30, boot_hi 36, cap_50pct 31.5).
Limits
Assumed network, 30 random adoption trials, 3 kWp per roof. A real transformer may differ.
results/hosting_p5_bootstrap_ci.csv
Generic 400 V model (sensitivity case; the headline is the Indian street model, E55): Ignoring phases overstates safe solar: at the normal tap (1.00 pu) the balanced model gives 1.3 to 3.5 times the 'Phase-unbalanced case (assumed split, not measured)' P5 across the three street types. P5 = 5th percentile over 30 random trials of the largest solar that passes the screening tests (see E40).
How it was checked
Ratios of balanced P5 to unbalanced P5 in hosting_lv_summary.csv at source_pu 1.0: 255/190.05 = 1.34, 147/73.35 = 2.0, 63/18 = 3.5.
Limits
Simulation on assumed typical streets; not measured on a real network. The case name was 'Unbalanced (field)' until 18 Nov 2026; it is a simulation with a random phase for each home, not a measurement (internal key stays 'unbalanced').
results/hosting_lv_summary.csv
Generic 400 V model (sensitivity case; the headline is the Indian street model, E55): The 50% transformer cap can be tight or loose depending on the street: for the long rural street in the phase-unbalanced case (assumed split, not measured) P5 (18 kWp) is below the 31.5 kWp cap, while for dense urban the working-reading cap (125 kW, unit assumed) is below the 190 kWp P5. P5 = 5th percentile over 30 random trials of the largest solar that passes the screening tests (see E40).
How it was checked
Compared p5 and cap_50pct_kwp row by row in hosting_lv_summary.csv and hosting_cap_unit_sensitivity.csv.
Limits
Depends on which reading of the cap unit is used (see E04) and on the assumed network.
results/hosting_lv_summary.csv
The unit of the 50% cap is not stated in TGERC Reg 1 of 2025 cl 5.1 or in TGSPDCL guideline IV(a): both say '50% of its rated capacity' of the DTR (identical words, no unit). Working reading: 0.5 x DTR kVA treated as kW (50 kWp per 100 kVA); unit assumed: kW on the DTR kVA rating; TGSPDCL to confirm. The 0.9 factor (the 2016 rule, 45 kW per 100 kVA) is an optional sensitivity, not law; the app shows all four readings and a toggle for the 0.9 case. Between R1 and R2 no verdict changes in 0 of 18 LV results (precomputed in results/hosting_cap_unit_sensitivity.csv).
How it was checked
Four readings (R1 to R4) are tabulated side by side in hosting_cap_unit_sensitivity.csv; the app shows all four.
because the unit is not confirmed by the regulator or the discom. (That neither text states a unit: checked - correct, SME label [checked-correct], official text read by the SME and not re-read here; see E25.)
Limits
Until confirmed, results are shown for every reading. To settle: a TGSPDCL feasibility reply, a TGERC clarification or an RTI to the Chief Engineer (IPC & RAC). Limits apply to AC export, not panel DC size: columns say kWp (panel) or kWac (inverter) where known, otherwise unit not stated.
results/hosting_cap_unit_sensitivity.csv
All network values (street lengths, transformer sizes, houses, 3 kWp roofs, load per home) are assumed typical values, not discom data.
How it was checked
Stated in hosting/README.md and in the data notes: no transformer, feeder or house data is held.
because no discom network or transformer data is held
Limits
The pilot replaces the assumed networks with the discom's GIS, transformer and phase data.
hosting/README.md
The standard hosting-capacity screen uses the minimum daytime load with the maximum PV at the sunniest hour.
How it was checked
Literature, as stated by the SME.
(SME label [checked-correct]; not re-checked here)
Limits
Our screen uses the sunniest hours and a flat assumed midday use of 0.25 kW per home (0.5 as a sensitivity), not a measured minimum load.
SME answer, item 4
P5 on the generic 400 V model (sensitivity case; the Indian headline uses 200 trials, E55): the 5th percentile (numpy, linear interpolation) over 30 random trials of the largest rooftop solar (3 kWp roofs) at which no tested limit is broken in the sunniest-hour screens; each trial redraws which homes adopt and (except the balanced model) the phase of each home. P5 is shown beside P50 and P95. Each trial value is the largest number of 3 kWp roofs that passes (roofs added one at a time, limit found by bisection), so every trial value is a multiple of 3 kWp; the percentile interpolates linearly between the sorted values, so the printed P5 can fall between 3 kWp steps (for example 34.35 kWp). Wording written 18 Nov 2026 from the code; the SME may adjust it.
How it was checked
Read from hosting/run_lv.py and hosting/lv.py. Recomputed here: the 5th percentile of the 30 trial values in results/hosting_lv_runs.csv and results/hosting_lv_load050_runs.csv reproduces the summary P5 in all 36 cases (largest difference 2e-15). All 1,080 trial values in the two run files are multiples of 3 kWp (checked 18 Nov 2026); some summary P5 values are not.
(checked here, local files). The SME could not confirm the definition, which is why it is printed under every P5 figure
Limits
91 of 540 roof-by-roof trials and a second engine (OpenDSS) show P5 can be optimistic; treat it as a screening range.
results/hosting_lv_runs.csv
Generic 400 V model (sensitivity case; the headline is the Indian street model, E55): The case formerly named 'Unbalanced (field)' is now 'Phase-unbalanced case (assumed split, not measured)': in hosting/run_lv.py and hosting/lv.py each home is put on a random phase (uniform over 3 phases), redrawn in each of the 30 trials; no real phase data is used.
How it was checked
Read from the code (lv.py build, run_lv.py _trial: rng.integers(0, 3, houses)).
(checked here, read from the code)
Limits
Internal key 'unbalanced' is kept in the database, CSV model column and code; the label mapping is in hosting/README.md.
hosting/run_lv.py
Headline street hosting capacity on the Indian street model (11 kV/433 V DTR, 415/240 V declared supply, named Indian conductors; 200 random trials per case), at 11 kV 1.00 pu: apartment block 315 kVA, 60 m, ABC 3x150, three-phase solar: P5 288 kWp (90% range 288 to 291), P50 291, deciding limit voltage, 50% cap 157.5 kW (unit assumed); city street 160 kVA, 300 m, ABC 3x95, phase unknown: P5 24 kWp (90% range 21 to 26.85), P50 48, deciding limit voltage, 50% cap 80 kW (unit assumed); city street 160 kVA, 300 m, ABC 3x95, phase-managed: P5 47.85 kWp (90% range 44.85 to 50.85), P50 63, deciding limit voltage, 50% cap 80 kW (unit assumed); town street 100 kVA, 400 m, ACSR Rabbit, phase unknown: P5 8.85 kWp (90% range 6 to 9), P50 18, deciding limit voltage, 50% cap 50 kW (unit assumed); town street 100 kVA, 400 m, ACSR Rabbit, phase-managed: P5 18 kWp (90% range 18 to 18), P50 30, deciding limit voltage, 50% cap 50 kW (unit assumed); village street 63 kVA, 700 m, ACSR Weasel, phase unknown: P5 0 kWp (90% range 0 to 0), P50 6, deciding limit voltage, 50% cap 31.5 kW (unit assumed); village street 63 kVA, 700 m, ACSR Weasel, phase-managed: P5 0 kWp (90% range 0 to 0), P50 9, deciding limit voltage, 50% cap 31.5 kW (unit assumed). P5 = 5th percentile of the 200 trials; the 90% range is the bootstrap interval stored with the results. The generic 400 V model (E01 to E03) is kept as a sensitivity case.
How it was checked
Read row by row from results/indian_summary.csv (written by hosting/run_indian.py; columns p5, p5_lo, p5_hi, p50, cap_kwp, binding) and loaded unchanged by scripts/load_data.py (scenario 'indian'); the API values are tested against the CSV in backend/tests/test_indian_headline.py.
(read from the local results file; a model result on assumed streets, not a measurement)
Limits
All network values are assumed (conductor, length, load points, 3 kWp roofs, 0.25 kW midday use); the neutral is modelled full size (optimistic). The OpenDSS and roof-by-roof checks were run on the generic model only. Screening values, not approved capacity.
results/indian_summary.csv
When a street is already above +6% voltage with no solar at all (for example a 433 V DTR with the 11 kV side at 1.03 pu), the hosting result is 0 and the binding is 'over limit before solar'. The app shows this as 'Over the voltage limit before any solar: fix the tap/voltage first', never as 0 kWp safe. In results/indian_summary.csv 7 of 21 cases are over the limit before solar: apartment block 315 kVA at 1.03 pu; city street 160 kVA at 1.03 pu; town street 100 kVA at 1.03 pu; village street 63 kVA at 1.03 pu.
How it was checked
Read from hosting/lv.py (hosting_one checks zero roofs first and returns OVER_BEFORE_SOLAR) and counted in results/indian_summary.csv column binding; the Street page and API state are tested (backend/tests/test_indian_headline.py, ui_tools/e2e/test_street.py).
(read from the code and the local results file)
Limits
The voltage before solar depends on the assumed 11 kV voltage, the DTR tap and the assumed midday load; a real transformer's tap position is not held.
results/indian_summary.csv
| Table | Source file | Rows | Loaded at (UTC) |
|---|---|---|---|
| annual_yield | results/annual_yield_check.csv | 10 | 2026-11-20T05:58:18+00:00 |
| area_band | results/area_test.csv | 4 | 2026-11-20T05:58:18+00:00 |
| cap_unit_sensitivity | results/hosting_cap_unit_sensitivity.csv | 24 | 2026-11-20T05:58:18+00:00 |
| circle_point | data/irradiance_openmeteo_tgspdcl/README.md | 20 | 2026-11-20T05:58:33+00:00 |
| evidence_item | scripts/evidence_items.json | 56 | 2026-11-20T05:58:31+00:00 |
| feeder_dtr | results/feeder_demo.json | 20 | 2026-11-20T05:58:18+00:00 |
| feeder_meta | results/feeder_demo.json | 3 | 2026-11-20T05:58:18+00:00 |
| forecast_accuracy[monthly] | results/test_monthly.csv | 12 | 2026-11-20T05:58:18+00:00 |
| forecast_accuracy[static] | results/test_static.csv | 12 | 2026-11-20T05:58:18+00:00 |
| forecast_by_point[monthly] | results/test_by_point_monthly.csv | 39 | 2026-11-20T05:58:18+00:00 |
| forecast_by_point[static] | results/test_by_point_static.csv | 39 | 2026-11-20T05:58:18+00:00 |
| forecast_example | results/live_area_example.txt | 24 | 2026-11-20T05:58:18+00:00 |
| forecast_hourly | results/test_predictions_monthly.parquet, results/test_predictions_static.parquet | 231438 | 2026-11-20T05:58:33+00:00 |
| growth_class | TGSPDCL_summary/net_meter_clean_22_months.csv (computed by hosting/growth_classes.py) | 18 | 2026-11-20T05:58:18+00:00 |
| hosting_bootstrap | results/hosting_p5_bootstrap_ci.csv | 9 | 2026-11-20T05:58:18+00:00 |
| hosting_runs[indian] | results/indian_runs.csv | 4200 | 2026-11-20T05:58:18+00:00 |
| hosting_runs[load025] | results/hosting_lv_runs.csv | 540 | 2026-11-20T05:58:18+00:00 |
| hosting_runs[load050] | results/hosting_lv_load050_runs.csv | 540 | 2026-11-20T05:58:18+00:00 |
| hosting_summary[indian] | results/indian_summary.csv | 21 | 2026-11-20T05:58:18+00:00 |
| hosting_summary[load025] | results/hosting_lv_summary.csv | 18 | 2026-11-20T05:58:18+00:00 |
| hosting_summary[load050] | results/hosting_lv_load050_summary.csv | 18 | 2026-11-20T05:58:18+00:00 |
| kusum_cap_sensitivity | results/hosting_kusum_cap_sensitivity.csv | 16 | 2026-11-20T05:58:18+00:00 |
| kusum_grid | results/hosting_kusum.csv | 16 | 2026-11-20T05:58:18+00:00 |
| net_meter_category_month | TGSPDCL_summary/net_meter_clean_22_months.csv | 163 | 2026-11-20T05:58:18+00:00 |
| net_meter_gap | TGSPDCL_summary/net_meter_clean_22_months.csv (derived) | 23 | 2026-11-20T05:58:19+00:00 |
| net_meter_section_month | TGSPDCL_summary/net_meter_clean_22_months.csv | 10099 | 2026-11-20T05:58:18+00:00 |
| net_meter_series_break | TGSPDCL_summary/net_meter_clean_22_months.csv (derived) | 7 | 2026-11-20T05:58:19+00:00 |
| nowcast_backtest | nowcast/results/backtest.csv | 6 | 2026-11-20T05:58:33+00:00 |
| real_dataset | computed from the files above | 8 | 2026-11-20T05:58:31+00:00 |
| real_fact | telangana_reports/mnre_2026_02.pdf; docs/Challenge16_DER_Final.md | 3 | 2026-11-20T05:58:31+00:00 |
| real_not_held | scripts/load_data.py (NOT_HELD) | 5 | 2026-11-20T05:58:31+00:00 |
| saturation | results/indian_months_to_full.csv (safe limit: indian_summary.csv P5 at 1.00 pu) | 21 | 2026-11-20T05:58:18+00:00 |
| weather_coverage | irradiance_openmeteo_tgspdcl/*.csv, prev_day1_tgspdcl/*.csv | 13 | 2026-11-20T05:58:31+00:00 |
| weather_daily | same files, every day, daily totals | 37310 | 2026-11-20T05:58:31+00:00 |
| weather_hourly | same files, last 14 days, hourly | 4368 | 2026-11-20T05:58:31+00:00 |
| weather_point | data/irradiance_openmeteo_tgspdcl/README.md | 13 | 2026-11-20T05:58:33+00:00 |
REAL = measured or published data held in this project. Weather actuals are satellite/reanalysis-based sunlight, not metered solar output. Our model, or a published model reference (PVGIS), run on real inputs. Not measured. Assumed typical values (street lengths, cables, houses, 3 kWp roofs, load per home). The pilot replaces them with the discom's data.
| Dataset | Tag | Period | Rows | Coverage | Last date | Source file | Can show | Cannot show |
|---|---|---|---|---|---|---|---|---|
| TGSPDCL rooftop net-meter records, monthly | REAL | 2025-01 to 2026-10 | 146,665 | 22 monthly files; 20 circles and 473 section offices (circle + section name) in 2026-10; 59,550 services in 2026-10; July 2025 de-duplicated; Aug 2025 has no Gadwal circle (kept missing) | Oct 2026 | data/TGSPDCL/ (22 monthly files, Open Data Telangana) -> data/TGSPDCL_summary/net_meter_clean_22_months.csv | Real billed services, billed kW (load column) and units, by month, circle and section office. | Per-transformer counts, hourly values, what 'units' means (import, export or net). |
| Open-Meteo weather actuals, 13 TGSPDCL points (hourly) | REAL | 2019-01-01 to 2026-11-09 | 895,440 | 13 points, 68,880 hourly rows each; satellite/reanalysis-based archive | 9 Nov 2026 | data/irradiance_openmeteo_tgspdcl/*.csv (Open-Meteo, CC BY 4.0) | Real sunlight (GHI, direct, diffuse), temperature, cloud, wind by hour for the area. | Ground-station measurements, metered solar output, the newest days are provisional (back-filled). |
| Open-Meteo day-before forecasts, 13 TGSPDCL points (hourly) | REAL | 2024-01-19 to 2026-11-09 | 319,891 | 13 points, 24,607 non-empty hourly rows each of 25,056 (the empty hours are before the first real forecast) | 9 Nov 2026 | data/prev_day1_tgspdcl/*.csv (Open-Meteo previous-runs API, CC BY 4.0) | What the weather model forecast one day before, to compare with the actuals above. | Metered solar output; it is a weather forecast, not a solar-power forecast. |
| MNRE state-wise renewable capacity table | REAL | 31.01.2026 | 1 | one Telangana row: rooftop 695.9 MW, solar total 5,065.10 MW | 31.01.2026 | data/telangana_reports/mnre_2026_02.pdf | State-level rooftop and total solar capacity on one date. | A time series (the other dates in the SME note are not held), anything per district, circle or transformer. |
| PM Surya Ghar installations, Telangana (quoted) | REAL | 27 Jul 2026 | 1 | 54,668 installations, 70,144 households (quoted from Lok Sabha Q 1698) | 27 Jul 2026 | docs/Challenge16_DER_Final.md (source file not held) | A state-level count of subsidised rooftop installations. | MW per state, per circle or per transformer. The source file is not held, so the figure cannot be checked yet. |
| PVGIS 1 kWp hourly output (published model reference) | MODEL | not a dated file | n/a | source files not found on this machine | n/a | data/pvgis_1kwp/*.csv | A published model reference for 1 kWp output. | Measured output. |
| Open-Meteo live forecast (called when you ask, LIVE badge) | REAL | not a dated file | n/a | 13 points, next day and the day after; falls back to the stored example when the call fails and says so | n/a | Open-Meteo API (CC BY 4.0) via backend/app/integrations/open_meteo/ | A real weather forecast fed into our shipped model. | The power estimate is modelled: it is not scored against metered output. |
| TGSPDCL guideline and agreement texts, CSTEP feeder report, MNRE table (PDFs) | REAL | not a dated file | n/a | source folder not found on this machine | n/a | data/telangana_reports/*.pdf | The published rules: 50% DTR cap wording, 56 kWp self-certification threshold, the CSTEP feeder method. | The TGERC regulation text and the 2016 gazette are not held; the unit of the 50% cap is not stated in either text. |
- Real transformer data (kVA, consumers, phase, 15-minute DTR or feeder load). Not public; the DTR list has to come from the department. Every network value here is assumed.
- Metered rooftop solar output. Not public and not downloadable (PVGIS stops at 2023; no metered source was found). Forecast accuracy is versus a physics model, not versus measurement.
- Ground-measured sunlight (GHI). No ground station file is held. The Open-Meteo actuals are satellite/reanalysis-based; NIWE or IMD stations would be the check.
- Hourly or 15-minute net-meter / smart-meter data. Only monthly counts, billed kW and units are public. The meaning of the 'units' column (import, export or net) is not documented.
- TGNPDCL (northern discom) net-meter data. No TGNPDCL file was found; the net-meter data covers TGSPDCL only.
- REAL Telangana rooftop solar, MNRE state table: 695.9 MW (as on 31.01.2026; telangana_reports/mnre_2026_02.pdf)Table headed 'State-wise (Location based) installed capacity of Renewable Power as on 31.01.2026', Telangana row. State total, not per transformer.
- REAL Telangana solar power total, MNRE state table: 5,065.1 MW (as on 31.01.2026; telangana_reports/mnre_2026_02.pdf)Same table, 'Solar Power Total' column (ground mounted 4,360.49 + rooftop 695.9 + the third solar column 8.71).
- REAL PM Surya Ghar installations, Telangana: 54,668 installations (as on 27 Jul 2026; docs/Challenge16_DER_Final.md (quotes Lok Sabha Q 1698))Quoted from Lok Sabha Q 1698; the source file is not held, so it cannot be checked yet (the expert review found it correct). 70,144 households in the same answer; no MW per state found.
A traffic light per transformer: reason, room left, early warning. Network values are assumed examples until the discom supplies its own data. Screening only, never approved capacity.
Every claim in this app, how it was checked, and what it cannot tell you. Labels: checked - correct, checked - wrong, cannot be checked yet, because ...
Limit on the street results (E01 to E03 generic sensitivity; E55 Indian headline). P5 is a screening value and can be optimistic. Checks run on the generic 400 V model (not repeated on the Indian model): in 91 of 540 roof-by-roof trials "more roofs is never better" fails, and OpenDSS gives 69.0 vs 73.35 kWp (urban) and 16.35 vs 18.0 kWp (rural), both unbalanced. Treat it as a range, not a guarantee.
P5 as defined here (Passes screening tests). P5 = 5th percentile over 200 random trials (Indian street model, the headline; 30 random trials on the generic 400 V sensitivity) of the largest rooftop solar (3 kWp roofs, panel kWp) that passes the screening tests at the sunniest hour (voltage rise +6%, transformer 100 per cent of rating, cable 100 per cent, unbalance 3%); each trial redraws which homes adopt and (except the balanced and three-phase cases) each home's phase. Each trial value is the largest number of 3 kWp roofs that passes, so it is a multiple of 3 kWp; the 5th percentile interpolates linearly between the sorted values (numpy), so the printed P5 can fall between 3 kWp steps (for example 34.35). P50 is the median of the same trials. Screening value, not a guarantee.
Label notes: where an item says SME label, the label is the SME's as given: [checked-correct] = official text read by the SME, [secondary] = news or think-tank, [cannot be checked] = no source. The project could not re-read any gazette or live site, so none of these is upgraded to checked here.