Hello,
Today I came across Rock
http://rock-robotics.org/
It is based on Orocos, and licensed under GPLv3.
Has anyone used/looked at it? How does it compare to Orocos? The
paragraph on "What's the difference with the Orocos Toolchain?" on the
main page doesn't say much.
I have used Orocos in some projects. Compared to it, the "Data Display
and Analysis" and model based deployment facilities of Rock seem quite
attractive. (Disclaimer: I've only read the documentation, not actually
used it.)
Perhaps I am not the only user interested in these things?
Regards,
Sagar
Rock vs Orocos
On 05/24/2011 12:05 PM, Sagar Behere wrote:
> It is based on Orocos, and licensed under GPLv3.
The "main" license is LGPL, not GPL. Where did you find GPL ? (so that I
can fix that occurence ...)
> Has anyone used/looked at it? How does it compare to Orocos? The
> paragraph on "What's the difference with the Orocos Toolchain?" on the
> main page doesn't say much.
I'm one of the main rock developers, so I can offer some insights.
Rock is a complete toolchain based on the RTT. RTT components are
(supposed to) be usable in the context of the orocos toolchain. However,
quite a few rock tools rely on the availability of specification files
for the components (orogen specification), so using "plain" (non-orogen)
RTT components in rock is unsupported at the moment. This could change
in the future if someone steps up to do it (we can't do it as we don't
*have* plain RTT components)
The release plan for Rock is:
* prerelease in june
* release in september
The main difference between the prerelease and release will be
documentation: reference doc, tutorials and use cases.
Rock vs Orocos
2011/5/24 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
> On 05/24/2011 12:05 PM, Sagar Behere wrote:
> > It is based on Orocos, and licensed under GPLv3.
> The "main" license is LGPL, not GPL. Where did you find GPL ? (so that I
> can fix that occurence ...)
>
> > Has anyone used/looked at it? How does it compare to Orocos? The
> > paragraph on "What's the difference with the Orocos Toolchain?" on the
> > main page doesn't say much.
> I'm one of the main rock developers, so I can offer some insights.
>
> Rock is a complete toolchain based on the RTT. RTT components are
> (supposed to) be usable in the context of the orocos toolchain. However,
> quite a few rock tools rely on the availability of specification files
> for the components (orogen specification), so using "plain" (non-orogen)
> RTT components in rock is unsupported at the moment. This could change
> in the future if someone steps up to do it (we can't do it as we don't
> *have* plain RTT components)
>
> The release plan for Rock is:
> * prerelease in june
> * release in september
>
> The main difference between the prerelease and release will be
> documentation: reference doc, tutorials and use cases.
>
There is some details that could be of interest :
Rock is using ruby (I can't tell precilely what, but it is a difference).
Rock has a pool of existing component.
> --
> Sylvain Joyeux (Dr.Ing.)
> Space & Security Robotics
>
> !!! Achtung, neue Telefonnummer!!!
>
> Standort Bremen:
> DFKI GmbH
> Robotics Innovation Center
> Robert-Hooke-Straße 5
> 28359 Bremen, Germany
>
> Phone: +49 (0)421 178-454136
> Fax: +49 (0)421 218-454150
> E-Mail: robotik [..] ...
>
> Weitere Informationen: http://www.dfki.de/robotik
> -----------------------------------------------------------------------
> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
> Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
> Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
> (Vorsitzender) Dr. Walter Olthoff
> Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
> Amtsgericht Kaiserslautern, HRB 2313
> Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
> USt-Id.Nr.: DE 148646973
> Steuernummer: 19/673/0060/3
> -----------------------------------------------------------------------
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
Rock vs Orocos
On Tue, May 24, 2011 at 16:45, Willy Lambert <lambert [dot] willy [..] ...>wrote:
> > Has anyone used/looked at it? How does it compare to Orocos? The
>> > paragraph on "What's the difference with the Orocos Toolchain?" on the
>> > main page doesn't say much.
>> I'm one of the main rock developers, so I can offer some insights.
>>
>> Rock is a complete toolchain based on the RTT. RTT components are
>> (supposed to) be usable in the context of the orocos toolchain. However,
>> quite a few rock tools rely on the availability of specification files
>> for the components (orogen specification), so using "plain" (non-orogen)
>> RTT components in rock is unsupported at the moment.
>>
>
> There is some details that could be of interest :
>
> Rock is using ruby (I can't tell precilely what, but it is a difference).
>
Maybe I am too biased toward a DSL/MDE/MDA, but as far as I understand the
Rock
(and the orogen in particular) is about providing the user with a
domain-specific language
for the specification of the Orocos components. However, it seems to not
calling itself
a DSL, rather a "tool implemented in Ruby".
In my opinion using Ruby (or any other language) for the job is of second
importance.
Typically in the MDE approach you can use a specialized tools for the the
notation
(where Rock is using Ruby for that) and model-to-text transformation (where
Rock is
using Ruby once again).
For me the benefit from using Rock is that it lifts you a one step higher in
the ladder
of abstraction levels. With Rock you are not building the C++ application
anymore
- instead you are writing a specification of your application, which can be
automatically
transformed into a really valuable artifact, namely a code skeleton. It is
not far for the
Rock to give you another artifacts like i.e. documentation skeletons.
Rock vs Orocos
On Tue, 24 May 2011, Sagar Behere wrote:
> Hello,
>
> Today I came across Rock
> http://rock-robotics.org/
>
> It is based on Orocos, and licensed under GPLv3.
>
> Has anyone used/looked at it? How does it compare to Orocos?
Rock is a very friendly orocos "partner"!
> The
> paragraph on "What's the difference with the Orocos Toolchain?" on the
> main page doesn't say much.
Since there are different development processes, it makes sense to have
several kinds tool support.
> I have used Orocos in some projects. Compared to it, the "Data Display
> and Analysis" and model based deployment facilities of Rock seem quite
> attractive. (Disclaimer: I've only read the documentation, not actually
> used it.)
>
> Perhaps I am not the only user interested in these things?
>
> Regards,
> Sagar
Herman