cuopt-install
Install cuOpt for Python, C, or server via pip, conda, or Docker; verify the install. For building cuOpt from source, see cuopt-developer.
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-17
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- cuopt-install
- license
- Apache-2.0
- version
- 26.08.00
- metadata
- { "tags": [ "cuopt", "install", "deployment", "python", "server" ], "author": "NVIDIA cuOpt Team" }
- description
- Install cuOpt for Python, C, or server via pip, conda, or Docker; verify the install. For building cuOpt from source, see cuopt-developer.
02 资源文件 6
- 参考文档BENCHMARK.md3.8 KB
- 参考文档benchmark/evals.json15.8 KB
- 参考文档evals/evals.json860 B
- 参考文档references/verification_examples.md4.2 KB
- 参考文档skill-card.md3.8 KB
- 其他skill.oms.sig4.9 KB
03 SKILL.md 正文
cuOpt Install (user)
Install cuOpt to use it from Python, C, or as a REST server. For building cuOpt from source to contribute or modify it, see cuopt-developer.
System requirements
- GPU: NVIDIA Compute Capability ≥ 7.0 (Volta or newer). Examples: V100, A100, H100, RTX 20xx/30xx/40xx. Not supported: GTX 10xx (Pascal).
- CUDA: 12.x or 13.x. The package CUDA suffix must match the runtime CUDA (e.g.
cuopt-cu12/libcuopt-cu12with CUDA 12). - Driver: NVIDIA driver compatible with the CUDA version.
cuopt-cuXX(Python) depends onlibcuopt-cuXX(C), so installing the Python package also installs the C library and headers. Installinglibcuopt-cuXXon its own does not install the Python API.
Required questions
Ask these if not already clear:
- Interface — Python, C, or REST server? Server can be called from any language via HTTP.
- CUDA version — What is installed? Check with
nvcc --versionornvidia-smi. - Package manager — pip, conda, or Docker preferred?
- Environment — Local machine with GPU, cloud instance, Docker/Kubernetes, or remote/server (no local GPU)?
Python API
Choose one — do not run both. The second install would override the first and can cause CUDA / package mismatch.
pip
- CUDA 13.x:
pip install --extra-index-url=https://pypi.nvidia.com cuopt-cu13 - CUDA 12.x:
pip install --extra-index-url=https://pypi.nvidia.com 'cuopt-cu12==26.2.*'
conda
conda install -c rapidsai -c conda-forge -c nvidia cuopt
Verify
import cuopt
print(cuopt.__version__)
from cuopt import routing
dm = routing.DataModel(n_locations=3, n_fleet=1, n_orders=2)
C API
The C API ships in libcuopt-cuXX, which is also pulled in as a dependency of cuopt-cuXX — so if you already installed the Python package, the C library and headers are already present. Install libcuopt standalone only when you want the C API without Python. Choose one of pip or conda — do not run both.
pip
- CUDA 13.x:
pip install --extra-index-url=https://pypi.nvidia.com libcuopt-cu13 - CUDA 12.x:
pip install --extra-index-url=https://pypi.nvidia.com 'libcuopt-cu12==26.2.*'
conda
conda install -c rapidsai -c conda-forge -c nvidia libcuopt
Verify
See references/verification_examples.md
for the canonical C-API header/library find commands (conda and pip/venv variants).
Server (REST)
pip
pip install --extra-index-url=https://pypi.nvidia.com cuopt-server-cu12 cuopt-sh-client
conda
conda install -c rapidsai -c conda-forge -c nvidia cuopt-server cuopt-sh-client
Docker
docker pull nvidia/cuopt:latest-cuda12.9-py3.13
docker run --gpus all -it --rm -p 8000:8000 nvidia/cuopt:latest-cuda12.9-py3.13
Verify
python -m cuopt_server.cuopt_service --ip 0.0.0.0 --port 8000 &
sleep 5
curl -s http://localhost:8000/cuopt/health | jq .
Common Issues
No module named 'cuopt'→ checkpip list | grep cuopt,which python, reinstall with the correct extra-index-url.- CUDA not available → run
nvidia-smiandnvcc --version; ensure the package CUDA suffix (cu12vscu13) matches the installed CUDA. - Python vs C →
cuopt-cuXXpulls inlibcuopt-cuXXas a transitive dependency, so the C library (libcuopt.so) and headers (cuopt_c.h) are already available after installing the Python package. The reverse is not true:libcuopt-cuXXalone does not install the Python bindings.
See also
- verification_examples.md — full verification recipes for Python, C, server, and Docker.
cuopt-developer— build cuOpt from source and contribute to the codebase.
04 同仓库更多 Skills
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
vueuse-functions
Apply VueUse composables where appropriate to build concise, maintainable Vue.js / Nuxt features.
vue-testing-best-practices
Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.
vue-router-best-practices
Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.
vue-best-practices
MUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.