condition {cna}  R Documentation 
Uncover relevant properties of msc, asf, and csf in a data frame or configTable
Description
The condition
function provides assistance to inspect the properties of msc, asf, and csf (as returned by cna
) in a data frame or configTable
, but also of any other Boolean function. condition
reveals which configurations and cases instantiate a given msc, asf, or csf and lists consistency and coverage scores.
Usage
condition(x, ...)
## Default S3 method:
condition(x, ct, type, add.data = FALSE,
force.bool = FALSE, rm.parentheses = FALSE, ..., tt)
## S3 method for class 'condTbl'
condition(x, ct, ...)
## S3 method for class 'condList'
print(x, ...)
## S3 method for class 'cond'
print(x, digits = 3, print.table = TRUE,
show.cases = NULL, add.data = NULL, ...)
Arguments
x 
Character vector specifying a Boolean expression as 
ct 
Data frame or 
type 
Character vector specifying the type of 
add.data 
Logical; if 
force.bool 
Logical; if 
rm.parentheses 
Logical; if 
digits 
Number of digits to print in consistency and coverage scores. 
print.table 
Logical; if 
show.cases 
Logical; if 
... 
Arguments passed to methods. 
tt 
Argument 
Details
Depending on the processed data frame or configTable
, the solutions output by cna
are often ambiguous; that is, it can happen that many solution formulas fit the data equally well. If that happens, the data alone are insufficient to single out one solution. While cna
simply lists the possible solutions, the condition
function is intended to provide assistance in comparing different minimally sufficient conditions (msc), atomic solution formulas (asf), and complex solution formulas (csf) in order to have a better basis for selecting among them.
Most importantly, the output of the condition
function highlights in which configurations and cases in the data an msc, asf, and csf is instantiated. Thus, if the user has independent causal knowledge about particular configurations or cases, the information received from condition
may be helpful in selecting the solutions that are consistent with that knowledge. Moreover, the condition
function allows for directly contrasting consistency and coverage scores or frequencies of different conditions contained in returned asf.
The condition
function is independent of cna
. That is, any msc, asf, or csf—irrespective of whether they are output by cna
—can be given as input to condition
. Even Boolean expressions that do not have the syntax of CNA solution formulas can be passed to condition
.
The first required input x
of condition
is a character vector consisting of Boolean formulas composed of factor values that appear in ct
, which is the second required input. ct
can be a configTable
or a data frame. If ct
is a data frame and the type
argument has its default value "auto"
, condition
first determines the data type and then converts the data frame to a configTable
. The data type can also be manually specified by giving the type
argument one of the values "cs"
, "mv"
, or "fs"
.
Conjunction can be expressed by “*
” or “&
”, disjunction by “+
” or “
”, negation can be expressed by “
” or “!
” or, in case of crispset or fuzzyset data, by changing upper case into lower case letters and vice versa, implication by “>
”, and equivalence by “<>
”. Examples are

A*b > C, A+b*c+!(C+D), A*B*C + (E*!B), C > A*B + a*b

(A=2*B=4 + A=3*B=1 <> C=2)*(C=2*D=3 + C=1*D=4 <> E=3)

