This looks like a (small) bug: if you explicitly set the estimator to
"WLSMV", you get the error message
Error in lav_options_set(opt) :
lavaan ERROR: missing="ml" is not allowed for estimator MLM, MLMV,
GLS, ULS, ULSM, ULSMV, DWLS, WLS, WLSM, WLSMV, PML
but without setting it explicitly, it is still set to the value
'default' when the check is done, thereby missing it.
But even if you specify missing = "ml", (or "direct" or "fiml"), lavaan
will do missing = "pairwise" anyway, because in the (categorical) code,
I just check for missing != "listwise". The only alternative (at least
for WLS and friends) is missing = "pairwise".
I will fix this after my holidays (end of august).
On 07/30/2018 01:27 AM, Terrence Jorgensen wrote:
> So call me extremely surprised when I used the "direct" option for
> missingness and treated the indicators as ordinal using WLSMV in
> lavaan. Can someone please clarify what exactly is the "direct"
> option doing at a technical level?
> That surprises me as well. From the ?lavOptions help page description
> of the missing= argument, "direct" is merely an alias for "fiml". Have
> you triedmissing = "pairwise" to see if that produces the "direct" behavior?
> Terrence D. Jorgensen
> Postdoctoral Researcher, Methods and Statistics
> Research Institute for Child Development and Education, the University
> of Amsterdam
> UvA web page: http://www.uva.nl/profile/t.d.jorgensen
> You received this message because you are subscribed to the Google
> Groups "lavaan" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to lavaan+un...@googlegroups.com