Susan Fox wrote:
Hi,
I should apologize for three messages in one day, but I've had a handful
of things crop up this week. I am running either simulated or real
Pioneer robots. Player uses the Pioneer's underlying dead-reckoning
position for robot.x and robot.y. I am using localization to correct
for dead-reckoning errors. To do so, I really need to update the
robot.x and robot.y values, and *not* have them reset from the
underlying system. I haven't had much luck with this before.
Is my best bet to make a subclass of the PlayerRobot class, and force it
not to use the underlying position values, or is there some way to
modify robot.x and robot.y and have it "stick".
Thanks,
Susan
Yes, I would think a subclass of PlayerRobot and then overloading of the
PlayerRobot.update method would do what you want (updating self.x,
self.y, self.thr, and self.th yourself). Of course, player's idea of
where it is wont be any use to you after that (unless you do reset it
ever once in a while). Will you need access to lower-level motor
information like acceleration, etc?
Sounds like a very interesting project; would like to hear more!
-Doug
_______________________________________________
Pyro-users mailing list
[email protected]
http://emergent.brynmawr.edu/mailman/listinfo/pyro-users
