wradlibhttp://wradlib.org/2016-08-31T13:00:00+02:00Release 0.9.02016-08-31T13:00:00+02:00wradlibtag:wradlib.org,2016-08-31:2016/08/wradlib_release_0_9_0/<p>With this post, we announce the release of wradlib 0.9.0. It finalizes our transition from example Python scripts to jupyter notebooks (as already announced in a <a href="http://wradlib.org/2016/04/introducing-wradlib-jupyter-notebooks/">previous post</a>). As a result, the documentation pages have become more consistent, and the handling of examples and tutorials more convenient and interactive. We hope you&#8217;ll&nbsp;agree!</p> <h3>Interactive examples with jupyter&nbsp;notebooks</h3> <p>As a consequence, the previous doc sections &#8220;Tutorials&#8221; and &#8220;Recipes&#8221; have been replaced by one single section <a href="http://wradlib.org/wradlib-docs/latest/notebooks.html">Tutorials and Examples</a>. The pages in that section were automatically built from jupyter (IPython) notebooks. These notebooks are distributed with the <a href="https://pypi.python.org/pypi/wradlib">new release</a>, and you can use them to interactively browse through our tutorials and examples. You can always download the latest notebooks from the <a href="https://github.com/wradlib/wradlib/tree/master/notebooks">wradlib repository</a>.</p> <p>For those who do not know, yet, how to handle jupyter notebooks, we prepared a <a href="http://wradlib.org/wradlib-docs/latest/jupyter.html">quick tutorial</a>. We also added a brief (and certainly incomplete) <a href="http://wradlib.org/wradlib-docs/latest/notebooks/learnpython.html">intro to Python</a> for those who would like to have some entry point to that language. This intro will certainly be further developed in the&nbsp;future.</p> <p>In case you don&#8217;t want to use notebooks: straight Python scripts are distributed alongside the notebooks with <a href="https://pypi.python.org/pypi/wradlib">each new release &gt;= 0.9.0</a>.</p> <h3>Get the example data from the new wradlib data&nbsp;repository</h3> <p>We moved all the example data from the main <a href="https://github.com/wradlib/wradlib/">wradlib repository</a> to a new <a href="https://github.com/wradlib/wradlib-data">data repository</a>. In order to run the notebooks on your computer, you need to download the example data archive yourself, and extract it to any directory on your computer. Then you need to create an environment variable pointing to that directory. After that, the example notebooks will automagically pull the required example data from that directory. See <a href="http://wradlib.org/wradlib-docs/latest/jupyter.html#how-can-i-get-the-example-data">here</a> for more detailed guidance on the&nbsp;process. </p> <h3>Further changes in wradlib&nbsp;0.9.0</h3> <p>Along with wradlib 0.9.0, we also released a couple of minor, though hopefully useful new features and fixes,&nbsp;e.g.:</p> <ul> <li><code>wradlib.io.read_RADOLAN_composite</code> can now read the new radolan <a href="https://github.com/wradlib/wradlib/pull/73"><span class="caps">FZ</span> product</a>,</li> <li><code>wradlib.io.readDX</code> can now read gzipped <span class="caps">DX</span>&nbsp;data,</li> <li><code>wradlib.io.read_Rainbow</code> was enhanced to read product pixmap data from rainbow5&nbsp;files,</li> <li>fixed <a href="https://github.com/wradlib/wradlib/issues/86">incompatibility issue with scipy 0.18.0</a>,</li> <li>and fixed some other&nbsp;issues.</li> </ul> <p>For more details on the new release, please visit our <a href="http://wradlib.org/wradlib-docs/0.9.0/">release notes</a>.</p> <h3>Updating to wradlib&nbsp;0.9.0</h3> <p>Do you want to safely check out the new version and still keep the old one? Then you can install wraldib 0.9.0 into a new conda environment, e.g. like&nbsp;this: </p> <div class="codehilite"><pre><span></span>$ conda config --add channels conda-forge $ conda create --name wradlib090 <span class="nv">python</span><span class="o">=</span>2.7 $ activate wradlib090 $ conda install wradlib </pre></div> <p>You can drop the first line if you already added the conda-forge&nbsp;channel.</p> <p>For more details, or if you do not use Anaconda or conda, see our <a href="http://wradlib.org/wradlib-docs/latest/gettingstarted.html">installation instructions</a>. </p> <p>In case you lost track of your Anaconda environments, you can&nbsp;use</p> <div class="codehilite"><pre><span></span>$ conda --info envs </pre></div> <p>in order to get an overview. You can list all the packages (and their versions) in an environment (let&#8217;s say wradlib090)&nbsp;via</p> <div class="codehilite"><pre><span></span>$ conda list --name wradlib090 </pre></div> <h3>For&nbsp;developers</h3> <p>Untagged <span class="caps">MICRO</span>-releases (0.9.1 and so on) are now released on <a href="https://testpypi.python.org/pypi/wradlib/">testpypi</a>. In the future, we hope to adopt this for <a href="https://anaconda.org/conda-forge/wradlib">conda-forge</a>, too. This might be interesting for users, too, for early checking of bug fixes (in case they do not want to use the bleeding edge&nbsp;code). </p>Release 0.8.02016-03-10T13:00:00+01:00wradlibtag:wradlib.org,2016-03-10:2016/03/wradlib_release_0_8_0/<p>As already announced in previous articles (<a href="http://wradlib.org/2016/02/wradlib-at-github/">#1</a>, <a href="http://wradlib.org/2016/02/wradlib-python3-compatibility/">#2</a>), we entirely moved our code development from <a href="https://bitbucket.org/wradlib/wradlib">bitbucket</a> to <a href="https://github.com/wradlib">github</a>, and applied a major code revision to make wradlib compatible with both Python 2.7 and 3.5. The tremendous efforts to achieve this have been spearheaded by Kai Muehlbauer (University of Bonn). Thanks also to Jonathan J. Helmus from Argonne National Laboratory for valuable advice in the transition&nbsp;period. </p> <p>Please understand that the <a href="https://bitbucket.org/wradlib/wradlib">bitbucket repository</a> will no longer be updated, and only hosted as legacy&nbsp;code.</p> <p>wradlib 0.8.0 is the first release that follows upon this major transition. As a user, you should (hopefully) not feel much of a difference. The most obvious change is that you will now find the library documentation on <a href="http://wradlib.org/wradlib-docs">http://wradlib.org/wradlib-docs</a>. <a href="http://wradlib.org">http://wradlib.org</a> itself will serve as a new central service to keep you updated on new&nbsp;developments. </p> <p>You can keep on installing new wradlib releases with the <code>pip install</code> mechanism. Cloning the bleeding edge code will require to install a <code>git</code> client and point it to <a href="https://github.com/wradlib/wradlib">https://github.com/wradlib/wradlib</a>. Developers are cordially invited to fork from that repository and share their developments via Pull&nbsp;Requests.</p> <p>Apart from these changes, wradlib 0.8.0 includes a couple of improvements particularly related to the <a href="http://wradlib.org/wradlib-docs/latest/zonalstats.html">zonalstats module</a>. Please expect further changes to that module in the future, making it more generic and more&nbsp;convenient.</p> <p>We are now using Travis <span class="caps">CI</span> to continuously scrutinize the integrity of our codebase. Still, the transition might imply a couple issues that we have not yet identified. Please bear with us, and do not hesitate to report issues <a href="https://github.com/wradlib/wradlib/issues">here</a>, or to seek help in our <a href="https://groups.google.com/forum/?fromgroups#!forum/wradlib-users">user forum</a>. </p>wradlib goes toward python32016-02-29T14:45:00+01:00wradlibtag:wradlib.org,2016-02-29:2016/02/wradlib-python3-compatibility/<p>With <a href="https://github.com/wradlib/wradlib/pull/5">Pull Request #5</a> we made the first step to have wradlib support Python3. All tests are running fine now, so we consider this a straight conversion. Nevertheless, there is an <a href="https://github.com/wradlib/wradlib/issues/8">open issue</a> which gets hold of remaining conversion problems. If you find a bug or issue, please report it&nbsp;there.</p>wradlib moves to github.com2016-02-29T14:00:00+01:00wradlibtag:wradlib.org,2016-02-29:2016/02/wradlib-at-github/<p>After over a year of reflection and thoughts, we finally decided to move from <a href="http://bitbucket.org/wradlib/wradlib">bitbucket</a> to <a href="https://github.com/wradlib/wradlib">github</a>.</p> <p>This means also to switch the versioning system from <em>mercurial</em> to <em>git</em>. The repository was transferred to git via hg-git. Thus, the commit history is available right from the beginning. The <a href="http://bitbucket.org/wradlib/wradlib">wradlib repo at bitbucket</a> will be left available for&nbsp;reference.</p> <p>The first step on github was setting up continuous integration, which works fine with <a href="https://travis-ci.org">Travis-<span class="caps">CI</span></a>. Within this process the wradlib docs are made available at <a href="http://wradlib.github.io/wradlib-docs/">wradlib-docs</a>. The whole process is not yet finished, so <a href="https://github.com/wradlib/wradlib/issues/6">stay tuned</a>.</p>