Research Computing Keywords
RC is Research Computing
RC Domains
The following are domains that belong to us. As a a general rule, anything that ends with rc.uab.edu
is ours. We plan to put all of our services in that domain.
- rc.uab.edu (Cheaha for now, will eventually become a portal to the others)
- cheaha.rc.uab.edu (Cheaha)
- cloud.rc.uab.edu (Cloud.rc)
- dashboard.cloud.rc.uab.edu (Cloud.rc)
- docs.rc.uab.edu (Documentation)
- exosphere.rc.uab.edu (Cloud.rc)
- gitlab.rc.uab.edu (GitLab)
- k8s.rc.uab.edu (Kubernetes.rc)
- s3.lts.rc.uab.edu (S3 Object Store via Ceph)
- lmgr.rc.uab.edu (Software license manager, MATLAB)
- xnat.rc.uab.edu (Neuro image repository)
- ldap.rc.uab.edu (Identity management)
- docs.uabgrid.uab.edu (Deprecated documentation, do not use, no support)
Very likely related to RC
- Research Computing (RC)
- High Performance Computing (HPC)
- High Throughput Computing (HTC)
- ScienceDMZ
- Data Transfer Node (DTN)
- Cheaha
- Cluster
- Cloud.rc
- Exosphere
- Jetstream
- OpenStack
- Horizon
- GitLab
- Globus
- Long-term Storage (LTS)
- XNAT
- GitLFS
- GPFS
- Ceph
- /data/user
- /data/project
- Project Directory/Folder/Space/Storage
- Scratch Directory/Folder/Space/Storage
- Network Scratch ...
- Local Scratch ...
- Open OnDemand (OOD)
- Workflow Engine/Manager
- Singularity [Container]
- Slurm [Command/Queue/Job/Task/Scheduler/Flag]
- sbatch
- srun
- squeue
- sacct
- seff
- scancel
- Array Job/Task
- HPC
- pascalnodes
- amperenodes
- largemem
- Interactive Apps
- My Interactive Sessions
- Job Composer
- Batch Job/Task
- JobID
- TRES
- GRES
- P100 [GPU]
- A100 [GPU]
- Open Science Grid (OSG)
Possibly related to RC
- Anaconda [Environment]
- Miniconda [Environment]
- Mambaforge
- conda
- mamba
- Jupyter [Notebook/Hub/Server]
- Docker [Container/Hub]
- Scheduler
- Queue
- Job/Task [Session]
- Job Script
- RStudio [Server/Package]
- PyTorch
- TensorFlow
- Keras
- GPU [Job]
- Module
- Quota
- Data Transfer
- Partition/Node/Core/CPU/GPU/Memory/Job
- MATLAB [License]
- Submit Job
- Virtual Machine (VM)
- Instance
- Volume
- Keypair
- Security Policy
- Snapshot
- Image
- Parabricks
- CUDA [toolkit]
- nvidia-smi
- Cloud
- UAB contracts with Microsoft Azure. I believe Scott Carson's group is involved with this.
- Kubernetes
- UAB IT Infrastructure plans to build, or built, a Kubernetes system.
- S3
- Used with LTS, but also an interface to commercial cloud storage.
Additional related keywords from tickets and RC docs
- ACLs
- Allocation
- Array Job
- Binary/Executable
- Bucket/object
- Bucket policy
- CI/CD
- Commercial software (Amber, Ansys, Gurobi, LS-Dyna, Mathematica, SAS, Stata)
- Command Line Interface (CLI)
- Community Container
- Compute node/
- Core/CPU
- Docker Image
- Duo 2FA
- FLOPS
- Globus CLI
- Globus Connect personal/Globus Connect Server
- Globus group
- Host
- IAM
- Ipykernel/kernel
- Job submission script
- Login node
- Message Passing Interface(MPI)
- Miniforge
- module
- module load
- module reset
- noVNC
- Package
- Quality of service
- Remote Tunnels
- rclone
- Scratch Retention Policy
- Single Sign-On (SSO)
- Secure SHell(SSH)
- Scheduler
- sbatch
- Snapshots
- Shared collection/globus collection
- Slurm Flags
- srun
- s3cmd/s5cmd
- UAB Box
- Virtual Machine (VM)
- VSCode
- XIAS ID/XIAS email
Some known common issues
Some examples of common issues that are related to us can be found here (this is basically our FAQ): https://ask.cyberinfrastructure.org/c/locales-data-centers-and-campus-rc/uab/52