Displaying 20 results from an estimated 10000 matches similar to: "arima models"
2017 Jun 20
1
How to write an estimated seasonal ARIMA model from R output?
I'm trying to use the following command.
arima (x, order = c(p,d,q), seasonal =list(order=c(P,D,Q), period=s)
How can I write an estimated seasonal ARIMA model from the outputs. To be specifically, which sign to use? I know R uses a different signs from S plus.
Is it correct that the model is:
(1-ar1*B-ar2*B^2-...)(1-sar1*B^s-sar2*B^2s-....)(1-B)^d(1-B^s)^D
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
2007 Oct 24
0
Package forecast
Hello All,
I trying to use the function auto.arima(....) from package forecast but I
have a problem.
My steps after I used the function auto.arima(...)
I create the time series like this:
>bbrass = scan("C:/Program Files/R/data PTIN/my_file.dat")
>regts.start = ISOdatetime(2006, 7, 1, hour=0, min=0, sec=0, tz="GMT") #2006
07 01 00
>regts.end = ISOdatetime(2006, 7,
2025 Jan 02
1
Possible issue in stats/arima.R package
On 2025-01-02 11:20 a.m., Duncan Murdoch wrote:
> On 2025-01-02 9:04 a.m., Norbert Kuder wrote:
>> Hello all,
>>
>> I am running R version 4.4.2 (2024-10-31 ucrt) on Windows 10 x64, and
>> noticed something that might be a minor bug (or at least inconsistent code)
>> in the stats/arima.R package.
>> I have found:
>> 1. A missing stop() call at line 69:
2025 Jan 02
2
Possible issue in stats/arima.R package
>>>>> Duncan Murdoch
>>>>> on Thu, 2 Jan 2025 11:28:45 -0500 writes:
> On 2025-01-02 11:20 a.m., Duncan Murdoch wrote:
>> On 2025-01-02 9:04 a.m., Norbert Kuder wrote:
>>> Hello all,
>>>
>>> I am running R version 4.4.2 (2024-10-31 ucrt) on Windows 10 x64, and
>>> noticed something that might
2025 Jan 02
1
Possible issue in stats/arima.R package
On 2025-01-02 9:04 a.m., Norbert Kuder wrote:
> Hello all,
>
> I am running R version 4.4.2 (2024-10-31 ucrt) on Windows 10 x64, and
> noticed something that might be a minor bug (or at least inconsistent code)
> in the stats/arima.R package.
> I have found:
> 1. A missing stop() call at line 69:
> if (length(order) == 3) seasonal <- list(order = seasonal) else
2003 Nov 18
0
arima() in ts
I am trying to find a way to obtain the fitted values for a model fit
using arima() in the ts package. I came across a suggestion in the
mailing list archive that these values can be simply calculated as:
model<-arima(t, order = c(1,1,0));
fitted<-t-model$residuals;
But, the help file for arima() in the ts package describes the residuals
values returned as being "standardized
2004 Jan 14
1
seasonal fractional ARIMA models
Hello,
does anyone know about:
a) simulating seasonal ARIMA models? arima out of package ts can fit it,
but it does not look like it can simulates data from seasonal models
b) fitting and simulating fractional seasonal ARIMA models?
Hints will be appreciated,
Henning
--
Henning Rust
Potsdam Institute for Climate Impact Research
Dept. Integrated Systems Analysis
Tel.: #49/331/288-2596
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 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),
2025 Jan 02
1
Possible issue in stats/arima.R package
>>>>> Martin Maechler on Thu, 2 Jan 2025 20:42:58 +0100 writes:
>>>>> Duncan Murdoch on Thu, 2 Jan 2025 11:28:45 -0500 writes:
>> On 2025-01-02 11:20 a.m., Duncan Murdoch wrote:
>>> On 2025-01-02 9:04 a.m., Norbert Kuder wrote:
>>>> Hello all,
>>>>
>>>> I am running R version 4.4.2 (2024-10-31
2003 Apr 07
1
filtering ts with arima
Hi,
I have the following code from Splus that I'd like to migrate to R. So far,
the only problem is the arima.filt function. This function allows me to
filter an existing time-series through a previously estimated arima model,
and obtain the residuals for further use. Here's the Splus code:
# x is the estimation time series, new.infl is a timeseries that contains
new information
# a.mle
2011 Jun 21
2
function to undo the DIFF command in ARIMA command
Hi users.
I'm new user in R.
I'm workiing with Time series and I would like to know how can I do to undo
the command DIFF(X), for exemple:
If I have the model: m=arima(X, order=c(0,1,1),
seasonal=list(order=c(0,0,1))) (note that have d=1 one difference), to find,
in the same scale, the original numbers (like one "unDiff"), after the
forecast, I need to develop some function or in
2005 Aug 27
1
ARIMA (seasonal) backcasting & interpolation
Thanks for everyone's help with zoo -- I think I've got my data set
ready. (The data consists of surface weather temperatures, from 2002
to 2005, one observation per hour. Some values are missing... i.e. NA)
I have three goals:
GOAL #1:Get the data in proper time series form, preserving frequency
information:
> w4.ts <- as.ts( w3.zoo, frequency=(1/3600) )
I hope that 1/3600
2005 Oct 13
1
arima: warning when fixing MA parameters.
I am puzzled by the warning message in the output below. It appears
whether or not I fit the seasonal term (but the precise point of doing
this was to fit what is effectively a second seasonal term). Is there
some deep reason why AR parameters
("Warning message: some AR parameters were fixed: ...")
should somehow intrude into the fitting of a model that has only MA
terms?
>
2008 Sep 16
0
Warning messages after auto.arima
Dear R-helpers.
Would appreciate if someone can explain the warning messages below, after
auto.arima. I couldn't find any clue in the archived help.
Also, how do I retrieve the AICs of each tried model in auto.arima? The
purposes are (1) to output to a text file, and (2) to find the 2nd best
model by finding 2nd lowest AIC instead of eyeballing thru the value at the
console
2011 Oct 21
2
Arima Models - Error and jump error
Hi people,
I´m trying to development a simple routine to run many Arima models result
from some parâmeters combination.
My data test have one year and daily level.
A part of routine is:
for ( d in 0:1 )
{ for ( p in 0:3 )
{ for ( q in 0:3 )
{ for ( sd in 0:1 )
{ for ( sp in 0:3 )
{ for ( sq in 0:3 )
{
2012 May 18
0
Forecast package, auto.arima() convergence problem, and AIC/BIC extraction
Hi all,
First:
I have a small line of code I'm applying to a variable which will be
placed in a matrix table for latex output of accuracy measures:
acc.aarima <- signif(accuracy(forecast(auto.arima(tix_ts,
stepwise=FALSE), h=365)), digits=3).
The time series referred to is univariate (daily counts from 12-10-2010
until 5-8-2010 (so not 2 full periods of data)), and I'm working on
2004 Jun 10
1
X-12-ARIMA
Dear All,
I've used the X-12-ARIMA or its earlier versions from S+ and R under both Unix
and Windows platforms for many years using the klugey approach of calling an
executable using in R the system function. I've found this serviceable for the
following reasons.
1) Paul Gilbert's hunch is correct that many of the subroutines have extensive
IO calls (especially the X-11 engine)
2004 May 24
0
Seasonal ARIMA question - stat package (formerly ts)
To whom it may concern:
I am trying to better understand the functionality of 'R' when making
arima predictions to avoid any "Black Box" disadvantages.
I'm fitting a seasonal arima model using the following command (having
already loaded 'stat' package).
arimaSeason <-
arima(Data,order=c(1,0,1),seasonal=list(order=c(1,0,1),period=12))
I can then generate