(A=2*B=4*!(A=3*B=1))  !(C=2D=4)*(C=2*D=3 + C=1*D=4 <> E=3)
Three types of conditions are distinguished:
The type boolean comprises Boolean expressions that do not have the syntactic form of causal models, meaning the corresponding character strings in the argument
x
do not have an “>
” or “<>
” as main operator. Examples:"A*B + C"
or"(A*B + (C+d))"
. The expression is evaluated and written into a data frame with one column. Frequency is attached to this data frame as an attribute.The type atomic comprises expressions that have the syntactic form of atomic causal models, i.e. asf, meaning the corresponding character strings in the argument
x
have an “>
” or “<>
” as main operator. Examples:"A*B + C > D"
or"A*B + C <> D"
. The expressions on both sides of “>
” and “<>
” are evaluated and written into a data frame with two columns. Consistency and coverage are attached to these data frames as attributes.The type complex represents complex causal models, i.e. csf. Example:
"(A*B + a*b <> C)*(C*d + c*D <> E)"
. Each component must be a causal model of type atomic. These components are evaluated separately and the results stored in a list. Consistency and coverage of the complex expression are then attached to this list.
The types of the character strings in the input x
are automatically discerned and thus do not need to be specified by the user.
If force.bool = TRUE
, expressions with “>
” or “<>
” are treated as type boolean, i.e. only their frequencies are calculated. Enclosing a character string representing a causal model in parentheses has the same effect as specifying force.bool = TRUE
. rm.parentheses = TRUE
removes parentheses around the expression prior to evaluation, and thus has the reverse effect of setting force.bool = TRUE
.
If add.data = TRUE
, ct
is appended to the output such as to facilitate the analysis and evaluation of a model on the case level.
The digits
argument of the print
method determines how many digits of consistency and coverage scores are printed. If print.table = FALSE
, the table assigning conditions to configurations and cases is omitted, i.e. only frequencies or consistency and coverage scores are returned. row.names = TRUE
also lists the row names in ct
. If rows in a ct
are instantiated by many cases, those cases are not printed by default. They can be recovered by show.cases = TRUE
.
Value
condition
returns a nested list of objects, each of them corresponding to one element of the input vector x
. The list has a class attribute “condList”, the list elements (i.e., the individual conditions) are of class “cond” and have a more specific class label “booleanCond”, “atomicCond” or “complexCond”, relfecting the type of condition. The components of class “booleanCond” or “atomicCond” are amended data frames, those of class “complexCond” are lists of amended data frames.
print
method
print.condList
essentially executes print.cond
(the method printing a single condition)
successively for each list element/condition. All arguments in print.condList
are thereby passed to print.cond
, i.e. digits
, print.table
, show.cases
, add.data
can also be specified when printing the complete list of conditions.
The option “spaces” controls how the conditions are rendered in certain contexts. The current setting is queried by typing getOption("spaces")
. The option specifies characters that will be printed with a space before and after them. The default is c("<>",">","+")
. A more compact output is obtained with option(spaces = NULL)
.
References
Emmenegger, Patrick. 2011. “Job Security Regulations in Western Democracies: A Fuzzy Set Analysis.” European Journal of Political Research 50(3):33664.
Lam, Wai Fung, and Elinor Ostrom. 2010. “Analyzing the Dynamic Complexity of Development Interventions: Lessons from an Irrigation Experiment in Nepal.” Policy Sciences 43 (2):125.
Ragin, Charles. 2008. Redesigning Social Inquiry: Fuzzy Sets and Beyond. Chicago, IL: University of Chicago Press.
See Also
condListmethods
describes methods and functions processing the output of condition
; see, in particular, the related summary
and as.data.frame
methods.
cna
, configTable
, condTbl
, as.data.frame.condList
, d.irrigate
, shortcuts
Examples
# Crispset data from Lam and Ostrom (2010) on the impact of development interventions
# 
# Build the configuration table for d.irrigate.
irrigate.ct < configTable(d.irrigate)
# Any Boolean functions involving values of the factors "A", "R", "F", "L", "C", "W" in
# d.irrigate can be tested by condition().
condition("A*r + L*C", irrigate.ct)
condition(c("A*r + !(L*C)", "A*(L  F)", "C > A*R + C*l"), irrigate.ct)
condition(c("A*r + L*C > W", "!(A*L*R > W)", "(A*R + C*l <> F)*(W*a > F)"),
irrigate.ct)
# Group expressions with ">" by outcome.
irrigate.con < condition(c("A*r + L*C > W", "A*L*R > W", "A*R + C*l > F", "W*a > F"),
irrigate.ct)
group.by.outcome(irrigate.con)
# Pass minimally sufficient conditions inferred by cna() to condition().
irrigate.cna1 < cna(d.irrigate, ordering = "A, R, L < F, C < W", con = .9)
condition(msc(irrigate.cna1)$condition, irrigate.ct)
# Pass atomic solution formulas inferred by cna() to condition().
irrigate.cna1 < cna(d.irrigate, ordering = "A, R, L < F, C < W", con = .9)
condition(asf(irrigate.cna1)$condition, irrigate.ct)
# Group by outcome.
irrigate.cna1.msc < condition(msc(irrigate.cna1)$condition, irrigate.ct)
group.by.outcome(irrigate.cna1.msc)
irrigate.cna2 < cna(d.irrigate, con = .9)
irrigate.cna2a.asf < condition(asf(irrigate.cna2)$condition, irrigate.ct)
group.by.outcome(irrigate.cna2a.asf)
# Return as regular data frame.
as.data.frame(irrigate.cna2a.asf)
# Add data.
(irrigate.cna2b.asf < condition(asf(irrigate.cna2)$condition, irrigate.ct,
add.data = TRUE))
# No spaces before and after "+".
options(spaces = c("<>", ">" ))
irrigate.cna2b.asf
# No spaces at all.
options(spaces = NULL)
irrigate.cna2b.asf
# Restore the default spacing.
options(spaces = c("<>", ">", "+"))
# Print only consistency and coverage scores.
print(irrigate.cna2a.asf, print.table = FALSE)
summary(irrigate.cna2a.asf)
# Print only 2 digits of consistency and coverage scores.
print(irrigate.cna2b.asf, digits = 2)
# Instead of a configuration table as output by configTable(), it is also possible to provide
# a data frame as second input.
condition("A*r + L*C", d.irrigate)
condition(c("A*r + L*C", "A*L > F", "C > A*R + C*l"), d.irrigate)
condition(c("A*r + L*C > W", "A*L*R > W", "A*R + C*l > F", "W*a > F"), d.irrigate)
# Fuzzyset data from Emmenegger (2011) on the causes of high job security regulations
# 
# Compare the CNA solution for outcome JSR to the solution presented by Emmenegger
# S*R*v + S*L*R*P + S*C*R*P + C*L*P*v > JSR (p. 349), which he generated by fsQCA as
# implemented in the fs/QCA software, version 2.5.
jobsecurity.cna < cna(d.jobsecurity, outcome = "JSR", con = .97, cov= .77,
maxstep = c(4, 4, 15))
compare.sol < condition(c(asf(jobsecurity.cna)$condition, "S*R*v + S*L*R*P + S*C*R*P +
C*L*P*v > JSR"), d.jobsecurity)
summary(compare.sol)
print(compare.sol, add.data = d.jobsecurity)
group.by.outcome(compare.sol)
# There exist even more high quality solutions for JSR.
jobsecurity.cna2 < cna(d.jobsecurity, outcome = "JSR", con = .95, cov= .8,
maxstep = c(4, 4, 15))
compare.sol2 < condition(c(asf(jobsecurity.cna2)$condition, "S*R*v + S*L*R*P + S*C*R*P +
C*L*P*v > JSR"), d.jobsecurity)
summary(compare.sol2)
group.by.outcome(compare.sol2)
# Simulate multivalue data
# 
library(dplyr)
# Define the data generating structure.
groundTruth < "(A=2*B=1 + A=3*B=3 <> C=1)*(C=1*D=2 + C=2*D=3 <> E=3)"
# Generate ideal data on groundTruth.
fullData < allCombs(c(3, 3, 2, 3, 3))
idealData < ct2df(selectCases(groundTruth, fullData))
# Randomly add 15% inconsistent cases.
inconsistentCases < setdiff(fullData, idealData)
realData < rbind(idealData, inconsistentCases[sample(1:nrow(inconsistentCases),
nrow(idealData)*0.15), ])
# Determine model fit of groundTruth and its submodels.
condition(groundTruth, realData)
condition("A=2*B=1 + A=3*B=3 <> C=1", realData)
condition("A=2*B=1 + A=3*B=3 <> C=1", realData, force.bool = TRUE)
condition("(C=1*D=2 + C=2*D=3 <> E=3)", realData)
condition("(C=1*D=2 + C=2*D=3 <> E=3)", realData, rm.parentheses = TRUE)
condition("(C=1*D=2 +!(C=2*D=3 + A=1*B=1) <> E=3)", realData)
# Manually calculate unique coverages, i.e. the ratio of an outcome's instances
# covered by individual msc alone (for details on unique coverage cf.
# Ragin 2008:6368).
summary(condition("A=2*B=1 * (A=3*B=3) <> C=1", realData)) # unique coverage of A=2*B=1
summary(condition("(A=2*B=1) * A=3*B=3 <> C=1", realData)) # unique coverage of A=3*B=3
# Note that expressions must feature factor VALUES contained in the data, they may not
# contain factor NAMES. The following calls produce errors.
condition("C*D <> E", realData)
condition("A=2*B=1 + C=23", realData)
# In case of mv expressions, negations of factor values must be written with brackets.
condition("!(A=2)", realData)
# The following produces an error.
condition("!A=2", realData)