-
Notifications
You must be signed in to change notification settings - Fork 48
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
igblastn and igblastp return an error #65
Comments
Hi, have you also set the $IGDATA environment variable as described in issue #48? Thanks, Mike |
Oh sorry. Just seen that you did! I’ll look into this tomorrow. |
Quick update: |
If you have the full Could it be something to do with the fact that PS - running Let me know how you get on... |
I did just change the IGDATA to what you suggested, but it did not help. After the change, I did run the application and got the following error.
|
Please can you send me the output of the following commands:
Thanks, Mike |
It's not pretty because of formatting but here you go:
[root@pyrite ~]# ls /tools/GNU/igblast/1.8.0
bin include internal_data internal_data_BACK lib optional_file
[root@pyrite ~]# ls /tools/GNU/igblast/1.8.0/bin
blastdb_aliastool blast_formatter convert2blastmask gc_cli
igblastp makembindex rpsblast seqdb_demo tblastn
vdb_test
blastdbcheck blastn csra_test_mt gene_info_reader
internal_data makeprofiledb rpstblastn seqdb_perf tblastx
wgs_test
blastdbcmd blastp datatool graph_test
legacy_blast.pl project_tree_builder run_with_lock snp_test test_pcre
blastdbcp blastx deltablast igblastn
makeblastdb psiblast seedtop sra_test
update_blastdb.pl
[root@pyrite ~]# ls /tools/GNU/igblast/1.8.0/bin/internal_data
human mouse rabbit rat rhesus_monkey
…On Thu, Mar 22, 2018 at 6:35 AM Mike Stubbington ***@***.***> wrote:
Please can you send me the output of the following commands:
ls /tools/GNU/igblast/1.8.0
ls /tools/GNU/igblast/1.8.0/bin
ls /tools/GNU/igblast/1.8.0/bin/internal_data
Thanks,
Mike
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#65 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AZqh1P2ZjA_O1N7hqS38kmepvC606aIKks5tg6iEgaJpZM4Spk8u>
.
|
Thanks. Please can you send me the path where you've installed Tracer and also the config file that you're using. |
Hi Mike,
Here's the path for Tracer: /tools/GNU/python/2.7.13/bin/tracer
I don't know what you mean by the config file. I'm an admin that installs
and fixes the applications our scientists use, so I'm not too familiar with
how these applications run or what is required to make them run.
…On Fri, Mar 23, 2018 at 4:25 AM Mike Stubbington ***@***.***> wrote:
Thanks. Please can you send me the path where you've installed Tracer and
also the config file that you're using.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#65 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AZqh1HaYl50dW9fycFpznMDgrvk4Ebwjks5thNuygaJpZM4Spk8u>
.
|
Thanks for this. The config file details some settings for TraCeR and is described here: https://github.com/teichlab/tracer#setup. It's found as follows:
|
Hey, sorry to butt in, but does your server support Docker by any chance? |
@mike
I will check with the researcher if they are running any special config
files. I was not able to find any in the Tracer base install directory
located in site-packages of Python 2.7.13.
@krzysztof,
We can support Docker but due to the nature of the applications and
research, it would be a short term solution. We have a CPU and GPU cluster
that we use for processing big data, and in our experiments, Docker wasn't
able to hold up in those environments. I know that NVIDIA came out with
their own Docker support but we haven't had much success with it yet.
…On Fri, Mar 23, 2018 at 9:01 AM Krzysztof Polanski ***@***.***> wrote:
Hey, sorry to butt in, but does your server support Docker by any chance?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#65 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AZqh1ASgQcDyEHijqzDCkjhT5z_4kfaKks5thRxjgaJpZM4Spk8u>
.
|
Unfortunately the researcher wasn't able to provide a config file or -c
string as she was using igblastn as the application and not Tracer. I did
check the users home dir and there is no .tracerrc file in their profile.
There are also no TRACER_CONF variable set in the environment when loading
the application.
On Fri, Mar 23, 2018 at 9:13 AM Aleksey Galipchak <[email protected]>
wrote:
… @mike
I will check with the researcher if they are running any special config
files. I was not able to find any in the Tracer base install directory
located in site-packages of Python 2.7.13.
@krzysztof,
We can support Docker but due to the nature of the applications and
research, it would be a short term solution. We have a CPU and GPU cluster
that we use for processing big data, and in our experiments, Docker wasn't
able to hold up in those environments. I know that NVIDIA came out with
their own Docker support but we haven't had much success with it yet.
On Fri, Mar 23, 2018 at 9:01 AM Krzysztof Polanski <
***@***.***> wrote:
> Hey, sorry to butt in, but does your server support Docker by any chance?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#65 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AZqh1ASgQcDyEHijqzDCkjhT5z_4kfaKks5thRxjgaJpZM4Spk8u>
> .
>
|
Hi,
I'm having an issue running igblastn. Every time I do, I get an error saying an annotation database in internal_data could not be found.
I did follow the installation instructions.
igblast is installed in "/tools/GNU/igblast/1.8.0"
PATH is set to "/tools/GNU/igblast/1.8.0/bin"
LD_LIBRARY_PATH is set to "/tools/GNU/igblast/1.8.0/lib"
$IGDATA is set to "/tools/GNU/igblast/1.8.0/bin"
I did download the internal_data folder from ticket 48 and placed the whole internal_data folder in the /bin directory as instructed.
The error is still there.
Fully copy of the error is as follows:
The text was updated successfully, but these errors were encountered: