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
Using only information contained in a fqstats file it is currently impossible to distinguish between processing pair.1, pair.2 and singles using pairing information paired(..., singles=...) versus treating each file independently fastq(...).
Adding file grouping information could alleviate this issue. Example:
A similar situation is seen when using load_mocat_sample(...) on a folder that includes multiple pairs/lanes. Here, a variable number of inputs makes parsing the stats file non-trivial.
In this case, and related to #55 (comment) we could treat all the inputs of a sample as the same filegroup.
Using only information contained in a fqstats file it is currently impossible to distinguish between processing
pair.1
,pair.2
andsingles
using pairing informationpaired(..., singles=...)
versus treating each file independentlyfastq(...)
.Adding file grouping information could alleviate this issue. Example:
A similar situation is seen when using
load_mocat_sample(...)
on a folder that includes multiple pairs/lanes. Here, a variable number of inputs makes parsing the stats file non-trivial.In this case, and related to #55 (comment) we could treat all the inputs of a sample as the same filegroup.
The text was updated successfully, but these errors were encountered: