Displaying 20 results from an estimated 3000 matches similar to: "Time-series moving average question"
2018 Jun 01
2
Time-series moving average question
You are right that there are no NAs in the practice data. But there are NAs in the moving average data.
To see this, break your work into two separate steps, like this:
tnr.ma <- ma(dat3[1:28], order=3)
TNR_moving_average <- forecast(tnr.ma, h=8)
I think you will find that the warning comes from the second step.
Print tnr.ma and you will see some NAs.
-Don
--
Don MacQueen
Lawrence
2018 Jun 01
0
Time-series moving average question
Hi Don, wow, you are so right. I picked that piece up from the bloggers tutorial and since I am R naive yet, I thought it was all one step
moving_average = forecast(ma(tdat[1:31], order=2), h=5)
Truly, I usually print and check at every step I can, as painful as it is sometimes.
Great lesson for this novice usR.
So the first and last values are NA in each case? Do you know why? Should I replace
2018 Jun 01
0
Time-series moving average question
Good morning, I hope someone can help with these questions, or perhaps suggest one of the other R-lists?
I have two questions:
1. Why am I getting this warning?
2. Why is the second example "Point Forecast" the same value, I do not see that in previous attempts with similar but different data sets as in example 1?
Example1:
dat3 <- structure(c(3539122.86, 3081383.87,
2018 Jun 01
0
Time-series moving average question
Hello Don, thank you for your response. I appreciate your help.
I am using the forecast package, originally I found it following a forecasting example on bloggers.com
https://www.r-bloggers.com/time-series-analysis-using-r-forecast-package/
And subsequently located the complete pdf https://cran.r-project.org/web/packages/forecast/forecast.pdf
Since I created this practice data using the
2018 May 15
0
Forecasting tutorial "Basic Forecasting"
Instead of
Tsp = c(2016, 2018, 12)
try
Tsp = c(2016, 2018.25, 12)
Hence, you can specify the object as
structure(c(5973156.76, 5159011.2, 6695766.64, 6365359, 6495218.53,
7226302.39, 6835272.7, 7383501.57, 6962748.19, 7623278.72, 7274994.33,
7919421.8, 7360740.81, 7436693.35, 8545765.55, 7337269.76, 8180585.44,
8376635.05, 7758261.24, 10374641.22, 8000314.11, 9114958.9, 9805149.15,
2018 May 15
3
Forecasting tutorial "Basic Forecasting"
Hi. I am trying to follow this forecasting tutorial at: https://www.r-bloggers.com/basic-forecasting/
Using my own data, I cannot get past the first step, lots of laughs.
dat3 <- structure(c(5973156.76, 5159011.20, 6695766.64, 6365359.00, 6495218.53, 7226302.39, 6835272.70, 7383501.57, 6962748.19, 7623278.72, 7274994.33
,7919421.80, 7360740.81, 7436693.35,
2018 May 07
1
read.csv and Decimal places
... and see also ?print.data.frame , the "digits" argument.
See also ?str
It might be worth your while spending time with an R tutorial or two that
covers such topics, i.e. distinguishing between an object and various (S3)
methods that "represent" it, such as print(), summary(), plot() etc.
-- Bert
Bert Gunter
"The trouble with having an open mind is that people keep
2018 May 07
2
read.csv and Decimal places
Hi, Novice UsR here.
I have a csv file that contains 13 columns of numeric data that have decimal places (for the most part).
After reading in the file
RevFCast = read.csv("RevAnalysisNov2016_April2018.csv", header=TRUE, dec = ".", stringsAsFactors=FALSE)
and viewing the data
View(RevFCast)
Some of the fields came in with the correct decimals and some not?
The view in R:
2018 May 07
0
read.csv and Decimal places
The stored numbers are correct. They are rounded on printing.
print(RevFCast, digits=17)
See
?options
And scroll down to digits.
On Mon, May 7, 2018 at 11:50 Bill Poling <Bill.Poling at zelis.com> wrote:
> Hi, Novice UsR here.
>
> I have a csv file that contains 13 columns of numeric data that have
> decimal places (for the most part).
>
> After reading in the file
>
2018 May 04
0
Converting a list to a data frame
It looks like you made a copy/paste error below. Your ata.frame should
be data.frame.
Kevin
On 05/04/2018 08:18 AM, Bill Poling wrote:
> Good morning.
>
> Novice usR. Here.
>
> I am following this string, among many, learning as I go.
>
> Quick question please?
>
> I thought that perhaps ata.frame was part of the zoo pkg, b/c when I
> searched it came up in
2018 May 04
2
Converting a list to a data frame
Good morning.
Novice usR. Here.
I am following this string, among many, learning as I go.
Quick question please?
I thought that perhaps ata.frame was part of the zoo pkg, b/c when I searched it came up in help?
However, evidently not or I am not using it properly.
Please advise, thank you.
x <- list(A=data.frame(x=1:2, y=3:4),B=data.frame(x=5:6,y=7:8))
x2 <- do.call(rbind,
2017 Oct 02
2
Default value of the option initial in the ses function in the forecast package.
Dear All,
I am trying to use the function ses from the forecast package.
>From its help I have :
Usage:
ses(y, h = 10, level = c(80, 95), fan = FALSE, initial = c("optimal",
"simple"), alpha = NULL, lambda = NULL, biasadj = FALSE, x = y, ...)
My query is that if I do not mention the initial value will its default
value be "optimal".
A MWE would be
2017 Oct 02
0
Default value of the option initial in the ses function in the forecast package.
The first one, i.e. "optimal"; check help for match.arg() for the idiom.
-pd
> On 2 Oct 2017, at 11:48 , Ashim Kapoor <ashimkapoor at gmail.com> wrote:
>
> Dear All,
>
> I am trying to use the function ses from the forecast package.
>
> From its help I have :
>
> Usage:
>
> ses(y, h = 10, level = c(80, 95), fan = FALSE, initial =
2018 May 02
0
Converting a list to a data frame
Hi Kevin,
There is probably a better way, but it can be done in two steps like this
temp <- list(A=data.frame(x=1:2, y=3:4),B=data.frame(x=5:6,y=7:8))
temp <- lapply(names(temp), function(n, temp) {
temp[[n]]$type <- n
return(temp[[n]])
}, temp = temp)
do.call(rbind, temp)
On Wed, May 2, 2018 at 1:11 PM, Kevin E. Thorpe <kevin.thorpe at utoronto.ca>
wrote:
> I suspect
2008 Jan 31
3
too many open files....??
Hi all,
I''m fighting with an error message right now, that I don''t understand:
puppetmasterd[16269]: Could not write report for steinbeck.tnr.dk
at /var/lib/puppet/reports/steinbeck.tnr.dk/200801311728.yaml: Too
many open files
But an output from lsof states that there is only ~5500 files open -
not reaching any max I know of.
Anyone else experiencing this...?
--
Med
2011 Oct 21
4
plotting average effects.
hi... i am a phd student using r. i am having difficulty plotting average
effects. admittedly, i am not really understanding what each of the
commands mean so when i get the error i am not sure where the issue is.
here is my code... i will include the points at which there are errors....
> dat2 <- dat3 <- dat
> dat2$popc100 <- dat2$popc100 + 1000
>
2011 Apr 06
1
Teradata ODBC driver
Hi.
I have had this URL passed to me in order to obtain the necessary driver to connect my R application to our Teradata warehouse, however, the URL does not seem to exist anymore, my internet explorer browser fails to connect for some reason.
http://downloads.teradata.com/download/applications/teradata-r/1.0
Is there an alternative site or location for obtaining the necessary driver?
Thanks
2009 Mar 31
2
Does R support double-exponential smoothing?
I want to use double-exponential smoothing to forecast time series
datas,but I couldn't find it in the document,does R support this
method?
2009 Aug 07
3
How do I plot a line followed by two forecast points?
Good day all,
I'm trying to plot a continuous line plot, which is followed by two
forecast points eg. one forecast point is 12 months out, and another
24 months out from the last date of the line plot.
In my attempts so far, the second plot (the forecast points) is scaled
against a new axis scale, thus the two plots are not directly
comparable (I need the forecast points to be scaled
2013 Mar 15
2
Help finding first value in a BY group
I have a large Excel file with SKU numbers (stock keeping units) and
forecasts which can be mimicked with the following:
Period <- c(1, 2, 3, 1, 2, 3, 4, 1, 2)
SKU <- c("A1","A1","A1","X4","X4","X4","X4","K2","K2")
Forecast <- c(99, 103, 128, 63, 69, 72, 75, 207, 201)
PeriodSKUForecast <-