-
Notifications
You must be signed in to change notification settings - Fork 14
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
multiple threads? #12
Comments
Hi there, The run time is mainly down to the nucmer alignment process unfortunately |
Thank you for the help. I made an attempt on the same mammal genomes I originally tried. By the way, those ran to completion. took about 30 hours. Here is the output from the new run. The command was the same except for the addition of the -t option. Nucmer alignment of genomes, filtering and converting to coordinates My what a large genome you have, this may take some time USAGE: nucmer [options] Try '/home/daray/conda/bin/nucmer -h' for more information. USAGE: nucmer [options] Try '/home/daray/conda/bin/nucmer -h' for more information. Could this be a mummer version issue? I notice that this is for MUMmer4 and the version that ran successfully was v3.23. In anticipation of this problem, I installed MUMmer4 using conda, 'conda install mummer4' . $ conda list packages in environment at /home/daray/conda/envs/mumco4:Name Version Build Channel_libgcc_mutex 0.1 main It looks to me like mummer4 is installed properly. Any ideas? Thank you again. --EDIT-- I just took a look at nucmer and, indeed, there is no -t option when looking at the help file. Not sure if this makes a difference but.... |
Well its nice to know it did finish within a 'reasonable' amount of time! It seems based on your version output that it is still running MUMmer3 In the MUM&Co script the way it finds the nucmer aligner is through 'which nucmer' (and the other MUMmer tools respectively on lines 9-11) Or alternatively, build and install MUMmer4 as from the github (with 'sudo make install' at the end) |
That seems to be doing the trick. It's running. I'll see if it finishes successfully. Regardless, thanks for being so responsive. |
Yep. That works and is a vast improvement. I ran a test using the same two genomes. V1 used 36 processors. V2 used only one. V1 finished in ~20 minutes. V2 is still running after 35 minutes. I expect it will take 20-30 hours based on the earlier run. So, you might want to put this in the final version. It works. Thanks for the help. |
Thanks for giving me the results. It makes a hell of a difference Looks like i'll be adding this option permanently soon and mentioning that MUMmer4 will then be a requirement |
Reopening this thread if that's ok. I've come back to this after a while and have found there's a new version based on what we discussed above. Unfortunately, this new version isn't working for me. I'm getting some very strange errors that I have no idea how to deal with. These new errors seem to stem from this issue that comes up four times during a run of the test data. g++: error: /opt/ohpc/pub/compiler/gcc/5.4.0/lib/../lib64/libstdc++.so: No such file or directory I've done some troubleshooting and I think I've narrowed it down to these lines:
There are four $SHOWCOORDS commands. Any idea what might be going on here? |
Trying this out for a project. Seems to be running fine on two mammal genomes but it's taking quite a while to run.
Can this package be run on multiple processors to speed things up?
Thanks.
The text was updated successfully, but these errors were encountered: