Testing robot_localization

[ros_wild_thumper.git] / launch / robot_localization.launch

diff --git a/launch/robot_localization.launch b/launch/robot_localization.launch
index a6e408dfaf8144cd14b4346c218b81fa805457f9..d3da3176d126d101ecd6ba882f80d79413ce5d0a 100644 (file)
--- a/launch/robot_localization.launch
+++ b/launch/robot_localization.launch
@@ -67,7 +67,6 @@
                   parameters obviously have no default values, and must be specified. -->
                <param name="odom0" value="odom"/>
                <param name="imu0" value="imu"/>
-               <param name="odom1" value="gps"/>
 
                <!-- Each sensor reading updates some or all of the filter's state. These options give you greater control over
                   which values from each measurement are fed to the filter. For example, if you have an odometry message as input,
@@ -76,10 +75,10 @@
                   message types lack certain variables. For example, a TwistWithCovarianceStamped message has no pose information, so
                   the first six values would be meaningless in that case. Each vector defaults to all false if unspecified, effectively
                   making this parameter required for each sensor. -->
-               <rosparam param="odom0_config">[true, true, false, false, false, true, true, true, false, false, false, true, true, true, false]</rosparam>
-               <rosparam param="imu0_config">[false, false, false, true, true, true, false, false, false, true, true, true, true, true, true]</rosparam>
-               <rosparam param="odom1_config">[true, true, true, false, false, false, false, false, false, false, false, false, false, false, false]</rosparam>
-
+               <!-- x/y not included because of redundancy with velocities -->
+               <!-- vyaw not included in odom because too inaccurate -->
+               <rosparam param="odom0_config">[false, false, false, false, false, false, true, true, false, false, false, false, false, false, false]</rosparam>
+               <rosparam param="imu0_config">[false, false, false, false, false, true, false, false, false, false, false, true, false, false, false]</rosparam>
 
                <!-- The best practice for including new sensors in robot_localization's state estimation nodes is to pass in velocity
                   measurements and let the nodes integrate them. However, this isn't always feasible, and so the state estimation
@@ -97,9 +96,8 @@
                   integration of velocities leads to slowly increasing error in the absolute (pose) variable. For position variables,
                   this is acceptable. For orientation variables, it can lead to trouble. Users should make sure that all orientation
                   variables have at least one source of absolute measurement. -->
-               <param name="odom0_differential" value="true"/>
+               <param name="odom0_differential" value="false"/>
                <param name="imu0_differential" value="false"/>
-               <param name="odom1_differential" value="false"/>
 
                <!-- When the node starts, if this parameter is true, then the first measurement is treated as a "zero point" for all
                   future measurements. While you can achieve the same effect with the differential paremeter, the key difference is
@@ -107,7 +105,6 @@
                   you simply want your measurements to start at 0 for a given sensor, set this to true. -->
                <param name="odom0_relative" value="false"/>
                <param name="imu0_relative" value="false"/>
-               <param name="odom1_relative" value="true"/>
 
                <!-- If we're including accelerations in our state estimate, then we'll probably want to remove any acceleration that
                   is due to gravity for each IMU. If you don't want to, then set this to false. Defaults to false if unspecified. -->
@@ -118,7 +115,5 @@
                <param name="print_diagnostics" value="true"/>
 
                <remap from="odometry/filtered" to="odom_combined"/>
-
        </node>
-
 </launch>