Displaying 20 results from an estimated 400 matches similar to: "help(arima) return value typo?"
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
2005 Apr 19
2
building recommended packages on Windows
Hi,
I am building 2.1.0 (re-release version, if that matters) on a Windows XP
machine. Following the instructions 3.1 "Building from source" in
R-admin.html, I managed to get up to 3.1.6. But when I try to build the
recommended packages, I get
C:\hiro\codes\proj\R-2.1.0\src\gnuwin32>make recommended
--- Unpacking recommended packages
---- VR
make[1]: *** No rule to make target
2004 Jul 16
3
rd2dvi bug on windoze?
hi,
can anyone confirm the following problem? when i do
dos> rcmd rd2dvi --pdf my-package-name
i get
dos> Can't open perl script "c:\PROGRA~1\r\rw1091/bin/rd2dvi": No such file or directory
might the problem be in (double back slashes rather than forward slashes)
R-1.9.1\src\gnuwin32\front-ends\rcmdfn.c(251): strcat(cmd, RHome); strcat(cmd, "/bin/Rd2dvi.sh");
2004 Aug 17
1
suggestion for ARMAacf()
hi,
in 1.9.1, the return value from ARMAacf(pacf=TRUE) is not named by lags,
contrary to ?ARMAacf. the simple fix is to move names(Acf) <-
down after if(pacf), with an appropriate starting lag as pacf=TRUE appears
to start at lag 1 (whereas pacf=FALSE starts at lag 0).
for consistency, one could argue to append 1 for lag 0 for pacf=TRUE
(or start pacf=F at lag 1). however, given the
2008 Jun 12
2
arima() bug
I guess this is more r-devel than r-help.
Note, I am just the messenger - I have no idea what the user is trying to model here.
arima() crashes R (segfault) with Linux R-2.7.0, Solaris R-2.6.0:
*** caught segfault ***
address 42400000, cause 'memory not mapped'
Traceback:
1: .Call(R_getQ0, phi, theta)
2: makeARIMA(trarma[[1]], trarma[[2]], Delta, kappa)
3: arima(x, c(1, 0, 1), c(1,
2004 Oct 15
1
se.fit from predict.lm
hi,
i noticed that se.fit from predict.lm is the same whether interval="conf"
or interval="pred". it is not clear to me from ?predict.lm whether this is
intended or not. i suggest that se.fit should match the type of interval
requested, if interval is specified. suggested change in lm.R line 700
if(se.fit || interval != "none") se <- sqrt(ip)
to
if(se.fit
2009 Mar 26
1
arima, xreg, and the armax model
Hello all,
I''m having fun again with the arima function. This time I read in:
http://www.stat.pitt.edu/stoffer/tsa2/R_time_series_quick_fix.htm
<<It has recently been suggested (by a reliable source) that using xreg in
arima() does NOT fit an ARMAX model [insert slap head icon here]. This will
be investigated as soon as time permits.>>
(by R.H. Shumway & D.S. Stoffer)
2013 Sep 09
1
Fitting Arima Models and Forecasting Using Daily Historical Data
Hello everyone,
I was trying to fit an arima model to a daily historical data, but, for
some reason, havent been able to.
I basically have 212 observations (from 12/1/2012 to 06/30/2013) containing
the number of transits for a particular vessel.
The following messages are produced by R:
dailytrans.fit<-arima(dailytrans$transits, order=c(0,1,2),
seasonal=list(order=c(0,1,2), period=365),
2009 Nov 01
1
problems whit seasonal ARIMA
Hello,
I have daily wind speed data and need to fit seasonal ARIMA model, problem
is that my period is 365. But when I use arima(...) function, with period
365, I?m getting error message: ?Error in makeARIMA(trarma[[1]],
trarma[[2]], Delta, kappa) : maximum supported lag is 350?. Can someone
help me with this problem?
Thank you
Sincerely yours,
Laura Saltyte
2009 Mar 01
0
Variable scope.
I have a question on scope/reference/value type of variables with 'R'.
The issue cam up first when I look at the arima code.
I see code like:
myupARIMA <- function(mod, phi, theta) {
. . . .
mod
}
Then
armafn <- function(p, trans) {
. . . .
Z <- upARIMA(mod, trarma[[1]], trarma[[2]])
. . . .
res <- .Call(R_ARIMA_Like, x,
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 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
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,
2010 Aug 11
1
sem & psych
Dear R users,
I am trying to simulate some multitrait-multimethod models using the
packages sem and psych but whatever I do to deal with models which do not
converge I always get stuck and get error messages such as these:
"Error in summary.sem(M1) : coefficient covariances cannot be computed"
"Error in solve.default(res$hessian) : System ist f?r den Rechner singul?r:
reziproke
2009 Oct 23
2
reg-tests-1.R failure with unstable
Hi,
I am getting an error from one of the test files
tests/reg-tests-1.R using the unstable version (r50179).
(i've learned my lessons; this is a clean build.) The tail
of reg-tests-1.Rout.fail is
Loading required package: myTst
building package pkgA ...
installing package pkgA using file pkgA_1.0.tar.gz ...
Error in as.octmode(mode) : invalid digits
Error in install.packages(r, lib =
2007 Jun 18
1
two bessel function bugs for nu<0
#bug 1: besselI() for nu<0 and expon.scaled=TRUE
#tested with R-devel (2007-06-17 r41981)
x <- 2.3
nu <- -0.4
print(paste(besselI(x, nu, TRUE), "=", exp(-x)*besselI(x, nu, FALSE)))
#fix:
#$ diff bessel_i_old.c bessel_i_new.c
#57c57
#< bessel_k(x, -alpha, expo) * ((ize == 1)? 2. : 2.*exp(-x))/M_PI
#---
#> bessel_k(x, -alpha, expo) * ((ize == 1)? 2. :
2007 Jan 18
2
building R on freebsd 6.2 (amd64)
Hi,
I updated my os to freebsd 6.2 and built R-patched with no changes in
configure. I pass make check and copy the R executable to
/usr/local/bin/R. Then when I start R, I get
/libexec/ld-elf.so.1: Shared object "libRblas.so" not found, required by "R"
and have to copy/link the two shared object files (libRblas.so and
libRlapack.so) to somewhere "visible" like
2017 May 24
2
reg-tests-1d.R fails in r72721
Hi,
I am failing make check in r72721 at the end of reg-tests-1d.R. The
relevant block of code is
## path.expand shouldn't translate to local encoding PR#17120
filename <- "\U9b3c.R"
print(Encoding(filename))
x1 <- path.expand(paste0("~/", filename))
print(Encoding(x1))
x2 <- paste0(path.expand("~/"), filename)
print(Encoding(x2))
stopifnot(identical(
2017 May 24
2
reg-tests-1d.R fails in r72721
On 2017-05-24, Duncan Murdoch wrote:
>
> I think the test is wrong because in the first case you are working in a
> locale where that character is representable. In my locale it is not, so x1
> is converted to UTF-8, and everything compares equal.
>
> An explicit conversion of x1 to UTF-8 should fix this, i.e. replace
>
> x1 <- path.expand(paste0("~/",
2003 Feb 25
2
syntax rules
hi,
i lost half a day trying to figure out how r is parsing statements
in multiple lines. can someone explain (or direct me to documentation) the
following. consider the following statements in a program file, say
foo.r:
a <- 1 +
2;
b <- {1
+ 2};
{c <- 1
+ 2};
d <- c(1,
2);
if i do source("foo.r"), i get a=3, b=2, c=1, d={1,2}.
according to the r language definition