Modular Detector Architecture Composition Via Registry System

via “modular detector composition via registry-based architecture”

OpenMMLab detection toolbox with 300+ models.

Unique: Uses a centralized registry system (MMCV Registry) where each detector component (backbone, neck, head, loss) is independently registered and instantiated via Python config files, enabling zero-code-modification composition compared to frameworks like Detectron2 that require subclassing or factory functions

vs others: More flexible than Detectron2's factory pattern because new components integrate purely through registration without touching detector assembly code; more discoverable than TensorFlow Object Detection API's config-based approach because Python configs enable IDE autocompletion and type hints

via “custom model architecture composition via modular components”

Meta's modular object detection platform on PyTorch.

Unique: Registry-based component system that enables custom architectures to be defined as nn.Module subclasses and composed via config, without modifying core Detectron2 code or forking the repository

vs others: More extensible than monolithic frameworks because components are registered and instantiated dynamically, enabling custom architectures to coexist with built-in ones in the same codebase

OpenMMLab Detection Toolbox and Benchmark

Unique: Uses a centralized registry pattern with lazy component instantiation, allowing arbitrary combinations of backbones, necks, and heads without inheritance hierarchies or factory methods — components are discovered and instantiated from configuration strings at runtime

vs others: More flexible than monolithic detector classes (like Detectron2's fixed inheritance chains) because any backbone can pair with any neck/head combination through the registry, reducing boilerplate and enabling rapid experimentation