I would like to conduct a one-factor CFA on a set of 10 categorical co-parenting items collected from 111 couples. I have data from each spouse within the couple; there are no covariates and no weights. I have read through “Example 9.7: Two-level CFA with categorical factor indicators..” in the M-Plus Users Guide but would like to clarify 1. How to organize my data file. Specifically, I have one couple’s data per row with a COUPLE ID identifier and each item identified by a subscript to denote father or mother (e.g. F1 – F10, M1 – M10). Is this correct? 2. Since I just expect one co-parenting factor, my attempt at Model syntax is:
%WITHIN% Fw BY F1 – F10 M1 – M10; %BETWEEN% Fb BY F1 – F10 M1 – M10;
Is this correct? Am I missing anything?
Any feedback you can provide will be most appreciated! Donna
There are two ways you can approach couple data. The first way is a single-level analysis. Here you have one record per couple with different variables names for each member of the couple. This approach is described in the following paper:
Khoo, S.T. & Muthén, B. (2000). Longitudinal data on families: Growth modeling alternatives. Multivariate Applications in Substance use Research, J. Rose, L. Chassin, C. Presson & J. Sherman (eds.), Hillsdale, N.J.: Erlbaum, pp. 43-78.
The second way is a two-level analysis. Here each couple's data would reside on separate records and a cluster variable would specify the couple id. The cluster variable would be couple.
I trying to do a CFA for 2 constructs with each having 5 categorical indicators. However these 2 constructs are answered (survey of 130 firms) by two persons (hence now 4 constructs) in each firm. Hence there is a dyad. Could you please direct me to files/handouts/articles where I can get an example to do this CFA for 4 constructs please. Also kindly suggest whether I should use 'analysis: type = complex ' OR 'analysis: type = twolevel'; how to arrive at a conclusion when to use which type of analysis for dyadic data? My sincere gratitude in advance.
Thank you very much. I was looking more for simple/basic examples of CFA for actor partner interdependence model type (dyad of couples in same firm), like the two people here in my research where one is senior manager and the other his/her subordinate, however both answer the same two constructs. Kindly correct me here please because I thought slide 52/56 were more like growth models. Sincerely Arun
Slide 52/56 can be applied to any model. The advantage is that you have access to more parameters. The non-independence of observations because of the dyad is taken into account by the multivariate nature of the data. You have a set of variables for each member of the dyad. If that is not of interest, you can use TYPE=COMPLEX or TYPE=TWOLEVEL. These are the three options you have for taking non-independence of observations into account.
Thank you for the clarification. Could you please direct me to Mplus examples from book 'Dyadic data analysis by Kenny Kashy Cook'. Also to get a more thorough understanding of dyadic data analysis using SEM what are the papers/handouts/books by Muthen(s)/statmodel website should I refer to. Please advice. Sincerely Arun. Once again my sincere gratitude for your ever quick help/advice !
Dear Arun--I have used Mplus to analyze dyadic data in thae past. I certainly agree with Linda's suggestion about the three alternative approaches to dyadic data in Mplus. I would go further and say that the multivariate (or wide) approach in Mplus would be the most straightforward and flexible way to go for the type of dyadic data that you are describing.
Dave Kenny has a website (http://davidakenny.net/kkc/kkc.htm) for his Dyadic Data Analysis book where there are example datasets and some code (but not for Mplus). If you point out a particular analysis that you would like to replicate in Mplus, feel free to note the chapter and page number and I can post the corresponding Mplus code to do it.
Dear Jean-Philippe: Thank you, very kind of you to help. I did run CFAs for the two constructs ( for each person- CEO & CEO's subordinate-Champion in the dyad ) using multivariate approach. However the model didn't converge. I thought the problem was complicated due to categorical indicators. Hence I tried param = theta. Still the model is not converging. But, am not very confident whether what am doing here is correct. Because the data file has 130 records with all the 10 indicators ( 5 for each construct) for each person in the dyad in the same row & in this multivariate approach am not explicitly telling mplus to account for the dyad say using some cluster variable (which is here the recordid itself)? ! CODE snippet CATEGORICAL = champintl champDiversification champMA champSell champRD CEODiversification CEOMA CEOSell CEORD CEOIntl ; param = theta; Model: iChamp Schamp | champDiversification@0champMA@1champSell@2champRD@3champintl@4 ; iCEO sCEO | CEODiversification@0 CEOMA@1CEOSell@2CEORD@3CEOIntl@4;
What you have here looks more like a growth model specification and not the kind of factor model you described wanting to run earlier. I think the following might be closer to what you are looking for:
Model: Champ BY champDiversification champMA champSell champRD champintl; CEO BY CEODiversification CEOMA CEOSell CEORD CEOIntl; champDiversification champMA champSell champRD champintl PWITH CEODiversification CEOMA CEOSell CEORD CEOIntl;
If you have 130 rows of data in your dataset and you have separate variables for Partner1 and Partner2 in your dyads, then this model syntax represents the multivariate approach and the dyadic interdependence is reflected in the covariance between the partners' factors and the covariances between the corresponding items each partner provides (see the last line of code with the PWITH statement).
Dear Arun--When it comes to dyadic modeling, what I described would be a general approach to doing CFA on dyadic data where there are separate partner 1 and partner 2 factors. There are other approaches to dyadic data that conceive of a latent variable as a common cause of the partner 1 and partner 2 observed variables. But more generally, a dyadic approach is typically reflective of a more general multivariate approach to data analysis where partners are repeated measures of the couple (as in the case for longitudinal data). Best wishes...
I am running a CFA with dyadic data. The dyad members are indistinguishable.
I am using a pairwise (double-entry) dataset and following instructions in Kenny, Kashy, & Cook, 2006 (p. 116). The text recommends weighting each case by 0.5 since there are two entries per person.
How would I accomplish this in MPlus? The "weight" option does not seem right because the weight is rescaled depending on the number of cases. I also considered "freqweight" but this only accepts integer values. The twolevel options do not make sense here because this is not a MLM.
Perhaps I can get around this weighting issue? I noticed that in the related article, Olsen & Kenny, 2006, there is no mention of weights. But how else would I adjust the standard errors for the various parameter estimates?
I think that may be an outdated way of handling dyadic data. You should have the data in wide format where multivariate analysis takes care of non-independence of observations. See the following reference:
James L. Peugh, David DiLillo & Jillian Panuzio (2013) Analyzing Mixed-Dyadic Data Using Structural Equation Models Structural Equation Modeling. Pages: 314-337 DOI: 10.1080/10705511.2013.769395
See also the Topic 8 course handout on the website under Multivariate Approach to Multilevel Modeling.
I am attempting to fit a two-factor CFA with continuous indicators from dyadic data. We have data in the "long" format where each case represents a person and then we have a couple ID. I told Mplus CLUSTER = ID and then here is my ANALYSIS syntax below.
EFA factors in the same set as AWAP must have the same set of factor indicators. Problem with: AWAP BY USE COST BY USE (not specified or fixed) COST BY EFFECT (not specified or fixed) COST BY DIFF COST BY DRAIN COST BY IMPORT (not specified or fixed) COST BY ATTRCT (not specified or fixed) COST BY CONFLCT COST BY COMMIT (not specified or fixed) COST BY SATIS (not specified or fixed)