From: Paul Osmialowski <newchief@ki...> - 2007-04-25 09:11:45
Migration works in our Virtual Laboratory are still in progress. Our
students use Octave (and Octplayer by Cameron Morland) during the classes,
so I had to make it possible to compile it with latest Player. Although
Player wiki pages says it is prepared both for 1.6.5 and 2.0.x I realised
that it's not the truth (BTW, Where Player Client Libraries section has
gone from Extensions wiki page?!). This migration wasn't as easy as I
hoped to be, but finally I did it. Here it is:
New features comparing to octplayer0_19 are:
- Makefile changed so it can also be compiled on old FC3
- new interfaces added: camera, map and localize
- new example of laser interface usage: laserscansxy.m
Another thing is the problem with Stage that I've discovered while working
on laser interface support in Octplayer2. Why range_res is not set at all?
(GetRangeRes() method returns 0.0 all the time). I think it's wrong.
From: Brian Gerkey <brian@ge...> - 2007-05-14 23:34:03
On Apr 25, 2007, at 2:11 AM, Paul Osmialowski wrote:
> Another thing is the problem with Stage that I've discovered while
> on laser interface support in Octplayer2. Why range_res is not set
> at all?
> (GetRangeRes() method returns 0.0 all the time). I think it's wrong.
Yeah, that's a bug; Stage is not filling in that field. To be
honest, I'm not sure what the right value is. Perhaps it depends on
the resolution of the world. Richard?
Note that you don't strictly need the range_res value to interpret
the ranges, because they're always reported in meters.