Closed jwidmann closed 8 years ago
Looking into this further. I think this shows up if LAST is compiled without openmp; I'll be switching over to the gnu-parallel version described in the docs soon (http://last.cbrc.jp/doc/last-parallel.html). In the meantime, yes, you should be able to continue by running that task manually, or, by running with n_threads = 1, canceling, and running again with however many threads you please.
Thanks for your reply. When I try running with n_threads=1 it just gives me directly the same output as before - do I have to delete a log file or something like that? Running lastal manually also doesn't work (also directly the error output). Any suggestions?
DAMMIT - Same problem here. Installed all dependencies, followed by dammit itself - all appropriately in PATH, and then ran >dammit dependencies and all is in order except LAST: lastal: invalid option -- '-' lastal: bad option ...... [ ] LAST... [1] [x] crb-blast
--- Dependency results
LAST missing
Also tried LAST-737 which compiled with -std=c++11, which apparently is needed for multithreading. Still no cookie.
Any help would be appreciated. Look forward to testing you pipeline. Thanks for making it available
This has now been fixed in v0.2.9. @Victaphanta , I believe your issue is something else, so I'll make a new issue for it.
There seems to be a problem with invalid options for lastal. I have installed last-658 and last-731. Maybe some options have changed. Will dammit take up after this step if i do this by hand?
Best wishes