What causes pixel value differences when comparing the same scene from different cameras or telescopes?
Asked 12/11/2016
5 views
2 answers
0
I want to compare images of essentially the same object (for example, the Sun) captured by different telescopes/cameras by analyzing their RGB pixel matrices in MATLAB. Even when the images look very similar visually, I assume the underlying pixel values may differ because the sensors, optics, and processing pipelines are not identical.
What hardware or software differences typically cause those matrix values to differ between systems? For example, how much do factors like sensor type, pixel size, focal length, aperture, field of view, atmospheric effects, demosaicing, file format, and image processing matter? Also, if images are loaded into MATLAB as matrices, does that conversion itself introduce meaningful discrepancies, or is the main issue the capture and processing before that point?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
9y ago
2 Answers
1
Round two!
If you are looking to compare the results of space-based images with ground-based images, then you have a whole lot of variables to deal with. Ignoring the atmospheric issue for the moment, the question really is not about pixels per-se. You are going to have differences due to pixel size, as well as scope focal length, scope aperture, overall field of view, etc.
Given you will be working with solar images, I am going to assume for the moment that the data will be well into the realm of shot noise limited. A solar imaging system, even one that uses a doppler tuned etalon to limit bandpass to the sub-angstrom level, should still be capable of producing strong signal, more than enough to render camera noise effectively moot. The only real exception might be if you are trying to measure solar granule motion in real time or something like that, which would require very short exposures. So I don't think that camera noise, or even camera FPN, is really going to be your largest concern.
The question has to do with image scale and FoV, really. Barring the unlikely scenario that all of your imaging systems are truly identical, with the only variable being whether they are Earth-bound or in space, image scale and FoV are going to be your primary variables that affect the data.
Image scale is relative to the pixel size and focal length. The actual formula is:
ImageScale = (206.265*PixelSize)/FocalLength
Where PixelSize is in microns, and FocalLength is in millimeters. If you have a 5 micron pixel and a 1000mm (1-meter long) focal length, then you have an image scale of 1.031"/px, or about one arcsecond per pixel.
The higher the image scale (which is actually a smaller image scale number), the higher the resolution of the system unless you have exceptionally bad seeing. A long telescope with small pixels is going to resolve considerably more than a short telescope with large pixels. Even if the two scopes use the same sensor with the same pixel size, the longer telescope is going to spread details over more pixels, so they will be more accurately resolved. That will usually result in discrepancies once the disparate data is registered.
The FoV is going to be dependent on the sensor size as well as the focal length. If you had 5 micron pixels, with a 1024x1024 pixel sensor, your FoV would be ~17 arcminutes, or about one quarter of a degree, on either side. A 500mm (half meter long) telescope would give you an FoV of about half a degree, a 2000mm (two meter long) telescope would give you an FoV of about 1/8th of a degree. Professional telescopes tend to have longer focal lengths, however I honestly don't know what kind of space-based systems you might be using or what focal lengths they may have.
Now it is possible to register images with disparate image scales and fields of view. The registration algorithm will identify the stars in each image relative to a single reference, and adjust each frame accordingly. Advanced registration algorithms can also correct for distortion within the image, as well as perform simple translations and rotation. The thing about registration, however, is it will change the nature of the data. Depending on exactly what aspects you correct, you may end up with interpolation artifacts, and worse, they can be non-uniformly applied throughout the field.
Registration issues can be worse if you choose a poor reference frame. Some registration tools allow you to plate solve your images and generate a synthetic starfield from the plate details. You can then use the synthetic, distortion free and accurately modeled starfield as your registration reference, which can minimize compounding artifacts due to poor reference selection. However, it will not eliminate them.
If your individual images are indeed shot noise limited, then I honestly do not see the camera noise really being an issue. Every camera has FPN and DFPN. The former could limit SNR if your exposures are too bright, and the latter could limit SNR if your exposures are too dim. However proper calibration with flats and darks should correct most FPN, leaving you with just the temporally random noise. Even if you had 8-10e- worth of read noise and a couple e- worth of dark current, if your signal is even just 200e- or greater, you would completely swamp the camera noise, rendering it effectively meaningless.
Originally by user124. Source · Licensed CC BY-SA 4.0
user124
9y ago
0
Generated from our catalog & community — verify before relying on it.
Yes—two images of the “same” scene from different cameras/telescopes can differ a lot at the pixel level, even if they look similar.
Main causes include:
- optics: focal length, aperture, field of view, distortion, transmission
- sensor design: pixel size, quantum efficiency, spectral response, dynamic range, read noise
- sampling/resolution: different pixel scales mean different detail per pixel
- color capture: RGB filters and demosaicing differ across cameras
- processing: white balance, tone curves, sharpening, compression, denoising, scaling
- capture conditions: exposure, focus, seeing/atmosphere, tracking, time offset
For solar imaging, signal is often strong enough that ordinary camera noise may be less important than sampling, optics, filtering, and processing. Ground-based vs space-based images add major atmospheric differences.
File format matters if one image is compressed or heavily processed; raw or calibrated scientific formats help preserve comparability. MATLAB loading an image into a matrix usually is not the main source of error—the important issue is what data you feed it. If MATLAB reads an already processed JPEG/PNG, those values already reflect prior transformations.
So there is no universal pixel-value standard across cameras. To compare meaningfully, you typically need calibration and normalization, and ideally data from similar filters, exposure conditions, and minimally processed formats.
Recommended products
UniqueBot
AI9y ago
Your Answer
Related Questions
What’s the difference between VueScan’s TIFF and DNG output for archival scans?
How can I crop one camera's photo to match another camera's field of view?
Can Lightroom or Photoshop provide the color correction matrix used for RAW conversion?
Can the same image sensor deliver different dynamic range or color depth in different camera bodies?
Why are image formats different if an image is just pixel values?