Category: Workshops and Conferences

2026.04 TESPy community meeting

Last week the second TESPy Community Meeting, held in Braunschweig, was a resounding success, offering developers and users an excellent opportunity to exchange ideas in person, discuss new concepts, and collaborate on the further development of TESPy.

The highlight of the meeting was the hackathons, during which participants worked intensively on various topics:

  • Introductory tutorials for TESPy
  • Best practices for initial values in automated simulations
  • Creation of a ModelTemplate class, which can serve as a powerful starting point for user models
  • First steps in implementing a new ejector component

A new TESPy release has already been published based on the results of the hackathons. This release already includes the new ModelTemplate class and also made the OptimizationProblem class compatible with it. Further details about the release can be found in the official release notes:
https://tespy.readthedocs.io/en/main/whats_new.html#whats-new-label

A big thank you goes to Hannes Schneider from Technical University of Braunschweig for the excellent organization and for hosting the meeting. We would also like to thank all participants for the open atmosphere, their enthusiastic participation in the hackathon, and the many engaging discussions.

Join the TESPy user meeting in April

From April 13 to 15 the 2nd TESPy user meeting will be held at the Technical University of Brunswick. You are invited to join us to network and exchange with the community, bring your questions to get help in hands-on tutorials and contribute to the development with your feedback, ideas and discussions. Please register here: https://cloud.oemof.org/apps/forms/s/KGPbPMQQJdeCRkmsEsi86Ezq

Join the upcoming oemof meetings

In just a bit more than a month the next oemof user meeting takes place in Nordhausen parallel to the RET.Con conference. From February 11 to 13 you can join us. You will have the chance to exchange with other oemof users and developers, learn something new in the tutorials and also connect with the participants of the RET.Con. Also, the general assembly of the oemof association will be held at the event. For registration and agenda details check out the wiki page on github: https://github.com/oemof/oemof/wiki/Meeting-2026.02

Two months later the second TESPy meeting will be hosted at the TU Braunschweig from April 13 to 15. We plan some tutorials and many hackathons to work on a couple of open issues and potential new features. Get all the information here: https://github.com/oemof/oemof/wiki/Meeting-2026.04%3A-tespy-user-meeting

2025.10 first ever TESPy community meeting

TESPy has been part of the oemof organization for about eight years. While it has always been represented at the meetings, it was time for the first ever TESPy community meeting!

Last week around ten of us got together at the University of Applied Sciences in Flensburg to discuss where TESPy is headed and how we can make open source thermodynamics even better. The discussions covered a broad range of topics:

  • A review of the most recent feature additions
  • Beginner tutorials
  • Debugging with tespy version 0.9
  • Custom equations into your model
  • Implementation of new components
  • Showcases of how the software is used
  • Strategies for the operation of large scale heat pumps

During the hackathon an addition to a component was not only drafted on paper but actually implemented in the framework. And, it has already
made it to the latest release of TESPy.

It was really inspiring to meet others working with the software, exchange ideas, and see how the community is growing. Thanks to everyone who took their time to come to Flensburg to join the meeting.


Looking forward to the next one!

2025.09 dev meeting retrospective

For the last three days, we were meeting at HTW in Berlin for our semi-annual developer meeting. Here are some of the key results:

  • We plan to have an improved lecture/ tutorial session, that might eventually develop into a summer school.
  • There will be a release of oemof.solph mid November. It will include whatever is done until then.
  • Costs calculations in oemof.solph will be aligned with VDI 2067. We plan to distinguish between energy-related costs (€/kWh), capacity related operational costs (€/kW/a), fixed operational costs (€/a) for OPEX and capacity related investment costs (€/kW/a) as well as an investment cost offset (€/a) for CAPEX. At the moment, we group by units, and thus have CAPEX and OPEX mixed.
  • The SubNetworks, we decided to have at the oemof 2025.02 developer meeting are functional, an example is merged in dev.
  • There is a software implementing robust optimisation. We plan to release something along these lines (as rolph).
  • Some of use will create an awareness concept. For upcoming meetings, there will be an awareness team you can contact if you do feel uncomfortable because of other participants or externals. We will also try to organise ourselves so that you can feel save on your trip back to the hotel.

See you next time (in Nordhausen)!

First tespy community meeting to be hosted in Flensburg

The first ever in-person community meeting of tespy will be held in one month in Flensburg. From October 13. to 15. we will meet at the location of tespy’s origin, Flensburg University of Applied Sciences. There are many interesting topics on the agenda, suitable from very beginners to advanced users and potential future developers.

You can find all details and register here: https://github.com/oemof/oemof/wiki/Meeting-2025.10%3A-tespy-user-meeting

See you in Flensburg!

Save the date: oemof user meeting 2026.02

Our next in-person user meeting will take place in Nordhausen from 11th to 13th of February 2026. It will be hosted by Nordhausen University of Applied Sciences partly parallel to the  9th Regenerative Energy Technology Conference (page in German).

We are posting this save the date already, as the parallel RET.Con also allows to submit contributions to its proceedings. If you wish to do so, please send an abstract (maximum two pages A4) to ret@hs-nordhausen.de. The deadline for abstracts to the RET.Con is the 15th of October. If accepted, full papers will be due at the 15th of January. Registration to the oemof track will be possible later, (as usual) without abstracts and proceedings.

2025.09 Developer Meeting in Berlin: Save the Date 

We just got the feedback that the next oemof meeting will be hosted by Reiner Lemoine Institut from September 15th to 17th at HTW Berlin. Due to the limited room capacity it will come as a developer meeting. Save the date and contribute, if you are interested! (Beginners, in particular first-time contributors, will get guidance, of course.) 

We created a wiki page for the Meeting 2025.09 to work on the agenda. 
 To register, you can either add your name to the linked Wiki page at GitHub, use the registration form, comment this post, or write an email to meetings@oemof.org. 

2025.02 dev meeting retrospective

At the last developer meeting, in sunny Flensburg, we focused on decision making and drafting for the future development of solph. Here are the main results:

  • There is consensus that we should have common approach of facades or sub-networks. Currently, there are several similar implementations, namely facades in oemof.tabular, nested energy system object (used for cellular approaches, now removed), and node containers (in MTRESS).
  • We worked hands on at the documentation. Improvements will be merged to the v0.6 dev branch. We also have a suggested colour palette to use in examples:
    Lapis Lazuli (#1F567D) , Cambridge blue (#8AA8A1), Pumpkin (#FA8334) , Rose (#FF006E), Icterine (#FFFD77)
  • We drafted a new class Results that will eventually replace the nested dict generated by solph.processing.results().
  • Before thinking about alternative back-ends to Pyomo, we should remove code duplication.
Group picture taken at the balcony of the FH Flensburg building near the habour.

oemof AUA 2025/03 (today)

As announced previously on other channels, we have an “ask us anything” session today. Unfortunately, we currently experience issues with the server that runs our cloud infrastructure, including the calendar. Thus, the link we originally shared is currently unavailable. So, here is a summary: