# What are the min and max arguments to EdgeDetect?

What are the min and max arguments to EdgeDetect, for all methods and specifically "Sobel"? How do I find the limits or ranges of functions in the future? Or is it 255?

• See Image Processing for the basics on image representation. Generally, channels and threshholds have a range of 0 to 1. Dec 23 '13 at 1:47
• You can find default values in the documentation: in the "Details and Options" section. It is most assuredly not 255 as Mathematica scales pixel values between 0 and 1. Dec 23 '13 at 1:48
• @MichaelE2 @ bill I think this could be a good question, as I think the doc of EdgeDetect is not very clear, and there DO be differences between a threshhold of 1 and 1.1. Dec 24 '13 at 12:55
• @Silvia Interesting. I interpreted the question as primarily "How do I find the limits or ranges of functions in the future." There seems to be a lack of explanation of thresholds and EdgeDetect in the docs. Dec 24 '13 at 14:47
• @MichaelE2 I always do some try-and-fail attempts when using some functions like EdgeDetect, I think they really need a more insightful documentation :( Dec 24 '13 at 14:55

In EdgeDetect[image, radius, threshold], the radius is expressed in pixels, and the threshold corresponds to normalized pixel values (ie. in the range from 0 to 1).

@Silvia, there may be differences between a threshold of 1 and a threshold of 1.1 indeed. Such cases include:

1. "Real" or "Real32" images where pixel values are outside the 0-1 range.
2. Multichannel images for which the vector gradient magnitude is greater than 1.
• So, Real images are not normalized in general? Or just in this particular case? Dec 30 '13 at 20:37
• The normal range for "Real" and "Real32" data type images is from 0 to 1. But these images can also hold values outside the 0-1 range. An example where it expected is LaplacianFilter that yields positive and negative pixel values. Dec 30 '13 at 21:12
• Matthias, I think it would be helpful if you noted in your profile that you work at WRI. Not because it is necessary (it is not), but because it would certainly make this answer credible for users who do not know that you work at WRI :)
– rm -rf
Dec 30 '13 at 22:47
• @rm-rf I try to write credible answers that stand by themselves --- falling a bit short at times unfortunately. Dec 30 '13 at 23:51
• Oh, I didn't mean to imply that your answers are not credible/don't stand for themselves... Sometimes, the nature of the question is such that it is impossible for the average user to be able to answer it authoritatively using only the documentation and/or spelunking. In such situations, an answer from someone who actually develops these functions and implements algorithms is much more valuable than speculations. I suppose I actually meant to use the word "authoritative" than "credible" :)
– rm -rf
Dec 31 '13 at 0:00