Hi,
it happened to me I had to disable softclipping altogether in hisat2 aligner a decrease limits for alignment extension as I was loosing some 10nt deletions due to too short alignment on either side of the deletion site. In addition I had to also disable softclipping.
Hisat2 is aimed at about 125 or 150 reads according to some comments in your Changelog. But if you get 75 nt reads you have to push down the thresholds and disable softlipping too. This should be inluded in the documentation, Readme.md and runtime help.
I ended up with hisat2-2.2.1/hisat2-align-s --bowtie2-dp 2 --score-min L,0,-1 --no-softclip .... Probably the trailing -1 is an overkill but I failed to understand how this works.
Hi, it happened to me I had to disable softclipping altogether in hisat2 aligner a decrease limits for alignment extension as I was loosing some 10nt deletions due to too short alignment on either side of the deletion site. In addition I had to also disable softclipping.
Hisat2 is aimed at about 125 or 150 reads according to some comments in your Changelog. But if you get 75 nt reads you have to push down the thresholds and disable softlipping too. This should be inluded in the documentation, Readme.md and runtime help.
I ended up with
hisat2-2.2.1/hisat2-align-s --bowtie2-dp 2 --score-min L,0,-1 --no-softclip ...
. Probably the trailing-1
is an overkill but I failed to understand how this works.Here is a small testcase:
read_pairs_spanning_10nt_deletion_at_chr5:112780802.R1.fastq.txt read_pairs_spanning_10nt_deletion_at_chr5:112780802.R2.fastq.txt