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:

oemof ask us anything: 2025-02-27

After premier of the “oemof consultation hour” we spontaneously decided to have a short AUA (ask us anything) this Thursday at 16:30 CET. We will try to use our own video call infrastructure (at cloud.oemof.org/call/). So, if you have questions, just dial in and get answers live from the 2025.02 developer meeting.

oemof consultation hour

Next week, at the 30th of January, we will have our first oemof consultation hour from 2 pm to 3 pm CET. To keep the entry barrier low, we plan to have it at https://meet.jit.si/oemof-consulation-hour. Feel free to join, if you have questions or just want to chat about oemof. (Note that there is something similar for the TESPy community for some time now.)

2025.02 dev meeting: Save the date

We just got the feedback that the next oemof meeting will be hosted by the Flensburg University of Applied Sciences from February 26th to 28th. To push the further development of oemof, it will come as a more developer focused meeting. Save the date and contribute, if you are interested! (Beginners, in particular first-time contributors, will get guidance, of course.)

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

Report from the anniversary meeting

The last days, we had our semi-annual meeting to discuss the state of open energy system modelling. This time in the flavour of a user meeting with a special 10-year celebration event. I am so happy that I can tell that the concept worked out: We had almost 40 guests, some of them were on their first oemof meeting. Still, they dynamically formed sub-groups for parallel sessions, had fruitful discussions, shared experiences, and eventually started implementing something together. To kick this off, we asked every participant to give a short pitch at the first day. This was quite a ride, but due to coffee breaks and a poster session in the DLR entry hall, it was possible to identify many persons you wanted to talk to later.

Group photo of those who stayed long enough on Thursday (after the 10-year celebration event). Unfortunately, we forgot to take a picture before.
Continue reading “Report from the anniversary meeting”