As far as I can tell (though I've only looked closely at the Pid class), there is nothing PR2-specific in this package. If it existed in a robot-agnostic stack it would be more likely to be discovered, used, debugged, and enhanced by the community. Also it would not require installation of the pr2_controllers stack and all the attendant dependencies.
As far as I can tell (though I've only looked closely at the Pid class), there is nothing PR2-specific in this package. If it existed in a robot-agnostic stack it would be more likely to be discovered, used, debugged, and enhanced by the community. Also it would not require installation of the pr2_controllers stack and all the attendant dependencies.
trac data: