...
The notebooks are configured so that any new conda environment you create (see Installing Library Packages in Anaconda) will automatically create can be configured to show a corresponding kernel launcher on your Jupyter homepage. For this reason, we recommend that users primarily install packages via Anaconda, rather than pip or CRAN, where possible.
...
- Open a Terminal window from the homepage.
- Create a new conda environment to install your package in,
conda create --name myshinynewenv nb_conda_kernels - Activate your new environment,
conda activate myshinynewenv - Install your package, e.g.
conda install -c conda-forge recordlinkage - You can also install from pip in the traditional way, ensuring you activate the environment (step 3) that you want to install the package into first.
- When you close the Terminal window and return to the homepage you should see a new python kernel with the same name as your new conda environment.
...
- Open a Terminal window from the homepage.
- If you want to use your new package within R Studio then just install it into the base environment.
- If you want to use it within Jupyter R then create a new env as in steps 2 and 3 in the Python section above.
- Install your package, e.g.
conda install-c rr-terra - You can also install from CRAN in the traditional R way.
If you prefer a GUI...
- On the top menu bar, go to Settings → Conda Package Manager
- This may take several minutes to load, but when it does you'll see your current environments and all of the packages installed in them.
- You can create new environments and install packages via this visual UI.
Using GIT
The notebooks are set up to be able to pull and push to the SAIL Gitlab. You can set this up how you set it up on your SAIL Desktop (see How to use GITLAB within SeRP, and instructions on the internal SAIL wiki).
...