You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- $\begingroup$ The cut between training and test data is (in most cases) as arbitrary as any cut inside the training set. Additionally, what excactly does it tell you if your accuracy/any other measure is slightly worse on the test set? And if it is significantly worse, all you know is something went wrong with your CV. Anyways, for both arguments, doing a repeated CV would give you more robust results (with each individual CV being better). If computational expense is a factor, comparing variance should give a sufficiently good measure in any of those cases without the risk of an (un)lucky test set. $\endgroup$Linrael– Linrael2024-11-11 13:57:54 +00:00Commented Nov 11, 2024 at 13:57
- $\begingroup$ @Linrael You say "if it is significantly worse, all you know is something went wrong with your CV", but without a test set you would not have realised this. How you separate the test data and create the cross-validation folds also matters: if you are looking at multiple observation for various individuals, there is a distinction between forecasting for the same individuals or forecasting fro new individuals, ans your data splits should reflect this. $\endgroup$Henry– Henry2024-11-11 21:53:24 +00:00Commented Nov 11, 2024 at 21:53
- $\begingroup$ Usually a repeated CV shows this. And to include measurement specific features into your training process there is grouped CV to consider this. $\endgroup$Linrael– Linrael2024-11-15 12:38:58 +00:00Commented Nov 15, 2024 at 12:38
- $\begingroup$ It is a best practice. I have definitely at times ignored this and just relied on CV results, because, indeed, I also believe it is usually fine. There are times when your CV results will however overestimate true performance, when you have little data, lots of hyperparameters. And it is not so easy to know when this starts having an effect. $\endgroup$Gijs– Gijs2024-11-18 08:03:59 +00:00Commented Nov 18, 2024 at 8:03
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
- MathJax equations
$\sin^2 \theta$
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. machine-learning), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you