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

scatter_count > 50 #73

Open
RoniHaas opened this issue Mar 19, 2022 · 5 comments
Open

scatter_count > 50 #73

RoniHaas opened this issue Mar 19, 2022 · 5 comments

Comments

@RoniHaas
Copy link

Hey @yashpatel6 ,
I think I am having memory problems:

Process `multi_sample_wgs:calculate_contamination_tumour:run_GetPileupSummaries_GATK (1)` terminated with an error exit status (247)

How much would you recommend increasing the scatter_count?

@yashpatel6
Copy link
Collaborator

The contamination calculation processes run on the merged BAM so increasing the scatter count won't have any effect. Could you point me to the log file for the job that failed?

@RoniHaas
Copy link
Author

Sure, Thanks for the help!

In this directory the csv, config and log files are found:
/hot/users/rhaas/Input/case_study/gSNP/(*config|*csv|*log)

I used the previous release (it was before you sent the email)

@yashpatel6
Copy link
Collaborator

Got it, thanks!

The release shouldn't affect this part of the pipeline, I'll run some tests and check the problem.

@yashpatel6
Copy link
Collaborator

I tried some test runs and, you're right, it does seem like a memory error. Resolving it would require the memory allocation for that process in the pipeline to be increased.

@RoniHaas
Copy link
Author

I tried some test runs and, you're right, it does seem like a memory error. Resolving it would require the memory allocation for that process in the pipeline to be increased.

Thanks for the update! No problem, I will re-run once the changes in memory allocation are committed.

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

No branches or pull requests

2 participants