Fixed Review of Issue #3: Traversal of the space of train/test splits #161
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One consideration for further exploration is how you would investigate the statement that 0.4/0.6 is an anomaly in your conclusions. Perhaps multiple runs with a variable random seed to see how the performance at different split ratios is affected by the random assignment into test vs train portions is worth investigating.
Above was the previous review made by @mlopatka in #101
I have researched on the above review and in this PR, I have been able to analyze the effect of different random state numbers (in the train_test_split function) on the performance of the model.