executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
setup-and-backendsGuides 3D Gaussian Splatting installation, CUDA extension builds, backend checks, and dependency troubleshooting.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is about installing gaussian-splatting, deciding a CUDA/PyTorch/compiler combination, initializing submodules, checking imports, or diagnosing build/runtime backend errors before training or rendering.
The repository is not a CPU-only Python package. Its primary optimizer, renderer, metrics, and Gaussian model code use CUDA tensors and custom CUDA extensions:
diff_gaussian_rasterization supplies the differentiable renderer.simple_knn supplies CUDA distance computations for Gaussian initialization.fused_ssim is optional but used when installed for faster SSIM loss.Do not claim training, rendering, or metric execution is verified unless CUDA and the required extensions import and a tiny CUDA allocation succeeds.
plyfile, tqdm, opencv-python, joblib), then build/install the CUDA extensions from their submodule directories.--require-cuda --require-extensions before planning any native train/render verification.python path/to/check_backend.py --repo-root /path/to/gaussian-splatting --require-cuda --require-extensions --tools
Interpretation:
PASS import diff_gaussian_rasterization, PASS import simple_knn._C, and PASS import fused_ssim mean the Python extension modules import.PASS tiny CUDA tensor allocation means PyTorch can allocate on a visible CUDA device.colmap or magick is not a Python stack failure unless the user is converting raw images.train.py, render.py, metrics.py, or full evaluation here; those are final/native workflow checks after skill integration.