Triage and reproduce three open GitHub issues (good first issue)

[dblizinski]

What this is

Pick three open issues from this repo that lack clear reproduction steps. Try to reproduce them yourself using the simulator or public test fixtures, then comment back with structured reproduction notes — or document why the issue couldn't be reproduced.

Why this matters

Issue triage is the unglamorous work that determines whether maintainers can actually fix things. Our tracker has signal-to-noise issues right now that slow down every other kind of contribution. Even cleaning up three issues meaningfully helps.

What to do

1. Comment to claim.
2. Browse open issues without the label needs-triage:reproduced. Pick three you find interesting and that look like they need clarification.
3. For each chosen issue: set up the environment per the docs, follow whatever steps exist in the issue, and try to reproduce.
4. Comment on each issue with structured notes in this format:

Reproduction attempt:

• Commit/branch tested: [SHA or branch name]
• Environment: [OS, Python version, etc.]
• Steps taken: [numbered list]
• Outcome: [reproduced / could not reproduce / partial reproduction]
• Logs / screenshots: [if relevant]

5. Apply the appropriate labels: needs-triage:reproduced if you reproduced it, needs-triage:cannot-reproduce if you couldn't, needs-info if more detail is needed from the reporter.
6. Comment on this meta-issue with links to the three issues you triaged.

Definition of done

• Three issues triaged with structured reproduction notes.
• Appropriate triage labels applied.
• This issue updated with links to the three triaged issues.

Skills

• Comfort setting up a dev environment
• Careful, patient debugging
• Clear writing

Scope estimate

3–5 hours per issue, so 9–15 hours total. Scope yourself accordingly when claiming.

Helpful starting points

• Open issues: https://github.com/OpenwaterHealth/opw_neuromod_sw/issues
• Repo CONTRIBUTING.md and README.md
• The Day-1 tutorial (D1) once it exists — it's the fastest way to a working environment

---

How to claim this issue

1. Comment "I'd like to work on this" — we'll assign it to you.
2. Within ~2 weeks of being assigned, comment with the three issues you've chosen so others know not to duplicate.
3. Ask any setup questions on this issue or in our Discord #contributing channel.

Contact: community@openwater.health

By contributing, you agree to our Contributor License Agreement. (If the CLA isn't yet live when you start, we'll handle it once the flow is up.)

[vaishnavidesai09]

I'd like to work on this

[dblizinski]

It's yours. Thanks!

[vaishnavidesai09]

Completed triage of three issues:

1. Logger issue when running test_sim by itself #328 — Logger issue when running test_sim by itself — partial reproduction on Windows 10 / Python 3.14.2. k-wave-python install is blocked by scipy==1.15.3 requiring a Fortran compiler not present on Windows, so the originally reported logger TypeError could not be reached. Root cause (kwave version constraint tied to Python version) confirmed. Requested needs-info label.

2. Session can contain stale references to photoscans #467 — Session can contain stale references to photoscans — confirmed via code inspection. TransducerTrackingResult loads photoscan_id directly from stored data in session.py lines 147–151 with no validation that the referenced photoscan exists in the database. Requested needs-triage:reproduced label.

3. Solution Analysis Options constants scaling #468 — Solution Analysis Options constants scaling — confirmed via code inspection. SolutionAnalysisOptions defaults (mainlobe_radius=2.5e-3, beamwidth_radius=5e-3, sidelobe_radius=3e-3, sidelobe_zmin=1e-3) are hardcoded in meters while distance_units defaults to "m". If a user sets a different unit, these defaults become incorrect. Requested needs-triage:reproduced label.

Structured reproduction notes added to each issue.

[vaishnavidesai09]

Completed triage of three issues:

1. Logger issue when running test_sim by itself #328 — Logger issue when running test_sim by itself — reproduced on Windows 10 / Python 3.11.5 with k-wave-python 0.4.0. Exact TypeError: not all arguments converted during string formatting confirmed in expand_grid_matrices.py:268 when running pytest -k test_sim alone. Requested needs-triage:reproduced label.

2. Session can contain stale references to photoscans #467 — Session can contain stale references to photoscans — confirmed via code inspection. TransducerTrackingResult loads photoscan_id directly from stored data in session.py lines 147–151 with no validation that the referenced photoscan exists in the database. Requested needs-triage:reproduced label.

3. Solution Analysis Options constants scaling #468 — Solution Analysis Options constants scaling — confirmed via code inspection. SolutionAnalysisOptions defaults (mainlobe_radius=2.5e-3, beamwidth_radius=5e-3, sidelobe_radius=3e-3, sidelobe_zmin=1e-3) are hardcoded in meters while distance_units defaults to "m". If a user sets a different unit, these defaults become incorrect. Requested needs-triage:reproduced label.

Structured reproduction notes added to each issue.