A visually correct preview is insufficient evidence that algorithm input data is correct. Capture-interface output, display images and model inputs may follow different processing paths. Record which capture interface supplies the image frames called original in the project. Those frames may already have passed through device image processing. The original label alone is insufficient evidence of unprocessed sensor data.

Record formats and processing by stage

Data stage Checks Records to retain
Capture interface Dimensions, pixel format, bit depth, row stride and time source Interface documentation and sample identifiers
Display image Color conversion, brightness mapping, scaling and overlays Display parameters and derived-file relationships
Algorithm input Channel order, data type, numerical range and shape Preprocessing configuration and model version
Result mapping Cropping, scaling, rotation and coordinate conventions Coordinate transforms and source-image references

Specify the channel order

Official OpenCV color-conversion documentation requires explicit channel order during conversion, such as RGB and BGR. A color-image description or file extension is insufficient as a format specification. Check input types and the actual API as well.

Keep source-to-input processing records

Assign stable identifiers to source frames and derived images. Record the order and parameters of cropping, scaling, rotation, color conversion and numerical processing. Use the model's documented numerical range, layout and normalization requirements rather than unverified generic assumptions.

Check the complete path using reproducible examples

Retain source data, display results, preprocessing outputs and associated parameters. Check whether selected pixels, regions, colors and coordinates change as configured. Lossy compression, quantization or other information-losing operations do not justify a promise of complete source-data recovery from derived images.

This method establishes data relationships. It does not report camera, driver or model compatibility validation. Related services: data, training and evaluation and project enquiries.