cbratt

It also seems that 1.0 requires (1) variable names to be declared and (2) missing value to be declared, at least for one model I tested. That seems to pose...

Case solved. I believe this particular problem was my tendency to declare an mplusObject() without data, then update() the model with specific data. That worked like a charm in 0.7-3...

@cjvanlissa, you can see the original case here: https://github.com/michaelhallquist/MplusAutomation/issues/130, with a reproducible example for 0.8. @JWiley stated that update() wasn't meant to be used this way, but still considered it...

Thanks, @JWiley. Here is the result - no error detected. > example1 example1b fit1b summary(fit1b) Estimated using ML Number of obs: 32, number of (free) parameters: 3 Model: Chi2(df =...

Here is what should be a reproducible example of a problem with MplusAutomation and split data: library(tidyverse) library(MplusAutomation) data_split % group_by(gear) %>% group_split # The data are now in a...

Just to be clear: There is a workaround for this issue: Include preliminary data before updating with a data subset. # Declaring a model, AND INCLUDE PRELIMINARY DATA mymodel

@JWiley, it would also be great if a new model with added variable(s) in MODEL could be declared simply by using `update()`, without manipulating VARIABLES in the mplusObject. (My experience...

THERE WAS AN ERROR IN THE CODE SUBMITTED HERE. I WILL FIRST RESOLVE THAT ERROR.

I am aware of the need to include a reproducible example (and usually include code). But since developing one requires some work, I wanted to make sure that there actually...

A related wish would be the possibility to add arguments to a tidy_sem object. For instance something similar to # Original model model select(mpg, vs)) |> add_paths(vs ~ mpg) #...