-
Notifications
You must be signed in to change notification settings - Fork 7
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
mop_mod running time #33
Comments
|
params.config.test file:
conf/local.config file:
|
Dear @aset8, I see that you are modifying the config... since your machine has no job scheduling system I would use the local config. But I won't use 110 CPUs because you need to parallelize several executions. https://github.com/biocorecrg/MOP2/blob/main/conf/sge.config Let me know how it goes. Luca |
@aset8 Not sure, if this issue got resolved. But one thing that can mysteriously terminate the MOP2 jobs being run are memory watchdogs being run on shared computing resources. These would terminate the jobs with no information being logged to nextflow logs. I would try running with less CPUs and ~30 to ~60 GB of memory. Also, try running with Epinano only or tombo only to narrow down the list of suspects. |
Yes with MoP2 you can just use one workflow at time, so you can narrow down the more intensive processes. Let me know how it goes. |
I have a similar msg when running on a high performance center by SLURM job (372 G memory and 56 cores):
How do I continue? |
which profile are you using? |
Hi, Are these profiles profiles you mentioned? tools_opt.tsv:
params.config:
|
@AndreaYCT No, there are config files in conf subdirectory, like slurm.config local.config and so on. |
Salutations,
First of all, thank you very much for your great and important work.
I have a few questions. I am running Master of Pores 2 on a workstation from Nanopore Promethion (370 gb ram, 112 cores). The first stage, mop_preprocess.nf finished pretty quickly. What cannot be said about the second stage - mop_mod.nf.
The stage of searching for modifications (mop_mod.nf) has been going on for almost 24 hours, no signs of work are visible. Htop shows no load on the server.
I tried it with -profile standard and -profile local. No change.
Could you please advise how to properly configure the configurations to get the work done as quickly as possible?
There are a few more questions about using references (genome, transcriptome) and running Master of Pores 2 on another machine. I will open another discussion. Thanks.
The text was updated successfully, but these errors were encountered: