Latent between level variable? PreviousNext
Mplus Discussion > Multilevel Data/Complex Sample >
Message/Author
 Xu, Man posted on Tuesday, June 18, 2013 - 12:33 am
I am trying to update some old model results from Mplus 5.1 for a manuscript. When I ran the same input file in the Mplus 7.1, I got the below warning:

"A latent between-level variable is created for an x-variable but not referred to on the between level. Please check that this is what is intended. If this is not intended, specify the variable as a within variable. Problem with: PVIQUAD"

The old syntax originally ran in Mplus 5.1 is pasted below. I was wondering if there is a way to reproduce the old results in Mplus 7.1? Thanks!

WEIGHT IS STUWT;
BWEIGHT IS W_FSCHWT;
WTSCALE = CLUSTER;

USEVARIABLES ARE
Zkst16 ZPVSCIE pviquad;
cluster is SCHOOLID;
missing are all (999);

ANALYSIS:
TYPE is TWOLEVEL;

MODEL:
%WITHIN%

Zkst16 ON ZPVSCIE (b_within);
Zkst16 ON pviquad;

%BETWEEN%

Zkst16 ON ZPVSCIE (b_betwn);
 Linda K. Muthen posted on Tuesday, June 18, 2013 - 7:42 am
You need to mention pviquad in the between level as a covariate or put it on the WITHIN list.
 Xu, Man posted on Tuesday, June 18, 2013 - 8:42 am
Thank you. I just tried putting pviquad at within level (within is pviquad;) - because it was not estimated at between level previously. The model ran, and had the same number of free parameters as in the above script from v5.1, but it still doesn't seem to give the same results as from v5.1.

Is this due to updates between versions?
 Bengt O. Muthen posted on Tuesday, June 18, 2013 - 11:31 am
I would have to see the old 5.1 output to see what was done then, but not mentioning pviquad on between runs the risk that it is not handled right. The new warning is therefore helpful.

I would think that you want to include pviquad as yet another predictor of Zkst16 on between given that context often matters.
Back to top
Add Your Message Here
Post:
Username: Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Password:
Options: Enable HTML code in message
Automatically activate URLs in message
Action: