Right now the sample fastq.gz file names are assumed to include a lane specifier (see Task.read_file_product), but when lane splitting is disabled, like for recent MiSeq i100 Plus runs, those won't be present in the names and downstream task processing won't handle the paths correctly. In the near term it can be worked around just by tweaking the allowed patterns, though in the longer term the whole thing should be made less dependent on sample names and file paths (and should center more on sample numbers).
Right now the sample fastq.gz file names are assumed to include a lane specifier (see
Task.read_file_product), but when lane splitting is disabled, like for recent MiSeq i100 Plus runs, those won't be present in the names and downstream task processing won't handle the paths correctly. In the near term it can be worked around just by tweaking the allowed patterns, though in the longer term the whole thing should be made less dependent on sample names and file paths (and should center more on sample numbers).