EVOLUTION-MANAGER
Edit File: stat_summary.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><title>R: Summarise y values at unique/binned x</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <link rel="stylesheet" type="text/css" href="R.css" /> </head><body> <table width="100%" summary="page for stat_summary_bin {ggplot2}"><tr><td>stat_summary_bin {ggplot2}</td><td style="text-align: right;">R Documentation</td></tr></table> <h2>Summarise y values at unique/binned x</h2> <h3>Description</h3> <p><code>stat_summary()</code> operates on unique <code>x</code> or <code>y</code>; <code>stat_summary_bin()</code> operates on binned <code>x</code> or <code>y</code>. They are more flexible versions of <code><a href="geom_histogram.html">stat_bin()</a></code>: instead of just counting, they can compute any aggregate. </p> <h3>Usage</h3> <pre> stat_summary_bin( mapping = NULL, data = NULL, geom = "pointrange", position = "identity", ..., fun.data = NULL, fun = NULL, fun.max = NULL, fun.min = NULL, fun.args = list(), bins = 30, binwidth = NULL, breaks = NULL, na.rm = FALSE, orientation = NA, show.legend = NA, inherit.aes = TRUE, fun.y, fun.ymin, fun.ymax ) stat_summary( mapping = NULL, data = NULL, geom = "pointrange", position = "identity", ..., fun.data = NULL, fun = NULL, fun.max = NULL, fun.min = NULL, fun.args = list(), na.rm = FALSE, orientation = NA, show.legend = NA, inherit.aes = TRUE, fun.y, fun.ymin, fun.ymax ) </pre> <h3>Arguments</h3> <table summary="R argblock"> <tr valign="top"><td><code>mapping</code></td> <td> <p>Set of aesthetic mappings created by <code><a href="aes.html">aes()</a></code> or <code><a href="aes_.html">aes_()</a></code>. If specified and <code>inherit.aes = TRUE</code> (the default), it is combined with the default mapping at the top level of the plot. You must supply <code>mapping</code> if there is no plot mapping.</p> </td></tr> <tr valign="top"><td><code>data</code></td> <td> <p>The data to be displayed in this layer. There are three options: </p> <p>If <code>NULL</code>, the default, the data is inherited from the plot data as specified in the call to <code><a href="ggplot.html">ggplot()</a></code>. </p> <p>A <code>data.frame</code>, or other object, will override the plot data. All objects will be fortified to produce a data frame. See <code><a href="fortify.html">fortify()</a></code> for which variables will be created. </p> <p>A <code>function</code> will be called with a single argument, the plot data. The return value must be a <code>data.frame</code>, and will be used as the layer data. A <code>function</code> can be created from a <code>formula</code> (e.g. <code>~ head(.x, 10)</code>).</p> </td></tr> <tr valign="top"><td><code>geom</code></td> <td> <p>Use to override the default connection between <code>geom_histogram()</code>/<code>geom_freqpoly()</code> and <code>stat_bin()</code>.</p> </td></tr> <tr valign="top"><td><code>position</code></td> <td> <p>Position adjustment, either as a string, or the result of a call to a position adjustment function.</p> </td></tr> <tr valign="top"><td><code>...</code></td> <td> <p>Other arguments passed on to <code><a href="layer.html">layer()</a></code>. These are often aesthetics, used to set an aesthetic to a fixed value, like <code>colour = "red"</code> or <code>size = 3</code>. They may also be parameters to the paired geom/stat.</p> </td></tr> <tr valign="top"><td><code>fun.data</code></td> <td> <p>A function that is given the complete data and should return a data frame with variables <code>ymin</code>, <code>y</code>, and <code>ymax</code>.</p> </td></tr> <tr valign="top"><td><code>fun.min, fun, fun.max</code></td> <td> <p>Alternatively, supply three individual functions that are each passed a vector of values and should return a single number.</p> </td></tr> <tr valign="top"><td><code>fun.args</code></td> <td> <p>Optional additional arguments passed on to the functions.</p> </td></tr> <tr valign="top"><td><code>bins</code></td> <td> <p>Number of bins. Overridden by <code>binwidth</code>. Defaults to 30.</p> </td></tr> <tr valign="top"><td><code>binwidth</code></td> <td> <p>The width of the bins. Can be specified as a numeric value or as a function that calculates width from unscaled x. Here, "unscaled x" refers to the original x values in the data, before application of any scale transformation. When specifying a function along with a grouping structure, the function will be called once per group. The default is to use the number of bins in <code>bins</code>, covering the range of the data. You should always override this value, exploring multiple widths to find the best to illustrate the stories in your data. </p> <p>The bin width of a date variable is the number of days in each time; the bin width of a time variable is the number of seconds.</p> </td></tr> <tr valign="top"><td><code>breaks</code></td> <td> <p>Alternatively, you can supply a numeric vector giving the bin boundaries. Overrides <code>binwidth</code>, <code>bins</code>, <code>center</code>, and <code>boundary</code>.</p> </td></tr> <tr valign="top"><td><code>na.rm</code></td> <td> <p>If <code>FALSE</code>, the default, missing values are removed with a warning. If <code>TRUE</code>, missing values are silently removed.</p> </td></tr> <tr valign="top"><td><code>orientation</code></td> <td> <p>The orientation of the layer. The default (<code>NA</code>) automatically determines the orientation from the aesthetic mapping. In the rare event that this fails it can be given explicitly by setting <code>orientation</code> to either <code>"x"</code> or <code>"y"</code>. See the <em>Orientation</em> section for more detail.</p> </td></tr> <tr valign="top"><td><code>show.legend</code></td> <td> <p>logical. Should this layer be included in the legends? <code>NA</code>, the default, includes if any aesthetics are mapped. <code>FALSE</code> never includes, and <code>TRUE</code> always includes. It can also be a named logical vector to finely select the aesthetics to display.</p> </td></tr> <tr valign="top"><td><code>inherit.aes</code></td> <td> <p>If <code>FALSE</code>, overrides the default aesthetics, rather than combining with them. This is most useful for helper functions that define both data and aesthetics and shouldn't inherit behaviour from the default plot specification, e.g. <code><a href="borders.html">borders()</a></code>.</p> </td></tr> <tr valign="top"><td><code>fun.ymin, fun.y, fun.ymax</code></td> <td> <p>Deprecated, use the versions specified above instead.</p> </td></tr> </table> <h3>Orientation</h3> <p>This geom treats each axis differently and, thus, can thus have two orientations. Often the orientation is easy to deduce from a combination of the given mappings and the types of positional scales in use. Thus, ggplot2 will by default try to guess which orientation the layer should have. Under rare circumstances, the orientation is ambiguous and guessing may fail. In that case the orientation can be specified directly using the <code>orientation</code> parameter, which can be either <code>"x"</code> or <code>"y"</code>. The value gives the axis that the geom should run along, <code>"x"</code> being the default orientation you would expect for the geom. </p> <h3>Aesthetics</h3> <p><code>stat_summary()</code> understands the following aesthetics (required aesthetics are in bold): </p> <ul> <li> <p><strong><code>x</code></strong> </p> </li> <li> <p><strong><code>y</code></strong> </p> </li> <li> <p><code>group</code> </p> </li></ul> <p>Learn more about setting these aesthetics in <code>vignette("ggplot2-specs")</code>. </p> <h3>Summary functions</h3> <p>You can either supply summary functions individually (<code>fun</code>, <code>fun.max</code>, <code>fun.min</code>), or as a single function (<code>fun.data</code>): </p> <dl> <dt>fun.data</dt><dd><p>Complete summary function. Should take numeric vector as input and return data frame as output</p> </dd> <dt>fun.min</dt><dd><p>min summary function (should take numeric vector and return single number)</p> </dd> <dt>fun</dt><dd><p>main summary function (should take numeric vector and return single number)</p> </dd> <dt>fun.max</dt><dd><p>max summary function (should take numeric vector and return single number)</p> </dd> </dl> <p>A simple vector function is easiest to work with as you can return a single number, but is somewhat less flexible. If your summary function computes multiple values at once (e.g. min and max), use <code>fun.data</code>. </p> <p><code>fun.data</code> will recieve data as if it was oriented along the x-axis and should return a data.frame that corresponds to that orientation. The layer will take care of flipping the input and output if it is oriented along the y-axis. </p> <p>If no aggregation functions are supplied, will default to <code><a href="mean_se.html">mean_se()</a></code>. </p> <h3>See Also</h3> <p><code><a href="geom_linerange.html">geom_errorbar()</a></code>, <code><a href="geom_linerange.html">geom_pointrange()</a></code>, <code><a href="geom_linerange.html">geom_linerange()</a></code>, <code><a href="geom_linerange.html">geom_crossbar()</a></code> for geoms to display summarised data </p> <h3>Examples</h3> <pre> d <- ggplot(mtcars, aes(cyl, mpg)) + geom_point() d + stat_summary(fun.data = "mean_cl_boot", colour = "red", size = 2) # Orientation follows the discrete axis ggplot(mtcars, aes(mpg, cyl)) + geom_point() + stat_summary(fun.data = "mean_cl_boot", colour = "red", size = 2) # You can supply individual functions to summarise the value at # each x: d + stat_summary(fun = "median", colour = "red", size = 2, geom = "point") d + stat_summary(fun = "mean", colour = "red", size = 2, geom = "point") d + aes(colour = factor(vs)) + stat_summary(fun = mean, geom="line") d + stat_summary(fun = mean, fun.min = min, fun.max = max, colour = "red") d <- ggplot(diamonds, aes(cut)) d + geom_bar() d + stat_summary(aes(y = price), fun = "mean", geom = "bar") # Orientation of stat_summary_bin is ambiguous and must be specified directly ggplot(diamonds, aes(carat, price)) + stat_summary_bin(fun = "mean", geom = "bar", orientation = 'y') # Don't use ylim to zoom into a summary plot - this throws the # data away p <- ggplot(mtcars, aes(cyl, mpg)) + stat_summary(fun = "mean", geom = "point") p p + ylim(15, 30) # Instead use coord_cartesian p + coord_cartesian(ylim = c(15, 30)) # A set of useful summary functions is provided from the Hmisc package: stat_sum_df <- function(fun, geom="crossbar", ...) { stat_summary(fun.data = fun, colour = "red", geom = geom, width = 0.2, ...) } d <- ggplot(mtcars, aes(cyl, mpg)) + geom_point() # The crossbar geom needs grouping to be specified when used with # a continuous x axis. d + stat_sum_df("mean_cl_boot", mapping = aes(group = cyl)) d + stat_sum_df("mean_sdl", mapping = aes(group = cyl)) d + stat_sum_df("mean_sdl", fun.args = list(mult = 1), mapping = aes(group = cyl)) d + stat_sum_df("median_hilow", mapping = aes(group = cyl)) # An example with highly skewed distributions: if (require("ggplot2movies")) { set.seed(596) mov <- movies[sample(nrow(movies), 1000), ] m2 <- ggplot(mov, aes(x = factor(round(rating)), y = votes)) + geom_point() m2 <- m2 + stat_summary(fun.data = "mean_cl_boot", geom = "crossbar", colour = "red", width = 0.3) + xlab("rating") m2 # Notice how the overplotting skews off visual perception of the mean # supplementing the raw data with summary statistics is _very_ important # Next, we'll look at votes on a log scale. # Transforming the scale means the data are transformed # first, after which statistics are computed: m2 + scale_y_log10() # Transforming the coordinate system occurs after the # statistic has been computed. This means we're calculating the summary on the raw data # and stretching the geoms onto the log scale. Compare the widths of the # standard errors. m2 + coord_trans(y="log10") } </pre> <hr /><div style="text-align: center;">[Package <em>ggplot2</em> version 3.3.2 <a href="00Index.html">Index</a>]</div> </body></html>