-
Notifications
You must be signed in to change notification settings - Fork 135
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
instabilty in head #11
Comments
First thank you for using our software. I would conduct several tests before commit changes to the master branch. I did not encountered any problem on my CentOS server and MacBook 2013. I think in most case it works well. But I am sorry that it is not an easy job for me to test MEGAHIT across many platforms and data. Would you please let me know what problem did you encounter by using the head? Compilation error, or run time error? It's better if you could send me some log files. If MEGAHIT ran well a few weeks ago in your environment, please download and use v0.1.2 from the release page before I fix the problem. |
I apologize, I did not see the releases page, I just followed the directions on the Github homepage. The releases page provides me with what I need. Thanks for pointing that out. Here is an example error message, that I was consistently getting. I was using commit deab846 [ERROR] Found a read of length 271 > max read length = 270 To me, it doesn't seem to be an issue with reads being longer than the max read length, since I have assemblies that have completed using reads that are longer than the specified max read length. I have switched to using release 0.1.2 and no longer have this problem. |
Are you using a 32-bit system? I've replace all |
I work for the US DOE Joint Genome Institute, where we assemble 100's of metagenomes and metatranscriptomes. One of our analysts checked out the repo, from head, a few weeks ago, and had no problems running MEGAHIT. Since then myself, and other analysts have checked out from head, and we have had problems running MEGAHIT. Would it be possible to tag a stable revision, or provide a stable build as a download? We would really like to use MEGAHIT for our assemblies, but are concerned about the stability of the master branch.
The text was updated successfully, but these errors were encountered: