Very (very) large image causes issues with function (int type related)

asked 2017-11-21 04:10:59 -0600

41 ●1 ●4

Hello !

I'm working on large images (~65000x40000 on average). I've experienced multiple issues with some functions (ie. cv::threshold and cv::medianBlur) that I don't have if I downscale these images.

After some code digging, I think the issue comes from the use of "int" types in most functions which, obviously, can't fit my size.

For example, in functions cv::threshold with Triangle method, operations like this are done:

size.width *= size.height

Is there any "easy" solution to use "int64" instead of "int" in OpenCV ? I've tried to change cv::Size alias from Size2i to Size2l but it isn't enough as most of OpenCV functions uses "int" as input/output type...

Thanks :)

answered 2017-11-21 16:39:22 -0600

Tetragramm

7376 ●13 ●37

Easy? No. But you can make the changes in each function as you use them and submit the changes as a pull request so they get integrated into the main trunk.

Part of the heritage of OpenCV is that it was once all C code. So it lacks a uniform use of typedefs or templates, such as the size_t you're familiar with from the C++ STL. So most people going along just assumed that int will be big enough.

Also, those are really big images.

edit flag offensive delete link

Comments

Thanks for the quick answer.

I assume OpenCV is also meant to be memory efficient so a straightforward change from int to size_t isn't a viable solution (even if, maybe, the change on cv::Size maybe insignificant in this regard). Am I right ?

However, this kind of change seems difficult to avoid (in C++).

In any case, I will typedef Size as Size_ <std::size_t> to workaround my (very) niche needs and see if it's enough for my algorithm. If I see that it works just fine and that it doesn't impact the memory efficiency of the library too much, I'll propose it to the community :).

Florent Tomi ( 2017-11-22 03:12:53 -0600 )edit

Yeah, the change from a 32 to 64 bit total size should have very little effect. You could even just change it to an unsigned int. It's just that there's no standard type for total size, so people just used whatever they thought was appropriate, which was often an int.

Tetragramm ( 2017-11-22 12:38:34 -0600 )edit

add a comment

Very (very) large image causes issues with function (int type related)

1 answer

Comments

Links

Question Tools

Stats

Related questions

Very (very) large image causes issues with function (int type related) edit

1 answer

Comments

Links

Question Tools

Stats

Related questions

Very (very) large image causes issues with function (int type related)