Displaying 20 results from an estimated 10000 matches similar to: "Differencing with auto.arima and xreg"
2008 Jan 11
1
question about xreg of arima
Hi,
I am trying to understand exactly what xreg does in arima. The documentation
for xreg says:"xreg Optionally, a vector or matrix of external regressors,
which must have the same number of rows as x." What does this mean with
regard to the action of xreg in arima?
Apparently somehow xreg made the following two arima fit equivalent in R:
arima(x, order=c(1,1,1), xreg=1:length(x))
is
2009 Mar 08
0
ARIMA second order differencing problem
Hi,
I have been using this site (
http://www.stat.pitt.edu/stoffer/tsa2/Rissues.htm) to help me with some
ARIMA modelling in R.
Unfortunately the methods mentioned do not appear to work with second order
differencing; arima(*, 2, *).
I have used some dummy data to illustrate my point.
When I use the xreg=... method, the estimate of intercept is *way* off. This
can be seen by the high s.e but I
2009 Nov 09
0
ARIMA, xreg and intercepts
David Stoffer describes some challenges with R's output when fitting
ARIMA models for different orders (see Issue 2 at
http://www.stat.pitt.edu/stoffer/tsa2/Rissues.htm). R doesn't fit an
intercept in the model if there is any differencing. David describes a
workaround using the xreg parameter to force R to calculate an
intercept.
Assume I have a variable y and 3 explanatory variables a,
2009 Mar 05
3
Time Series - ARIMA differencing problem
Hi,
I have been using this website (
http://www.stat.pitt.edu/stoffer/tsa2/Rissues.htm
http://www.stat.pitt.edu/stoffer/tsa2/Rissues.htm ) to help me to fit ARIMA
models to my data. At the moment I have two possible methods to use.
Method 1
If I use
arima(ts.data, order=c(1,2,0), xreg=1:length(ts.data))
then the wrong value for the intercept/mean is given (checked on SPSS and
Minitab) and
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
2015 May 21
3
Fix for bug in arima function
On 21 May 2015, at 12:49 , Martin Maechler <maechler at lynne.stat.math.ethz.ch> wrote:
>>>>>> peter dalgaard <pdalgd at gmail.com>
>>>>>> on Thu, 21 May 2015 11:03:05 +0200 writes:
>
>> On 21 May 2015, at 10:35 , Martin Maechler <maechler at lynne.stat.math.ethz.ch> wrote:
>
>>>>
>>>> I noticed that
2011 Jun 30
0
CCF of two time series pre-whitened using ARIMA
Hi all,
I have two time series that I would like to correlate but as they are
autocorrelated, I am "pre-whitening" them first by fitting ARIMA models,
then correlating their residuals....as described in
https://onlinecourses.science.psu.edu/stat510/?q=node/75
However, http://www.stat.pitt.edu/stoffer/tsa2/Rissues.htm discusses some
issues with ARIMA in R. In particular, for issue 2, if
2002 Nov 18
1
Prediction from arima() object (library ts) (PR#2305)
Full_Name: Allan McRae
Version: 1.6.0
OS: Win 2000 P
Submission from: (NULL) (129.215.190.229)
When using predict.Arima in library ts(), it appears differencing is only
accounted for in the first step of prediction and so any trend is not apparent
in the predictions. The example shows the difference between the predictions of
an arima(1,1,1) model and the backtransformed predictions of an
2015 May 21
0
Fix for bug in arima function
>>>>> peter dalgaard <pdalgd at gmail.com>
>>>>> on Thu, 21 May 2015 11:03:05 +0200 writes:
> On 21 May 2015, at 10:35 , Martin Maechler <maechler at lynne.stat.math.ethz.ch> wrote:
>>>
>>> I noticed that the 3.2.1 release cycle is about to start. Is there any
>>> chance that this fix will make it into
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,
2008 Sep 10
0
FW: RE: arima and xreg
hi: you should probably send below to R-Sig-Finance because there are
some econometrics people over there who could also possibly give you
a good answer and may not see this email ? Also, there's package called
mar ( I think that's the name ) that may do what you want ?
Finally, I don't know how to do it but I think there are ways of
converting a multivariate arima into the
2008 Sep 10
2
arima and xreg
Dear R-help-archive..
I am trying to figure out how to make arima prediction when I have a
process involving multivariate time series input, and one output time
series (output is to be predicted) .. (thus strictly speaking its an
ARMAX process). I know that the arima function of R was not designed
to handle multivariate analysis (there is dse but it doesnt handle
arma multivariate analysis, only
2007 Jan 16
2
ARIMA xreg and factors
I am using arima to develop a time series regression model, I am using arima
b/c I have autocorrelated errors. Several of my independent variables are
categorical and I have coded them as factors . When I run ARIMA I don't
get any warning or error message, but I do not seem to get estimates for all
the levels of the factor. Can/how does ARIMA handle factors in xreg?
here is some example
2008 Nov 27
1
"xreg" in ARIMA modelling.
Hello,
Does anyone know how the parameter estimates are calculated for xreg
variables when called as part of an arima() command, or know of any
literature that provides this info? In particular, I was wondering if there
is a quick way to compare different combinations of "xreg" variables in the
arima() fit in the same way that you would in multiple regression (using AIC
& R^2
2015 Apr 20
2
Fix for bug in arima function
There is currently a bug in the arima function. Namely, for arima models with differencing or seasonal differencing, the innovation variance estimator uses the wrong denominator whenever xreg is non-null. This is the case, for example, when fitting an ARIMA(p,1,q) model with a drift term (common in financial applications). I reported the bug (and a fix) at
2015 May 20
2
Fix for bug in arima function
I noticed that the 3.2.1 release cycle is about to start. Is there any
chance that this fix will make it into the next version of R?
This bug is fairly serious: getting the wrong variance estimate leads to
the wrong log-likelihood and the wrong AIC, BIC etc, which can and does
lead to suboptimal model selection. If it's not fixed, this issue will
affect every student taking our time series
2015 Apr 21
0
Fix for bug in arima function
The bug repository is like an elephant: It doesn't forget, but the gestation period is long.
In the present case, it is clear that something is not right, but someone needs to have sufficient recall and insight to check that your proposed fix is not unfixing a deliberate change. We should get to it eventually. (For some value of "we" not including "me"...)
-pd
On 20 Apr
2008 Jan 31
0
xreg in ARIMA function
Hi everyone,
I'm trying to include an external regressor in my ARIMA model but am having some problems with the data format in R. I've named my dependent variable of interest "count" and the external regressor "abc". The external regressor is a binary variable. Here are the contents of "abc" and the model I've attemped (along with its error message):
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)
2015 May 21
2
Fix for bug in arima function
On 21 May 2015, at 10:35 , Martin Maechler <maechler at lynne.stat.math.ethz.ch> wrote:
>>
>> I noticed that the 3.2.1 release cycle is about to start. Is there any
>> chance that this fix will make it into the next version of R?
>>
>> This bug is fairly serious: getting the wrong variance estimate leads to
>> the wrong log-likelihood and the wrong