-
Notifications
You must be signed in to change notification settings - Fork 0
Development Requirements
Will Pitchers edited this page Apr 12, 2019
·
2 revisions
These were the considerations considered essential when developing this workflow:
- It should run
sistr
to generate the serotype calls. - It should implement rules and filters to modify the
sistr
output where identified as appropriate during the validation -- these are detailed in the SOP and validation documents. - Document over each run how these rules and filters are applied.
- For each run of the software, ensure positive and negative controls are run, and the results documented.
- Produce, when appropriate, an output that can be uploaded directly in to LIMs.
- Have a process in place for self-validation of any changes to the code. This should produce a PDF that can be filed with Quality demonstrating that the characteristics of the test have not changed with modifications to the code.
- Have an easy way of introducing and documenting new rules and filters.
- Be deployed in a Singularity container.
- Output must report
sistr
version, as well as container version. - Workflow should be in Snakemake, and be able to work on an HPC running SLURM.
Reviewed by Anders Goncalves da Silva on 2019-06-21