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
Aida mentioned that the default behavior of always collapsing libraries within a single sample for input into genotyping may be inappropriate when mutliple libs have different UDG treatment status/damage models, etc.
Modifying necessary for the input channel generation for genotyping to be able to either get unmerged or merged data.
Unmerged data also necessitates changes to the prefix and tags for all processess where previously only unique sampleIDs would be sufficient.
The text was updated successfully, but these errors were encountered:
@aidaanva@ilight1542
Was looking through the PR for the second time, when I realised I am not entirely sold on the idea. Sorry if this is not the first time you have to explain it (it could be my lack of coffee atm), but I did not see this discussion documented anywhere:
Is this added complexity actually needed?
How would this be different from the user tweaking their TSV file to give each library a different Sample_ID? Unless the genotypes from each library get merged to a sample level eventually? But aren't we then back to square one?
Aida mentioned that the default behavior of always collapsing libraries within a single sample for input into genotyping may be inappropriate when mutliple libs have different UDG treatment status/damage models, etc.
Modifying necessary for the input channel generation for genotyping to be able to either get unmerged or merged data.
Unmerged data also necessitates changes to the prefix and tags for all processess where previously only unique sampleIDs would be sufficient.
The text was updated successfully, but these errors were encountered: