Repository navigation
Triage and reproduce three open GitHub issues (good first issue) #460
Description
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
- Comment to claim.
- Browse open issues without the label
needs-triage:reproduced. Pick three you find interesting and that look like they need clarification. - For each chosen issue: set up the environment per the docs, follow whatever steps exist in the issue, and try to reproduce.
- 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]
- Apply the appropriate labels:
needs-triage:reproducedif you reproduced it,needs-triage:cannot-reproduceif you couldn't,needs-infoif more detail is needed from the reporter. - 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.mdandREADME.md - The Day-1 tutorial (D1) once it exists — it's the fastest way to a working environment
How to claim this issue
- Comment "I'd like to work on this" — we'll assign it to you.
- Within ~2 weeks of being assigned, comment with the three issues you've chosen so others know not to duplicate.
- Ask any setup questions on this issue or in our Discord
#contributingchannel.
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.)
Activity
vaishnavidesai09 commentedon Jun 9, 2026
I'd like to work on this
dblizinski commentedon Jun 9, 2026
It's yours. Thanks!
vaishnavidesai09 commentedon Jun 12, 2026
Completed triage of three issues:
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-pythoninstall is blocked byscipy==1.15.3requiring a Fortran compiler not present on Windows, so the originally reported loggerTypeErrorcould not be reached. Root cause (kwave version constraint tied to Python version) confirmed. Requestedneeds-infolabel.Session can contain stale references to photoscans #467 — Session can contain stale references to photoscans — confirmed via code inspection.
TransducerTrackingResultloadsphotoscan_iddirectly from stored data insession.pylines 147–151 with no validation that the referenced photoscan exists in the database. Requestedneeds-triage:reproducedlabel.Solution Analysis Options constants scaling #468 — Solution Analysis Options constants scaling — confirmed via code inspection.
SolutionAnalysisOptionsdefaults (mainlobe_radius=2.5e-3,beamwidth_radius=5e-3,sidelobe_radius=3e-3,sidelobe_zmin=1e-3) are hardcoded in meters whiledistance_unitsdefaults to"m". If a user sets a different unit, these defaults become incorrect. Requestedneeds-triage:reproducedlabel.Structured reproduction notes added to each issue.
vaishnavidesai09 commentedon Jun 12, 2026
Completed triage of three issues:
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 formattingconfirmed inexpand_grid_matrices.py:268when runningpytest -k test_simalone. Requestedneeds-triage:reproducedlabel.Session can contain stale references to photoscans #467 — Session can contain stale references to photoscans — confirmed via code inspection.
TransducerTrackingResultloadsphotoscan_iddirectly from stored data insession.pylines 147–151 with no validation that the referenced photoscan exists in the database. Requestedneeds-triage:reproducedlabel.Solution Analysis Options constants scaling #468 — Solution Analysis Options constants scaling — confirmed via code inspection.
SolutionAnalysisOptionsdefaults (mainlobe_radius=2.5e-3,beamwidth_radius=5e-3,sidelobe_radius=3e-3,sidelobe_zmin=1e-3) are hardcoded in meters whiledistance_unitsdefaults to"m". If a user sets a different unit, these defaults become incorrect. Requestedneeds-triage:reproducedlabel.Structured reproduction notes added to each issue.
AayushDey commentedon Sep 6, 2026
I'd like to work on this issue. I’ll set up the environment and triage three open issues with structured reproduction notes.
Angelo9up commentedon Sep 16, 2026
Hi! I'd like to work on this issue. I'm a new contributor and will follow the project's contribution workflow.
Alexd062024 commentedon Sep 22, 2026
Hi! I'd like to work on this.
I've already set up the development environment and reproduced #136 locally on
main(58069a0ffee2e104edc7cca7e9464d70881e89e2).I'm currently planning to triage:
I'll post structured reproduction notes on each issue as I work through them.
Please let me know if any of these are already being handled or if you'd prefer that I choose different issues.
dblizinski commentedon Sep 22, 2026
These are yours. Thanks.
Alexd062024 commentedon Sep 23, 2026
Hi! I’ve completed the triage for the three issues I selected:
Overwriting a volume can leave a dangling volume file in the database #136 — REPRODUCED
The stale volume file is still present on current
main. There is already an open fix in Fix stale volume file on overwrite #497 under review.Overwriting a volume can leave a dangling volume file in the database #136
Sessions should not allow duplicate target ID #134 — REPRODUCED
Sessioncurrently accepts duplicate target IDs through construction, serialization, database write, and reload. The previous attempt in Fix #134: Prevent duplicate target IDs in Session #327 was closed without merge.Sessions should not allow duplicate target ID #134
Source of truth on parameter constraints unclear #293 — REPRODUCED
Protocol.param_constraintsis the effective source used by the normal analysis flow.SolutionAnalysisOptions.param_constraintsis serialized/deserialized but is not consumed bySolution.analyze(options=...)unless constraints are passed separately through theparam_constraintsargument.Source of truth on parameter constraints unclear #293
All three were tested on:
58069a0ffee2e104edc7cca7e9464d70881e89e2(main)Environment:
I posted the detailed reproduction notes directly on each issue.
Please let me know if you’d like any additional verification or follow-up on any of them.