Skip to content

Commit a245f8c

Browse files
author
James-QiuHaoran
committed
update doc
1 parent 7d92087 commit a245f8c

File tree

2 files changed

+11
-1
lines changed

2 files changed

+11
-1
lines changed

stop-sign-detection.cpp

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,6 @@ int main(int argc, char** argv) {
4343
// start time
4444
int t0 = clock();
4545

46-
bool stop_sign_found = false;
4746
Mat tmpImg = prototypeImg.clone();
4847
Mat window;
4948
cout << tmpImg.rows << " " << tmpImg.cols << endl;

stop-sign-detection.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -107,3 +107,14 @@ After get the location of the stop sign, we draw a rectangle to mark it. Here, `
107107
// show the image
108108
imshow("image", targetImage);
109109
```
110+
111+
## Tuning Parameters
112+
113+
There are several critical parameters in this program detecting stop signs:
114+
115+
- `THRESHOLD` - given the algorithm runs well, this parameter should be the threshold of distinguishing images with stop signs and images without stop signs. It can be set after we run a huge amount of tests and choose a suitable value that do not yield much precision.
116+
- The descending scale - it determines the execution time. The larger the scale is, the faster the program runs but the result would not be good if scale is larger than some value.
117+
- The minimum pyramid value - it determines when the for-loop generating pyramids of prototype image will stop. Similar to the descending scale, it should be cautiously chosen by tuning with the test results.
118+
- Iterative step of searching match in the target image - similar to descending scale, the result will be worse if step is too large but if step is too small the program will take a lot of time.
119+
120+
It's believed that these parameters should be tuned with the help of machine learning and large amounts of test cases. Currently the program will give a decision in about 1-2 seconds with correct rate around 70%.

0 commit comments

Comments
 (0)