And where did they put it? On the biggest US platform.

Someday we'll get there, someday.

Cringe. China and Russia are building energy infrastructure and here we have Europe open sourcing tools to help cope with its self-inflicted bureaucratic burdens instead.

Yay, sustainability!

Nice. Better energy grid seems like an easy win for Europe. It has enough diversity of sources that just connecting it cleverly can get you crazy efficiency.

e.g. Right now the UK grid is running on just over 80%+ renewable. But when the wind isn't cooperating french nuclear helps.

Broad reliance on renewables just doesn't work without interconnects across large geo regions

Educate me, what’s the point of (open-sourcing) this?

What a great present for Russians planning their drone attacks on Europe. Why not open source military bases and personal development too? It's all theoretically could be found in public sources anyway, so why not help Ivan save some time and put it all together. As a EU citizen, I should be able to freely receive access to public infrastructure data by request, but it should not be put online for everyone to see.

And where did they put it? On the biggest US platform.

Someday we'll get there, someday.

If it were "the EU", it would be on https://code.europa.eu

I moved stuff out of github to a private codeberg while walking my dog.

The moat on that is non existant.

Git repos are distributed by design. I bet all the contributors have at least 1 branch (probably closer to an average of 3) of this project on at least 1 computer that they own.

it's juste a model from Technical University of Munich not an official model from ENTSOE for TYNDP

What exactly is the issue with that?

This is the type of pointless complaint that really go nowhere

Nice. Better energy grid seems like an easy win for Europe. It has enough diversity of sources that just connecting it cleverly can get you crazy efficiency.

e.g. Right now the UK grid is running on just over 80%+ renewable. But when the wind isn't cooperating french nuclear helps.

Broad reliance on renewables just doesn't work without interconnects across large geo regions

Educate me, what’s the point of (open-sourcing) this?

The EU is demanding that the European Network of Transmission System Operators for Electricity (ENTSO-E) implement this ten-year power infrastructure plan transparently. Unfortunately, this modelling has so far been carried out using an expensive, proprietary tool (PLEXOS Energy Exemplar). The results were not easily reproducible. However, with the new model based on PyPSA-Eur, a transparent Ten-Year Network Development Plan can be created.

This is a repo build using the PyPSA python framework. PyPSA is an open-source Python framework for optimizing modern power systems with renewable energy, storage, and multi-sector coupling.

The repo linked “seeks to complement the tools currently used in the TYNDP cycles, especially for Scenario Building (SB) and Cost-Benefit Analysis (CBA). This approach is designed to enhance transparency and lower barriers to stakeholder participation in European energy planning. Beyond Europe, the project aspires to demonstrate the viability of open-source (OS) frameworks in energy planning, encouraging broader global adoption.

Why this report is shared appears to be an application of PyPSA for others to reference and become inspired by its implementation.

Why it’s open source I think is clear from the above paragraph. Open source standards make it drastically easier to harmonise and collaborate while allowing as much engagement as possible to scrutinise the framework.

People who are interested can look at it and use it. People who aren't interested are free to ignore it.

What's the downside of open-sourcing this?

We should commend bureaucracies on the rare instance that they open-source their software, not ridicule them for it.

There's a very expensive process for resource planning the electrical grid that is highly modeling dependent. Most electricity grids are planned with a least cost expansion modeling approach. A small number of incumbent vendors provide expensive closed source tools to do this. There are quite a few open tools in this space, but open energy transition is building consensus around pypsa and pypsa-eur as equivalent top of class models (better in a lot of ways) to use for various IRPs.

All government (funded) software should be at the very least open source.

I think a good example is the Norwegian Meteorological Institute: https://github.com/metno (EEA, though, not real EU, but still)

It's not like all of it is useful for someone else, but it's the principle of it, and allowing people to see what their tax money (sometimes) goes to.

If it were "the EU", it would be on https://code.europa.eu

Git repos are distributed by design. I bet all the contributors have at least 1 branch (probably closer to an average of 3) of this project on at least 1 computer that they own.

This is the type of pointless complaint that really go nowhere

This is a repo build using the PyPSA python framework. PyPSA is an open-source Python framework for optimizing modern power systems with renewable energy, storage, and multi-sector coupling.

Why this report is shared appears to be an application of PyPSA for others to reference and become inspired by its implementation.

I moved stuff out of github to a private codeberg while walking my dog.

The moat on that is non existant.

The reason people cite when defending Github usually isn't the repisitory hosting itself, but the extra features like oull request management and issue tracker that also generate massive network effects by enabling the same accounts to participate in all public projects. Github is nore of a social network posing as a development tool.

Codeberg is not keen on closed-source repos.

Also, I moved about 10 repos to a private Forgejo installation with pretty average (non-trivial) GH actions workflows. Zero repos has workflows running oob (java, .net, node). The moat is a bit there.

does it matter if we have most of our stuff on gh private repos?

it's juste a model from Technical University of Munich not an official model from ENTSOE for TYNDP

It is actually an model that has been developed in collaboration with entso-e by Open Energy Transition. You can read more about it here: https://open-tyndp.openenergytransition.org/

What exactly is the issue with that?

He just told you; US platform.

Thanks for actually answering the question. I was curious, too.

People who are interested can look at it and use it. People who aren't interested are free to ignore it.

What's the downside of open-sourcing this?

We should commend bureaucracies on the rare instance that they open-source their software, not ridicule them for it.

It’s an honest question, perhaps not worded friendly enough. Forgive my English.

Let’s zoom in on your reply, the people who are interested and look at it and use it. What will they be able to do with it?

does it matter if we have most of our stuff on gh private repos?

It is actually an model that has been developed in collaboration with entso-e by Open Energy Transition. You can read more about it here: https://open-tyndp.openenergytransition.org/

Thanks for actually answering the question. I was curious, too.

All government (funded) software should be at the very least open source.

I think a good example is the Norwegian Meteorological Institute: https://github.com/metno (EEA, though, not real EU, but still)

It's not like all of it is useful for someone else, but it's the principle of it, and allowing people to see what their tax money (sometimes) goes to.

Thanks, definitely positive they’re moving towards open and freely accessible modeling tools. I can see the benefits for students and budget-constrained institutions.

check out tangled https://tangled.org/

Codeberg is not keen on closed-source repos.

> Codeberg is not keen on closed-source repos.

A feature, not a bug. If I go to a website meant to distribute source repos (git, etc), I expect them to be FOSS. Also, the title mentions 'EU Open Sources [...]' so this is irrelevant to the topic at hand.

Either way, perfect is the enemy of good, and this is good. You can find hypocrisy or lack of perfectionism anywhere.

He just told you; US platform.

It can be hosted in multiple locations.

I guess if the github UI becomes critical to their continued development or PR then they expose themselves to a potential rug pull by github/microsoft.

I do not know much about the project so I can not tell if that is concern or if there is some other concern at play here or if those concerns apply to this project or not.

Those are the types of details I wanted to see in the comment.

It’s an honest question, perhaps not worded friendly enough. Forgive my English.

Let’s zoom in on your reply, the people who are interested and look at it and use it. What will they be able to do with it?

Thanks, definitely positive they’re moving towards open and freely accessible modeling tools. I can see the benefits for students and budget-constrained institutions.

> Codeberg is not keen on closed-source repos.

Either way, perfect is the enemy of good, and this is good. You can find hypocrisy or lack of perfectionism anywhere.

It can be hosted in multiple locations.

I guess if the github UI becomes critical to their continued development or PR then they expose themselves to a potential rug pull by github/microsoft.

I do not know much about the project so I can not tell if that is concern or if there is some other concern at play here or if those concerns apply to this project or not.

Those are the types of details I wanted to see in the comment.

1. Run the analyses themselves to help them understand it 2. Provide feedback and even improvements 3. Simply trust that the project is run in good faith because there's transparency

check out tangled https://tangled.org/

Don't forget the little `alpha` tag next to tangled !

If I'm working in software development, the last thing I want to do is trust my coding workflow to an alpha-state platform.

1. Run the analyses themselves to help them understand it 2. Provide feedback and even improvements 3. Simply trust that the project is run in good faith because there's transparency

Don't forget the little `alpha` tag next to tangled !

If I'm working in software development, the last thing I want to do is trust my coding workflow to an alpha-state platform.

Surely can't be worse than GitHub going down every 15 minutes no?

