OSDL (3.7)

This class is an implementation of the Ordinal Stochastic Dominance Learner. Further information regarding the OSDL-algorithm can be found in: S

Lievens, B.De Baets, K.

Cao-Van (2006).A Probabilistic Framework for the Design of Instance-Based Supervised Ranking Algorithms in an Ordinal Setting.

Annals of Operations Research..

Kim Cao-Van (2003). Supervised ranking: from semantics to algorithms.

Stijn Lievens (2004).Studie en implementatie van instantie-gebaseerde algoritmen voor gesuperviseerd rangschikken.

For more information about supervised ranking, see

http://users.ugent.be/~slievens/supervised_ranking.php

(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.

Options

OSDL Options

D: If set, classifier is run in debug mode and may output additional info to the console

C: Sets the classification type to be used. (Default: MED)

B: Use the balanced version of the Ordinal Stochastic Dominance Learner

W: Use the weighted version of the Ordinal Stochastic Dominance Learner

S: Sets the value of the interpolation parameter (not with -W/T/P/L/U) (default: 0.5).

T: Tune the interpolation parameter (not with -W/S) (default: off)

L: Lower bound for the interpolation parameter (not with -W/S) (default: 0)

U: Upper bound for the interpolation parameter (not with -W/S) (default: 1)

P: Determines the step size for tuning the interpolation parameter, nl. (U-L)/P (not with -W/S) (default: 10)

Select target column
Choose the column that contains the target variable.
Preliminary Attribute Check

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, Nominal class, Binary class, Missing class values] Dependencies: [] min # Instance: 0

Command line options

It shows the command line options according to the current classifier configuration and mainly serves to support the node's configuration via flow variables.

Additional Options

Select optional vector column
If the input table contains vector columns (e.g. double vector), the one to use can be selected here. This vector column will be used as attributes only and all other columns, except the target column, will be ignored.
Keep training instances
If checked, all training instances will be kept and stored with the classifier model. It is useful to calculate additional evaluation measures (see Weka Predictor) that make use of class prior probabilities. If no evaluation is performed or those measures are not required, it is advisable to NOT keep the training instances.

Input Ports

Icon
Training data

Output Ports

Icon
Trained model

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found

Views

Weka Node View
Each Weka node provides a summary view that provides information about the classification. If the test data contains a class column, an evaluation is generated.

Workflows

  • No workflows found

Links

Developers

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.