Formicant's profile - activity

overview network karma followed questions activity

2017-08-11 04:09:47 -0600	commented question	Destination image size of LinearPolar / LogPolar I’ve added this: https://github.com/opencv/opencv/issu...
2017-08-11 00:37:13 -0600	received badge	● Supporter (source)
2017-08-11 00:20:25 -0600	commented question	Destination image size of LinearPolar / LogPolar Should I open an issue in the OpenCV GitHub bugtracker?
2017-08-11 00:06:13 -0600	commented question	Destination image size of LinearPolar / LogPolar Sorry, I’ve just copied the text from the wrong place. I use OpenCV 3 actually.
2017-08-11 00:04:24 -0600	received badge	● Editor (source)
2017-08-10 23:55:32 -0600	received badge	● Student (source)
2017-08-10 23:53:16 -0600	commented answer	Is it possible to edit an image in hex format and then to open it as normal You could also consider steganography. https://en.wikipedia.org/wiki/Stegano... Choose a solution capable to survive JPEG compression.
2017-08-10 23:52:51 -0600	asked a question	Destination image size of LinearPolar / LogPolar The documentation says: `void cv::linearPolar (InputArray src, OutputArray dst, Point2f center, double maxRadius, int flags)` src – Source image dst – Destination image. It will have same size and type as src. … Why is the size of the destination image forced to be the same as the one of the source image? Does it make any sense? As far as I understand, the angular and radial resolution of the resulting image shouldn’t depend on the width and height of the source. Ideally, it should be set manually with some reasonable defaults depending on the maxRadius parameter (say, maxRadius × 2π∙maxRadius to match the resolution of the circle edge, or maxRadius × π∙maxRadius to match the average resolution of the source for LinearPolar).