Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.



  • Content Count

  • Joined

  • Last visited

Community Reputation

103 Excellent

About rubecula

  • Rank
    Star Forming

Profile Information

  • Gender
  • Interests
    Astronomy, Lepidoptera
  • Location
    North Hampshire, UK
  1. I have a permenant set-up so the imaging train doesn't change. I have been using the same set of flats for the last 7 months and so far they seem ok. I take darks with the L filter but have flats for all 7 filters.
  2. brilliant, puts my recent efforts to shame
  3. I've never been that excited about NGC 7000 but your Hubble treatment really brings it to life, I'm going to have to give that a go whenever the skies clear,
  4. It might be "luminance only" but that's a lovely image. Did you take darks, flats and bias frames for the 10s exposures or just the 300s?
  5. As I don't have a dome rotator I can't leave things unattended but can confirm that Sequence Generator performs the flip without any intervention from me. In fact it seems to platesolve more rapidly than when first starting the imaging run.
  6. Wow vlaiv! What a wonderful and comprehensive answer. You've given me so much to do and think about. Thank you so much
  7. 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?
  8. 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,
  9. I think I'm getting to grips with CCD and particularly narrowband imaging. Below are my last couple of efforts. The Cocoon Nebula is a HaLRGB image using Olly's recipe for adding the Ha, 15% to Luminance and 85% to the red channel. The Elephant Trunk is a an SHO image. In both case the processing has done nothing for the star colours. Is there a way of protecting star colour during development or is the best way to remove them, stretch the image, and then put them back again. If removing them is the best way I can see that there are a couple of apps to help with that (e.g. Straton and StarNet++) but how do you put them back? Thanks Thanks
  10. Got out last night after nearly a fortnight's cloud cover. Set off to image the Wizard Nebula. I'll shorten what could be a long tale. The scope was out of focus - completely, nothing at all visible in either the imaging or guide cameras. After a lot of fiddling I re-calibrated the motor focuser after which it went to a random setting. I did a GoTo 21400 which was where the scope had previously been in focus - still out of focus. So I set it to go to 0. I expected it to count down from 21400 to 0 but instead it went upwards to 60,000 at which point the counter in SGP said 0. I don't know why but I thought if it thinks 60,000 is zero then instead of trying to go from 0 to 21400 I would try 60,000 to 38600 (60,000 - 21400) and lo and behold the scope was in focus. I've no idea what caused all this. Why it wasn't in focus as I had left it and why the focus setting was 38600 and not 21400. Anyone any ideas? Is this likely to happen again? Thanks
  11. Camera's on its way to Starlight Express. Fingers crossed!
  12. Alan, There are a few comments on-line concerning problems with the mini usb port so that maybe the problem. I'll approach SX tomorrow to see if they will take a look at it. Typical to have an issue when the nights are getting longer. Thanks for all your help with this I really appreciate it. Best wishes,
  13. I'm not sure what it's telling me but I've just plugged a cable into the other socket on the Lodestar (ST4?) to the USB hub and the PC made a sound.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.