Workspace Extension Functionality #36
Merged
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.
By default, Zethus uses the
ROS_PACKAGE_PATH
set before Jupyter Hub launches.To use a new ROS workspace inside of Jupyter Lab, the existing procedure is,
This workflow is doable in a local instance. The problem arises with the Jupyter Hub instance launched from a Dockerfile.
In the Jupyter Hub instance with the current Jupyterlab-ros server plugin, it's impossible to add the new workspaces and fetch new robot models making it cumbersome to visualise robot models.
The updated plugin tries to solve this problem by enabling the user to add and delete workspaces as required for the task without restarting the Jupyter lab, copying the packages to the base path, modifying the Dockerfile and restarting Jupyter Hub instance.
To test the plugin