New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
high rate of reads unmapped: too short #1959
Comments
It could be an issue with pairing of reads in FASTQ files. You can test it by mapping Read1 and Read2 separately. |
When I map the Read1 and Read2 files separately, the map rate of the two files reaches more than 80%,how can i slove the problem about the pairing of reads in FASTQ files? THANK YOU |
If you are trimming reads before mapping, I would try to map untrimmed (raw) reads. |
When I analyze the new command parameters given by the sequencing company, the mapping rate has reached 70%. Excuse me, which of these parameters have played a key role?THANK YOU! the low mapping rate command : the high mapping rate command: |
When I use STAR for alignment, many reads do not align. How can I resolve this? THANK YOU !
below is my parameter:
STAR --runThreadN 15 --runMode alignReads --quantMode TranscriptomeSAM GeneCounts --sjdbOverhang 149 --twopassMode Basic --outSAMtype BAM SortedByCoordinate --outBAMsortingThreadN 15 --limitSjdbInsertNsj 12115510 --genomeDir /storage/zuozd/genome/ipomoea_batatas_tai6/star-gffreadgtf149/ --readFilesIn /storage/zuozd/20230921bleeding_sap/00cleandata/${i}_1.clean.fq.gz /storage/zuozd/20230921bleeding_sap/00cleandata/${i}_1.clean.fq.gz --readFilesCommand zcat --outFileNamePrefix ${i}
The text was updated successfully, but these errors were encountered: