[Bug]: Bayesian One Sample T test analysis terminated unexpectedly.

[drravikch]

JASP Version

0.19.1

Commit ID

No response

JASP Module

T-Tests

What analysis are you seeing the problem on?

No response

What OS are you seeing the problem on?

Windows 11

Bug Description

Expected Behaviour

The Bayesian analysis will be completed, and output results will be displayed without unexpected termination.

Steps to Reproduce

1. Open the file 'One sample t-test.csv.
2. Click T-tests, Bayesian One Sample-T test.
3. Transfer height to variables box.
4. Selct the input Options: as indicated in the manual

Log (if any)

No response

More Debug Information

I am learning Bayesian analysis. I opened the file the OSF Data Set file 'One sample t-test'.
I entered the input as given in the manual 'Bayesian inference in JASP A Guide For Students.
I got the error as shown in the attached file.
Request help to do successful analysis with JASP.
Thank you.
One sample t-test.csv

Final Checklist

• I have included a screenshot showcasing the issue, if possible.
• I have included a JASP file (zipped) or data file that causes the crash/bug, if applicable.
• I have accurately described the bug, and steps to reproduce it.

[tomtomme]

@drravikch
Thx for the report. With data from the data library this works just fine:

Same with your data:

there is a different error message from a plot, but that is not related I think. And that is an informative error message at least.

So maybe just try again? Possibly some sampling stuff went wrong during your analysis. Or can you reproduce the error repeatedly?

@vandenman
Or can this be win11 specific? I am testing on flatpak linux.

[drravikch]

Thank you. I will try that.

…

On Mon, 14 Oct 2024 at 4:19 AM, Thomas Langkamp ***@***.***> wrote: @drravikch <https://github.com/drravikch> Thx for the report. With data from the data library this works just fine: grafik.png (view on web) <https://github.com/user-attachments/assets/69096639-179b-4e70-9b74-cdd2fef004ff> Same with your data: grafik.png (view on web) <https://github.com/user-attachments/assets/cfa18ed7-86d2-47d1-b5d6-3c8c2c468dd8> there is a different error message from a plot, but that is not related I think. And that is an informative error message at least. So maybe just try again? Possibly some sampling stuff went wrong during your analysis. Or can you reproduce the error repeatedly? — Reply to this email directly, view it on GitHub <#2964 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJ6XUMGI3RUJUVFUVKXMJRTZ3N473AVCNFSM6AAAAABP3TODB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJQGQYDANZXGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[vandenman]

@tomtomme unlikely that it is a os specific issue, but it could be a state issue.

[tomtomme]

@drravikch
any news for us

@vandenman
how can we help with state issues?

[vandenman]

To replicate a state issue we need the exact sequence of clicks, in addition to the jasp file/ data. Often, state issues dissappear when refreshing an analysis.

[drravikch]

I tried repeating the One Sample t-test using the teaching OSF data set 'One sample t-test.csv'.
Now I get new problem in output of results.
One Sample t-test Output problem.docx
Problem in Bayesian One Sample T-Test output of results.pdf

[drravikch]

On reanalysis using the teaching data set One Sample t-test.csv, I get still problems in output of results.
Problem in Bayesian One Sample T-Test output of results.pdf
One Sample t-test Output problem.docx

[drravikch]

Thank you. I shall try your advice.

…

On Wed, Oct 16, 2024 at 8:49 AM Don van den Bergh ***@***.***> wrote: To replicate a state issue we need the exact sequence of clicks, in addition to the jasp file/ data. Often, state issues dissappear when refreshing an analysis. — Reply to this email directly, view it on GitHub <#2964 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJ6XUMAL6O6BG3OAPNEGRL3Z3ZOG3AVCNFSM6AAAAABP3TODB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJWG42TEMZQGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>