In response to question 1, what do the parameters -I and -X (min and max fragment length) have to do with the paired end parameters. I guess I don't completely understand the correlation between these and the other parameters such as disabling looking for discordant mates, etc.
How does HISAT calculate the alignment score? (and other TopHat to HISAT questions)
I've recently switched from using TopHat to using HISAT. Trying to figure out which parameters do what I want has been a bit of a challenge in spite of the manual. I realize some things may not be explainable as they are proprietary. But I think a few of my questions can be addressed.
- Is there a "Mean Inner Distance between Mate Pairs" (TopHat) equivalent in HISAT?
- Is there a way to only display/align reads that have no mismatches? (I think I figured this one out, but see the next question)
- How does HISAT calculate the Alignment Score (AS)? From what I can tell with my data, if the read is a perfect match the AS = 0, but if there is a mismatch/insertion/deletion/soft-clipping/etc. it is around AS=250.
- How does the program decide if it is using HGM or HGFM?
Thanks for any help that can be provided!
1 answer
- No, thankfully.
- I guess you could set
--mpto something quite high, though why you would want to forbid mismatches is beyond me. - An alignment starts with a score of 0 and gets penalized according to how it aligns and the settings for
--mp,--spand so on. - I have no idea what you mean by "HGM". Hisat2 uses an HGFM index which may or may not include things like SNPs or splice sites. Whether it does or not depends on how you made the indices. See the help for
hisat2-build.
BTW, since you mentioned "proprietary", please be aware that it's rare for anything in bioinformatics to involve proprietary code. For example, hisat2's entire source code is available here.
• 0 views
•
link
written
by
Devon Ryan
Fragment lengths outside of those ranges will be discordant.
• 0 views
•
link
written
by
Devon Ryan
I guess you could set --mp to something quite high, though why you would want to forbid mismatches is beyond me.
please explain a bit more, i also need a specific number of mis-matches. alignments with one mismatch and with two mismatches allowed..
• 1 views
•
link
written
by
ataulhaleem •
Log in to answer this question.
More posts like this
-
Different mapping results between HISAT and TopHat
written by concetta •
-
Filtering noise out of SAM file using CIGAR
written by blur
-
How to extract forward and reverse primer coordinates for soft clipping?
written by bioinfo89 •
-
Doubts about RNA-seq Cufflinks
written by vm.higareda •
-
Is there a tool to convert soft clipping to hard clipping in bam files?
written by Ryan Thompson
-
Tophat Parameters for RNA seq de novo
written by nikelle.petrillo
-
No soft-clipping in BWA 0.7.10 anymore?
written by Sebastian •
-
Soft Clipping
written by Gregor Rot
-
Why Is Bwa Soft-Clipping Exactly Matching Reads?
written by ktpetrie •
-
Galaxy Tophat
written by KS
Hello! I am trying to figure out how to only allow a specific number of mismatches (eg 2) using HISAT2, which should be in your question 2. Could you please let me know how you achieve that? Thank you!
Old post, but will include for anyone else looking for similar answer.
HISAT2 has a scoring function that it uses to calculate the final alignment. You can set the mismatch penalty to be a constant penalty that will be some multiple of the function that you change.
So if you want two mismatches you can change the minimum scoring function to something like
Changing the function to no longer be dependent upon the read length (the second integer term).
Then, changing mismatch penalty, we can have the min/max be the same so a constant term is subtracted whenever a mismatch is detected.
The other options are to prevent gaps and ambigious characters from being reported in abundance. You're probably better off using something like bowtie2 if you want to specify an exact number of mismatches.