Closed GoogleCodeExporter closed 9 years ago
Hi,
The binaries that we distribute with InterProScan should work on most linux
systems. However, in some cases they may not work on a particular system. So
the first thing to try is to get/compile your own version of the binary and
update the relevant interproscan.properties to point at the new location.
Instructions on how to recompile blastall on your own system are given here:
https://code.google.com/p/interproscan/wiki/CompilingBinaries
Note that we use 2 different versions of blastall, but it looks like version
2.2.6 was giving you your error.
https://code.google.com/p/interproscan/wiki/FAQ#7.Why_does_InterProScan_5_use_bl
astall_2.2.6_and_2.2.19?
If this doesn't solve the problem then just let us know!
Thanks,
Matthew
Original comment by Mr.Matth...@gmail.com
on 2 Jun 2014 at 2:20
Original comment by Maxim.Sc...@gmail.com
on 16 Jul 2014 at 1:49
Hi there, has this problem been solved? I have encountered exactly the same
problem using the same version of InterProScan, InterProScan-5.4-47.0.
As for the command, bin/blast/2.2.6/blastall -p blastp -F F -e 0.0005 -b 300 -v
300 -m 8 -a 4 -d /home/macmanes/interproscan-5.4-47.0/data/pirsf/2.84/sf.seq -i
/home/macmanes/interproscan-5.4-47.0/temp/davinci_20140601_070135568_9iu4//jobPI
RSF-2.84
/000000000101_000000000150.blastInputFile.fasta
By simply replace blastall-2.2.6 with blastall-2.2.19, it completes
successfully. Is there another way around the problem other than recompiling
blastall from source, please?
Thanks,
Zhuyi
Original comment by alfred53...@gmail.com
on 1 Oct 2014 at 11:09
Hi Zhuyi,
Thank you for the message! Although the compiled binaries we distribute should
work on most Linux systems, they won't necessarily work on all.
I can confirm that the wiki documentation is all up-to-date in this area, FAQ
items #3 and #7 still contain the latest advice on what you can try to get
blastall 2.2.6 working. So other than recompiling, I don't know if you saw
here...
https://code.google.com/p/interproscan/wiki/FAQ#3.What_should_I_do_if_one_of_the
_binaries_included_with_InterProScan_5_doesn%27t_work_on_my_system?
Hope that helps you get blastall 2.2.6 working!
Regards,
Matt
InterPro team
Original comment by Mr.Matth...@gmail.com
on 2 Oct 2014 at 2:03
Hi Matt,
Thank you for your quick reply. I would like to add another bit of information.
The sequence I have used to get the error is FLT3, which is of length 993. But
if it is truncated into half, the error will be gone, which makes it seem to be
related to the length of the sequence. It's wired, but that's what I have
found. Similarly, for another two sequences I have tested, which are of lengths
of 326 and 239, respectively. InterProScan also works. Do you have any comment
on how this could be the case?
Regards,
Zhuyi
Original comment by alfred53...@gmail.com
on 2 Oct 2014 at 3:21
Hi Matt,
I wonder where the blastall-2.2.19 that comes with InterProScan is from?
I downloaded 2.2.19 from ftp://ftp.ncbi.nlm.nih.gov/blast/executables/release/,
and surprisingly, the same problem persists, but it does not with the
blastall-2.2.19 that came from InterProScan.
Regards,
Zhuyi
Original comment by alfred53...@gmail.com
on 2 Oct 2014 at 4:45
Hi Matt,
I tried to avoid compiling from source as much as possible since debugging
compilation errors is very time consuming, especially for the ncbi tool kit
with blastall-2.2.6, which was released in 2003 and old.
After some experimentation, I have collected more information about the problem.
On Machine 1 with uname -a of
Linux <HOSTNAME> 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
blast-2.2.19-ia32-linux.tar.gz doesn't work
blast-2.2.19-x64-linux.tar.gz works
blast-2.2.6-ia32-linux.tar.gz doesn't work
There is no blast-2.2.6-x64-linux compiled on
ftp://ftp.ncbi.nlm.nih.gov/blast/executables/release/2.2.6/
For Machine 2 with uname -a of
Linux <HOSTNAME> 2.6.18-371.1.2.el5 #1 SMP Tue Oct 22 12:51:53 EDT 2013 x86_64
GNU/Linux
the blast-2.2.6 that comes with InterProScan just works.
Seemly, the error has something to do with the CPU architectures, but I don't
have the knowledge to explain why this is the case. If you know why, please let
me know. To me, the two machines don't have much difference since they're both
of x86_64, but the same blastall works on one but not the other.
Regards,
Zhuyi
Original comment by alfred53...@gmail.com
on 2 Oct 2014 at 5:08
Hi Zhuyi,
As you saw there is no blast-2.2.6-x64-linux compiled on the FTP site, that is
why the 64-bit InterProScan 5 distribution contains a 32 bit binary as it is
all we have available. As the InterProScan wiki mentions, one option to enable
32-bit binaries to run on 64-bit Ubuntu (if you have that) is...
sudo apt-get install ia32-libs-multiarch
...or...
sudo apt-get install ia32-libs
Not all binaries work on every linux distribution. Sorry, I can't really
comment on the blastall source code, it's not something we look into changing
or anything as that's a bit beyond the scope of InterProScan 5 - we tend to
just use the standard binaries in the same way the member database analysis
does, to ensure we get the same results.
You could use blastall-2.2.19 in place of 2.2.6. It may work fine, but there is
a small chance it may slightly affect your PIRSF 2.84 and Panther 9.0 results.
This test would be interesting to add to our todo list, but I can't comment
further at this stage...
So generally recompiling from source on your own system is the recommended
option, but the two options above should also work!
Thanks,
Matt
Original comment by Mr.Matth...@gmail.com
on 6 Oct 2014 at 2:24
Original issue reported on code.google.com by
macma...@gmail.com
on 1 Jun 2014 at 1:12