Adding more explicit instructions on how to launch WaypointFlyer and WaypointFlyerSimple examples #3
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
Added some simple instructions to the Waypoint_flyer_simple to make it easier to understand how to launch the service.
Added some simple instructions to the Waypoint_flyer to make it easier to understand how to launch the service.
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.
This pull request adds some extra steps for helping others run the WaypointFlyer and WaypointFlyerSimple examples.
Since we were asked to get to know a bit the MRS System before the 2024 summer school, and the examples are referenced in the repository, I tried running them but did not know that there were extra steps aside from running the prepared
start.shscripts for the examples.By adding these extra steps, on the questions/problems I had about getting the examples to run, I hope to make it easier for others to run and start tinkering with the examples by their own without having to spend time wondering why the drone does not move around in Rviz.