cleanup all globally hardcoded remaps for multirobots#1214
cleanup all globally hardcoded remaps for multirobots#1214SteveMacenski merged 24 commits intoros-navigation:masterfrom
Conversation
|
Also @orduno I see you have a multirobot system test PR, you're more than welcome to pull my commit into that branch and I can close this PR. It was just a quick cleanup job |
Codecov Report
@@ Coverage Diff @@
## master #1214 +/- ##
========================================
- Coverage 39% 38.2% -0.8%
========================================
Files 244 244
Lines 11033 11033
Branches 4565 4565
========================================
- Hits 4303 4215 -88
- Misses 3874 3990 +116
+ Partials 2856 2828 -28
Continue to review full report at Codecov.
|
|
Seems to me best action is to have the |
|
@crdelsey @orduno can I get reviews? |
Are you planning on adding this to this PR? |
|
I can. What namespace(s) would you like? |
|
|
|
What I'm asking is what is that |
|
we'll need one per robot, so |
|
I think you mean |
|
@orduno done. This also has the added benefit of allowing a user to launch multiple heterogenerous (ei completely different robots) if they require unique configuration files. I usually hate Edit: Forgot to update the multirobot tests to do this -- one moment |
e64703a to
3c57c07
Compare
|
This PR should be squash merged, battling small python flake issues that only appear in CI. I'll force push a squashed last commit from this garbage but in general this is a small change and shouldn't need more than 1 |
4ca636e to
26ac5be
Compare
|
@orduno this is ready again for review. I'm not seeing anything subscribed/published to the global So this is probably going to have to sit here until the spawn_robot CI bug is fixed or I can get the stack running on my computer again. That's fine |
|
Travis also fails on the Edit: Thanks to @crdelsey that's all handled now, passing tests 👍 |
c835b4c to
83155d0
Compare
|
Can I get a couple reviews? I'm passing the multi-robot CI & I'd love it if I didn't have to fix another 5 merge conflicts on this one PR 😿 |
| source_file=rviz_config_file, | ||
| replacements={'<robot_namespace>': ('/' + robot['name'])}) | ||
|
|
||
| params_file = eval(robot['name'] + '_params_file') |
There was a problem hiding this comment.
Can we change this to:
params_file = LaunchConfiguration(robot['name'] + '_params_file')
Then we can get rid of the LaunchConfiguration lines above.
Maybe it's just me, but I find the use of eval here difficult to read.
There was a problem hiding this comment.
So on first glance I agree with you, but something that came to mind was that since we're doing this eval in a loop, that if someone changes 2 robots to N robots and there aren't N parameter files, you're not going to be able to statically look at the initialization of the launch configurations and see that there are things missing.
If you don't think that's a real problem, I can do that -- I'm just thinking and if there's a bug, some analyzer isn't going to catch that.
|
Build breaking from branching issue, given it was passing and this is a 1 line change, I'm inclined to push this |
…#1214) * cleanup all globally hardcoded remaps for multirobots * fixing map path * fix pep8 indent * linter happy now? * Fix linter errors * reincluding /scan on scan * multirobot launch with unique configurations * multirobot tests using both configuration files * make flake8 happy * flake8 try2 * flakey9 * flake10 * attempt flake exception * flake11 * flake12 * noqa on lin * changing launch configuration in loop
Fixes #746
This PR cleans up all the hardcoded global scope topics across the stack so were not unnecessarily remapping basic topics.
Passes tests but I think @orduno is in the best position to give this the thumbs up that it resolves all the issues he needed the remaps for.
Now the remaps are just for things genuinely needed (TF) where there isn't (yet) an option for a prefix