Also remember "git" is decentralized itself, you're supposed to have your git repo locally too, if PR's, or issues or comments are "alpha" your code shouldn't be affected by it at all

Im personally down to try alpha software usually, i just havent found the need to retrain all my muscle memory to not use GH yet, as much as I hate it's owned by microsoft nowadays.

They also do offer pretty good "free tier" services for CI via Actions that otherwise you'd need to pay yourself

Cringe. China and Russia are building energy infrastructure and here we have Europe open sourcing tools to help cope with its self-inflicted bureaucratic burdens instead.

Yay, sustainability!

China is building for sure, but Russia? The majority of russia does not have normal roads, full of crappy old trains, and infrastructure which was built in the soviet times. Russia is a joke of a country, oligarchy and kleptocracy rules.

Also remember "git" is decentralized itself, you're supposed to have your git repo locally too, if PR's, or issues or comments are "alpha" your code shouldn't be affected by it at all

Im personally down to try alpha software usually, i just havent found the need to retrain all my muscle memory to not use GH yet, as much as I hate it's owned by microsoft nowadays.

They also do offer pretty good "free tier" services for CI via Actions that otherwise you'd need to pay yourself

With satellite data, any large grid infrastructure is visible from sky. See https://openinframap.org & things that are visible from sky are also visible by humans walking around.

Also, some data create more benefits when being public: https://nworbmot.org/blog/open-grid-data.html (incl. data that increases certain risks)

With satellite data, any large grid infrastructure is visible from sky. See https://openinframap.org & things that are visible from sky are also visible by humans walking around.

Also, some data create more benefits when being public: https://nworbmot.org/blog/open-grid-data.html (incl. data that increases certain risks)

GitHub release (latest by date including pre-releases) Commits behind PyPSA-Eur

Citations & Data:

Open-TYNDP: Interfacing Open Energy System Planning with ENTSO-E Models and Contributing to TYNDP

[!WARNING] Open-TYNDP is under active development and is not yet feature-complete. The current development status and the general Limitations are important to understand before using the model.

This repository introduces the open model dataset of the Open-TYNDP research and innovation project, which is a collaboration between Open Energy Transition (OET) and the European Network of Transmission System Operators for Electricity (ENTSO-E). The project’s aim is to explore and consider the adoption of PyPSA in the Ten-Year Network Development Plan (TYNDP) by building a workflow based on PyPSA-Eur. It seeks to complement the tools currently used in the TYNDP cycles, especially for Scenario Building (SB) and Cost-Benefit Analysis (CBA). This approach is designed to enhance transparency and lower barriers to stakeholder participation in European energy planning. Beyond Europe, the project aspires to demonstrate the viability of open-source (OS) frameworks in energy planning, encouraging broader global adoption.

To build trust in and ensure reproducibility with the new open-source toolchain, the project first focuses on replicating key figures from the 2024 TYNDP cycle, before aligning with the current 2026 TYNDP cycle. This process involves developing new features within the open-source domain to address existing gaps, integrating tools for data interoperability and dynamic visualizations, and publishing best practices to encourage the adoption of open energy models. Additionally, the project emphasizes stakeholder consultations and interactive workshops alongside the development of the PyPSA tool, further promoting collaboration and transparency throughout the process.

This repository is a soft-fork of OET/PyPSA-Eur and contains the entire project Open-TYNDP supported by OET, including code and documentation. The philosophy behind this repository is that no intermediary results are included, but all results are computed from raw data and code.

This repository is maintained using OET's soft-fork strategy. OET's primary aim is to contribute as much as possible to the open-source upstream repositories. For long-term changes that cannot be directly merged upstream, the strategy organizes and maintains OET forks, ensuring they remain up-to-date and compatible with upstream on a regular basis, while also supporting future contributions back to the OS repositories.

Development status

Warning: Open-TYNDP is under active development and is not yet feature-complete. The current development status and general Limitations are important to understand before using the model. The model includes partial data from the TYNDP 2024 cycle, and its validation is ongoing. The github repository issues collect known topics we are working on (please feel free to help or make suggestions). The fact that this project relies on a soft-fork strategy implies that upstream issues need to be addressed in the PyPSA-Eur repository. The documentation also remains work in progress.

Repository structure

