[Bug]: 0.001 in the input box becomes 1 in the output

[Jillderon]

JASP Version

0.95.1

Commit ID

No response

JASP Module

Equivalence T-Tests

What analysis are you seeing the problem on?

Bayesian Equivalence Independent T-Test

What OS are you seeing the problem on?

macOS Intel

Bug Description

When I set my equivalence bounds with three decimals in the input box, it will specify the equivalence bounds wrong in the output of the analysis. So my specified 0.001 in the input box becomes 1 in the output. Thus, giving me back the wrong bayes factors. This happens for each equivalence test within the module, so also the classical/frequentist tests.

The same happens for specifying the scale of the Cauchy prior, where my scale input of 0.001 becomes a 1 in the output.

Expected Behaviour

The equivalence bounds should be as specified in the input box

Steps to Reproduce

1. Load in data
2. set the equivalence bounds with three decimals

Log (if any)

No response

More Debug Information

No response

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]

@Jillderon
you used a comma instead of a dot. I do not think this is already possible, or is it?

@JorisGoosen
If I would use the setting below, will this effect only the output or also such input values so that I can use comma instead of dot?

[JorisGoosen]

Uhm, @Jillderon can you make a screenshot of the same settings as Thomas did?
Cause it looks like you have a comma as a decimal separator

Which means you also use a comma as decimal separator in the input fields.

Of courtse, if you dont want this you can switch to an american english locale, and for instance disable "thousands separators".

And I guess that also answers your question @tomtomme, yes, the inputs also use that locale.
I did fix this issue https://github.com/jasp-stats/INTERNAL-jasp/issues/2969 but too late for 0.95.2.
And it might be implicated in weird behaviour and so could also maybe have triggered it.

[JorisGoosen]

Or @Jillderon when you type "0.001" in the issue you actually mean that you typed "0,001" ?

[JorisGoosen]

Ive tried repropducing the bug bug I just get: