The next oemof developer meeting starts soon. From Wednesday the 4th (noon) until Friday the 6th of December 2019 (noon) we will meet at the Beuth Hochschule für Technik in Berlin.
Please find the final agenda and the venue here: https://github.com/oemof/organisation/wiki/Meeting-December-2019
A detailed description of the topics can be found at: https://etherpad.wikimedia.org/p/oemof_dev_meeting_dec_2019
Some space for additional sessions is still left.
There will also be a poster session with space for 10 posters. You can present your current work and have the chance to connect with other developers in your scientific field. As the winter meeting has a developer focus, we would like the contributions to address your ongoing developments, interesting new methods, or approaches worth discussing. There are no formal requirements. If you want to show your problems and approaches, feel free to bring a collection of A4/A3 pages and pin them on the board so we can discuss. We prefer an interesting exchange to shiny perfectionism, so a more improvised version would count as a poster as well.
If you like to participate, have topics to add, plan to bring a poster, or only want to be part of oemof’s 5-years birthday party (Wednesday, 4th of December, 17 pm), please register until November 27th 2019 via firstname.lastname@example.org.
Anyone who is interested is cordially invited! We are looking forward to meeting you in Berlin!
The Beuth Hochschule für Technik in Berlin will be our host for the next oemof developer meeting from Wednesday the 4th until Friday the 6th of December 2019. Let’s celebrate oemof’s 5th birthday and use these three days to develop new features and functions and to improve the organization and structure of the community.
Anyone who is interested is cordially invited to participate and to contribute topics. All topics together with additional information will be collected here: https://github.com/oemof/organisation/wiki/Meeting-December-2019
If you want to register or have topics to add please contact us at https://github.com/oemof/organisation/issues/46 or via email (email@example.com). We will develop the agenda based on your input.
With v0.3, the API of the GenericStorage has changed. Due to the open structure of solph, the old parameter names were still accepted, but practically ignored. Therefore users may not notice that a default value is used instead of the value they wanted. Especially after an update from v0.2.x to v0.3.0, code often still runs but produces different results. With the new v0.3.1 release, an error is raised when legacy parameter names are used. We work on a structure to avoid such problems in the future. To update, just:
Approximately 1000 commits since v0.2 have evolved oemof, so that now is the time for a new major “development” release . In the meantime, the number of contributors has almost doubled (to 26). The mix of experienced and new developers helped to further improve structure and documentation. Continue reading “v0.3.0 – Lovely Load”
In 2019 Oldenburg celebrated its premier as a oemof meeting host. We had about 40 participants from 10 different organisations. New formats were presented like the speed poster season and an issue auction. (Note for further meetings: Noone wants energy drinks as price.)
The next oemof meeting will take place in Oldenburg from 15th to 17th of May. The event is hosted by the DLR Institute of Networked Energy Systems. It will combine the 3rd annual user meeting and the 10th biannual developer meeting.
The developer meeting aims at the specification of upcoming features and functions within oemof. The user meeting gives the opportunity to improve and accelerate your work by exchanging with other users. This second part officially starts on Thursday (May 16th) after lunch. It will include an introduction to oemof v0.3.
Recently a book about oemof  has been published. As explicitly stated by the author, this book is not written by the oemof community. Generally, books about software can be a good source to give newcomers a comprehensive view of a field and show how the software can be used to approach problems in that field. In this sense, they can fulfill a purpose that goes beyond what can be reached by the documentation written by the programmers.