Deployed 7201e4e with MkDocs version: 1.4.2

adding_tabs_in_the_explorer/index.html

@@ -743,10 +743,10 @@ <h1>Description</h1>
 
 <h3 id="description">Description<a class="headerlink" href="#description" title="Permanent link">#</a></h3>
 <p>This article explains how to add extra tabs in the Explorer in order to add new functionality without the hassle of having to dig into the Explorer code oneself. With the new plugin-architecture of the Explorer it is fairly easy making your extensions available in the GUI.</p>
-<p><strong>Note:</strong> This is also covered in chapter <em>Extending WEKA</em> of the WEKA manual in versions later than 3.6.1/3.7.0 or <a href="../snapshots/">snapshots</a> of the stable-3.6/developer version later than 10/01/2010.</p>
+<p><strong>Note:</strong> This is also covered in chapter <em>Extending WEKA</em> of the WEKA manual in versions later than 3.6.1/3.7.0 of the stable-3.6/developer version later than 10/01/2010.</p>
 <h3 id="version">Version<a class="headerlink" href="#version" title="Permanent link">#</a></h3>
 <blockquote>
-<p>3.5.5 or <a href="../snapshots/">Snapshot</a></p>
+<p>3.5.5</p>
 </blockquote>
 <h3 id="requirements">Requirements<a class="headerlink" href="#requirements" title="Permanent link">#</a></h3>
 <p>Here is roughly what is required in order to add a new tab (the examples go into more detail):</p>

downloading_weka/index.html

@@ -66,7 +66,7 @@
     <div data-md-component="skip">
 
 
-        <a href="#snapshots" class="md-skip">
+        <a href="#stable-version" class="md-skip">
           Skip to content
         </a>
 
@@ -253,13 +253,6 @@
     </label>
     <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
 
-        <li class="md-nav__item">
-  <a href="#snapshots" class="md-nav__link">
-    Snapshots
-  </a>
-
-</li>
-
         <li class="md-nav__item">
   <a href="#stable-version" class="md-nav__link">
     Stable version
@@ -715,13 +708,6 @@
     </label>
     <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
 
-        <li class="md-nav__item">
-  <a href="#snapshots" class="md-nav__link">
-    Snapshots
-  </a>
-
-</li>
-
         <li class="md-nav__item">
   <a href="#stable-version" class="md-nav__link">
     Stable version
@@ -862,8 +848,7 @@ <h1>Downloading and installing Weka</h1>
 
 <p>There are two versions of Weka: Weka 3.8 is the latest stable version
 and Weka 3.9 is the development version. New releases of these two versions
-are normally made once or twice a year. For the bleeding edge, it is
-also possible to download nightly snapshots of these two versions. </p>
+are normally made once or twice a year. </p>
 <p>The stable version receives only bug fixes and feature upgrades that
 do not break compatibility with its earlier releases, while the
 development version may receive new features that break compatibility
@@ -872,13 +857,6 @@ <h1>Downloading and installing Weka</h1>
 easy for the Weka community to add new functionality to Weka. The
 package management system requires an internet connection in order to
 download and install packages.</p>
-<h3 id="snapshots">Snapshots<a class="headerlink" href="#snapshots" title="Permanent link">#</a></h3>
-<p>Every night, a snapshot of the <a href="../git/">Git</a> repository with the Weka
-source code is taken, compiled, and put together in ZIP files. This
-happens for both the development branch of the software and the stable
-branch. Those who want the latest bug fixes before the next official
-release is made can download these
-<a href="https://ml.cms.waikato.ac.nz/weka/snapshots/weka_snapshots.html">snapshots</a>.</p>
 <h3 id="stable-version">Stable version<a class="headerlink" href="#stable-version" title="Permanent link">#</a></h3>
 <p>Weka 3.8 is the latest stable version of Weka. This branch of Weka
 only receives bug fixes and upgrades that do not break compatibility

faqs/how_do_i_perform_one_class_classification/index.html

