Anyone seen this?
http://www.hindawi.com/journals/jr/2012/959013/
Especially look at table 2:
They suggest that Orocos does not support behavior coordination (we
have at least two mechanisms!).
I would also question that the Control model is "Event-based
control". This is supported, but non-event driven synchronous
data-flow is equally possible.
Apparently distributed environments are also not supported, sigh.
Markus
Orocos in "Robotics Middleware: A Comprehensive Literature Surve
On Thu, Jan 10, 2013 at 10:24 AM, Markus Klotzbuecher <
markus [dot] klotzbuecher [..] ...> wrote:
> Anyone seen this?
>
> http://www.hindawi.com/journals/jr/2012/959013/
>
> Especially look at table 2:
>
> They suggest that Orocos does not support behavior coordination (we
> have at least two mechanisms!).
>
> I would also question that the Control model is "Event-based
> control". This is supported, but non-event driven synchronous
> data-flow is equally possible.
>
> Apparently distributed environments are also not supported, sigh.
>
These papers are as usual very subjective. For starters, Orocos is hardly a
middleware but a component based software framework for robotics.
The paper looks to me as a bunch of copy-paste snippets from various
websites, written by people who have hardly used the software they reviewed
(I'm particularly curious how they could review OPROS and what that tells
us about their Korean reading skills. The first tutorial (on the *english*
webpage) is like this:
http://ropros.org/pages/viewpage.action?pageId=4980857 please scroll down
all the way ! :-) )
Peter