This is a list of some questions we recently got. If you cannot find an answer for your questions here, you are welcome to post it on our mailing list.
An environment for graphical analysis as well as scenario design is currently developed and will presumably be released in 2015. However, we argue that graphical tools are not feasible for the design of large and complex scenarios. For most applications the more flexible scenario design by code is advantageous.
There is none yet but it’s quite on top of our to-do list. You’ll soon find one here.
We like Wikis but consider them the wrong tool for documenting software (and we are not alone with that).
There are a lot of other resources, though:
There’s not much that a wiki could add here.
Yes. Since mosaik 2 you can even use a variable step size for your simulator that can dynamically change during the simulation.
No, mosaik can be used with any language that provides network sockets and ways to (de)serialize JSON.
Since implementing network event loops and message (de)serialization is repetitive work and unnecessary overhead, we provide so called high-level APIs for certain languages that provide a base class that you can inherit and just need to implement a few methods representing the API calls.
Currently, a high-level API is only available for Python, but implementations for JAVA and other languages will follow soon.
Yes, you can. We will provide an example soon. In the end, if you manage to let your model communicate via sockets and are capable of serializing/deserializing JSON data objects you can use it with mosaik (see Can I use mosaik only with Python programs? for details).
Of course, it only depends on your models. The basic models distributed with mosaik 2 only produce active power outputs (cos phi = 1), so we don’t display reactive power.
Check https://bitbucket.org/mosaik/mosaik-pypower under “input file format”. Typically, line values are given in R per km and X per km.