Add optional CUDA LiDAR terrain sweeps - #2
Draft
jpooley-hearst wants to merge 1 commit into
Draft
Conversation
jpooley-hearst
force-pushed
the
codex/cuda-lidar-terrain
branch
from
August 3, 2026 21:27
5ecb13a to
ec6905e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Design
The contribution lives under
cuda/and builds assignalserver-cuda. The existingsrc/Makefile,signalserver,signalserverHD, andsignalserverLIDARpaths are unchanged.A run shares transmitter location, frequency, terrain, radius, and sampling geometry. Terrain profiles and prefix state are reused; each
[variant.NAME]is an explicitly requested scenario, so pattern and power inputs are not cross-joined.The LiDAR preparation path accepts GeoTIFF, COG, VRT, and other GDAL-readable sources. It creates signed-int16 DTM and optional uint8 DSM-minus-DTM clutter rasters, validates metadata and binary sizes, and carries nodata through cache, GPU propagation, and output.
Validation boundary
Free-space output has an analytic regression baseline. The included CUDA P.1812 and ITM implementations remain experimental and emit
model_validation=unvalidated_implementationplus a runtime warning. The documentation explicitly excludes them from regulatory, safety, or other decision-grade use until independent reference-vector validation is complete.Verification
direct=spool,shards=full