Separate coverage grid into project sections
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 11
- Avg merge
- 12h 5m
- Merged PRs (30d)
- 24
Description
Sample names indicate the selected project with a suffix: E1234_HCV selected the HCV project. On the MiCall page of QAI, group the samples by project, and sort by extraction number within each group.
Shared tags are a little tricky. For example, E1111_HLA-B;E2222-1_V3LOOP should appear both in the HLA-B group and in the V3LOOP group. Also, the sample should be sorted by E1111 in the HLA-B group and E2222 in the V3LOOP group.
Each group's coverage grid should display gene regions that appear in its samples. If none of the V3LOOP samples have shared tags or contamination from an HCV sample, then the V3LOOP group won't include the HCV columns.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the QAI MiCall page and the code that builds its coverage grid, then trace how sample names, shared tags, extraction numbers, and gene-region columns are currently handled. Done means samples are grouped and sorted per project, shared-tag samples appear in every relevant group, and each grid contains only regions represented by that group's samples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100