We are about to move oemof.org to a new web space. To allow for a smooth transition, the new page (this one) is already on-line. So, hopefully, the posts announcing the transitions here and there (at the old site) will be the mayor signs of the relocations. But there is more:
- Improved control: By doing more on our own, we have more flexibility on what we do. Several times already, we came to the point that we wanted to implement something for the page but were not able to because of our web page plan. This will be different from now on.
- Improved data protection: The first thing we use our newly gained power for, is sniping of the trail of your data to third parties. Also, hosting has moved from the US to Europe.
- More to come: This is not planned to be a relaunch but a smooth transition. Honestly, I would not even write this if I did not have to test the post notification mailer.
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.
Continue reading “oemof.solph v0.4 – Unique Unbundling”
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