MichaelBibby

I live under bortle 2-3 skies and I am often surprised by how well DSO images turn out with a bright moon. I would recommend doing your own comparison on the same target, one taken during the new moon and the other during the near full moon so you have a much better idea how much of a compromise it is for you under your skies with your equipment and using your methods of post processing.

I asked it: Me: "give me the scientific definition of 'average' and 'good' seeing conditions." Bard: "Average seeing conditions are characterized by atmospheric turbulence that causes the image of a star to blur to a diameter of about 1 arcsecond. This is equivalent to the resolution of the human eye. Under average seeing conditions, it is possible to resolve double stars that are separated by about 1 arcsecond, and to see the details of larger astronomical objects, such as planets and galaxies. Good seeing conditions are characterized by atmospheric turbulence that causes the image of a star to blur to a diameter of about 0.5 arcseconds or less. This is better than the resolution of the human eye. Under good seeing conditions, it is possible to resolve double stars that are separated by about 0.5 arcseconds, and to see finer details of astronomical objects. The following table shows a more detailed classification of seeing conditions: Seeing condition Image blur (diameter) Poor 2 arcseconds or more Fair 1-2 arcseconds Average 1 arcsecond Good 0.5-1 arcsecond Excellent 0.25-0.5 arcseconds Exceptional 0.25 arcseconds or less drive_spreadsheetExport to Sheets Seeing conditions can vary depending on the location, the time of day, and the weather. The best seeing conditions are typically found at high altitudes, in dry climates, and during clear nights. Astronomers use a variety of techniques to improve the resolution of their images under average and good seeing conditions. These techniques include: Adaptive optics: This technology uses a deformable mirror to correct for the effects of atmospheric turbulence. Lucky imaging: This technique combines many short exposures of an object to select the best images that are not affected by atmospheric turbulence. Stacking: This technique combines multiple images of an object to reduce noise and improve the signal-to-noise ratio. By using these techniques, astronomers can obtain high-resolution images of astronomical objects even under average and good seeing conditions." tuneshare more_vert

While playing with Microscofts generative 'A.I.' model called 'Bard' I thought I would test it with this question and see what it came up with: Me: "if I were to compare images taken through each of those telescopes using a camera with a pixel size of 2.9um, and was guiding at a total error of 0.5 arc seconds, would I notice the difference in resolution under 'average' to 'good' seeing conditions?" Bard: "Yes, you would likely notice the difference in resolution between images taken through a 150mm Newtonian telescope and a 200mm Newtonian telescope, using a camera with a pixel size of 2.9um and guiding at a total error of 0.5 arc seconds, under average to good seeing conditions. The 150mm telescope has a theoretical resolution of 0.8 arcseconds, while the 200mm telescope has a theoretical resolution of 0.6 arcseconds. This means that the 200mm telescope can resolve finer details. The pixel size of the camera is 2.9um, which corresponds to a sampling rate of 0.12 arcseconds per pixel. This means that the camera is capable of sampling the images from both telescopes at a high enough rate to capture the difference in resolution. The guiding error of 0.5 arc seconds is relatively small, so it will not significantly degrade the resolution of the images. Under average to good seeing conditions, the atmosphere will typically introduce a blurring of about 1 arcsecond. This means that the effective resolution of both telescopes will be limited to about 1 arcsecond. However, the 200mm telescope will still be able to resolve finer details than the 150mm telescope, even under average to good seeing conditions. In conclusion, you would likely notice the difference in resolution between images taken through a 150mm Newtonian telescope and a 200mm Newtonian telescope, using a camera with a pixel size of 2.9um and guiding at a total error of 0.5 arc seconds, under average to good seeing conditions. Here is a table that summarizes the expected resolution of the two telescopes under different seeing conditions (Please note that these are just estimates. The actual resolution of the images will depend on a number of factors, including the quality of the optics, the observing conditions, and the processing of the images.): Seeing Expected resolution of 150mm telescope Expected resolution of 200mm telescope 1 arcsecond 0.9 arcseconds 1.1 arcseconds 0.5 arcseconds 0.8 arcseconds 0.9 arcseconds

I would HIGHLY recommend rotating the scope so that the focuser, and guidescope, is facing DOWN, and I would remove the finderscope too. Doing that should really help improve the guiding performance. You want to get as much weight closer to the axis of the mount to reduce the 'moment arm'.

As I understand it, there is also the effect of improved 'contrast' with the wider aperture, which in and of itself can have the effect of making an image look 'sharper'?

Sorry John, deep sky objects, not planetary.

Thanks everyone. I understand that in a vacuum angular resolution is a function of aperture and wavelength, and although I understand the supervening atmosphere imposes limitations beyond those of the wave nature of light itself, am still getting my head around the relevant maths. I was looking at buying an 8" F4 but it looks like a cheap but good as new 8" F5 has landed in my lap, which I will be using with a Nexus CC that will bring it down to F3.75 at 750mm, so I should be able to make some direct comparisons, under varying conditions, with my 6" F5 which is also 750mm. I'll post some comparison images in the coming months so that hopefully others can learn along with me (targets like m42 and the Horsehead nebula are rising on the East coast of Australia), but obviously the biggest confounding variables I'll have to find ways to mitigate or at least record is seeing conditions and integration time with different focal ratios.

To be clear, the question is: what kind of gains, in terms of resolution, can you reasonably expect from increasing aperture at these focal lengths?

An F5 6" Newtonian has a focal length of 750mm, and a F5 8" Newt with a 0.75x reducer (Starizona Nexus) also has a focal length of 750mm (i.e., at F3.75). My question is quite simply: will the increase in resolution going from the 6" at 750mm to 8" at 750mm be noticeable? Obviously there are some variables to consider, like the pixel size of the camera and the seeing conditions. In my case I am using the 585 sensor with a pixel size of 2.9um which will be oversampled at 750mm. Will the difference in resolution only be noticeable in the very best seeing conditions, or would it be noticeable in average seeing conditions? Another use case would be going from 6" F5 Newt with 0.75x reducer (about 585mm) vs a 8" F4 with 0.75x reducer (about 600mm). Obviously we would be comparing an F5 scope vs an F3 scope at the same focal length, but again the question arises: will the greater theoretical resolving power of the 8" be noticeable in real world conditions? Any guidance here would be helpful (and what would be super helpful is a direct comparison of two different images taken under comparable conditions).

Hi all, quick question: when I bought the Uranus-C 585 about a year ago the HCG switch point was 180 (confirmed by sensor analysis in Sharpcap) but now I see they have changed the specs on this camera to make the HCG 210. My question is: can I update the driver to change the HCG to the new value? (The latest camera driver was released about a month ago.) While I'm here I may as well share my latest image: This is the raw Sharpcap livestack image of the Lagoon nebula in Sagittarius made up of only 48 x 1 minute subs (gain was 250 in Bortal 2.5 skies) on an 6" F5 Newtonian (no post processing, slight crop in from the edges):

Thanks for the technical corrections, because it doesn't do anyone any good to be clumsy and imprecise with a technical language, every use of it should be a practice of it's precision, especially on forums were people augment so much of their knowledge (learning both good and bad habits).

Great image. Nexus .75x brings an F5 down to F3.75, 1.78x the amount of light per unit of time, great upgrade (you can almost halve your exposure times for the same gain settings). I do still see a bit of coma on the edges of your image, did you get exactly 55mm of back spacing?

Sorry to derail the thread, but can anyone tell me if this adapter (which allows you to screw a 1.25" filter into m42 thread on the ZWO camera body, but so that the camera can still be connected to an m42 imaging train) work for the player one camera's (specifically Uranus-C)? Any guidence here appreciated. I have an existing 1.25" uv ir cut filter and am looking for a way to connect it to my imaging train with a Starizona Nexus CC/reducer. I understand that if the filter is added after the coma corrector then the back spacing will have to be increased by about 1mm (to 56mm) to compensate for the change in focal length caused by the filter in the light path. UPDATE: Looking at the thread on the camera body, there isn't enough room to fit both an adapter for the filter and another m42 extension so it looks like this adapter won't work. https://www.testar.com.au/products/zwo-t2-1-25-filter-adapter?variant=38122570547392&utm_source=google&utm_medium=organic&utm_campaign=Google Shopping feed app&utm_content=ZWO T2 1.25" FILTER ADAPTER&utm_campaign=gs-2019-12-27&utm_source=google&utm_medium=smart_campaign&gclid=Cj0KCQiA8t2eBhDeARIsAAVEga1Nxrpms_1oa77naDzWPryX8W3HAqUoj1kPddcKIECSVOKETMOG0RIaAlJJEALw_wcB

Thanks, I'll have a play with it. The reason I want to get parallax information is to add the depth dimension to my images, just to explore them in more detail and get a better sense of what I am looking at.

I know that Pix Insight has a plugin or script called 'Image Annotation' that can be used to indicate the magnitude and parallax (i.e., 'distance') of each star in an image using the GAIA survey data. I don't have PI, is there any other way of getting this functionality? And while I'm here, can someone recommend a (free) program to 'blink' through my FITS (to look for satellite trails, meteors, asteroids, etc.)?