Preface
Structural equation modeling (SEM) has been used and developed for decades across various research fields such as (among others) psychology, sociology, and business research.
As an almost inevitable consequence, a different terminology system and, to some extent, mathematical notation has evolved within each field over the years. This “terminology mess” is one of the major obstacles in interdisciplinary research and (scientific) debates, since it hampers a broader understanding of methodological issues, and, even worse, promotes systematic misuse (e.g., the use of Cronbach’s alpha as an estimator for congeneric reliability). This is particularly true for users new to SEM or practitioners who are overwhelmed by terminology of their own field only to find that the term they just thought to have finally completely grasped is defined differently in another field, making the confusion complete. A prime example is the term “formative” (measurement) which has been used to describe a causalformative as well as a composite model. See e.g., Henseler (2017) for a clarification.
Ultimately, this is a matter of (mis)communication which, in our opinion, can only be satisfactorily solved by establishing a clear, unambiguous definition for each term and symbol that is used within the package. We emphasize that we do not seek to impose “our” conventions, nor do we claim they are the “correct” conventions, but merely seek to make communication between us (the authors of the package) and you (the package user) as unambiguous and errorfree as possible.
Hence, we provide a Terminology and a Notation file that contains key terms and mathematical notation/symbols that we consider crucial, alongside our definition. Users are encouraged to read these files carefully to avoid potential misunderstandings.
 The Terminology file contains each term that we think should be defined and explained in order to make sure package users understand complementary help files and vignettes the way the package authors intended them to be understood.
 The Notation files contains some fundamental mathematical notation/ symbols used in the package documentation alongside a definition. Bearing some exceptions, we mostly follow standard notation as laid out in e.g., Bollen (1989).
The package is designed based on a set of principles and a terminology that is partly in contrast to commonly used opensource or commercial software packages offering similar content (e.g., smartPLS). Together with the Terminology and Notation file this introduction seeks to explain these principles. Lastly, to use cSEM effectively, it is helpful to understand its design. Hence, the package architecture and design as well as what we consider the “cSEM workflow” are discussed.
Compositebased structural equation modeling
What is structural equation modeling (SEM)
Structural equation modeling (SEM) is about analyzing, i.e., modeling, estimating, assessing, and testing, the (causal) relationships between concepts  an entity defined by a conceptual definition  with other concepts and/or observable quantities generally referred to as indicators, manifest variables or items. Broadly speaking, two modeling approaches for the concepts and their relationship exist. We refer to the first as the latent variable or common factor model and to the second as the composite model. Each approach entails a set of methods, test, and evaluation criteria as well as a specific terminology that may or may not be adequate within the realm of the other approach.
The classical latent variable or common factor model
Assuming a researcher identifies \(J\) concepts and \(K\) indicators, the fundamental feature of the latent variable model is the assumption of the existence of a set of \(J\) latent variables (common factors) that each serve as a representation of one of the \(J\) concepts to be studied in a sense that each latent variable is causally responsible for the manifestations of a set of \(K_j\) indicators which are supposed to measure the concept in question. The entirety of these measurement relations is captured by the measurement model which relates indicators to latent variables according to the researchers theory of how observables are related to the concepts in question. The entirety of the relationships between concepts (i.e., its representation in a statistical model, the construct) is captured by the structural model whose parameters are usually at the center of the researchers interest. Caution is warranted though as the common factor and its respective concept are not the same thing. Within the “classical” covariancebased or factorbased literature concept, construct, latent variable and its representation the common factor have often been used interchangeably (Rigdon 2012, 2016; Rigdon, Becker, and Sarstedt 2019). This will not be the case in cSEM and readers are explicitly made aware of the fact that concepts are the abstract entity which may be modeled by a common factor, however, no assertion as to the correctness of this approach in terms of “closeness of the common factor and its related concept” are made.
Parameters in latent variable models are usually retrieved by maximum likelihood (ML). The basic idea of ML is to find parameters such that the difference between the modelimplied and the empirical indicator covariance matrix is minimized. Such estimation methods are therefore often referred to as covariancebased methods.
The composite model
The second approach is known as the composite model. As opposed to the latent variable or common factor model, composites do not presuppose the existence of a latent variable. Hence, designed entities (artifacts) such as the “OECD Better Life Index” that arguably have no latent counterpart may be adequately described by a composite, i.e., the linear combination of observables defining the composite. Composites may also be formed to represent latent variables/common factors (or more precisely concepts modeled as common factors) in which case the composite serves as a proxy or standin for the latent variable. However, in cSEM, the term “composite model” is only used to refer to a model in a the former sense, i.e., a model in which the composite is a direct representation of concept/construct!
Parameters in composite models are retrivied by a compositebased approach such as partial least squares path modeling (PLSPM), generalized structured component analysis (GSCA) or dimension reduction techniques such as principal component analysis (PCA). The basic idea of any compositebased approach is to build scores/composites for each concept and subsequently retrieve structural model parameters by a series of (linear) regressions. Such estimation methods are therefore often referred to as variancebased methods as regression maximizes the explained variance of the dependent variable.
What is compositebased SEM?
Compositebased SEM is the entirety of methods, approaches, procedures, algorithms that in some way or another involve linear compounds (composites/proxies/scores), i.e., linear combinations of observables when retrieving (estimating) quantities of interest such as the coefficients of the structural model. It is crucial to clearly distinguish between the composite model and compositebased SEM. They are not the same. While the former is “only” a statistical model relating concepts to observables, the latter simply states that composites  linear compounds, i.e., weighted linear combinations of observables  are used to retrieve quantities of interest! Hence, compositebased SEM as a way of obtaining/estimating parameters of interest may thus be used for the latent variable or common factor model as well as the composite model. However, interpretation of the parameter estimates is fundamentally different since the underlying models differ!
As sketched above, common factor and composite models fundamentally differ in how the relation between observables and concepts is modeled. Naturally, results and, most notably, their (correct/meaningful) interpretation critically hinge on what type of model the user specifies. Across the package we therefore strictly distinguish between
 Concepts/Constructs modeled as common factors (or alternatively latent variables)
 Concepts/Constructs modeled as composites
These phrases will repeatedly appear in help files and other complementary files. It is therefore crucial to remember what they supposed to convey.
Using cSEM
The idea of cSEM is twofold:
 Provide a unified framework to all common compositebased SEM approaches, including typical postestimation procedures. In principal, it should be similar to what lavaan does for covariancebases/factorbased SEM.
 Make the user experience as hasslefree as possible.
The first point is an always ongoing task since approaches are constantly evolving with new developments appearing at a pace that we, the package authors, will not be able to keep up with. The second point, however, was particularly important to us as we have been frustrated ourselves by how technical, unfriendly packages in R can be. Hence, from the very start we envisioned a workflow that essentially only comprises three steps:
Get the essential: no estimator or approach works without data and a description of what parameters are to be estimated and how data is related to these parameters, i.e. a model. Hence, we always need a data set and model. Since, model specification in lavaan model syntax is probably unbeatable in its ease and well known to R users that have an interest in SEM, to us, lavaan model syntax is the obvious tool for users to specify their model. Experience tells, that for R beginners the biggest obstacle has been to get the data into R. However, largely thanks to RStudio, data import and data transformation are nowadays relatively easy to handle. See the Preparing the data and the Specifying a model sections below.
Estimate: no matter the model and type of data, estimation is always done using one central function with the data as its first and the model as its second argument:
csem(.data = my_data, .model = my_model)
Naturally, the
csem()
function has a number of additional arguments to finetune the estimation, however, sincecsem()
automatically recognizes, for instance, whether a concept was modeled as a common factor or composite and automatically applies appropriate correction for attenuation, default arguments are often sufficient. See the Estimate using csem() section below.Postestimate: Inspired by the grammar of data manipulation underlying the dplyr package, cSEM provides 5 postestimation verbs that concisely cover all common postestimation tasks as well as 4 additional test commands and 2 general do commands:
assess()
infer()
predict()
summarize()
verify()
testOMF()
testMICOM()
testHausman()
testMGD()
doIPMA()
doNonlinearRedundancyAnalysis()
doRedundancyAnalysis()
All verbs accept the result of a call to
csem()
as input which makes working with these function extremely simple. You only need to remember the word, not any specific syntax or arguments. Of course, all functions have a number of additional arguments to finetune the postestimation. See the Apply postestimation functions sections below. For details on the arguments consult the individual help files.
The price we pay for an increase in flexibility is primarily a, mostly minor, loss in computational speed, in particular, when intense resampling is involved (i.e., 5000 bootstrap run for a complex model with, say, 1000 observations). Users looking for the most efficient implementation of common resampling routines may find faster implementations. That said, we believe, the time saved when using a standardized estimatepostestimate workflow, no matter the model or data used, well outweighs the potential loss in computational efficiency.
The following sections describe the workflow in more detail.
The cSEMWorkflow
As described in the previous section, working with cSEM consists of 34 steps:
 Prepare/load the data to analyze
 Specify the model to estimate
 Estimate using the
csem()
function  Apply postestimation functions to the result of 3.
Prepare the data
Technically, preparing the data does not require the cSEM and is therefore better considered a preparation task, i.e., a “precSEM” task. The reason why this step is nevertheless considered an explicit part of the cSEMworkflow is motivated by the experience that applied/causal users tend to shy away from software like R because “just getting the data in” and understanding how to show, manipulate and work with data can be frustrating if one is not aware of R’s rich and easy to learn data import and data processing capabilities. While these topics may have been overwhelming for newcomers several years ago, data import and data transformation have become extremely simple and userfriendly if the right tools packages are used. The best place to start is the Rstudio Cheat sheet webpage, especially the Data Import and the Data Transformation cheat sheets.
cSEM is relatively flexible as to the type of data accepted. Currently the following data types/structures are accepted:
A
data.frame
ortibble
with column names matching the indicator names used in the lavaan model description of the measurement or composite model. Possible column types or classes of the data provided are:"logical"
(TRUE
/FALSE
),"numeric"
("double"
or"integer"
),"factor"
("ordered"
and/or"unordered"
) or a mix of several types. Additionally, the data may also include one character column whose column name must be given to.id
. Values of this column are interpreted as group identifiers andcsem()
will split the data by levels of that column and run the estimation for each level separately.Example:
Assuming the following simple model is to be estimated:
< " model # Structural model EXPE ~ IMAG # Reflective measurement model EXPE =~ expe1 + expe2 IMAG =~ imag1 + imag2 "
To estimate the model a data frame with \(N\) rows (the observations) and \(K = 4\) columns with column names
expe1
,imag1
,expe2
,imag2
is required. The order of the columns in the dataset is irrelevant. In cSEM the order is defined by the order in which the names appear in the measurement or composite model equations in the model description. In this case any resulting matrix or vector whose (row/column) names contain the indicator names would have the orderexpe1
,expe2
,imag1
,imag2
. More one model specification below.A
matrix
with column names matching the indicator names used in the lavaan model description of the measurement model or composite model description.A list of data frames or matrices. In this case estimation is repeated for each data frame or matrix separately.
The current version 0.5.0 available on CRAN does not provide any tools to handle missing values. Future versions are likely to include at least the basic approaches for handling missing values. Regularly check https://github.com/MERademaker/cSEM/ to get the latest updates.
Specify a model
Models are defined using lavaan model syntax. Currently, only the “standard” lavaan model syntax is supported. This comprises:
 The definition of a latent variable/common factor (or more
precisely: the definition of a concept modeled as a common factor) by
the “
=~
” operator.  The definition of a composite (or more precisely: the definition of
a concept modeled as a composite) by the “
<~
” operator.  The specification of regression equations by the “
~
” operator.  The definition of error (co)variances, indicator correlations, or
correlations between exogenous constructs using the “
~~
” operator.
cSEM handles linear, nonlinear and hierarchical
models. Syntax for each model is illustrated below using variables of
the buildin satisfaction
dataset. For more information see
the lavaan
syntax tutorial.
Linear models
A typical linear model would look like this:
< "
model # Structural model
EXPE ~ IMAG
QUAL ~ EXPE
VAL ~ EXPE + QUAL
SAT ~ IMAG + EXPE + QUAL + VAL
LOY ~ IMAG + SAT
# Composite model
IMAG <~ imag1 + imag2 + imag3 # composite
EXPE <~ expe1 + expe2 + expe3 # composite
QUAL <~ qual1 + qual2 + qual3 + qual4 + qual5 # composite
VAL <~ val1 + val2 + val3 # composite
# Reflective measurement model
SAT =~ sat1 + sat2 + sat3 + sat4 # common factor
LOY =~ loy1 + loy2 + loy3 + loy4 # common factor
# Measurement error correlation
sat1 ~~ sat2
"
Note that the operator <~
tells cSEM
that the concept to its left is modeled as a composite; the operator
=~
tells cSEM that the concept to its left
is modeled as a common factor. ~~
tells
cSEM that the measurement errors of sat1
and sat2
are assumed to correlate.
Nonlinear models
Nonlinear terms are specified as interactions using the dot operator
"."
. Nonlinear terms include interactions and exponential
terms. The latter is described in model syntax as an “interaction with
itself”, e.g., x_1^3 = x1.x1.x1
. Currently the following
terms are allowed
 Single, e.g.,
