2020 – what a year – the second digital meeting was held in the internet 😉 We had more than 20 participants. The establishment of the oemof foundation is nearing completion. In this year’s social event a neighbourhood board game App was played in the Alpha. Due to the many bugs the challenge became a last-man-standing (winner: Patrik).
The next oemof developer meeting will be held from Wednesday the 2nd to Friday the 4th of December 2020. It will be an online event full of virtual workshops and discussions about technical and organisational aspects of oemof. One topic will be the current status of the “oemof foundation” (working title), which is planned be incorporated at the next in-person meeting.
Anyone who is interested is cordially invited to participate and to contribute topics. All topics including additional information will be collected at the oemof organisation wiki page for the 2020 December Meeting. If you want to register, please contact us in the according ticket at GitHub. You can also suggest additional topics at the same place, we will continue shaping the agenda based on your input at least until the 23rd of November.
After oemof v0.3.2, we decided to make oemof’s structure more clear: Both, the framework (including e.g. TESPy) and the Package for energy system optimisation (using solph) were called the same – oemof. With the release of v0.4.0, there are now split packages for oemof.solph, oemof.network, and oemof.tools.
In 2020 the first digital oemof meeting was held. Unfortunately, we failed to take a video conference screenshot to keep up the tradition of taking photos together. Maybe next time…On the oemof map, Bremen has now been populated as a new location. Despite the digital meeting, 26 participants from 13 different organizations came together. Bremen proclaims its right to the next analog meeting. Whenever that may be…
The oemof meeting stream is available for up to 200 participants without registration. The link can be found here: https://ethercalc.org/b2zg1e72npzv
In the stream questions can be asked via the chat.
If you want to be part of the session and be able to talk you have to send an e-mail with the sessions you want to take part to the following address: oemof_spring_meeting_2020@posteo.eu
On Tuesday night you will get an e-mail with all login details. The limit for each session is 22.
Please also register if you are already on this list, but you will have priority.
Looking forward to seeing you soon online!
Less than a week until the next user/dev meeting will begin. We set up a schedule for the meeting, which might be updated in the next days. We still have some free slots available to organize additional sessions.
For registering, please sign up here (scroll to the bottom). We still have some spots available. If you don’t have sufficient access rights, drop us a line here.
All registered people get access to the web conference. We’ll get in touch with you by mail. The meeting will be streamed including an option for Q&A via chat. The stream will be announced on the wiki page.
If you have any trouble or questions, please ask at contact@oemof.org
The oemof developer and user meeting, which was planned for May 13th-15th, will take place within the same time frame as a slimmed version in the virtual world.
The real life meeting in Bremen will be shifted to the second half of the year.
The agenda which is continuously developed can be found here: https://github.com/oemof/organisation/wiki/Meeting-May-2020-%28online%29
News concerning the registration process follow soon.
If you like to contribute a session, please contact us via: https://github.com/oemof/oemof/issues/59 Deadline for contributions is April 30th 2020.
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 caroline.moeller@rl-institut.de.
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 (caroline.moeller@rl-institut.de). We will develop the agenda based on your input.
Looking forward to meeting you in Berlin!
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:
pip install oemof --upgrade
