All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Remove the default read filters in the
samtools coverage
function. (This caused results with ReadsDeduped > 0 but CoveredBP 0). - Remove bug in the
final_report.tsv
report generation, the bug kept duplicated families (from Kraken) with MappedReads 0 in the report. - Update default values in the report to match the format of the
final_report.tsv
(e.g. 0.0 instead of 0)
- Add a
--doublestranded
flag to adjust damage pattern analysis to the ones observed in data created from double stranded libraries.- Changes the
bam_deam_stats.py
and themask_deamination.py
scripts to look at 3' G to A substitutions instead of the C to T changes as done before. - Nothing changes for default runs
- Changes the
- Fix a bug in the processing of paired fastq-files.
- removes the "1" flag from the resulting bam files (make sure to merge your reads before quicksand!)
This version adds 4 columns to the end of the final_report.tsv
file and adds an additional file filtered_report_{n}p_{m}b.tsv
to the output-directory. This file should serve as a quick look on the final_report and shoult not be treated as the final output file
This version alters the final_report.tsv
file and adds an additional file filtered_report_{n}p_{m}b.tsv
which is a filtered version of the final_report based on two freshly introduced filter-flags
--reportfilter_percentage
sets the filter threshold for the FamPercentage column--reportfilter_breadth
sets the filter threshold for the ProportionExpectedBreadth column
Within the workflow quicksand now takes additional information from the samtools coverage
command that analyzes the deduplicated reads. This additional information is (or is used to calculate)
- Depth of Coverage
- Breadth of Coverage
- Expected Breadth of Coverage, based on the inStrain documentation
- Proportion of Expected Breadth, based on the inStrain documentation
This is a rewrite of the v1.6.1
pipeline in dsl2 syntax of nextflow
to account for nextflow-versions >22.10
While the code was restructured, the flags, features and outputs remain the same as in v1.6.1
making these versions (almost) fully compatible. See the changes below.
- instead of
FamKmers
now reportSpeciesKmers
and the respective kmer-stats to better compare assignments. Before, families with many species always had lower kmer-stats - for each genome in the fixed-references file, run the full pipeline. They are no longer reduced to 1 reference per family as in
v1.6.1
- parse the taxonomy directly from the DB, no need to add an additional file!
- remove the test-data and the -profile test option, as it was no longer working
This is a minor update to the final_report created
- Added two columns to the end of the final_report.
MeanFragmentLength
: The mean fragment length of all the DNA molecules in the bedfiltered or deduped bamfileMeanFragmentLength(3term)
: The mean fragment length of all deaminated DNA molecules in the bedfiltered or deduped bamfile