New JASP version not working
With the latest JASP version I get it hanging for example when opening the ANOVA module with this error message given:
"Waiting for the initialization (of the engine) of module: ANOVA"
And seen this when opening other modules. It is completely unuseable and I am thinking to uninstall and go back to the prior version. Has anyone else had such problems?
Perhaps relatedly, when I input data I sometimes (but not always) see an error message "The engine crashed while trying to run the filter", which I never saw before with the prior version.
Comments
Completely unuseable.
Waiting to hear back from someone here before I uninstall and reinstall the prior version. But I don't know whether my nerves can withstand much more of this. Please has anyone got any redress of this? Anyone else seen the same?
I think we have seen a handful of these messages. I recommend that you search for this issue in our GitHub page -- I think these issues were solved. Regardless, the JASP team is always willing to assist, and your best bet if something does not work the way it should is to contact the team directly, by posting a bug report on our GitHub page (for details see https://jasp-stats.org/2018/03/29/request-feature-report-bug-jasp/). The more detail you add, the easier it will be to help you. But I strongly recommend searching the issue list for similar complaints.
Cheers,
E.J.
This seems similar, if not exactly the same:
But was left unresolved, and has been for some time. So I don't know where that leaves us. No point me just posting the same again. Unsure how to proceed now. Should I just revert to the old version of JASP? A real shame as I was really looking forward to using the Bayesian SEM, which is only in the latest version.
This is not the same issue I don't think. Did you post yours?
Is the same.
To copy and paste the issue from that github post:
---------------------
-----------------------
All be it I can't replicate 6 above, which is the basterdized fix of it, as I don't quite understand what they are referring to. Any expansion, greater explanation, of this would be greatly appreciated.
It is noteworthy that that bug report hasn't been closed and is still extant. There is just this workaround mentioned, which I can't quite understand.
Hi all,
From that issue link we still cannot get any useful log to debug this problem. could you please provide more log and debug information to find out what happened? comment on that issue or open a new one both are OK.
with Thanks
Shun Wang
The JASP team.