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
{{ message }}
This repository has been archived by the owner on Jan 6, 2021. It is now read-only.
this issue is to request ignoring dup reads as an option. gatk best practice is to keep all duplicates in the bam, and i have read from a few issues here and here that a deduplicated (not just marked duplicate) bam is best for msisensor msi. therefore, we have to run an extra step and use almost twice as much storage to run msisensor from a deduplicated bam. ignoring dup reads from marked bam would avoid the trouble while hopefully not adding to the run time of msisensor
The text was updated successfully, but these errors were encountered:
this issue is to request ignoring dup reads as an option. gatk best practice is to keep all duplicates in the bam, and i have read from a few issues here and here that a deduplicated (not just marked duplicate) bam is best for
msisensor msi
. therefore, we have to run an extra step and use almost twice as much storage to runmsisensor
from a deduplicated bam. ignoring dup reads from marked bam would avoid the trouble while hopefully not adding to the run time ofmsisensor
The text was updated successfully, but these errors were encountered: