NetcdfReporting with complex types

Submitted by dustingooding on Thu, 2012-08-09 14:13

I'm trying to get the NetcdfReporting component working with complex
types (strings, ROS messages, etc). However, I see that
NetcdfMarshaller only supports char, short, int, float, double, and
double[]. Is the correct approach to write a new Reporting component
and an associated Marshaller (perhaps that inherit from the Netcdf
ones), or is there a way to tell NetcdfReporting about new types?

‹ Error importing KDL typekit rttlua error on import kdl_typekit ›
»
Ruben Smits's picture

NetcdfReporting with complex types

Submitted by Ruben Smits on Thu, 2012-08-09 18:12.

Hello Dustin,

On Thu, Aug 9, 2012 at 4:13 PM, Dustin Gooding <dustin [dot] r [dot] gooding [..] ...>wrote:

> I'm trying to get the NetcdfReporting component working with complex
> types (strings, ROS messages, etc). However, I see that NetcdfMarshaller
> only supports char, short, int, float, double, and double[]. Is the
> correct approach to write a new Reporting component and an associated
> Marshaller (perhaps that inherit from the Netcdf ones), or is there a way
> to tell NetcdfReporting about new types?
>
>
AFAIK the ReportingComponent (and therefor the NetCDF version too) has a
property to decompose types. If it is set to true it will use the typekit
and the typekits getMember function to decompose complex types into smaller
pieces. I don't know about strings but I believe this works for the ROS
messages.

Ruben

> --
> *Dustin Gooding*
> NASA/JSC Robotics
>
>
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>

»