On 02/27/2012 06:42 PM, gauthampdas wrote:
Inside of the client's "info" member is are a few fields such as
"datatime" and "fresh". You can use these to determine when
read() was successful and you have valid information in the client.
1). I am using python api (playerc) of player 2.1.3. Almost all were
working fine when I was testing in stage (2.x and 3.x). When I started
testing in pioneers, after a read from client, sometimes the odometry values
given are of original pose. This is like a false positive. This happens
randomly and after that the correct value comes up from no-where. It might
be because of the delay in populating the data from the client. Has anyone
faced such problems? Any solutions other than waiting for many reads in a
loop until u get the correct value?
You might be able to use the C++ python bindings; the
RequestConfigure() method reads the config values into C++ class
members instead of into pointers given as arguments to the function.
2). This is with laser config reading. I cannot pass the parameters required
for reading the laser configuration as some values required are double* in
the playerc function. anyone knows any workarounds for this?