Skip to content

Commit 92a1b94

Browse files
authored
Update 01 - ROS and Sensor Fusion Tutorial.md
Swapped "odom -> base_link" and "map -> odom" paragraph titles
1 parent 1bd5055 commit 92a1b94

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Diff for: 01 - ROS and Sensor Fusion Tutorial.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -369,7 +369,7 @@ So, naturally, you'd want to fuse data to cater to these two transforms!
369369

370370
**Fusing Sensors for the /map frame (map -> odom)**
371371

372-
> **For map -> odom** you need an ekf/ukf_localization_node with the node's **"world_frame" parameter set to the name of your map frame.**
372+
> **For odom -> base_link** you need an ekf/ukf_localization_node with the node's **"world_frame" parameter set to the name of your map frame.**
373373
>
374374
> It fuses:
375375
>
@@ -381,11 +381,11 @@ So, naturally, you'd want to fuse data to cater to these two transforms!
381381
382382
**Fusing Sensors for the /odom frame (odom -> base_link)**
383383

384-
> **For odom -> base_link** you need an ekf/ukf_localization_node with the node's **"world_frame" parameter set to the name of your odom frame.**
384+
> **For map -> odom** you need an ekf/ukf_localization_node with the node's **"world_frame" parameter set to the name of your odom frame.**
385385
>
386386
> It fuses:
387387
>
388-
> - All continuous sensor data and algorithm outputs that aren't global pose estimates
388+
> - All continuous sensor data and algorithm outputs that are global pose estimates
389389
> - Global pose estimates, for example...
390390
> - AMCL (or other localisation algorithms)
391391
> - Absolute global pose data, for example...

0 commit comments

Comments
 (0)