Heuristic Filtering
Heuristic filtering uses simple, rule-based metrics to identify and filter out low-quality documents from your dataset. NVIDIA NeMo Curator provides a variety of pre-built heuristic filters that can be configured and combined to meet your specific needs.
How It Works
Heuristic filters examine specific attributes of text documents and apply predefined thresholds to determine document quality. Unlike classifier-based filtering, heuristic filters don’t require training data but rely on configurable thresholds and rules.
These filters assess quality using measurable document characteristics such as:
- Document length (word or character count)
- Punctuation ratios and patterns
- Repetitive content detection
- Language-specific patterns
- Text completeness and coherence
For details on filter structure and the filtering process, refer to Data Processing Concepts .
Usage
Python
Configuration
Available Filters
NeMo Curator includes more than 30 heuristic filters for assessing document quality. Below are the most commonly used filters with their parameters:
Text Length Filters
Repetition Detection Filters
Character and Symbol Filters
Content-specific Filters
Special Purpose Filters
Configuration
NeMo Curator pipelines can be configured using YAML files with Hydra. The configuration uses _target_ to specify class paths:
Hydra Configuration
See nemo_curator/config/text/ for complete pipeline examples.
For non-English texts, you may need to adjust the filter parameters based on the specific characteristics of your target language.
Best Practices
When building filter chains, follow these best practices:
Order for Efficiency
Performance Tuning
Precision vs. Recall
Language Considerations
Multiple Filters
Analyzing Filter Results
When tuning filter thresholds, analyze score distributions before applying filters. NeMo Curator provides two modules for this workflow:
Score: Computes scores and adds them as columns without removing documentsScoreFilter: Computes scores, filters based on thresholds, and optionally retains scores in output
Use Score first to understand your data distribution, then apply ScoreFilter with tuned thresholds.
Score Without Filtering
Analyze Score Distribution
Apply Tuned Filters
Use Score to add score columns to your data without removing any documents:
Output files are written to the scored_output/ directory with one file per input partition.
Performance Tuning
For large datasets, consider these performance optimizations:
XennaExecutor (Default)
RayDataExecutor (Experimental)
Batch Size Optimization
XennaExecutor is the default executor, optimized for streaming workloads. You can customize its configuration or use the defaults:
If no executor is specified, pipeline.run() uses XennaExecutor with default settings.
Remember that the goal of filtering is to improve the quality of your training data, not necessarily to remove as many documents as possible. Monitor your filtering results and adjust thresholds based on your specific data characteristics and downstream tasks.