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
The proposal above adds a check to determine whether the first read of a paired fastq sample shares its flowcell id. However, if a user were to supply a fastq file that was merged from different fastq files of the same sample (e.g., across lanes or sequence runs), the flowcell id would not be the same for all reads in the fastq file.
Ideally we'd add a check to ensure that this is the case (seqkit?), or if possible, use something like fastp to split the files into separte fastq files with uniform flowcell ids?
The text was updated successfully, but these errors were encountered:
Description of feature
This is an extension of #1664
The proposal above adds a check to determine whether the first read of a paired fastq sample shares its flowcell id. However, if a user were to supply a fastq file that was merged from different fastq files of the same sample (e.g., across lanes or sequence runs), the flowcell id would not be the same for all reads in the fastq file.
Ideally we'd add a check to ensure that this is the case (seqkit?), or if possible, use something like
fastp
to split the files into separte fastq files with uniform flowcell ids?The text was updated successfully, but these errors were encountered: