<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;D04MQn09fCp7ImA9WhNaEko.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990</id><updated>2013-01-27T06:39:43.364-02:00</updated><category term="SciPy" /><category term="Google Translate" /><category term="Statistics" /><category term="Free Software" /><category term="MathJax" /><category term="Math" /><category term="Random number generation" /><category term="CPython" /><category term="RIA" /><category term="Translation" /><category term="Programming" /><category term="MongoDB" /><category term="Just-in-time compilation" /><category term="Open source" /><category term="numerical" /><category term="Languages" /><category term="Google AppEngine" /><category term="python" /><category term="Language" /><category term="Prior probability" /><category term="Text mining" /><category term="Event-driven programming" /><category term="math research education" /><category term="Servers" /><category term="science" /><category term="Cloud computing" /><category term="Gnuplot" /><category term="Probability distribution" /><category term="Markov chain Monte Carlo" /><category term="Liveplots" /><category term="PyQt" /><category term="Search Engines" /><category term="Matplotlib" /><category term="Google Scholar" /><category term="Web2.0" /><category term="Data visualization" /><category term="Latex" /><category term="NoSQL" /><category term="NumPy" /><category term="networks" /><category term="simulations" /><category term="Graphing" /><category term="Source code" /><category term="Cython" /><category term="cool tools" /><category term="Database" /><category term="Linux" /><category term="plotting" /><category term="Qt" /><category term="Pypy" /><category term="Free" /><category term="collaborative" /><title>Python in Science</title><subtitle type="html">Scientific adventures with Python.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://pyinsci.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>66</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/PythonInScience" /><feedburner:info uri="pythoninscience" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>PythonInScience</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><entry gd:etag="W/&quot;CkYBQnk8fyp7ImA9WhNVFUs.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-7897017020547395528</id><published>2012-12-26T20:15:00.003-02:00</published><updated>2012-12-26T20:15:53.777-02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-12-26T20:15:53.777-02:00</app:edited><title>Compressing GeoJSON with Python</title><summary>GeoJSON can get quite big when you need represent complex maps with lots of polygons. Even though it compresses well, being text, it can still be quite a hassle to store and upload to a website in uncompressed form. Recently while working on a web app which requires the upload of maps in GeoJSON format, I stumbled upon Google App Engine's limitation of 32MB for POST requests. At that point I </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/7897017020547395528/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=7897017020547395528" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7897017020547395528?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7897017020547395528?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/BGUQ00YhCvw/compressing-geojson-with-python.html" title="Compressing GeoJSON with Python" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2012/12/compressing-geojson-with-python.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkIAQX86cSp7ImA9WhVQEkU.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-3036093561041683254</id><published>2012-04-01T10:55:00.000-03:00</published><updated>2012-04-01T10:55:40.119-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-04-01T10:55:40.119-03:00</app:edited><title>Benchmarking NLTK under Pypy</title><summary>Natural Language Processing (NLP). A marvelous world of possibilities! Fortunately it is also a great example of another domain of application for which Python is wonderfully well equipped.

I have been playing with Python and NLP, for a couple of years now, integrating its tools on a reasonably large project. I hope to demo this project really soon, but it is not the topic of this post.

