[Rock-dev] Matrix as properties
Chris Mueller
christoph.mueller at dfki.de
Mon Mar 12 12:18:17 CET 2012
Alternatively, you can also use /std/vector<double> for defining a fixed
Matrix and
it only needs a small convertion for aligning all elements from the
vector to the fixed matrix.
Though i'm currently working much on NEXT, this was quite comfortable
especially using the ports
on the ruby and yaml side, where you can use Array Literals for math.
matrices and vectors like e.g.:
matrix = [1, 0, 0,
0, 1, 0,
0, 0, 1]
Don't know if something similar is applicable on MASTER.
Surely, this rather a workaround for that, but it would avoid
modifications in the base/orogen/types.
Not sure if it's recommanded; I've have only seen that in another orogen
package, which uses intensively
many matrix vector configurations with different dimensions and it was
quite useful in that moment.
Chris
Am 12.03.2012 11:55, schrieb Sylvain Joyeux:
> On 03/12/2012 11:00 AM, Javier Hidalgo Carrió wrote:
>> Could I do this in a .orogen file:
>>
>> property "Dacc", "/base/Matrix3d"
>>
>> Basically a property using eigen vectors and matrices.
>> and after fill the values using configuration files like task::Name.yml
>>
>> I got this error when compiling the .orogen.
>>
>> ruby1.8
>> /home/likewise-open/DFKI/jhidalgocarrio/iMoby/iMoby-dev/tools/orogen/bin/orogen
>> --corba --parallel-build=4 --transports=corba,typelib
>> --type-export-policy=used imumodel.orogen
>> imumodel.orogen:33: /base/Matrix3d, defined in the base, base
>> typekits, is never exported
> You need to go in base/orogen/types and add /base/Matrix3d in the list
> of exported types that you will find there.
>
> Sylvain
> _______________________________________________
> Rock-dev mailing list
> Rock-dev at dfki.de
> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
More information about the Rock-dev
mailing list