eta1
 Quadratic, e.g.,
eta1.eta1
 Cubic, e.g.,
eta1.eta1.eta1
 Twoway interaction, e.g.,
eta1.eta2
 Threeway interaction, e.g.,
eta1.eta2.eta3
 Quadratic and twoway interaction, e.g.,
eta1.eta1.eta3
A simple example would look like this:
< "
model # Structural model
EXPE ~ IMAG + IMAG.IMAG
# Composite model
EXPE <~ expe1 + expe2
IMAG <~ imag1 + imag2
"
Hierarchical (second order) models
Currently only secondorder models are supported. Specification of the secondorder construct takes place in the measurement/composite model.
< "
model # Structural model
SAT ~ QUAL
VAL ~ SAT + QUAL
# Reflective measurement model
SAT =~ sat1 + sat2
VAL =~ val1 + val2
# Composite model
IMAG <~ imag1 + imag2
EXPE <~ expe1 + expe2
# Secondorder term
QUAL =~ IMAG + EXPE
"
In this case QUAL
is modeled as a secondorder common
factor measuring IMAG
and EXPE
, where
IMAG
is modeled as a composite and and EXPE
is
itself a common factor.
Estimate using csem()
csem()
is the central function of the package. Although
it is possible to estimate a model using individual functions called by
csem()
(such as parseModel()
,
processData()
, calculateWeightsPLS()
,
estimatePath()
etc.) using R’s :::
mechanism
for nonexported functions, it is virtually always easier, safer and
quicker to use csem()
instead (this is why these functions
are not exported).
csem()
accepts all models and data types described
above. The result of a call to csem()
is always an object of
class cSEMResults
. Technically, the resulting object has an
additional class attribute, namely cSEMResults_default
,
cSEMResults_multi
or cSEMResults_2ndorder
that
depends on the type of model and/or data provided, however, users
usually do not need to worry since postestimation functions
automatically work on all classes.
The simplest possible call to csem()
involves a data set
and a model:
require(cSEM)
< "
model # Path model / Regressions
eta2 ~ eta1
eta3 ~ eta1 + eta2
# Reflective measurement model
eta1 =~ y11 + y12 + y13
eta2 =~ y21 + y22 + y23
eta3 =~ y31 + y32 + y33
"
< csem(.data = threecommonfactors, .model = model)
a a
## ________________________________________________________________________________
##  Overview 
##
## Estimation was successful.
##
## The result is a list of class cSEMResults with list elements:
##
##  Estimates
##  Information
##
## To get an overview or help type:
##
##  ?cSEMResults
##  str(<objectname>)
##  listviewer::jsondedit(<objectname>, mode = 'view')
##
## If you wish to access the list elements directly type e.g.
##
##  <objectname>$Estimates
##
## Available postestimation commands:
##
##  assess(<objectname>)
##  infer(<objectname)
##  predict(<objectname>)
##  summarize(<objectname>)
##  verify(<objectname>)
## ________________________________________________________________________________
This is equivalent to:
csem(
.data = threecommonfactors,
.model = model,
.approach_cor_robust = "none",
.approach_nl = "sequential",
.approach_paths = "OLS",
.approach_weights = "PLSPM",
.conv_criterion = "diff_absolute",
.disattenuate = TRUE,
.dominant_indicators = NULL,
.estimate_structural = TRUE,
.id = NULL,
.iter_max = 100,
.normality = FALSE,
.PLS_approach_cf = "dist_squared_euclid",
.PLS_ignore_structural_model = FALSE,
.PLS_modes = NULL,
.PLS_weight_scheme_inner = "path",
.reliabilities = NULL,
.starting_values = NULL,
.tolerance = 1e05,
.resample_method = "none",
.resample_method2 = "none",
.R = 499,
.R2 = 199,
.handle_inadmissibles = "drop",
.user_funs = NULL,
.eval_plan = "sequential",
.seed = NULL,
.sign_change_option = "no"
)
See the csem()
documentation for details on the
arguments.
Inference
By default, no inferential quantities are calculated since
compositebased approaches, generally, do not have closedform solutions
for standard errors. cSEM relies on the
bootstrap
or jackknife
to estimate standard
errors, test statistics, critical quantiles, and confidence
intervals.
cSEM offers two ways to compute resamples:
 Inference can be done by first setting argument
