file: info:HOW_TO_WRITE_READ_IANS_SL3_GEOM_FILES.DOC From: IN%"JGebben@rsinc.com" "Jeremy Gebben" 4-MAY-1998 18:34:31.89 To: IN%"SIMMONS@pisces.colorado.edu" "'KAREN SIMMONS AT LASP/COLORADO'" > -----Original Message----- > From: KAREN SIMMONS AT LASP/COLORADO > Sent: Monday, May 04, 1998 11:47 AM > To: jgebben@rsinc.com > Subject: quick question - I think > > Hi Jeremy, > Ian Stewart says that you used to make some geometry files for his > torus data. Did you have a program to do that or did you just use GGGS and > one of the Torus pull down menu items? Pat says he does not recall you > telling him anything about this job. And, of course, I cannot remember! I > hope you can! > I used the "Ian's torus parameters" pulldown on GGGS, but I did have a program to create the input times list based on the times in the data files. It is DISKK:[GLL_RAW.JEREMY.SYSIII]GEN_SYSIII.PRO You give the output of this program as the input file on the GGGS dialog and then it writes the files that Ian uses. Jeremy ======================================================================= 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: what are the xxx.SL3 files? >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 > Karen, I gave you the wrong list of the contents of the data files, here is the correct one. I also forgot to explain about the 'TOR' and 'JUP' parts of the file names. The Z and Rj parameters are calculated relative to the torus center in the 'TOR' files and the jupiter center in the 'JUP' files. I'm also not sure if I have the best explanation for what all these values mean. We might have to check with Ian on it. 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]GEN_SYSIII.PRO, but all it does is figure out the times at which we need to have this data. You give the output of this program as the input file on the GGGS dialog and then it writes the files that Ian uses. Basically, the files give the following paramters: UVS files are fltarr(20): 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 (rj above Jupiter's orbital plane) 9 = point 1 rj (of torus intersection point from juptier) 10 = point 1 system iii longitude 11 = point 1 torus local time (seconds since midnight, i think) point 2 = middle of torus 12 = point 2 z (same as pt. 1 if outside ansa) 13 = point 2 rj (same as pt. 1 if outside ansa) 14 = point 2 system iii longitude (same as pt. 1 if outside ansa) 15 = point 2 torus local time point 3 = far side of torus 16 = point 3 z (same as pt. 1 if outside ansa) 17 = point 3 rj (same as pt. 1 if outside ansa) 18 = point 3 system iii longitude (same as pt. 1 if outside ansa) 19 = point 3 torus local time EUV files are fltarr(297) 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 1 torus local time sectors(1-24) 104-127 = point 2 z sectors(1-24) 128-151 = point 2 rj sectors(1-24) 152-175 = point 2 system iii longitude sectors(1-24) 176-199 = point 2 torus local time sectors(1-24) 200-223 = point 3 z sectors(1-24) 224-247 = point 3 rj sectors(1-24) 248-271 = point 3 system iii longitude sectors(1-24) 272-295 = point 3 torus local time sectors(1-24) According to Ian (May 5,98) the point 1,2,3 values are defined as follows: the Jupiter magnetic dipole is the center of a cylinder of radius 5.76 Rj and if the instrument line-of-sight intersects that cylinder then point 2 is the foot of the perpendicular to that dipole center and points 1 and 3 are the near and far, respectively, intersections with the 5.76Rj cylinder. 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... :) ) ======================================== a sample run follows: IDL> .run TORUS1:[GLL_RAW.SOFTWARE]GEN_SYSIII.PRO % Compiled module: CLPOOL. % Compiled module: LDPOOL. % Compiled module: UTC2ET. % Compiled module: ET2UTC. % Compiled module: SCS2E. % Compiled module: SCE2S. % Compiled module: RESET. % Compiled module: ERRACT. % Compiled module: ERRPRT. % Compiled module: SP_RETURN. % Compiled module: TIME_INIT. % Compiled module: UTC2SCLK. % Compiled module: SCLK2UTC. % Compiled module: MAKE_SYSIII_FILE. % Compiled module: GEN_FILES. % Compiled module: FIND_START_TIME. % Compiled module: FIND_END_TIME. % Compiled module: FIND_TIMES. % Compiled module: READ_PREDICT. % Compiled module: DO_SYSIII. IDL> $sho log p2 "P2" = "GLLUVS2:[GLL_RAW.UVS_P2]" (LNM$PROCESS_TABLE) IDL> f=findfile('p2:c10a_urt*.dat') IDL> help,f F STRING = Array(28) IDL> gen_files,f,'c10_test.lis GLLUVS2:[GLL_RAW.UVS_P2]C10A_URT_10AURA01.DAT;1 4134269 to 4134328 delta = 59 4134298 loading the spice kernel buffer, please wait... % Compiled module: STR_SEP. 4134329 to 4134388 delta = 59 4134358 4134391 to 4134450 delta = 59 4134420 GLLUVS2:[GLL_RAW.UVS_P2]C10A_URT_10FANS01.DAT;1 4132565 to 4132624 delta = 59 etc,etc through all the files defined in the "f" parameter... ending like this: GLLUVS2:[GLL_RAW.UVS_P2]C10A_URT_NTRLCL01.DAT;2 4135191 to 4135220 delta = 29 4135205 4135221 to 4135280 delta = 59 4135250 4135281 to 4135310 delta = 29 4135295 4135311 to 4135340 delta = 29 4135325 4135341 to 4135370 delta = 29 4135355 IDL> IDL> $d c10* Directory DISKH:[SIMMONS] C10_TEST.LIS;1 6 5-MAY-1998 20:11:02.39 Total of 1 file, 6 blocks. IDL> IDL> $ty c10_test.lis 1997-257//08:36:17.115 1997-257//09:36:57.113 1997-257//10:37:37.111 1997-257//11:38:17.109 etc, etc 1997-263//10:51:42.801 1997-263//11:52:22.799 1997-263//12:53:02.797 1997-263//13:53:42.795 IDL> so this file is then read by GGGS and geometry is provided for each (Flush packet) time. THEN, get into GGGS and make a plot (I used the first time in the file created above, with a 30m duration - but it shouldn't matter what you us to create the plot.) Using the "Analysis Tools" menu, select "Ian's Parameters" from those listed under the "Io Torus" item. An input window will open with four values to be listed; if the Rotor (RTR) kernel has been loaded, the last two params (spin rate and ??) will be filled in. Using the OAPELS or the SEF command file, find the EUV Starting Angle (Phase 2 command parameter number 4 = third from last param - but convert from hex to input as decimal!) and the Number of Sectors (cmd param 5) and Scans per Sector (cmd param #6). Enter these all as decimal values and hit the "Done" button. A new small window will appear and ask if input times will come from a file or to use the ones for this GGGS plot: now enter the file created above - don't forget the pathname. Enter "Done" and another window comes up for the name of the output filename: enter the file name, with a new pathname if desired, and DO NOT PROVIDE a file extension: .S3 will be used. At the end of the processing a list file is created containing EUV sector geometry information (at the moment I think this is for the CITEP analysis program and I'm not sure if it should be saved, but a window comes up to give you the chance to specify a save file name.) A look at the start of the file is: +++++++++++++++++++++++++++++++++++++++++++++++ B$ty DISKK:[GLL_RAW]C10_TEST_U.LIS;2 Data format: Sector #, Scan #, Point #, : z (Rj), radius (Rj), Sys III Long. (deg), Local tim e UTC: 1997-257 // 08:36:17.115 START-OF-DATA - EUV, From IO Torus center Sector = 1, Scan = 1, Point = 1: 9.393, 29.258, 262.271, 8047 3.820 Sector = 2, Scan = 1, Point = 1: 9.134, 29.177, 262.508, 8048 1.931 Sector = 3, Scan = 1, Point = 1: 8.874, 29.099, 262.739, 8048 8.909 Sector = 4, Scan = 1, Point = 1: 8.613, 29.022, 262.963, 8049 4.706 Sector = 5, Scan = 1, Point = 1: 8.351, 28.948, 263.179, 8049 9.273 ... Sector = 22, Scan = 1, Point = 1: 3.763, 28.043, 265.734, 8040 9.120 Sector = 23, Scan = 1, Point = 1: 3.489, 28.013, 265.815, 8038 5.192 Sector = 24, Scan = 1, Point = 1: 3.214, 27.985, 265.889, 8035 9.490 END-OF-DATA START-OF-DATA - EUV, From Jupiter center Sector = 1, Scan = 1, Point = 1: 7.937, 29.194, 280.067, 7669 5.657 Sector = 2, Scan = 1, Point = 1: 7.689, 29.112, 280.357, 7666 9.905 ... Sector = 24, Scan = 1, Point = 1: 1.909, 27.906, 285.007, 7582 3.087 END-OF-DATA START-OF-DATA - UVS, From IO Torus center UVS vector, Point # 1 : 1.316, 27.862, 266.184, 80252.671 END-OF-DATA START-OF-DATA - UVS, From Jupiter center UVS vector, Point # 1 : 0.016, 27.785, 285.733, 75566.661 END-OF-DATA Distance to Jupiter: 3434864.3 km ( 48.045 Rj) --------------------------------------------------- UTC: 1997-257 // 09:36:57.113 START-OF-DATA - EUV, From IO Torus center Sector = 1, Scan = 1, Point = 1: 7.442, 28.985, 298.915, 7986 etc +++++++++++++++++++++++++++++++++++++++++++++++ That's the end of this process. NOW If I look at the files created by Jeremy I have: B$d p2:*c10*.sl3 Directory GLLUVS2:[GLL_RAW.UVS_P2] C10A_UVS_JUP.SL3;1 18 29-OCT-1997 21:02:00.16 C10A_UVS_TOR.SL3;1 18 29-OCT-1997 21:02:00.46 Total of 2 files, 36 blocks. and B$d ep2:*c10*.sl3 Directory GLLUVS2:[GLL_RAW.EUV_P2] C10A_EUV_JUP.SL3;1 63 31-OCT-1997 20:13:47.71 C10A_EUV_TOR.SL3;1 63 31-OCT-1997 20:16:47.85 Total of 2 files, 126 blocks. and if I look at these with IDL I see: ----- IDL> openr,1,'p2:C10A_UVS_JUP.SL3;1 IDL> print,fstat(1) { 1 GLLUVS2:[GLL_RAW.UVS_P2]C10A_UVS_JUP.SL3;1 1 0 0 0 1 0 0 0 8800 80} IDL> openr,1,'p2:C10A_UVS_TOR.SL3;1 % OPENR: File unit is already open: 1. % Execution halted at: $MAIN$ IDL> openr,2,'p2:C10A_UVS_TOR.SL3;1 IDL> print,fstat(2) { 2 GLLUVS2:[GLL_RAW.UVS_P2]C10A_UVS_TOR.SL3;1 1 0 0 0 1 0 0 0 8800 80} IDL> openr,3,'ep2:C10A_euv_TOR.SL3 IDL> print,fstat(3) { 3 GLLUVS2:[GLL_RAW.EUV_P2]C10A_EUV_TOR.SL3; 1 0 0 0 1 0 0 0 31968 1184} IDL> openr,4,'ep2:C10A_euv_jup.SL3 IDL> print,fstat(4) { 4 GLLUVS2:[GLL_RAW.EUV_P2]C10A_EUV_JUP.SL3; 1 0 0 0 1 0 0 0 31968 1184} ----- FINALLY, the files I created today are: Directory DISKH:[SIMMONS] C10_TEST_U_EUV_JUP.S3;1 255 5-MAY-1998 21:14:39.81 C10_TEST_U_EUV_TOR.S3;1 255 5-MAY-1998 21:14:40.20 C10_TEST_U_UVS_JUP.S3;1 18 5-MAY-1998 21:14:39.97 C10_TEST_U_UVS_TOR.S3;1 18 5-MAY-1998 21:14:40.36 Directory DISKK:[GLL_RAW] C10_TEST_U.LIS;2 1769 5-MAY-1998 21:21:16.84 C10_TEST_U.LIS;1 1769 5-MAY-1998 21:21:02.94 Total of 2 files, 3538 blocks. and if I look at these with IDL I get: -------- IDL> openr,1,'sim:C10_TEST_U_EUV_JUP.S3;1 IDL> print,fstat(1) { 1 DISKH:[SIMMONS]C10_TEST_U_EUV_JUP.S3;1 1 0 0 0 1 0 0 0 130240 1184} IDL> openr,2,'sim:C10_TEST_U_EUV_tor.S3;1 IDL> print,fstat(2) { 2 DISKH:[SIMMONS]C10_TEST_U_EUV_TOR.S3;1 1 0 0 0 1 0 0 0 130240 1184} IDL> openr,3,'sim:C10_TEST_U_uvs_tor.S3;1 IDL> print,fstat(3) { 3 DISKH:[SIMMONS]C10_TEST_U_UVS_TOR.S3;1 1 0 0 0 1 0 0 0 8800 80} IDL> openr,4,'sim:C10_TEST_U_uvs_jup.S3;1 IDL> print,fstat(4) { 4 DISKH:[SIMMONS]C10_TEST_U_UVS_JUP.S3;1 1 0 0 0 1 0 0 0 8800 80} ---------- which agrees! ONE FINAL ***CAUTION***: Earlier versions of these files wrote different file lengths for UVS (at least). Look at the file "TORUS1:[GLL_RAW.INFO]OLD_SL3_GEOMS.DOC" for a definition of the parameters in .S3 # files made before October 17, 1997 (which was when Jeremy updated his program from version ;1 to ;2.) # This seems to be the time when full orbits of flush times get renamed with the .SL3 extension while individual observation files keep an extension of .S3; but a few new files didn't get renamed from .S3 either! -kes ====================================== #1 5-MAY-1998 22:27:30.74 NEWMAIL From: IN%"JGebben@rsinc.com" "Jeremy Gebben" To: IN%"SIMMONS@pisces.colorado.edu" "'KAREN SIMMONS AT LASP/COLORADO'" CC: Subj: RE: another .SL3 question You're right, I was renaming the files that GGGS created from .S3 to .SL3. I forgot about that. It was easier for me to just rename the files than to figure out which part of the GGGS code was creating the file names. I think the reason for the name change was related to the change in array size, or some other change on the GGGS side. Anyway, I think Ian was only using the .SL3 files at present. I think that any .S3 files that are around are "old" stuf that is not really needed. Hope that helps... Sorry for the mess! Jeremy > -----Original Message----- > From: KAREN SIMMONS AT LASP/COLORADO > Sent: Tuesday, May 05, 1998 4:16 PM > To: jgebben@rsinc.com > Subject: another .SL3 question > > Hi Jeremy, > I found all the software, ran it all and, after a GGGS hickup when > I tried to add a file extension to the output name!, managed to run through > the entire GEN_SYSIII.PRO sequence. One final remaining question though: > the GGGS program creates files with the .S3 extension. On the data > directories > I see files with individual observation names and a .S3 extension and > I also see a .SL3 file which seems to be a complete file set. (See below.) > So I'm guessing that when you run this for the entire orbit period you > rename the file with the .SL3 and if you run individual files you leave them > named .S3 - right? > You did a program update in 17-Oct-97 and I figure that's when you made > it do all the flushes and also you changed the (at least) UVS aprameters > from an array of 17 to an array of 20 values. Does that sound right also? > > Good. Thanks! > > Karen > > J0CD_UVS_NANS33_JUP.S3;1 > 1 12-JUL-1996 19:44:59.24 > J0CD_UVS_NANS33_TOR.S3;1 > 1 12-JUL-1996 19:29:50.65 > J0CD_UVS_NANS34_JUP.S3;1 > 1 12-JUL-1996 19:45:30.71 > J0CD_UVS_NANS34_TOR.S3;1 > 1 12-JUL-1996 19:30:07.80 > > Total of 40 files, 46 blocks. > B$d p2:*j0c*.sl3 > Directory GLLUVS2:[GLL_RAW.UVS_P2] > > J0CD_UVS_JUP.SL3;1 34 11-JUN-1997 20:45:22.12 > J0CD_UVS_TOR.SL3;1 34 11-JUN-1997 20:31:57.67 > > Total of 2 files, 68 blocks.