2017-08-15 11:39:38 -0600 | received badge | ● Student (source) |
2015-02-04 14:55:28 -0600 | commented question | Where can I find documentation for image registration? I looked into this about 6 months ago and didn't have much luck. Hopefully someone can provide more guidance on this issue. Good luck! |
2015-02-04 13:59:37 -0600 | received badge | ● Editor (source) |
2015-02-04 13:53:40 -0600 | asked a question | imdecode, imread mismatch I've found that when using imdecode and imread on identical Byte data I get different Mats returned. I am trying to decode corrupt JPEG files (essentially the first half or so of a JPEG file). imread handles the decoding gracefully filling in the missing data with a flat value. imdecode returns a Mat with 0 rows. Based on the documentation for imdecode I would expect their functionality to be identical. My question is, is this a bug or a feature request? It's not strictly speaking a bug, but it would seem sensible to me to have imread read the Byte data and then hand that off to imdecode so that their functionality would be iden |
2015-02-04 13:49:04 -0600 | commented question | Bug or feature request? This question does not show up on my profile's question section. Did I do something wrong? |
2014-11-13 14:43:55 -0600 | asked a question | Bug or feature request? I've found that when using imdecode and imread on identical Byte data I get different Mats returned. I am trying to decode corrupt JPEG files (essentially the first half or so of a JPEG file). imread handles the decoding gracefully filling in the missing data with a flat value. imdecode returns a Mat with 0 rows. Based on the documentation for imdecode I would expect their functionality to be identical. My question is, is this a bug or a feature request? It's not strictly speaking a bug, but it would seem sensible to me to have imread read the Byte data and then hand that off to imdecode so that their functionality would be identical. |
2014-11-13 13:57:38 -0600 | asked a question | bug or feature? I've found that when using imdecode and imread on identical Byte data I get different Mats returned. I am trying to decode corrupt JPEG files (essentially the first half or so of a JPEG file). imread handles the decoding gracefully filling in the missing data with a flat value. imdecode returns a Mat with 0 rows. Based on the documentation for imdecode I would expect their functionality to be identical. My question is, is this a bug or a feature request? It's not strictly speaking a bug, but it would seem sensible to me to have imread read the Byte data and then hand that off to imdecode so that their functionality would be identical. |