On 12 April 2012 09:15, Alexander Görtz <nyl...@googlemail.com> wrote: > Maybe if you are on to some simple changes I have some more bugs for you :P > I'm not sure if I should start a new topic for new bugs if I should just say > so and I will resend this message under a new topic.
Do send over a new topic or submit them here http://sourceforge.net/tracker/?group_id=2888&atid=102888 We much prefer bug reports a patch. > the mat2gray function doesn't handle zero matrices like > mat2gray(zeroes(10,10)) results in a division by zero. It's not that much of a > deal but I was wondering about some strange NaN errors after doing the above. Check the development release. mat2gray should return a matrix of 1 in those cases. This is still not matlab compatible. I have made further changes to it this morning and now should return zeros. The problem is the way matlab handles the image when the min and max are the same. I've been trying to figure out the logic behind it but I don't get it and it's not documented. Carnë ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
