Wideband autonomous SDR analysis engine forked from sdr-visual-suite
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Jan Svabenik fb1ea9e4f8 chore: checkpoint current green baseline пре 2 дана
..
build chore: checkpoint current green baseline пре 2 дана
native Add stream-aware kernel launch entry points пре 2 дана
README.md docs: split CUDA build paths by platform пре 3 дана
batch.go Add batch extraction API to gpudemod пре 2 дана
batch_runner.go Use stream-backed Windows batch runner for extraction пре 2 дана
batch_runner_other.go Use stream-backed Windows batch runner for extraction пре 2 дана
batch_runner_windows.go Repair stream-backed batch runner with central Windows bridge пре 2 дана
doc.go docs: add initial CUDA demod kernel source пре 3 дана
errors.go Introduce reusable gpudemod batch runner пре 2 дана
gpudemod.go Add GPU shift-filter-decimate path for signal extraction пре 2 дана
gpudemod_cufft_test.go build: wire CUDA demod package through nvcc and MSVC пре 3 дана
gpudemod_stub.go Add GPU shift-filter-decimate path for signal extraction пре 2 дана
gpudemod_test.go feat: prepare CUDA demod launch boundary пре 3 дана
gpudemod_windows.go Repair stream-backed batch runner with central Windows bridge пре 2 дана
kernels.cu feat: add demod validation and GPU mode telemetry пре 3 дана
validation.go feat: wire CUDA freq-shift launcher пре 3 дана
validation_extra.go feat: add demod validation and GPU mode telemetry пре 3 дана
validation_extra_test.go feat: add demod validation and GPU mode telemetry пре 3 дана
validation_runtime.go Disable GPU validation by default in production пре 2 дана
validation_test.go feat: validate CUDA freq-shift output пре 3 дана
windows_bridge.go Repair stream-backed batch runner with central Windows bridge пре 2 дана

README.md

gpudemod

Phase 1 CUDA demod scaffolding.

Current state

  • Standard Go builds use gpudemod_stub.go (!cufft).
  • cufft builds allocate GPU buffers and cross the CGO/CUDA launch boundary.
  • If CUDA launch wrappers are not backed by compiled kernels yet, the code falls back to CPU DSP.
  • The shifted IQ path is already wired so a successful GPU freq-shift result can be copied back and reused immediately.
  • Build orchestration should now be considered OS-specific; see docs/build-cuda.md.

First real kernel

kernels.cu contains the first candidate implementation:

  • gpud_freq_shift_kernel

This is not compiled automatically yet in the current environment because the machine currently lacks a CUDA compiler toolchain in PATH (nvcc not found).

Next machine-side step

On a CUDA-capable dev machine with toolchain installed:

  1. Compile kernels.cu into an object file and archive it into a linkable library
    • helper script: tools/build-gpudemod-kernel.ps1
  2. On Jan's Windows machine, the working kernel-build path currently relies on nvcc + MSVC cl.exe in PATH
  3. Link gpudemod_kernels.lib into the cufft build
  4. Replace gpud_launch_freq_shift(...) stub body with the real kernel launch
  5. Validate copied-back shifted IQ against dsp.FreqShift
  6. Only then move the next stage (FM discriminator) onto the GPU

Why this is still useful

The runtime/buffer/recorder/fallback structure is already in place, so once kernel compilation is available, real acceleration can be inserted without another architecture rewrite.