-
Novel QSAR and QSPR descriptors?
For the past few weeks I have been working on a review article, which will contain a section with new QSAR/QSPR descriptors published in the period 2000-now. Here are a few:
-
BlueObelisk: OpenSource, OpenData and OpenStandards
OpenSource, OpenData and OpenStandards are not as strong in chemoinformatics as they are in bioinformatcs, where it is common knowledge that sharing is a good. Today, the JCIM published on the web an article about the Blue Obelisk movement, which promotes these three idealogies.
-
Blogging chemistry on blogspot.com
You might have read earlier posts in this blog on CMLRSS, and received a question today on how to integrate CMLRSS with blogs on blogspot.com. Now, current CMLRSS feeds are normally generated with customized scripts, often directly from a database.
-
Chemical reactions in CML
Gemma Holiday’s article on CMLReact was published in the january issue of the JCIM (doi:10.1021/ci0502698), which seems to be marked as sample issue right now. She used CMLReact as data format for MACiE (see doi:10.1093/bioinformatics/bti693), a database of 100 enzyme reactions, with fully annotated reaction mechanisms, making this an remarkable and insightfull database.
-
Hot articles; mining the semantic web
Roland Krause discussed today in his blog Notes from the Biomass an interesting website: postgenomic.com . This website, still marked BETA, mines blogs in the field of genomics and extract noteworthy statistics from it: which articles are cited in those blogs.
-
Kalzium Wins Award; Carsten Niehaus Interviewed
I was very pleased to read today that Kalzium, one of the projects that participate in the Blue Obelisk, got awarded! Cheers, Carsten!
-
An test suite for free, open source JVMs
This weekend I continued my work on getting the CDK and Jmol run with free, open source JVMs. Really, a lot works fine, as reported earlier in this blog: JChemPaint works and Jmol almost works (see the Classpath’s FreeSwingTestApps wiki page), and well over 95% of the CDK JUnit tests run without trouble too. So it comes down to identifying what does not run properly, and file bugs for this. For example, 26101 and 26108.