Jump to content

NLCbanner2024.jpg.2478be509670e60c2d6efd04834b8b47.jpg

dph1nm

Members
  • Posts

    2,053
  • Joined

  • Last visited

Posts posted by dph1nm

  1. Hmm - this seems to have stopped working for me with the latest W10 update. Happily had it working with Hildo's instructions in June, but no longer. The driver installs (apparently successfully) from the device manager as usual, but does not appear under sound & video controllers, and if I close and re-open the device manager it goes back to reporting  unknown device, no driver installed. Anyone else had this?

    NigelM

  2. 5 hours ago, Northernlight said:

    Hi All,

    I'm contemplating a SW quattro and i've been looking on Astrobin for samples images from both scopes and i noticed that there are hardly any images taken with the 12" and 95% seems to be with the 10" and i just wondered if there was any reason for this.

    I guess weight and general size would be the main factors, but wondered if there was anything else about the 12" that makes people favor the 10" instead. For me the slightly longer Focal length and larger aperture would be great and the pixel scale is pretty decent and based on OK seeing conditions then the larger scope is a better match for my qsi 683 ccd as at 1x & 2x both binning levels are a good match, whilst the 10" is great at 1x, but undersmaples at 2x

    So why is it there aren't more 12" quttro's appearing on Astrobin, as it seems like a no brainer to me if your mount can handle it

    Cheers.

    Rich.

    I highly recommend the 12", but mine is on an EQ8! Here are some DSLR images (I only take 45sec subs in very light polluted skies, so don't expect miracles from these!)

    http://community.dur.ac.uk/nigel.metcalfe/astro/photo_quattro.php

    I use the Skywatcher Aplanatic f/4 coma corrector.

    NigelM

  3. On 04/06/2020 at 16:49, davew said:

    I think the most qualified person on this site to answer your question could well be dph1nm . 

    I hope he sees this post.

    Dave.

    Err, well it took me a while to see it, and I am not sure I can help much. With my DSLR I usually point the telescope relatively near the zenith at dusk and wait until 0.5s exposures just saturate the back of the camera histogram (in blue of course, not green or red). Note that on my 1000D 'saturation' in the histogram is actually when the jpeg saturates - there is another two stops (4x) to play with in RAW. I usually aim for about 40 before I get bored (or it gets too dark).

    Professionally it is easy - you just look up a suitable 'blank' field and then ask the night assistant when to start observing or sneak a look at the logs to see when the previous observers did theirs)!!

    I have also used night flats professionally - they waste too much time amateur-wise given how little clear sky I get round here. If you targets are small and you dither (or you take lots of different fields) then they can work extremely well. Obviously they do not work well if you are imaging a large nebula!

    NigelM

    • Thanks 1
  4. Remember that if you are dominated by read noise, which this shot probably is, then lower ISO on a 450D is bad news - it just makes the signal-to-noise worse. The only real answer is to take multiple shots and stack them. If you do use a tracker then I would take a separate static shot for the foreground stuff (with the same total exposure as your tracked shots) and combine the two in software.

    NigelM

  5. 21 hours ago, Pompey Monkey said:

    They do indeed add a constant value to the image to avoid negative numbers. However, this is a constant and is called the pedestal. It is not the bias signal.

    When I started CCD imaging many,many years ago this is exactly what was done. An average value was calculated from the bias frames (or indeed the overscan region)  and subtracted from the lights and flats. We never subtracted bias frames to avoid adding noise. It worked perfectly well.

    NigelM

    • Like 1
  6. Both CMOS & CCD manufacturers tend to add a constant value to the image before it is read out, in order to avoid negative values. This needs to be subtracted (both from flats and lights) before flats will work correctly. Easiest way to find out what this value is is to take zero-length exposure (i.e. with no light getting in), known as the bias. For DSLR cameras the best approximation to 'zero-length' is to use the shortest shutter speeds available with the camera in the dark.

    You could use darks and flat-darks instead, as darks also have the bias signal added, so subtracting a dark gets rid of bias as well.

    NIgelM

     

  7. I happily re-use flats, even taken months previously. The only issue is if there are significant dust spots, but my Canon does sensor cleaning whenever you switch it on and off, and there are very rarely any visible dust spots. If there are they can be fixed in post-processing.                

    NigelM

    • Thanks 1
  8. On 25/11/2019 at 16:46, 8472 said:

    Large PE with a harmonic drive? That doesn't sound good.

    As I read it, the main  benefit of harmonic drives is zero backlash. They still have periodic error, and as with most  mounts it would seem that the more you pay the better it is.

    NigelM

    • Like 1
  9. On 22/11/2019 at 06:42, johneta said:

    I had ->Cosmetic Tab  -  Detect and Clean Remaining Hot pixels ticked and set to 1px and 50% threshold.

    This is because stars are essentially single pixels at this resolution - so DSS tends to think they are hot pixels! It is possible to get caught by this on shots at much longer focal length as well, if the seeing is good. I have had the central pixels of stars removed at 1200mm focal length! For this reason I am very wary of the cosmetic cleaning, but if you turn it off all together I find that some real hot pixels get through.

    NigelM

  10. On 20/11/2019 at 12:48, vlaiv said:

    If we are talking about signal and measurement, and if we have mathematical model that describes that process, why do you think it is not useful to think about it as if there were definite signal with definite photon rate, but it is the measurement that can't be done with absolute precision?

     

    Because this encourages people to think that it is their camera which is the cause of all the noise, and that by spending lots of money they will do better. In fact the signal from the source really does fluctuate and there is nothing you can do about this.

    NIgelM

  11. On 13/10/2019 at 13:27, vlaiv said:

    Here is an example of binned image vs unbinned image that clearly shows improvement in SNR:

    Sorry vlaiv, but this is misleading. Software binning does not change the S/N per sq arcsec on the sky, so the two halves of your images should look identical. It looks like you threw away 3/4 of the data when downsampling the unbinned shot.

    NigelM

×
×
  • 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.