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
when (a certain number of?) underscores are used in sample column, sometimes only a substring of the entire value is read in, rather than the whole value.
E.g. BATCH_DATE_SAMPLE is read in as BATCH_DATE in the following example. The impact is that when the read-in partial value is not unique , the pipeline will erroneously treat multiple (unique) rows as replicates.
See screenshots of an example samplesheet and running pipeline for example
Command used and terminal output
No response
Relevant files
No response
System information
version methylseq 2.6.0 No response
The text was updated successfully, but these errors were encountered:
I'm so happy I found this issue, was pulling my hair the whole day thinking my code was wrong. Quickfix: changed the underscore to a dot in my samplesheet.csv (F0_1 -> F0.1)
I've encountered the same issue that the sample name inputs were uncompleted causing later errors. My sequencing was paired-end with 4 lane per sample, so may also have the problem mentioned in #381 . Could anyone provide an updated workable samplesheet.csv example? Really confused now.
Description of the bug
when (a certain number of?) underscores are used in sample column, sometimes only a substring of the entire value is read in, rather than the whole value.
E.g. BATCH_DATE_SAMPLE is read in as BATCH_DATE in the following example. The impact is that when the read-in partial value is not unique , the pipeline will erroneously treat multiple (unique) rows as replicates.
See screenshots of an example samplesheet and running pipeline for example
Command used and terminal output
No response
Relevant files
No response
System information
version methylseq 2.6.0
No response
The text was updated successfully, but these errors were encountered: