<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Automated retrieval of expression data with Python and R</title>
	<atom:link href="http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/feed/" rel="self" type="application/rss+xml" />
	<link>http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 09:34:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Chris Plaisier</title>
		<link>http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-198</link>
		<dc:creator><![CDATA[Chris Plaisier]]></dc:creator>
		<pubDate>Sat, 04 Sep 2010 00:00:52 +0000</pubDate>
		<guid isPermaLink="false">http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-198</guid>
		<description><![CDATA[Just FYI there is a great download of the meta information from GEO @ this web site:

http://gbnci.abcc.ncifcrf.gov/geo/

Like your python implementation. ;-)

Peace,
Chris]]></description>
		<content:encoded><![CDATA[<p>Just FYI there is a great download of the meta information from GEO @ this web site:</p>
<p><a href="http://gbnci.abcc.ncifcrf.gov/geo/" rel="nofollow">http://gbnci.abcc.ncifcrf.gov/geo/</a></p>
<p>Like your python implementation. ;-)</p>
<p>Peace,<br />
Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas</title>
		<link>http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-161</link>
		<dc:creator><![CDATA[Nicolas]]></dc:creator>
		<pubDate>Thu, 25 Mar 2010 09:30:42 +0000</pubDate>
		<guid isPermaLink="false">http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-161</guid>
		<description><![CDATA[alright, thanks i ll mail the dev list then.]]></description>
		<content:encoded><![CDATA[<p>alright, thanks i ll mail the dev list then.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Chapman</title>
		<link>http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-160</link>
		<dc:creator><![CDATA[Brad Chapman]]></dc:creator>
		<pubDate>Wed, 24 Mar 2010 13:08:11 +0000</pubDate>
		<guid isPermaLink="false">http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-160</guid>
		<description><![CDATA[Nicolas;
That sounds great and would definitely be useful for Biopython. Contributions are very welcome. The best plan is to fork the GitHub trunk:

http://github.com/biopython/biopython/

For organizing, testing and documenting the code, useful tips are here:

http://biopython.org/wiki/Contributing

Feel free to send along any questions or progress reports to the Biopython mailing lists.

Brad]]></description>
		<content:encoded><![CDATA[<p>Nicolas;<br />
That sounds great and would definitely be useful for Biopython. Contributions are very welcome. The best plan is to fork the GitHub trunk:</p>
<p><a href="http://github.com/biopython/biopython/" rel="nofollow">http://github.com/biopython/biopython/</a></p>
<p>For organizing, testing and documenting the code, useful tips are here:</p>
<p><a href="http://biopython.org/wiki/Contributing" rel="nofollow">http://biopython.org/wiki/Contributing</a></p>
<p>Feel free to send along any questions or progress reports to the Biopython mailing lists.</p>
<p>Brad</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas Rapin</title>
		<link>http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-159</link>
		<dc:creator><![CDATA[Nicolas Rapin]]></dc:creator>
		<pubDate>Mon, 22 Mar 2010 10:15:51 +0000</pubDate>
		<guid isPermaLink="false">http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-159</guid>
		<description><![CDATA[Hi,

This is indeed a very nice little script you have made here.
Actually, I wrote a similar one based on yours, that does not depend on Rpy2 and the GEOquery package. and is purely in python. could that be something for BioPython?]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>This is indeed a very nice little script you have made here.<br />
Actually, I wrote a similar one based on yours, that does not depend on Rpy2 and the GEOquery package. and is purely in python. could that be something for BioPython?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-146</link>
		<dc:creator><![CDATA[Paul]]></dc:creator>
		<pubDate>Tue, 09 Feb 2010 20:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-146</guid>
		<description><![CDATA[Hey man just saying thanks for the great article it was very useful to what I&#039;m doing at the moment.]]></description>
		<content:encoded><![CDATA[<p>Hey man just saying thanks for the great article it was very useful to what I&#8217;m doing at the moment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lgautier</title>
		<link>http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-144</link>
		<dc:creator><![CDATA[lgautier]]></dc:creator>
		<pubDate>Sun, 07 Feb 2010 15:44:48 +0000</pubDate>
		<guid isPermaLink="false">http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-144</guid>
		<description><![CDATA[Similar issue for me. I had something to post off-blog, but had a hard time finding an email address.]]></description>
		<content:encoded><![CDATA[<p>Similar issue for me. I had something to post off-blog, but had a hard time finding an email address.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sri Kosuri</title>
		<link>http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-142</link>
		<dc:creator><![CDATA[Sri Kosuri]]></dc:creator>
		<pubDate>Tue, 02 Feb 2010 20:22:04 +0000</pubDate>
		<guid isPermaLink="false">http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-142</guid>
		<description><![CDATA[Hi Brad,

I&#039;m a post-doc in George Church&#039;s lab at Harvard; I&#039;ve been trying to contact you using your address in your code repositories (the synbio package) to no avail.  Could you drop me a line when you get a chance.

Thanks.]]></description>
		<content:encoded><![CDATA[<p>Hi Brad,</p>
<p>I&#8217;m a post-doc in George Church&#8217;s lab at Harvard; I&#8217;ve been trying to contact you using your address in your code repositories (the synbio package) to no avail.  Could you drop me a line when you get a chance.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Chapman</title>
		<link>http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-138</link>
		<dc:creator><![CDATA[Brad Chapman]]></dc:creator>
		<pubDate>Wed, 06 Jan 2010 12:49:55 +0000</pubDate>
		<guid isPermaLink="false">http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-138</guid>
		<description><![CDATA[Laurent;
Thanks for the more pythonic example -- that&#039;s really useful. Personally, I go back and forth on whether I prefer that way or the code snippets approach. Moving into snippets has been helping me practice my R skills, but does require the reader to feel comfortable with both Python and R syntax.

Thanks also for all your hard work on rpy. 2.1.0 is awesome; I love the ggplot2 integration.

Brad]]></description>
		<content:encoded><![CDATA[<p>Laurent;<br />
Thanks for the more pythonic example &#8212; that&#8217;s really useful. Personally, I go back and forth on whether I prefer that way or the code snippets approach. Moving into snippets has been helping me practice my R skills, but does require the reader to feel comfortable with both Python and R syntax.</p>
<p>Thanks also for all your hard work on rpy. 2.1.0 is awesome; I love the ggplot2 integration.</p>
<p>Brad</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurent</title>
		<link>http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-137</link>
		<dc:creator><![CDATA[Laurent]]></dc:creator>
		<pubDate>Wed, 06 Jan 2010 07:17:32 +0000</pubDate>
		<guid isPermaLink="false">http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-137</guid>
		<description><![CDATA[Once more an interesting demonstration of how some tools can be bridged.

This is also making me notice that some features in rpy2 are probably not as well documented as they should.

The use of a snippets of R code is perfectly fine,
however the option to move the code logic to Python exists (can make it easier for debugging with pdb,
allows the use of anonymous R variable that do not stay in R&#039;s &quot;globalenv&quot;).

(note: the following code is taking advantage of the features in rpy2-2.1.0, but the same idea could be used with 2.0.x...)

[sourcecode language=&quot;python&quot;]
from rpy2.robjects.packages import importr
utils    = importr(&quot;utils&quot;)
geoquery = importr(&quot;GEOquery&quot;)
rjson    = importr(&quot;rjson&quot;)

def _write_gsm_map(self, gsm_id, 
                   meta_file, table_file):
    &quot;&quot;&quot;Retrieve GEO expression values using Bioconductor, saving to a table and a jason file.
    &quot;&quot;&quot;
    gsm = geoquery.getGEO(gsm_id)
    utils.write_table(geoquery.Table(gsm),
                      file = table_file,
                      sep = &quot;\t&quot;,
                      row_names = False,
                      col_names = True)
    json_data = rjson.toJSON(geoquery.Meta(gsm))
    fh = file(meta_file, &quot;w&quot;)
    fh.write(json_data)
    fh.close()

[/sourcecode]

One can as also return &quot;json_data&quot; rather than save it into a file then read it immediately from the file.


L.]]></description>
		<content:encoded><![CDATA[<p>Once more an interesting demonstration of how some tools can be bridged.</p>
<p>This is also making me notice that some features in rpy2 are probably not as well documented as they should.</p>
<p>The use of a snippets of R code is perfectly fine,<br />
however the option to move the code logic to Python exists (can make it easier for debugging with pdb,<br />
allows the use of anonymous R variable that do not stay in R&#8217;s &#8220;globalenv&#8221;).</p>
<p>(note: the following code is taking advantage of the features in rpy2-2.1.0, but the same idea could be used with 2.0.x&#8230;)</p>
<pre class="brush: python; title: ; notranslate">
from rpy2.robjects.packages import importr
utils    = importr(&quot;utils&quot;)
geoquery = importr(&quot;GEOquery&quot;)
rjson    = importr(&quot;rjson&quot;)

def _write_gsm_map(self, gsm_id, 
                   meta_file, table_file):
    &quot;&quot;&quot;Retrieve GEO expression values using Bioconductor, saving to a table and a jason file.
    &quot;&quot;&quot;
    gsm = geoquery.getGEO(gsm_id)
    utils.write_table(geoquery.Table(gsm),
                      file = table_file,
                      sep = &quot;\t&quot;,
                      row_names = False,
                      col_names = True)
    json_data = rjson.toJSON(geoquery.Meta(gsm))
    fh = file(meta_file, &quot;w&quot;)
    fh.write(json_data)
    fh.close()

</pre>
<p>One can as also return &#8220;json_data&#8221; rather than save it into a file then read it immediately from the file.</p>
<p>L.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-136</link>
		<dc:creator><![CDATA[Nick]]></dc:creator>
		<pubDate>Tue, 05 Jan 2010 13:44:27 +0000</pubDate>
		<guid isPermaLink="false">http://bcbio.wordpress.com/2010/01/02/automated-retrieval-of-expression-data-with-python-and-r/#comment-136</guid>
		<description><![CDATA[Brad,

Good to see you&#039;re still posting.  I&#039;ve found some of your code to be quite useful.  Thanks!

- Nick]]></description>
		<content:encoded><![CDATA[<p>Brad,</p>
<p>Good to see you&#8217;re still posting.  I&#8217;ve found some of your code to be quite useful.  Thanks!</p>
<p>- Nick</p>
]]></content:encoded>
	</item>
</channel>
</rss>
