Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
O
opencv_contrib
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
opencv_contrib
Commits
27f6d4e7
Commit
27f6d4e7
authored
May 27, 2017
by
Alexander Alekhin
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #1190 from catree:fix_aruco_doCornerRefinement
parents
2abf45d1
dc8e29a0
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
7 additions
and
7 deletions
+7
-7
detector_params.yml
modules/aruco/samples/detector_params.yml
+1
-1
aruco_detection.markdown
.../aruco/tutorials/aruco_detection/aruco_detection.markdown
+4
-4
charuco_detection.markdown
...co/tutorials/charuco_detection/charuco_detection.markdown
+2
-2
No files found.
modules/aruco/samples/detector_params.yml
View file @
27f6d4e7
...
...
@@ -12,7 +12,7 @@ minCornerDistance: 10.0
minDistanceToBorder
:
3
minMarkerDistance
:
10.0
minMarkerDistanceRate
:
0.05
doCornerRefinement
:
false
cornerRefinementMethod
:
0
cornerRefinementWinSize
:
5
cornerRefinementMaxIterations
:
30
cornerRefinementMinAccuracy
:
0.1
...
...
modules/aruco/tutorials/aruco_detection/aruco_detection.markdown
View file @
27f6d4e7
...
...
@@ -702,23 +702,23 @@ Default value: 0.6
#### Corner Refinement
After markers have been detected and identified, the last step is performing subpixel refinement
in the corner positions (see OpenCV ```
cornerSubPix()
```)
in the corner positions (see OpenCV ```
cornerSubPix()
```
and ```
cv::aruco::CornerRefineMethod
```
)
Note that this step is optional and it only makes sense if the position of the marker corners have to
be accurate, for instance for pose estimation. It is usually a time consuming step and it is disabled by default.
- ```
bool doCornerRefinement
```
- ```
int cornerRefinementMethod
```
This parameter determines if the corner subpixel process is performed or not. It can be disabled
if accurate corners are not necessary.
Default value:
false
.
Default value:
```
CORNER_REFINE_NONE
```
.
- ```
int cornerRefinementWinSize
```
This parameter determines the window size of the subpixel refinement process.
High values can produce that close image corners are included in the window region, so that the
High values can produce th
e effect th
at close image corners are included in the window region, so that the
marker corner moves to a different and wrong location during the process. Furthermore
it can affect to performance.
...
...
modules/aruco/tutorials/charuco_detection/charuco_detection.markdown
View file @
27f6d4e7
...
...
@@ -142,7 +142,7 @@ are optional. A similar example without these parameters would be:
std::vector
<int>
markerIds;
std::vector
<std::vector
<
cv::Point2f
>
> markerCorners;
cv::Ptr
<cv::aruco::DetectorParameters>
params;
params->
doCornerRefinement = false
;
params->
cornerRefinementMethod = cv::aruco::CORNER_REFINE_NONE
;
cv::aruco::detectMarkers(inputImage, board.dictionary, markerCorners, markerIds, params);
// if at least one marker detected
...
...
@@ -207,7 +207,7 @@ Finally, this is a full example of ChArUco detection (without using calibration
cv::Ptr<cv::aruco::CharucoBoard> board = cv::aruco::CharucoBoard::create(5, 7, 0.04, 0.02, dictionary);
cv::Ptr<cv::aruco::DetectorParameters> params;
params->
doCornerRefinement = false
;
params->
cornerRefinementMethod = cv::aruco::CORNER_REFINE_NONE
;
while (inputVideo.grab()) {
cv::Mat image, imageCopy;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment