Skip to content
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, FileOpenForReadingFailure() entered with 4 != 5 input arguments #2

Open
473021677 opened this issue Jun 19, 2020 · 2 comments
Open

Comments

@473021677
Copy link

Hello:
I am using ssu-align to identify prokaryotic SSU rRNA sequences in my sequences and align them using CMs to create domain-specific SSU multiple sequence alignments. But the program terminated abnormally and reported the error "ERROR, FileOpenForReadingFailure() entered with 4 != 5 input arguments.". I don't know now to solve it and need your help. I have appended the log files. Thanks!

Best regards,
Yang Yuan
SSU-align.ssu-align.log

@nawrockie
Copy link
Member

Thanks for your bug report.

This problem has been fixed in the development code but not yet included in a new release.

To fix this problem in your local copy, follow these steps:

  1. Download the 'ssu.pm' file from the develop branch of the git repo, located here:
   https://raw.githubusercontent.com/EddyRivasLab/ssu-align/develop/trunk/src/ssu.pm

One way you can download it on the command line is:

   $ curl -o ssu.pm https://raw.githubusercontent.com/EddyRivasLab/ssu-align/develop/trunk/src/ssu.pm
  1. Copy the ssu.pm file to the directory where you installed ssu-align, replacing the existing ssu.pm file there:
$ echo $SSUALIGNDIR

(this should return the path to where you installed ssu-align, if not, let me know)

$ cp /PATH/TO/NEW/ssu.pm $SSUALIGNDIR

Replace 'PATH/TO/NEW/' with the path to the 'ssu.pm' you downloaded in step 1.

Once you do that and rerun then you shouldn't see the error anymore. But please let me know either way if this does or doesn't fix your problem.

@473021677
Copy link
Author

Thanks for your help very much. The problem has been fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants