similar to: pretty.Date(): new "halfmonth" time step

Hi all. pretty() is now generic in R-2.12 and there are new methods for Date and POSIXt classes. These methods could potentially be used inside axis.Date and axis.POSIXt (and Axis methods), although that has not been decided yet. The main advantage of the new method is that it is flexible, in the sense that users can specify the desired number of ticks on an axis. (e.g. one could easily draw,

Hi R-devel. I've noticed a couple of quirks in the current time/date axis functions (axis.Date, axis.POSIXct, and the equivalents in lattice). Looking at the code, it seems like a fairly ad-hoc approach, often using pretty() on components of the time. This is not always ideal - for example a one-hour interval gets cut into 10-minute chunks rather than the more natural 15-minute chunks (since

I HAVE BEEN ASKED TO BE REMOVED FROM THIS LIST OVER 20 TIMES, PLEASE CAN I BE REMOVED!!!!!!!!!!!!! --- On Thu, 3/12/09, Peng Cai <pengcaimaillist@gmail.com> wrote: From: Peng Cai <pengcaimaillist@gmail.com> Subject: Re: [R] Help: barchart() {Lattice} To: "Felix Andrews" <felix@nfrac.org> Cc: r-help@r-project.org Received: Thursday, 3 December, 2009, 10:17 AM Got it

x <- seq(as.POSIXct("2000-01-01"), by = "days", length = 20) cut(x, breaks = 3) # Error in `levels<-.factor`(`*tmp*`, value = character(0)) : # number of levels differs cut(as.Date(x), breaks = 3) # Error in `levels<-.factor`(`*tmp*`, value = character(0)) : # number of levels differs Index: base/R/datetime.R

Hi, Just wondering whether anyone had thought about moving the R sources to a "distributed" version control system such as Bazaar, Git or Mercurial. These new generation systems make it easier to work on feature branches, allow working offline, are very fast, etc. Some projects that have moved to Git are Linux Kernel Perl Ruby on Rails ... http://en.wikipedia.org/wiki/Git_(software)

Hi, I am getting unexpected behaviour from aggregate.ts(). The 'ndeltat' argument is effectively being reduced by 1 in some cases, even when it is an integer, with the result that the blocks to be aggregated are not of the expected size, and also that the end() of the aggregated series is much later than the end() of the original series. rawts <- ts(rep(1:10, each = 5), start = 1) ##

Package plotAndPlayGTK provides a graphical user interface for R plots. Wrap it around your plot commands, like playwith(plot(mydata)). A window pops up with a Cairo plot device and a toolbar with buttons to interact with the plot. The default buttons allow you to add persistent labels to data points, zoom in and out and around, save the plot to a file, and so on. Furthermore, you can edit the

Package plotAndPlayGTK provides a graphical user interface for R plots. Wrap it around your plot commands, like playwith(plot(mydata)). A window pops up with a Cairo plot device and a toolbar with buttons to interact with the plot. The default buttons allow you to add persistent labels to data points, zoom in and out and around, save the plot to a file, and so on. Furthermore, you can edit the

list(...), I would like to zoom in to the leaves of large trees in a dendrogram plot. The playwith package allows zooming by passing xlim and ylim arguments to the plot call (Hmisc does this too I think). But currently stats:::plot.dendrogram does not accept xlim or ylim. So I would like to enable that. In place of the existing code chunk: xlim <- c(x1 - 1/2, x2 + 1/2) ylim <- c(0,

list(...) I can not get at the grid viewports in a ggplot2 plot. I know there is supposed to be a viewport called "panel_1_1" but downViewport() can't find it. Has the viewport been popped? I had a quick look at the functions involved (eg ggplot_plot) but there is no obvious problem there. > library(ggplot2) > qplot(1:10, 1:10) > current.viewport() viewport[ROOT] >

Great stuff, thanks. I'm copying this solution to R-help for reference. On 6/24/07, deepayan.sarkar at gmail.com <deepayan.sarkar at gmail.com> wrote: > On 6/23/07, Felix Andrews <felix at nfrac.org> wrote: > > Hi Deepayan, > > > > I have a Lattice question: is there any way to plot just one > > (specified) page of a multi-page display? > > Not in

Times from seq.POSIXt come out wrong in AEST timezone around Feb 29 every leap year before 1970 (on Windows XP). According to help(DateTimeClasses), this is handled by "our own C code". > x <- as.POSIXct("1968-02-27") # tz="AEST" > x.gmt <- as.POSIXct("1968-02-27", tz="GMT") > data.frame( GMT=seq(x.gmt, by="day",

playwith package version 0.8-55 is now on CRAN. It provides a GTK+ interface for interacting with R plots. Screenshots of some examples are online at: http://code.google.com/p/playwith/wiki/Screenshots Changes in Version 0.8-55 o argument `parameters`: automatically constructs widgets to control parameter values appearing in the call. o default action when dragging on the plot is zoom.

playwith package version 0.8-55 is now on CRAN. It provides a GTK+ interface for interacting with R plots. Screenshots of some examples are online at: http://code.google.com/p/playwith/wiki/Screenshots Changes in Version 0.8-55 o argument `parameters`: automatically constructs widgets to control parameter values appearing in the call. o default action when dragging on the plot is zoom.

Hi R-devel I use the packages RGtk2 and cairoDevice. The cairoDevice package has a few stand-alone functions, plus "asCairoDevice" which depends on RGtk2 and calls require(RGtk2). So cairoDevice lists RGtk2 under "Suggests" in the DESCRIPTION file. It can not Import RGtk2 because that would force all users to install RGtk2. The upshot of this is, if you *import* the RGtk2

list(...), I am working with environmental time series (eg rainfall, stream flow) that have attached quality codes for each data point. The quality codes have just a few factor levels, like "good", "suspect", "poor", "imputed". I use the quality codes in plots and summaries. They are carried through when a time series is aggregated to a longer time-step,

I am still experiencing problems with seq.POSIXt() missing off the last day of the series: > seq(as.POSIXct("2004-03-25"),as.POSIXct("2004-03-31"),by="DSTdays") [1] "2004-03-25 GMT Standard Time" "2004-03-26 GMT Standard Time" "2004-03-27 GMT Standard Time" [4] "2004-03-28 GMT Standard Time" "2004-03-29 GMT Daylight

Dr Murrell and others, It seems grid.ls() fails after any use of grid.remove(). It gives an infinite recursion error even in the simplest cases, and no matter what arguments are passed to grid.ls. > library(grid) > grid.newpage() > grid.lines(name="foo") > grid.ls() foo > grid.remove("foo") > grid.ls() Error: evaluation nested too deeply: infinite recursion

A question about vectorized operations (avoiding loops, for speed)... I need to run a simple recursive (autoregressive) filter with a time-varying coefficient. It is just a one-step recursive filter, so it would be an exponential decay if the filter was constant. I just want to do this, where 'x' is the data and 'w' is the weight to apply to the previous time step: x <- c(1,

Dear useRs, I am trying to model a time series with a transfer function. I think it can be put into the ARMA framework, and estimated with the 'arima' function (and others have made similar comments on this list). I have tried to do that, but the results have so far been disappointing. Maybe I am trying to make 'arima' do something it can't... The data are time series of