.resample_method
to"jackkinfe"
or"bootstrap"
to perform resampling and subsequently useinfer()
(or more convenientlysummarize()
which internally callsinfer()
) to compute the actual inferential quantities of interest.  The same result is achieved by passing a
cSEMResults
object toresamplecSEMResults()
and subsequently usingsummarize()
orinfer()
.
< csem(.data = threecommonfactors, .model = model, .resample_method = "bootstrap")
b1 < resamplecSEMResults(a) b2
Several confidence intervals are implemented, see
?infer()
:
summarize(b1)
## ________________________________________________________________________________
##  Overview 
##
## General information:
## 
## Estimation status = Ok
## Number of observations = 500
## Weight estimator = PLSPM
## Inner weighting scheme = "path"
## Type of indicator correlation = Pearson
## Path model estimator = OLS
## Secondorder approach = NA
## Type of path model = Linear
## Disattenuated = Yes (PLSc)
##
## Resample information:
## 
## Resample method = "bootstrap"
## Number of resamples = 499
## Number of admissible results = 499
## Approach to handle inadmissibles = "drop"
## Sign change option = "none"
## Random seed = 928168071
##
## Construct details:
## 
## Name Modeled as Order Mode
##
## eta1 Common factor First order "modeA"
## eta2 Common factor First order "modeA"
## eta3 Common factor First order "modeA"
##
##  Estimates 
##
## Estimated path coefficients:
## ============================
## CI_percentile
## Path Estimate Std. error tstat. pvalue 95%
## eta2 ~ eta1 0.6713 0.0451 14.8990 0.0000 [ 0.5778; 0.7605 ]
## eta3 ~ eta1 0.4585 0.0795 5.7659 0.0000 [ 0.3194; 0.6176 ]
## eta3 ~ eta2 0.3052 0.0837 3.6452 0.0003 [ 0.1276; 0.4566 ]
##
## Estimated loadings:
## ===================
## CI_percentile
## Loading Estimate Std. error tstat. pvalue 95%
## eta1 =~ y11 0.6631 0.0429 15.4578 0.0000 [ 0.5712; 0.7448 ]
## eta1 =~ y12 0.6493 0.0385 16.8502 0.0000 [ 0.5677; 0.7211 ]
## eta1 =~ y13 0.7613 0.0338 22.5356 0.0000 [ 0.6936; 0.8303 ]
## eta2 =~ y21 0.5165 0.0510 10.1303 0.0000 [ 0.4177; 0.6135 ]
## eta2 =~ y22 0.7554 0.0364 20.7282 0.0000 [ 0.6785; 0.8209 ]
## eta2 =~ y23 0.7997 0.0351 22.7760 0.0000 [ 0.7322; 0.8655 ]
## eta3 =~ y31 0.8223 0.0327 25.1707 0.0000 [ 0.7576; 0.8794 ]
## eta3 =~ y32 0.6581 0.0400 16.4411 0.0000 [ 0.5837; 0.7339 ]
## eta3 =~ y33 0.7474 0.0392 19.0440 0.0000 [ 0.6735; 0.8306 ]
##
## Estimated weights:
## ==================
## CI_percentile
## Weight Estimate Std. error tstat. pvalue 95%
## eta1 <~ y11 0.3956 0.0230 17.1896 0.0000 [ 0.3484; 0.4379 ]
## eta1 <~ y12 0.3873 0.0198 19.5585 0.0000 [ 0.3460; 0.4259 ]
## eta1 <~ y13 0.4542 0.0202 22.4512 0.0000 [ 0.4161; 0.4994 ]
## eta2 <~ y21 0.3058 0.0262 11.6602 0.0000 [ 0.2539; 0.3545 ]
## eta2 <~ y22 0.4473 0.0207 21.5786 0.0000 [ 0.4064; 0.4868 ]
## eta2 <~ y23 0.4735 0.0205 23.0671 0.0000 [ 0.4350; 0.5105 ]
## eta3 <~ y31 0.4400 0.0188 23.3986 0.0000 [ 0.4007; 0.4738 ]
## eta3 <~ y32 0.3521 0.0187 18.7931 0.0000 [ 0.3156; 0.3871 ]
## eta3 <~ y33 0.3999 0.0185 21.6690 0.0000 [ 0.3648; 0.4352 ]
##
##  Effects 
##
## Estimated total effects:
## ========================
## CI_percentile
## Total effect Estimate Std. error tstat. pvalue 95%
## eta2 ~ eta1 0.6713 0.0451 14.8990 0.0000 [ 0.5778; 0.7605 ]
## eta3 ~ eta1 0.6634 0.0397 16.7009 0.0000 [ 0.5825; 0.7299 ]
## eta3 ~ eta2 0.3052 0.0837 3.6452 0.0003 [ 0.1276; 0.4566 ]
##
## Estimated indirect effects:
## ===========================
## CI_percentile
## Indirect effect Estimate Std. error tstat. pvalue 95%
## eta3 ~ eta1 0.2049 0.0552 3.7100 0.0002 [ 0.0888; 0.3083 ]
## ________________________________________________________________________________
Or directly via infer()
< infer(b1, .quantity = c("CI_standard_z", "CI_percentile"), .alpha = c(0.01, 0.05))
ii $Path_estimates ii
## $CI_standard_z
## eta2 ~ eta1 eta3 ~ eta1 eta3 ~ eta2
## 99%L 0.5552935 0.2580104 0.08520027
## 99%U 0.7874221 0.6676746 0.51646494
## 95%L 0.5830437 0.3069845 0.13675666
## 95%U 0.7596718 0.6187004 0.46490855
##
## $CI_percentile
## eta2 ~ eta1 eta3 ~ eta1 eta3 ~ eta2
## 99%L 0.5505414 0.2593851 0.09708731
## 99%U 0.7802155 0.6611865 0.50012919
## 95%L 0.5778226 0.3194488 0.12759854
## 95%U 0.7605403 0.6176354 0.45655261
Both bootstrap and jackknife resampling support platformindependent
multiprocessing as well as random seeds via the future framework.
For multiprocessing simply set .eval_plan = "multiprocess"
in which case the maximum number of available cores is used if not on
Windows. On Windows as many separate R instances are opened in the
background as there are cores available instead. Note that this
naturally has some overhead. Consequently, for a small number of
resamples multiprocessing will generally not be faster compared to
sequential (single core) processing (the default). Seeds are set via the
.seed
argument. A typical call would look like this:
< csem(
b .data = satisfaction,
.model = model,
.resample_method = "bootstrap",
.R = 999,
.seed = 98234,
.eval_plan = "multiprocess")
# Output omitted
Apply postestimation functions
There are 5 major postestimation function and 4 testfamily functions:
assess()

