Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cvts vignette #66

Closed
dashaub opened this issue Jan 17, 2017 · 2 comments
Closed

cvts vignette #66

dashaub opened this issue Jan 17, 2017 · 2 comments
Milestone

Comments

@dashaub
Copy link
Collaborator

dashaub commented Jan 17, 2017

Add a cvts() vignette. This might have to wait while we work out the new API to handle xreg.

@dashaub dashaub mentioned this issue Jan 17, 2017
@dashaub dashaub added this to the 2.0 milestone Dec 31, 2017
@dashaub
Copy link
Collaborator Author

dashaub commented Jan 1, 2018

added 70d7262

@dashaub dashaub closed this as completed Jan 1, 2018
@russellcameronthomas
Copy link

In the last example of this vignette, you wrote (emphasis added):

As a final example, suppose we foolish want to implement our own version of naive() for performing cross validation.

I think I understand what you are trying to convey, but it is poorly worded for most readers, especially anyone who doesn't read English as a first language. Nobody will "foolishly want to implement their own version of naive()".

May I suggest this instead:

As a final example, I want to illustrate how you can write a custom model function (for the FUN parameter) and a custom forecast function (for the FCFUNparameter) to cross validate nearly any model. For illustration purposes only, I will implement a naive() model, where the forecast is simply a repetition of the last actual value in the time series.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants