You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In many cases, I get a single FASTQ with pared end reads "interleaved", namely reads for a pair are consecutive, have the same name except for a trailing /1 or /2 to identify the end of the pair. I see --mate1 and --mate2 for paired-end reads, and --read for single end reads.
The text was updated successfully, but these errors were encountered:
We appreciate all your useful feedback about making PuffAligner easier to use.
Support for interleaved FASTQ files seems as it would be a useful option. One question (for us as developers) is if it is better to special-case the parser for this format, or to take care of it externally in how the program is invoked. For example, a script like this one would make it possible to provide interleaved FASTQ files to Puffaligner and have it treat them as separate paired-end files by splitting the interleaved FASTQ file into two input FIFOs. The downside to this approach is that access to the executable in this case is mediated by one more level of indirection. On the plus side, something like this doesn't complicate the code and would work almost immediately. Perhaps we can provide a script like this for Puffalinger and you can let us know if it is adequate for your purposes.
In many cases, I get a single FASTQ with pared end reads "interleaved", namely reads for a pair are consecutive, have the same name except for a trailing
/1
or/2
to identify the end of the pair. I see--mate1
and--mate2
for paired-end reads, and--read
for single end reads.The text was updated successfully, but these errors were encountered: