Rewrite paired end fastq files to make sure that all reads have a mate and to separate out singletons.
This code does one thing: it takes two fastq files, and generates four fastq files. That's right, for free it doubles the number of fastq files that you have!!
Usually when you get paired end read files you have two files with a /1 sequence in one and a /2 sequence in the other (or a /f and /r or just two reads with the same ID). However, often when working with files from a third party source (e.g. the SRA) there are different numbers of reads in each file (because some reads fail QC). Spades, bowtie2 and other tools break because they demand paired end files have the same number of reads.
This program solves that problem.
It rewrites the files with the sequences in order, with matching files for the two files provided on the command line, and then any single reads that are not matched are place in two separate files, one for each original file.
This code is designed to be fast and memory efficient, and works with large fastq files. It does not store the whole file in memory, but rather just stores the locations of each of the indices in the first file provided in memory.
The most efficient way to use this code is to provide the smallest file first (though it doesn't matter which way you
provide the files), and then to manipulate the -t parameter on the command line. The code implementation is based
on a hash table and the size of that table is the biggest way to make this
code run faster. If you set the hash table size too low, then the data structure quickly fills up and the performance
degrades to what we call O(n). On the other hand if you set the table size too big, then you waste a lot of memory,
and it takes longer to initialize the data structures safely.
The optimal table size is basically somewhere around the number of sequences in your fastq files. You can quickly find out how many sequences there are in your fastq file:
wc -l fastq_filename
The number of sequences will be the number printed here, divided by 4.
Note: If you get an error that looks like
"We cannot allocate the memory for a table size of -436581356. Please try a smaller value for -t"
you are probably suffering from an integer overflow, so try reducing the value you are providing to the -t option.
See issue 12 for more details.
If you are not sure, you can run this code with the -p parameter. Before it prints out the matched pairs of sequences,
it will print out the number of sequences in each "bucket" in the table. If this number is more than about a dozen you
need to increase the value you provide to -t. If most of the entries are zero, then you should decrease the size of
-t.
As an aside, this code is also really slow if none of your sequences are paired. You should most likely use this after taking a peek at your files and making sure there are at least some paired sequences in your files!
We recommend installing fastq-pair using bioconda
mamba install -c bioconda fastq-pair
or in its own environment:
mamba create --name fastq-pair -c bioconda fastq-pair
To install the code, grab the github repository, then make a build directory:
mkdir build && cd build
cmake3 ..
make && sudo make install
There are more instructions on the installation page.
fastq_pair takes two primary arguments. The name of the two fastq files that you want to pair up.
fastq_pair file1.fastq file2.fastq
You can also change the size of the hash table using the -t parameter:
fastq_pair -t 50021 file1.fastq file2.fastq
You can also print out the number of elements in each bucket using the -p parameter:
fastq_pair -p -t 100 file1.fastq file2.fastq
In the test directory there are two fastq files that you can use to test fastq_pair. There are 250 sequences
in the left file and 75 sequences in the right file. Only 50 sequences are common
between the two files.
You can test the code with:
fastq_pair -t 1000 test/left.fastq test/right.fastq
This will make four files in the test/ directory:
- left.fastq.paired.fq
- left.fastq.single.fq
- right.fastq.paired.fq
- right.fastq.single.fq
The paired files have 50 sequences each, and the two single files have 200 and 25 sequences (left and right respectively).
Unfortunately fastq_pair doesn't work with gzipped files at the moment, because it relies heavily on random access of
the file stream. That is complex with gzipped files, especially when the uncompressed file exceeds available memory
(which is exactly the situation that fastq_pair was designed to handle).
Therefore, at this time, fastq_pair does not support gzipped files. You need to uncompress the files before using
fastq_pair.
If you really need to use gzipped files, and can accept slightly worse performance, then we have some alternative approaches written in Python that you can try.
Testing for gzipped files (issue #6)
We take a peek at the first couple of bytes in the file to see if the file is gzip compressed. Per the standard, the
files should start 0x1F and 0x8B as the first two bytes. There is a small tester for the gzip program, called test_gzip.c,
that takes a single argument and reports whether it is gzipped or not. You can compile that tester with the command:
gcc -std=gnu99 -o testgz ./test_gzip.c is_gzipped.c
We now test both files and exit (hopefully gracefully) if either is gzip compressed. The easiest solution is to uncompress your files, and we recommend and love pigz because it is awesome!
Please see the CITATION file for the current citation for fastq-pair
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent