[Bug]: report median in case normality assumptions are not met

[zmirasilman]

JASP Version

0.95.4

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

wrong information is presented
in case normality cannot be assumed descriptive should be basesd on no parametric not mean & SD
also the summary of descriptive should be relevant for the paired comparison should

Expected Behaviour

Steps to Reproduce

use any data

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.

[EJWagenmakers]

We could add the median and IQR. What do you think @JohnnyDoorn @vandenman

[tomtomme]

@zmirasilman maybe you forgot, but again, this is a duplicate, see my answer to your older identical request here: #3989 (comment)

[zmirasilman]

Sorry for the duplication. When using JASP in different teaching situations, I sometimes point out things that feel missing based on what I see in students’ work. Please let me know if you would prefer that I skip repeating such points and avoid sending additional requests. I believe I may have repeated a request related to paired analyses- so sorry for that as well. One last recommendation from a teaching perspective is to mark descriptive information as default and even locate is as the first table before the hypothesis testing similarly to SPSS. Without this, students often "jump" directly to hypothesis testing and draw conclusions without first understanding the data. Thanks Zmira

…

------------------------------------ Zmira Silman Biostatistical consulting https://www.dibiz.com/zmiras Mobile: 052-2369239

On Tue, Jan 20, 2026 at 5:38 PM Thomas Langkamp ***@***.***> wrote: *tomtomme* left a comment (jasp-stats/jasp-issues#4016) <#4016 (comment)> @zmirasilman <https://github.com/zmirasilman> maybe you forgot, but again, this is a duplicate, see my answer to your older identical request here: #3989 (comment) <#3989 (comment)> — Reply to this email directly, view it on GitHub <#4016 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ442DFWASJRPNQQ2IXLY3T4HZDYRAVCNFSM6AAAAACSI3AWXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONZTGUYTMNRTHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>