-
Notifications
You must be signed in to change notification settings - Fork 5
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
Train function #33
Comments
A function named |
We have a function called predict. We should also have one called train. I wouldn’t bother with train/test in the same function.
From: Dario Strbenac ***@***.***>
Sent: Friday, 26 August 2022 11:00 AM
To: DarioS/ClassifyR ***@***.***>
Cc: Ellis Patrick ***@***.***>; Author ***@***.***>
Subject: Re: [DarioS/ClassifyR] Train function (Issue #33)
A function named train doesn't suggest that prediction happens but it would. What about independentTrainTest?
—
Reply to this email directly, view it on GitHub<#33 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACAALBMKAQSKHEHZC3IXHKTV3AJKHANCNFSM56DDBU7A>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Closed by ba722d2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If would be good to have a train() function to complement predict() for situations where people don't need to run crossValidate.
Effectively this would take most of the same input as crossValidate() and then do a runTest.
One key distinction from crossValidate would be that for multiViewMethod is only fits one model. So by default this should be the full model unless they specify a assayCombination.
The text was updated successfully, but these errors were encountered: