Why no any improvement of QV is achieved using NextPolish2?
bioinformaticspcj opened this issue · 11 comments
Dear the authors,
Thanks for developing such a useful tool to polish the results of Hifiasm. I try to polish my Hifiasm's assembly (assembled with 40 × hifi reads) but found the QV of the polished assembly is as the same as the unpolished one. The species genome is highly heterozygous (rate: 0.77%). I do not know why? Could you be kind to help me?
The commands used are as follows:
hifiasm -t 60 -o Pvat -l 2 -s 0.75 --h1 R1.fq.gz --h2 R2.fq.gz hifi.fastq.gz
winnowmap -k 21 -t 100 -W repetitive_k21.txt -ax map-pb Pvat.hic.p_ctg.fa hifi.fastq.gz |samtools sort -@ 100 -o hifi.map.sort.bam -
yak count -t 100 -o k21.yak -k 21 -b 37 <(zcat illumina_.fq.gz)
yak count -t 100 -o k31.yak -k 31 -b 37 <(zcat illumina_.fq.gz)
nextPolish2 -r hifi.map.sort.bam Pvit.hic.p_ctg.fa k21.yak k31.yak -t 100 -o Pvat.hic.p_ctg.polished.v1.fa
The QV before polishing:
45.1437
The QV after polishing:
45.1451
Thanks again!
Bob
Could you share the raw data (assembly.fa illumina_.fq.gz hifi.fastq.gz) to me? so I can figure out why?
In addition, you can map the illumina reads to the assembly, and then check the mapping coverage/quality of regions in the assembly with error kmers. If these regions do not have short reads mapped, nextPolish2 can not polish them because nextPolish2 requires short reads to validate kmes.
OK
No, but the improvement will not be great. becasue nextPolish2 will keep ref. unchanged if it cannot confirm that the candidate kmer is correct to avoid potential overcorrections, BTW: You can use PCR-free library.
yes
@bioinformaticspcj hello, did you resolved this problem now? i met the same problem.
You need to first check the mapping coverage/quality in the regions of the assembly with error kmers. If these regions has no short reads mapped, NextPolish2 can not be used to improve QV.
@bioinformaticspcj did you got the QV by nextpolish2 or the merqury ?