Steve on Image Processing

October 8th, 2008

Getting updates on reported bugs

Did you know that MathWorks publishes information about product bugs on its web site? And that you can be automatically notified with updates regarding specific bugs, or regarding specific products?

A few weeks ago, Joan posted a blog comment about strange behavior in the deconvwnr function. I investigated and determined that there was a bug in some code that was intended to avoid divide-by-zero warnings. I fixed the problem and then published a bug report, including a work-around, to our support site. (The fix was too late to be included in the upcoming R2008b release, so it will be in R2009a.)

The bug report includes a summary of the problem, which product releases have the problem, whether the problem has been fixed in a shipped release, and whether there is a work-around. In the case of the deconvwnr problem, there is a work-around, and the report includes instructions for downloading new versions of two M-files.

To search the online bug reports, start at the MathWorks home page, then click on Support, and then click on View and Report Bugs. From this page you can search the bug reports, look at bug reports for specific products, set up a watch list, and more. You can sign up to receive e-mail whenever a specific bug report is updated, or you can subscribe to RSS feed, customized to the list of products you are interested in.

There is also a "Frequently Asked Questions" page about bug reports that explains, for example, what an "OPEN" status means, or why some bugs aren't shown in the bug reports.

We are continually trying to improve the quality of our products and therefore reduce the need for published bug reports. In my area, there are fewer unfixed bugs in the development builds of the Image Processing Toolbox and the Mapping Toolbox than at any previous time in the history of these products. But any number of unfixed bugs is too many, and we're trying to do better for you.

Note: Most of the time, you should report product bugs directly to MathWorks technical support rather trying to post them as comments on this or other MATLAB Central blogs. My usual practice is to delete any comments that aren't directly relevant to the topic of the blog post. Joan's comment was relevant to the topic, so I let it through.

By Steve Eddins

13:26 UTC | Posted in Uncategorized | Permalink |

You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

Leave a Reply

Wrap code fragments inside <pre> tags, like this:

<pre class="code">
a = magic(3);
sum(a)
</pre>

If you have a "<" character in your code, either follow it with a space or replace it with "&lt;" (including the semicolon).

About

Steve Eddins manages the Image & Geospatial development team at The MathWorks and coauthored Digital Image Processing Using MATLAB. He writes here about image processing concepts, algorithm implementations, and MATLAB.

Subscribe


Recent Comments

  • Steve: Kezia—Try imrotate.
  • kezia: steve, how to perform rotation of structuring element by 15 degrees. kindly answer my question. thank u kezia...
  • Steve: Tasha—I only accept comments that are relevant to the particular blog post or are questions or comments...
  • Tasha: Steve,I send you a comment here but still didn’t get any reply yet.I did not see my comment posted here...
  • Steve: Carsten—Thanks for your input.
  • Carsten: Another vote for either imtranslate.m, or at least a blurb in the imtransform help why pure translation...
  • Loren Shure: If you look towards the end of the fftfilt program, you will see that there’s a check to see if...
  • Steve: Sonja—My imwritesize submission on the MATLAB Central File Exchange might be helpful. It was posted...
  • Steve: Grant—Sorry, but it won’t be for R2010a. That development deadline has already passed.
  • Sonja: My publisher is wanting images for a new book to be 300 dpi. Only 5 of the 19 images are 300, the rest are...

Blog Admin

These postings are the author's and don't necessarily represent the opinions of The MathWorks.