Custom Image Classifier: From Imbalanced Data to Production

You're deploying a model for a product catalog and get macro-F1 = 0.72 due to severe class imbalance. Recently, an e-commerce project approached us with a dataset of 15,000 images, 30 categories, where 80% belonged to five classes. We applied Weighted Random Sampler and Focal Loss, boosting macro-F1 from 0.72 to 0.94 in two weeks. The key challenge is not the model itself (standard benchmarks are passed), but adaptation to the specific domain: noise in labeling, lighting variations, incomplete data.

We also tackled a medical diagnostic project requiring detection of rare pathologies in MRI scans. The imbalance was even more severe: 99% healthy, 1% diseased. Combining oversampling, augmentation, and focal loss, we achieved sensitivity of 0.92 at specificity of 0.98. Projects start at $3,000 and vary based on complexity.

Which Architecture to Choose?

For most tasks, we select EfficientNet-B4 or ConvNeXt-Tiny: they offer a good balance of accuracy and inference time. EfficientNet-B4 is 2x faster than ViT-B/16 with comparable accuracy. The table below compares popular architectures.

For edge devices (Raspberry Pi, Jetson Nano), we use MobileNetV3 or EfficientNet-Lite – they run in 1–2 ms on CPU.

Why Fine-Tuning Beats Training from Scratch?

Training from scratch requires millions of labeled examples. Fine-tuning a pretrained model yields excellent results with just hundreds of images per class. This approach is described in Wikipedia: Transfer Learning. We also leverage contrastive learning and knowledge distillation to further improve performance.

import timm
import torch.nn as nn

def build_classifier(num_classes: int,
                     pretrained_model: str = 'efficientnet_b4'):
    model = timm.create_model(
        pretrained_model,
        pretrained=True,
        num_classes=0
    )
    embedding_dim = model.num_features  # 1792 for B4

    for param in model.parameters():
        param.requires_grad = False

    classifier = nn.Sequential(
        nn.Linear(embedding_dim, 512),
        nn.GELU(),
        nn.Dropout(0.3),
        nn.Linear(512, num_classes)
    )
    model.classifier = classifier
    return model

Fine-tuning strategy step by step:

1. Freeze backbone, train only classifier for 5 epochs.
2. Unfreeze last 2 blocks, train for 10 epochs with LR 10x lower.
3. Full unfreezing, another 10 epochs with cosine schedule.
4. Evaluate on validation: if metrics are not met, repeat with different hyperparameters.

How to Handle Class Imbalance?

Real datasets are rarely balanced. We combine several techniques:

• Weighted random sampler – sampling frequency inversely proportional to class size.
• Focal Loss – focuses on hard examples (γ=2).
• Oversampling rare classes via data augmentation (albumentations).
• Class-weighted cross-entropy – weights 1/class_frequency.

This approach lifts macro-F1 by 15–20% compared to baseline training. Order a pilot project – we'll show results on your data within two weeks.

Difference Between Multi-Class and Multi-Label Classification

Multi-class: one class per image – softmax + cross-entropy (e.g., animal type). Multi-label: multiple classes simultaneously – sigmoid + binary cross-entropy (e.g., photo tags). The threshold for each class is tuned separately based on F1.

Model Quality Metrics

• Top-1/Top-5 Accuracy for balanced sets.
• Macro-averaged F1 for imbalanced sets.
• Cohen's Kappa for medical tasks.
• AUC-ROC per class for multi-label.

Work Process for Classification System

Analysis → design → implementation → testing → deployment. In the first stage, we study your dataset, identify problematic classes, assess labeling quality. Then we select architecture and run a series of A/B experiments with hyperparameters. After model approval – export to ONNX, containerization, and deployment into your infrastructure. All steps are documented, your engineers receive access to the model and operating instructions. Contact us to get a cost estimate and roadmap for your project.

Timelines

Cost is determined after analysis – contact us for a detailed estimate.

What's Included?

