This classifier generates a two-class kernel logistic regression model
The model is fit by minimizing the negative log-likelihood with a quadratic penalty using BFGS optimization, as implemented in the Optimization class.Alternatively, conjugate gradient optimization can be applied.
The user can specify the kernel function and the value of lambda, the multiplier for the quadractic penalty.Using a linear kernel (the default) this method should give the same result as ridge logistic regression implemented in Logistic, assuming the ridge parameter is set to the same value as lambda, and not too small.
By replacing the kernel function, we can learn non-linear decision boundaries.
Note that the data is filtered using ReplaceMissingValues, RemoveUseless, NominalToBinary, and Standardize (in that order).
If a CachedKernel is used, this class will overwrite the manually specified cache size and use a full cache instead.
To apply this classifier to multi-class problems, use the MultiClassClassifier.
This implementation stores the full kernel matrix at training time for speed reasons.
(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.
S: Random number seed. (default 1)
D: If set, classifier is run in debug mode and may output additional info to the console
K: The Kernel to use. (default: weka.classifiers.functions.supportVector.PolyKernel)
L: The lambda penalty parameter. (default 0.01)
G: Use conjugate gradient descent instead of BFGS.
P: The size of the thread pool, for example, the number of cores in the CPU. (default 1)
E: The number of threads to use, which should be >= size of thread pool. (default 1)
D: Enables debugging output (if available) to be printed. (default: off)
no-checks: Turns off all checks - use with caution! (default: checks on)
C: The size of the cache (a prime number), 0 for full cache and -1 to turn it off. (default: 250007)
E: The Exponent to use. (default: 1.0)
L: Use lower-order terms. (default: no)
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, Missing values, Binary class, Missing class values] Dependencies:  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.
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.
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.Try NodePit Runner!
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.