On Thu, Oct 22, 2009 at 7:06 PM, Chris Colbert firstname.lastname@example.org wrote:
for the limit for uint8 regardless of what may be routine is 255 ;)
that said, I think a more important question is how should we handle overflow on uint8 images? and should we even bother trying?
The numpy standard is to wrap, the opencv standard is to threshold at 255. I don't see any easy way to make either of these two do it the other way.
Indeed not easy to do, and there's very little one can do with uint8 data anyway. Don't bother trying I would say.
2009/10/22 Stéfan van der Walt email@example.com:
A question that pertains to the scikit as a whole: what do we assume the limits of images to be? I think a common convention is 0-255 for type uint8 and 0-1 for type float. These need to be handled in all functions, and we may soon see patterns emerging that can be captured in standard utility functions.
For float images I think we should not assume anything. Rescaling loses information that is valuable, like absolute light intensity. Is there a need to make an assumption like this?
uint8: 0-255, the only choice. but again, why assume anything?