← Energy board · written 2026-10-18 by claude-opus-5-5 from the pipeline's evidence only

Lukas Trippe (lkstrp): energy, open-source power system modelling

Skoor 35 · n = 3 signals · confidence 0.7

What they built

Trippe commits to PyPSA, an open-source Python framework for optimising and simulating power and energy systems. It covers generators with unit commitment, wind and solar, hydro, storage, sector coupling and linearised power flow [source]. It is made for researchers, planners and utilities [source]. PyPSA was created in 2016 and has many contributors [source]. His GitHub account dates from 2020 [source].

He also commits to PyPSA-Eur, a sector-coupled optimisation model of the European energy system [source]. The one repo he owns is a newspaper scraper. It has 22 stars and was last pushed in May 2023 [source].

Record

Measured signals:

27 of the 100 commits to PyPSA/PyPSA in the last 90 days are his [source].

He made commits in the last 90 days to both PyPSA/PyPSA and PyPSA/pypsa-eur [source] [source].

He has 2,990 commit contributions in the last year [source].

PyPSA/PyPSA has 2,197 stars and 719 forks [source]. PyPSA-Eur has 623 stars and 475 forks [source].

His profile lists Technische Universität Berlin and has 37 followers [source].

Inference: about a quarter of recent PyPSA core commits points to a maintainer-level role. Whether he is a listed maintainer is not in the evidence.

Why now

Both PyPSA repos were pushed within two days of observation [source] [source].

Inference: the activity is current, not historical. Any company, spin-out plan or commercial trigger is not in the evidence.

Unknowns

His role at TU Berlin (student, researcher, staff): not in the evidence.
His commit count on PyPSA-Eur: not in the evidence.
Papers: none listed in the evidence.
Users or customers of PyPSA: not in the evidence.
Intent to start a company: not in the evidence.
Bio, blog and Twitter are empty [source].

Questions for the room

"You wrote 27 of the last 100 PyPSA commits. Which parts of the codebase do you own, and who decides merges?" This tests the maintainer-role inference.
"Who runs PyPSA in production today: utilities, planners or researchers, and what do they pay for, if anything?" This tests the stated audience in the README.
"Is the 2,990 commits a year mostly PyPSA work under TU Berlin, and would you leave to build on it?" This tests what the activity signal actually measures.

What would move the Skoor

It would rise with evidence of a company or spin-out, named utility or planner users, or authored papers. It would fall if most recent commits turn out to be maintenance or automation, or if his role is tied to the university with no intent to leave.