-
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
Running igblast returns an error #70
Comments
Hi, Thanks for this. This specific crash is happening because of a bug in the way that TraCeR tries to report an error if IgBlast fails. I've just pushed a fix for this to the Very best, Mike |
##Running IgBLAST## Traceback (most recent call last): I got the same errors by using tracer-0.6.0. Have you fixed the bug ? How to solve this problems ? Best |
##Running IgBLAST## BLAST query/options error: Germline annotation database mouse/mouse_TR_V could not be found in [internal_data] directory When I update to the latest commit to and then try running tracer test again - I got the IgBLAST error |
Have you got a working version of IgBlast as per the instructions here? https://github.com/Teichlab/tracer/blob/master/README.md#installing-igblast Make sure you've downloaded the |
Cheers , I solve the problems by run "export IGDATA=/Bailab5/xingxudong/Software/ncbi-igblast-1.10.0/bin" straightly. But somehow It cant be found by the systems. Best |
Hi,
I'm going to testing TraCer by runing
tracer test
.But everytime it returns an error after printing runing IgBlast,fully copy as follows:`##Running IgBLAST##
CMD failed:
Traceback (most recent call last):
File "/share/apps/anaconda3/bin/tracer", line 9, in
load_entry_point('tracer==0.5', 'console_scripts', 'tracer')()
File "/share/apps/anaconda3/lib/python3.5/site-packages/tracer-0.5-py3.5.egg/tracerlib/launcher.py", line 43, in launch
Task().run()
File "/share/apps/anaconda3/lib/python3.5/site-packages/tracer-0.5-py3.5.egg/tracerlib/tasks.py", line 1206, in run
loci=['A', 'B'], max_junc_len=50).run()
File "/share/apps/anaconda3/lib/python3.5/site-packages/tracer-0.5-py3.5.egg/tracerlib/tasks.py", line 371, in run
cell = self.ig_blast()
File "/share/apps/anaconda3/lib/python3.5/site-packages/tracer-0.5-py3.5.egg/tracerlib/tasks.py", line 502, in ig_blast
self.resume_with_existing_files, fmt)
File "/share/apps/anaconda3/lib/python3.5/site-packages/tracer-0.5-py3.5.egg/tracerlib/tracer_func.py", line 1265, in run_IgBlast
print(" ").join(pipes.quote(s) for s in command)
AttributeError: 'NoneType' object has no attribute 'join'
I followed the installation to install igblast,the tree of
igblast/binis as follows:
|-- igblastn|-- igblastp
|-- internal_data
|
-- human | |-- human.ndm.imgt | |-- human.ndm.kabat | |-- human.pdm.imgt | |-- human.pdm.kabat | |-- human_TR_V.nhr | |-- human_TR_V.nin | |-- human_TR_V.nog | |-- human_TR_V.nsd | |-- human_TR_V.nsi | |-- human_TR_V.nsq | |-- human_TR_V.phr | |-- human_TR_V.pin | |-- human_TR_V.pog | |-- human_TR_V.psd | |-- human_TR_V.psi | |-- human_TR_V.psq | |-- human_V.nhr | |-- human_V.nin | |-- human_V.nog | |-- human_V.nsd | |-- human_V.nsi | |-- human_V.nsq | |-- human_V.phr | |-- human_V.pin | |-- human_V.pog | |-- human_V.psd | |-- human_V.psi |
-- human_V.psq-- makeblastdb
And I set $IGDATA to ~/tool/igblast-1.9.0/bin
I got a file under test_data/results/cell1/IgBLAST_output/ named cell1_TCR_A_fmt3.IgBLASTOut,but it's empty,so I tried to run igblast with cell1_TCR_A.Trinity.fasta under test_data/results/cell1/Trinity_output/ by
igblastn -germline_db_V /home/user/tool/tracer-master/resources/Hsap/igblast_dbs/TCR_V.fa \ -germline_db_D /home/user/tool/tracer-master/resources/Hsap/igblast_dbs/TCR_D.fa \ -germline_db_J /home/user/tool/tracer-master/resources/Hsap/igblast_dbs/TCR_J.fa \ -domain_system imgt \ -organism human \ -ig_seqtype TCR \ -num_alignments_V 5 \ -num_alignments_D 5 \ -num_alignments_J 5 \ -outfmt 3 \ -query cell1_TCR_A.Trinity.fasta
It looks like everything is fine,but there is a warning message above:
Warning: Auxilary data file could not be found
.I don't know which step is going to be a problem.
The text was updated successfully, but these errors were encountered: