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 #292 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Submit a merge request that closes this issue to earn points on merge — bounties stack on the standard +40 merge_pr award. New to the repo? See the Contributing guide, and Local Development & SSO to run the app locally (cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.

Description

The training-event survey guide recommends pre/post comparison and CSV analysis. Provide an offline exercise that handles missing responses and changing denominators visibly.

Who might enjoy this

  • Community interests: Warfare studies, Research, Professional development
  • Skills: python, data, docs
  • Experience: starter; work style: analytical.
  • 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

  • Original synthetic pre/post CSVs with fictitious participant IDs, an optional-pairing field and deliberately missing answers.
  • A Python standard-library CLI producing counts, denominators, missingness and clearly labeled paired/unpaired summaries plus a worked guide.

Dependencies and decisions

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

Acceptance criteria

  • [ ] Known-answer fixtures verify each count and denominator; missing answers are excluded from that question's denominator and are reported separately.
  • [ ] The paired result includes only synthetic IDs present in both periods; the unpaired result clearly shows different sample sizes.
  • [ ] Invalid rating, duplicated ID and missing column produce actionable failures; no files are uploaded and no raw free-text responses are printed.
  • [ ] 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 the CLI on the supplied fictional workshop CSVs, remove one post response, and inspect the paired and unpaired denominators.

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 real student/member records, automated effectiveness claims, demographic inference or integration with survey accounts.
  • No new questionnaire platform.
  • 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:training-survey-analysis -->

Relevant files

Hints

No hints yet.

Activity

No points have been awarded for this bounty yet.

Comments

No comments yet. Be the first to weigh in.

↑ Top