similar to: start.ts, end.ts (PR#513)

This message is in MIME format --_=XFMail.1.3.p0.Linux:990702182137:16900=_ Content-Type: text/plain; charset=us-ascii There was some discussion a while back on R-devel between Ross Ihaka, Paul Gilbert and myself about row subsetting in time series. I think the consensus was that "[.ts" should not try to coerce its result back to a time series object (which is underlying the problem

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) ##

There is now a preliminary version of a time series package in the R-devel snapshots, and we would welcome feedback on it. It is based in part on the packages bats (Martyn Plummer) and tseries (Adrian Trapletti) and in part on code I had or have written. (Thanks for the contributions, Martyn and Adrian!) Some of the existing ts code has been changed, for example to plot multiple time series, so

I'm having some problems with aggregate.ts, e.g. R> x <- ts(1:20) R> frequency(x) [1] 1 R> aggregate(x, nfreq=1/3) Error in aggregate.ts(x, nfreq = 1/3) : cannot change frequency from 1 to 0.333333333333333 In fact aggregate.ts only accepts a new frequency that is a negative power of two in this example. The problem with the current test for compatible frequencies if

>>>>> On Fri, 02 Jul 1999, Adrian Trapletti <Adrian.Trapletti@wu-wien.ac.at> said: Adrian> There seems to be a problem with plot.ts (R Version 0.64.2) > x<-cbind(1:10,2:11) > x<-as.ts(x) > plot(x) Adrian> Error: subscript (20) out of bounds, should be at most 10 This is definitely a bug --> CC: R-bugs ALL NOTE : This is *not* new

Thanks for the very detailed explanation. I did not create the series using structure(), that was the result of dump() on an intermediate object created within tsdisagg::ta(), which is where I found the error in the first place. ta() indeed manipulates .Tsp directly, rather than using ts. I guess this is a bug in tsdisagg then. Thanks! -- Andrea Altomani On Sat, Sep 2, 2017 at 12:31 AM

On Fri, 1 Sep 2017, Andrea Altomani wrote: > I should have formulated my question in a more specific way. > > 1. I suspect this is a floating point precision issue. I am not very > knowledgeable about R internals, can someone else confirm it? Yes. If you represent a series with increment 1/12 it depends on how you do it. As a simple example consider the following two descriptions

I have done a re-working of the time series code in base R and library ts that will appear in Friday's snapshot. I am sure at least one person will be dissatisfied, but I am convinced there are fewer errors than there were before (I found more than 20, as well as several documented features that did not exist.) The principles in the code are: tsp attributes can only go on vectors of length

This message is in MIME format --_=XFMail.1.1.p0.Linux:970825095458:252=_ Content-Type: text/plain; charset=us-ascii Here is a patch which fixes some problems with time series functions. Some examples of what goes wrong... > x <- ts(rnorm(100),start=1,deltat=2) > start(x) Error in ts[1] : object is not subsettable > end(x) Error in ts[2] : object is not subsettable > y <-

I've stumbled across an issue with aggregate.ts that either is due to a misuse of %/% or something deeper relating to numerical precision on Windows. The test code is x <- rep(6:10, 1:5) as.vector(aggregate(as.ts(x), FUN = mean, ndeltat = 5)) On Linux and Mac I get the correct answer > x <- rep(6:10, 1:5) > as.vector(aggregate(as.ts(x), FUN = mean, ndeltat = 5) [1] 7.2 8.8

I have a time series vector (not necessarily ts class) that has NAs in it. How can I omit the NAs when using aggregate.ts() to compute a function on each window? If there is at least one non-NA value in each window, I'd like to proceed with evaluating the function; otherwise, I would like NA returned. I'm not wedded to aggregate.ts and don't need ts class if there is another fast,

The following seems confused (0.65 snapshot) > x <- ts(1:20) > window(x, 1, 1) Time Series: Start = c(1, 1) End = c(1, 1) Frequency = 1 [1] 1 Warning message: Not returning a time series object in: [.ts(x, i) (it of class ts, as the print method shows). Under 0.64.2 it is even more confusing: > x <- ts(1:20) > window(x, 1, 1) Warning: Not returning a time series object

aggregate.ts does not behave in the same way as the equivalent method aggregate.rts in S-PLUS. In particular it - changes the start of the time series - tends to have a length which is 1 shorter For example: R> x <- ts(1:10) R> aggregate(x, nfreq=0.5, FUN=min) Time Series: Start = 2 End = 8 Frequency = 0.5 [1] 2 4 6 8 S> x <- rts(1:10) S> aggregate(x, nf=0.5, fun = min) [1]

Marcus Eger <marcus.eger@physik.uni-marburg.de> writes: > > time(sqrt(arrts)) > Time Series: > Start = c(1, 1) > End = c(5, 1) > Frequency = 1 > [1] 1 2 3 4 5 Looks like a bug... > ---------------------------------------------------------------------------- > 2. (At least) boolean indexing with matrices does not seem to work > properly: >

I have a suggestion for kernapply for ts objects. When we choose the option circular=F, the returned series don't have the correct dates. The removed dates are all at the beginning instead of half at the beginning and half at the end. It is particularly useful when we need to smooth the series (or remove a trend using a filter) before estimating a model (like in macroeconomics) or simply

This seems like a FAQ, but I can't figure it out. I have a mv ts object: R > tsp(pg) [1] 1982 2003 1 R > dim(pg) [1] 22 12 and a univariate ts: R > tsp(rw) [1] 1690 1996 1 Yet, when I try to intersect them: R > tsp(ts.intersect(rw, pg)) [1] 1982 2176 1 the process goes awry. How to I get rw and pg to be one ts that runs from 1982 to 1996 and has 13 univariate time

I'm trying to convert a column of a table into a ts object. The data is monthly, so I want the ts frequency to be 12. I did this ... > filings.ts = as.ts(Filings.100K, frequency=12) > filings.ts Time Series: Start = 1 End = 311 Frequency = 1 [1] 246.9336 305.6789 ... ... > tsp(filings.ts) [1] 1 311 1 > tsp(filings.ts) <- c(1,311,12) Error in attr(x, "tsp")

I posted the question below about a month ago but received no response. I still have not been able to figure out what is happening. I also noticed another oddity. When the data part of the object is a multivariate time series, it doesn't show up in the structure, but it can be treated as a multivariate time series. Is this a bug in str? > setClass("tsExtended", representation =

I should have formulated my question in a more specific way. 1. I suspect this is a floating point precision issue. I am not very knowledgeable about R internals, can someone else confirm it? 2. Should this be considered a bug or not, because it is "just a precision issue"? Should I report it? 3. How can it happen? From a quick review of ts.R, it looks like the values of the time

Hi all. Currently, if you try: > lag.plot(1:10) you get superposed labels '1' and '10'. Things go worse in more extreme cases: x <- ts(1:10) x1 <- lag(x, 4) plot(x1, x) This is due to a mistake in plot.ts. My suggestion is the following really minimal patch to plot.ts: @@ -530,7 +530,7 @@ plot.ts <- text(xy, labels =