cv.imread() pixel-level errors between py2 and py3
I'm debugging an image-related program in py2 and py3 environments. The strange point is, the performance in py3 env is always belower than that in py2 env. So I traced back to the very beginning,and I found that after the first cv.imread(), there exists pixel-level errors. The two pixels at the same location but in different envs having an difference of 1. .What may be the reason leading to this problem?
opencv in two envs: opencv3 - 3.1.0 - build py36_0 opencv - 2.4.11 -build nppy27_0
Besides, though searched, I'm still confused at the relationship of opencv3, opencv 3.x, and opencv 2.x. Can the version of opencv be the reason leading to this small difference?
Most likely you are trying to open
.jpgimage?@dkurt, sorry for the late reply, yes I'm trying to open an
.jpegfile. Any clues?I see. I didn't realize that it may be related to file formats and decompression process. Thanks for your insightful clues.