Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pileup variant process stuck on specific chunks #224

Open
antoniognmk opened this issue Oct 11, 2024 · 0 comments
Open

Pileup variant process stuck on specific chunks #224

antoniognmk opened this issue Oct 11, 2024 · 0 comments

Comments

@antoniognmk
Copy link

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant