What is Türkiye Grid Foundation Model?
Türkiye's electricity system produces several hourly signals that are related but not identical. One describes how much electricity is consumed. Another describes generation from solar, wind, hydro, geothermal, biomass, gas, coal and other sources. A third is the hourly day-ahead market clearing price, known in Türkiye as PTF.
Instead of treating these as unrelated forecasting problems, the project asks whether one shared temporal representation can learn useful common structure across them. The first design forecasts consumption, renewable generation and PTF at +1, +6 and +24 hours.
2 · Why does the project exist?
A forecasting system can look impressive while answering a weak question. Electricity has strong seasonality; prices change regime; renewable output can ramp sharply; random time splitting can leak future information; and an over-large experiment can become too expensive to finish.
The repository therefore follows one rule: build research controls before opening final evidence. Data contracts, leakage-resistant windows, baselines, uncertainty tools, tests, a compute-safe smoke path and publication structure are created first. The final holdout comes later.
3 · What goes into the project?
| Input | Plain-language meaning | Research role |
|---|---|---|
| Real-time consumption | Hourly electricity demand. | Primary load target and system context. |
| Source-level generation | Solar, wind, hydro, geothermal, biomass, gas, coal and other fields. | Renewable target, generation mix and regime features. |
| MCP / PTF | Hourly day-ahead clearing price in TRY/MWh. | Price target and market-state signal. |
| Calendar features | Hour, weekday and annual-cycle encodings. | Seasonality without future leakage. |
The software targets official EPİAŞ Transparency Platform REST services. Credentials stay in environment variables and never enter Git history. Raw third-party records are not redistributed by default; reproducibility is preserved through retrieval instructions, source identifiers, manifests and hashes.
4 · How does it work step by step?
Why 168 hours?
One week exposes a full daily and weekly cycle before each forecast origin. It is compact, interpretable and affordable.
Why +1, +6 and +24 hours?
They separate short-, medium- and day-ahead behavior. Transfer may help at one horizon and hurt at another.
Why three tasks together?
Load, renewables and price are coupled yet distinct. That creates both useful-transfer potential and negative-transfer risk.
5 · What model exists today?
The v0.1 model is intentionally compact. Hourly multivariate inputs are projected into a shared representation, receive positional encoding, pass through a Transformer encoder and feed multi-horizon heads. Each output supplies a central forecast and positive uncertainty scale. Split-conformal utilities can then calibrate empirical prediction intervals on a separate calibration period.
6 · What has been completed, exactly?
| Component | Status | What that means |
|---|---|---|
| Repository architecture | Completed | Research package, configs, scripts, tests and documentation are present. |
| EPİAŞ REST client | Completed | TGT authentication and bounded acquisition paths are implemented. |
| Feature & window pipeline | Completed | Hourly alignment, calendar features and leakage-resistant 168-hour windows exist. |
| Shared Transformer | Completed | Compact multi-task, multi-horizon model is implemented. |
| Uncertainty layer | Completed | Probabilistic scale output and split-conformal utilities are implemented. |
| Tests + synthetic smoke training | Completed | Software behavior is tested; synthetic output is not empirical evidence. |
| GitHub CI + Pages | Completed | Automated testing and public documentation are deployed. |
| Real historical EPİAŞ audit | Next | Coverage, missingness, schema stability and timezone integrity must be measured. |
| Exploratory benchmark | Not yet | Strong baselines and runtime budget must be selected without final-holdout evidence. |
| Frozen protocol / OSF | Not yet | Hypotheses, dates, seeds, tests and exclusions are not frozen or registered. |
| Confirmatory results | Not yet | No paper-level model-performance claim exists. |
| Journal manuscript + DOI | Future | Publication follows only after frozen evidence exists. |
7 · Why has the project paused here?
It has not paused because the code failed. Software construction and empirical inference are different phases. If years of real data are inspected first, models are changed after future-period scores are seen, and the hypothesis is written only afterward, a later “confirmatory” claim becomes much weaker.
Research scaffold
↓
Real-data audit
↓
Exploratory model + runtime study
↓
Protocol freeze / optional OSF preregistration
↓
Untouched confirmatory holdout
↓
Evidence archive + paper
Before freezing the experiment we need to know whether data coverage is stable, whether timestamp or schema changes exist, which baselines are credible and how much compute the complete model × seed × horizon plan costs. The pause protects the scientific value of the next stage.
8 · What does the project deliver today?
Research software
EPİAŞ client, data alignment, feature engineering, forecasting windows, shared Transformer, baselines, losses, uncertainty tools and lightweight training.
Research controls
Chronological evaluation, training-only preprocessing, synthetic/empirical separation, deterministic tests and compute-aware configuration.
Publication infrastructure
Research protocol, reproducibility notes, data documentation, manuscript scaffold, citation metadata, multilingual Pages and publication roadmap.
It does not currently deliver an operational market forecast, trading signal, dispatch instruction or validated claim that the shared Transformer is superior.
9 · What can fool this kind of study?
Temporal leakage
Future periods influencing training, scaling or features can inflate apparent skill.
Holdout tuning
Changing the model after viewing final-test scores destroys the meaning of an untouched test.
Weak baselines
A complex model must beat strong seasonal and task-specific alternatives.
Regime blindness
Average error can hide failure during price spikes, renewable ramps or unusual demand.
Uncalibrated confidence
A probabilistic model may sound confident without delivering promised coverage.
Compute drift
An over-large protocol can become impossible to complete and invite post-hoc compromises.
10 · What would count as scientific success?
| Observed outcome | Interpretation | Why it matters |
|---|---|---|
| Shared model wins | Useful transfer | Evidence that cross-task representation learning adds predictive value under the frozen design. |
| Shared model ties | Limited complexity benefit | Evidence that extra architecture gives little practical gain for tested horizons/regimes. |
| Shared model loses | Negative transfer | Evidence that shared representation can damage one or more grid tasks—a scientifically useful boundary. |
A null or negative finding is not a failed project if the experiment is controlled. The research object is the hypothesis, not the model's reputation.
11 · What can be added from here?
| Stage | Work | Deliverable |
|---|---|---|
| v0.2 — Data Audit | Bounded real EPİAŞ history; missing hours, duplicates, timezone/DST, schema stability, generation consistency and price outliers. | Data audit report, availability map, provenance manifest and hashes. |
| v0.3 — Exploratory Benchmark | Persistence, seasonal-naive, linear/MLP, recurrent, task-specific and shared Transformer baselines using train/validation only. | Exploratory benchmark and measured compute budget. |
| v0.35 — Modern Baselines | Add feasible DLinear, N-HiTS/N-BEATS, PatchTST, TimesNet or TFT baselines. | Modern comparison matrix. |
| v0.4 — Regime Intelligence | Define renewable-share, price-spike, load-ramp, seasonal and unusual-demand regimes. | Frozen regime definitions and analysis plan. |
| v0.45 — Explainability | Feature ablation, masking, attention diagnostics and secondary explainability tools. | Interpretability evidence. |
| v0.5 — Pretraining | Explore masked time-series pretraining for a shared representation reusable across downstream tasks. | Stronger foundation-model direction. |
| v0.6 — Transfer | Test low-data adaptation to downstream forecasting, anomaly or regime tasks. | Transfer-learning evidence. |
| v0.7 — Probabilistic Suite | Quantiles, adaptive conformal methods, CRPS and coverage-width trade-offs. | Trustworthy uncertainty benchmark. |
| v0.8 — Stress Testing | Missing observations, delayed data, price shocks, renewable ramps and distribution shift. | Robustness evidence. |
| v0.9 — Protocol Freeze | Freeze holdout, hypotheses, metrics, tests, seeds, exclusions, multiplicity and compute budget; optionally register on OSF. | Immutable confirmatory protocol. |
| v1.0 — Confirmatory Study | Open untouched holdout once; preserve predictions, statistics, figures, configs and hashes. | Paper-level evidence archive. |
| v1.1+ — Publication | Finalize manuscript, citable software snapshot, Zenodo DOI and appropriate preprint/journal submission. | Citable research record. |
12 · The strongest eventual paper
When Does Cross-Task Learning Help Electricity Forecasting? A Reproducible Multi-Task Study of Load, Renewable Generation and Market Price in Türkiye.
The strongest contribution is not a marketing claim that a “foundation model” wins. It is a controlled answer about transfer, horizon dependence, market regimes and calibrated uncertainty, backed by preserved evidence that another researcher can reproduce or challenge.
13 · Research boundary
This repository is research software. It is not an EPİAŞ product, grid-operator tool, production forecasting service, trading recommendation or dispatch controller. Until a frozen real-data study is completed, it should be read as a research platform and experimental design.
OSF Open-Ended Registration accepted and assigned a DOI
The current research lifecycle state is now archived on OSF as a public, persistent registration. Registration DOI: 10.17605/OSF.IO/FMCYQ. Associated OSF project: osf.io/tz5pw.
The registration time-stamps the completed January 2024 real-data EPİAŞ audit, corrective generation-accounting audit, reproducibility rules, and the boundary between exploratory development and a later confirmatory study. It is not the final confirmatory preregistration; the confirmatory holdout remains undefined and untouched.