Open
Conversation
- Add filter_low_quality parameter (default True for backward compat) - Check if 'low_quality' column exists before filtering - Add clear error message for missing required columns - Print warning when low_quality column is expected but not found
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
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.
Bug Fix
This PR fixes #2 - the KeyError when 'low_quality' column is missing from info.csv.
Problem
When loading the Alan dataset, if the CSV file doesn't have a 'low_quality' column, the code fails with:
Solution
filter_low_qualityparameter (default True for backward compatibility)Changes
Usage