Obtaining Voyager positions relative to targets |
Obtaining Voyager positions relative to targets |
Jul 23 2016, 07:03 PM
Post
#1
|
|
Junior Member Group: Members Posts: 54 Joined: 7-July 16 From: Austin, Texas Member No.: 7991 |
I'd like to obtain or create a table for the Voyager images with distance information, e.g.
Volume, Image, Target, Distance (km) 5101, C1327538, Io, 134474 (The indexes with the PDS volumes have the times for each image) Does anyone know a source for this or good or simple way to calculate it? I've just started looking at the documentation for SPICE at http://naif.jpl.nasa.gov/naif/, which looks like it would be the way to do it, but I'm not sure how involved it would be. This would give you the size of the target relative to the camera field of view, which would allow you to interleave the narrow and wide angle camera views, and also turn off the center-detection algorithm when generating movies. Thank you for any pointers! |
|
|
Aug 12 2017, 08:14 PM
Post
#2
|
|
Newbie Group: Members Posts: 2 Joined: 8-August 17 Member No.: 8223 |
Thanks for the comments/suggestions. It looks like the NAIF kernels and software are right and the reference to "It came within 570,000 km of the planet's cloud tops", which may come from a JPL Voyager web page is wrong. The Wikipedia article for Voyager 2 detailed "Timeline of Travel" says "1979-07-09 - 22:29 Jupiter closest approach at 721,670 km from the center of mass", which matches the NAIF/SPICE values. By the way, when I tried running the script with target JUPITER instead of JUPITER_BARYCENTER I got an error "Insufficient ephemeris data has been loaded to compute the position of 599 (JUPITER) relative to -32 (VOYAGER 2) at the ephemeris epoch 1979 JUL 08 00:00:50.183."
|
|
|
Aug 13 2017, 12:01 AM
Post
#3
|
|
Senior Member Group: Members Posts: 2511 Joined: 13-September 05 Member No.: 497 |
By the way, when I tried running the script with target JUPITER instead of JUPITER_BARYCENTER I got an error "Insufficient ephemeris data has been loaded... Yes, that's typical. If the kernel doesn't contain records for the geometric object you have to use the barycenter. The offset is insignificant for most purposes. In my experience numerical values in press releases and other prose descriptions are sometimes not very trustworthy. -------------------- Disclaimer: This post is based on public information only. Any opinions are my own.
|
|
|
Lo-Fi Version | Time is now: 19th April 2024 - 01:18 AM |
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. |