Skip to main content
After ingestion converts raw corpus files into Arrow shards, the processing stage runs normalization and segmentation over every record — breaking continuous Myanmar text into syllables and words that downstream stages can count and index.

Overview

Pipeline Processing Flow

Components

CorpusSegmenter

The CorpusSegmenter processes Arrow shards and produces segmented output:
For most use cases, use the Pipeline class:

Configuration

Options

Segmentation Engines

MyWord (Default)

High-accuracy segmentation using the myword library:

CRF

Conditional Random Fields - good balance of speed and accuracy.

Transformer

Highest accuracy using a HuggingFace token classification model (XLM-RoBERTa fine-tuned for Myanmar word boundary detection). Requires the transformers package.

Comparison

Parallel Processing

Worker Configuration

Configure parallel workers via PipelineConfig:

macOS Note

OpenMP requires libomp on macOS:

Performance Optimization

Batch Size

Larger batches improve throughput:

Memory Management

For memory-constrained environments:

Benchmarks

Integration with Pipeline

See Also