Solving : Issue with Accuracy Calculation #19
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
There happens to be some error in app.py. Please check it again |
|
I checked app.py and resolved issue also update requirements.txt |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
Instead of just counting matching characters, we calculate edit distance (insertions, deletions, substitutions).
Accuracy is based on how close the user's input is to the original passage.
Instead of blindly counting words, we count correctly typed words using word-level comparison.
🔍 Improvements Explained
✅ 1. More Accurate WPM Calculation
We count correctly typed words instead of just total words typed.
It ensures that errors impact the WPM calculation.
✅ 2. Better Accuracy Using Levenshtein Distance
The edit distance accounts for extra/missing characters.
The formula:
Accuracy=(Max Length−Edit Distance/Max Length)×100