Search Results

It's notable that all the bad pixels seem to be located on the upper limits of width and height. Let's look at one of them: if ( i == 0 && j == width) Note the limit on j. Wouldn't setting j = width …

Look at the test conditions. Here's an example. else if (0<h<height-1) That form is fine in python but not in C. It needs to look like else if (0 < h && h < height - 1) Not sure this is the only …

I took a quick look at it and one thing jumped out at me. The limits for checking right and bottom sides have a problem. They're going off the edge of the array. Let's take one of them. You should …

The code is using the temp array to add the values of the surrounding pixels to blur the current pixels. This is a problem. Open and read the bmp.h file and look at the declaration of RGBTRIPLE. … Use that total to calculate the blur value, make sure it is 255 or less, and then store it in the temp array. …

Actually, it's only filtering the first row correctly. It took me a bit to find the root cause. First of all, it would have been a better practice to initialize the copy array to all zeros to start. …

If you click on the link in the check50 results, you can see more detailed results. Check50 is showing that the two tests, 3x3 and 4x4, are failing. If you look at the detailed results, you will see t …

Let's look at one case, line 130. The rest will follow. if ((w < width) && (h < height)) // edge case 5: S E { // record bottom right aveRed += image[h + 1][w + …

For starters, the loops never run. That's why the output looks like the original image. Look at the test conditions in the for loop: for (int i = 0; i < height && i > 0; i++) { for (int j = 0; j …

The code is calculating the blur values (correctly, I assume), but then it is storing the result back in the original image array immediately. …

The errors are the same issue. The 3rd parameter that the pixels() function takes is an array of RGBTRIPLEs. The problem is that the array that the code is trying to pass is declared as an array of …

wouldn't it be easier to check if i-1, j-1, i+1 or j+1 are within acceptable limits?

Not so in blur, but you knew that. The blur logic is broken. The way it's written, it won't use any values other than 0 and 1 for image array indexes. Perhaps you meant to use [i+k][j+l]???? …

To calculate the blur for any pixel, the code needs to use the original values from all the surrounding pixels. … This code is calculating blur and putting the calculated blur values back into the same image array. …

The way to get the values for the blur is to average the values from the surrounding pixels in the original image. So, what happens when you're updating the original image as you go??? …

Yes, it produces a blurred picture, just not correctly blurred. You should work with something simple, like a 3x3 bitmap and look at the actual input and output values to see what it does. Specificall …