Jump to content

NLCbanner2024.jpg.2478be509670e60c2d6efd04834b8b47.jpg

image with noise and sensor grid?


rubecula

Recommended Posts

About 2/3 weeks ago I got a set of Ha images of the Wizard - all were ok and they stacked and stretched with no issues.  The other night during an unexpected clear spell I managed to get 24 x 600sec OIII images.  A jpeg of the stacked and stretched images is below.  Except for the top corners it shows an unacceptable amount of noise and there is a feint grid visible.  Is this from the sensor?  An extreme stretch of the Ha data didn't show the grid.  I thought it might be condensation but on both occasions I was using a dew shield and the dew heaters were on.

The only thing that changed is that there was a Windows update between sessions.  The Atik 383L+ camera and the filter wheel wouldn't connect so I re-installed the driver and everything connected OK.  I've experienced that before and had to re-install just the Atik driver after a Windows update. But in previous cases the resulting images have been fine.

Anyway does anyone have any idea as to what is causing the noise and feint grid at the bottom in the OIII?

Thanks,

1131557397_NGC7380WizardNebulaOIIIstretched2.thumb.jpg.b370f38da3b221423c6ea2c1f2f388a8.jpg

Edited by rubecula
Link to comment
Share on other sites

Yeah it is out of focus.  The numbers in SGP looked ok so I thought I'd play with the image as I had nothing else to work on :-).

The "grid" is definitely there particularly in the bottom third of the image and the horizontals stand out a bit more.

If the grid is from the sensor, and I'm not sure either way, then I wouldn't have thought being out of focus would cause the grid and excessive noise.  But what do I know?

Link to comment
Share on other sites

Not sure if it has something to do with Windows update.

First let address issue of noise everywhere but top part of the image. Noise that you are seeing is background noise consisting out of read noise, dark current noise (all across the frame) and LP noise. LP signal often has gradient to it because sky is not uniformly lit up by ground light sources - closer to horizon there is more LP and near the zenith there is less - that creates gradient.

You can see that there is gradient running from top of the image down to bottom - that is most likely LP gradient. Your level of stretch is such that it managed to push top part of the image (or rather it's background) - to be dark enough so that noise does not stand out as much while bottom of the image is still bright enough for noise to show.

Try removing gradient first and doing less aggressive histogram stretch so that background noise is better controlled.

Now let's look at pattern in the image. My guess is that it is not related to the sensor at all, and it is due to noise visible and another effect. You are probably guiding but your polar alignment is not spot on. This creates slight rotation between subs. Slight rotation between subs can happen if you have cone / orthogonality error - once you flip meridian frame will be slightly rotated. If frames gradually change rotation - it's due to PA. If one side of pier has one orientation, and other side of pier after meridian flip is slightly rotated - it is due to cone / orthogonality error (I'm not expert in that field, still don't know why exactly it happens, but I know it does sometimes).

Now let's see what that has to do with grid pattern? When you start stacking your images - subs need to be aligned, so some of them need to be "rotated back" to match reference frame. Software uses certain interpolating algorithm to do this, and choice of algorithm can impact creation of the grid pattern. Particularly bilinear resampling can cause that. Here is synthetic example done on just pure noise and stretched to show grid forming:

image.png.89ce81e02bc1dcb07a1642d02d43f344.png

This is pure gaussian noise (otherwise no pattern is visible), rotated by 1 degree using bilinear resampling method, and stretched to show grid clearly. Depending on rotation angle, grid will be coarser or finer.

That is what I believe is going on, but might be wrong. If you want to lessen this effect- use bicubic resampling or some more advanced resampling technique (lanczos for example is excellent).

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.