R2 file contains duplicate data (R1 and R2)
Hello folks! I'm really new to all this, but am confused about some data files. I have the R1 and R2 files directly from the sequencer, but the R2 file is twice as large and contains all of the R1 data exactly duplicated before the actual R2 data. Am I misunderstanding the way this is organized? Why would the sequencer do this? (Like I said, I am really new so please be gentle!)
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
Why there are only two .fastq files in scATAC-seq raw data?
written by 浩然 •
-
Expected number of raw reads in fq.gz files in PE sequencing
written by Lada •
-
Dropseq, GSE124872 and structure of the reads in the FastQ files
written by tmms •
-
cat command to get multiple fq reads into single fastq file
written by Bioinfonext
-
Paired end data with R1 demultiplexed but not R2
written by singlegenome •
-
isolate reads from a paired-ended fastq files that fall within a certain bp range
written by nibhelim •
-
Trim Paired-end Fastq Files
written by yuabrahamliu •
-
Remove duplicates reads Ids
written by BioGeek
-
How to resync paired-end data?
written by germelcar •
-
Pandaseq in a bash for-loop - Error nofile
written by fibar
Hello, your question is valid but unfortunately not reproducible. Please show some data to illustrate the problem. How did you find about this issue, please show code and data examples to help us understand what is going on, then one might advise you what to do about it.
Hi! I'm not sure what data I could add that would be helpful here; I'm just looking at this manually at this point because I was running into problems using Galaxy. I noticed that the R2 file was exactly twice as large as the R1 file, so I selected the entirety of the R1 text and searched for it in the R2 file. The entire R1 text perfectly matched the text of the first half of the R2, including the identifiers. I'm just wondering why the sequencer would organize the data like this, since these files are directly from the sequencer. The rest of the R2 file looks as it should, with proper identifiers and everything. I think the data are just combined and I don't know why.