similar to: patch proposal for plot.ts

Displaying 20 results from an estimated 3000 matches similar to: "patch proposal for plot.ts"

2006 Nov 23
1
dumping/loading objects with 'tsp' attribute
Dear all, I'm indirectly faced with the fact that setting the 'tsp' attribute of an object modifies its class definition: > class( structure(1:2, tsp=c(1,2,1), class=c("myts","ts")) ) [1] "ts" "myts" In general, this is of really little (ok, I admit: totally no) interest for me because 'myts' class is added just after assigning the
2011 Nov 02
1
kernapply.ts
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
2005 Jun 03
1
ts.intersect a multivariate and univariate ts
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
2005 Sep 21
3
ts.intersect bug?
This code gives an error: a <- ts(1:10, start=0, freq=10) b <- ts(1:10, start=1, freq=10) ts.intersect(a,b) This one works normally (and correctly): a <- ts(1:10, start=0) b <- ts(1:10, start=1) ts.intersect(a,b) Antonio, Fabio Di Narzo. P.S. How to switch off italian error messages to post on r-help? > version _ platform i386-pc-mingw32 arch i386 os
2010 Jul 03
2
Change the frequency of a ts?
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")
2005 Jan 31
2
changing the time base in a ts
I'm probably apporaching this all wrong to start but.... Suppose I have a monthly time series and I want to compute the mean of months 6,7, and 8. I want to plot the original time series and the seasonal time series, one above the other. When I do that as below the time series don't line up for reasons that are obvious. How can I change the base of the seasonal time series so I can make
1999 Jul 27
3
Preliminary version of ts package
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
2017 Sep 02
1
Precision error in time index of ts objects
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
2006 May 05
0
plot.ts bad default labelling and lag.plot incomplete doc
Hi all. I've found that also in R-2.3.0 there is the bad labelling previously found in R-2.2.1. x <- ts(1:3) plot(lag(x,1),x) #labels 1 and 3 are superposed on the first point. plot(lag(x,1),x, xy.labels=as.character (1:2)) #this is ok xy <- ts.intersect(lag(x,1),x) plot(xy[,1],xy[,2]) #this also is ok The same problem is shown by lag.plot, which in turn calls plot.ts. Also note that
2013 Oct 23
2
Multivariate time series in R 3 vs R 2
Hello! Recently I got report that my package mar1s doesn't pass checks any more on R 3.0.2. I started to investigate and found the following difference in multivariate time series handling in R 3.0.2 compared to R 2 (I've checked on 2.14.0). Suppose I wish to calculate seasonal component for time series. In case of multivariate time series, I wish to process each column independently.
2009 Jun 14
1
time function behavior for ts class objects
Hi all- I am trying to use the time function for ts class objects and do not understand the return value. I want to use it to set up a time trend in arima fits. It does not seem to return a correct linear sequence that matches the underlying time series. I am running: R version 2.8.1 (2008-12-22). For example: R> ## create a time series R> x <- rnorm(24) R> (xts <-
2017 Sep 01
0
Precision error in time index of ts objects
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
2017 Sep 01
2
Precision error in time index of ts objects
I have a time series x, and two other series obtained from it: x <- structure(2017, .Tsp = c(2017.41666666667, 2017.41666666667, 12), class = "ts") y <- floor(x) z <- x-y I would expect the three series to have exactly the same index. However I get the following > time(x)-time(y) Jun 2017 0 as expected, but > time(x)-time(z) integer(0) Warning message: In
2000 Aug 21
2
diff.default / diff.ts in wrong package bug (PR#640)
{all recent versions of R} Problem / design bug : diff.default() doesn't deal with "ts" objects properly, diff.ts() does, but that is only available from package "ts" where as the constructor function ts() is in base. It's not sufficient to just move diff.ts() to package base, since it relies itself on lag & lag.default which are also only in package ts.
1999 Jul 15
1
[R] R: ts - objects (PR#228)
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: >
2009 Nov 20
2
How to setup the tsp attribute of a dataset
Hello, I am wondering how I should set up the tsp attribute (available through attr(x, "tsp")) of a dataset x? Let's assume that x has 100 points, and I want to set the frequency to 4. I tried: > attr(x,"tsp")<-c(1,100,4) Error in attr(x, "tsp") <- c(1, 100, 4) : invalid time series parameters specified Is there any other way to set the frequency of
2011 Aug 19
3
ATSP to TSP reformulation
Greetings, I am having trouble getting the function reformulate_ATSP_as_TSP to work for me. I have provided a simple example of some of the code I've been using. In particular, I'm not sure why I'm getting the error "Error in dimnames(tsp) <- list(lab, lab) : length of 'dimnames' [1] not equal to array extent" since I created the object ATSP with a valid
1998 Sep 28
1
"tsp<-"
If value is NULL I think tsp assignment should not return a class ts object. Below is a fixed version. Paul Gilbert ____ "tsp<-" <-function(x, value) {if (is.null(value)) {attr(x, "tsp") <- value if(inherits(x,"ts")) class(x) <- NULL return(x) } attr(x, "tsp") <- value class(x) <- "ts" x }
2006 Mar 24
3
bug in plot.acf (PR#8705)
(Moved from r-devel to r-bugs) On 3/24/2006 5:03 AM, Antonio, Fabio Di Narzo wrote: > Hi all. > There's a bug in plot.acf, when plotting acf for multivariate time series. > Here a reproducible example: > > X <- rnorm(1000) > Y <- -X + rnorm(1000, sd=0.6) > Z <- cbind(X,Y) > > In > acf(Z) > cross-correlation plot y-axis is limited to 0-1. But: >
2017 Sep 01
2
Precision error in time index of ts objects
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