-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mediation analysis termination #480
Comments
Could you please add the jasp file as a zip to this thread? |
This is a duplicate of #465 |
That’s great, thank you!
On 11 Sep 2019, at 12:27, Tim de Jong <[email protected]<mailto:[email protected]>> wrote:
This is a duplicate of #465<#465>
A fix for this will *hopefully* be available by next week in JASP 0.11
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#480?email_source=notifications&email_token=ANFBXYL53VFPD2DJ5OQFMUTQJDIZXA5CNFSM4IVSLNL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6OFHXY#issuecomment-530338783>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ANFBXYIFNFSECBHJPQQJ7ATQJDIZXANCNFSM4IVSLNLQ>.
|
It would nonetheless be good to try it out with a test case so we can confirm that it's indeed fixed. |
Hi! Is this fixed already? |
Hi medbuenaventura, It's solved. I've even tested this with the jasp files that were included in the issues. If you send me yours I can double check for you as well. Cheers, |
Have been using the same data for a number of regressions in JASP with no issues. Mediation analysis attempt: two scaled predictors, two scaled mediators, one scaled outcome, received this message:
This analysis terminated unexpectedly.
Error in rawToChar(as.raw(out)): embedded nul in string: 'X0/x80'
Tried the same predictors and mediators (no error message when only these are entered), with an ordinal outcome. Error message:
Estimation failed
Message:
lavaan ERROR: missing = “fiml” not available in the categorical setting
The text was updated successfully, but these errors were encountered: