<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for So much to do, so little time</title>
	<atom:link href="http://rguha.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://rguha.wordpress.com</link>
	<description>Trying to squeeze sense out of chemical data</description>
	<lastBuildDate>Mon, 23 Feb 2009 16:45:24 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on The ONS Challenge &amp; Visualizing Chemical Space by Rajarshi Guha</title>
		<link>http://rguha.wordpress.com/2008/12/30/the-ons-challenge-visualizing-chemical-space/#comment-173</link>
		<dc:creator>Rajarshi Guha</dc:creator>
		<pubDate>Mon, 23 Feb 2009 16:45:24 +0000</pubDate>
		<guid isPermaLink="false">http://rguha.wordpress.com/?p=217#comment-173</guid>
		<description>Hi Joe - there was an update to the service which required that Base64 encoded SMILES be provided. See the Update in http://blog.rguha.net/?p=53</description>
		<content:encoded><![CDATA[<p>Hi Joe &#8211; there was an update to the service which required that Base64 encoded SMILES be provided. See the Update in <a href="http://blog.rguha.net/?p=53" rel="nofollow">http://blog.rguha.net/?p=53</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The ONS Challenge &amp; Visualizing Chemical Space by Joe Mulvaney</title>
		<link>http://rguha.wordpress.com/2008/12/30/the-ons-challenge-visualizing-chemical-space/#comment-172</link>
		<dc:creator>Joe Mulvaney</dc:creator>
		<pubDate>Mon, 23 Feb 2009 16:30:58 +0000</pubDate>
		<guid isPermaLink="false">http://rguha.wordpress.com/?p=217#comment-172</guid>
		<description>FYI, the example link is currently broken.  Clicking takes me to a mod_python exception page.  Looks like something in the XML lib.  If you can&#039;t reproduce, I can send the mod_python error report.</description>
		<content:encoded><![CDATA[<p>FYI, the example link is currently broken.  Clicking takes me to a mod_python exception page.  Looks like something in the XML lib.  If you can&#8217;t reproduce, I can send the mod_python error report.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Papers About Systems You Can&#8217;t Use or Buy by Tobias Kind</title>
		<link>http://rguha.wordpress.com/2009/02/01/papers-about-systems-you-cant-use-or-buy/#comment-166</link>
		<dc:creator>Tobias Kind</dc:creator>
		<pubDate>Sat, 07 Feb 2009 07:37:33 +0000</pubDate>
		<guid isPermaLink="false">http://rguha.wordpress.com/?p=291#comment-166</guid>
		<description>Hi Rajarshi,
I think the cool thing is, that Thomas Sander actually replied here.
After reading his post the whole message also got another taste.

I would usually agree with your post from a comp chem point of view.
If somebody reports of a system in a blurred manner only showing results
instead of the methods its pretty useless. Its impossible to test 
if the system works really in that way or if its just wishful thinking.
But that holds also true for all kind of conference talks or posters.

The first problem I had was that from home I could not read about 
Advanced Biological and Chemical Discovery (ABCD) or OSIRIS 
an Entirely in-House Developed Drug Discovery Informatics System,
because its ACS closed source.

So if the authors dont want to pony up 1000 Dollars (or $3000) for
ACS Open Access option its probably not worth (it). Or lets say
its only important for a very small part of the scientific community
or comp chem researchers and of no general interest.

On the other hand I have to agree with Thomas that there is certainly
pressure from outside and inside to report such a development. Its good
for the reputation and also gives you scientific kudos. The OSIRIS system 
itself was built over 10 years according to the Actelion company report.
http://www1.actelion.com/documents/AR_Actelion_1999.pdf

If you look at actelion.com there are only three OSIRIS hits; so its of
minor importance to the whole company or ... wait maybe it is, maybe its
so good it must be held secretive and the the whole publications suddenly
is an enlightenment?! (I could not read it because of closed access, 
so I just assume it is a satori) (google for OSIRIS site:actelion.com)

I would say this is not about company bashing, allthough two of your links
point to publications from companies, it is also not about open source 
or open data (the highest level of scientific reporting), but it is about 
proper scientific reporting with very detailed methods sections 
(many journals do not appreciate that). So here I agree again with you and
would come to the conclusion: A non-opaque system or program should be 

1) open source OR
2) commercially available OR 
3) contain a very well description to fully reproduce the system.

And we certainly should try to understand scientists in companies who 
are operating under the Sword of Damocles, hence their legal department,
and are actually not allowed to disclose any valuable information.  

Kind regards
Tobias Kind (FiehnLab)</description>
		<content:encoded><![CDATA[<p>Hi Rajarshi,<br />
I think the cool thing is, that Thomas Sander actually replied here.<br />
After reading his post the whole message also got another taste.</p>
<p>I would usually agree with your post from a comp chem point of view.<br />
If somebody reports of a system in a blurred manner only showing results<br />
instead of the methods its pretty useless. Its impossible to test<br />
if the system works really in that way or if its just wishful thinking.<br />
But that holds also true for all kind of conference talks or posters.</p>
<p>The first problem I had was that from home I could not read about<br />
Advanced Biological and Chemical Discovery (ABCD) or OSIRIS<br />
an Entirely in-House Developed Drug Discovery Informatics System,<br />
because its ACS closed source.</p>
<p>So if the authors dont want to pony up 1000 Dollars (or $3000) for<br />
ACS Open Access option its probably not worth (it). Or lets say<br />
its only important for a very small part of the scientific community<br />
or comp chem researchers and of no general interest.</p>
<p>On the other hand I have to agree with Thomas that there is certainly<br />
pressure from outside and inside to report such a development. Its good<br />
for the reputation and also gives you scientific kudos. The OSIRIS system<br />
itself was built over 10 years according to the Actelion company report.<br />
<a href="http://www1.actelion.com/documents/AR_Actelion_1999.pdf" rel="nofollow">http://www1.actelion.com/documents/AR_Actelion_1999.pdf</a></p>
<p>If you look at actelion.com there are only three OSIRIS hits; so its of<br />
minor importance to the whole company or &#8230; wait maybe it is, maybe its<br />
so good it must be held secretive and the the whole publications suddenly<br />
is an enlightenment?! (I could not read it because of closed access,<br />
so I just assume it is a satori) (google for OSIRIS site:actelion.com)</p>
<p>I would say this is not about company bashing, allthough two of your links<br />
point to publications from companies, it is also not about open source<br />
or open data (the highest level of scientific reporting), but it is about<br />
proper scientific reporting with very detailed methods sections<br />
(many journals do not appreciate that). So here I agree again with you and<br />
would come to the conclusion: A non-opaque system or program should be </p>
<p>1) open source OR<br />
2) commercially available OR<br />
3) contain a very well description to fully reproduce the system.</p>
<p>And we certainly should try to understand scientists in companies who<br />
are operating under the Sword of Damocles, hence their legal department,<br />
and are actually not allowed to disclose any valuable information.  </p>
<p>Kind regards<br />
Tobias Kind (FiehnLab)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Locality of References in a Paper by Vladimir Chupakhin</title>
		<link>http://rguha.wordpress.com/2008/09/30/locality-of-references-in-a-paper/#comment-165</link>
		<dc:creator>Vladimir Chupakhin</dc:creator>
		<pubDate>Fri, 06 Feb 2009 19:36:12 +0000</pubDate>
		<guid isPermaLink="false">http://rguha.wordpress.com/?p=92#comment-165</guid>
		<description>The idea seems to be quite old - http://eigenfactor.org/map/maps.htm</description>
		<content:encoded><![CDATA[<p>The idea seems to be quite old &#8211; <a href="http://eigenfactor.org/map/maps.htm" rel="nofollow">http://eigenfactor.org/map/maps.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Papers About Systems You Can&#8217;t Use or Buy by Rajarshi Guha</title>
		<link>http://rguha.wordpress.com/2009/02/01/papers-about-systems-you-cant-use-or-buy/#comment-163</link>
		<dc:creator>Rajarshi Guha</dc:creator>
		<pubDate>Wed, 04 Feb 2009 16:50:36 +0000</pubDate>
		<guid isPermaLink="false">http://rguha.wordpress.com/?p=291#comment-163</guid>
		<description>Thomas, thanks a lot for the clarification. (I&#039;ve copied your comment to the new blog at blog.rguha.net)</description>
		<content:encoded><![CDATA[<p>Thomas, thanks a lot for the clarification. (I&#8217;ve copied your comment to the new blog at blog.rguha.net)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Papers About Systems You Can&#8217;t Use or Buy by Thomas Sander</title>
		<link>http://rguha.wordpress.com/2009/02/01/papers-about-systems-you-cant-use-or-buy/#comment-162</link>
		<dc:creator>Thomas Sander</dc:creator>
		<pubDate>Wed, 04 Feb 2009 16:42:32 +0000</pubDate>
		<guid isPermaLink="false">http://rguha.wordpress.com/?p=291#comment-162</guid>
		<description>The paper is a followup to a poster displayed on the ICCS2008, which caused great interest from cheminformaticians at larger corporations, who seek to convince upper management to support a higher degree of internal development. The main motivation for the paper was to prove by experience that this approach can work and to deliver an argument for those, who are willing to take the risk and go into a similar direction. Only if many drug companies develop their own software ideally on agreed open standards, the commercial software industry will be forced to improve their products and to support common standards. It is a shame that products from different vendors hardly interoperate.

I agree that use of the paper is limited if your job is not related to developing chemistry related software. I also support the idea of open source and open tools. We are in a dialog with our management with the intend to release substantially more stuff (source code and/or tools).

The J&amp;J paper was actually cited.</description>
		<content:encoded><![CDATA[<p>The paper is a followup to a poster displayed on the ICCS2008, which caused great interest from cheminformaticians at larger corporations, who seek to convince upper management to support a higher degree of internal development. The main motivation for the paper was to prove by experience that this approach can work and to deliver an argument for those, who are willing to take the risk and go into a similar direction. Only if many drug companies develop their own software ideally on agreed open standards, the commercial software industry will be forced to improve their products and to support common standards. It is a shame that products from different vendors hardly interoperate.</p>
<p>I agree that use of the paper is limited if your job is not related to developing chemistry related software. I also support the idea of open source and open tools. We are in a dialog with our management with the intend to release substantially more stuff (source code and/or tools).</p>
<p>The J&amp;J paper was actually cited.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Locality of References in a Paper by Rajarshi Guha</title>
		<link>http://rguha.wordpress.com/2008/09/30/locality-of-references-in-a-paper/#comment-159</link>
		<dc:creator>Rajarshi Guha</dc:creator>
		<pubDate>Mon, 02 Feb 2009 21:34:43 +0000</pubDate>
		<guid isPermaLink="false">http://rguha.wordpress.com/?p=92#comment-159</guid>
		<description>Certainly an interesting view. It&#039;d be interesting to look at if I could easily extract bibligraphies.

PS. This blog has now moved to http://blog.rguha.net</description>
		<content:encoded><![CDATA[<p>Certainly an interesting view. It&#8217;d be interesting to look at if I could easily extract bibligraphies.</p>
<p>PS. This blog has now moved to <a href="http://blog.rguha.net" rel="nofollow">http://blog.rguha.net</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Locality of References in a Paper by Vladimir Chupakhin</title>
		<link>http://rguha.wordpress.com/2008/09/30/locality-of-references-in-a-paper/#comment-158</link>
		<dc:creator>Vladimir Chupakhin</dc:creator>
		<pubDate>Mon, 02 Feb 2009 21:31:17 +0000</pubDate>
		<guid isPermaLink="false">http://rguha.wordpress.com/?p=92#comment-158</guid>
		<description>The web-like picture of the cited literature :)

X (original) - X1 (cited in X) - X2 (cited in X1) - two levels would be enough I think. And for the molecular modeling and QSAR papers I think we will see some interesting intersections (would it?)</description>
		<content:encoded><![CDATA[<p>The web-like picture of the cited literature <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>X (original) &#8211; X1 (cited in X) &#8211; X2 (cited in X1) &#8211; two levels would be enough I think. And for the molecular modeling and QSAR papers I think we will see some interesting intersections (would it?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Playing with REST Descriptor Services by Update to the REST Descriptor Services at So much to do, so little time</title>
		<link>http://rguha.wordpress.com/2009/01/07/playing-with-rest-descriptor-services/#comment-157</link>
		<dc:creator>Update to the REST Descriptor Services at So much to do, so little time</dc:creator>
		<pubDate>Mon, 02 Feb 2009 13:19:42 +0000</pubDate>
		<guid isPermaLink="false">http://rguha.wordpress.com/?p=245#comment-157</guid>
		<description>[...] the example URL&#8217;s described in my previous post that involve SMILES strings, should be rewritten using base64 encoded SMILES. So to get a document [...]</description>
		<content:encoded><![CDATA[<p>[...] the example URL&#8217;s described in my previous post that involve SMILES strings, should be rewritten using base64 encoded SMILES. So to get a document [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Update to the REST Descriptor Services by Deploying Predictive Models at So much to do, so little time</title>
		<link>http://rguha.wordpress.com/2009/01/11/update-to-the-rest-descriptor-services/#comment-156</link>
		<dc:creator>Deploying Predictive Models at So much to do, so little time</dc:creator>
		<pubDate>Mon, 02 Feb 2009 06:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://rguha.wordpress.com/?p=250#comment-156</guid>
		<description>[...] the model. This leads to a limitation - the descriptor calculation step of the service uses the CDK descriptor service and so the models must employ the CDK descriptors. While restrictive it&#8217;s not too bad, since [...]</description>
		<content:encoded><![CDATA[<p>[...] the model. This leads to a limitation &#8211; the descriptor calculation step of the service uses the CDK descriptor service and so the models must employ the CDK descriptors. While restrictive it&#8217;s not too bad, since [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
