Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upTimeSlice feature request #346
Comments
|
This would also be useful for non-time slice models too. If all of the models in the tuneGrid are bad, it might not be worth the time to train the final model. |
|
Good point. I'll think of a good way to do that. |
|
great. fyi i made the following modification to train.default : <<
then i also modify the output of trainControl as follows : Control <- trainControl(....) thanks for all your great and valuable work on caret!! Jason
|
|
To solve some unknown future issues, I think that I will make an option On Fri, Jan 15, 2016 at 12:15 PM, jbheman notifications@github.com wrote:
|
|
I just checked in a change for this if you would like to give it a try. |
|
Will do thanks!
|
|
I'm going to assume that these changes are good for your problem. |
|
Hi @topepo , I am not sure if
Please see following code
The above code gives result
It says it fit final model on full training set. I thought caret should return an error when using only two samples! In addition, changing the
Thanks for your help! |
hi,
Regarding timeslice cross-validation : I think it would be useful to have an option NOT to fit a 'final' model on the full dataset. The whole point of timeslice crossvalidation in many contexts is to reflect the temporal context with non-stationarity. We fit a model only using X days of lookback and test on the next Y days - partly to determine if that X-Y paradigm is effective. In this case I'd rather not waste cycles training the model on the full data set because at the end i'm only interested in the most recent fit and the hyperparameters.
best, Jason