[R] cut.POSIXt misconception/feature/bug?
Brian Diggs
diggsb at ohsu.edu
Thu Mar 11 22:15:29 CET 2010
On 3/11/2010 11:52 AM, Brian Diggs wrote:
> I've included a patch against cut.POSIXt.Rd with these proposed changes.
Apparently the patch didn't make it through, so I'm just pasting it below.
> --
> Brian Diggs, Ph.D.
> Senior Research Associate, Department of Surgery, Oregon Health & Science University
Index: cut.POSIXt.Rd
===================================================================
--- cut.POSIXt.Rd (revision 51247)
+++ cut.POSIXt.Rd (working copy)
@@ -20,8 +20,10 @@
\arguments{
\item{x}{an object inheriting from class \code{"POSIXt"} or
\code{"Date"}.}
\item{breaks}{
- a vector of cut points \emph{or} number giving the number of
- intervals which \code{x} is to be cut into \emph{or} an
+ either a \code{POSIXt} or \code{Date} vector of two or
+ more cut points \emph{or} a single number (greater than
+ or equal to 2) giving the number of intervals into which
+ \code{x} is to be cut \emph{or} an
interval specification, one of \code{"sec"}, \code{"min"},
\code{"hour"}, \code{"day"}, \code{"DSTday"}, \code{"week"},
\code{"month"}, \code{"quarter"} or \code{"year"}, optionally
@@ -42,7 +44,7 @@
}
\details{
Using both \code{right = TRUE} and \code{include.lowest = TRUE}
- will include both ends of the range of dates.
+ will include both ends of the range of \code{breaks}.
Using \code{breaks = "quarter"} will create intervals of 3 calendar
months, with the intervals beginning on January 1, April 1,
More information about the R-help
mailing list