 Cross-Lagged Path Analysis & Standard...    Message/Author  Christopher Wiese posted on Tuesday, March 15, 2016 - 1:04 pm
Drs. Muthen,

Currently, I am working on a simple cross-lagged path analysis (i.e., not latent variables) with two variables measured at three time points. My question concerns the standardized parameter estimates. Specifically, when constraining the cross-lagged paths to be equal across time, the standardized estimates (STDYX - I'm using continuous control variables) are not equal. For example, the standardized estimate for Time 1 Variable X --> Time 2 Variable Y is not equal to Time 2 Variable X --> Time 3 Variable Y when that path is constrained to be equal in the code.

Is there a way to force these estimates to be equal? How would this be done and what would the potential implications for model fit be?  Linda K. Muthen posted on Tuesday, March 15, 2016 - 2:56 pm
The estimates are standardized using the standard deviations of the variables involved. If these are not the same, the standardized estimates will not be the same even if the raw estimates are held equal.  Christopher Wiese posted on Tuesday, March 15, 2016 - 4:13 pm
Thanks Linda - Quick Follow up.

Is it possible to constrain SDs to be equal? For instance, could I constrain X to have the same SD across the different time points?  Bengt O. Muthen posted on Tuesday, March 15, 2016 - 5:35 pm
You can constrain X variable variances to be equal across time but you still have the Y variances to contend with. But I would argue that you should focus on the equality of unstandardized coefficients. I would not confound them with (uninteresting) changes in variances and residual variances as you would if you focus on standardized coeffs.  Christopher Wiese posted on Wednesday, March 16, 2016 - 7:33 am
That makes perfect sense! Thank you very much for your response! I sincerely appreciate your time.  Tunde Ogunfowora posted on Friday, May 25, 2018 - 1:28 pm
Drs. Muthen,

A follow-up question regarding modeling cross-lagged path analysis (involving three time points). It is my understanding from a few published works that one should constrain the stability effects to be equal, as well as the cross-lagged paths. If this is done, as you noted above, the unstandardized estimates will be the same but the standardized estimates are likely to be different for paths constrained to be equal.
In this scenario, how does one test for mediation effects, given that one would use the same labels to constrain the relevant paths to be equal. Testing for mediation using path labels under model constraint (e.g., Med1 = a*b*c, where b is the label for two cross-lagged paths or two stability paths constrained to be equal) would be problematic.
Thank you.  Bengt O. Muthen posted on Friday, May 25, 2018 - 1:59 pm
Why would it be problematic?  Tunde Ogunfowora posted on Friday, May 25, 2018 - 3:07 pm
Below is a Sample syntax involving crossed lagged effects of two team processes each measured at three time points (T2, T3, T4), and subsequent effect on team performance (measured once at time 5):

TmCd_T3r on TmCd_T2r (b1);
TmCd_T4r on TmCd_T3r (b1);

Gcoh_T3 on Gcoh_T2 (b2);
Gcoh_T4 on Gcoh_T3 (b2);

Gcoh_T2 with TmCd_T2r;
GCoh_T3 with TmCd_T3r;
GCoh_T4 with TmCd_T4r;

TmCd_T3r on Gcoh_T2 (b3);
TmCd_T4r on Gcoh_T3 (b3);

Gcoh_T3 on TmCd_T2r (b4);
Gcoh_T4 on TmCd_T3r (b4);

TeamPerf on Gcoh_T4 (q)
TeamPerf on TmCd_T4r (s);

One possible indirect path from Gcoh_T2 to TeamPerf is:
Gcoh_T2 --> Gcoh_T3 --> Gcoh_T4 --> Team perf.
However, given that (Gcoh_T2 --> Gcoh_T3) is constrained to be equal to (Gcoh_T3 --> Gcoh_T4) as denoted by the label b2, the mediation effect would be b2*b2*q. Is it a problem in this case because b2 (unstandardized) is the same value? In calculating the indirect effect, it seems to me that mplus will only actually multiple b2*q rather than b2*b2*q. If these paths were not constrained to be equal, this would not be a problem because the paths would have different labels.

Thanks  Bengt O. Muthen posted on Friday, May 25, 2018 - 5:30 pm
If you say b2*b2*q in Model Constraint, Mplus will compute just that; no problem. You can check in the output.  Tunde Ogunfowora posted on Friday, May 25, 2018 - 7:56 pm
I see. Thank you.    Topics | Tree View | Search | Help/Instructions | Program Credits Administration