Hi Alex,
star-2.7.9a
It appears that --readFilesManifest does not like a mix of single and paired reads. If I run using a manifest of all of one type it works fine. Below is what my manifest looks like that does not work. Is this by design that it only takes one read type? If so, is it possible to make this work for a manifest of intermixed paired and unpaired reads?
The use case is for data that comes out of read trimming (trimmomatic in this case) where one read was removed due to quality etc. and three files are written for each input paired set of files (Paired, F only, R only). I believe it would be beneficial to have all of these run together since I'm doing --twopassMode Basic, am I mistaken?
Hi Alex,
star-2.7.9a
It appears that--readFilesManifest
does not like a mix of single and paired reads. If I run using a manifest of all of one type it works fine. Below is what my manifest looks like that does not work. Is this by design that it only takes one read type? If so, is it possible to make this work for a manifest of intermixed paired and unpaired reads?The use case is for data that comes out of read trimming (trimmomatic in this case) where one read was removed due to quality etc. and three files are written for each input paired set of files (Paired, F only, R only). I believe it would be beneficial to have all of these run together since I'm doing
--twopassMode Basic
, am I mistaken?Thanks Bob