Jump to content

Banner.jpg.b89429c566825f6ab32bcafbada449c9.jpg

Adam1234

Members
  • Posts

    835
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Adam1234

  1. Jupiter, GRS and Calisto. 29 Sept 2022. Southampton, UK (50 45 North). 

    200mm RC8" f/8, 2x barlow, ZWO ADC, ZWO ASI120mc-s, EQ6-R Pro. 3200mm focal length. 

    10 x 60s videos at 84fps, gain 100%, exposure 11.88ms. Each video stacked, sharpened and de-rotated, with final bit of sharpening. Firecapture, PIPP, AS3, Winjupos. Total 11430 out of 49283 frames stacked. 

    image.jpeg.8633d0f333a8c366bdddffc750512787.jpeg

     

    • Like 4
  2.  

    Jupiter and its moon Calisto, imaged on 29 Sept 2022.   10 videos of 60s at 84fps, gain 100%, exposure 11.88ms. Each video stacked, sharpened and de-rotated, with final bit of sharpening.  Total 11430 out of 49283 frames stacked. Stella Lyra 200mm RC8, 2x barlow, ASI120mc, ZWO ADC. PIPP, Autostakkert 3, Registax 6, Winjupos.

     

    image.jpeg.0595f6e209c55a94d1c07cbbb6d07496.jpeg

     

    I did take a set of videos of Saturn and another set of Jupiter with reduced ROI and faster fps, but I had to abandon these - unfortunately, I realised just after I finished Saturn that my secondary mirror had dewed up 😩. I continued to video Jupiter anyway despite the dewed up secondary as the live feed looked ok, but the Saturn set and one of the Jupiter sets looked absolutely horrible! But I wasn't surprised, I was more probably more surprised that this one came out ok!

     

     

    • Like 6
  3. 5 hours ago, CraigT82 said:

    Nice shots! Jupiter looks good with some nice sharp detail but the Saturn might be a touch out of focus? It’s tough to get focus when they’re low down in the murk. Might just be fuzziness due to the relatively long exposures.  Don’t worry too much about the histogram it can be really quite low and dim raw frame and still result in a nice bright final image after processing. Faster exposures are more important and that will also lead to faster frame rates.
     

     

    Thanks! Yeah Saturn I definitely think was slightly out of focus, it was tough without an autofocuser (can anyone recommend an motorised focuser for Stella Lyra scopes?), I was going backward and forward manually for ages and just settled on what looked OK since I couldn't see much detail

  4. My first ones of Jupiter and Saturn this year, also the first using my Ritchey Chretien 8" f/8.  Taken with ZWO ASI120mc-s, 2x barlow, ZWO ADC, EQ6-R Pro. I've since discovered that RC's are a less than optimal instrument for planetary imaging. 

    Jupiter: 31 x 45s videos, av.95fps, exposure 5.9ms, gain 100%. Total frames stacked 27329 out of 130840.

    Saturn: 4 x 120s videos, av.30fps, exposure 30ms, gain 100%. Total frames 920 stacked out of 14122. Saturn could have been better but I had to discard a load of bad quality videos because of cloud. 

    Each video stacked, sharpened, derotated and further sharpened. Firecapture, PIPP, AS3, Winjupos.

    One thing I struggled with during capture was getting a decent histogram, especially with Saturn. I could barely get it above 30% even with gain at 100%, so had to cope with 30ms and less than optimal fps. I guess probably because the 8" is smaller than my 10" dob, plus the large central obstruction on the RC.

    Jupiter_180922.jpg.9b11fc6e4c8fb8afa7c80d3783f8d488.jpg

     

    Saturn_180922.jpg.b5302060b4589d202ae5df4c4f08987b.jpg

     

    • Like 6
  5. 4 hours ago, vlaiv said:

    It is fairly simple calculation really - trick is to just imagine single point on Jupiter's equator.

    440000Km is circumference and Jupiter makes one revolution in ~10 hours, so any point on equator will travel at 440000Km / 10h so we get 12.22Km/s when we do the math.

    From our perspective in one second - that point will move 12.22km - imagine tangent to Jupiter's equator. When diameter is large compared to motion - it is like point is moving perpendicular to us.

    Here is little diagram (not to scale because of distances and sizes involved):

    image.png.06c5b3fb6f0c893d21833fc768c0149f.png

    Arrow is how much point will move in one second. This is correct only if movement is very small compared to diameter / circumference - otherwise curving needs to be taken into account - but 12Km is very small compared to size of Jupiter so distance along straight line and along surface are almost the same.

    It is then just simple trigonometry: tan(angle) = 12.222...Km / distance to Jupiter => angle = arctan(12.222.. / 591,000,000)

    (just remember to convert to degrees if your calculator is using radians - standard for trig functions is radians if not otherwise indicated)

    By the way - if you search google for "arctan(12.22 / 591,000,000)" it will give you right answer in radians :D  - and even better do search for arc seconds :

    image.png.5a9652c95e042d2dcfb688147bac6bb5.png

    That is just brilliant :D

    By the way - all the numbers come from google - I searched for circumference of Jupiter, rotation speed and current distance to earth (and I rounded results)

    Perfect, thanks!

  6. Not sure where exactly the focus point on the 200p is, but I've got the 250p flextube and the focus point when using a camera is very close to the draw tube, to the point where I had to screw directly and even then was only just about to achieve focus.

    Using a barlow definitely helped to bring the focus point further out, so I'd recommend using a barlow

    • Thanks 1
  7. 29 minutes ago, neil phillips said:

    Hi Adam, yes, its wrong its hyper rotated. North on that image is sitting directly above the south equatorial belt. so, it should be reversed. Next time you catch Jupiter it would likely help if you captured the planet fairly straight. Makes life easier to see if nothing else. Also try dropping the LD value to 50 for that bright limb on the right. 

    Great, thanks, weird how the automatic detection is getting it wrong!

  8. I've just done an experiment where I inputted my longitude as both -001 25, and +001 25, and in both cases the de-rotated images are coming out blurred, whereas my first attempt didn't.

    I think I now know why - I think the automatic detection is getting north the wrong way. I'm sure I remember on my first attempt that it was putting north on the other side. I'm not sure why it would be getting this wrong now though? 

    Is anyone able to confirm that the automatic detection is indeed wrong, and perhaps why?

    In the meantime, I will give it another go and rotate the outline by 180 to see if it works.

     

    image.thumb.png.4eba3d61cfac7fa277b2ecb6d3cb24a4.png

     

    the resulting blurry derotated image

    53256298_2022-09-18-2354_5-2022-Jupiter_positivelongitude.jpg.ec47cff91ed55909276497749bcac4aa.jpg

     

    My first attempt, which worked ok, except for the bright limb on the right hand side

    Jupiter_180922_version1.jpg.781de14fc19eb145e92445366f974740.jpg

     

     

  9. 10 minutes ago, CraigT82 said:

    West of meridian is minus, east positive.

    Cool that's what I thought. Oddly, when I put my long. As +001 25, my image came out OK, but with a bright ring on the limb, but when I used -001 25 it came out blurred.

    I was playing around with manual alignment of the outline rather than automatic, to try and get more accurate alignment so maybe the blurring was just an unsuccessful attempt at manual alignment. I'll try again tomorrow

  10. Just trying to get the best out of winjupos for derotating some stacked images of Jupiter from last weekend and I have a question on the latitude and longitude coordinates. 

    If my coordinates are 50°54'N and 1°25'W, would I enter +001 25 or -001 25 for longitude?

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