Displaying 6 results from an estimated 6 matches for "rules2".
Did you mean:
rules
2009 Feb 28
0
arules: rules are built on item ordering in the dataframe, rather than
...gives the expected results:
## Working example:
my.df2 <- data.frame(
transaction=as.factor(1:4),
a = rep("a", 4),
b = rep("b", 4),
c = c(NA, "c", NA, NA),
d = c(NA, NA, "d", "d"))
my.trans2 <- as(my.df2[,2:5], "transactions")
rules2 <- apriori(my.trans2, parameter=list(support=.01, confidence=0.6))
inspect(rules2)
## End code
I can't figure out how to coerce my data frame into this format (or if
this is the best way to accomplish my objective).
I appreciate your help.
Thanks,
Matt
2015 Jul 29
0
[LLVMdev] The Trouble with Triples
...ferent vendors use different configure options and may change them at
> will. When they do change them, the vendors often desire to keep the same
> triple to be able to drop in the new version without causing wider impact
> on their environment. For example, assuming I'm reading debian/rules2 for
> Debian's gcc-4.9 package correctly then the i386-linux-gnu means i486 on
> Debian Etch and Lenny but means i586 on more recent versions. On a similar
> note, on Debian, mips-linux-gnu targets MIPS-II (optimised for typical
> MIPS32 implementations) rather than the usual MIPS-I...
2015 Jul 08
5
[LLVMdev] The Trouble with Triples
...selection. Different vendors use different configure options and may change them at will. When they do change them, the vendors often desire to keep the same triple to be able to drop in the new version without causing wider impact on their environment. For example, assuming I'm reading debian/rules2 for Debian's gcc-4.9 package correctly then the i386-linux-gnu means i486 on Debian Etch and Lenny but means i586 on more recent versions. On a similar note, on Debian, mips-linux-gnu targets MIPS-II (optimised for typical MIPS32 implementations) rather than the usual MIPS-I. The last example o...
2015 Jul 30
3
[LLVMdev] The Trouble with Triples
...selection. Different vendors use different configure options and may change them at will. When they do change them, the vendors often desire to keep the same triple to be able to drop in the new version without causing wider impact on their environment. For example, assuming I'm reading debian/rules2 for Debian's gcc-4.9 package correctly then the i386-linux-gnu means i486 on Debian Etch and Lenny but means i586 on more recent versions. On a similar note, on Debian, mips-linux-gnu targets MIPS-II (optimised for typical MIPS32 implementations) rather than the usual MIPS-I. The last example o...
2015 Jul 30
0
[LLVMdev] The Trouble with Triples
...ferent vendors use different configure options and may change them at
> will. When they do change them, the vendors often desire to keep the same
> triple to be able to drop in the new version without causing wider impact
> on their environment. For example, assuming I'm reading debian/rules2 for
> Debian's gcc-4.9 package correctly then the i386-linux-gnu means i486 on
> Debian Etch and Lenny but means i586 on more recent versions. On a similar
> note, on Debian, mips-linux-gnu targets MIPS-II (optimised for typical
> MIPS32 implementations) rather than the usual MIPS-I...
2015 Jul 31
2
[LLVMdev] The Trouble with Triples
...selection. Different vendors use different configure options and may change them at will. When they do change them, the vendors often desire to keep the same triple to be able to drop in the new version without causing wider impact on their environment. For example, assuming I'm reading debian/rules2 for Debian's gcc-4.9 package correctly then the i386-linux-gnu means i486 on Debian Etch and Lenny but means i586 on more recent versions. On a similar note, on Debian, mips-linux-gnu targets MIPS-II (optimised for typical MIPS32 implementations) rather than the usual MIPS-I. The last example o...