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
"FPGrowth/Assiciationrule Generator - filter useless rules"
Hi,
I am currently testing the FPGrowth algorithm using an example set which is structured like this
id attribute1 attribute2 attribute3
-----------------------------------------------------
4711 true false true
4712 false false false
...
Now, FPGrowth followed by AssociationRuleGenerator generates rules like
IF attribute1 = 0 THEN attribute2 => 0
These rules are not important (at least for me), because they just say that if attribute1 does not appear, attribute2 does not appear.
Is there any other way to filter such rules from the FrequentItemset? I tested the FPGrowth-Parameter "must contain" with the simple regex "attribute1 = 1", but it had no effect
Thanks for your help !
Werner
I am currently testing the FPGrowth algorithm using an example set which is structured like this
id attribute1 attribute2 attribute3
-----------------------------------------------------
4711 true false true
4712 false false false
...
Now, FPGrowth followed by AssociationRuleGenerator generates rules like
IF attribute1 = 0 THEN attribute2 => 0
These rules are not important (at least for me), because they just say that if attribute1 does not appear, attribute2 does not appear.
Is there any other way to filter such rules from the FrequentItemset? I tested the FPGrowth-Parameter "must contain" with the simple regex "attribute1 = 1", but it had no effect
Thanks for your help !
Werner
Tagged:
0
Answers
Now it produces only rules which start with
IF attribute = 1 THEN ....
but the generated rules do not rely on the correct data. Instead you are using the inverted data now: Each false is treated as being true. In normal transaction data, the false case is much more frequent than the true case. So rules based on the false case will have a greater support. That's why you find some rules and don't when switching back to "true". You might lower the support for finding rules, if there aren't any found.
Greetings,
Sebastian