Package weka.knowledgeflow.steps

Class MemoryBasedDataSource

  • All Implemented Interfaces:
    java.io.Serializable, BaseStepExtender, Step
    @KFStep(name="MemoryDataSource",
        category="DataSources",
        toolTipText="Memory-based data",
        iconPath="weka/gui/knowledgeflow/icons/DefaultDataSource.gif")
public class MemoryBasedDataSource
extends BaseStep
    Simple start step that stores a set of instances and outputs it in a dataSet connection. Gets used programmatically when the setInstances() method is invoked on the MainKFPerspective in order to create a new Flow containing this step.
    Version:
    $Revision: $
    Author:
    Mark Hall (mhall{[at]}pentaho{[dot]}com)
    See Also:
    Serialized Form

    • Constructor Detail

      • MemoryBasedDataSource

        public MemoryBasedDataSource()

    • Method Detail

      • setInstances

        public void setInstances​(Instances instances)
        Set the data to output from this step
        Parameters:
        instances -

      • getInstances

        public Instances getInstances()
        Get the data to output from this step
        Returns:

      • stepInit

        public void stepInit()
              throws WekaException
        Initialize the step
        Throws:
        WekaException - if the data to output has not been set yet

      • getIncomingConnectionTypes

        public java.util.List<java.lang.String> getIncomingConnectionTypes()
        Get a list of incoming connection types that this step can accept. Ideally (and if appropriate), this should take into account the state of the step and any existing incoming connections. E.g. a step might be able to accept one (and only one) incoming batch data connection.
        Returns:
        a list of incoming connections that this step can accept given its current state

      • getOutgoingConnectionTypes

        public java.util.List<java.lang.String> getOutgoingConnectionTypes()
        Get a list of outgoing connection types that this step can produce. Ideally (and if appropriate), this should take into account the state of the step and the incoming connections. E.g. depending on what incoming connection is present, a step might be able to produce a trainingSet output, a testSet output or neither, but not both.
        Returns:
        a list of outgoing connections that this step can produce