Contains:  Solar system body or event
Jupiter from my spaceship (9 July 2018), Rod Kennedy

Jupiter from my spaceship (9 July 2018)

Acquisition type: Lucky imaging

Equipment

Loading...

Acquisition details

Loading...

Description

This is 21.5 minutes of Jupiter in the red channel that I captured last year on 9 July 2018. The raw data has been sitting in a drawer piled with 2TB and 4TB hard drives full of Jupiter and Saturn captures from last year. Now during idle time when DSO imaging I processes my accumulated planetary data.

In the capture the Great Red Spot is rotating off the limb to the right. (The true rotation is left to right, the pause is at the end). North is up. Some clouds appear to be floating above others as the planet rotates. The approach is to attempt a natural realistic photographic quality and taking it very easy on wavelet processing. I try to be consistent, systematic and minimalistic in processing.

Many thanks for the great Astrobin community and those titans who labored hard to generate the indispensable software.

Technobabble (Original Version)

Strictly this was not lucky imaging because I used every frame. As it was, the amount of processing time and effort was huge. Stacking was just straight averaging using WinJUPOS "derotation of video streams" applied to a 5 minute sliding (rectangular) video window generated from PIPP. The sliding window shifts by 30 seconds to generate each output frame. Because of Jupiter's fast rotation one can see rotation even after 20 seconds(†). Note that two parts of the final video more than 10 minutes apart are completely independent, which is a form of cross-validation. There is no global Jupiter map done here, just sequential local (sliding) processing, which is at the mercy of the consistency of the seeing conditions. Doing "unlucky" imaging gives softer results but more dynamic range (realism).

Technobabble (Final Version)

This version I used PIPP to keep 80% of the frames for each output movie frame, which helped bring out more detail (discarded junk frames). The original just used a straight average and light wavelet processing.

Scope=LX200GPS
Camera=ZWO ASI183MM Pro
Filter=R
Diameter=40.44"
Magnitude=-2.25
CMI=151.6° CMII=359.7° CMIII=240.6° (during mid of capture)
FocalLength=6050mm (F/23)
Resolution=0.08"
Date=090718
Start(UT)=083203.763
Mid(UT)=083933.772
End(UT)=084703.781

(†) The interval 20 seconds is at the low end of recommended integration times of 30-120 seconds with 60 seconds integration being a common recommendation when imaging Jupiter. However, some of this overestimation of integration time is due to the dependence on Autostakkert which, because of the way it does spatially localized processing, can alleviate the blurring due to limited amounts of rotation (even for up to 180 seconds integration). For this type of movie result Autostakkert is not recommended (because it would cause local spatial anomalies between adjacent frames) and even lucky imaging is not strictly recommended (because it would cause local temporal anomalies between adjacent frames). Well, in my view anyway.

Comments

Revisions

    Jupiter from my spaceship (9 July 2018), Rod Kennedy
    Original
  • Final
    Jupiter from my spaceship (9 July 2018), Rod Kennedy
    E

E

Description: Longer duration and discarding 20% of frames, more contrast and more detail.

Uploaded: ...