From 30e930f051996736c6aa95f64a3733da848de59e Mon Sep 17 00:00:00 2001 From: Jade Date: Sun, 29 Sep 2024 23:42:19 +0800 Subject: [PATCH] [docs] Fix invalid max error bits recommendation (#1443) --- docs/source/docs/apriltag-pipelines/2D-tracking-tuning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/docs/apriltag-pipelines/2D-tracking-tuning.md b/docs/source/docs/apriltag-pipelines/2D-tracking-tuning.md index 84e760611..c9f205eb6 100644 --- a/docs/source/docs/apriltag-pipelines/2D-tracking-tuning.md +++ b/docs/source/docs/apriltag-pipelines/2D-tracking-tuning.md @@ -47,7 +47,7 @@ Pose iterations represents the amount of iterations done in order for the AprilT Max error bits, also known as hamming distance, is the number of positions at which corresponding pieces of data / tag are different. Put more generally, this is the number of bits (think of these as squares in the tag) that need to be changed / corrected in the tag to correctly detect it. A higher value means that more tags will be detected while a lower value cuts out tags that could be "questionable" in terms of detection. -We recommend a value of 0 for the 16h5 and 7+ for the 36h11 family. +We recommend a value of 0 for the 16h5 and at most 3 for the 36h11 family. ### Decision Margin Cutoff