Acquisition
Iris capture requires optical and distance conditions appropriate to the device. Public documentation does not attribute NIR, single-eye or binocular capability to CheckID without a tested profile.
Iris requires suitable capture, quality control and segmentation before representation. separates enrollment, verification and identification and links the modality to compatible devices.
Eye acquisition → localization/segmentation → quality → template → 1:1/1:N
Iris capture requires optical and distance conditions appropriate to the device. Public documentation does not attribute NIR, single-eye or binocular capability to CheckID without a tested profile.
Eye/iris localization and segmentation must address eyelid/eyelash/occlusion/reflection according to the engine. Algorithm details absent from sources are not inferred.
Focus, usable iris region, occlusion and capture consistency are modality-specific quality dimensions rather than a generic cross-biometric score.
Enrollment should define eye/sample association, template/version and re-capture handling according to actual product sources.
Verification and identification use different protocols and performance measures. The API catalog supports `IRIS_IDENTIFICATION` in the identification-group context but provides no operating benchmark.
No eye, poor focus, excessive occlusion, segmentation failure, missing reference and search no-match are distinct classes to map to implementation results when source evidence exists.