-
Notifications
You must be signed in to change notification settings - Fork 189
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
[version 3.8.0] Roary crashes at end on perl error message #323
Comments
I also got this problem and just found some relevant discussions in #199 |
I deinstalled and reinstalled, and I don't get the line 98 error message anymore. However, I do notice that after running and producing the 17 files, memory is filling up and perl keeps on running. Only way to stop my 32 Gb RAM + 32 Gb swap te stop filling is to Ctrl-C the program. Very weird. Unfortunately there is no older version on CPAN? Would be good to always leave one previous version on CPAN for testing purposes :) |
Hi @dutchscientist CPAN had a space issue and asked module authors do a spring clean. They said theres lots of mirrors which archive all historic versions so theres no need for them to also do it. I'll keep the last 2 versions from now on. Thats quite a massive pan genome. You might have insufficient RAM. Another possiblity is with the files themselves. If one is moved, temporarily unavailable (network disk down) or renamed while roary is running it will throw that error. Andrew |
Thanks, Andrew. It worked fine with 3.7.0, so size should not be the issue?
…Sent from my BlackBerry
From: notifications@github.com
Sent: 18 April 2017 4:47 p.m.
To: Roary@noreply.github.com
Reply to: reply@reply.github.com
Cc: dutchscientist@gmail.com; mention@noreply.github.com
Subject: Re: [sanger-pathogens/Roary] [version 3.8.0] Roary crashes at end on perl error message (#323)
Hi @dutchscientist<https://github.com/dutchscientist>
You can ignore the warning:
"Use of uninitialized value in require at /usr/lib/perl/5.18/Encode.pm line 60."
CPAN had a space issue and asked module authors do a spring clean. They said theres lots of mirrors which archive all historic versions so theres no need for them to also do it. I'll keep the last 2 versions from now on.
Thats quite a massive pan genome. You might have insufficient RAM. Another possiblity is with the files themselves. If one is moved, temporarily unavailable (network disk down) or renamed while roary is running it will throw that error.
Andrew
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#323 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AJ8e0Nr8LOo1RDy3y1eUKJTaS8u4ie47ks5rxNsigaJpZM4M-nfM>.
|
So the only coding difference between 3.7.0 and 3.8.0 is a single line removing this parameter from the makeblastdb command: In the latest version of blast the functionality of this parameter changed triggering a remote lookup at NCBI (which is silly really). This slowed down roary and introduced the requirement for a live internet connection. So it was removed. What version of blast are you running? |
My Biolinux8 still runs v2.2.28. Should that make a difference? |
Just updated to v. 3.8.0, and at the end of the run, it suddenly keeps on repeating the following message:
"Use of uninitialized value $filename in hash element at /usr/local/share/perl/5.18.2/Bio/Roary/GroupStatistics.pm line 98."
It is fairly late in the run, i.e. after the Blast comparisons.
(for info: it is a 5829 genome comparison, 100000 groups, both with 90% and 70% cut-off, paralog clustering disabled)
I also get an earlier Perl error message, after extraction of the proteins and before combining them in a single file:
"Use of uninitialized value in require at /usr/lib/perl/5.18/Encode.pm line 60."
That does not stop Roary working.
The text was updated successfully, but these errors were encountered: