[X] My Assistant

[elakdawalla]

New images released!

And raw images at various processing levels from PJ1 are now in the JunoCam gallery.

[Gerald]

Yes, there is quite a lot in the images waiting for being squeezed out.

Derived from image #06166, an idea of a flyover, each frame rendered directly from the raw:
 JNCE_2016240_00C06166_V01_raw.bmp_30px_234.5_69500.0_80.84_cx700.0_0_133frames_1140x935.avi ( 764.89K ) Number of downloads: 773

According to the JunoCam paper,

when stereo is available we will encourage the making of visualization products like flyovers.

So the above example shows only the feasability without modeling the cloud topography.

I've too large inconsistencies at the moment to seriously try stereo imaging or methane band analysis.
Via spy.exe I don't get an x-position for the Sun or Earth in the JunoCam frame. So I'm using Jupiter and Jupiter_Barycenter in J2000 and Juno_JunoCam to infer a transformation matrix between a fixed JunoCam pointing and J2000; this provides a transformation from the J2000 trajectory data to my chosen JunoCam frame.
But Jupiter and Jupiter_Barycenter are almost identical, so I might have run into some numerical instability, since the resulting base of the vector space is almost singular.
Another cause for the inconsistencies may be the simplistic spherical model for Jupiter, which is waiting to be replaced by a spheroid.
The third possible cause is, that I'm using preliminary SPICE trajectory data.
To accomodate for the inconsistency, I need to choose the x-value of optical center of the camera dependent of the image, in the above case at x=700, which results in some noticeable rgb misalignment.
I'll begin with reducing my own obvious inaccuracies, and if this doesn't resolve the inconsistencies, I'll check the data sources.

[mcaplinger]

Via spy.exe I don't get an x-position for the Sun or Earth in the JunoCam frame.

I have to confess I'm not sure what you're trying to accomplish here, but if you're not getting a result, it means that you don't have all of the needed kernel files loaded or they don't cover the time range of interest.