Changes between Version 76 and Version 77 of Release1.4

Timestamp:

Dec 24, 2008, 10:47:27 AM (17 years ago)

Author:

Scooter Morris

Comment:

--

Release1.4

@@ -120 +120 @@
    4. allow simultaneous fit of multiple molecules
 
-==== Sequence/Structure (Core 4) ====
-
- * connect to our own Web service to BLAST on PDB, provide dialog for choosing which hit structures to open, whether to show pairwise sequence alignment from BLAST (in MAV), whether to superimpose hit and query structures (with Matchmaker). Input is sequence of molecule model already open in Chimera. ECM
-    * (search other databases such as NR? PSI-BLAST on NR?) 
-
- * connect to our own Web service to multiple sequence alignment program (Muscle, T-Coffee, ... see [http://www.cgl.ucsf.edu/home/meng/sources.html#d list and links]), show result in MAV. Input would be sequence alignment already open in Chimera, probably would have to reformat into unaligned multi-FASTA for server. ECM
-
- * allow sending template structure and template/target sequence alignment to comparative modeling program, either local or Web. ECM
-
- * given a sequence alignment and associated structure, allow showing indels on structure relative to one of the sequences in the alignment (user specifies which structure and which sequence). ECM
-    * on my secondary MAV to-do list. EFP
-
- * allow editing sequence name. ECM
-    * on my secondary MAV to-do list. EFP
-
- * allow specifying "sequence to add" by accession code (Uniprot?). Its feature annotations would automatically come along as regions.  ECM
-    * would we want Fetch by ID for sequences? (would we want a sequence with no structure and not aligned with any other sequences?)
-    * perhaps allow specifying Uniprot accession or BLAST on Uniprot for existing sequences, retrieve and load feature annotations as sequence regions (would require global alignment to Uniprot sequence for correct mapping of features when the existing sequence is not identical)
-    * on my secondary MAV to-do list. EFP
-
-  * Matchmaker option to create post-fit alignment with Match->Align and refit on that to give more meaningful # of pairs and RMSD statistics along with the better alignment.  Perhaps even multiple such rounds, reporting stats and showing alignment only at the end. ECM
-  
-  * MAV report all-by-all percent identities to Reply Log in form of a (text) matrix instead of a line for each pair.  ECM
-    * on my tertiary MAV to-do list. EFP
-
-Most of the above aren't realistic for the 1.4 release given my work on other Chimera projects and on cluster backups.  However, many of these features aren't even on my radar at this point, so it would be good to have a discussion about them in order to begin to prioritize them so that perhaps some can make the 1.5 release. EFP
-
-The things that I *do* have on my primary MAV to-do list are:
-
- * When aligning in a structure sequence, consider secondary structure markups of non-structure sequences
- * If gaps are created while adding a sequence, make corresponding gaps in any markups
- * Vertical scrolling of alignment with scroll wheel
- * Show region names as tool tips
- * Allow add-sequence alignment parameters to be reset to defaults
- * Be smarter about what to use as the default gap character when adding a sequence
- * Aqua background -> gray, or put black border around sequence-name color swatches
- * "Sticky" headers (and remove Conservation/Consensus from Layout prefs)
- * "Diffing" of sequence/node against consensus/node/remainder of alignment
- * Symbols (cylinders, stars, etc.) in headers, and then manual header creation
- * Extract region into new alignment
- * Tree improvements: session save/restore; handle sequence addition/deletion; hide/show nodes; delete node; conservation/consensus of nodes; highlight node sequences; show numeric branch weights; restrict operations to nodes; trees where alignment isn't 1-to-1
-
-The first two items are the ones with the best chance of making the 1.4 release.
-
-==== Other Projects ====