The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
Inconsistent results
I'm starting to use RapidMiner after using Weka and there's one thing that is driving me crazy.
I'm using a simple dataset:
http://cs.uns.edu.ar/~cic/dm2007/downloads/datasets/titanic.arff
Four nominal columns: passenger class (4 classes), age (adult or child), sex (man or woman), survived? (yes or no).
I store that data in a repository and create a very simple process: retrieve the data and apply W-Apriori operator with default parameters. No rules found message.
I don't understand how is working. In Weka GUI with the same parameters, rules are not only found but also they are right. If I insert an operator (with a multiplier) before W-Apriori and write the input to a arff file, in order to ensure what input is getting W-Apriori operator, and run Weka with that file, the same rules are obtained. I've tested with other datasets, and they aren't working either.
If I switch the algorithm to W-FPGrowth, results are consistent. Same results in Weka and in RapidMiner. I also did try to look inside of Weka plugin. I did a binary comparison between my Weka.jar and classes in the plugin. They matched completely. So I'm using exactly the same Weka version.
Does anybody know what I'm doing wrong?
I know that RapidMiner have other own operators for association rules, but all my team is working with Weka, and my first step to convince them to switch to RapidMiner is showing that all we do in Weka is directly possible in RapidMiner.
Thanks in advance!
I'm using a simple dataset:
http://cs.uns.edu.ar/~cic/dm2007/downloads/datasets/titanic.arff
Four nominal columns: passenger class (4 classes), age (adult or child), sex (man or woman), survived? (yes or no).
I store that data in a repository and create a very simple process: retrieve the data and apply W-Apriori operator with default parameters. No rules found message.
I don't understand how is working. In Weka GUI with the same parameters, rules are not only found but also they are right. If I insert an operator (with a multiplier) before W-Apriori and write the input to a arff file, in order to ensure what input is getting W-Apriori operator, and run Weka with that file, the same rules are obtained. I've tested with other datasets, and they aren't working either.
If I switch the algorithm to W-FPGrowth, results are consistent. Same results in Weka and in RapidMiner. I also did try to look inside of Weka plugin. I did a binary comparison between my Weka.jar and classes in the plugin. They matched completely. So I'm using exactly the same Weka version.
Does anybody know what I'm doing wrong?
I know that RapidMiner have other own operators for association rules, but all my team is working with Weka, and my first step to convince them to switch to RapidMiner is showing that all we do in Weka is directly possible in RapidMiner.
Thanks in advance!
0
Answers
Best regards,
Marius
Sorry for forgetting those important details:
OS X 10.8
Apple Java 1.6.0_51
RapidMiner 5.3.008
Weka Extension 5.3.1 (which includes Weka 3.6.9)
Weka Standalone 3.6.9
I've also tried with other Weka Extension versions with no luck.
Please, tell me if you need more details. I'm very interested in migrating my work group to RapidMiner. I find RapidMiner very useful!
Thanks again.
What I do observe is that the results of the W-Apriori are not shown due to a bug that will probably be fixed in the release of RapidMiner.
Best regards,
Marius
This is the content of the RapidMiner output: When I run Weka GUI, this is the output:
Best regards,
Marius
I think what you refer is part of the algorithm output.
Nevertheless, if I set the output min confidence (0.35) and support (0.9), I get the following message in RapidMiner:
Thanks again.