Changes between Version 1 and Version 2 of DevMtgMinutes/20090219
- Timestamp:
- Feb 19, 2009, 4:22:22 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevMtgMinutes/20090219
v1 v2 3 3 4 4 === New Action Items === 5 * XXX5 * Conrad will move previous action items into trac where appropriate 6 6 7 7 === Previous Action Items === … … 16 16 === Minutes === 17 17 18 1. 3D printer 19 * 3D printer arrived and installed on second floor 20 * Greg is investigating nugraf as x3d->stl conversion tool 18 21 1. Previous action items 19 22 * Eric forwarded PDB-L message … … 21 24 1. Open bug report updates 22 25 1. Meeting with Sali group 23 * Meeting is scheduled for Tuesday 2/24 at 1pm in BH-215 24 * Elaine will demonstrate some Chimera tools for visualizing structure ensembles (EnsembleCluster, molmap, RMSD, RenderByAttribute) 26 * Meeting is scheduled for one hour on Tuesday 2/24 at 1pm in BH-215 27 * Elaine will demonstrate some Chimera tools for visualizing structure ensembles (EnsembleCluster, molmap, RMSD, RenderByAttribute). Demo is targeted for 15 minutes. Some features are not working as expected and need further examination. 28 * Tom mentioned that Karen is interested in a Chimera interface to Multifit. 25 29 1. PDB SPLIT record 26 30 * Conrad reported the following: 27 31 * How often do SPLIT records appear in the PDB? 28 - There are three instances:29 - 3BZ1 3BZ230 - 3F1E 3F1F 3F1G 3F1H31 - 2ZUO 2ZV4 2ZV532 - The PDB files appear to be split at molecule or chain boundaries. According to PDB format documentation, if a PDB "entry is part of a SPLIT record (larger multi-protein complex), REMARK 350 represents only the quaternary structure of that split entry."32 - There are three instances: 33 - 3BZ1 3BZ2 34 - 3F1E 3F1F 3F1G 3F1H 35 - 2ZUO 2ZV4 2ZV5 36 - The PDB files appear to be split at molecule or chain boundaries. According to PDB format documentation, if a PDB "entry is part of a SPLIT record (larger multi-protein complex), REMARK 350 represents only the quaternary structure of that split entry." 33 37 * What does the mmCIF equivalent to partial models look like? 34 - Corresponding mmCIF and PDB files have exactly the same set of atoms.38 - Corresponding mmCIF and PDB files have exactly the same set of atoms. 35 39 * Can chain ids be reused in different partial models? 36 - Yes. For example, 3BZ1 and 3BZ2 both have a chain Z.40 - Yes. For example, 3BZ1 and 3BZ2 both have a chain Z. 37 41 * Other new PDB records in v3.20: 38 - NUMMDL (number of models)39 - MDLTYP (free text structural annotation)40 - DBREF1 DBREF2 (database cross reference for PDB, Genbank, Uniprot and NORINE)42 - NUMMDL (number of models) 43 - MDLTYP (free text structural annotation) 44 - DBREF1 DBREF2 (database cross reference for PDB, Genbank, Uniprot and NORINE) 41 45 * Updated PDB records in v3.20: 42 - COMPND SOURCE EXPDTA REVDAT JRNL REMARK SEQRES MODRES SSBOND LINK 46 - COMPND SOURCE EXPDTA REVDAT JRNL REMARK SEQRES MODRES SSBOND LINK 47 * Greg will update PDB parsing library to recognize 3.20 records 48 * Eric will add code to pop up info dialog when SPLIT record is present 49 * Eric is working on getting sequence annotations from Uniprot via web service 43 50 1. Possible annotation sources 44 * Conrad reported that the RCSB's official reply is that the database cross reference data is not available programmatically but to try MSD from EBI. It turns out that the MSD is now PDBe (PDB Europe) and they offer a SIFTS web service that provides database cross referencing. 51 * Conrad reported that the RCSB's official reply is that the database cross reference data is not available programmatically but to try MSD from EBI. It turns out that the MSD is now PDBe (PDB Europe) and they offer a SIFTS web service that provides database cross referencing 52 * Conrad pointed out that the information from SIFTS does not include any additional information from the non-PDB databases 53 * Tom mentioned it is possible to group residues by eg domain without fetching more information 54 * Tom will look into using SIFTS data for domain annotation 55 1. '''Meeting ends. Topics below not discussed.''' 45 56 1. Removal of features 46 57 1. Initial model appearance
![[Chimera Issue Tracking System]](/trac/chimera/chrome/site/chimera_logo.png)