Tweet
Hello,
after reading the paper, I am still not sure about what is the advantage of building an index for HISAT2 by calling hisat2-build with options —s and —exon instead of using the genome sequence only.
The online manual of HISAT2 tells that for the alignment phase it is possible to use the option --known-splicesite-infile and says: "Note that it is better to use indexes built using annotated transcripts (such as genome_tran or genome_snp_tran), which works better than using this option.”
But what 'better' means? Will be faster? Or will have more sensitivity? Or both?
In other words, if I do not build the index by giving annotated transcripts from a GTF file, and than I align by passing that GTF file, I loose only CPU time or I loose some alignments?
Thanks very much!
Alberto
after reading the paper, I am still not sure about what is the advantage of building an index for HISAT2 by calling hisat2-build with options —s and —exon instead of using the genome sequence only.
The online manual of HISAT2 tells that for the alignment phase it is possible to use the option --known-splicesite-infile and says: "Note that it is better to use indexes built using annotated transcripts (such as genome_tran or genome_snp_tran), which works better than using this option.”
But what 'better' means? Will be faster? Or will have more sensitivity? Or both?
In other words, if I do not build the index by giving annotated transcripts from a GTF file, and than I align by passing that GTF file, I loose only CPU time or I loose some alignments?
Thanks very much!
Alberto