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
I encountered this issue running a WGS sample with multiple FASTQs. The run failed due to a memory issue in align-DNA. Not sure if we could customize this, so I changed the setting in the align-DNA by reducing the 56 CPUs to 36:
withName: align_DNA_BWA_MEM2 {
cpus = 36
}
@yashpatel6 Is there a way to customize this in the config file?
The text was updated successfully, but these errors were encountered:
Generally, the metapipeline doesn't directly set any resource allocations for the individual pipelines; if there is a memory error showing up with one of the pipelines, it should really be addressed in that pipeline (probably with some sort of retry mechanism)
I encountered this issue running a WGS sample with multiple FASTQs. The run failed due to a memory issue in
align-DNA
. Not sure if we could customize this, so I changed the setting in the align-DNA by reducing the 56 CPUs to 36:@yashpatel6 Is there a way to customize this in the
config
file?The text was updated successfully, but these errors were encountered: