Mark coverage scores for review
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 11
- Avg merge
- 12h 5m
- Merged PRs (30d)
- 24
Description
James is working on the review feature, and we decided that the pipeline should decide which coverage scores need manual review.
Include a new column in the coverage scores file that requests a review. It could hold one of three values: pass, needs review, or fail.
- add
review_statecolumn - generate resistance results even for failed samples, so reports can be released if they are manually overridden
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
Locate the code that writes the coverage scores file and the pipeline stage that produces resistance results. Trace how failed samples are currently handled, then define completion as adding a review_state value of pass, needs review, or fail and producing resistance results for failed samples so manually overridden reports can be released.
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
- 35/100