[X] My Assistant

[elakdawalla]

New images released!

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

[Gerald]

Sorry for a short interruption of the JunoCam image processing, but
-- when googling for Juno, I come repeatedly across references to and citations of the recent press release of PJ1 stating

The download of six megabytes of data collected during the six-hour transit, from above Jupiter’s north pole to below its south pole, took one-and-a-half days.

With a data rate of 119.56 kb/s,

this sounds like an understatement by at least two orders of magnitude,
since 119.56 kb/s x 36 x 3600s = 15.4e6 kb = 1.9e6 kB = 1.9 GB >> 4 MB.
If the data have been compressed, and only occasional error corrections have become necessary, the decompressed data should have been closer to 4 GB.

---

Regarding the winds, we have now the opportunity to verify or adjust the models of the polar wind systems. I'd think, that within vortices wind velocities can be much higher than mean regional or global winds. I'm curious, what we can find out. A pixel isn't necessarily the accuracy limit for displacement measurements. It depends much on the actual structure of the respective clouds.

[mcaplinger]

this sounds like an understatement by at least two orders of magnitude,

I didn't write this part of the press release so I can't say what was intended, but a few points:

1) Not all passes are to 70m antennas. To the 34m HEF subnet the data rate is only 22 kbit/sec. And DSN passes weren't continuous through this period, especially because some of the 70m time was lost to STEREO B.

2) Junocam only gets a small fraction of the total downlink rate (about 5%) with the remainder going to the rest of the payload.

3) Any dropped packets during transmission have to be explicitly commanded to be retransmitted, which takes a day or so typically.