drawChessboardCorners argument isn't described (Bug #713)

Added by Kurt Konolige over 14 years ago. Updated about 13 years ago.

Status:Done Start date:
Priority:High Due date:
Assignee:Ethan Rublee % Done:

0%
Category:documentation
Target version:-
Affected version: Operating System:
Difficulty: HW Platform:
Pull request:

Description

Please describe the format of the corner array that is the 3rd argument of drawChessboardCorners.

Also please say you can take the return argument of findChessboardCorners and wrap it with cv::Mat() to get the correct matrix.

Associated revisions

Revision 077dd777
Added by Ethan Rublee over 14 years ago

Clarifying the findChessboardCorners and drawChessboardCorners documentation
as per the tickets: #712 and #713

Revision 2a1cf23f
Added by Andrey Kamaev almost 12 years ago

Merge pull request #713 from bitwangyaoyao:2.4_perf

History

#1
Updated by Ethan Rublee over 14 years ago

Yes, you can take a vector<Point2f> and wrap it in cv::Mat and get the correct matrix for drawChessboardCorners.

I'm not sure if this is an android issue... I'll see if I can clarify this in the documentation.

A typical usage of drawChessboardCorners:

  Mat gray = ....; //source image
  vector<Point2f> corners;

  bool patternfound = findChessboardCorners(gray, patternsize, corners);

  if(patternfound)
     cornerSubPix(gray, corners, Size(11, 11), Size(-1, -1), [[TermCriteria]](CV_TERMCRIT_EPS + CV_TERMCRIT_ITER, 30, 0.1));

  drawChessboardCorners(img, patternsize, Mat(corners), patternfound);

#2
Updated by Ethan Rublee over 14 years ago

I updated the tex documentation in r4070. Closing bug, re open if this explanation is not clear enough.

  • Status changed from Open to Done
  • (deleted custom field) set to fixed

#3
Updated by Andrey Kamaev about 13 years ago

  • Category changed from android to documentation

Also available in: Atom PDF