Metric Composition And Custom Criteria Evaluation

RAG evaluation framework — faithfulness, relevancy, context precision/recall metrics.

Unique: Metric system uses inheritance hierarchy (Metric → SingleTurnMetric → specific implementations) with PromptMixin for dynamic prompt management and Instructor adapter for structured output. Supports metric training/alignment workflows to calibrate custom metrics against human judgments.

vs others: More flexible than fixed metric suites because metrics are composable Python objects with pluggable LLM backends, enabling domain-specific evaluation without forking the framework.

via “custom metric definition with schema-based validation”

LLM evaluation framework — 14+ metrics, faithfulness/hallucination detection, Pytest integration.

Unique: Provides a BaseMetric abstract class with a standardized measure() interface and optional schema validation, allowing custom metrics to be plugged into the evaluation pipeline without modifying core code; includes helper functions (e.g., G-Eval prompt templates) to reduce boilerplate for common metric patterns

vs others: More extensible than Ragas because it provides clear extension points (BaseMetric subclass) and helper utilities for common patterns, reducing the friction for implementing custom metrics

via “custom-evaluation-metric-definition”

LLM eval and monitoring with hallucination detection.

Unique: unknown — insufficient data on custom metric implementation, API surface, and integration with the EvalRunner orchestration system. Documentation does not specify whether custom metrics are Python functions, declarative schemas, or another abstraction.

vs others: unknown — without clarity on implementation approach, cannot position against alternatives like Ragas custom metrics or LangSmith's custom evaluators.

via “custom metric definition and composition framework”

Evaluation framework for RAG and LLM applications

Unique: Implements a simple base class extension pattern for custom metrics with automatic integration into evaluation pipelines, enabling users to define domain-specific metrics without understanding internal framework architecture; supports metric-specific configuration through constructor parameters

vs others: Lower barrier to entry than building evaluation frameworks from scratch; provides scaffolding and integration points while remaining flexible enough for novel metric implementations

via “custom metric implementation with geval base class”

The LLM Evaluation Framework

Unique: Provides a GEval base class that abstracts LLM-as-judge metric implementation, handling prompt templating, response parsing, and score normalization. Custom metrics inherit caching and provider abstraction from the base class.

vs others: More extensible than fixed metric libraries and more integrated than standalone evaluation scripts because custom metrics inherit framework capabilities (caching, provider abstraction, result aggregation).

via “custom-evaluation-metric-definition”

via “custom evaluation metric definition and tracking”

via “custom-metric-definition-and-scoring”

via “evaluation metric definition and customization”

via “custom evaluation metrics and scoring”