It is now possible to registrate for the Hands-on-Workshop “Co-Simulation in Smart-Grids with mosaik” from 28. April 2015 13:00 to 29. April 2015 13:00 at AIT - Austrian Institute of Technology in Vienna.

You can register by using this form and sending it not later than 27. March 2015 to mosaik-workshop at offis.de. More information in the form.

There is a preliminary agenda. You can find information about the workshop in our last blog.

While we implemented some cool new features for mosaik-hdf5 we found some new bugs in mosaik which are now fixed in Mosaik 2.1.2 .

You can get the new version by running pip install -U mosaik.

Mosaik 2.1.1 now prints a warning message if a simulator’s entities were not connected. It also fixes some problems with the internal data-flow cache.

You can get the new version by running pip install -U mosaik.

We just released moasik 2.1. It’s only been about a month since version 2.0, but we already implemented some cool new ideas (some originating from the workshop in Risø last month) and added tons of documentation. So mosaik is now even better, faster and easier to use.

Here is the complete change-log for this version:

• [NEW] Mosaik can now perform real-time simulations. Before, this functionality needed to be implemented by simulators. Now it’s just World.run(until=x, rt_factor=y), where rt_factor defines the simulation speed relative to the wall-clock time (issue #24).
• [NEW] Simulators can now expose extra methods via their API that can be called from a mosaik scenario. This allows you to, e.g., store static data in a data base. These extra API methods need to be specified in the simulator’s meta data (issue #26).
• [NEW] util.connect_many_to_one() helper function.
• [NEW] More and better documentation:
  • Tutorial for integrating simulators, control strategies and for creating scenarios.
  • Sim API description
  • Scenario API description
  • Sim Manager documentation
  • Scheduler documentation
  • Discussion of design decisions
  • Logo, colors, CI
• [NEW] Added util.sync_call() which eases calling proxied methods of a simulator synchronously.
• [CHANGE] The rel attribute in the entity description returned by create() is now optional.
• [CHANGE] Moved proxied methods from SimProxy to SimProxy.proxy in order to avoid potential name clashes with other attributes.
• [CHANGE] Check a simulator’s models and extra API methods for potential name clashes with the built-in API methods.
• [CHANGE] The argument execution_graph of World was renamed to debug. The execution graph now also stores the time after a simulation step (in addition to the time before the step).
• [FIX] issue #22: The asynchronous requests get_data() and set_data() now check if the async_requests flag was set in World.connect().
• [FIX] issue #23: finalize() is now called for in-process Python simulators.
• [FIX] issue #27: Dramatically improved simulation performance (30 times as fast in some cases) if simulators use different step sizes (e.g. 1 minute and 1 hour) by improving some internal data structures.

To get the new version, run pip install -U moasik from within your mosaik virtualenv. If you have any questions or feedback, please come to our mailing list.

At the same time as the release of mosaik 2.0, DTU and OFFIS arranged the first mosaik Workshop in order to bring developers and (prospective) users of mosaik together.

The event took place at DTU’s premises at Risø September 24, 2014 and was attended by about 20 international participants from DTU as well as guests from Sweden (KTH), Austria (AIT) and Germany (Uni-Passau and IWES).

Beside a thorough introduction to mosaik, the focus of the workshop was on practical work. Anna Kosek (DTU) demonstrated the integration of a PV-plant of DTU’s SYSLAB with mosaik. This turned out to be very straightforward thanks to SYSLAB’s and mosaik’s Java APIs. Later, Stefan Scherfke (OFFIS) and Giuseppe Costanzo (DTU) showed how to connect a house simulator with controllable loads to mosaik.

After a productive event, the participants travelled home with a lot of impressions and know-how about mosaik and its use cases. And we came back with a lot of feedback and with new ideas for the further development of mosaik.

After half a year of alpha versions, we are very pleased to finally release mosaik 2.0!

Changes in this version:

• [NEW] A lot of documentation improvements.
• [NEW] mosaik.util.connect_randomly(): a utility method that randomly connects two sets of entities with each other.
• [CHANGE] The mosaik logo was slightly updated. It now uses plain colors instead of gradients.
• [CHANGE] The Sim API version and mosaik’s package version are now separated. Sim API versions are always integer numbers, while semantic versioning is used for the Python package (issue #17).
• [CHANGE] The default timeout for starting and stopping external simulator processes was raised to ten seconds.
• [CHANGE] mosaik.simulator was renamed to mosaik.scheduler to avoid confusion with the actual simulators.
• [CHANGe] Entiy and World.entity_graph now also contain the simulator name, because the model name may not be globally unique.
• [FIX] issue #16: When a simulator unexpectedly closes it socket, its name will now be printed to ease debugging.

We still have a lot more ideas for new features, but by now we consider mosaik ready enough for a broader audience.

The mosaik-demo was also updated and uses mosaik 2.0 now.

To get the new version, run pip install -U moasik from within your mosaik virtualenv. If you have any questions or feedback, please come to our mailing list.