What problem does it solve? CPU-bound Python code for numerical computing, dataframes, machine learning, graph analytics, image processing, and simulation runs orders of magnitude slower than it could on an NVIDIA GPU, and choosing the right GPU library for each workload is difficult. ## Core Features & Use Cases - Library Decision Framework: Maps workloads to the right tool ā CuPy for NumPy arrays, cuDF for pandas, cuML for scikit-learn, cuGraph for NetworkX, cuCIM for scikit-image, cuVS for vector search, cuSpatial for GeoPandas, Warp for physics simulation, Numba for custom CUDA kernels, KvikIO for GPUDirect Storage IO, cuxfilter for dashboards, and RAFT for low-level primitives. - Code Transformation Patterns: Provides before/after examples for converting NumPy, pandas, scikit-learn, NetworkX, scikit-image, and GeoPandas code to GPU equivalents, including zero-code-change accelerator modes like cudf.pandas, cuml.accel, and nx-cugraph. - Optimization Workflow: Guides profiling, GPU suitability assessment, memory management, and common pitfalls such as host-device transfer overhead and implicit CPU fallback. - Use Case: A data scientist with a slow pandas ETL pipeline and a scikit-learn training loop can convert both to cuDF and cuML, achieving 10-100x speedups with minimal code changes. ## Quick Start Ask the assistant to convert your NumPy or pandas script to run on the GPU and it will select the right library and rewrite the code.