Jupiter Cloud Sequence from Cassini

  • Released Monday, September 21, 2009

When the Cassini mission flew by the planet Jupiter in late 2000, a sequence of full disk images were taken of the planet. Assembled with proper spatial and temporal registration, the sequence could produce fourteen distinct images suitable for wrapping around a sphere.

But the time steps between images were large and exhibited significant jumping. The solution was to create additional images between the existing set by interpolation. But simple interpolation would not work due to significant changes between the images.

To solve this, we interpolated between the images using the velocity vector field of the cloud images. The velocity vector field was computed by performing a 2-dimensional cross-correlation (Wikipedia: Cross-correlation) between the images. This velocity field was checked against Jupiter velocity profiles from the scientific literature and agreement was excellent. With the addition of a simple vortex flow at the location of the Great Red Spot, the interpolation process was used to generate intermediate images, increasing the total number of images from 14 to 220 and resulting in a smoother animation. The elapsed time between each interpolated frame corresponds to about 1 hour. More info on the image sequence is available at Jupiter Mosaics and Movies - Rings, Satellites, Atmosphere

IMPORTANT NOTE: These images are for visualization purposes only. They are not suitable for scientific analysis.


Please give credit for this item to:
NASA/Goddard Space Flight Center Scientific Visualization Studio, the Cassini Imaging Team, CICLOPS, and Cosmos Studios. Special thanks to Andrew Ingersoll (CalTech) for technical assistance.

Release date

This page was originally published on Monday, September 21, 2009.
This page was last updated on Wednesday, May 3, 2023 at 1:54 PM EDT.


This visualization can be found in the following series:

Datasets used in this visualization

Note: While we identify the data sets used in these visualizations, we do not store any further details, nor the data sets themselves on our site.