Hi everyone,
now, with some more or less experience, a new mount that allows longer exposures and guiding, I did another sensor analysis for my Neptune-C and ASI120MC-s.
I'm struggling with interpreting the results, especially for the Player One Neptune-C (IMX178c).
It would be great, if someone could take a look on the results and give my some guidance.
I'm familiar with gain, exp, offset settings, noise ratio etc. etc. as well as the use of calibration frames.
Thx in advance
Gottfried
ASI120MC-s
Neptune-C
...interpret sensor analysis results
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
...interpret sensor analysis results
TS Photoline 60/360, TS Photon 150/750 Advanced Newton, Bresser 90/500 & MC 127/1900, ZWO ASI120MC-s, Player One Neptune-C, Altair Hypercam 294C Pro, SVBONY SV165 Guidescope, iOptron Cube Pro & CEM25P, Bortle 4, Germany-northwest region
- admin
- Site Admin
- Posts: 17492
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: ...interpret sensor analysis results
Hi,
there look to be a couple of glitches, potentially the value of read noise for gain 20 on the ZWO and the rise in read noise at the far right on the Neptune-C, but those do not really affect the key features of the analysis.
The key things to take away are
* The NeptuneC is a 14 bit sensor compared to 12 bit for the 120MC
* The full well depth of both sensors is roughly the same - that is they will both saturate with roughly the same number of electrons captured
* The read noise of the NeptuneC is about 1/3 of the 120MC - this is important as it means that if you want to use the camera for deep sky, the Nepture needs exposures that are 9 times shorter than the 120MC
Overall, the improvements in the Neptune are really just the result of about a decade of sensor improvements, since the 120MC uses the Aptina AR0130 sensor that is well over 10 years old now.
cheers,
Robin
there look to be a couple of glitches, potentially the value of read noise for gain 20 on the ZWO and the rise in read noise at the far right on the Neptune-C, but those do not really affect the key features of the analysis.
The key things to take away are
* The NeptuneC is a 14 bit sensor compared to 12 bit for the 120MC
* The full well depth of both sensors is roughly the same - that is they will both saturate with roughly the same number of electrons captured
* The read noise of the NeptuneC is about 1/3 of the 120MC - this is important as it means that if you want to use the camera for deep sky, the Nepture needs exposures that are 9 times shorter than the 120MC
Overall, the improvements in the Neptune are really just the result of about a decade of sensor improvements, since the 120MC uses the Aptina AR0130 sensor that is well over 10 years old now.
cheers,
Robin
Re: ...interpret sensor analysis results
Thanks a lot for your help Robin,
I've tried different values for the Neptune-C and could achieve some (at least for me) good results.
Yesterday, I worked with Exp 120s, Gain 180 and Offset 250 with my TS Photoline 60/360.
47 selected frames stacked with DSS and processed with SIRIL and Astrosurface.
Testobject: NGC 3938, very faint and far far away (at least for this setup)
Bortle 4, FWHM around 4 and unfortunately interrupted by clouds.
Another one, the Monkeyhead nebula NGC2174, with the same settings. This one, the 16bit Fits summary of the Liveaddition, processed with SIRIL and Astrosurface. 57 frames.
Btw. it was the first time, I used Dither. Is there a way to prevent the short exposure frames to get stored ?
Gottfried
I've tried different values for the Neptune-C and could achieve some (at least for me) good results.
Yesterday, I worked with Exp 120s, Gain 180 and Offset 250 with my TS Photoline 60/360.
47 selected frames stacked with DSS and processed with SIRIL and Astrosurface.
Testobject: NGC 3938, very faint and far far away (at least for this setup)
Bortle 4, FWHM around 4 and unfortunately interrupted by clouds.
Another one, the Monkeyhead nebula NGC2174, with the same settings. This one, the 16bit Fits summary of the Liveaddition, processed with SIRIL and Astrosurface. 57 frames.
Btw. it was the first time, I used Dither. Is there a way to prevent the short exposure frames to get stored ?
Gottfried
TS Photoline 60/360, TS Photon 150/750 Advanced Newton, Bresser 90/500 & MC 127/1900, ZWO ASI120MC-s, Player One Neptune-C, Altair Hypercam 294C Pro, SVBONY SV165 Guidescope, iOptron Cube Pro & CEM25P, Bortle 4, Germany-northwest region
- admin
- Site Admin
- Posts: 17492
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: ...interpret sensor analysis results
Hi Gottfried,
excellent images - glad that things are starting to work well for you
In Live Stacking, there is an option to set which raw frames are saved which lets you choose to ignore the short frames during dithering. For saving raw frames you can choose to save
* None
* All
* Those added to the stack or
* All except when paused/dithering
See https://docs.sharpcap.co.uk/4.0/#Controls%20Group for more info.
cheers,
Robin
excellent images - glad that things are starting to work well for you
In Live Stacking, there is an option to set which raw frames are saved which lets you choose to ignore the short frames during dithering. For saving raw frames you can choose to save
* None
* All
* Those added to the stack or
* All except when paused/dithering
See https://docs.sharpcap.co.uk/4.0/#Controls%20Group for more info.
cheers,
Robin