Updated to use J48 for base classifier for FilteredClassifierTest.
Updated for 3.7.9
trunk is now 3.7.10-SNAPSHOT
Fixed so that string attributes are handled properly during incremental processing.
Was not indicating finished if there was only an in-memory buffer to output (and no files) - fixed.
Was not handling the end of stream correctly in some cases when running in incremental mode - fixed.
[maven-release-plugin] prepare release weka-dev-3.7.9
[maven-release-plugin] prepare for next development iteration
Now allows multiple incoming testSet connections. This allows a flow to train a model (or load one) and then have multiple separate loaders sending test sets to the classifier. This will only work reliably and give sensible evaluation results if the user runs the flow by launching start points sequentially (and optionally setting the order that start points get launched by setting each one's name with a numeric prefix). The component will now pop up a dialog informing the user about this if it detects more than one testSet connection.
Is now quiet if no class is set in an incoming format-only set of instances.
Components can now use @!@ as a prefix to their name to tell the log panel not to start a timer.
Status messages from the Knowledge Flow itself now no longer start a timer in the LogPanel.
Was not handling the end-of-stream case properly when end-of-stream was indicated by a null instance - fixed.
Was reporting one to many instances when processing incrementally - fixed.
If a component's first message starts with 'finished' or 'done" then a timer is not started.
Fixed a bug where the list of string attribute indexes used during incremental processing when string atts are present was not getting reset on the start of a new stream.
Initial status message when processing incrementally now reads "Predicting..." rather than "Training..." when the user has not chosen to update the classifier.
Fixed a bug where a structure-only test set would get stored in the queue of valid test sets when training and test sets originated from separate sources.
Fixed a bug that affected evaluation of InputMappedClassifier.
Now evaluates single set batches sequentially rather than in a separate thread. This makes an attempt at protecting classifiers who's classify/distributionForInstance methods are not thread safe (e.g FilteredClassifier) in the case where there might be more than one batchClassifier connection outgoing from the Classifier component.