Changes between Initial Version and Version 1 of Architecture


Ignore:
Timestamp:
Jan 7, 2009, 10:50:16 AM (17 years ago)
Author:
goddard
Comment:

.

Legend:

Unmodified
Added
Removed
Modified

  • Architecture

    v1 v1  
     1Architecture and Implementation Issues
     2
     3 1. Use numpy for vector, point, transform, bounding box, coordinate set data types.  Our current home-brewed Vector, Point, and Xform classes are a significant obstacle to implementing geometric calculations.  The Chimera volume data code is littered with conversions back and forth between these undernourished data types and the much more usable numpy arrays. TG
     4 1. Use SWIG to make Python wrappers for C++ code.  Our current home-brewed WrapPy seems to require maintenance for every new Python version. WrapPy does not support numpy array arguments which are used throughout the volume data C++ code. SWIG is well-maintained and the industry standard and it does not make sense for us to duplicate that work. TG
     5 1. Don't auto-generate molecular data classes with OTF.  Our current auto-generated molecule classes introduce unnecessary difficulty in maintaining and enhancing those data structures. Those classes should be directly hand-written.  The OTF appears to be historical baggage. TG
     6 1. Many GUI features have no command equivalent.  This impairs movie making and scripting to process large numbers of models.  May want to establish a protocol that no new feature goes into a production release without a command interface?  TG
     7 1. Separate _chimera C++ library into a molecule library and a 3d viewer library (Camera, viewer, side view, lights, opengl management, colors). More modularity will help code quality and faster code modification/testing cycle. TG