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
Hello, I am currently testing the wf-human-variation Nextflow pipeline on AWS Batch. I aligned a human sample with mean depth coverage 29X with wf-alignment workflow, and it worked well.
Anyway, during my first try with wf-human-variation, using the [email protected] for the override_basecaller_cfg parameter, the snp:pileup_variants step triggered 632 processes, one for each chunk. The majority of chunks were processed within minutes. However, chunks 26, 29, 497, and 498 ran for over 24 hours and did not finish. Therefore, I canceled the execution.
The next day, thinking that perhaps I had chosen the wrong model, I tried again, this time with [email protected]. To my surprise, the same chunks got stuck again.
I am trying to execute the workflow with all variant call options active (sv, cnv, str, mod, snp). All other parameters are with their default values (except bam_min_coverage, which I am using 15).
Does anybody have any insights on the matter? Thanks for your attention.
Relevant log output
Unfortunately, I could not retrieve the logs because I canceled the execution and AWS CloudWatch did not produce the Nextflow engine.log.
Application activity log entry
No response
Were you able to successfully run the latest version of the workflow with the demo data?
yes
Other demo data information
No response
The text was updated successfully, but these errors were encountered:
Operating System
Other Linux (please specify below)
Other Linux
Amazon Linux on AWS Batch
Workflow Version
v2.4.1
Workflow Execution
Command line (Cluster)
Other workflow execution
No response
EPI2ME Version
No response
CLI command run
No response
Workflow Execution - CLI Execution Profile
None
What happened?
Hello, I am currently testing the wf-human-variation Nextflow pipeline on AWS Batch. I aligned a human sample with mean depth coverage 29X with wf-alignment workflow, and it worked well.
Anyway, during my first try with wf-human-variation, using the [email protected] for the override_basecaller_cfg parameter, the snp:pileup_variants step triggered 632 processes, one for each chunk. The majority of chunks were processed within minutes. However, chunks 26, 29, 497, and 498 ran for over 24 hours and did not finish. Therefore, I canceled the execution.
The next day, thinking that perhaps I had chosen the wrong model, I tried again, this time with [email protected]. To my surprise, the same chunks got stuck again.
I am trying to execute the workflow with all variant call options active (sv, cnv, str, mod, snp). All other parameters are with their default values (except bam_min_coverage, which I am using 15).
Does anybody have any insights on the matter? Thanks for your attention.
Relevant log output
Application activity log entry
No response
Were you able to successfully run the latest version of the workflow with the demo data?
yes
Other demo data information
No response
The text was updated successfully, but these errors were encountered: