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

Methylation extractor stuck #644

Open
xbarvazx opened this issue Dec 20, 2023 · 4 comments
Open

Methylation extractor stuck #644

xbarvazx opened this issue Dec 20, 2023 · 4 comments

Comments

@xbarvazx
Copy link

xbarvazx commented Dec 20, 2023

Hi,

I am running methylation_extractor and the process gets stuck. I have run this successfully in the past.
the output error last lines are:

Processed lines: 554500000
Finished processing child process. Exiting..

I tried it a few times and its always stuck at this part while the job seems to continue running for days.

bismark_methylation_extractor --multicore 25 --no_overlap --gzip --bedGraph --comprehensive --no_header --buffer_size 100G -o bismark_result2 raw.deduplicated.bam > bismark_extract.log 2> bismark_extract.err &

Thanks,
Raz

@FelixKrueger
Copy link
Owner

hmm, is it sill doing something? Can you run top to see? Has it progressed to the bedGraph conversion step yet, or is it stuck at the extraction stage? You should be able to see a single splitting report and M-bias file in the folder if the extraction is complete. Is there anything informative in the STDOUT log?

The only thing that looks a little dodgy to me is the high number of --multicore ....

@xbarvazx
Copy link
Author

Hi Felix,

No its stuck at the extraction stage. The log file is empty.
--multicore is the available cores right? I have a whole node allocated with 80 cores. I could actually increase it if it might help?

@FelixKrueger
Copy link
Owner

If anything I would probably try to bring it down to point where you are happy that it is alll still working as expected... maybe --parallel 8?

@xbarvazx
Copy link
Author

Hi Felix,

it worked with --parallel 8 instead or --multicore 25
Interesting that it failed now and not with other similar runs I did.

Thanks anyway!
Raz

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