search

jasp-stats / jasp-issues

This repository is solely meant for reporting of bugs, feature requests and other issues in JASP.
58 stars 29 forks source link

[Bug]: Group number doesn't update after filtering out some of them #2916

Closed nothik closed 2 days ago

nothik commented 2 days ago

JASP Version

0.19.0

Commit ID

No response

JASP Module

T-Tests

What analysis are you seeing the problem on?

Independent Samples T-Test

What OS are you seeing the problem on?

Windows 10

Bug Description

I have a grouping variable with 3 groups. When I filter out one of them, all corresponding entries appear in grey in the database. However, when I try running an independent samples t-test, I get an error message saying that there are 3 groups. Even when I use the edit function and completely delete the rows where the 3rd group appears, the system still remembers that there were initially 3 groups.

Expected Behaviour

The system should understand (as it did in previous versions of JASP) that there are now 2 groups remaining so that an independent samples t test is possible.

Steps to Reproduce

1.Open a database with one grouping variables with 3 groups, and one numerical variable. 2.Filter out one group. 3.Try making a t-test. ...

Log (if any)

No response

More Debug Information

No response

Final Checklist

github-actions[bot] commented 2 days ago

@nothik, thanks for taking the time to create this issue. If possible (and applicable), please upload to the issue website (https://github.com/jasp-stats/jasp-issues/issues/2916) a screenshot showcasing the problem, and/or a compressed (zipped) .jasp file or the data file that causes the issue. If you would prefer not to make your data publicly available, you can send your file(s) directly to us, issues@jasp-stats.org

nothik commented 2 days ago

image

nothik commented 2 days ago

I can't upload the .jasp file: image

EJWagenmakers commented 2 days ago

This was the reason for our 0.19.1 hotfix I believe! Could you try the latest version? I am closing this issue in the expectation that 0.19.1 has it fixed. Feel free to re-open if that is not the case.