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
These two steps eat up lots of disk costs:
sequenceToFastq: 0.139237127 local-disk 552 SSD (two of those)
trimFastq: 0.792021773 local-disk 1148 SSD (two of those)
sequenceToFastq runs even when fastqs are given, and makes a copy - this is wasteful. Can we set conditional execution of that step (does WDL support that?)
trimfastq could probably by piped directly into bwa, sacrificing some composability for speed. There is already optional adapter trimming in sequence_align_and_tag.wdl. Seems like we could add other trimming there as well (or in the HISAT or STAR steps for RNA)
The text was updated successfully, but these errors were encountered:
Boolean flag # some flag for existence or non-existence
if ( flag ) {
call some_task { ... }
}
edit: it seems that the conditional if-block does not have their ✨ symbol (which is used to indicate a new feature) next to it. Maybe it is actually in version 1.0 as well...
These two steps eat up lots of disk costs:
sequenceToFastq: 0.139237127 local-disk 552 SSD (two of those)
trimFastq: 0.792021773 local-disk 1148 SSD (two of those)
sequenceToFastq runs even when fastqs are given, and makes a copy - this is wasteful. Can we set conditional execution of that step (does WDL support that?)
trimfastq could probably by piped directly into bwa, sacrificing some composability for speed. There is already optional adapter trimming in
sequence_align_and_tag.wdl
. Seems like we could add other trimming there as well (or in the HISAT or STAR steps for RNA)The text was updated successfully, but these errors were encountered: