domains / families / software-engineering / warp-eval
warp-eval
separate
Evaluate whether an existing hot path is a credible NVIDIA Warp candidate. Use for irregular or spatial queries, particle or geometry simulation, branch-heavy loops, many small launches, host fallbacks, or large intermediates. CPU-only code and absent GPU dependencies are normal unless NVIDIA is prohibited. Exclude required cross-vendor or CPU-only deployment, vendor-lowered dense or NN layers, general Warp API questions, and already-selected Warp kernels. Contribution policy alone is not exclusion.
When to use
- Collect reproducible evidence about how a **narrow seam** in an existing codebase would behave in NVIDIA Warp. Report facts; the user decides. Name Warp as the option under evaluation in the first line, state that no adoption recommendatio…
When not to use
- **Warp CPU kernels are serial and outside this skill's evaluation scope.**
- **Mesh and geometry queries compute in float32/int32** even behind a float64
- **Warp does not follow semver.** Feature releases can break APIs, only the
- **`latest` docs track development, not the shipped release.** Pin to the
- **Kernel-only builtins are not resolvable from Python** —
- **`enable_backward=False`** (kernel, module or global) removes adjoint
Skill page
Source