The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.
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). Much of the code for is based on Nick Brown’s rSPRITE shiny app, 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.
rsprite2 can be installed from CRAN with:
install.packages("rsprite2")
Or you might want to install the development version from GitHub:
install.packages("remotes")
::install_github('LukasWallrich/rsprite2') remotes
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?
library(rsprite2)
<- set_parameters(mean = 2.2, sd = 1.3, n_obs = 20, min_val = 1, max_val = 5)
sprite_parameters 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.
<- set_parameters(mean = 2.20, m_prec = 2, sd = 1.32,
sprite_parameters 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()
find_possible_distributions(sprite_parameters, 10)
They can then be plotted to identify features that are shared across distributions.
<- find_possible_distributions(sprite_parameters, 10)
res plot_distributions(res)
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.
<- set_parameters(mean = 1.95, sd = 1.55, n_obs = 20,
sprite_parameters min_val = 1, max_val = 5, n_items = 3)
find_possible_distribution(sprite_parameters)
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.
<- set_parameters(mean = 1.95, sd = 1.55, n_obs = 20,
sprite_parameters 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)
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.