Five ways to get software
- System modules (recommended). Check first:
module avail software-name, thenmodule load software-name/version. - Conda environments. Ideal for Python packages, data-science tools, or packages with complex dependencies (numpy, pandas, TensorFlow, PyTorch) — see conda environments.
- Python venv. Best for lightweight Python projects without compiled dependencies.
- Install from source. For software not available through modules or package managers, or when you need custom compilation options — see installing from source.
- Request a system-wide install. Submit at iacs.supportsystem.com for multi-user needs.
Where to install
| Location | Quota | Backed up | Persistent | Best for |
|---|---|---|---|---|
Home /gpfs/home/ | 20 GB | Yes | Yes | Personal tools, small apps |
Project /gpfs/projects/ | Large | No | Yes | Shared tools, group use |
Scratch /gpfs/scratch/ | 20 TB | No | No — 45-day purge | Temp files ONLY |
Critical: Do NOT install software in scratch space — files are automatically deleted after 45 days, breaking your installation even while in use.
Best practices
- Organize by purpose in directories like
$HOME/software/and include version numbers in directory names - Monitor quota with
myquota; clean the conda cache withconda clean --all - Document installations and dependencies
- Set group permissions with
chmodfor shared software
Applies to