API review

Proposer: Ken Conley

Present at review:

  • List reviewers

This is just a brainstorming document

Parallel killing on shutdown?

Put CPU/mem usage in netapi, roslaunch-console becomes rostop

2-arg calling for roslaunch

Check prefix args, perhaps have a diagnose() function that runs after a launch failure.

Do we want to start adding phases to the launch, e.g. setup, launch, teardown phases?

<include pkg="" > attribute

<exec> tag

<exec args="ls -alF" blocking="true" />

  • General tag for execution. Any executables referenced by it must be locatable on the default system path as roslaunch does not execute via shell on remote machines.

== <rosexec> tag

Like <exec> tag, but specifies that the executable is in ROS_ROOT/bin. This tag must be used when referencing a ROS executable as it guarantees, in the case that multiple ROS installations are on a machine, that the correct ROS executable is found.

<bag> tag

  • By using <bag> tag, can tweak launch time to occur after nodes

  • If we start leveraging namespaces, could automatically record within a particular namespace
  • Another advantage of bag tag is that it can push bags down into a namespace as well.


Package status change mark change manifest)

  • /!\ Action items that need to be taken.

  • {X} Major issues that need to be resolved

Wiki: roslaunch/Reviews/2009-06-01_Brainstorming_API_Review (last edited 2009-08-14 20:53:56 by localhost)