The seeded estimator will break and not allow any new launches of the node if Gazebo Classic breaks and somehow reports 0 as the lat/long/alt/pressure (only one of these) it throws an invalid type error where the string is cast to an int instead of a double. I think this is low priority, because either a fresh build or reverting the parameter changes will fix it, and because we will be decoupling the sensors from the sim relativity soon. That being said a type error like this should not be possible.
--EDIT-- This is actually a pretty big issue, it happens every time Gazebo implodes while rosplane is running
Okay so it is actually only during a specific gazebo crash, just the most common one. An easy way to avoid this is to launch rosplane only when Gazebo has been confirmed to have successfully launched.
The seeded estimator will break and not allow any new launches of the node if Gazebo Classic breaks and somehow reports
0
as the lat/long/alt/pressure (only one of these) it throws an invalid type error where the string is cast to anint
instead of adouble
. I think this is low priority, because either a fresh build or reverting the parameter changes will fix it, and because we will be decoupling the sensors from the sim relativity soon. That being said a type error like this should not be possible.--EDIT-- This is actually a pretty big issue, it happens every time Gazebo implodes while rosplane is running