#include "../util/defines.h"
#include <time.h>
#include <assert.h>
Go to the source code of this file.
Classes | |
class | Feature |
class | PersistantFeature |
class | FeatureProvider |
DLL initialization functions | |
These functions will be called when a library is loaded or unloaded by the framework. | |
void | library_initialize () |
void | library_finalize () |
Defines | |
#define | EXPORT_FEATURE(provider) |
Typedefs | |
typedef parametermap | providerparams |
typedef parametermap | featureparams |
typedef pair< time_t, Feature * > | aggregatefeature |
typedef list< aggregatefeature > | aggregatelist |
typedef map< unsigned long, double > | membershiplist |
typedef vector< Feature * > | featurevector |
typedef FeatureProvider *(* | getProvider_t )(const providerparams ¶ms) |
This file contains the interfaces that have to be implemented to enable a sensor to be used by the framework.
© 2003-2004 by Rene Mayrhofer, Harald Radi
Harald Radi <harald.radi@nme.at>
|
Value: \ static provider *fp; \ void INIT_EXPORT library_initialize() { fp = NULL; } \ void FINI_EXPORT library_finalize() { if (fp != NULL) delete fp; } \ \ extern "C" FEATURE_EXPORT FeatureProvider* getProvider(providerparams ¶ms) { if (fp == NULL) fp = new provider(params); return fp; } This macro has to be used in global scope and gets substituted with the implementation for exporting a FeatureProvider singleton instance to the framework.
|
|
A <timestamp, Feature> tuple |
|
A list of <timestamp, Feature> tuples |
|
|
|
Ordered list of features This is one of the basic datatypes in this framework. It represents an ordered list of features, which describes a single point in the heterogeneous feature space.
|
|
Type of the getProvider function This type definition is needed by the FeatureContainer to query a Feature implementation for an instance of its class. |
|
A map type for returning membership values for each cluster. |
|
Parameters passed to feature providers When initializing a feature provider, an arbitrary number of named (string) parameters can be passed from the application (e.g. read from a config file). These key-value tuples can then be used by the feature provider as configuration or initialization values. They are completely FeatureProvider specific. The same structure is also used to store and read persistant feature data.
|
|
Unload library |
|
Load library |