file: TORUS1:[GLL_RAW.INFO]OLD_SL3_GEOMS.DOC May 5,1998 -kes ************************************************************************ NOTE: IF USING OLDER .SL3 FILES (PRE 17-OCT-1997) USE THE FOLLOWING PARAMETER DEFINITIONS; IF USING YOUNGER FILES, SEE THE FILE INFO:HOW_TO_WRITE_READ_IANS_SL3_GEOM_FILES.DOC May 5,1998 -kes ************************************************************************ From: IN%"gebben@ansa.colorado.edu" "Jeremy Gebben" 18-JUL-1997 14:28:02.42 To: IN%"SIMMONS@pisces.colorado.edu" "KAREN SIMMONS AT LASP/COLORADO" Subj: RE: questions Ok, these things are torus geometry parameters that are created with a thing in gggs2.6 called 'Tools->Io Torus->Ian's parameters'. I also have some related software in DISKK:[GLL_RAW.JEREMY.SYSIII], but all it does is figure out the times at which we need to have this data. Basically, the files give the following paramters: UVS files are fltarr(17): 0 = spacecraft clock 1 = utc year (last 2 digits) 2 = utc doy 3 = utc hour 4 = utc minute 5 = utc seconds 6 = utc milliseconds 7 = distance from S/C to Jupiter in Rj point 1 = near side of torus 8 = point 1 z 9 = point 1 rj 10 = point 1 system iii longitude point 2 = middle of torus 11 = point 2 z (same as pt. 1 if outside ansa) 12 = point 2 rj (same as pt. 1 if outside ansa) 13 = point 2 system iii longitude (same as pt. 1 if outside ansa) point 3 = far side of torus 14 = point 3 z (same as pt. 1 if outside ansa) 15 = point 3 rj (same as pt. 1 if outside ansa) 16 = point 3 system iii longitude (same as pt. 1 if outside ansa) EUV files are fltarr(222) 0 = spacecraft clock 1 = utc year (last 2 digits) 2 = utc doy 3 = utc hour 4 = utc minute 5 = utc seconds 6 = utc milliseconds 7 = distance from S/C to Jupiter in Rj 8-31 = point 1 z sectors(1-24) 32-55 = point 1 rj sectors(1-24) 56-79 = point 1 system iii longitude sectors(1-24) 80-103 = point 2 z sectors(1-24) 104-127 = point 2 rj sectors(1-24) 128-151 = point 2 system iii longitude sectors(1-24) 152-175 = point 3 z sectors(1-24) 176-199 = point 3 rj sectors(1-24) 200-223 = point 3 system iii longitude sectors(1-24) We make one file for each encouter (e.g we have one for C03C/E04A). Even though this is torus specific, we include all UVS realtime observations in the UVS files. The time resolution is about 30min, but it follows a strange algorithm that Ian came up with to give uniform coverage of the really long flushes. For the short ones (<=60 rims) there is one set of data for each flush, at the midpoint of the flush. As far as I know, these are not the final data files of this product. Ian has expressed interest in redoing at least some of the encounters with changes to the sampling times and possibly to the software that is doing the actual calculations. He is still looking through the latest versions to make sure he likes what he sees. Also, we used the quick look kernels for orbits E04A, G07A, and G08A with the intention of redoing them when we get the 'final' PLT kernels. For the other orbits, we did use the 'final' kernels: CKC03_FINAL.PLT;1 3840 18-APR-1997 14:58:21.00 CKE06_FINAL.PLT;1 1740 14-MAY-1997 10:05:12.00 CKG01_FINAL.PLT;1 4114 13-MAR-1997 22:15:54.00 CKG02_FINAL.PLT;1 4574 5-APR-1997 22:57:27.00 Because of this, I haven't been thinking 'archive' and there are not log files. I will be sure to make them on the next pass. (an old story, I know... :) ) On Thu, 17 Jul 1997, KAREN SIMMONS AT LASP/COLORADO wrote: > Hi Jeremy, > In June you sent a msg to Ian about the creation of some files > called "xxx.SL3" . They are 'geometry' apparently for him. What are > these files, are there .log files for them, what are they created with, > etc, etc. Think archive. > > Karen >