Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.

An MR completes this bounty when it is merged into main with Closes #282 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Description

File-only SDR exercises become confusing when sample format, rate or length is missing. Provide an explicitly educational sidecar checker for local synthetic captures.

Who might enjoy this

  • Community interests: RF / SDR (Dragon), Research
  • Skills: python, qa, docs
  • Experience: starter; work style: automation.
  • Readiness: ready; bounty size: S (existing points tier; standard merge award stacks separately).

Current behavior and starting points

Source-reviewed against main cf05b29c6256dba70d0ebc09b22cc9867cdb786a on2026-10-18. Check current main and related issues/MRs before implementing so existing work is reused.

Relevant Files

Deliverables

  • A documented minimal sidecar schema for one supported IQ format with sample rate, byte order, sample count and synthetic provenance.
  • A read-only standard-library Python validator plus good and deliberately malformed local fixtures.

Dependencies and decisions

No prerequisite issue is required. Re-read current main and linked MRs before starting.

Acceptance criteria

  • [ ] The CLI accepts the known-good recording and reports the computed duration; a truncated data file and mismatched sample count fail by name.
  • [ ] Missing/invalid sample rate, unsupported format and paths outside the explicitly selected exercise directory produce nonzero status without modifying files.
  • [ ] Demonstrate the validator never opens sockets and never prints sample contents; deterministic JSON output supports future benches.
  • [ ] Record named baseline failures and the exact commands used. A behavior fix includes a real route/database/protocol check observed failing before the change. Knowledge work includes source traceability and reproducible reviewer evidence.
  • [ ] Run the affected app's existing checks. Explain any baseline failures rather than reporting a matching failure count as proof.

Try it locally

Start from the existing source files above. The following is the target demo your contribution should enable; a newly proposed script or fixture is part of the deliverable:

Run python3 apps/wiki/scripts/check_rf_exercise.py --manifest <synthetic-manifest>; truncate a copy of its data file to see a useful rejection.

Use public or synthetic examples. Starter work should run without production access; explicitly name any software/device prerequisite before claiming it is ready.

Out of scope

  • No new production upload or library-ingestion schema, automatic directory scan or claim of full SigMF conformance.
  • No copying private recordings or changing live collection tools.
  • Unrelated refactors, new services/providers, bulk dependency changes, production access changes, unrequested notifications, and copying private member material. Keep credentials and unresolved security findings outside the issue and repository.

For a coding agent and reviewer

Read AGENTS.md, applicable .cursor/rules/, app instructions and docs/contributing/agentic-bounty-review.md. Reuse the existing shared helpers, identity/access paths and app styling. Implement one bounded story and provide evidence the accepting app maintainer can reproduce. State updated / pre-release verified / released / live verified accurately.

A parent index carries no duplicate award for these child deliverables. Open one scoped MR using this issue's actual number after the closing keyword. Link your GitLab identity on Scoreboard; the existing merge webhook handles eligible points.

Catalog index: #258.

<!-- community-interest-bounty:2026-10-18:rf-capture-sidecar -->

Relevant files

Hints

No hints yet.

Activity

  • +50 Hugo Zarate earned S bounty Oct 19

Comments

No comments yet. Be the first to weigh in.

↑ Top