If applications are hard to design and toolkits are harder, then frameworks are hardest of all. A framework designer gambles that one architecture will work for all applications in the domain. Any substantive change to the framework's design would reduce its benefits considerably, since the framework's main contribution to an application is the architecture it defines. Therefore it's imperative to design the framework to be as flexible and extensible as possible.
One of the most important considerations when building an application is the choice of framework. As the quote from the Gang of Four implies, there's much more to frameworks than just a collection of re-usable code. At their best, frameworks provide a foundation for thinking about a problem domain and a language for communicating with other developers about it. In this article, I'll introduce Octet, an object-oriented framework for molecular representation.
The Molecular Representation Problem
Isn't molecular representation a solved problem? After all, don't SMILES, Molfile, InChI, and CML adequately represent any molecule the average software developer is likely to see?
As previously discussed, molecular representation technologies have stagnated while the molecules chemists themselves now routinely make and use have continued to become more and more "exotic." Developers are now faced with the thorny problem that a variety of common structural motifs in chemistry can't be adequately represented with industry-standard cheminformatics tools.
This point is so important, I'll repeat it: cheminformatics has fallen behind chemistry in the kinds of molecules it can work with. Quick fixes only allow the problem to fester; what's needed is a comprehensive solution. This is Octet's problem domain.
Every framework is bounded by a specific problem domain. Although the size of the domain can vary, a framework provides a comprehensive solution within it. For complex and poorly standardized domains (such as molecular representation), a good framework can greatly accelerate application development.
A good frameworks stays within its problem domain. One of the most important reasons is to prevent featuritis, the root of much software evil. Keeping a framework focused on its core mission makes it much more likely that it can remain documented, tested, extensible, and efficient.
By intention, a variety of features fall outside Octet's problem domain and so will never be directly supported. For example, rendering 2-D structure diagrams is a common problem in cheminformatics that has nothing to do with solving the molecular representation problem. Similarly, reading and writing SMILES strings and Molfiles are supported by many toolkits, but not by Octet directly. After all, it's the inherent limitations of these languages that Octet is trying to overcome.
Higher-level functionality such as legacy language support and 2-D rendering, although not part of Octet itself, can be developed with Octet as a foundation. For example, two Octet add-on frameworks specifically address these problems. They are called Rosetta and Structure, respectively.
About This Series
This article is the first in a series discussing Octet. Future articles will describe in detail Octet's design, implementation, and use. Although Octet has come a long way, it's far from finished. My motivation for writing these articles is to hear what you have to say about Octet, so please feel free to contact me.
Although Octet is written in Java, code examples discussed here will be written in Ruby. I've taken the same approach in discussing the Chemistry Development Kit (CDK) and Structure-CDK. Ruby's brevity and comfortable syntax make it ideal for both writing and discussing code.
A Simple Test
Assuming you've installed Ruby, RubyGems and Ruby Java Bridge, you can perform a simple demonstration of Octet in Ruby:
require 'rubygems' require_gem 'rjb' require 'rjb' BasicMoleculeBuilder = Rjb::import('net.sf.octet.builder.BasicMoleculeBuilder') RepresentationKit = Rjb::import('net.sf.octet.util.RepresentationKit') MoleculeKit = Rjb::import('net.sf.octet.util.MoleculeKit') System = Rjb::import('java.lang.System') builder = BasicMoleculeBuilder.new RepresentationKit.buildHexane(builder) molecule = builder.releaseMolecule
The above code generates an Octet representation for n-hexane, and prints the representation to the console. To run this example, save the above code to a file called test.rb in your working directory. Then add octet-0.8.2.jar, which can be found in the Octet-0.8.2 source distribution, to the same directory. The test can then be run with the following sequence of commands:
export CLASSPATH=./octet-0.8.2.jar ruby test.rb **Molecule Properties** Atom Count: 6, Bonding System Count: 5 Atoms: atom: C (2nu 0e, 0or, 0.0fc, 1bs, 1n, 4.0val, 3ih ) atom: C (2nu 0e, 0or, 0.0fc, 2bs, 2n, 4.0val, 2ih ) atom: C (2nu 0e, 0or, 0.0fc, 2bs, 2n, 4.0val, 2ih ) atom: C (2nu 0e, 0or, 0.0fc, 2bs, 2n, 4.0val, 2ih ) atom: C (2nu 0e, 0or, 0.0fc, 2bs, 2n, 4.0val, 2ih ) atom: C (2nu 0e, 0or, 0.0fc, 1bs, 1n, 4.0val, 3ih ) No non-natural isotopic distributions specified. No Orbitals specified. Bonding Systems: bonding system: ( 2be, 0abe, 2a, 1ap ) [ (0, 1) ] bonding system: ( 2be, 0abe, 2a, 1ap ) [ (1, 2) ] bonding system: ( 2be, 0abe, 2a, 1ap ) [ (2, 3) ] bonding system: ( 2be, 0abe, 2a, 1ap ) [ (3, 4) ] bonding system: ( 2be, 0abe, 2a, 1ap ) [ (4, 5) ] Atom Pairs: atom pair: (0, 1) (1.0 bo) atom pair: (1, 2) (1.0 bo) atom pair: (2, 3) (1.0 bo) atom pair: (3, 4) (1.0 bo) atom pair: (4, 5) (1.0 bo) No Atomic Configurations specified. No Conformation specified.
Octet shares the same concepts and vocabulary as FlexMol. We'll drill down into the meaning of the output in later articles. The important thing to remember is that we can print out a report like the one above for any Molecule, no matter how complex.
Octet is an object-oriented framework designed to solve the molecular representation problem and serve as a solid foundation for a variety of cheminformatics applications. Of course, there's much more to Octet than the simple example shown here. Future articles will describe in greater detail the design and use of Octet through illustrative examples.