-
Notifications
You must be signed in to change notification settings - Fork 8
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
error at step5 #6
Comments
Hi Michel, You're right, the pax_k200.first.frags.dist.png.FAIL file is nothing to do with the error. It looks like it might be something to do with your data. Could you send me your read files so we can try to replicate the error and let me know which version of w2rap you are running? There should be a git commit flag in the log file. Thanks, |
It could also be a out-of-memory error as step 5 is the other memory intensive step. Are you able to increase the memory for this step or sub-sample your reads and run again from step 1? |
your right, might be another memory-issue. an assembly with 1/5 of the data ran without problems. |
Memory requirements are difficult to estimate as they will depend on the quality of your sequencing and the heterozygosity of your genome. We usually plot a kmer frequency distribution from the reads before assembly to check this - see https://github.com/bioinfologics/w2rap/ |
Hi Michel, Jon " Fatal error (pid=5865) at Fri Sep 21 00:38:25 2018: It show the peak men usage =222.07GB Thank you |
Hi @jonwright99 I get the same error at stage 5:
And my node has 500gb of RAM. Any suggestions? |
Can you post the command line you are using to start the contigger please? There is a soft memory limit parameter that you might not be including (-m) which defaults to 10Tb. |
Yes I didn't use -m. If I use -m will it solve the problem? In a node with 500GB, what do I have to use in -m? -m 500GB ?? |
It's a soft limit so I usually set it to 4/5ths of available memory which in your case will be 400. You could try setting this. It definitely looks like a memory issue, the log for the previous part is using 333Gb so it may well be requiring more than 500Gb. You could also try reducing the number of reads you use as input. If this is a memory issue, there's no way around it, you'll need more memory to assemble the coverage you have. |
Dear Jon,
I reached step5 but get a core dump.
Sterr:
By looking at stout, it is unclear to me if some parameter setting might resolve the problem.
Stout:
Additionally, when looking into the assembly-folder, i got an
pax_k200.first.frags.dist.png.FAIL
-file telling me some execs are missing on the cluster i run w2rap:But i assume this would not cause the assembly to terminate, right?
Could you help me to get arround this error?
Thank you,
Michel
The text was updated successfully, but these errors were encountered: