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

Continuous "core dumped" errors during the M step #117

Open
KANGseungseok opened this issue Mar 14, 2023 · 2 comments
Open

Continuous "core dumped" errors during the M step #117

KANGseungseok opened this issue Mar 14, 2023 · 2 comments

Comments

@KANGseungseok
Copy link

Hello,
I am a student who wants to perform somatic variant calling using CaVEMan.

I am experiencing continuous "core dumped" errors during the M step. While most areas are unaffected, I always encounter a segmentation fault (core dumped) at specific CHR and POS locations for the sample. Even when I retry only those specific locations, the same problem occurs. (I will attach a screenshot of the log file).

If there are any solutions or ways to adjust the memory for this problem, I would appreciate your help.
Thank you very much.

Error_log_image

@davidrajones
Copy link
Contributor

davidrajones commented Apr 24, 2023

Hi there,

The error at the bottom suggests CaVEMan can't see a covariate output file it is expecting to see. How are you running CaVEMan? In the same directory each time? However this may be from the merge step trying to run even though previous M steps have failed.

It looks like you're setting -a 100 in the mstep. This is exceptionally low. What's the coverage at the locations you're seeing issues with? samtools view -c <path/to/bam> <region>

@Ajburdett
Copy link

Closing issue due to lack of response

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

3 participants