gz: publish sensor_gps #24416
Closed
gz: publish sensor_gps #24416
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rather than setting it to 0 you should just not set it (off by default). |
dakejahl
force-pushed
the
pr-gz_sim_improvements
branch
from
a7c3901 to
fc91044
Compare
… update step and run() loop does not share resources.
dakejahl
force-pushed
the
pr-gz_sim_improvements
branch
from
52df4b9 to
492a3ef
Compare
|
replaced by #24421 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Disable
sensor_gps_simmodule in gz airframes (SENS_EN_GPSSIM 0)Publish
sensor_gpsdirectly from GZBridge. Implemented first order markov process for GPS noise model.Update gz models submodule to include updated IMU and Baro noise parameters
Fix IMU + baro noise model PX4-gazebo-models#81
Removed mutex in gz topic callbacks. Callbacks run synchronously from gz and there are no shared resources with Run().
Removed
hrt_absolute_time() == 0check in topic callbacks. Not sure why it was there. If we need to validate that PX4-SITL has started before callbacks run we should do that before subscribing.