Assess the quality of the estimated model without conducting a statistical test. Quality in this case is taken to be a catchall term for all common aspects of model assessment. This mainly comprises fit indices, reliability estimates, common validity assessment criteria and other related quality measures/indices that do not rely on a formal test procedure. In cSEM a generic (fit) index or quality/assessment measure is referred to as a quality criterion.
infer()

Calculate common inferential quantities. For users interested in the estimated standard errors and/or confidences intervals
summarize()
will usually be more helpful as it has a much more userfriendly print method. predict()

Predict indicator scores of endogenous constructs based on the procedure introduced by Shmueli et al. (2016).
summarize()

Summarize a model. The function is mainly called for its side effect, the printing of a structured summary of the estimates. It also provides most estimates in userfriendly data frames. The data frame format is usually much more convenient if users intend to present the results in e.g., a paper or a presentation.
verify()

Verify admissibility of the estimated quantities for a given model. Results based on an estimated model exhibiting one of the following defects are deemed inadmissible: nonconvergence, loadings and/or (congeneric) reliabilities larger than 1, a construct VCV and/or a modelimplied VCV matrix that is not positive (semi)definite.
The test_*
family of postestimation functions
testHausman()

The regressionbased Hausman test for SEM.
testOMF()

Test for overall model fit based on Beran and Srivastava (1985). See also Dijkstra and Henseler (2015).
testMGD()

