Description Usage Arguments Details Value Note Author(s) References See Also Examples

There are many summary statistics available in R; this function provides the ones most useful for scale construction and item analysis in classic psychometrics. Range is most useful for the first pass in a data set, to check for coding errors.

1 2 3 4 |

`x` |
A data frame or matrix |

`na.rm` |
The default is to delete missing data. na.rm=FALSE will delete the case. |

`interp` |
Should the median be standard or interpolated |

`skew` |
Should the skew and kurtosis be calculated? |

`ranges` |
Should the range be calculated? |

`trim` |
trim=.1 – trim means by dropping the top and bottom trim fraction |

`type` |
Which estimate of skew and kurtosis should be used? (See details.) |

`check` |
Should we check for non-numeric variables? Slower but helpful. |

`fast` |
if TRUE, will do n, means, sds, min, max, ranges for an improvement in speed. If NULL, will switch to fast mode for large (ncol * nrow > 10^7) problems, otherwise defaults to fast = FALSE |

`quant` |
if not NULL, will find the specified quantiles (e.g. quant=c(.25,.75) will find the 25th and 75th percentiles) |

`IQR` |
If TRUE, show the interquartile range |

`omit` |
Do not convert non-numerical variables to numeric, omit them instead |

`head` |
show the first 1:head cases for each variable in describeData |

`tail` |
Show the last nobs-tail cases for each variable in describeData |

In basic data analysis it is vital to get basic descriptive statistics.
Procedures such as `summary`

and hmisc::describe do so. The describe function in the `psych`

package is meant to produce the most frequently requested stats in psychometric and psychology studies, and to produce them in an easy to read data.frame. The results from describe can be used in graphics functions (e.g., `error.crosses`

).

The range statistics (min, max, range) are most useful for data checking to detect coding errors, and should be found in early analyses of the data.

Although describe will work on data frames as well as matrices, it is important to realize that for data frames, descriptive statistics will be reported only for those variables where this makes sense (i.e., not for alphanumeric data).

If the check option is TRUE, variables that are categorical or logical are converted to numeric and then described. These variables are marked with an * in the row name. This is somewhat slower. Note that in the case of categories or factors, the numerical ordering is not necessarily the one expected. For instance, if education is coded "high school", "some college" , "finished college", then the default coding will lead to these as values of 2, 3, 1. Thus, statistics for those variables marked with * should be interpreted cautiously (if at all).

In a typical study, one might read the data in from the clipboard (`read.clipboard`

), show the splom plot of the correlations (`pairs.panels`

), and then describe the data.

na.rm=FALSE is equivalent to describe(na.omit(x))

When finding the skew and the kurtosis, there are three different options available. These match the choices available in skewness and kurtosis found in the e1071 package (see Joanes and Gill (1998) for the advantages of each one).

If we define *m_r = [sum(X- mx)^r]/n* then

Type 1 finds skewness and kurtosis by *g_1 = m_3/(m_2)^{3/2} * and *g_2 = m_4/(m_2)^2 -3*.

Type 2 is *G1 = g1 * √{n *(n-1)}/(n-2)* and *G2 = (n-1)*[(n+1)g2 +6]/((n-2)(n-3))*.

Type 3 is *b1 = [(n-1)/n]^{3/2} m_3/m_2^{3/2}* and *b2 = [(n-1)/n]^{3/2} m_4/m_2^2)*.

The additional helper function `describeData`

just scans the data array and reports on whether the data are all numerical, logical/factorial, or categorical. This is a useful check to run if trying to get descriptive statistics on very large data sets where to improve the speed, the check option is FALSE.

An even faster overview of the data is `describeFast`

which reports the number of total cases, number of complete cases, number of numeric variables and the number which are factors.

The fast=TRUE option will lead to a speed up of about 50% for larger problems by not finding all of the statistics (see NOTE)

To describe the data for different groups, see `describeBy`

.

A data.frame of the relevant statistics:

item name

item number

number of valid cases

mean

standard deviation

trimmed mean (with trim defaulting to .1)

median (standard or interpolated

mad: median absolute deviation (from the median).

minimum

maximum

skew

kurtosis

standard error

For very large data sets that are data.frames, `describe`

can be rather slow. Converting the data to a matrix first is recommended. However, if the data are of different types, (factors or logical), this is not possible. If the data set includes columns of character data, it is also not possible. Thus, a quick pass with `describeData`

is recommended. Even faster is a quick pass with `describeFast`

which just counts number of observations per variable and reports the type of data (numerical, factor, logical).

For the greatest speed, at the cost of losing information, do not ask for ranges or for skew and turn off check. This is done automatically if the fast option is TRUE or for large data sets.

Note that by default, fast=NULL. But if the number of cases x number of variables exceeds (ncol * nrow > 10^7), fast will be set to TRUE. This will provide just n, mean, sd, min, max, range, and standard errors. To get all of the statistics (but at a cost of greater time) set fast=FALSE.

The problem seems to be a memory limitation in that the time taken is an accelerating function of nvars * nobs. Thus, for a largish problem (72,000 cases with 1680 variables) which might take 330 seconds, doing it as two sets of 840 variable cuts the time down to 80 seconds.

The object returned is a data frame with the normal precision of R. However, to control the number of digits displayed, you can set digits in a print command, rather than losing precision at the descriptive stats level. See the last two examples. One just sets the number of digits, one gives uses signif to make 'prettier' output where all numbers are displayed to the same number of digits.

The MAD (median absolute deviation from the median) is calculated using the mad function from the stats package in Core-R. Note that by default, the MAD is adjusted by a scaling factor (1.4826) that will give the expectation of the MAD to be the same as the standard deviation for normal data.

An interesting problem with describe is that a function with the same name is in the Hmisc package. HMisc is loaded by qqgraph which in turn is loaded by SemPlot. So even if not directly loading HMisc, if you load SemPlot after loading psych, describe will not work, but the reverse order for loading should work.

https://personality-project.org/revelle.html

Maintainer: William Revelle [email protected]

Joanes, D.N. and Gill, C.A (1998). Comparing measures of sample skewness and kurtosis. The Statistician, 47, 183-189.

`describeBy`

, `skew`

, `kurtosi`

`interp.median`

, `read.clipboard`

. Then, for graphic output, see `error.crosses`

, `pairs.panels`

, `error.bars`

, `error.bars.by`

and `densityBy`

, or `violinBy`

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 | ```
data(sat.act)
describe(sat.act)
describe(sat.act,skew=FALSE)
describe(sat.act,IQR=TRUE) #show the interquartile Range
describe(sat.act,quant=c(.1,.25,.5,.75,.90) ) #find the 10th, 25th, 50th,
#75th and 90th percentiles
describeData(sat.act) #the fast version just gives counts and head and tail
print(describeFast(sat.act),short=FALSE) #even faster is just counts (just less information)
#now show how to adjust the displayed number of digits
des <- describe(sat.act) #find the descriptive statistics. Keep the original accuracy
des #show the normal output, which is rounded to 2 decimals
print(des,digits=3) #show the output, but round to 3 (trailing) digits
print(des, signif=3) #round all numbers to the 3 significant digits
``` |

psych documentation built on May 7, 2018, 1:04 a.m.

Embedding an R snippet on your website

Add the following code to your website.

For more information on customizing the embed code, read Embedding Snippets.