EDOBE XDOM PMML Manual de usuario descargar pdf (Pagina 25)

ENGINE CLASSES

Overview For each type of node, there is a class extending EngineNode that is

responsible for providing metadata to the activity node model and

coordinating the computations when the node is executed.

The actual computation will be performed by methods in the

EngineNode class for a Java-based computation, or in a C++ class for

a C++-based computation. Coordination between the pipeline, the

EngineNode, and other classes performing the computation is handled

by a

CNKProc object.

It is possible for multiple activity node model classes to use the same

engine node class. For example, several of the S-PLUS related nodes

all use the

SplusScriptEngineNode class. Engine node code can also

be shared by having multiple classes extend a parent class that does

most of the computation for that family of nodes.

General

Methods

The EngineNode class has a wide variety of useful utility methods.

These methods typically are not overridden. Exceptions are

discussed in the following subsections.

The

getNodeProperties() method is useful for determining the

properties specified for the node.

The

getInputMetaData() and getOutputMetaData() methods are

useful for getting information about the inputs and outputs of the

node.

Constructors The constructor is typically a single no-argument constructor:

public ReadTextFileEngineNode() {

}

Initialization Actual initialization is performed in the procCreate() method. This

is where the

CNKProc object for the node is created. This initialization

is performed every time the node is executed. This method is a good

place to initialize any class member variables and to print any initial

messages regarding the computations the node will be performing.

1 2 ... 20 21 22 23 24 25 26 27 28 29 30 ... 97 98

Sin comentarios

EDOBE XDOM PMML Manual de usuario Pagina 25