It is very possible that the filter you used could do something for some components. In the end, lower resolution images do not contain higher frequencies, which also contribute to what components you are going to get. If the component weights (lambdas) in these images are small, there is also a good chance of errors.
I assume your component images are sorted by weight. If so, I will try to use another pre-downsampling filter and see if it gives different results (essentially, get low-resolution images in different ways). It is possible that components that come out differently have a lot of frequency content in the transition band of this filter. It appears that the images circled in red are almost perfect inversions of each other. Filters can cause such things.
If your images are not sorted by weight, I wonβt be surprised if the ones you circled have very little weight, and this might just be a computational error or something like that. In any case, we probably need a little more information about how you reduce the size, how to sort the images before displaying them. In addition, I would not expect all images to be very similar, because you essentially get rid of several frequency components. I am sure that this would have nothing to do with the fact that you are stretching images into vectors to calculate PCA, but try to stretch them in the other direction (instead of columns instead of columns or vice versa) Try this. If it changes the result, you might want to try to run the PCA a little differently, not sure how to do it.
source share