-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
default precisions for s_summary.numeric #979
Comments
currently we have inconsistent which I believe could be refined.
if range has 1 dp, then mean should have 2 dp |
hey @khatril , what do you think? I have no strong preference here. perhaps we should also consider, set them as the most commonly used? |
If this is the standard we can change the internal standard in tern to reflect that. We need only to be certain that there is alignment in what the new standards should be |
For 3.3 in the original issue, and specifically looking at variable such as STUDY DAY, does 3.3 suggest we should show min-max in its original precision, i.e. whole number? |
For reference, GDSR update from March 2023 includes the following details on number of decimal places: https://github.com/insightsengineering/sme-tasks/issues/639 |
This comment was marked as resolved.
This comment was marked as resolved.
Possible to achieve this now by doing |
3.1. Measures of location and dispersion (e.g., mean, median, variance, SD, SE, and corresponding confidence intervals) are displayed with 1 more decimal place of precision than the most precise collected data.
3.2. Percentiles (eg, Q1, Q3, 99th percentile) are displayed with 1 more decimal place of precision than the most precise collected data.
3.3. When data are summarized in the same unit as collected, the minimum and the maximum are displayed with the same number of decimal places of precision as the most precise collected data.
Originally posted by @barnett11 in insightsengineering/chevron#343 (comment)
The text was updated successfully, but these errors were encountered: