This provides the quickest fix to issue #680 by extracting a normalized world name from any incoming path, and adding a few likely names to our list of worlds that we recognize and create bridges for. It doesn't fix the deeper conceptual problems described in #680.
and verify that you see the correct list of topics. Next, rename one of our task worlds to one of the generic names we use in our testing, and check the topics again to verify that it still works:
This provides the quickest fix to issue #680 by extracting a normalized world name from any incoming path, and adding a few likely names to our list of worlds that we recognize and create bridges for. It doesn't fix the deeper conceptual problems described in #680.
To test:
Run a task using an absolute path:
in another terminal run
and verify that you see the correct list of topics. Next, rename one of our task worlds to one of the generic names we use in our testing, and check the topics again to verify that it still works:
Bonus: Gazebo will no longer crash if the user accidentally includes the world file extension.