KNIME WEKA nodes (3.7) version 4.1.0.v201911281246 by KNIME AG, Zurich, Switzerland
This method constructs a decision tree based classifier that maintains highest accuracy on training data and improves on generalization accuracy as it grows in complexity
The classifier consists of multiple trees constructed systematically by pseudorandomly selecting subsets of components of the feature vector, that is, trees constructed in randomly chosen subspaces.
For more information, see
Tin Kam Ho (1998).The Random Subspace Method for Constructing Decision Forests.
IEEE Transactions on Pattern Analysis and Machine Intelligence.20(8):832-844.
(based on WEKA 3.7)
For further options, click the 'More' - button in the dialog.
All weka dialogs have a panel where you can specify classifier-specific parameters.
P: Size of each subspace: < 1: percentage of the number of attributes >=1: absolute number of attributes
S: Random number seed. (default 1)
num-slots: Number of execution slots. (default 1 - i.e. no parallelism)
I: Number of iterations. (default 10)
D: If set, classifier is run in debug mode and may output additional info to the console
W: Full name of base classifier. (default: weka.classifiers.trees.REPTree)
M: Set minimum number of instances per leaf (default 2).
V: Set minimum numeric class variance proportion of train variance for split (default 1e-3).
N: Number of folds for reduced error pruning (default 3).
S: Seed for random data shuffling (default 1).
P: No pruning.
L: Maximum tree depth (default -1, no maximum)
I: Initial class value count (default 0)
R: Spread initial count over all class values (i.e. don't use 1 per value)
The Preliminary Attribute Check tests the underlying classifier against the DataTable specification at the inport of the node. Columns that are compatible with the classifier are marked with a green 'ok'. Columns which are potentially not compatible are assigned a red error message.
Important: If a column is marked as 'incompatible', it does not necessarily mean that the classifier cannot be executed! Sometimes, the error message 'Cannot handle String class' simply means that no nominal values are available (yet). This may change during execution of the predecessor nodes.
Capabilities: [Nominal attributes, Binary attributes, Unary attributes, Empty nominal attributes, Numeric attributes, Date attributes, Missing values, Nominal class, Binary class, Numeric class, Date class, Missing class values] Dependencies: [Nominal attributes, Binary attributes, Unary attributes, Empty nominal attributes, Numeric attributes, Date attributes, String attributes, Relational attributes, Missing values, No class, Nominal class, Binary class, Unary class, Empty nominal class, Numeric class, Date class, String class, Relational class, Missing class values, Only multi-Instance data] min # Instance: 1
It shows the command line options according to the current classifier configuration and mainly serves to support the node's configuration via flow variables.
To use this node in KNIME, install KNIME Weka Data Mining Integration (3.7) from the following update site:
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to firstname.lastname@example.org, follow @NodePit on Twitter, or chat on Gitter!
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.