Is this ranger interface designed to replace all other range interfaces
laser, sonar, infrared, ...? Does someone modify the sick or hokuyo
driver for example so that they implement the ranger interface?
Geoffrey Biggs schrieb:
> It's also worth noting that the new ranger interface in Player 2.1 is
> fully 3D. This interface is in CVS and working already, so if you want
> to get started on writing your driver using this interface, you can.
> Toby Collett wrote:
>> I would like to modify all pose's in player to be a consistent 3d pose.
>> Also do we need a standard on where poses are measured with respect to,
>> i.e. the origin of the component it is attached to, and do we need a way
>> of specifying these attacments? I know those of us doing 3d
>> visualisation have had to specify this in parallel.
>> I have added this to the player 2.1 roadmap. the change to 3d should be
>> pretty much backwards compatible where the player_pose_t type was used.
>> On 6/21/07, * Stefan Stiene* <sstiene@... <mailto:sstiene@...>> wrote:
>> I want to write a driver, that integrates different laserscanners into a
>> single 360° laserscanner, by mapping the laser data of each laserscanner
>> into the horizontal plane. Therefor I need a a player_pose3d_t in
>> laser_geom not a player_pose_t since the laserscanners are not mounted
>> horizontally. Are there any reasons to use a 2d pose instead of a 3d
>> Best Stefan