similar to: R-alpha: ts problems

Displaying 20 results from an estimated 3000 matches similar to: "R-alpha: ts problems"

1999 Jul 02
0
Bug in "[.ts" for multivariate ts {Problem with plot.ts, "[" (PR#217)
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
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 02
1
Bug in "[.ts" for multivariate ts {Problem with plot.ts, "["} (PR#216)
>>>>> 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
2000 Aug 24
1
Method dispatch fails for autoloaded methods (PR#642)
(As mentioned before, on R-devel) This code snippet shows what the Subject above says : > autoload("diff.ts", file="ts") > diff(ts(1:10,freq=2)) Error in tsp<-(*tmp*, value = c(xtsp[1] + lag * differences * xtsp[3], : invalid time series parameters specified > traceback() [1] "tsp<-(*tmp*, value = c(xtsp[1] + lag * differences * xtsp[3], " [2]
2002 Apr 03
1
predict.Arima fails when x is not a time-series
I'm playing with predict.Arima in the 3/19/02 development snapshot of R-devel. The following produces an error message because x is not of class "ts": R> x <- rnorm(20) R> obj <- arima(x, c(2,0,0)) R> predict(obj) Error in round(x, digits) : Non-numeric argument to mathematical function Granted the documentation for arima says x should be a time-series, but
2009 Feb 17
0
What's the predict procedure of ARIMA in R?
Hello,guys: Recently, I am working on a seasonal ARIMA model. And I met some problem in the forecasting. Now I just want to know that How does R perform the predict procedure(the predict formula, the initial setting of errors,etc.)? I run the following commands and get the original code of the "predict" command, but I can't read it. Can anybody explain it to me? Thanks! saji from
2013 Mar 22
0
predict.Arima error "'xreg' and 'newxreg' have different numbers of columns"
Hello all, I use arima to fit the model with fit <- arima(y, order = c(1,0,1), xreg = list.indep, include.mean = TRUE) and would like to use predict() to forecast: chn.forecast <- rep(0,times=num.record) chn.forecast[1] <- y[1] for (j in 2:num.record){ indep <- c(aa=chn.forecast[j-1], list.indep[j,2:num.indep]) # this is the newxreg in the
2009 Mar 06
0
modifying a built in function from the stats package (fixing arima) (CONCLUSIONS)
Thanks a lot to everybody that helped me out with this. Conclusions: (1) In order to edit arima in R: >fix(arima) or alternatively: >arima<-edit(arima) (2) This is not contained in the "Introduction to R" manual. (3) A "productive" fix of arima is attached (arma coefficients printed out and error catched so that it doesn't halt parent loops to search for
1997 Nov 28
3
R-alpha: Problems with dimnames and names
This message is in MIME format --_=XFMail.1.1.p0.Linux:971128122615:3052=_ Content-Type: text/plain; charset=us-ascii I have rounded up three buglets in R-0.50-a4. Two of them I can fix and a patch is supplied below. I hope this is useful for the current source (if these haven't been fixed already :) 1) cov cov() fails when it's argument is a matrix with one column and with column names
2010 Mar 31
1
predict.Arima: warnings from xreg magic
When I run predict.Arima in my code, I get warnings like: Warning message: In cbind(intercept = rep(1, n), xreg) : number of rows of result is not a multiple of vector length (arg 1) I think this is because I'm not running predict.Arima in the same environment that I did the fit, so the data object used in the fit is no longer present. Looking at the predict.Arima source,
1999 Apr 13
1
make check (PR#165)
This message is in MIME format --_=XFMail.1.3.p0.Linux:990413120342:8241=_ Content-Type: text/plain; charset=us-ascii R 0.64.0 on RedHat Linux 5.1 I decided to add a "make check" command in the R RPM spec file to ensure that R works properly before packaging it up. I found (by sabotaging one of the *.Rout.save files) that errors found by "make check" are ignored and do not
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
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")
2009 Jan 22
0
Confused about behavior of an S4 object containing a ts object
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 =
2002 Sep 03
1
t(xmat)
Hi, I have a matrix and time series "xmat". I have no problem executing any matrix functions except t(xmat) which gives the following error message. My question if "xmat" is a matrix why I can not execute this matrix function?? converting the time series and matrix into a data frame solves the problem >dim(xmat) [1] 98 7 > t(xmat) Error in "tsp<-"(*tmp*,
1999 Apr 22
1
mvfft (PR#176)
This message is in MIME format --_=XFMail.1.3.p0.Linux:990422185944:4782=_ Content-Type: text/plain; charset=us-ascii R-0.64.0 on RedHat Linux 5.1 Some problems with multivariate fast fourier transform. I have attached the dump of a 30 x 3 matrix that seems to reliably reproduce these problems 1) mvfft doesn't like vectors. It complains about not having enough memory: R>
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
2007 Nov 24
1
patch proposal for plot.ts
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 =
1999 Aug 12
1
ts in R (again)
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