Evidence
How was each claim checked?
Growth9
TGSPDCL net-meter services rose from 25,687 (Jan 2025) to 59,550 (Oct 2026); Oct 2026 is 68% above Oct 2025 (35,397).
How it was checked
Independent pandas sum of totservices by month on net_meter_clean_22_months.csv; 59,550 / 35,397 = 1.682.
Limits
Southern discom only; Aug 2025 is missing for the Gadwal circle and 8 Sangareddy sections (7, plus the one-service section Kangti; marked missing, not interpolated); Kodangal 6 to 789 services in May 2026 is treated as two series; July 2025 duplicates were removed in the clean file.
net_meter_clean_22_months.csv
Whether net-meter 'units' are gross generation, net or export-billed. The SME has not seen the units column, so its meaning is not checked by the SME either.
How it was checked
Units do not follow the seasonal shape of the forecast (correlation -0.16 over 22 months) and units per kW average 53 kWh a month against an expected gross 118-127, so gross generation is not supported; import, export and import minus export all remain open. No negative values (a zero floor would hide net export). Discom question: Is the net-meter units column import, export, or import minus export, in kWh, per month?
because the billing basis of the units is not stated in the open data
Limits
The app shows services (counts), not units, for growth. The units column is not used as installed kWp or generation until the discom confirms; the size test rests on reading the 'load' column as installed solar kW, which is not confirmed. Our own data-test result stands: gross generation is not supported; net import versus export-only is open (sme_review/A7_*).
data.md section 1d
Months-to-full is an estimate shown as a range (for example 28 of 50 kWp: 9.4 to 61.3 months across the slow, median and fast net-meter growth classes, computed in the loader on a billed kW basis; 20.5 to 34.5 months at the three MNRE reference rates). Display rule (project decision made 18 Nov 2026): the numbers stay in the API and the database; any figure above 120 months is shown as 'more than 10 years' and a transformer already at or over its cap or limit is shown as 'already full' (checked before the cap). The growth rate used is shown next to every months-to-full number.
How it was checked
Months = ln(cap / installed) / ln(1 + monthly growth), recomputed for the example transformers independently with pandas, without the loader (backend/tests/test_growth_classes.py: classes and ranges); hosting_saturation.csv is regenerated from the same computed classes by hosting/saturation.py and the loader recomputes the months from them at full precision. The older sme_review/A8_months_to_full_ranges.csv holds the earlier values from the stored classes 0.9 / 2.9 / 6.3 (superseded). One rounding function (one decimal, display only) serves every page. Since 19 Nov 2026 the stored months-to-full table on the Growth page uses the Indian street model: installed and cap from results/indian_months_to_full.csv, safe limit = the Indian P5 at 11 kV 1.00 pu (results/indian_summary.csv), months recomputed by the loader from the same growth classes.
because no per-transformer solar counts are held
Limits
Growth of services in a section is not growth of kWp on one transformer and is not an acceptable per-transformer proxy. Thresholds Act now under 2 months and Watch under 6 months are PROPOSED - NOT TESTED (set from the discom's real upgrade lead time). Show a range, not one number. MNRE reference rates, recomputed on 18 Nov 2026 with the true table date (31 Jan 2026): 1.69% a month (31 Jan to 30 Sep, 8 months), 1.82% (31 Jan to 31 Oct, 9 months), 2.87% (30 Sep to 31 Oct, 1 month), 1.96% (31 Dec 2025 to 31 Jan 2026, 1 month); derived and conditional on the SME-note values (source tables not held). Roofs up to 10 kWp skip the feasibility study (rule 11(7A), SME answer of 18 Nov 2026; official text not re-read here), so a transformer can fill without anyone checking (see E44).
results/indian_months_to_full.csv
Kodangal (Vikarabad circle) goes from 6 services in Apr 2026 to 789 in May 2026 and 1,498 in Oct 2026. The other 19 Vikarabad sections add 17 services in total that month and no section in the file loses more than 1 service, so it is not a move between sections of this file; the 783 added services average 0.34 kW of billed load each against about 6 kW elsewhere.
How it was checked
Section totals by month from net_meter_clean_22_months.csv (a_netmeter_tests.py).
Limits
Cause (reorganisation, re-coding, new population) cannot be checked yet, because the discom has not been asked. Kodangal is treated as two series; no growth across the break.
net_meter_clean_22_months.csv
The Aug 2025 file has no rows for the Gadwal circle (13 sections, about 186 services) and 8 Sangareddy sections: 7 that are present in July and Sep 2025 (73 services in July) plus the one-service section Kangti (no rows from Jul 2025 to Aug 2026). Aug 2025 total services (33,272) are about 0.55% low.
How it was checked
Circle and section presence by month; Gadwal 182 (Jul) and 189 (Sep) services. Sangareddy sections counted again on 18 Nov 2026 straight from data/TGSPDCL/*.csv: 33 sections in July and September 2025, 26 in August; the 7 missing are Zaheerabad Town and Rural, Koheer, Mannapur, Nyalkal, Jharasangam, Raikode; Kangti (1 service) has rows in Jan to Jun 2025 and from Sep 2026 only, so it is also absent in Aug 2025 (8 in all). Earlier notes said 7: that count left Kangti out.
Limits
Marked missing, excluded from growth rates, not interpolated. Ask the discom for the missing month.
net_meter_clean_22_months.csv
MNRE Telangana rooftop: 682.5 (31 Dec 2025), 695.9 (31 Jan 2026), 795.90 (30 Sep 2026), 818.76 (31 Oct 2026). The 695.9 table is headed 'as on 31.01.2026' (read in the original PDF). On those dates the compound rates are 1.96% (Dec to Jan, 1 month), 1.69% (Jan to Sep, 8 months), 1.82% (Jan to Oct, 9 months) and 2.87% (Sep to Oct, 1 month) a month.
How it was checked
Rates: arithmetic with exact month counts from the true date of 695.9 (sme_review/a_mnre_corrected.py). 682.5, 795.90 and 818.76 are from the SME note, source table not held. The date of 695.9 is item E24.
because the SME-note values 682.5, 795.90 and 818.76 are not on disk, so the rates that use them are derived and conditional
Limits
With the true date growth looks fairly steady at about 1.7 to 2.0% a month, so the SME's earlier reading of a recent speed-up (which assumed 31 Mar) is not supported; the median early-warning class (3.0% a month, computed) is above these multi-month rates and close to the latest single month only (2.87%). SME's earlier rates 2.35 / 2.26 / 0.65 assumed 31 Mar and are superseded (decision of 18 Nov 2026).
telangana_reports/mnre_2026_02.pdf
MNRE table headed as on 31.01.2026 (read in the original PDF): Telangana rooftop 695.9 MW, total 5,065.10 MW.
How it was checked
pdftotext -layout on telangana_reports/mnre_2026_02.pdf on 18 Nov 2026: heading 'State-wise (Location based) installed capacity of Renewable Power as on 31.01.2026', Telangana row rooftop 695.9, total 5,065.10 (4,360.49 + 695.9 + 8.71). Decision of the SME on 18 Nov 2026: 31.01.2026 is correct.
Limits
The SME's reading '31 Mar 2026' is not supported by the table we hold. A state total, not per transformer. The SME-note values for other dates are not held (E19).
telangana_reports/mnre_2026_02.pdf
Roofs up to 10 kWp skip the feasibility study (rule 11(7A)), so a transformer can fill without anyone checking. Telangana single-phase supply goes up to 15 kW (GTCS amended to 2016), while the 5 kW / 75 kW table is only the 2016 net-metering guideline.
How it was checked
SME answer, item 6. Label as the SME gives it: supported (earlier notes had it at AGENT level). Rule and GTCS texts not held here.
because the rule and GTCS texts are not held here (SME label: supported)
Limits
Months to full above 120 is shown as 'more than 10 years' (display rule, project decision 18 Nov 2026).
SME answer, item 6
Growth classes (P10 / P50 / P90 across sections of the compound monthly growth, first to last month, Jan 2025 to Oct 2026) are now COMPUTED in the loader from the net-meter table: billed kW of the kW categories 0.95 / 3.04 / 6.37% a month (440 sections; used for months to full); second basis, services 1.62 / 3.77 / 8.40% (441 sections); comparison, billed load of all categories as recorded (adds kW and hp) 0.91 / 2.98 / 6.43% (441 sections; this is the reviewer's recompute of 0.90 / 2.98 / 6.43 on 443 sections including Kodangal). Rules: Aug 2025 missing, not interpolated (only the two end months are used); Kodangal left out (two series); flagged-step sections included in the primary classes and reported without them as well (0.93 / 3.02 / 6.31). Classes now computed in the loader on billed kW basis (18 Nov 2026); previous stored values 0.93/2.91/6.26 came from a JSON not held.
How it was checked
Computed by hosting/growth_classes.py (called by scripts/load_data.py, table growth_class with the definition) and recomputed independently with plain pandas in backend/tests/test_growth_classes.py (18 cases agree to 1e-9).
(computed and independently recomputed from the local file); the earlier stored values 0.93 / 2.91 / 6.26: cannot be checked yet, because their source JSON (saturation_growth_rates.json) is not held, and they are no longer used
Limits
Section growth is not a per-transformer rate. Services growth (+68% in a year, 1.62 / 3.77 / 8.40% a month by section) and billed kW growth (0.95 / 3.04 / 6.37% a month) are different quantities: only billed kW feeds months to full. Choosing the all-category load instead of the kW categories changes the 28-of-50 range from 9.4 to 61.3 to 9.3 to 64.1 months; the kW-only basis was chosen because hp and kW cannot be added.
TGSPDCL_summary/net_meter_clean_22_months.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.