search for: moving_averag

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 the NA with a value, say the average of the others?...

Hi We're using 1.8.23.1 on CentOS 5 and are trying to get accurate stats for queues. For a particular customer, when I run queue show <queue_name> I get the following numbers: <queue_name> has 0 calls (max unlimited) in 'ringall' strategy (17s holdtime, 94s talktime), W:0, C:175, A:44, SL:48.6% within 45s So from that data we look at 17s holdtime And assume that is the

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 Livermore National Laboratory 7000 East Ave., L-627 Livermore, CA 94550 925-423-1062 Lab cell 925-724-7509 ? From: Bill Poling...