Feature full rules

[irm-codebase]

Fixes #1

Summary of changes in this pull request

• Full processing of powerplants at global scale
• Subdivided in to 7 categories (solar, wind, nuclear, hydropower, geothermal, bioenergy, fossil)
• Solar has unique steps that calculate 'missing' rooftop PV capacity using statistics and a proxy

Reviewer checklist

• INTERFACE.yaml is up-to-date with all relevant user resources and results.
• The integration example is up-to-date with a minimal use-case of the module.
• Module documentation is up-to-date.

[irm-codebase]

@sjpfenninger the module is (for now) feature-complete.
All data (including test data and a sample of the alternative wind dataset) are in this zenodo repo: https://zenodo.org/records/16541007

Brief summary:

Necessary inputs

• country borders
• desired shapes / regions
• proxy for rooftop PV

Configuration

• 7 categories (solar, wind, bioenergy, fossil, geothermal, nuclear, hydropower)
• 2 output options (adjusted or unadjusted to national statistics)
• 4 scenarios of planned future capacity (historical, near-future, far-future, far-off-future)
• Technologies and fuels within each category can be re-mapped to enable different degrees of simplification (e.g., 1 or 5 types of nuclear reactor, 5 or 1 types of coal, etc).
• Users can remove or impute individual powerplants if necessary, before aggregation.
• Adjustable reference year (max 2023, which is recommended).

Testing
Besides the integration test, you can test it locally at 3 levels of computational expense (MNE-1region, MEX-32 regions, Europe-30+ countries). Running these tests will also give you the report and the DAG of the module.

Missing stuff (not for this PR)

• Documentation

[sjpfenninger]

It generally looks great!

There is quite a lot going on, so a high-level overview of the steps, and the data sources used, in docs/index.md is really required.

I did not go very deep into code for imputing and the special treatment of solar, but the results that I looked at are credible.

[sjpfenninger]

If gregor needs to be dependency across multiple modules, it should become part of the org. Otherwise, this will be problematic again and again

[irm-codebase]

Agreed. I'm just waiting for the latest release, to use the official version.

[irm-codebase]

@sjpfenninger I've fixed most review comments. Two things are still missing.

• Documentation is missing
• REFERENCE_YR in _utils.py should change to DATASOURCE_YEAR or something. I also need to adjust the approach based on our recent conversation of reference year standardisation. Once we have clear agreement there it's not a hard thing to update.