Jump to content

Banner.jpg.b83b14cd4142fe10848741bb2a14c66b.jpg

The Lazy Astronomer

Members
  • Posts

    952
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by The Lazy Astronomer

  1. 25 minutes ago, TheThing said:

    Something that has always puzzled me and I've not found a clear answer to it as yet - How do you DSO imagers know how long to take exposures for?  I suppose I could just go through the pictures that are posted and make a table to correlate them, but is there a hard and fast rule or is it just luck?

    For example, say that I wanted to take some images of the Orion Nebula, how long should my exposures be and how many should I take?  Is it the same for the Pleiades and the Andromeda galaxy or do these differ?

    Thanks in advance,

    Puzzled of Epsom Spa  

    Generally, once you've determined an appropriate sub exposure length by the methods mentioned above, there is no need to adjust sub exposure time for different targets using the same equipment from the same location. The only real need to deviate from that would be on targets with a very high dynamic range of brightness (e.g. M42) - in this case, you may also shoot some short exposures specifically to capture the very brightest parts (these areas would most likely have been overexposed with a longer sub).

    29 minutes ago, wongataa said:

    As for how long to take exposures for, well as long as possible in general. Darker skies will require less exposure than brighter skies as faint details will be easier to capture.

    It should be clarified that this true for total exposure (integration) time, not individual sub exposures. Darker skies would require longer subs to facilitate the swamping of the read noise, but the desired signal to noise ratio would be achieved in less total integration time.

    • Like 2
  2. I recently downloaded a trail of noise exterminator (which I now completely love!), and went through a reprocess of my bubble image from last year, plus a couple of extras. These are crops from the same SHO stacks - I'll be working on the full image next, although I'm not very good at processing wider field shots, so that may never be finished!!

    Approx 12hrs, split equally between Ha, Oiii and Sii.

    Let me know your thoughts!

    Bubble:

    I always get comments on my magenta stars, but I feel they are appropriate in some images (i.e. hubble recreations) - their inclusion in this one is deliberate. 

    SHO_BubbleV2.png.ddffb0d13d70d866f17bf23ebcb47493.png

     

    NGC7538:

    SHO_NGC7538CropNXT.png.ae5364b71f79a2ea758bcdbbbf2a5521.png

     

    SH2-159:

    I liked the structures in this, but I don't think it stands up too well to zooming into it. I think because it's fainter the other two above, I've pushed it a little too hard.

    SH2_159Crop_SHO.png.446e59d67bff8379a3997344d9299278.png

    • Like 5
  3. This thread needs more images!! (and a bit less arguing)

    If anyone's got a few comparisons of their data with no decon vs blurx vs the best they could do with manual decon (and no other processing) I'd very much like to see it. 

    I don't necessarily mind doing deconvolution (it's somewhat cathartic, I think - playing around with the settings to try and get it right), but I never feel I've gotten the best out of it, purely due to lack of experience, so BlurX is a tempting prospect. 

    • Like 3
  4. I missed this one first time around too. It's an object l really like, and this is a nice rendition. It's on my list to do one day, but l did some test shots on it a while ago and discovered I'd need a 9 panel mosaic to capture the whole thing with my set up - far more of a ballache than I'm willing to undertake at moment!

  5. 13 hours ago, Priesters said:

     

    I suspect it is pinched optics as this is the first time I’ve used this scope (WO GT81) in such cold weather.   Only other change has been a new camera (Altair HyperCam 183C).  Is there anything I can do about pinched optics?

    A dew heater tight to the lens cell may help. There's probably also some adjustment that could be done, but it's not something I've ever done (or indeed would ever want to do, for fear of messing something up). 

    Wait to see what the stars are like on a less cold night - it may be that under more normal winter temperatures all is well again. If it's still bothering you after that, I'd look to have a professional sort it out, personally. 

  6. On 04/12/2022 at 09:43, wornish said:

    Looks like a serious piece of kit. But, at 33lbs (15KG) the head is just not practical for nightly setup and take down.

    If I ever get a permanent site then I would be very tempted.

    The head on this is actually lighter than the head of the EQ6-R, which is nightly setup/take down mount for many of us. Granted, the overall package would be heavier when you included tripod and counterweights though.

  7. The L-enhance is a narrowband filter, with a bandpass at Ha and another at Oiii & Hb. Narrowband images are false colour (although the HOO combination afforded by these dual/triband filters gives a relatively close approximation of true colour, with Ha mapped to red and Oiii mapped to green and blue), but the fact that most of the light spectrum is not recorded means photometric colour calibration won't give the optimum result.

    The heart is quite strong in Ha emission and Oiii is generally much weaker for all objects, so I would say a fairly strong red bias is to be expected.

  8. 1 hour ago, Icesheet said:

    starless + stars' in pixel math.

    That'll be the culprit l reckon. A good way I've found is use an unscreening and rescreening technique:

    1. Do all your normal processes up to star removal, then duplicate the image and run starnet (or starX, whatever you use) on one, but don't ask for it to make a stars only image.

    2. In pixelmath, do:

    ~((~original)/(~starless))

    This will give you your unscreened stars image

    3. Process your starless and the unscreened stars images however you desire, then rescreen the stars back in with pixelmath:

    ~((~starless)*(~stars))

    • Thanks 1
  9. It seems like we're in a HGTTG situation here - perhaps I need to start a thread on the right question to ask first 😁

    I'll try again: what are people's thoughts on which is the best planetary cam to buy these days? I think the 462mc was generally regarded as a good option previously, but are there any new thoughts on that given the new cameras that have been released in the past few months? 

    Find a way out of that, @vlaiv 🤣

    • Like 1
  10. 1 hour ago, Elp said:

    I think you need to do it if you're going to be changing targets or moving somewhere different in the sky. If you think about it, if you're pointing near the zenith the star field will hardly appear to move, if you point near the celestial equator the stars will appear to move a lot more. Unless the calibration accounts for this you'd have to recalibrate, or at least try adjusting the sidereal rate. To be safe I recalibrate every session on each target.

    As per the phd instructions (https://openphdguiding.org/man-dev/Basic_use.htm#Automatic_Calibration

    Because this is a measurement process that is subject to various kinds of mount and atmospheric effects, the most accurate results will be gotten when the scope is pointing within 20 degrees of Dec = 0 (near the celestial equator) and at least 60 degrees above the nearest east/west horizon (i.e. within 2 hours of the celestial meridian).  Calibrations can be done in other pointing positions if required by conditions at your site but they will be subject to somewhat more measurement uncertainty.  You cannot do calibrations pointing very close to the north or south celestial poles, and the mount must be tracking at the sidereal rate.

  11. Sorry, a bit of a thread hijack here, but I think it's relevant.

    @vlaiv Speaking of colour calibration, pixinsight has recently gained a new one: spectrphotometry-based colour calibration, which uses star spectra data and camera QE curves and filter transmissions to perform colour calibration. https://pixinsight.com/doc/docs/SPCC/SPCC.html

    What are your thoughts on this - is this essentially the approach you've been advocating for for ages, or is it still an imprecise method?

  12. You seem to be making the assumption you have a polar alignment problem, but phd is giving you the 3 possible causes and you've discarded the other 2. Personally, I would think PA is the least likely cause unless you've made some recent change to how or where you set up. Like others have said, we need the log to make any conclusions. 

    • Like 1
  13. I often see a Celestron's c9.25 touted as the sweet spot for planetary imaging, but slightly over your budget, and, assuming the equipment in your sig is up to date, a scope that big will lead you to run into issues with mount payload capacity, so I'd think you'd need a scope and mount package. 

    Coming in bang on your budget is the Celestron 8SE, and I think that would be my recommendation unless you say you already have another mount with a higher payload capacity. 

  14. On 24/11/2022 at 08:06, Andy56 said:

    To close this with feedback, the change I made to use Saturation Via Star-profile worked.

    I think the multi-star guiding is selected but it only selects one star.

    I'll experiment with this on the next clear night.

    Many thanks for your assistance.

    Andy

    Phd2 will only show the guiding cross on one star, but if it's using multi star guiding, it should show circles around 5 - 10ish other stars within the FOV

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