
cuPyNumeric Install
OfficialFreeEasily install and verify cuPyNumeric for Python.
Free · Opens the source repo
What cuPyNumeric Install does
cuPyNumeric Install is a skill designed to facilitate the installation and verification of the cuPyNumeric library for Python, which is essential for numerical computations leveraging GPU acceleration. This skill guides users through the necessary prerequisites, installation commands, and verification processes to ensure that cuPyNumeric is correctly set up and operational. It is particularly useful for developers and data scientists who rely on high-performance computing for their projects and need a reliable way to integrate cuPyNumeric into their workflows.
The skill emphasizes user autonomy by providing detailed instructions for installation without executing any commands on the user's behalf. This approach allows users to maintain control over their environments, ensuring that installations are performed in isolated environments to avoid conflicts with existing packages. Users are prompted to confirm their system's compatibility with cuPyNumeric, including checking for the appropriate GPU capabilities, CUDA version, and Python environment, before proceeding with the installation.
Once the installation commands are provided, the skill also includes verification steps to confirm that cuPyNumeric is functioning correctly. This includes a smoke test script that checks basic functionality and an additional GPU usage check to ensure that the library is utilizing the GPU as intended. By following the structured instructions, users can effectively set up cuPyNumeric and troubleshoot any potential issues that may arise during installation or verification.
Overall, cuPyNumeric Install is tailored for Python developers and data scientists who require efficient numerical computing capabilities and want a straightforward method to install and verify the cuPyNumeric library without the risks associated with manual installations.
When to use it
Use this skill when you need to install cuPyNumeric for Python, especially in environments where GPU acceleration is required.
When not to use it
This skill is not suitable for users looking to build cuPyNumeric from source or for those who do not have the required system specifications.
What you can build with it
Setting up a new Python environment
When starting a new project that requires cuPyNumeric, use this skill to ensure a clean and correct installation.
Verifying GPU functionality
After installation, run the verification steps to confirm that cuPyNumeric is utilizing the GPU as expected.
Transitioning from CPU to GPU workflows
If you're moving from CPU-based computations to GPU-accelerated tasks, this skill helps set up cuPyNumeric efficiently.
How to install cuPyNumeric Install
View source1. Install with the skills CLI
npx skills add nvidia/skills/cupynumeric-install --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by nvidiacuPyNumeric Install (user)
Purpose
Use this skill to install cuPyNumeric for use from Python and to verify the install actually works (including GPU usage). Apply it whenever a user wants cuPyNumeric running via conda or pip. Do not use it to build from source (to modify or contribute) — that is out of scope.
Mandatory rules
- Never run installs. Do not run
pip install,conda install, or any installer. Print the command; let the user run it. - Always isolate. No installs into base conda, system Python, or shared global envs.
- Detect before recommending. Read-only
--versionchecks are fine.
Prerequisites
Confirm these system requirements before recommending any install:
- GPU: Compute Capability ≥ 7.0 (Volta+). CPU-only also supported.
- CUDA: 12.2+.
- OS: Linux (x86_64 / aarch64), Windows via WSL.
- Python: 3.11 through 3.14
- conda: ≥ 24.1 (conda path only).
- Package manager: conda (upstream-recommended) or pip. If neither is present, bootstrap one first (see Instructions).
Instructions
Follow these steps in order: confirm the prerequisites, ask the scoping questions, install via the chosen path, then verify.
Ask before installing
- Package manager? Check
conda --versionandpip --version. Prefer conda (upstream-recommended); fall back to pip. - Env target? GPU machine, CPU-only laptop, cloud, container, or remote/server.
- CUDA version? Ask only when forcing the GPU variant on a host without a visible GPU. Check with
nvidia-smi/nvcc --version.
Bootstrap — install a package manager first
If neither conda nor pip is available, install one. Provide the command and the docs link; do not run it.
Recommended: Miniforge (full conda, conda-forge default)
curl -L -O "https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-$(uname)-$(uname -m).sh"
bash "Miniforge3-$(uname)-$(uname -m).sh"
Docs: https://github.com/conda-forge/miniforge
Alternative: Python + pip
Install Python from your OS package manager (apt/dnf/brew) or https://www.python.org/downloads/. If pip is missing on an existing Python: python -m ensurepip --upgrade.
After installing, open a new shell so the binary is on PATH.
Install — conda path
conda create -n cupynumeric -c conda-forge -c legate cupynumeric
conda activate cupynumeric
Into an existing env: conda install -c conda-forge -c legate cupynumeric.
conda auto-selects the GPU vs CPU variant from whether nvidia-smi works at install time. To override that, see below.
Force the GPU variant
Set CONDA_OVERRIDE_CUDA only when no GPU is visible at install time (e.g. building a container for a GPU host). Use the runtime host's CUDA version:
CONDA_OVERRIDE_CUDA="12.2" conda install -c conda-forge -c legate cupynumeric
Nightly (less validated)
conda install -c conda-forge -c legate-nightly cupynumeric
Install — pip path
python -m venv .venv
source .venv/bin/activate
pip install nvidia-cupynumeric
Verify
Smoke test (always run)
Run a self-contained script through the legate launcher — no repo checkout needed.
TMP=$(mktemp -d)
cat > "$TMP/smoke.py" <<'EOF'
import cupynumeric as np
a = np.arange(10)
b = np.ones((4, 4))
print("sum:", a.sum()) # expect 45
print("matmul:", (b @ b).sum()) # expect 64.0
EOF
legate "$TMP/smoke.py"
rm -rf "$TMP"
Expect sum: 45 and matmul: 64.0. If legate is missing, the env is not activated — see Troubleshooting.
GPU usage check (mandatory when a supported GPU is present)
A passing smoke test does not prove GPU usage — a CPU-variant install on a GPU box produces correct results too. Run both steps.
1. Force a GPU launch. legate --gpus N requests N GPUs; fails fast if no GPU is visible or the CPU variant is installed.
TMP=$(mktemp -d)
cat > "$TMP/check.py" <<'EOF'
import cupynumeric as np
print(np.ones((4096, 4096)).sum())
EOF
legate --gpus 1 "$TMP/check.py"
rm -rf "$TMP"
Expect 16777216.0. If you see CUDA driver, libcudart, or no GPUs available, the CPU variant is installed; reinstall with CONDA_OVERRIDE_CUDA.
2. Confirm the GPU was touched. Run a deadline-bounded matmul loop alongside nvidia-smi, all from one shell — no second-terminal race:
TMPDIR_GPU=$(mktemp -d)
SCRIPT="$TMPDIR_GPU/cupynumeric_gpu_check.py"
cat > "$SCRIPT" <<'EOF'
import cupynumeric as np, time
a = np.ones((10000, 10000))
deadline = time.time() + 20
iters = 0
while time.time() < deadline:
b = a @ a
_ = float(b.sum()) # force sync so the matmul actually runs
iters += 1
print("iters:", iters)
EOF
legate --gpus 1 "$SCRIPT" &
WORKLOAD=$!
sleep 5 # buffer for Legate startup
for _ in $(seq 10); do # 10 samples at 1s — covers slow startup
nvidia-smi --query-gpu=utilization.gpu,memory.used --format=csv,noheader
sleep 1
done
wait "$WORKLOAD"
rm -rf "$TMPDIR_GPU"
Expect memory.used in the GiB range across most samples and non-trivial
utilization.gpu in several. If both stay at baseline across every sample, the
GPU variant is not installed — check conda list cupynumeric for *_gpu (not
*_cpu).
Deeper recipes
See verification_examples.md for multi-GPU checks, CPU fallback, container, and troubleshooting.
Limitations
- Don't mix conda and pip in one env. Mixing overrides the first install and breaks at import. To switch, run
pip uninstall nvidia-cupynumericorconda remove cupynumericfirst. - Use the
legatelauncher for multi-GPU / multi-rank runs. Plainpythonruns single-process:legate --gpus 2 script.py. - Force the GPU variant on a CPU-only host with
CONDA_OVERRIDE_CUDA. conda otherwise auto-selects the CPU or GPU variant fromnvidia-smiat install time. - Require Volta or newer. Pascal (GTX 10xx / P100) is unsupported.
- Verify
conda --version≥ 24.1. Older releases silently break variant selection. - Treat multi-node / MPI / UCX as out of scope. Defer to https://docs.nvidia.com/legate/latest/networking-wheels.html and https://docs.nvidia.com/legate/latest/mpi-wrapper.html.
Troubleshooting
ModuleNotFoundError: No module named 'cupynumeric'→ Runwhich pythonandpip list | grep cupynumeric(orconda list | grep cupynumeric) from the same shell to find the env mismatch.ImportErrormentioning CUDA /libcudart→ Reinstall withCONDA_OVERRIDE_CUDA="<your-cuda-version>"; the CPU variant is on a GPU box, or CUDA versions are mismatched.legate: command not found→ Activate the env, then runwhich legateto confirm.- Slower than NumPy on a laptop → Expect this for small problems (Legate per-task overhead). See the cuPyNumeric FAQ.
See also
- references/verification_examples.md — verification + troubleshooting recipes.
- Upstream docs: https://docs.nvidia.com/cupynumeric/latest/installation.html
- Legate requirements: https://docs.nvidia.com/legate/latest/installation.html
Frequently asked questions about cuPyNumeric Install
Similar skills
Spring Boot Testing
Master testing techniques for Spring Boot 4 applications.
GitHub Issues
Manage GitHub issues efficiently with MCP tools.
Geofeed Tuner
Optimize your IP geolocation feeds in CSV format.
Batch Files
Master Windows batch scripting for automation and task management.
Adobe Illustrator Scripting
Automate your Illustrator workflows with ExtendScript.
Plugin Structure
Create and organize Claude Code plugins effectively.
