liuruoze / liuruoze/EasyPR

字符定位车牌准确率怎么优化

Open
#294 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
6.4k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Description

**I'm submitting a ...** (check one with "x")
我这边尝试优化字符定位车牌的部分;但是介绍不是很详细,实际测试发现有很多不应该定位不到的情况出现(只是用字符定位plateMserLocate);我想知道我应该具体怎么优化呢?
```
[ ] bug [report]([url](url))
[ ] help wanted
[ ] feature request
```

![12](https://user-images.githubusercontent.com/9446616/49338000-67459080-f657-11e8-9616-a495c8e41967.jpg)

**Current behavior**

**Expected/desired behavior**

**Reproduction of the problem**

If the current behavior is a bug or you can illustrate your feature request better with an example, please provide the steps to reproduce.

**What is the expected behavior?**

**What is the motivation / use case for changing the behavior?**

**Please tell us about your environment:**

* **System:** CentOS

* **Compiler version/IDE:** gcc4.8

* **CMake version:** 3.5.1

* **OpenCV version:** [2.4.9 | 2.4.10 | 2.4.11 | 2.4.12 | 2.4.13 | 3.0 ALPHA | 3.0 BETA | 3.0 RC1 | 3.0 | 3.1 ]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the plateMserLocate entry point and reviewing how it is exercised under the stated CentOS, gcc4.8, CMake 3.5.1, and OpenCV environment. The issue provides no reproducible image set, failing test, or acceptance criteria, so the missed detections and what counts as improved accuracy need to be defined before work can be considered done.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, opencv
Domain
computer-vision
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.