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.
What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Added my full work for Assignment 1 — step-by-step KNN classification. Includes data inspection, standardization, setting a random seed, splitting the data, using GridSearchCV, and checking accuracy on test data.
What did you learn from the changes you have made?
I got a better understanding of how KNN works and why standardizing features is important. Also learned how to use GridSearchCV properly to tune hyperparameters.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
I mostly followed the standard path we practiced in the live code, but thought about checking fewer neighbor values just to save time. Ended up doing the full 1–50 range as asked.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Nothing major — just had to double-check a few steps to make sure I followed the format from class. Also confirmed that I was on the right Git branch before making edits.
How were these changes tested?
Ran everything in Jupyter Notebook — results looked good. Final test accuracy came out to around 0.955, which makes sense.
A reference to a related issue in your repository (if applicable)
N/A
Checklist