Fix UnboundLocalError in WER metric computation #40402
Merged
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.
Summary
Fixes a variable naming conflict in the
compute_metricsfunction example in the ASR documentation that causes anUnboundLocalError.Problem
The original code had a naming conflict where
werwas used both as:wer = evaluate.load("wer"))wer = wer.compute(...))This caused Python to treat
weras a local variable throughout the function, leading to anUnboundLocalErrorwhen trying to access it before assignment.Solution
wertower_metricwer_scoreChanges
docs/source/en/tasks/asr.md: Fixed variable naming in compute_metrics exampleTesting
Type of Change