Closed hynekcigler closed 4 years ago
Update: I am sorry, the error is not possibly produced by difference between Mplus 7 and 8, but by fixing parameters. If I fix certain parameters to prespecified values, MplusAutomation read all the parameters as character. Unfortunately, I am not able to compare this behavior with Mplus 7 license.
Hi there, I've seen these kinds of errors many times... it almost always comes from Mplus having a section heading that I've never seen before. We have to trap each one of these individually, and they tend to change from version to version. It's usually a very quick and easy fix, but we need the .out files to reverse engineer that part.
Would you please upload the .out file (you may have to rename the suffix .txt for Github to like it) here? I can then take a look in more detail and figure out which section is being missed.
Thanks, Michael
I'm going to close this issue for now since I believe Mplus v8+ outputs parse correctly in general and I haven't gotten any further details from you about this.
-Michael
Dear dr. Hallquist, I have problem with extracting model parameters from Mplus 8. I tried also the newest version on GitHub, but the problem is still there. The class of parameters extracted from version 8 is character, but from version 7 it was numeric. There are also some more warnings
... and several more similar warnings (I suppose for each group one).
I use these parameters for subsequent analyses and it causes several problems as I have to use as.numeric in all the functions; shouldn't be the result the same for both Mplus versions?