Version 7 (modified by sylvain.joyeux, 8 years ago) (diff)


  • slam => localization vs. mapping vs. SLAM
    • use tags ?
  • separate system monitoring types ? temperature, voltage,
    • options:
      1. create a separate tools/system_monitoring package with the types (and corresponding tools/orogen/...)
      2. add to base::samples
      3. add to base::system_monitoring
  • vote on NaN for unknown position / orientation
    • related vote: default initialization on RigidBodyState
  • cleanup of filters (orientation_estimator, pose_estimator)
    • place of covariance: in sensor, as property of the filter
    • have it both ways: make the sensors output it, but also offer a way to override it on the estimator components
    • type / naming scheme
  • [Janosch] vizkit: pain to create and updating (move around, ...) primitives


  • how to add types to base/types => discussion + vote needed on rock-dev
    • two resolutions: either goes into base/types or stays on a separate package


  • add tags to packages
  • package documentation
    • improve package directory layout
    • allow custom pages to be added per-package
  • show available vizkit3d plugins and vizkit widgets
    • integrate in orogen types pages (what displays type X)
    • can use rock-inspect code for that
  • openrobots integration
    • PA10 driver
  • cross compilation
  • compilation times
    • test Sylvain's patch
    • debian packaging
    • remove unneeded dependencies across typekits (remove direct inclusion of Types.hpp from every typekits)
  • rock-display / rock-replay:
    • does not work fine with slow links
    • reconnect not working properly (OBJECT_NOT_EXIST)
    • non-smoothness in vizkit
  • make orogen display a warning if needs_configuration got added but the constructor is not updated yet
  • transformer
    • TODO:
      • documentation
      • ruby scripting integration
      • log replay integration
      • live display integration
    • goal: be able to select a data stream and display it, in 3D, in its frame
    • display / replay
      1. add the frame in every data samples. Requires changing types and components.
      2. save all the required information (static transformations, producer-to-frame-transform mappings, port-to-frame associations) in (a) separate log stream(s). For live, have a separate component that stores the same information.
        • needed: data and transformation from data to display frame
        • information broadcasted / stored:
          1. associations (task & port => frame)
          2. producers associations (task & port => dynamic transform)
          3. static transformations
        • Vizkit3d is given a port (normal port-to-widget connection mechanism)
        • does port => port_frame translation using 1.
        • queries a transformer instance to get root_frame => port_frame using 2. and 3.
        • one transformer per connection
        • first step: don't align
    • see bla.rb
    • fix load times of typekits
    • fix orogen loading
    • allow limited access to remote components even though the model is not available
    • change to have more of a "showcase" style: short descriptions + one video for each topic.
    • robots running rock page ?
  • Release schedule

Attachments (1)

Download all attachments as: .zip