Fix: Resolve factor conversion error in randomForest model #47
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixed bug related to non-numeric argument in prediction process by ensuring correct data types for input variables. Refactored the datasetInput reactive expression for better clarity and efficiency.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
The original app was throwing the following error during model training:
Error in y - ymean : non-numeric argument to binary operatorThis occurred because the
play,outlook, andwindycolumns were being read as characters rather than factors, whichrandomForestrequires for classification.Changes
stringsAsFactors = FALSEtoread.csv.play,outlook, andwindyto factors (Lines 23-25).datasetInputreactive expression in the server to ensure input data types match the training data levels exactly.