Juno Perijove 48, January 22, 2023 |
Juno Perijove 48, January 22, 2023 |
Jan 28 2023, 04:48 PM
Post
#1
|
|
Senior Member Group: Members Posts: 2511 Joined: 13-September 05 Member No.: 497 |
https://www.nasa.gov/feature/jpl/nasa-s-jun...lyby-of-jupiter
QUOTE The JunoCam imager aboard NASA’s Juno spacecraft did not acquire all planned images during the orbiter’s most recent flyby of Jupiter on Jan. 22. Data received from the spacecraft indicates that the camera experienced an issue similar to one that occurred on its previous close pass of the gas giant last month, when the team saw an anomalous temperature rise after the camera was powered on in preparation for the flyby. However, on this new occasion the issue persisted for a longer period of time (23 hours compared to 36 minutes during the December close pass), leaving the first 214 JunoCam images planned for the flyby unusable. As with the previous occurrence, once the anomaly that caused the temperature rise cleared, the camera returned to normal operation and the remaining 44 images were of good quality and usable. The good images have been posted to missionjuno. -------------------- Disclaimer: This post is based on public information only. Any opinions are my own.
|
|
|
Feb 11 2023, 11:51 PM
Post
#2
|
|
IMG to PNG GOD Group: Moderator Posts: 2250 Joined: 19-February 04 From: Near fire and ice Member No.: 38 |
I should mention that interestingly, I have found that if I use any of the most recent clock kernels (JNO_SCLKSCET.00144.tsc, 143 or 142) I get very large pointing (or timing?) errors, typically ~230 (!) pixels in the vertical direction in the images. I have to use JNO_SCLKSCET.00141.tsc to get normal results. I find this interesting because JNO_SCLKSCET.00141 predates PJ48. In fact JNO_SCLKSCET.00142 and 143 also predate PJ48.
The same is true for PJ47, I get large errors unless I use JNO_SCLKSCET.00141.tsc (I suspect 140 would also work). JNO_SCLKSCET.00141.tsc predates not only PJ48, it also predates PJ47. |
|
|
Feb 17 2023, 06:58 AM
Post
#3
|
||
Member Group: Members Posts: 406 Joined: 18-September 17 Member No.: 8250 |
I should mention that interestingly, I have found that if I use any of the most recent clock kernels (JNO_SCLKSCET.00144.tsc, 143 or 142) I get very large pointing (or timing?) errors, typically ~230 (!) pixels in the vertical direction in the images. I have to use JNO_SCLKSCET.00141.tsc to get normal results. I find this interesting because JNO_SCLKSCET.00141 predates PJ48. In fact JNO_SCLKSCET.00142 and 143 also predate PJ48. The same is true for PJ47, I get large errors unless I use JNO_SCLKSCET.00141.tsc (I suspect 140 would also work). JNO_SCLKSCET.00141.tsc predates not only PJ48, it also predates PJ47. Thanks. Investigating this made me realize I'd processed PJ48 using the PJ47 SPK predict. After reprocessing PJ48 using today's juno_pred_orbit.bsp and JNO_SCLKSCET.00145.tsc, the largest offsets I'm seeing are ~9 pixels. But even using PJ47 predict and 144.tsc, I was only seeing offsets of ~15 pixels. Below is PJ48_217, one of the large offset images, with limbs marked. I'm curious if "mis-fit" on right will get better when PJ48 reconstructed SPK shows up. |
|
|
||
Lo-Fi Version | Time is now: 27th April 2024 - 05:02 PM |
RULES AND GUIDELINES Please read the Forum Rules and Guidelines before posting. IMAGE COPYRIGHT |
OPINIONS AND MODERATION Opinions expressed on UnmannedSpaceflight.com are those of the individual posters and do not necessarily reflect the opinions of UnmannedSpaceflight.com or The Planetary Society. The all-volunteer UnmannedSpaceflight.com moderation team is wholly independent of The Planetary Society. The Planetary Society has no influence over decisions made by the UnmannedSpaceflight.com moderators. |
SUPPORT THE FORUM Unmannedspaceflight.com is funded by the Planetary Society. Please consider supporting our work and many other projects by donating to the Society or becoming a member. |