<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to KeplerWeka</title><link>https://sourceforge.net/p/keplerweka/wiki/KeplerWeka/</link><description>Recent changes to KeplerWeka</description><atom:link href="https://sourceforge.net/p/keplerweka/wiki/KeplerWeka/feed" rel="self"/><language>en</language><lastBuildDate>Tue, 20 May 2014 20:58:17 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/keplerweka/wiki/KeplerWeka/feed" rel="self" type="application/rss+xml"/><item><title>KeplerWeka modified by Peter Reutemann</title><link>https://sourceforge.net/p/keplerweka/wiki/KeplerWeka/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;&lt;img alt="Kepler logo" src="/apps/trac/keplerweka/raw-attachment/wiki/KeplerWeka/kepler-logo.png" /&gt; &lt;img alt="Ptolemy II logo" src="/apps/trac/keplerweka/raw-attachment/wiki/KeplerWeka/ptIIplanet.gif" /&gt; &lt;img alt="" src="/apps/trac/keplerweka/raw-attachment/wiki/KeplerWeka/Weka%20%28software%29%20logo.png" /&gt;&lt;/p&gt;
&lt;p&gt;While working on a project at the &lt;a class="" href="http://www.waikato.ac.nz/" rel="nofollow"&gt;University of Waikato&lt;/a&gt;, I needed a workflow engine based on Java, that would allow me to implement my own components. After searching the web and a few initial tests, the choice fell on &lt;a class="" href="http://kepler-project.org/" rel="nofollow"&gt;Kepler&lt;/a&gt;, an open-source, scientific workflow engine, released under the &lt;a class="" href="http://www.opensource.org/licenses/bsd-license.php" rel="nofollow"&gt;BSD licence&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;Kepler is based on the &lt;a class="" href="http://ptolemy.berkeley.edu/ptolemyII/" rel="nofollow"&gt;Ptolemy II&lt;/a&gt; system, a mature platform supporting multiple models of computation suited to distinct types of analysis (processing sensor data, for example, or integrating differential equations). Even though it provides a graphical user interface, normally used for modeling, workflows can also be executed from command-line. What I really liked about Kepler, was the ability to run flows on grids and its inherent support for multi-core architectures. &lt;/p&gt;
&lt;p&gt;Since the aforementioned project also needed some basic support for &lt;a class="" href="http://www.cs.waikato.ac.nz/~ml/weka/" rel="nofollow"&gt;WEKA&lt;/a&gt;, I started out on creating WEKA actors (an &lt;em&gt;actor&lt;/em&gt; is an atomic component in a Kepler workflow). In order to enable WEKA's GenericObjectEditor in Kepler, I needed to patch the underlying Ptolemy II system. My contributions ([[1]](/apps/trac/keplerweka/wiki/CustomQueryBoxesInPtolemy), [[2]](/apps/trac/keplerweka/wiki/CustomQueryBoxesInPtolemy2)) were surprisingly quickly accepted and integrated. Such an active developer community was another bonus for Kepler/Ptolemy II. &lt;/p&gt;
&lt;p&gt;Since I thought, that other people might be interested in my WEKA add-ons for Kepler as well, I started up a project page (first on my university homepage and now on sf.net) to make these actors publicly available: &lt;strong&gt;&lt;a class="alink" href="/p/keplerweka/wiki/KeplerWeka/"&gt;[KeplerWeka]&lt;/a&gt;&lt;/strong&gt; was born. &lt;/p&gt;
&lt;p&gt;A final word on the license: all WEKA actors are, just like WEKA, released under the &lt;a class="" href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html" rel="nofollow"&gt;GNU General Public License (version 2)&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;-- &lt;em&gt;FracPete&lt;/em&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Reutemann</dc:creator><pubDate>Tue, 20 May 2014 20:58:17 -0000</pubDate><guid>https://sourceforge.net26cf512c5137de507fb9d1c6522b399a972e3bb2</guid></item></channel></rss>