Closed MartinPippel closed 2 years ago
@MartinPippel thank you for sharing your results. The plot is nice.
We decided to change the min-quality
default to output all reads by default. Users should set this value as needed for their use case.
I have updated the release notes to add an item detailing this change.
@MartinPippel after discussing this issue we decided to revert the --min-quality
flag to the original default value of 20. This update was just release (v0.3.1), and that is the only significant change in that release.
Dear DeepConsensus developers,
thanks for the update. I really like the performance improvements of release 0.3.
Quick question: Why does the --min_quality flag is not set to 20? Due to the great yield, it was a bit hard to detect that I got several reads with an error rate >> 2%.
I usually run DC (v03) only on reads that have 97%-99.9% consensus accuracy (for time reasons). Without setting the --min_quality flag to 20 I do get the following results (filtered afterwards with >=Q20: pass, otherwise fail)
When I add the --min_quality 20 value to the deepconsensus run: I get the expected results:
Just for completeness. A very very small fraction of the DC improved reads got a lower QV value compared to the input reads. When I try rescue those, that initially had >=Q20 I get the following "rescued" read stats:
Once again thanks for the great tool. I just posted this message so that others are aware of this behaviour. The attached figure compares unfiltered QV values between pbccs v6.4 - deepconsensus v0.2 - deepconsensus v0.3 (from left to right) The red dots highlight reads <Q20.
Cheers, Martin