Meetings2012-02-02 » History » Version 4

« Previous - Version 4/7 (diff) - Next » - Current version
Anonymous, 02/02/2012 04:24 PM
RST type consolidation - stable

Meetings 2012-02-02

RST Release Management

Type Consolidation

Component-specific (non-domain) Data Types

  • How can these be retrieved?
  • Mandatory installation to file system?
  • Other serialization formats than protobuf?

Meeting Planning

  1. Collect additional topics
  2. Determine topic priorities
  3. Roughly assign to meeting slots (~ short-term, mid-term, long-term)


Type Consolidation


  • rst/audition/ITD.proto: filename should be fulle name, not abbreviation
  • Forces/Torques/Wrench still sandbox-ish (do you need wreench split up?)
  • Do coordinate types need (optional) coordinate systems and units?
  • Yes, express units right inside the proto file
    • For first release, check, that units are documented in every proto file
    • For next release, check how to express units (enum?)
  • For geometry/pointcloud tyes, check compliance with PCL