...
| Info |
|---|
Note that you want to install miniconda in a network lab directory as it will quickly fill up your home directory! |
Step-by-step guide
- Connect to head.arcc.albany.edu via SSH (see: How-to: Connect via SSH (PuTTY, macOS terminal, X2Go)
Run the following commands, line by line. Make sure you change [lab_directory] to be your lab directory name.
Code Block language bash title Installing miniconda cat ~/.bashrc >> ~/.bash_profile wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O ~/miniconda.sh bash ~/miniconda.sh -b -p /network/rit/lab/[lab_directory]/miniconda /network/rit/lab/[lab_directory]/miniconda/bin/conda init cat ~/.bashrc >> ~/.bash_profile source ~/.bash_profile
- Some helpful hints
- Do not install packages in your (base) environment (e.g. conda activate base). It is best to create separate environments for different packages, or conda is at a risk of breaking (e.g.
conda create -n tensorflow python=3) - Sharing conda across lab group members is possible, make sure the folder is g+rwx (
chmod -R g+rwx /network/rit/lab/[lab_directory]/miniconda) - Always check if conda has a software package available. There are many different channels, but researchers and software developers commonly publish to conda-forge (e.g.
conda install -c conda-forge ffmpeg) - Read the docs: https://conda.io/projects/conda/en/latest/user-guide/index.html
- Do not install packages in your (base) environment (e.g. conda activate base). It is best to create separate environments for different packages, or conda is at a risk of breaking (e.g.
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...