I would like to propose getting rid of the trajectory log in the model
as we can do the same sort of thing using State classes. Since these
aren't part of the Model, they would be much more flexible and
customizable. I currently have such a state for writing chimera BILD
files that I can submit at some point.
Agreed. The trajectory log is very inflexible, and does not use any kind
of standard format. I had also mentally targeted it for destruction.
This will, of course, horribly break the Restrainer web interface, but
presumably Jeremy will speak up if this is a problem for him.
And I would propose removing the ModelData OptimizedIndexIterator (or
whatever it is called). The API is funny and it doesn't provide any
functionality which can't be achieved other ways using more or less
the same number of lines of code.
No complaints from me.
Ben
--
http://salilab.org/~ben/
"It is a capital mistake to theorize before one has data."
- Sir Arthur Conan Doyle