-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Task1]: TF frame tree disconnection in non-ground-truth mode #78
Comments
In hector theory, the "world" means the point where longtitude = 0 and latitude = 0, while the "nav" is the point calculated only by GPS. So in our challenge, the center point of arena does not coincide with the "world" frame. We have to calculate the offset between the GPS value and relative position of arena(x:-65m, y:20m) in terms of the start point. |
you can define "center_of_the_world"(longitude = 0 and latitude = 0) and ◉ Kei Okada On Thu, Jun 2, 2016 at 7:28 PM, 趙 漠居 [email protected] wrote:
|
or consider center of the world is the center of the arena ◉ Kei Okada On Thu, Jun 2, 2016 at 7:36 PM, Kei Okada [email protected]
|
I found that if I use the following non-ground-truth-mode in task1, there is a disconnection in tf frame tree(frames_non_ground_truth.pdf).
roslaunch jsk_mbzirc_tasks jsk_mbzirc_task_1.launch use_ground_truth:=false
frames_non_ground_truth.pdf.
And the "/nav" is fixed at "/world", which "/nav" is the start point of the uav(x:-65m, y: 20m), and "/world" is the the center point of arena.
In comparison, under ground-truth-mode, all frames are connected(frames_ground_truth.pdf)
frames_ground_truth.pdf
I will send a PR to fix the tf problem.
The text was updated successfully, but these errors were encountered: