Document test process for a new release
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 11
- Avg merge
- 12h 5m
- Merged PRs (30d)
- 24
Description
Once the HLA assay has been validated, we will need to validate each new release of the Micall pipeline. This task is to document how that validation process will work, and possibly document how the initial validation of the HLA assay will work.
Roughly, the validation of a new release will involve:
- reprocess the data files from a standard set of interesting samples (see issue #275)
- compare the results of the new Micall version to the previous version's results
- if a result differs, compare the new version's result to the 3730 result
- calculate if the changes are within acceptable limits
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 reviewing issue #275 for the standard sample set and the repository's release and validation context. Document the workflow for reprocessing samples, comparing versions, checking differences against 3730 results, and determining acceptable limits; clarify whether initial HLA assay validation is included.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100