knitr::opts_chunk$set( collapse = TRUE, comment = "#>", fig.width = 7, fig.height = 5, warning = FALSE )
One of the goals in the design of this package is to be able to integrate with the
arules package. This means that any one using the
arules functionalities can export to and import from
fcaR objects, more precisely,
For these examples, we are using two binary datasets,
Mushroom (from the
arules package) and
data("Mushroom", package = "arules")
At the moment, in
arules there is no support for fuzzy sets, so we must restrict ourselves to the binary case.
Let us create a
FormalContext object for the
fc_planets <- FormalContext$new(planets)
We begin by converting between the objects which store the datasets.
It suffices to initialize a
FormalContext object with the transactions dataset:
fc <- FormalContext$new(Mushroom) fc
From this point, we can use all the functionalities in the
fcaR package regarding formal contexts, concept lattices and implication sets.
to_transactions() function enables us to export a formal context to a format compatible with the
and use the functionality in that package.
Other point of integration between the two packages is the ability to import rules from the
arules package, operate on them to compute closures, recommendations or to remove redundancies, or to export an implication set as a
Let us suppose that we have extracted implications from the
Mushroom dataset using the
mushroom_rules <- apriori(Mushroom, parameter = list(conf = 1), control = list(verbose = FALSE))
Once we have created the
fc object storing the
Mushroom dataset, we simply add the implications to it as:
And we can use all the functionalities for the
If we want to export the implications extracted for a binary formal context, we can use:
fc_planets$find_implications() fc_planets$implications$to_arules(quality = TRUE)
An example of use may be to extract rules in the
arules package by using
eclat(), then importing everything into
fcaR as described above, and use the functionalities to simplify, remove redundancies, compute closures, etc., as needed, and then re-export back to
Any scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.