-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ros2 Humble - Translated flatland viz tools to rviz plugins #92
Ros2 Humble - Translated flatland viz tools to rviz plugins #92
Conversation
Fix usage of get_parameter in YamlPreprocessor. Change integer in yaml out-file to floating point number (result of a calculation in lua).
This fixes a problem where rviz doesn't start on time to catch the publish of the layer markers.
When pressed, it toggles the paused state of the simulation.
The message that will be used by the change rate service to change the simulation speed in run time.
Simulation manager needs a setter for the simulation rate, so the ChangeRate service can alter it in runtime.
Cleans the memory reserved for the ros WallRate object
It is exported to use in rviz
Used by the change rate tool, so the user can choose the desired rate
Added a service and rviz tool to change the simulation update rate in runtime. |
This is a really neat feature. Probably a bit dangerous but no more than changing the update rate normally is. I can see a typo in calling the service causing really funny errors! I look forward to trying it out. |
Would it also make sense to control the simulation timestep in the same way (either as the same service call, or a similar one)? The two variables somewhat work together, since the real-time factor is timestep*update rate. |
For any new cpp/hpp files, can you add the BSD 3 clause license: License Template
We do not have a contributor license agreement (CLA) requiring that you transfer copyright to Avidbots to merge, but we do need each file to contain an appropriate license. In this case Flatland uses BSD-3 clause (like most ROS packages), so that would be preferred. For modified files, the existing license headers is fine. Any contributions merged under those existing licenses are assumed (and possibly required) to be under the existing header license. (It would be impractical to license portions of code in the same file under different licenses). Copyright could be done line by line, but I don't think anyone wants that much beurocratic overhead. I'm trying to figure out why I'm getting a large number of lint errors (including missing copyright headers) on my local build and not on the github action for this branch (well, actually I'm getting different errors on githubactions). Locally I'm running: Todo items:
|
Ye that makes sense. It could probably be part of the same menu/rviz plugin. |
We've finished correcting the errors that the code had, however there were some that left us not knowing how to proceed:
|
@TheZambi I have created a copy of your branch and fixed the various errors a few different ways:
I also tweaked the header paths and includes for flatland_rviz_plugins since they were a bit inconsistant (some headers in the src folder, others in include, some with source relative paths, others include relative). I think they're consistant now. Local testing, building and CI all seem to work but I haven't tested running flatland yet. Can you merge my branch into yours and push it so this PR updates to include both changes? https://github.com/avidbots/flatland/tree/ros2-rviz-plugins I'd like to merge my changes in the flatland_turtlebot master branch into your proposed Humble/ros2 port, along with pointing it at nav2, which if combined correctly should allow a turtlebot 1 like simulation in ros2 with nav2 and flatland. That said, I don't think I'll be able to get to that soon. If you want to try, feel free. My most recent merge into master bundles a lot of the now deprecated turtlebot1 launchfiles and dependencies so that turtlebot_flatland isn't dependant on the turtlebot repo as much. This might help with the nav2/ros2 version. |
Finished pushing the merge. Sadly, we will most likely not be able to look into the other merges that deal with the turtle_bot as the members of the group are starting to work on the master's thesis, and we will be occupied with it for the next months. Thank you for your help throughout the development and all the best. |
No problem. Thanks for the hard work. This has really helped push the ros2 version of flatland ahead. I'll see if I can get a demo repo working with ros2. Good luck with your academic persuits! |
This PR adds a new package to flatland called flatland_rviz_plugins that enables the smooth transition from flatland_viz to rviz.
The plugins added are:
Note: these are already in use in our ros2 branch in our turtlebot_flatland repo.