• Data analysis and dataset preparation.
• Architecture selection and fine-tuning (with A/B config tests).
• Quality evaluation per chosen metrics (report).
• Deployment as REST API or integration into your infrastructure.
• Documentation and team training.
• Guarantee – if accuracy does not meet agreed targets, we rework for free.

With years of experience, we have completed over 40 image classification projects for e-commerce, medical, and industrial domains. Our engineers hold certifications from NVIDIA, AWS, and Google Cloud, and use MLOps practices for experiment reproducibility. We guarantee achieving target metrics – if accuracy is below the agreed level, we rework for free. Contact us to discuss your project and get a preliminary timeline estimate.

How Distribution Shift Kills CV Model Metrics in Industry

On a production line, a camera is installed to control product quality. The model is trained on 10,000 labeled images—test accuracy mAP 0.84. Deployed to production, and in the first week it misses 30% of defects. Lighting on the line changes between shifts; distribution shift nullifies the metrics. This is a classic story with computer vision in industry, where pattern recognition fails without proper drift handling.

Our engineers, with experience from 60+ computer vision projects, know how to eliminate such scenarios. We guarantee stable model performance under real conditions.

Object Detection: YOLO, RT-DETR, and Everything in Between

YOLO is the standard for real-time detection. YOLOv8 and YOLOv11 from Ultralytics are the most used versions in production: simple API, active community, built-in validation, and export to ONNX/TensorRT. For tasks with high accuracy requirements and less critical latency, RT-DETR, a transformer-based architecture without NMS, gives better mAP on COCO at comparable speed to YOLOv8l.

A typical mistake when training a detector: dataset of 8000 images, 3 classes, fine-tune YOLOv8m—F1 0.73 on validation. Look at confusion matrix—one class is almost never detected. Cause: imbalance 1:23. Solution: oversampling rare class, focal loss for objectness, augmentations (Mosaic, MixUp disabled for rare class as they "blur" it). Transfer learning is mandatory: pretrained on COCO weights reduces data requirement by 10 times. Fine-tuning on 500–2000 domain images yields a working model in 1–2 days on a single GPU.

For edge deployment: export to ONNX → TensorRT engine. YOLOv8n in TensorRT FP16 on Jetson AGX Orin gives 150+ FPS at P99 latency < 8 ms—3 times faster than ONNX Runtime without TensorRT. On server A10G: 700+ FPS for YOLOv8n in TensorRT INT8.

How Does Fine-Tuning YOLO Help in Pattern Recognition?

Suppose you need to find micro-defects on a metal surface—a task with high resolution and class imbalance. We use YOLOv8m pretrained on COCO and fine-tune on 2000 proprietary images. Apply augmentations Mosaic, MixUp, random perspective. After 200 epochs, mAP 0.5 reaches 0.93. Key techniques:

• Focal loss for the objectness head—reduces contribution of easily classified examples.
• Class-balanced sampling—equalizes representation of rare classes.
• Test Time Augmentation (TTA)—increases recall by 5–7% through averaging over flips and scales.

Get a consultation on architecture selection for your task—contact us.

Segmentation: SAM, Mask R-CNN, and Instance Segmentation

SAM (Segment Anything Model) from Meta changed the approach to segmentation. SAM 2 works with video, supports object tracking across frames—for interactive object selection by point or bbox, it's the best out-of-the-box choice. For production instance segmentation without interactive prompting, Mask R-CNN or YOLOv8-seg are used. YOLOv8-seg trains like a regular detector with additional masks, convenient in the same pipelines. Semantic segmentation (each pixel is a class) uses SegFormer, DeepLabV3+. SegFormer-B5 provides a good balance of accuracy and speed for satellite imagery or medical segmentation.

Case study: cell segmentation on microscopic images. Dataset of 400 images with manual annotation. Training Mask R-CNN on ResNet-50 backbone gave IoU 0.61—poor. Problem: objects (cells) overlap; standard NMS kills overlapping predictions. Solution: switch to cellpose (specialized architecture for biomedical tasks) + soft-NMS. IoU increased to 0.79.

OCR: When Tesseract Fails

Tesseract is a starting point for simple tasks: printed text, good lighting, straight layout. As soon as there are handwritten elements, non-standard fonts, perspective distortions, or multi-column layouts, Tesseract degrades quickly.

PaddleOCR is a production-grade solution: text block detection + recognition + structural analysis. Works out of the box for 80+ languages, including Russian. Supports tables and complex document structures. TrOCR (Microsoft) is a transformer OCR with strong results on handwritten text. For Russian handwritten text, fine-tuning is needed: the base model is trained mostly on Latin script.

What to Do When Tesseract Cannot Handle Pattern Recognition on Documents?

For tasks like "extract data from invoices/contracts/passports," we use LayoutLMv3 or Donut—these models understand document layout, not just text. Integration via Hugging Face Transformers, fine-tuning on 200–500 annotated documents. Typical pipeline:

1. Preprocessing: deskew, denoising, binarization via OpenCV.
2. Text block detection: PaddleOCR detection or CRAFT.
3. Recognition: PaddleOCR recognition or TrOCR.
4. Post-processing: normalization, validation via regex or LLM for structured fields.

For documents with fixed structure, template matching + OCR by coordinates is often more reliable than an end-to-end solution.

Face Recognition: Identification and Verification

Face recognition = detection + alignment + embedding + matching. Each stage matters.

Detection: RetinaFace or InsightFace for accurate face localization and keypoints. MTCNN is older but reliable. Embedding: ArcFace (InsightFace) is state-of-the-art for face recognition embeddings. Models iresnet50/iresnet100 pretrained on MS1MV3 (5M identities). Embedding vector 512 float32, comparison by cosine similarity. Threshold tuning: decision threshold is a critical parameter. At threshold 0.6, typical FPR on LFW benchmark is 0.001, TPR is 0.985. In production, threshold must be calibrated to the real distribution: people in masks, with changed appearance, different lighting conditions. Liveness detection is mandatory: MiniFASNet—lightweight model on CPU; FaceX-Zoo contains several pretrained liveness detectors.

Video Analytics

Video is a sequence of frames plus a temporal dimension. A naive approach—detecting on every frame—is expensive.

Tracking: ByteTrack and BoT-SORT are the standard for multi-object tracking. They work on top of any detector, adding persistent IDs to objects across frames—enabling object counting, motion tracking, velocity.

Optimization: not every frame needs processing. For static scenes, detect every 5–10 frames, with tracking in between. For event detection (person entering a zone), background subtraction (OpenCV MOG2) serves as a lightweight pre-filter before neural detection. Action recognition: SlowFast, VideoMAE for action classification. Heavy models—for production use ONNX export + TensorRT or offline processing.

How to Measure Pattern Recognition Model Quality in Production?

Quality monitoring is key to MLOps. We track:

• Prediction confidence distribution.
• Share of low-confidence predictions (indicator of OOD data).
• Drift of input images via feature distribution (embeddings from backbone).

A drop in average confidence from 0.87 to 0.71 over a week is an early signal of distribution shift. NVIDIA Triton Inference Server recommends tracking these metrics via Prometheus. Our certified engineers set up monitoring and guarantee SLA for inference quality.

Deployment of CV Models

For online inference, we use Triton Inference Server (NVIDIA)—production standard for serving CV models. Supports TensorRT, ONNX, PyTorch, dynamic batching, multiple instances. REST and gRPC API. We guarantee stable operation under load.

Edge deployment: ONNX Runtime on ARM/x86 CPU. TensorFlow Lite for mobile devices. OpenVINO for Intel CPU/GPU/VPU—gives 2–3× speedup on Intel hardware compared to ONNX Runtime. After deployment, we hand over the model with documentation and train personnel.

What Is Included in the Work

Deadlines and Cost

A prototype detector on existing data takes 1–2 weeks. Production system with optimization for target hardware takes 4–8 weeks. Full cycle including data labeling (1000–5000 images) takes 2–4 months. Cost is calculated individually for each task. Typical savings from implementing a quality control system can be significant per production line.

We have been in the market for over 5 years and completed 60+ computer vision projects. We will evaluate your project end-to-end—request a consultation to get a quote and technical proposal.