No GPU? No problem. Without CUDA, warp-md gracefully falls back to CPU. Your agent’s code runs everywhere.
Requirements
- NVIDIA GPU with CUDA support
- CUDA Toolkit (driver + nvrtc)
CUDA_HOMEorCUDA_PATHenvironment variable set
Setup
Device Selection
All analysis plans accept adevice parameter:
What Gets Accelerated?
| Category | GPU-Accelerated Analyses |
|---|---|
| Core | Rg, RMSD, MSD, RDF |
| Polymer | End-to-end, contour length, chain Rg, bond histograms |
| Orientation | RotAcf (orientation extraction) |
| Transport | Conductivity (group COM), Dielectric, Dipole alignment |
| Structure | Ion-pair correlation, Structure factor (RDF kernel) |
| Spatial | Water occupancy grid |
| Thermodynamic | Equipartition (group kinetic energy) |
| Bonding | H-bond counts (distance + angle) |
Performance Tips
Troubleshooting
CUDA not detected
CUDA not detected
Set The
CUDA_HOME or CUDA_PATH to your CUDA installation:cudarc crate needs this breadcrumb to find the runtime.GPU out of memory
GPU out of memory
Reduce Sometimes discretion is the better part of valor.
chunk_frames or switch to CPU:Kernel compilation fails
Kernel compilation fails
Ensure
nvrtc is available. This ships with the CUDA Toolkit.Benchmarks
Typical speedups on modern GPUs (RTX 3080): | Analysis | CPU Time | GPU Time | Speedup | |----------|----------|----------|---------|| | Rg (10k frames) | 2.5s | 0.3s | ~8x | | RDF (10k frames) | 45s | 3s | ~15x | | MSD (100k frames) | 120s | 8s | ~15x |Actual speedup depends on system size, trajectory length, and hardware. Your mileage may vary - but it’s usually impressive.
Feature Flags in Cargo.toml
CUDA support is enabled via thecuda feature flag in crates/traj-gpu/Cargo.toml:
cudarcis an optional dependency- Feature flag:
--features cuda - CUDA 12.0.40+ supported
See Also
- Basic Analysis Workflows - Common analysis patterns
- CLI Usage - Command-line device selection
- Analysis Plans Reference - Full API documentation