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.
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
Potato/inner/calibration split #483
Potato/inner/calibration split #483
Changes from all commits
7586614
7bbc732
c966979
d306c59
d668b75
893b071
f42e8fd
c582aaf
171c83f
3a6030a
f915a34
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we happy with that name? We can also go back and change it later (like container -> tailor).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do kind of appreciate that
inner_split()
gives the vibe that these methods are for internal use.inner_split()
feels good to me! I'm open to other options but would give preference to names that hint these are for expert use only.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not to be pedantic, but wouldn't
class_inner
by definition be"mc_split_inner"
? same for otherclass_inner
. While i appreciate the same code being used across, I think we could just note the class directlyThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean that in reference to this particular method or for all the methods?
Since I had just come across #478, I opted for constructing the class rather than writing it out manually here to make sure it would always stay in sync with the class of the input
x
. In terms of readability, I would say that the class of that one is fairly easy to see from the S3 dispatch.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what i meant, is that each
paste0(class(x)[1], "_inner")
in this file could be swapped with amc_split_inner
,apparent_split_inner
, etc etc as they are called inside s3 methods, on the object that drives the s3 dispatchThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that the basic idea of
clustering_cv()
is to use one cluster as the assessment set, I would reducev
by one for the inner split, so that the cluster left out for the inner split is more likely to be similar to one of the original clusters. If we use the samev
, the inner clustering is likely to break up thev-1
clusters in this (outer) analysis set.I would put that into tune though, not here.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.