8000 cvh/doc at main · zihaomu/cvh · GitHub
[go: up one dir, main page]

Skip to content

Latest commit

 

History

History

doc

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.md

cvh Documentation

cvh is an independent header-only C++ computer vision library. OpenCV is an API, behavior, and performance reference; it is not the product identity or a binary dependency of the normal cvh package.

Current Documents

Ownership Rules

Fact Owner
Public usage and current report entry top-level README.md
Product/module/target boundary design.md
CPU configuration and dispatch cpu-optimization.md
GEMM implementation facts gemm-optimization.md
Supported Pipeline API, v1 matrix, and execution contract pipeline-module-design.md
Pipeline P1 implementation status and evidence pipeline-p1-implementation-plan.md
Supported operation families API coverage
Tutorial organization and authoring contract tutorial/README.md
Phase 2-P0 acceleration work Phase 2-P0 operator acceleration plan
v0.1 direct-NEON hot-kernel work v0.1 NEON hot-kernel acceleration plan
v0.1 U8C3 fixed-point resize closure v0.1 Resize U8C3 fixed-point NEON acceleration plan
v0.1 Core/Mat native-NEON acceleration v0.1 Core/Mat native-NEON acceleration plan
Unfinished release work release-readiness plan
Test status test/ci/header_gate_expectations.json and upstream manifests
Performance numbers dated benchmark report plus CSV/metadata

Git history is the default archive for completed rollout logs. A restored historical record must be explicitly labeled and must not become the owner of current product facts.

Maintenance Rules

  • Documents describe current behavior or unfinished work. Git history retains completed implementation and acceptance records.
  • Local paths use portable placeholders.
  • Dated benchmark reports are immutable artifacts; corrections require a new dated report.
  • New benchmark reports are written in English.
  • Public claims must trace to code, tests, or report metadata.
  • Add, remove, or rename a document and this index in the same change.
  • Run scripts/check_docs.sh before committing documentation changes.
0