Skip to main content

Proposed CDK changes related to PDBReader and BioPolymer

This is expanding on one of the points that Rajarshi made in his blog (which he followed up here) on the PDB file handling capabilities of the CDK. There are two related topics : reading of PDB format files (the ancient, fixed column-width ATOM files) and the model that these are read into.


The old PDB format is being replaced with mmCIF and/or PDBML formats. Only there are lots of programs that write out this format, so it makes sense to still support it for a while at least.

However, it is a quite nasty format, in some ways. Not so much the fixed column width, but the fact that crystallographers abuse the file format in all sorts of ways. Even simple things like expecting that atom numbers will always increase, may not be true.

So it is not easy making a good reader for PDB files. The current CDK one won't read a file with just ATOM records, for example. Think that's reasonable? Well, tough luck for people that made programs that produce simple files like this.

A more serious problem is the fact that you can't get properly connected ligands from a PDB file. Or easily get at the disordered regions. Or get at the waters. Well, sort of - I suppose that many of these things can be done after reading, with CDK classes.


In some ways - so long as the atoms are read in - anything can be done to the model post-reading. However, the point of having data model classes like Polymer and BioPolymer is to capture some of the complexity of the macromolecule's organisation.

BioPolymer and the PDBReader do a good job of reading and storing the information in the header files (except that it is not always right!). Apart from calling chains 'Strands', some things are done reasonably well. I don't think that ligand atoms should be stored 'loose' as they are, but probably in referenced atom containers.

The real difficulty with modelling proteins lies with representing the hierarchy. One way is 'PMCA' - protein, model, chain, atom. This misses out secondary structure, but it may be too literal to have objects for every concept; the CDK stores the secondary structure given in the header file as IPDBStructure objects - with insertion codes, which is good to see.

However, there are more secondary structures than helix, turn, and strand. I'm never quite sure what the best way to model the more flexible situation, though.

Integration with biojava

It seems a shame that several open source java projects have very little in the way of integration (that I can see). At least on this topic. Of course, Egon (among others) has done work on both both CDK and Jmol, but it concerns me that incompatible ways of doing things lead to projects drifting apart, that should work together.

For example, here is a class I wrote today (for someone else) that uses both biojava and the CDK. It is very much a hack, but the key point is the method makeLigandsFromGroups that takes both a List of biojava.Group objects and a List of IMolecules, along the way converting biojava Atoms to CDK Atoms.

Clearly, biojava has a better interface to its model as you can get a List of the hetatm groups. The CDK, on the other hand, has better support for determining atom types and setting properties on them.


Popular posts from this blog

How many isomers of C4H11N are there?

One of the most popular queries that lands people at this blog is about the isomers of C4H11N - which I suspect may be some kind of organic chemistry question on student homework. In any case, this post will describe how to find all members of a small space like this by hand rather than using software.

Firstly, lets connect all the hydrogens to the heavy atoms (C and N, in this case). For example:

Now eleven hydrogens can be distributed among these five heavy atoms in various ways. In fact this is the problem of partitioning a number into a list of other numbers which I've talked about before. These partitions and (possible) fragment lists are shown here:

One thing to notice is that all partitions have to have 5 parts - even if one of those parts is 0. That's not strictly a partition anymore, but never mind. The other important point is that some of the partitions lead to multiple fragment lists - [3, 3, 2, 2, 1] could have a CH+NH2 or an NH+CH2.

The final step is to connect u…

Havel-Hakimi Algorithm for Generating Graphs from Degree Sequences

A degree sequence is an ordered list of degrees for the vertices of a graph. For example, here are some graphs and their degree sequences:

Clearly, each graph has only one degree sequence, but the reverse is not true - one degree sequence can correspond to many graphs. Finally, an ordered sequence of numbers (d1 >= d2 >= ... >= dn > 0) may not be the degree sequence of a graph - in other words, it is not graphical.

The Havel-Hakimi (HH) theorem gives us a way to test a degree sequence to see if it is graphical or not. As a side-effect, a graph is produced that realises the sequence. Note that it only produces one graph, not all of them. It proceeds by attaching the first vertex of highest degree to the next set of high-degree vertices. If there are none left to attach to, it has either used up all the sequence to produce a graph, or the sequence was not graphical.

The image above shows the HH algorithm at work on the sequence [3, 3, 2, 2, 1, 1]. Unfortunately, this produce…

Generating Trees

Tree generation is a well known (and solved!) problem in computer science. On the other hand, it's pretty important for various problems - in my case, making tree-like fusanes. I'll describe here the slightly tortuous route I took to make trees.

Firstly, there is a famous theorem due to Cayley that the number of (labelled) trees on n vertices is nn - 2 which can be proved by using Prüfer sequences. That's all very well, you might well say - but what does all this mean?

Well, it's not all that important, since there is a fundamental problem with this approach : the difference between a labelled tree and an unlabelled tree. There are many more labeled trees than unlabeled :

There is only one unlabeled tree on 3 vertices, but 3 labeled ones
this is easy to check using the two OEIS sequences for this : A000272 (labeled) and A000055 (unlabeled). For n ranging from 3 to 8 we have [3, 16, 125, 1296, 16807, 262144] labeled trees and [1, 2, 3, 6, 11, 23] unlabeled ones. Only 23 …