JASP Goes Blank When Computing Large Tables of Correlations

[amsa1234]

• JASP version: 12.2
• OS name and version: Windows 10
• Analysis: Pearson's correlation (for a large set of variables; in this case, 94 variables, 93 of which are the language features generated by the Linguistic Inquiry and Word Count software).
• Bug description: The whole output window simply goes blank after a while (see attached). It first looks as if it's computing (i.e., the variable names are shown, with blank entries where the r-values and p-values will appear), but then it all goes blank.
• Expected behaviour: The whole table of correlations should appear.
  

--->

[boutinb]

Hi @16665k00 Could you give us (in a zip format) the JASP log files: go to Preferences/Advanced/Logging options, click Log to file, then redo the reproduction path of this issue. When you click the Show Logs button, you should see the last 4 log files: 1 desktop & 4 engines log files.
Hopefully can we get some hints over this issue with these log files.

[EJWagenmakers]

This happens because, by mistake, JASP computes Kendall's tau for all correlations, even though it is not requested. This really, really slows down the computation time.
@Kucharssim , would be very good to have this fixed before the new release.

[EJWagenmakers]

@Kucharssim The output it correct (99.9% sure here, otherwise we would have to do a hotfix) so the tau's a hidden.

[Kucharssim]

@Kucharssim , would be very good to have this fixed before the new release.

Yes indeed, we already have a fix (jasp-stats/jaspRegression#1), but we need to test and merge it. It will be in the next release.

@16665k00 It would be great if you could please share with us your data, so that I can confirm that the fix really solves your problem. That would help us a lot.

[amsa1234]

Yes, of course. What email address can I send the data to you at?

…

On Friday, 1 May 2020, Simon Kucharsky ***@***.***> wrote: @Kucharssim <https://github.com/Kucharssim> , would be very good to have this fixed before the new release. Yes indeed, we already have a fix (jasp-stats/jaspRegression#1 <jasp-stats/jaspRegression#1>), but we need to test and merge it. It will be in the next release. @16665k00 <https://github.com/16665k00> It would be great if you could please share with us your data, so that I can confirm that the fix really solves your problem. That would help us a lot. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#712 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANB5F7Z7CPSG36LODP26ACLRPJ7GDANCNFSM4MREWFFA> .

[Kucharssim]

s.kucharsky@uva.nl, please, thank you!