The </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/3036093561041683254/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=3036093561041683254" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3036093561041683254?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3036093561041683254?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/-2_mWDVtJss/benchmarking-nltk-under-pypy.html" title="Benchmarking NLTK under Pypy" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>4</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2012/04/benchmarking-nltk-under-pypy.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEYERn87eSp7ImA9WhdbEkg.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-3904400937279250815</id><published>2011-10-10T10:08:00.000-03:00</published><updated>2011-10-10T10:08:27.101-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-10T10:08:27.101-03:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="MongoDB" /><category scheme="http://www.blogger.com/atom/ns#" term="Search Engines" /><category scheme="http://www.blogger.com/atom/ns#" term="Google Scholar" /><category scheme="http://www.blogger.com/atom/ns#" term="NoSQL" /><category scheme="http://www.blogger.com/atom/ns#" term="python" /><category scheme="http://www.blogger.com/atom/ns#" term="Database" /><category scheme="http://www.blogger.com/atom/ns#" term="Text mining" /><title>Scrapy, Google Scholar and MongoDB</title><summary>I have been deeply involved in text mining problems lately, If you watched my presentation a EuroScipy this year (http://www.slideshare.net/fccoelho/mining-legal-texts-with-python) you have an idea of some of the things I am up to.

Well part of problem of text mining is to get hold of the text you want to analyze in the first place. For many projects I am involved with, I already have mountains </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/3904400937279250815/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=3904400937279250815" title="7 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3904400937279250815?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3904400937279250815?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/bht_AWsyls4/scrapy-google-scholar-and-mongodb.html" title="Scrapy, Google Scholar and MongoDB" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>7</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2011/10/scrapy-google-scholar-and-mongodb.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUYGQn48cCp7ImA9WhdWEkw.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-728257062939640650</id><published>2011-09-05T07:05:00.000-03:00</published><updated>2011-09-05T07:05:23.078-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-05T07:05:23.078-03:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="PyQt" /><title>Generating Qt resource files from whole directory trees</title><summary>Yesterday I had to scratch a little annoying itch. I had to embed a  javascript library (MathJax) into a PyQt project of mine(Model-Builder).  Embedding static files into Qt projects is done via resource files. I  was surprised that Qt Designer resource editor has no way to recursively  scan directories. You have to add files manually.

That  was not an option for me since MathJax is somewhat </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/728257062939640650/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=728257062939640650" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/728257062939640650?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/728257062939640650?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/bnZwzx8tNCg/generating-qt-resource-files-from-whole.html" title="Generating Qt resource files from whole directory trees" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2011/09/generating-qt-resource-files-from-whole.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0QAQHk7eyp7ImA9Wx9QFU8.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-8663941621245297669</id><published>2010-12-28T07:06:00.005-02:00</published><updated>2010-12-28T07:42:21.703-02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-12-28T07:42:21.703-02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Cython" /><category scheme="http://www.blogger.com/atom/ns#" term="SciPy" /><category scheme="http://www.blogger.com/atom/ns#" term="NumPy" /><title>Efficient MCMC in Python -- Errata and some extra info</title><summary>In my previous post, some readers pointed out that the pure Python version of the code was slower than it should be. I checked and found out that the timing was wrong due to some bug in the %time flag in the sage notebook.Some other interested readers pointed out that using numpy's RNGs in the pure Python version would sure improve the performance. Again I went back and tested it.So without </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/8663941621245297669/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=8663941621245297669" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8663941621245297669?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8663941621245297669?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/55xegNgpqzY/efficient-mcmc-in-python-errata-and.html" title="Efficient MCMC in Python -- Errata and some extra info" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>4</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2010/12/efficient-mcmc-in-python-errata-and.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUUASXwzeip7ImA9Wx9QE0s.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-5599834357026795857</id><published>2010-12-25T19:59:00.014-02:00</published><updated>2010-12-26T09:34:08.282-02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-12-26T09:34:08.282-02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Programming" /><category scheme="http://www.blogger.com/atom/ns#" term="Markov chain Monte Carlo" /><category scheme="http://www.blogger.com/atom/ns#" term="Languages" /><category scheme="http://www.blogger.com/atom/ns#" term="Cython" /><category scheme="http://www.blogger.com/atom/ns#" term="Just-in-time compilation" /><category scheme="http://www.blogger.com/atom/ns#" term="CPython" /><category scheme="http://www.blogger.com/atom/ns#" term="python" /><category scheme="http://www.blogger.com/atom/ns#" term="Pypy" /><title>Efficcient MCMC in Python</title><summary>I have recently come across a very interesting blog. That is, interesting for people like me, who are enthusiasts of Statistics, programming and their combination expressed preferably in the Python language. One recent post of that blog, caught my attention, as it offered a comparison between MCMC  implementations of a simple  Gibbs sampler in multiple languages, namely: R, Python, Java and </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/5599834357026795857/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=5599834357026795857" title="7 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/5599834357026795857?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/5599834357026795857?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/yLqFBYOuPcY/efficcient-mcmc-in-python.html" title="Efficcient MCMC in Python" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>7</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2010/12/efficcient-mcmc-in-python.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IMQnY4fip7ImA9Wx5bEUU.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-8291512518592160068</id><published>2010-10-22T10:07:00.039-02:00</published><updated>2010-10-27T11:19:43.836-02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-10-27T11:19:43.836-02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="PyQt" /><category scheme="http://www.blogger.com/atom/ns#" term="Latex" /><category scheme="http://www.blogger.com/atom/ns#" term="MathJax" /><category scheme="http://www.blogger.com/atom/ns#" term="python" /><category scheme="http://www.blogger.com/atom/ns#" term="Qt" /><title>Model-Builder: the road to 1.0</title><summary>Model-Builder is a niche educational software and the first "largish" Python application I ever wrote, way back in 2001. Back then, WxPython seemed like the easiest way to develop a GUI application inPython, mainly due to the automation provided by the IDE Boa-constructor.A lot has changed since then and for many years now, my favorite GUI Toolkit has been Qt via it's Python binding, PyQt. For a </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/8291512518592160068/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=8291512518592160068" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8291512518592160068?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8291512518592160068?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/KFI8Sch4fhM/model-builder-road-to-10.html" title="Model-Builder: the road to 1.0" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2010/10/model-builder-road-to-10.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU4FRng8cSp7ImA9Wx5RFUw.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-7952677028070060373</id><published>2010-08-22T17:21:00.009-03:00</published><updated>2010-08-22T18:51:57.679-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-22T18:51:57.679-03:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Cloud computing" /><category scheme="http://www.blogger.com/atom/ns#" term="Open source" /><category scheme="http://www.blogger.com/atom/ns#" term="Free Software" /><category scheme="http://www.blogger.com/atom/ns#" term="python" /><category scheme="http://www.blogger.com/atom/ns#" term="Free" /><category scheme="http://www.blogger.com/atom/ns#" term="Google AppEngine" /><title>Python in the Clouds</title><summary>Consegi 2010 is over.  It was a great meeting! I was happily suprised to realize how far the adoption of free software has come in the last few years. Congratulations to the Free Software community for such a successful lobby!Big thanks are due to Giuseppe (@gsromag) , Luiz Guilherme (@aldabalde)  and their colleagues from SERPRO,  who where responsible for the or ganization of this amazing </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/7952677028070060373/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=7952677028070060373" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7952677028070060373?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7952677028070060373?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/o-lv-mCiumo/python-in-clouds.html" title="Python in the Clouds" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2010/08/python-in-clouds.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEUHR3c8fSp7ImA9WxFaEk0.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-2852567878718817255</id><published>2010-07-15T09:09:00.007-03:00</published><updated>2010-07-15T10:57:16.975-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-15T10:57:16.975-03:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Cloud computing" /><title>Consegi 2010</title><summary>I have been invited to give a talk on the 3rd International Congress on Free Software and E-Government -- Consegi, taking place in Brasilia on 18-20 of august. It is a massive event bringing together Leading professionals from all over the world. Last year's event had 6000 participants from 19 countries!This year's theme is cloud computing and I'll bee talking about Google AppEngine (GAE). Since </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/2852567878718817255/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=2852567878718817255" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2852567878718817255?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2852567878718817255?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/hRtPlDoO2a4/consegi-2010.html" title="Consegi 2010" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2010/07/consegi-2010.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkQFQHY4fSp7ImA9WxFWFUg.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-1163689374184075457</id><published>2010-06-03T05:38:00.001-03:00</published><updated>2010-06-03T05:38:31.835-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-06-03T05:38:31.835-03:00</app:edited><title>PyBrain</title><summary>Just came across this interesting python library for machine learning. People interested in this should also checkout Peach: http://code.google.com/p/peach/acerca de: http://pybrain.org/pages/features (ver no Google Sidewiki)</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/1163689374184075457/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=1163689374184075457" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1163689374184075457?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1163689374184075457?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/Dz-wDa-0JtQ/pybrain.html" title="PyBrain" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2010/06/pybrain.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU8DQXoyfyp7ImA9WxFSFkQ.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-602212831469165971</id><published>2010-04-19T14:04:00.004-03:00</published><updated>2010-04-19T14:24:30.497-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-04-19T14:24:30.497-03:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Math" /><category scheme="http://www.blogger.com/atom/ns#" term="Liveplots" /><category scheme="http://www.blogger.com/atom/ns#" term="Gnuplot" /><category scheme="http://www.blogger.com/atom/ns#" term="Servers" /><category scheme="http://www.blogger.com/atom/ns#" term="Graphing" /><title>New Liveplots Release</title><summary>I recently blogged about Liveplots. I have just released another version with a very important improvement. Before, even though plot server was running on a separate process, there was still a small overhead for the calling code since the plotting function had to be evaluated (and data piped to Gnuplot) before the execution returned to your simulation. To improve matters, I have implemeted </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/602212831469165971/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=602212831469165971" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/602212831469165971?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/602212831469165971?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/s-S6hnesAZs/new-liveplots-release.html" title="New Liveplots Release" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2010/04/new-liveplots-release.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ck8GRn4zfCp7ImA9WxFSE0k.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-836889655486656411</id><published>2010-04-15T10:40:00.008-03:00</published><updated>2010-04-15T11:13:47.084-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-04-15T11:13:47.084-03:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Programming" /><category scheme="http://www.blogger.com/atom/ns#" term="Linux" /><category scheme="http://www.blogger.com/atom/ns#" term="Event-driven programming" /><category scheme="http://www.blogger.com/atom/ns#" term="python" /><category scheme="http://www.blogger.com/atom/ns#" term="Gnuplot" /><category scheme="http://www.blogger.com/atom/ns#" term="Source code" /><title>Liveplots package</title><summary>I have recently released a package I had been using privately for a while. It's called Liveplots and is a package which provides the tools for monitoring computationally intensive, long running numerical simulations. I am aware that similar tools for Java, like Livegraph. But I needed something that was light, simple, and in Python.Liveplots provide a daemonized plot server (i.e. running as a </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/836889655486656411/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=836889655486656411" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/836889655486656411?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/836889655486656411?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/qzIJ3-cFWPk/liveplots-package.html" title="Liveplots package" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>4</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2010/04/liveplots-package.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0cMQXk_eCp7ImA9WxFTFEU.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-8987121683979753490</id><published>2010-04-05T12:25:00.008-03:00</published><updated>2010-04-05T13:31:20.740-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-04-05T13:31:20.740-03:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Random number generation" /><category scheme="http://www.blogger.com/atom/ns#" term="Prior probability" /><category scheme="http://www.blogger.com/atom/ns#" term="Statistics" /><category scheme="http://www.blogger.com/atom/ns#" term="Probability distribution" /><title>Automatic Parameterization of Scipy's Random Number Generators</title><summary>I am working on a new version of Model-Builder, which will incorporate Uncertainty analysis features based on my BIP package.One key aspect of doing uncertainty analysis, is the ability to attribute prior distributions to the model's parameters, and programatically, this is easily accomplished through the use of scipy.stats random number generators which provide a large variety of both continuous</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/8987121683979753490/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=8987121683979753490" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8987121683979753490?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8987121683979753490?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/LubsRZPIkPo/automatic-parameterization-of-scipys.html" title="Automatic Parameterization of Scipy's Random Number Generators" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>4</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2010/04/automatic-parameterization-of-scipys.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEEDRH87eSp7ImA9WxBbGU8.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-3861924588211793226</id><published>2010-03-18T12:30:00.004-03:00</published><updated>2010-03-18T12:37:55.101-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-03-18T12:37:55.101-03:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Language" /><category scheme="http://www.blogger.com/atom/ns#" term="Translation" /><category scheme="http://www.blogger.com/atom/ns#" term="python" /><category scheme="http://www.blogger.com/atom/ns#" term="Google Translate" /><title>Converting C code to Python</title><summary>This may sound like a weird thing to do, but actually, I have craved for something like that every time I have to read C code. Converting C code to Python, can not only help us understand code more easily, but also turn non perfomance-critical code easier to maintain. C can be easy enough to read if well-written and formatted (indented) adequately, however having to move back and forth between .h</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/3861924588211793226/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=3861924588211793226" title="8 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3861924588211793226?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3861924588211793226?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/Jq55F8NGQyI/converting-c-code-to-python.html" title="Converting C code to Python" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>8</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2010/03/converting-c-code-to-python.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU8EQnwzeCp7ImA9WxBUEUQ.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-7540222353643744731</id><published>2010-02-26T11:16:00.001-03:00</published><updated>2010-02-26T11:16:43.280-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-02-26T11:16:43.280-03:00</app:edited><title>Utopia</title><summary>Interesting post, But hoping to invert those proportions, i.e., making the smarter guys the 80% is harder that having a society where everyone earns more money than they can spend... Pretty next to impossible...;-)in reference to: Coding Horror: The Two Types of Programmers (view on Google Sidewiki)</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/7540222353643744731/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=7540222353643744731" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7540222353643744731?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7540222353643744731?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/naS1xF5km_w/utopia.html" title="Utopia" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2010/02/utopia.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMCQ3syfCp7ImA9WxBTF0U.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-1123828241350127968</id><published>2009-12-14T08:27:00.001-02:00</published><updated>2009-12-14T08:27:42.594-02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-12-14T08:27:42.594-02:00</app:edited><title>LaTeX Tikz examples</title><summary>I am currently working on a presentation where I have to include a lot of mathematical graphs, so instead of plotting using matplotlib and inserting the result as a figure, I am considering using specialized LaTeX packages to create the graphs. While searching for documentation, I found this great repository of examples for the Tikz package.referente a: http://www.texample.net/tikz/examples/ (ver</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/1123828241350127968/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=1123828241350127968" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1123828241350127968?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1123828241350127968?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/fWVbbcVjIFw/latex-tikz-examples.html" title="LaTeX Tikz examples" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>5</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/12/latex-tikz-examples.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkQGSXs4eyp7ImA9WxNbFk8.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-4547637543559404172</id><published>2009-11-19T06:10:00.004-02:00</published><updated>2009-11-19T06:45:28.533-02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-19T06:45:28.533-02:00</app:edited><title>Developing a Wave Robot in Python</title><summary>I have been so busy lately that I almost forgot to write about my lightning venture into writing a Google Wave robot: Trendy.For those of you living under a rock in the last several months, Google Wave offers an API for the development of robot, which are... well, robots, which when added to waves, do automated tasks with its contents. There are robots for translating, do syntax highlighting on </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/4547637543559404172/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=4547637543559404172" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/4547637543559404172?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/4547637543559404172?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/eUcxueWYebE/dveloping-wave-robot.html" title="Developing a Wave Robot in Python" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/11/dveloping-wave-robot.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0IBRHwyfSp7ImA9WxNVEk0.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-3430892466512580152</id><published>2009-10-22T09:05:00.001-02:00</published><updated>2009-10-22T09:05:55.295-02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-22T09:05:55.295-02:00</app:edited><title>ASCII Histograms</title><summary>I have recently come across an interestng problem while working on my random variable implementation for BIP. Any type in Python is expected to have a __str__(self) method which returns an adequate and expressive string representation of the object. Well, as far as I could think, the most straightforward representation of a random variable is its probability distribution. Probability </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/3430892466512580152/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=3430892466512580152" title="8 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3430892466512580152?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3430892466512580152?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/xmZNRFfsBtg/ascii-histograms.html" title="ASCII Histograms" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>8</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/10/ascii-histograms.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A04FR3kyeyp7ImA9WxNXEk8.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-1275895338508074330</id><published>2009-09-29T10:11:00.001-03:00</published><updated>2009-09-29T10:11:56.793-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-29T10:11:56.793-03:00</app:edited><title>The Internet Manifesto</title><summary>This document is a must read (see link at the end).I want to add my own items to it:1. Net Neutrality is not only protecting Internet content provider corporations' profitsWe need to defend net neutrality in a way which goes beyond what is currently done: We need to establish fixed ip addresss for every private individual so that publishing rights don't have to be gatekeeped by large corporations</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/1275895338508074330/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=1275895338508074330" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1275895338508074330?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1275895338508074330?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/TPwteFiOTvc/internet-manifesto.html" title="The Internet Manifesto" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>3</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/internet-manifesto.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0QASHk5fSp7ImA9WxNXEU4.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-2487339663708522536</id><published>2009-09-28T06:49:00.001-03:00</published><updated>2009-09-28T06:49:09.725-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-28T06:49:09.725-03:00</app:edited><title>Python(x,y) A Scientific Python Distribution</title><summary>I recently came across, this interesting, opensource Python Scientific Distribution for Windows. I normally don't pay too much attention to windows tools, but it's good to have something to recommend to windows users when you want them to try out some Python code. For Linux users, it's not really relevant, because we all have powerfull package managers to help us get most Python packages </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/2487339663708522536/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=2487339663708522536" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2487339663708522536?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2487339663708522536?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/XHLMf9vl800/pythonxy-scientific-python-distribution.html" title="Python(x,y) A Scientific Python Distribution" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>3</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/pythonxy-scientific-python-distribution.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0IFRHY8cSp7ImA9WxNQF0U.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-7432476178969952020</id><published>2009-09-24T07:51:00.001-03:00</published><updated>2009-09-24T07:51:55.879-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-24T07:51:55.879-03:00</app:edited><title>Scientific Python Group at LinkedIn</title><summary>I have just created a Scientific Python Group at LinkedIn. I was actually surprised that there wasn't one already.Python is quickly becoming a major tool in scientific computing and we should all do our best to advertise its capabilities.referente a: Scientific Python Group | LinkedIn (ver no Google Sidewiki)</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/7432476178969952020/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=7432476178969952020" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7432476178969952020?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7432476178969952020?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/3wdmWF4nRqA/scientific-python-group-at-linkedin.html" title="Scientific Python Group at LinkedIn" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/scientific-python-group-at-linkedin.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0cBRHs7eSp7ImA9WxNQEk0.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-3432521621967114419</id><published>2009-09-17T11:41:00.008-03:00</published><updated>2009-09-17T12:24:15.501-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-17T12:24:15.501-03:00</app:edited><title>Violin Plot with Matplotlib</title><summary>One of the things I sorely missed from matplotlib for a very long time,  was a violin plot implementation. Many a time, I thought about implementing one myself, but never found the time.Today, browsing through Matplotlib's documentation, I found the recently added fill_betweenx function. Finally it seemed to have become a piece of cake to implement a violin plot. I Googled for violin plot and </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/3432521621967114419/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=3432521621967114419" title="8 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3432521621967114419?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3432521621967114419?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/3eJwjQw5_AM/violin-plot-with-matplotlib.html" title="Violin Plot with Matplotlib" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_lq_qzMa71Ns/SrJSildeV9I/AAAAAAAAAlw/1z16wN46WZc/s72-c/violin.png" height="72" width="72" /><thr:total>8</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/violin-plot-with-matplotlib.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ck4AQXw9fyp7ImA9WxNRFkU.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-1939601755298551830</id><published>2009-09-11T11:52:00.002-03:00</published><updated>2009-09-11T11:55:40.267-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-11T11:55:40.267-03:00</app:edited><title>Why Python</title><summary>I recently came across a repository of jewels in the form of the unpublished manuscripts of E.W. Dijkstra. I just finished reading one entitled "Some Meditations on Advanced Programming". It is amazingly well written and still so relevant to present-day computer science, that I recommend anyone with at least a passing interest on the subject to read it. I was pleasantly surprised to find in the </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/1939601755298551830/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=1939601755298551830" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1939601755298551830?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1939601755298551830?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/NRAFOg9C_pU/why-python.html" title="Why Python" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/why-python.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0QDRXY9fCp7ImA9WxNSGEQ.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-3567186964742670572</id><published>2009-09-02T10:27:00.003-03:00</published><updated>2009-09-02T10:49:34.864-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-02T10:49:34.864-03:00</app:edited><title>New-style String Formatting and LaTeX</title><summary>The recommended new way (since 2.6) of doing string formating in Python is to use the format method of string objects instead of the % operator and %s (and variants) placemarks.I decided to check it out to generate some LaTeX tables programatically. Bad Idea. the  method expects placemarks like this: "some string {key}".format(key=123) and that is a big problem when formatting LaTeX strings. </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/3567186964742670572/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=3567186964742670572" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3567186964742670572?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3567186964742670572?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/QngeanAfUdA/new-style-string-formatting-and-latex.html" title="New-style String Formatting and LaTeX" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>5</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/new-style-string-formatting-and-latex.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D08EQXk9fSp7ImA9WxJUEkg.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-780597518430419776</id><published>2009-07-10T16:28:00.002-03:00</published><updated>2009-07-10T16:56:40.765-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-10T16:56:40.765-03:00</app:edited><title>Chrome OS and Google World Domination</title><summary>The web platform is starting to get annoying in its attempt to re-invent and re-create everything that previously existed in the Desktop space.Finally, Desktop developers are beginning to wake up to this problem.For years, browser-developing companies have tried to turn the Browser into an operating-system-like autonomous system. While the rest of us were trying to figure out how to get our </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/780597518430419776/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=780597518430419776" title="11 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/780597518430419776?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/780597518430419776?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/7ANRMF1u9U0/chrome-os-and-google-world-domination.html" title="Chrome OS and Google World Domination" /><author><name>Flavio Coelho</name><uri>https://plus.google.com/106488325672572942691</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-vO4vKFIzknI/AAAAAAAAAAI/AAAAAAAAC8k/tDa-Q3Ur0uw/s512-c/photo.jpg" /></author><thr:total>11</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/07/chrome-os-and-google-world-domination.html</feedburner:origLink></entry></feed>
