Thanks for that Terrence, your help is always much appreciated.
A small follow-up question, so I can better understand the syntax. Say I generate measEq.syntax for two levels of measurement invariance, e.g.
- long.equal = c("thresholds") vs.
- long.equal = c("thresholds", "loadings")
As expected, the first model constrains only the thresholds, while the second model constrains thresholds and item loadings.
However, what I find interesting is that syntax 2 also releases some constraints which are present in syntax 1. Specifically, syntax 2 allows all common factor variances at the second occasion to be freely estimated.
Comparing a subset of the syntax (highlighted are the lines of syntax which differ between the two):
-
## COMMON-FACTOR
VARIANCES:
slp1 ~~ 1*slp1 + psi.1_1*slp1
slp2 ~~ 1*slp2 + psi.2_2*slp2
dep1 ~~ 1*dep1 + psi.3_3*dep1
dep2 ~~ 1*dep2 + psi.4_4*dep2
man1 ~~ 1*man1 + psi.5_5*man1
man2 ~~ 1*man2 + psi.6_6*man2
-
## COMMON-FACTOR
VARIANCES:
slp1 ~~ 1*slp1 + psi.1_1*slp1
slp2
~~ NA*slp2 + psi.2_2*slp2
dep1 ~~ 1*dep1 + psi.3_3*dep1
dep2
~~ NA*dep2 + psi.4_4*dep2
man1 ~~ 1*man1 + psi.5_5*man1
man2
~~ NA*man2 + psi.6_6*man2
My understanding of measurement invariance (which is admittedly, quite elementary) is that when testing increasingly strict levels of invariance, constraints are added and not released.
So why is it the case that when going from 1 > 2, certain constraints are released?
N.B. I have also noticed this behaviour when comparing
long.equal = c("thresholds", "loadings") with
long.equal = c("thresholds", "loadings", "intercepts")syntax.
Thanks