Developer Guide¶
- Architecture
- GPU Kernels
- Testing
- Design Decisions
- 1. Standalone package via namespace extension
- 2. Drop cuCIM – custom CCCL kernels for labeling
- 3. OwnedRasterArray follows OwnedGeometryArray pattern
- 4. No new KernelClass values needed
- 5. Raster crossover thresholds are very low
- 6. Raster IO is HYBRID (with GPU_NATIVE alternative)
- 7. Standalone function API surface
- 8. No xarray core dependency
- 9. GPU-Native Raster IO via nvImageCodec
- vibespatial Core Integration