In the last days, we intensively discussed the next steps in the development of oemof. It was very intense and exciting to see other enthusiastic developers in person, drafting solutions at the white board and reviewing code in the presence of the persons who wrote it. We discussed long-term plans but also very particular problems, e.g. how to rewrite up-times in solph so that they are meaningful in models with time-steps of varying length. The most noticeable topics were mostly considering solph:Continue reading “2023-11 dev days: Retrospective”
At the last user meeting, we decided that there should be more pre-releases. So, here we go: Today, there is a version “continuous clean-up” of oemof.network (github.com: oemof-network/v0.5.0a5, oemof.network · PyPI). As the code name suggests, it is mostly a clean-up without adding new functionality. However, the code quality improved quite a lot and we have prepared the deletion of code that is unused or seems to be unnecessary. So, please check out this alpha release to tell if we are wrong.
Update: Deprecating the use of network.Source and others in favour of network.Node only makes sense when the latter is really part of the public API. so, we’re at v0.5.0 alpha 5 already.
For next year’s user meeting, we take a special opportunity: It will be held from 7th to 9th of Februar 2024, partly in parallel to the 7th Regenerative Energy Technology Conference (RET.Con) in Nordhausen. The oemof user meeting will be in its established style, but we want to make it possible for attendees to the conference (which is held mostly in German) to visit presentations and tutorials given at the user meeting. Additionally, it is possible to add an entry for the proceedings of the conference.
This is also why we are announcing the user meeting already before the dev days have taken place: For the RET.Con, there is a deadline for abstract submission at the 30th of September 2023. Note that papers should be in German but presentations may also be in English. If you do not want to publish a paper, you can hand in a headline and a very brief summary for a talk until the 15th of November, so that an announcement can be made at the RET.Con. At last, of course you can ignore this early deadline and present something at the user meeting without having it announced at the conference.
If you want to want to submit something for the RET.Con via the oemof user meeting, please send an email to firstname.lastname@example.org. All emails to this address will also be forwarded to the organisers in Nordhausen.
Today, oemof.solph v0.5.1, code name “compilant converter” has been released. (Package at PyPI, Tag at GitHub). The most noteworthy addition is a new (still experimental) feature multi-period (dynamic) investment models. The code name refers to a small but maybe more evident change: The component
Transformer is renamed to
Converter. This is because people typically think of electrical devices when they hear the word “transformer”. However, as experienced users of our package know, the Transformer is neither meant to be (only) electrical nor bidirectional (as electrical transformers typically are). Thus, the more generic term “converter” is now used. (Note that we always had the argument “conversion_factor”.) To maintain compatibility for v0.5.0, there is a transitional wrapper that still allows to name the component “Transformer”. It will keep telling you about the upcoming change, though. Another usability feature is the presentation of the examples as part of the documentation. Also, we fixed error when calling
oemof_installation_test as a console script. It turned out to confuse quite a few new users that it did not work as documented in the previous release.
We hope to have a fair balance between improvements in usability and new (experimental) features to make this an exciting release for all kinds of users. For us, it definitely is.
We opened registration for the omof developer meeting 2023. (As suggested by the local organisers, Fraunhofer UMSICHT, they are now “dev days”.) The meeting will take place in the Osterfelder Straße 3 in Oberhausen from the 22nd to the 24th of November 2023. At the moment, the agenda is still blank and leaves plenty room for ideas. It will be continuously developed at https://github.com/oemof/oemof/wiki/Meeting-2023.11 – depending on suggestions from registrees.
We always try to keep the entry barrier as low as possible. The meeting is targeted to everybody who wants to contribute to oemof. Of course this includes the further development of the packages, but in the past there have been also non programming-related sessions, e.g. about the content of this website. We have no conference fee, you only have to organise and pay for travel, accommodation, and food. To register, please send an email to email@example.com or post a comment at https://github.com/oemof/oemof/issues/112.
We have a release candidate for v0.5.1 (Package at PyPI, Tag at GitHub). There are some additions, but we also prepare for significant API changes that will come obligatory with v0.6. When upgrading from v0.5.0 to v0.5.1, there should be no changes required for you code. (This is not true if you use features that are explicitly marked “experimental”. Those may change without notice.)
Noticeable changes include:
- The component
Transformeris now named
- You can now combine
- Having energy stored in a
GenericStoragecan now have a cost.
- You can now give an
Investmentobject as the
nominal_value. We considered this more intuitive than working with two mutually exclusive different keyword arguments.
- Tons of improvements in the (still experimental) MultiPeriod optimisation.
Again, there are transitional wrappers, so nothing should break when updating from v0.5.0, using the new API should be voluntary (you get a warning) for now. It would be nice if you test if your solph v0.5 code still works with this RC. We are aiming for a final release of v0.5.1 by the end of August.
For many years, we have had a newsletter (via email). However, in recent time there were issues with that. For example, newsletters were delayed or not delivered. Sorry for that. (Note: Technical tests using a small number of recipients often worked, but with an increasing number of subscribers to address we had issues e.g. with spam protection measures. (Some sources go so far to call email “broken”, e.g. CERN and wired. But if you can help out, you are warmly welcome.)
Of course, there are alternative protocols developed exactly for announcements. Some have always existed at our site, but have not been promoted. For example, we of course have RSS and ATOM feeds. Also, we are working on modern a alternative, namely support for ActivityPub. Luckily, it is easily activated in WordPress.
To work around the issue that you can only subscribe authors, there is now a virtual author “News Bot”. That one will be co-author to posts that should be announced in the Fediverse.
We are happy to announce oemof.solph v0.5.0 (codename “Rigorous refactoring”) . This release brings an extreme shift towards more user focused design:
- Clean definition of time indexes: You need N+1 points in time do define N time spans.
- Parts of the energy system graph are now clearly structured into
flows. This adds some extra words to imports but makes the underlying logic more transparent.
- Public and private API are be more distinguished now. (‘_’ signifies private, public API is defined in init files.)
- Experimental code is now sitting in sub-modules called
- The flow arguments
summed_maxnow have the more descriptive names
- Keyword arguments are now explicit. This will make it easier to find the correct arguments and will also catch typos. Custom attributes can be added using the argument
custom_attributes. Those will be passed down the class hierarchy and can (possibly) be handled in parent classes.
inactivity_costsas an option for
Flows. Inactivity costs is a cost for times where a Flow is not operated.
- Examples are added to the documentation. (The format of the examples could be improved, though.)
Besides these changes, there is one big thing that has happened “under the hood”. It is now possible to combine
NonConvex and Investment optimisation in the same
We are happy to announce that we have released a new version of oemof.tabular. Oemof.tabular allows to create energy systems from tabular datapackages, which makes it easy to build models without writing a lot of code.
The focus of the release has been the adaption of tabular to oemof.solph 0.4.5. The following changes have been made:
- Adjusted to new oemof.solph structure.
- Allowed definition of costum foreign keys. Keys and related descriptors are now read from config files (.json) and can be adopted by setting environment variables using custom config files.
- Added constraint tests for most facades.
- Reduced number of imported packages.
- Cleaned up the badges in README.
- Moved CI services to GitHub actions.
The following issues have been fixed:
- Fixed Link by not setting constraints that limit direction.
- Fixed storage investment with existing capacities
- Introduced a conditional to fix error when running datapackages with expandable links.
- Fixed typo in the attribute
- Introduced marginal costs for both output flows instead of only one to avoid elimination of energy.
A detailed summary can be found here.