Would someone know why unappropriate "genomeSAindexNbases" value causes Segmentation Fault?
When I was creating an Index file using HIV virus genome sequence with STAR, I realized with a lot of help, if the genome sequence I am indexing is too small or big, I needed to set a "genomeSAindexNbases" value based on log2(GenomeLength)/2 -1 or it would cause segmentation fault.
I was wondering the mechanism behind why it wouldn't just make make a faulty or inadequate index file. Is it by the creator's design? or is it just programmatically not possible?
I hope someone might have information on this matter.
• 830 views
•
link
written
by
maxdlf12 •
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
Biscuit Alignment and Index failed - WGBS - Bisulfite analysis
written by Palanikumar.Palanichamy •
-
STAR error (segmentation fault) in Aligning reads
written by sp29 •
-
Problem mapping mRNA seq data using STAR.
written by Seq225
-
is -a bwtsw flag compulsory for indexing human genome with BWA?
written by marongiu.luigi
-
HIV question and certainty in a legal setting
written by d233938d •
-
Aligning unmapped reads to viral genomes
written by cristina_sabiers
-
RNAstar alignment segmentation fault
written by sam •
-
Problem In Indexing The Sorted Bam File For Exome Sequencing Downstream Analysis
written by ivivek_ngs
-
Bedtools "Segmentation Fault" While Working With Genome.Fa
written by PoGibas
-
Bwa Index Segmentation Fault
written by Nitram •