Test for group differences using several different approaches such as e.g., the one described in Klesel et al. (2019).
testMICOM()

Test of measurement invariance of composites proposed by Henseler, Ringle, and Sarstedt (2016)
The do_*
family of postestimation functions
doIPMA()

Performs an importanceperformance matrix analysis (IPMA).
doNonlinearEffectsAnalysis()

Performs nonlinear effects analysis such as floodlight and surface analysis as described in e.g., Spiller et al. (2013).
doRedundancyAnalysis()

Performs a redundancy analysis (RA) as proposed by Hair et al. (2016) with reference to Chin (1998).
Technically, postestimation functions are generic function with
methods for objects of class cSEMResults_default
,
cSEMResults_multi
, cSEMResults_2ndorder
. In
cSEM every cSEMResults_*
object must also
have class cSEMResults
for internal reasons. When using one
of the major postestimation functions, method dispatch is therefore
technically done on one of the cSEMResults_*
class
attributes, ignoring the cSEMResults
class attribute. As
long as a postestimation function is used directly method dispatch is
not of any practical concern to the enduser. The difference, however,
becomes important if a user seeks to directly invoke an internal
function which is called by one of the postestimation functions (e.g.,
calculateAVE()
or calculateHTMT()
as called by
assess()
). In this case, only objects of class
cSEMResults_default
are accepted as this ensures a specific
structure. Therefore, it is important to remember that internal
functions are generally not generic.
Principles underlying cSEM
cSEM is based on a number of principles, that have shaped its design, terminology and scope. These principles are discussed below
Model vs. Estimation
The way different concepts and their relationship are modeled is strictly distinct from how they are estimated. Hence we strictly distinguish between concepts modeled as common factors (or composites) and the actual estimation for a given model. In our opinion, these differences are fundamental to understanding the scope and limits of a certain approach. The most notable consequence is that approaches such as partial least squares and everything related to it (e.g., the modes) or generalized structured component analysis are “only” considered as estimators/estimation approaches for a given model.
Composites in a composite model vs. composites in a common factor model and disattenuation
By virtue of the package, cSEM uses compositebased
estimators/approaches only. Depending on the postulated model, linear
compounds may therefore either serve as a composite as part of the
composite model or as a proxy/standin for a common factor. If a concept
is modeled as a common factor, proxy correlations, proxyindicator
correlations and path coefficients are inconsistent estimates for their
supposed construct level counterparts (construct correlations, loadings
and path coefficients) unless the proxy is a perfect representation of
its construct level counterpart. This is commonly referred to as
attenuation bias. Several approaches have been
suggested to correct for these biases. In cSEM
estimates are correctly dissattenuated by default if any of the concepts
involved is modeled as a common factor! Disattentuation is controlled by
the .disattenuate
argument of csem()
.
Example
< "
model ## Structural model
eta2 ~ eta1
## Measurement model
eta1 <~ item1 + item2 + item3
eta2 =~ item4 + item5 + item6
"
# Identical
csem(threecommonfactors, model)
csem(threecommonfactors, model, .disattenuate = TRUE)
# To supress automatic disattenuation
csem(threecommonfactors, model, .disattenuate = FALSE)
Note that since .approach_weights = "PLSPM"
and
.disattentuate = TRUE
by default (see for The role of the weighting scheme and partial least
squares (PLS) below) and one of the concepts in the model above is
modeled as a common factor, composite (proxy) correlations, loadings and
path coefficients are adequately disattenuated using the correction
approach commonly known as consistent partial least squares
(PLSc). If .disattenuate = FALSE
or all concepts
are modeled as composites “proper” PLS values are returned.
The role of the weighting scheme and partial least squares (PLS)
In principal, any weighted combination of appropriately chosen observables can be used to estimate structural relationships between these compounds. Hence, any conceptual or methodological issue discussed based on a composite build by a given (weighting) approach may equally well be discussed for any other potential weighting scheme. The appropriateness or potential superiority of a specific weighting approach such as “partial least squares path modeling” (PLSPM) over another such as “unit weights” (sum scores) or generalized structured component analysis (GSCA) is therefore to some extent a question of relative appropriateness and relative superiority.
As a notable consequence, we believe that well known approaches such
partial least squares path modeling (PLSPM) and generalized structured
component analysis (GSCA) are  contrary to common belief  best
exclusively understood as prescriptions for forming linear compounds
based on observables, i.e., as weighting approaches. Not more, not
less.^{1} In
cSEM this is reflected by the fact that
"PLS"
and "GSCA"
are choices of the
.approach_weights
argument.
< "
model ## Structural model
eta2 ~ eta1
## Composite model
eta1 <~ item1 + item2 + item3
eta2 <~ item4 + item5 + item6
"
### Currently the following weight approaches are implemented
# Partial least squares path modeling (PLS)
csem(threecommonfactors, model, .approach_weights = "PLSPM") # default
# Generalized canonical correlation analysis (Kettenring approaches)
csem(threecommonfactors, model, .approach_weights = "SUMCORR")
csem(threecommonfactors, model, .approach_weights = "MAXVAR")
csem(threecommonfactors, model, .approach_weights = "SSQCORR")
csem(threecommonfactors, model, .approach_weights = "MINVAR")
csem(threecommonfactors, model, .approach_weights = "GENVAR")
# Generalized structured component analysis (GSCA)
csem(threecommonfactors, model, .approach_weights = "GSCA")
# Principal component analysis (PCA)
csem(threecommonfactors, model, .approach_weights = "PCA")
# Factor score regression (FSR) using "unit", "bartlett" or "regression" weights
csem(threecommonfactors, model, .approach_weights = "unit")
csem(threecommonfactors, model, .approach_weights = "bartlett")
csem(threecommonfactors, model, .approach_weights = "regression")
Literature
In fact, labels such as PLSPM and even more so PLSSEM are misleading as they create the impression that PLS(PM) is somehow capable of more than other compositebased approaches. While among compositebased approaches, methodological research surrounding composites formed using weights obtained by the PLS(PM) algorithm is most advanced, the PLS algorithm remains a weighting scheme in its core.↩︎