Rev 15458 | Blame | Compare with Previous | Last modification | View Log | Download | RSS feed
\name{cut.POSIXt}\alias{cut.POSIXt}\title{Convert a Date-Time Object to a Factor}\description{Method for \code{\link{cut}} applied to date-time objects.}\usage{\method{cut}{POSIXt}(x, breaks, labels=NULL, start.on.monday=TRUE, \dots)}\arguments{\item{x}{an object inheriting from class \code{"POSIXt"}.}\item{breaks}{a vector of cut points \emph{or} number giving the number ofintervals which \code{x} is to be cut into \emph{or} aninterval specification, one of \code{"secs"}, \code{"mins"},\code{"hours"}, \code{"days"}, \code{"weeks"}, \code{"months"}or \code{"years"}.}\item{labels}{labels for the levels of the resulting category. By default,labels are constructed using \code{"(a,b]"} interval notation. If\code{labels = FALSE}, simple integer codes are returned insteadof a factor.}\item{start.on.monday}{logical. If \code{breaks = "weeks"}, should theweek start on Mondays or Sundays?}\item{\dots}{arguments to be passed to or from other methods.}}\value{A factor is returned, unless \code{labels = FALSE} which returnsthe integer level codes.}\seealso{\code{\link{seq.POSIXt}}, \code{\link{cut}}}\examples{## random dates in a 10-week periodcut(ISOdate(2001, 1, 1) + 70*86400*runif(100), "weeks")}\keyword{manip}\keyword{chron}