benchmarks: will store snakemake benchmarks (does not exist initially)
config: configurations used in the study
cutouts: will store raw weather data cutouts from atlite (does not exist initially)
data: includes input data that is not produced by any snakemake rule
doc: includes all files necessary to build the readthedocs documentation of PyPSA-Eur
envs: includes backup conda environments if pixi installation does not work.
logs: will store log files (does not exist initially)
notebooks: includes all the notebooks used for ad-hoc analysis
report: contains all files necessary to build the report; plots and result files are generated automatically
rules: includes all the snakemakerules loaded in the Snakefile
resources: will store intermediate results of the workflow which can be picked up again by subsequent rules (does not exist initially)
results: will store the solved PyPSA network data, summary files and plots (does not exist initially)
scripts: includes all the Python scripts executed by the snakemake rules to build the model

Installation and Usage

1. Installation

Option A: Windows Installer (Recommended for Windows)

For Windows users, download the latest installer (e.g., open-tyndp-0.4.0-pixi-Windows-x86_64.exe) from the releases page and run it. The installer automatically sets up everything you need, including pixi, the repository, and the conda environment. See utils/windows-installer/README.md for details.

Option B: Manual Installation (All Platforms)

Clone the repository:

git clone https://github.com/open-energy-transition/open-tyndp

PyPSA-Eur, and consequently Open-TYNDP, relies on a set of other Python packages to function. We manage these using pixi. Once pixi is installed, you can activate the project environment for your operating system and have access to all the PyPSA-Eur dependencies from the command line:

pixi shell -e open-tyndp

[!NOTE] pixi will create a distinct environment in every project directory, even if you have identical copies of a project cloned locally. As there is a common system-level package cache, pixi efficiently conserves disk space in such cases.

[!TIP] If pixi isn't working, you can install from one of the fallback conda environment files found in envs. For more details see the PyPSA-Eur installation guide.

2. Run the analysis

To run all analysis steps of the Scenario Building to reproduce results and build the report, you can execute:

pixi run tyndp-sb

To list all the rules that need to be executed (dry run), run:

pixi run tyndp-sb -n

Similarly, to run all steps of the Cost-Benefit Analysis, you can execute:

pixi run tyndp-cba

and append -n for the corresponding dry run:

pixi run tyndp-cba -n

[!TIP] Dependency graphs can be built by a dedicated pixi task and saved to the resources/ directory. Since this can grow very large for the full list of scenarios, you can restrict it to a single scenario:
pixi run create-tyndp-graphs --config 'run={"name":"NT"}'

Contributing and Support

We strongly welcome anyone interested in contributing to this project. If you have any ideas, suggestions or encounter problems, feel invited to file issues or make pull requests on GitHub.

To discuss with other PyPSA users, organise projects, share news, and get in touch with the community you can use the Discord server. Open-TYNDP has its own dedicated channel pypsa-open-tyndp for project-specific discussions.
For bugs and feature requests, please open a new issue. We provide templates geared for community members to report bugs or request features, but you're also welcome to use the more detailed maintainer-oriented templates if you're comfortable with them. The Open-TYNDP team reviews new issues shortly after they are submitted. Issues specific to Open-TYNDP belong on the Open-TYNDP Issues page, while PyPSA-Eur issues should be submitted to the PyPSA-Eur Github Issues page.

Contact

For any questions about Open-TYNDP or other queries, reach out via the pypsa-open-tyndp channel or tyndp@openenergytransition.org.

Citation

If you want to cite a specific Open-TYNDP version, since v0.5, each release is archived on Zenodo with a release-specific DOI:

Versions v0.5 and v0.5.1 are archived at 10.5281/zenodo.18494362.

If you use Open-TYNDP in your research, please cite it as shown on Zenodo or using the "Cite this repository" button in the sidebar of Open-TYNDP.

This work builds upon PyPSA-Eur and follows the methodology described in ENTSO-E's and ENTSOG's TYNDP 2024 Scenarios Methodology Report.

Licence

Open-TYNDP is a soft-fork of PyPSA-Eur, relying on a similar licensing strategy. As with PyPSA-Eur, the code in Open-TYNDP is released as free software under the MIT License, see Licenses for attribution and licensing strategy details. Additionally, different licenses and terms of use may apply to the various input data, see Data Sources.

Hacker Times