-
Notifications
You must be signed in to change notification settings - Fork 1
/
README.Rmd
101 lines (72 loc) · 5.08 KB
/
README.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
---
output: github_document
---
<!-- README.md is generated from README.Rmd. Please edit that file -->
```{r, include = FALSE}
knitr::opts_chunk$set(
collapse = TRUE,
comment = "#>",
fig.path = "man/figures/README-",
out.width = "100%"
)
```
# rsprite2 - Identify Distributions that Match Reported Sample Parameters <img src='man/figures/logo.png' align="right" style="float:right; height:120px;" />
<!-- badges: start -->
[](https://github.com/LukasWallrich/rsprite2/actions)
[](https://app.codecov.io/gh/LukasWallrich/rsprite2?branch=master)
[](https://github.com/LukasWallrich/rsprite2)
[](https://github.com/LukasWallrich/rsprite2/actions)
<!-- badges: end -->
This package creates possible distributions based on reported sample parameters, using the SPRITE algorithm. This can be used to check what the original sample might have looked like, and thus to understand the data generation process better. This can help with the identification of fabricated data or misreported parameters, but also with checking whether sample characteristics such as floor/ceiling effects might suggest that findings are spurious.
For that, it implements the SPRITE algorithm proposed by [Heathers et al. (2018)](https://peerj.com/preprints/26968/). Much of the code for is based on [Nick Brown's rSPRITE shiny app](https://github.com/sTeamTraen/rSPRITE), with some extensions. If you are just interested in interactive use and do not need these extensions (see advanced usage below) that Shiny online app (see https://shiny.ieis.tue.nl/sprite/) might be better for you.
The package also includes dedicated functions to run the GRIM and GRIMMER tests. `GRIM_test()` checks whether a reported mean based on integers is consistent with a given sample size, while `GRIMMER_test()` checks whether a reported standard deviation is consistent with a reported mean and sample size. They can help catch impossible distributions and reporting errors without running any simulations.
## Installation
rsprite2 can be installed from CRAN with:
```{r warning=FALSE, message=FALSE, eval=FALSE}
install.packages("rsprite2")
```
Or you might want to install the development version from GitHub:
```{r, warning=FALSE, message=FALSE, eval=FALSE}
install.packages("remotes")
remotes::install_github('LukasWallrich/rsprite2')
```
## Simple example
To create possible distributions, SPRITE needs the reported mean, standard deviation, sample size and range of values.
For instance, what distribution of 20 responses on a 1 to 5 scale might result in a mean of 2.2 and a standard deviation of 1.3?
```{r}
library(rsprite2)
sprite_parameters <- set_parameters(mean = 2.2, sd = 1.3, n_obs = 20, min_val = 1, max_val = 5)
find_possible_distribution(sprite_parameters)
```
If these means and standard deviations had been reported to two decimal places, they might be 2.20 and 1.33. NB: Given that trailing zeroes are ignored by R, you need to *specify the precision if mean or standard deviation ends in 0*.
```{r}
sprite_parameters <- set_parameters(mean = 2.20, m_prec = 2, sd = 1.32,
n_obs = 20, min_val = 1, max_val = 5)
find_possible_distribution(sprite_parameters)
```
To find more than one distribution that matches the parameters, you can use `find_possible_distributions()`
```{r}
find_possible_distributions(sprite_parameters, 10)
```
They can then be plotted to identify features that are shared across distributions.
```{r}
res <- find_possible_distributions(sprite_parameters, 10)
plot_distributions(res)
```
## Advanced features
### Multi-item scales
Often, several Likert-type items are averaged to measure a single construct (e.g., participants might be asked how happy, satisfied and fulfilled they are, with the results averaged into a measure of well-being). Possible resulting distribution can be explored by rsprite2 by specifying the `n_items` parameter.
```{r}
sprite_parameters <- set_parameters(mean = 1.95, sd = 1.55, n_obs = 20,
min_val = 1, max_val = 5, n_items = 3)
find_possible_distribution(sprite_parameters)
```
### Restrictions
Sometimes, you might know how often certain values should appear in the distribution. Such restrictions need to be passed to the `set_parameters()` function as a named list. They can either specify the exact number of occurrences (`restrictions_exact`) or the minimum number of occurrences (`restrictions_minimum`) of a specific value.
```{r}
sprite_parameters <- set_parameters(mean = 1.95, sd = 1.55, n_obs = 20,
min_val = 1, max_val = 5, n_items = 3,
restrictions_exact = list("3"=0, "3.67" = 2),
restrictions_minimum = list("1" = 1, "5" = 1))
find_possible_distribution(sprite_parameters)
```