Trimming Barcodes/Index Reads from FASTQ Read Headers before Alignment
Is it critical to trim the barcodes (or index reads), present in read headers before aligning sequences to the NR database using a tool such as DIAMOND?
Dataset consists of dual-indexed paired-end reads generated on the HiSeq
• 2,936 views
•
link
written
by
adityabandla •
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
Multiplexing for pooled CRISPR screen sequencing
written by Tuấn Anh •
-
single- indexed sequenced as paired end
written by amitpande74 •
-
Paired-end metagenomics data for MEGAN analysis
written by wangdp123
-
bcl2fastq with xGen Dual Index UMI Adapters to produce 3 read and 2 index fastqs
written by segrossk •
-
How to process Illumina MiSeq paired-end reads for analysis
written by snow_seq •
-
bcl2fastq2: how to correctly use the --use-bases-mask for different sequencing methods by Illumina ?
written by 乙
-
QIIME - Illumina MiSeq, Paired-end Data - Mapping file and Data Preprocessing Questions
written by sarajeanne08 •
-
Demultiplexing fastq files with dual barcodes
written by Thomas Moody •
-
merge .fastq reads of different lengths and align
written by User6891
-
How To Look For Known Fusion In Fastq File
written by Angel
No. You would need to convert the fastq sequences to fasta format (in strict fasta format anything after the first space in fasta header is ignored).
PE reads should basically give you the same result (unless you have a fusion or something unusual) so searching with only one of the reads should be adequate.
Hi Genomax
Thank you for the reply! Much appreciated. DIAMOND seems to accept FASTQ files as input as well (https://github.com/bbuchfink/diamond)
So I am just trimming adapters and adjusting the read headers before running them through DIAMOND
Ah well in that case you possibly don't need to worry about the tag sequence in fastq header (I assume your data is already de-multiplexed).