Middleware for Robotic Applications

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
MIRA
DevelopersMetraLabs GmbH,
Ilmenau University of Technology
Initial release27 April 2012; 13 years ago (2012-04-27)
Stable release
2020-04-26 / 26 April 2020; 5 years ago (2020-04-26)
Repository
  • {{URL|example.com|optional display text}}Lua error in Module:EditAtWikidata at line 29: attempt to index field 'wikibase' (a nil value).
Written inC++
Engine
    Lua error in Module:EditAtWikidata at line 29: attempt to index field 'wikibase' (a nil value).
    Operating systemLinux, Windows
    TypeRobotics suite, Middleware
    LicenseDual License:
    GPL Version 3,
    Professional Edition License
    Websitewww.mira-project.org

    Lua error in mw.title.lua at line 392: bad argument #2 to 'title.new' (unrecognized namespace name 'Portal').

    Middleware for Robotic Applications (MIRA) is a cross-platform, open-source software framework written in C++ that provides a middleware, several base functionalities and numerous tools for developing and testing distributed software modules. It also focuses on easy creation of complex, dynamic applications, while reusing these modules as plugins. The main purpose of MIRA is the development of robotic applications, but as it is designed to allow type safe data exchange between software modules using intra- and interprocess communication it is not limited to these kinds of applications.[1]

    MIRA is developed in a cooperation of the MetraLabs GmbH and the Ilmenau University of Technology/Neuroinformatics and Cognitive Robotics Lab. Therefore, MIRA was designed to fulfill the requirements of both commercial and educational purposes.

    Features

    [edit | edit source]

    General:

    • adds introspection/reflection and serialization to C++ with the usage of C++ language-constructs only (a meta-language or metacompilers are not necessary)
    • efficient data exchange between software modules
    • the used communication technique based on "channels" always allows non-blocking access to the transferred data [2]
    • for the user the communication is fully transparent no matter if the software modules are located within the same process, different processes or on different machines, the underlying transport layer will choose the fasted method for data transportation automatically[2]
    • beside data exchange via "channels", MIRA supports Remote Procedure Calls (RPC) and Remote Method Invokation.
    • MIRA is fully decentralized, hence there is no central server or central communication hub, making its communication more robust and allows its usage in multi-robot applications
    Screenshot of MIRACenter

    Robotic Application specific:

    • easy configuration of software modules via configuration files
    • parameters of algorithms can be modified live at runtime to speed up the debugging and development process
    • huge amounts of robot sensor data can be recorded in Tapes for later playback, here different codecs can be used to compress the data

    Platforms

    [edit | edit source]

    MIRA supports and was successfully tested on the following platforms:

    Applications using MIRA

    [edit | edit source]

    MIRA is used within the following applications:

    and projects:

    • CompanionAble - Integrated Cognitive Assistive & Domotic Companion Robotic System for Ability & Security[9]
    • Robot-Era - Implementation and integration of advanced robotic systems and intelligent environments in real scenarios for the ageing population[10]

    Usability

    [edit | edit source]

    Reflection/Serialization

    [edit | edit source]
    class Data 
    {
        int value;
        std::map<std::string,std::list<int> > complex;
        Foo* ptr;
    
        template <typename Reflector>
        void reflect(Reflector& r) 
        {
            r.member("Value",   value,   "an int member");
            r.member("Complex", complex, "a complex member");
            r.member("Pointer", ptr,     "a pointer pointer");
        }
    };
    
    • arbitrary complex data types can be serialized by adding a simple reflect method to the class as shown above
    • after these minor changes, the objects of the class can be transported via inter-process communication, can be used as parameters in configuration files for software modules, can be recorded in "Tape" files, etc.

    Remote Procedure Calls

    [edit | edit source]
    class MyClass
    {
        int compute(const std::list<float>& values);
    
        template <typename Reflector>
        void reflect(Reflector& r) 
        {
            r.method("compute", &MyClass::compute, this, "comment");
        }
    };
    
    • arbitrary methods can be turned into RPC methods by adding one line of code within the reflect() method. There is no need to write wrappers around the methods or to use meta description languages.

    See also

    [edit | edit source]

    References

    [edit | edit source]
    1. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    2. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    3. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    4. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    5. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    6. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    7. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    8. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    9. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    10. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    [edit | edit source]