Guaranteed to score a 0 or your money back
So now we should score a 2, a second score attempt will 99.9% fail like in a test it was (x was off by 2m, y was off by 22m), this is how bad our real odom is
Score uses an offset for odom and created class member variable to store it for future use.
If we fail on the first attempt, we are toast, please paste the output of ./src/scripts/src/closestVolPose.py and either the output from the roslaunch ./launch/whatever or ~/.ros/log/latest/scout_1-Task-*.log
A failed output would look like this:
Guaranteed to score a 0 or your money backSo now we should score a 2, a second score attempt will 99.9% fail like in a test it was (x was off by 2m, y was off by 22m), this is how bad our real odom isScore uses an offset for odom and created class member variable to store it for future use.
If we fail on the first attempt, we are toast, please paste the output of
./src/scripts/src/closestVolPose.py
and either the output from theroslaunch ./launch/whatever
or~/.ros/log/latest/scout_1-Task-*.log
A failed output would look like this:output from
./src/scripts/src/closestVolPose.py
Rover pose and true_pose_got match We want
trying vol_loc
to be as close as possible toClosest Volatile pose