Opened 6 years ago
Closed 3 years ago
#3014 closed enhancement (fixed)
Blast Protein tool: threading
Reported by: | Tom Goddard | Owned by: | Zach Pearson |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Sequence | Version: | |
Keywords: | Cc: | Elaine Meng, Eric Pettersen | |
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | ChimeraX |
Description
The following bug report has been submitted: Platform: Linux-5.3.0-45-generic-x86_64-with-debian-buster-sid ChimeraX Version: 0.93 (2020-04-03) Description I am unable to use the Blast Protein tool. Where one is supposed to insert the sequence allignments or protein sequence, the software does not allow you to paste anything. I was also hoping that I could run the jobs using multithreading. Log: UCSF ChimeraX version: 0.93 (2020-04-03) © 2016-2020 Regents of the University of California. All rights reserved. How to cite UCSF ChimeraX > toolshed show "Blast Protein" > help help:quickstart Expected a collection of one of 'atoms', 'bonds', 'cartoons', 'models', 'pbonds', 'pseudobonds', 'ribbons', or 'surfaces' or a keyword Expected an objects specifier or a view name or a keyword Expected a collection of one of 'atoms', 'bonds', 'cartoons', 'models', 'pbonds', 'pseudobonds', 'ribbons', or 'surfaces' or a keyword > ui autostart false "Model Panel" Expected a models specifier or a keyword Expected a collection of one of 'atoms', 'bonds', 'cartoons', 'models', 'pbonds', 'pseudobonds', 'ribbons', or 'surfaces' or a keyword QObject::startTimer: Timers can only be used with threads started with QThread QObject::startTimer: Timers can only be used with threads started with QThread > toolshed show "Modeller Comparative" Expected a collection of one of 'atoms', 'bonds', 'cartoons', 'models', 'pbonds', 'pseudobonds', 'ribbons', or 'surfaces' or a keyword > toolshed show "Blast Protein" > help help:user > toolshed show "Modeller Comparative" OpenGL version: 3.3 (Core Profile) Mesa 19.2.8 OpenGL renderer: llvmpipe (LLVM 9.0, 256 bits) OpenGL vendor: VMware, Inc. Manufacturer: Dell Inc. Model: PowerEdge R520 OS: Ubuntu 18.04 bionic Architecture: 64bit ELF CPU: 32 Intel(R) Xeon(R) CPU E5-2450L 0 @ 1.80GHz Cache Size: 20480 KB Graphics: 06:00.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. G200eR2 [102b:0534] Subsystem: Dell G200eR2 [1028:04f6] Kernel driver in use: mgag200
Change History (18)
comment:1 by , 6 years ago
Cc: | added |
---|---|
Component: | Unassigned → Sequence |
Owner: | set to |
Platform: | → all |
Project: | → ChimeraX |
Status: | new → assigned |
Summary: | ChimeraX bug report submission → Blast Protein tool: allow sequence input; threading |
Type: | defect → enhancement |
comment:2 by , 5 years ago
Resolution: | → not a bug |
---|---|
Status: | assigned → closed |
Currently, the Blast Protein tool can only use the sequence from a chain in an opened model as the query.
An alternative is to open your sequence (FASTA format works) and then used the "blast {sequence_name}" command. For FASTA format, "{sequence_name}" is the label on the description line that starts with >.
comment:3 by , 5 years ago
Resolution: | not a bug |
---|---|
Status: | closed → reopened |
This is an RFE not a bug report. Request is to allow entering sequence directly into the Blast Protein GUI, like can be done in Chimera.
comment:4 by , 5 years ago
Blasting against a sequence in Chimera can only be done by entering the sequence, but ChimeraX supports opening sequence files. Once opened, the sequences can be used in blast searches, although only from the command line. So the question is whether we should add a blast GUI to sequence viewer, or continue to support entering a sequence via blastprotein.
follow-up: 5 comment:5 by , 5 years ago
There is another option, like what we had in Chimera: Blast Protein GUI allows pasting a sequence in as the query.
comment:6 by , 5 years ago
Cc: | added |
---|
comment:7 by , 5 years ago
Cc: | removed |
---|---|
Owner: | changed from | to
Status: | reopened → assigned |
Summary: | Blast Protein tool: allow sequence input; threading → Blast Protein tool: allow direct sequence input; threading |
comment:8 by , 4 years ago
Cc: | added |
---|---|
Owner: | changed from | to
comment:9 by , 4 years ago
Summary: | Blast Protein tool: allow direct sequence input; threading → Blast Protein tool: threading |
---|
I think it would be good to consider the threading issue separately from arbitrary sequence input, which is now part of #5055
comment:10 by , 4 years ago
I've never used ChimeraX < 1.2.5, so I'm not sure what BlastProtein was like for 0.93 (the version from the user's report).
If the blastprotein tool's new UI could be run multiple times without hanging the UI while waiting for results, would this ticket be obsolete?
comment:11 by , 4 years ago
I don't think this ticket is about multithreading -- why the reporter mentioned that is unclear. There question was about pasting in a sequence which the current and past GUIs did not allow. It may be worth allowing pasting in a sequence -- the AlphaFold GUI is an example that allows that.
comment:12 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
As of tonight's daily build, several instances of the blastprotein command can now be run at the same time (whether from the command line or from the GUI), and results windows will independently display themselves afterwards. I think this _probably_ satisfies the multithreading ask. I realize I forgot to add the user to #5055 -- will add.
comment:13 by , 3 years ago
This ticket is NOT about multithreading. It is about pasting plain text sequence into the Blast dialog. Structural biologists refer to finding 3D structures consistent with a sequence as "threading."
comment:14 by , 3 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:15 by , 3 years ago
Cc: | removed |
---|---|
Reporter: | changed from | to
comment:16 by , 3 years ago
What's the expectation here, is it running several separate BLAST jobs from one interface given several sequences, or is it running all the sequences in the same BLAST job?
comment:17 by , 3 years ago
The reporter was Karl Voigtritter from 2.5 years ago. It seems like his description is clear enough, he didn't know where to enter a sequence because he could not paste in anything to the user interface. And the multithreading part very likely means running blast froze ChimeraX at that time (ChimeraX 0.93). The blocking of ChimeraX was long ago fixed. Perhaps your recent changes allow pasting in a sequence.
Reported by Karl Voigtritter