Gene coverage / QC coverage pages - improvements
- Dominant language
- Python
- Stars
- 30
- Forks
- 3
- Avg merge
- 9h 28m
- Merged PRs (30d)
- 42
Description
🤖 Written by Claude
*(Updated: evidence replaced with real VG3 production figures — the original table was mistakenly drawn from VG4 dev/test box logs. The VG3 numbers are considerably stronger.)*
SA Path **VG3 production** logs (4–18 Aug 2026, 15 days) show per-sample coverage review is part of the routine lab workflow, while nearly all commits touching these grids since 2021 have been mechanical (linting, refactors):
| Page | Requests |
|---|---|
| `genes/gene_coverage/grid` (handler + config) | 356 |
| `genes/uncovered_genes/grid` (handler + config) | 201 |
| `seqauto/api/view_enrichment_kit_summary` | 289 |
| `seqauto/view_qc/view_gene_coverage_collection_tab` | 2 |
| `genes/qc_coverage` pages | ~0 |
So it's the **gene coverage and uncovered-genes grids** (loaded from sample/QC pages) that are used — both still jqGrid. Suggested:
* Convert these grids to DataTables (#1461 family)
* Ask SA Path users what would make coverage review easier (e.g. uncovered-region reporting, better navigation from sample/run pages)
Evidence gathered in `claude/vg3_usage/` (nginx usage vs git effort analysis).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the genes/gene_coverage/grid and genes/uncovered_genes/grid entry points, including their handlers and config, then review the usage evidence in claude/vg3_usage/. Confirm the desired coverage-review improvements with SA Path users; done should be an agreed scope for the two grids and a decided implementation direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100