Main Page | Class Hierarchy | Class List | Class Members

kddml.Operators.DataMining.AssociationAlgorithms.DCI_RESOLVER Class Reference

Inheritance diagram for kddml.Operators.DataMining.AssociationAlgorithms.DCI_RESOLVER:

kddml.Operators.DataMining.AssociationAlgorithms.AssociationAlgorithmResolverTask kddml.Operators.DataMining.DMAlgorithmResolverTask kddml.Operators.AlgorithmResolverTask List of all members.

Public Member Functions

void readParameters (Hashtable< String, KDDMLScalarManager > parameters) throws ResolverException, KDDMLCoreException
void readXMLDestination (String xml_dest)
Object inputFormatting (InternalTableManager instances) throws ResolverException, KDDMLCoreException
Object execute (Object hash_table) throws ResolverException, KDDMLCoreException
AssociationModel outputFormatting (Object items_mapped) throws ResolverException, KDDMLCoreException
String[] getTmpFiles ()

Detailed Description

Resolver class for the DCI algorithm.
DCI (Direct Count & Intersect) is an algorithm for finding frequent sets of items from a transactional database. It can be considered an enhancement of the well known Apriori, because they both share the same level-wise approach and use the same candidate generation technique. Nevertheless, DCI improves considerably the performance of Apriori by introducing a new pruning technique and the automatic switching to a vertical database representation, during execution. DCI adopts a direct counting based approach for the first iterations and an intersection based approach for the vertical dataset iterations. Moreover DCI adopts a new counting inference strategy based on the notion of key-patterns.
The input data source can be in a relational format, i.e. a row for each single transaction and an attribute for every item. This format allows for deriving inter-attribute association rules such as “carType=racing AND homeInsurance=false --> married=false“. In a relational table, numeric attributes are ignored by the DCI algorithm. Also the transactional format is recognized. The last one is used to deriving intra-attribute association rules such as “spaghetti AND tomato --> parmesan“. In a transaction format, the DCI algorithm uses only the attributes item and transaction during the extraction process. Other attributes are allowed in the table, but they are ignored by the mining algorithm.

Title: KDDML

Description: Knowledge Discovery in Database Environment

Copyright: Copyright (c) 2003 - 2005

Company: Universita' di Pisa - Dipartimento di Informatica

Author:
Andrea Romei (romei@di.unipi.it)
Version:
2.0.16


Member Function Documentation

void kddml.Operators.DataMining.AssociationAlgorithms.DCI_RESOLVER.readParameters Hashtable< String, KDDMLScalarManager parameters  )  throws ResolverException, KDDMLCoreException
 

Reads the XML parameters related to a generic algorithm stored in the ALGORITHM entity. An algorithm settings object captures the parameters associated with a particular algorithm. It allows a knowledgeable user to fine tune algorithm parameters. Generally, not all parameters must be specified, however, those specified are taken into account by the KDDML.
Parameters are given as hashtable, where the key is the name of the parameter related to the algorithm and the value is a KDDMLScalar object containing the parameter value. Parameter value is checked by the interpreter layer and its type is correct.

Parameters:
parameters Hashtable the parameters related to the algorithm. The key of the hashtable is the name of the parameter. The value of the hashtable is a KDDMLScalar representing the value of the parameter.
Exceptions:
ResolverException if a resolving error occurs.
KDDMLCoreException if a level core error occurs.

Implements kddml.Operators.AlgorithmResolverTask.

void kddml.Operators.DataMining.AssociationAlgorithms.DCI_RESOLVER.readXMLDestination String  xml_dest  ) 
 

Reads the XML destination that stores the final result.

Parameters:
xml_dest String

Implements kddml.Operators.DataMining.DMAlgorithmResolverTask.

Object kddml.Operators.DataMining.AssociationAlgorithms.DCI_RESOLVER.inputFormatting InternalTableManager  instances  )  throws ResolverException, KDDMLCoreException [virtual]
 

Formatting of the input dataset. It scans the passed data in order to transform the data source into the format as the algorithm specification requires. The method returns a generic java.lang.Object (e.g. the name of the temporary file created during the formatting process) that is used as input of the excute() method.

Parameters:
instances InternalTableManager the data set to scan.
Returns:
Object the generic object used as input of the excute() method. Can be null.
Exceptions:
ResolverException if a resolving error occurs.
KDDMLCoreException if a level core error occurs.

Implements kddml.Operators.DataMining.DMAlgorithmResolverTask.

Object kddml.Operators.DataMining.AssociationAlgorithms.DCI_RESOLVER.execute Object  hash_table  )  throws ResolverException, KDDMLCoreException [virtual]
 

Main execute method. It takes the result of the inputFormatting() method and, tipically, the procedure calls an external DM library implemented in C,C++ in order to extract the model. The method returns a generic java.lang.Object (e.g. the name of the temporary file created during the extraction process) that is used as input of the outputFormatting(Object obj) method.

Parameters:
hash_table Object the result of the inputFormatting() method.
Returns:
Object the generic object used as input of the outputFormatting() method. Can be null.
Exceptions:
ResolverException if a resolving error occurs.
KDDMLCoreException if a level core error occurs.

Implements kddml.Operators.DataMining.DMAlgorithmResolverTask.

AssociationModel kddml.Operators.DataMining.AssociationAlgorithms.DCI_RESOLVER.outputFormatting Object  items_mapped  )  throws ResolverException, KDDMLCoreException [virtual]
 

Interprets the output generated by the algorithm in order to return an appropriate AssociationModel. The method takes as input a generic java.lang.Object that is the result of the execute() method.

Parameters:
items_mapped Object the result of the execute() method. It can be null.
Returns:
AssociationModel the final result of the extraction process.
Exceptions:
ResolverException if a resolving error occurs.
KDDMLCoreException if a level core error occurs.

Implements kddml.Operators.DataMining.AssociationAlgorithms.AssociationAlgorithmResolverTask.

String [] kddml.Operators.DataMining.AssociationAlgorithms.DCI_RESOLVER.getTmpFiles  ) 
 

Returns the list of temporary files used during the mining. Files will be removed at the end of execution of the algorithm. Returns an empty array if the algorithm do not generate temporary files.

Returns:
String[]

Implements kddml.Operators.DataMining.DMAlgorithmResolverTask.


Generated on Thu Feb 23 13:04:48 2006 for kddml by  doxygen 1.4.3