On Mon, Aug 22, 2011 at 10:15 AM, Stephan Beisken <[email protected]> wrote: > I tested the functionality using several KNIME workflows. The nodes function > within the limits of their underlying CDK classes and handle errors without > breaking the workflow.
I am sure it does :) I was just wondering how this functionality testing is done, but your answer suggests that is manual work. Now, I could imagine that KNIME workflow are run in a test suite, with some validation of the outcome, like number of objects in a few output nodes or so. (I'm just interested in automated testing :) > Once 1.4.2 is released, I will update the version. Well, I just did that this weekend :) > Additional atom types would be great! I'm sorry your work on the iron atom types was already covered by Asad group's work. I always hate to see duplicate work :/ I still have some 20 atom types lined up from the Asad's group, and these will get merged bit by bit into the 1.4.x branch. Something else, which you surely must have been talking about with Christoph... how do the CDK-KNIME workflows compare to the CDK-Taverna versions? Will you be writing about that? I'd love to see a Battle-of-the-CDK-workflows! :) Egon -- Dr E.L. Willighagen Postdoctoral Researcher Institutet för miljömedicin Karolinska Institutet (http://ki.se/imm) Homepage: http://egonw.github.com/ LinkedIn: http://se.linkedin.com/in/egonw Blog: http://chem-bla-ics.blogspot.com/ PubList: http://www.citeulike.org/user/egonw/tag/papers ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Cdk-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cdk-user
