See: Description
Interface | Description |
---|---|
Processor |
Class to represent a processor factory.
|
Processor.Instance |
Instance.
|
Class | Description |
---|---|
AbstractDoubleProcessor |
Abstract base class for processors that output double values.
|
AbstractDoubleProcessor.Instance |
Instance.
|
DoubleMinMaxProcessor |
Sink collecting minimum and maximum values.
|
DoubleMinMaxProcessor.Instance |
Instance for a particular sub-channel / part of the data set.
|
KDistanceProcessor |
Compute the kNN distance for each object.
|
KDistanceProcessor.Instance |
Instance for precomputing the kNN.
|
KNNProcessor<O> |
Processor to compute the kNN of each object.
|
KNNProcessor.Instance<O> |
Instance for precomputing the kNN.
|
WriteDataStoreProcessor<T> |
Output channel to store data in a
WritableDataStore . |
WriteDoubleDataStoreProcessor |
Write double values into a
WritableDoubleDataStore . |
WriteIntegerDataStoreProcessor |
Write int values into a
WritableIntegerDataStore . |
SharedVariable
API.
The other key difference is that ELKI is not (yet?) running in a distributed framework,
therefore it is perfectly possible to have a mapper query the database, or write to
an output storage. It may be necessary to apply locking in such cases!
As we want to write to some storage at the end, the last processor usually will not have
an "output", thus the name "map" is not a good match anymore.Copyright © 2019 ELKI Development Team. License information.