New JASP version not working

Comments

• Michael_Jasper

  November 20

  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?
• EJ

  November 21

  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.
• Michael_Jasper

  November 21

  This seems similar, if not exactly the same:

  https://github.com/jasp-stats/jasp-issues/issues/2924

  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.
• EJ

  November 21

  This is not the same issue I don't think. Did you post yours?
• Michael_Jasper

  November 22

  Is the same.

  To copy and paste the issue from that github post:

  ---------------------

  1. Start JASP
  2. Go to OPEN- DATA LIBRARY - DESCRIPTIVES
  3. Open Sleep.csv (though the same fault with other files)
  4. Opens file but with a warning in the top panel "The engine crashed trying to run the filter..."
  5. Select Descriptives - the window simply hangs at "Waiting for initialization (of the engine) of module: Descriptives" (but same faults with other options
  6. If you go into back into the data set and filter a variable but clicking it off and on again (x then tick) the problem resolves itself (that is the intialises the engine)

  -----------------------

  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.
• shun_wang

  November 25 edited November 25

  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.