@@ -574,7 +574,7 @@ <h1>How do i perform one class classification</h1>
 <p>WEKA offers some rudimentary support for one-class classfication:</p>
 <ul>
 <li>via the <code>weka.classifiers.functions.LibSVM</code> wrapper classifier (stable 3.6 and developer version). See the <a href="../../lib_svm/">LibSVM</a> article for more information.</li>
-<li>via the <code>weka.classifiers.meta.OneClassClassifier</code> meta-classifier (developer version &gt;3.7.0 or <a href="../../snapshots/">snapshot</a> later than 23/7/2009)</li>
+<li>via the <code>weka.classifiers.meta.OneClassClassifier</code> meta-classifier (developer version &gt;3.7.0)</li>
 </ul>
 
 

faqs/how_do_i_use_wekas_classes_in_my_own_code/index.html

@@ -578,8 +578,8 @@ <h1>How do i use wekas classes in my own code</h1>
 </ul>
 <p>Further resources:</p>
 <ul>
-<li>Check out the chapter <em>Using the API</em> in the Weka manual (<a href="../../snapshots/">snapshots</a> later than 09/08/2009 and releases &gt;3.6.1 and &gt;3.7.0).</li>
-<li>The <a href="../../weka_examples/">Weka Examples</a> collection is a an <a href="../../ant/">ANT</a> project that is available through <a href="../../snapshots/">snapshots</a> and releases later than 09/08/2009, containing a lot of example classes.</li>
+<li>Check out the chapter <em>Using the API</em> in the Weka manual (releases &gt;3.6.1 and &gt;3.7.0).</li>
+<li>The <a href="../../weka_examples/">Weka Examples</a> collection is a an <a href="../../ant/">ANT</a> project that is available through releases later than 09/08/2009, containing a lot of example classes.</li>
 </ul>
 <p><strong>Note:</strong> WEKA is open-source software under the <a href="http://www.gnu.org/copyleft/gpl.html">GNU General Public License</a>, which means that your code has to be licensed under the GPL as well.</p>
 

faqs/how_do_i_write_a_new_classifier_or_filter/index.html

@@ -577,7 +577,7 @@ <h1>How do i write a new classifier or filter</h1>
 <li><a href="../../writing_filter/">Writing your own Filter</a></li>
 </ul>
 <p>If your scheme is outside the usual WEKA packages, you need to make WEKA aware of this package in order to be able to use it in the GUI as well. See <a href="../how_do_i_add_a_new_classifier_filter_kernel_etc/">How do I add a new classifier, filter, kernel, etc?</a> for more information about this.</p>
-<p><strong>Note:</strong> This is also covered in chapter <em>Extending WEKA</em> of the WEKA manual in versions later than 3.6.1/3.7.0 or <a href="../../snapshots/">snapshots</a> of the stable-3.6/developer version later than 10/01/2010. Furthermore, this chapter also covers clusterers, attribute selection algorithms and associators.</p>
+<p><strong>Note:</strong> This is also covered in chapter <em>Extending WEKA</em> of the WEKA manual in versions later than 3.6.1/3.7.0. Furthermore, this chapter also covers clusterers, attribute selection algorithms and associators.</p>
 
 
 

faqs/latest_bugfixes/index.html

@@ -571,7 +571,7 @@
 
   <h1>Latest bugfixes</h1>
 
-<p>The article <a href="../../get_latest_bugfixes/">How to get the latest bugfixes</a> explains it in detail (it's basically either obtaining the source code from <a href="../../git/">git</a> and compiling it yourself or getting a snapshot from the download section of the <a href="http://cs.waikato.ac.nz/ml/weka/">WEKA homepage</a>).</p>
+<p>The article <a href="../../get_latest_bugfixes/">How to get the latest bugfixes</a> explains it in detail (it's basically either obtaining the source code from <a href="../../git/">git</a> and compiling it yourself.</p>
 
 
 

faqs/pluggable_evaluation_metrics/index.html

@@ -625,7 +625,7 @@
 
   <h1>Pluggable evaluation metrics</h1>
 
-<p>WEKA 3.7.8 (and nightly snapshots of the developer branch of WEKA from 15-11-2012) has a mechanism to allow new classification and regression evaluation metrics to be added as plugins. The new metrics will be output, along with WEKA's standard set of evaluation metrics, in the output generated on the command line, in the Explorer's Classify panel and by the Knowledge Flow's ClassifierPerformanceEvaluator component. Furthermore, new plugin metrics are also available for analysis in the Experimenter.</p>
+<p>WEKA 3.7.8 has a mechanism to allow new classification and regression evaluation metrics to be added as plugins. The new metrics will be output, along with WEKA's standard set of evaluation metrics, in the output generated on the command line, in the Explorer's Classify panel and by the Knowledge Flow's ClassifierPerformanceEvaluator component. Furthermore, new plugin metrics are also available for analysis in the Experimenter.</p>
 <p>Previously, adding a new evaluation metric involved editing and recompiling the monolithic weka.classifiers.Evaluation class - a shudder-worthy undertaking at the best of times. With the new plugin mechanism it is easy to add a new metric and deploy it via the package management system. The "Additional configuration files" section of <a href="../../packages/structure/">How are packages structured for the package management system?</a> details how to tell the PluginManager class about your new plugin evaluation metric.</p>
 <h3 id="classes-and-interfaces">Classes and interfaces<a class="headerlink" href="#classes-and-interfaces" title="Permanent link">#</a></h3>
 <p>The main base class for all new metrics is <code>weka.classifiers.evaluation.AbstractEvaluationMetric</code>. This class requires the following methods to be implemented by concrete sub classes:</p>

generating_source_code_from_weka_classes/index.html

@@ -605,7 +605,7 @@
 
   <h1>Generating source code from weka classes</h1>
 
-<p>Some of the schemes in Weka can generate Java source code that represents their current internal state. At the moment these are classifiers (book and developer version) and filters (<a href="../snapshots/">snapshot</a> or &gt;3.5.6). The generated code can be used within Weka as normal classifier/filter, since this code will be derived from the same superclass (<code>weka.classifiers.Classifier</code> or <code>weka.filters.Filter</code>) as the generating code.</p>
+<p>Some of the schemes in Weka can generate Java source code that represents their current internal state. At the moment these are classifiers (book and developer version) and filters (&gt;3.5.6). The generated code can be used within Weka as normal classifier/filter, since this code will be derived from the same superclass (<code>weka.classifiers.Classifier</code> or <code>weka.filters.Filter</code>) as the generating code.</p>
 <p><strong>Note:</strong> The commands listed here are for a Linux/Unix bash (the backslash tells the shell that the command isn't finished yet and continues on the next line). In case of Windows or the SimpleCLI, just remove the backslashes and put everything on one line.</p>
 <h3 id="classifiers">Classifiers<a class="headerlink" href="#classifiers" title="Permanent link">#</a></h3>
 <p>Instead of using a serialized filter to perform further classifications/predictions, one can also obtain source code from a trained classifier and use this instead. The advantage of this is being less dependent on version changes and incompatible serialized files. All classifiers implementing the <code>weka.classifiers.Sourcable</code> interface can turn their model into Java source code (check the Javadoc of this interface for all the classifiers implementing it).</p>
@@ -623,7 +623,7 @@ <h3 id="classifiers">Classifiers<a class="headerlink" href="#classifiers" title=
 </code></pre></div>
 <strong>Note:</strong> the Explorer can output source code as well, you only have to check the <em>Output source code</em> option in the <em>More options</em> dialog.</p>
 <h3 id="filters">Filters<a class="headerlink" href="#filters" title="Permanent link">#</a></h3>
-<p>With versions of Weka later than 3.5.6 or a <a href="../snapshots/">snapshot</a> of the developer version, one can now also turn filters into source code. The process is basically the same as with classifiers outlined above. All filters that implement the <code>weka.filters.Sourcable</code> interface can be turned into Java code (again, check out the Javadoc for this interface, to see the filters implementing it).</p>
+<p>With versions of Weka later than 3.5.6 of the developer version, one can now also turn filters into source code. The process is basically the same as with classifiers outlined above. All filters that implement the <code>weka.filters.Sourcable</code> interface can be turned into Java code (again, check out the Javadoc for this interface, to see the filters implementing it).</p>
 <p>The following command turns an initialized ReplaceMissingValues filter into source code:</p>
 <p><div class="highlight"><pre><span></span><code><a id="__codelineno-2-1" name="__codelineno-2-1" href="#__codelineno-2-1"></a><span class="w"> </span>java<span class="w"> </span>weka.filters.unsupervised.attribute.ReplaceMissingValues<span class="w"> </span><span class="se">\</span>
 <a id="__codelineno-2-2" name="__codelineno-2-2" href="#__codelineno-2-2"></a><span class="w">   </span>-i<span class="w"> </span>/somewhere1/input.arff<span class="w"> </span><span class="se">\</span>

get_latest_bugfixes/index.html

@@ -572,20 +572,12 @@
   <h1>Get latest bugfixes</h1>
 
 <p>Weka is actively developed, that means that bugs are fixed and new functionality is added (only to the developer version) all the time. Every now and then (about every 6-12 months), when there was a sufficiently large number of improvements or fixes, a release is made and uploaded to <a href="http://sourceforge.net/projects/weka/">Sourceforget.net</a>.</p>
-<p>If you don't want to wait that long, you have two options:</p>
+<p>If you don't want to wait that long, you can get the latest source code from <strong>Git</strong> and compile it yourself. </p>
+<p>See the following articles for more information:</p>
 <ol>
-<li>
-<p>Get the latest source code from <strong>Subversion</strong> and compile it yourself. See the following articles for more information</p>
-<ol>
-<li><a href="../subversion/">obtaining the source code from Subversion</a>, either book or developer version</li>
+<li><a href="../git/">obtaining the source code from Git</a>, either book or developer version</li>
 <li><a href="../compiling_weka/">compiling the source code</a></li>
 </ol>
-</li>
-<li>
-<p>Download a <strong>snapshot</strong> from the download section of the <a href="http://cs.waikato.ac.nz/~ml/weka/">Weka homepage</a>. Snapshots for book and developer version are generated automatically every night, based on the current Subversion code. The <a href="http://en.wikipedia.org/wiki/ZIP_%28file_format%29">ZIP files</a> have the same content as a release, i.e., compiled classes (= weka.jar), source code (= weka-src.jar), Javadoc and other documentation.</p>
-</li>
-</ol>
-<p><strong><em>Note:</em></strong> compare the timestamp of the <a href="../mailing_list/">Weka Mailing List</a> post that reports a bugfix with the one of the snapshot to make sure the bugfix is already included in the snapshot.</p>
 
 
 

making_predictions/index.html

@@ -701,7 +701,7 @@ <h4 id="classifiers">Classifiers<a class="headerlink" href="#classifiers" title=
 <li>Using the <code>-classifications</code> option instead of <code>-p ...</code> you can also use different output formats, like <a href="https://weka.sourceforge.io/doc.stable-3-8/weka/classifiers/evaluation/output/prediction/CSV.html">CSV</a>: <code>-classifications "weka.classifiers.evaluation.output.prediction.CSV -p ..."</code> (the <code>-p</code> option takes the indices of the additional attributes to output).</li>
 </ul>
 <h4 id="filters">Filters<a class="headerlink" href="#filters" title="Permanent link">#</a></h4>
-<p>The <a href="https://weka.sourceforge.io/doc.stable-3-8/weka/filters/supervised/attribute/AddClassification.html">AddClassification</a> filter (package <code>weka.filters.supervised.attribute</code>) can either train a classifier on the input data and transform this or load a serialized model to transform the input data (even though the filter was introduced in 3.5.4, due to a bug in the commandline option handling, it is recommended to download a version &gt;3.5.5 or a snapshot from the Weka homepage).
+<p>The <a href="https://weka.sourceforge.io/doc.stable-3-8/weka/filters/supervised/attribute/AddClassification.html">AddClassification</a> filter (package <code>weka.filters.supervised.attribute</code>) can either train a classifier on the input data and transform this or load a serialized model to transform the input data (even though the filter was introduced in 3.5.4, due to a bug in the commandline option handling, it is recommended to download a version &gt;3.5.5 from the Weka homepage).
 This filter can add the classification, class distribution and the error per row as extra attributes to the dataset.</p>
 <ul>
 <li>training the classifier, e.g., J48, on the input data and replacing the class values with the ones of the trained classifier:</li>
@@ -742,7 +742,7 @@ <h4 id="explorer">Explorer<a class="headerlink" href="#explorer" title="Permanen
 <a id="__codelineno-5-10" name="__codelineno-5-10" href="#__codelineno-5-10"></a>    20          ?        3:3      +   0      0     *1      0      0      0    
 <a id="__codelineno-5-11" name="__codelineno-5-11" href="#__codelineno-5-11"></a>    ...
 </code></pre></div>
-<strong>Note:</strong> The developer version (&gt;3.5.6 or <a href="../snapshots/">snapshot</a>) can also output additional attributes like the commandline with the <code>-p</code> option. In the <em>More options...</em> dialog you can specify those attribute indices with <em>Output additional attributes</em>, e.g., <em>first</em> or <em>1-7</em>. In contrast to the commandline, this output also works for cross-validation.</p>
+<strong>Note:</strong> The developer version (&gt;3.5.6) can also output additional attributes like the commandline with the <code>-p</code> option. In the <em>More options...</em> dialog you can specify those attribute indices with <em>Output additional attributes</em>, e.g., <em>first</em> or <em>1-7</em>. In contrast to the commandline, this output also works for cross-validation.</p>
 <h4 id="knowledgeflow">KnowledgeFlow<a class="headerlink" href="#knowledgeflow" title="Permanent link">#</a></h4>
 <h4 id="using-the-predictionappender">Using the PredictionAppender<a class="headerlink" href="#using-the-predictionappender" title="Permanent link">#</a></h4>
 <p>With the <em>PredictionAppender</em> (from the <em>Evaluation</em> toolbar) you cannot use an already saved model, but you can train a classifier on a dataset and output an <a href="../formats_and_processing/arff/">ARFF</a> file with the predictions appended as additional attribute. Here's an example setup:</p>

optimizing_parameters/index.html

@@ -714,7 +714,7 @@ <h3 id="cvparameterselection">CVParameterSelection<a class="headerlink" href="#c
 </code></pre></div>
 <h3 id="gridsearch">GridSearch<a class="headerlink" href="#gridsearch" title="Permanent link">#</a></h3>
 <p><code>weka.classifiers.meta.GridSearch</code> is a meta-classifier for exploring 2 parameters, hence the <em>grid</em> in the name. If one turns the log on, the classifier will create output suitable for <a href="http://www.gnuplot.info/">gnuplot</a>, i.e., sections of the log will contain script and data sections. Instead of just using a classifier, one can specify a base classifier <strong>and</strong> a filter, which both of them can be optimized (one parameter each). In contrast to <code>CVParameterSelection</code>, <code>GridSearch</code> is not limited to first-level parameters of the base classifier, since it's using <a href="http://java.sun.com/docs/books/tutorial/javabeans/">Java Beans</a> <a href="http://java.sun.com/docs/books/tutorial/javabeans/introspection/">Introspection</a> and one can specify <em>paths</em> to the properties one wants to optimize. A <em>property</em> here is the string of the parameter displayed in the GenericObjectEditor (generated though Introspection), e.g., <code>bagSizePercent</code> or <code>classifier</code> of <code>weka.classifiers.meta.Bagging</code>.</p>
-<p>Due to some important bugfixes, one should obtain a version of Weka &gt;3.5.6 or a <a href="../snapshots/">snapshot</a> later than 11 Sept 2007.</p>
+<p>Due to some important bugfixes, one should obtain a version of Weka &gt;3.5.6 later than 11 Sept 2007.</p>
 <p>For each of the two axes, X and Y, one can specify the following parameters:</p>
 <ul>
 <li><strong>property</strong><blockquote>