In the genotype matching step, I noticed my dataset had reversed column ordering compared to what the pipeline expected. The pipeline expects freemuxlet clusters will exist in the 2nd column and sample ids will exist in the 3rd column of gtcheck.out files, but for me the sample ids were in column 2 and the freemuxlet clusters were in column 3. Thinking there's inherent inconsistency, this PR adds an attempt to use the opposite ordering if the initial expectation yields 0 rows.
In the genotype matching step, I noticed my dataset had reversed column ordering compared to what the pipeline expected. The pipeline expects freemuxlet clusters will exist in the 2nd column and sample ids will exist in the 3rd column of gtcheck.out files, but for me the sample ids were in column 2 and the freemuxlet clusters were in column 3. Thinking there's inherent inconsistency, this PR adds an attempt to use the opposite ordering if the initial expectation yields 0 rows.
Note: Only touches the "1.18" version of the code