file GLLUVS1:[GLL_RAW.PDS_ARCHIVE]USER_HANDBOOK_p2.DOC = Part 2, the last appendix May, 2000 - kes Appendix H May 01, 2000 WHO'S WHO Scientists Dr. A. Ian F. Stewart - PI - LASP Dr. Charles A. Barth - CoI - LASP Dr. Larry W. Esposito - CoI - LASP Dr. William E. McClintock - CoI - LASP Dr. Wayne R. Pryor - CoI - LASP Dr. Gary E. Thomas - CoI - LASP Dr. Joseph M. Ajello - CoI - JPL Dr. Kent Tobiska - JPL - Co-I (1997) & JPL Experiment Rep Dr. A. Lonne Lane - CoI - JPL Dr. Robert A. West - CoI - JPL Dr. A. Lyle Broadfoot - CoI - LPL Dr. Donald M. Hunten - CoI Dr. Bill R. Sandel - CoI - LPL (Tuscon) Dr. Donald F. Shemansky - CoI - UCLA Dr. Amanda R. Hendrix Graduate Students (LASP): David A. Brain Operations Karen E. Simmons - Experiment Manager - LASP Jim Adams - LASP - undergrad.student (1/2 time) Pat Shriver - LASP - (graduate/hourly) student (1/2 time) Engineering Neil White - LASP Past Players and Associates Dr. Charles W. Hord - PI, Retired 1998 - LASP Will B. Colwell - LASP - Graduate Student -> PhD Martin Taylor - LASP - Graduate Student -> PhD Kirk Benell - LASP - student (1/2 time); now at RSI/IDL Bruce Waggoner - LASP student, now JPL Jeff Culwell - LASP - student (1/2 time) Jeremy Gebben - LASP - student (1/2 time): data trans/Fmt/Analysis Greg Rutz - LASP - student (1/2 time): Sequencing/Verification Cate Fowler - LASP - student (1/2 time) -> PhD Wendy Sweet - LASP - student (1/2 time) Pamme Crandall - LASP - student (1/2 time) Krista Schwantz - LASP - student (1/2 time): Backups/Archiving Jennifer Ray - LASP - student (1/2 time) Naomi Mosser - LASP - Student (1/2 time): Backups/Archiving Deb Miller - LASP - GGGS programmer Brian Pape - LASP - GGGS programmer Scott Lasica - LASP - GGGS programmer Leslie Tamppari - JPL - ex-Asst. Experiment Rep John Farrar - JPL - engineering Bob Ebbett - JPL - engineering Jack Schwartz - JPL - OET Gaylon McSmith - JPL -OET Steve Edberg - JPL - 1/2 time UVS, Asst. Experiment Rep Keith Naviaux - JPL - ex-Asst. Experiment Rep John J. Aiello - JPL - ex-Asst. Experiment Rep Stuart K. Stephens - JPL - ex-Asst. Experiment Rep Lisa Crowe - JPL - Asst UVS/EUV sequence designer Past Engineering Gene McNutt - Experiment Manager - LASP Vic Argabright - LASP Engineering Kurt Filsinger - LASP Fred O'Neil - Independent Addresses: LASP Laboratory for Atmospheric and Space Physics University of Colorado 1234 Innovation Dr Boulder, Co 80303 JPL Jet Propulsion Laboratory 4800 Oak Grove Dr. Pasadena, Ca. 91109 U of A Lunar and Planetary Laboratory University of Arizona 901 Gould-Simpson Bldg Tucson, Az 85721 UCLA Deptment of Aerospace Engineering University of Southern California 854 W.36th Place RRB 222 Los Angeles, CA 90089-1191 Pg 1a - Jan 21,94 KES ROLES OF THE VARIOUS PLAYERS 1) LASP Roles * Karen's - "Experiment Manager" Health and Welfare of Instruments Safe in Sequence Planning Safe in realtime commanding Verification of every-day operation Instrument Functionality Interface Sequence Design Scientist-to-Implementor Interface "Bookkeeper" Error Cross-check/backup Operations and Analysis Reformat software generation and maintenance JPL Ground system functionality LASP operations and data system functionality Data distribution and Archiving activities Publication assistance any other hat not mentioned above Phase II instrument and s/c design, functional req. * Student's (see add'l sheets) THINK Our second line of defense: watch everything for inst health Data Maintenance/Archiving Routine Monitoring Sequence History File and Records Maintenance Tape Recorder Monitoring Software Archive Maintenance Software Creation * Scientist's ... Science Requests for Sequence Design Science Analysis Publication 2) JPL Roles * Joe's - "Co-I / Experiment Rep" * Steve, Keith, Kent - "Asst Experiment Reps" Build Sequences POINTER Work Interface w/other science teams Interface w/other JPL groups (SROP, OET, etc) Monitor Quick Look Health: Our first line of defense DTV daily Engineering data at NERT/NORT Science data at NERT/NORT Attend Meetings! Workshop Pg 1b - KES GALILEO - UVS & EUV TELEPHONE GUIDE December 6, 1999 Addr phone Home Elect.Mail Code *SpaceTechBldg phone /campus Ian Stewart 2 *303-492-4630 303-444-1330 ZODIAC::STEWART 1 303-492-8689 Charlie Hord 2 *303-492-7923 303-494-0105 PISCES::HORD secs:Nancy=6412,Ann=7670,Bonnie=3742 980 Hartford Dr, Boulder, 80303-6316 Charles Barth 2 303-492-7502 303-499-3726 PISCES::BARTH 1 303-492-7503 Larry Esposito 1 303-492-7325 303-499-5791 ZODIAC::ESPO Bill McClintock 2 *303-492-8407 303-449-7812 PISCES::MCCLINT Wayne Pryor 2 *303-492-1259 303-666-4445 PISCES::PRYOR Gary Thomas 1 303-492-7022 ZODIAC::GTHOMAS Karen Simmons 2 *303-492-8363 303-447-8607 simmons@pisces mt303-447-0321 PISCES::SIMMONS Joe Ajello 3 818-393-0523,sec:3-1130 (Bldg 264-744),Fax:818-393-4530 Bldg 183-601: 818-354-2457, 4-0120, sec:4-2140 626-447-2471 GLLSVC::AJELLO *303-492-8970 PISCES::JAJELLO Lonne Lane 3 818-354-2725,46186 818-355-8628 JPLAL2::ALANE (Office:233-201D,Mail:233-200)Fax:818-394-8333 or4-3938 1815 Oakwood Ave, Arcadia, CA 91006-1724 Bob West 3 818-354-0479 818-797-4758 raw@west.jpl... Bldg 169-237, Fax:818-393-4619 ISSAC::RWEST 2097 N. Mar Vista, Altadena,91001 Kent Tobiska 3 818-393-7742,0523 310-573-4185 tobiska@pop.jpl.nasa.gov ms.bldg 264-580 Dnvr:237-8995 fax:818-393-4530 Bill Sandel 4 520-621-4305,secry=4301 sandel@arizona.edu sandel@vega.lpl.arizona.edu Don Shemansky 5 213-740-7184 fax:213-740-7228 dons@athena.usc.edu Neil White 2 *303-492-7959 303-979-7918 PISCES::WHITE LASP Ops:(303)492-5877, 2-4311; Phil Evans 2-6951,beep 869-9554 2nd Floor Fax 735-4843. Gene McNutt,303-492-8216, h:303-776-8558; JD beep=869-9282 OET/David Acevedo 818-393-1065 (BEEP:818-423-2459; home=909-428-9264) Julio Orsina (JPL Computer Manager)=818-393-1230 POINTER 3-0960,6,7,8 Kathy Schimmels 3-7713 fax: 3-4530 Kathryn.Schimmels@jpl.nasa.gov Pat Lynn 3-1148 PLYNN@glvax0.jpl.nasa.gov ACE: (818)393-5806/7; Gll Sci (818)393-0918; JPL UVS Fax:818-393-4530 Lisa:3-7718, Saga(818)795-0431; Glendale DaysInn(818)956-0202 ; 1 Univ of Co/LASP, Campus Box 392, Boulder,Co 80309-0392 ;Fax:303-492-6946 *2 Univ of Co/LASP, 1234 Innovation Dr,Bldr,Co 80303 ; Fax:303-492-6444 3 JPL, 4800 Oak Grove Dr., Pasadena, Ca. 91109 JPL Info= 818-354-4321 4 Univ of Az/LPL,901 Gould-Simpson Bldg, Tucson, Az 85721 ;Fax:602-621-8364 5 Dept.of Aero Eng,854 W.36th Place RRB 222,U.of So.Ca,LA,CA 90089-1191 JPL 800 phone access: 800-367-5754:tone:575:tone:5-digit-extension JPL Launch status line: 1-800-391-6654; Kennedy launch status:704-867-2525 Kennedy Press room: 704-867-2468 Pat Shriver shriver@lasp.colorado.edu Jim Adams Adams@lasp.colorado.edu Workshop Pg 3 - Jan 20,94 KES DATA MANAGEMENT WHY * Convert JPL binary and character information for easier use by the (distributed) team members * Consistent, central storage of data products and associated information * Provide information about and access to these archives HOW * Data distribution entirely via electronic transfer (Internet network) * Fortran software for conversion from Univac to Vax and IDL formats * Fortran and IDL quick look analysis and graphics display software (EDRs and EUV cruise memory dump data) * Fortran SPICE (kernel) Toolkit and inhouse software for geometry generation * IDL software for sequence/commanding information processing/archiving * INGRESS data base manager (prototype operational) for data browse and request processing * OPS83 Expert system for Data Certification (prototype operational) * Individual team member's analysis software WHEN UVS/EUV -> S/C - Real Time | or | -> DSN -> JPL -> Tape/Playback| LASP |-> Scientists/Engineers - JOURNALS... |-> ARCHIVES WHERE * Most processing at LASP # Quick look available at JPL on the NERT (Near Real Time) system and on the DTV (Digital Television) display (engineering only) # SANTA prototypes for design of replacement current NERT system * Team member's local sites DSN |-> SFOC# (Space Fight Operations Center) (Galileo Prototype) -> SANTA | |-> Engineering DTV system -> DTV display | |-> UNIVAC |-> DMT (Data Management Team computers) -> NERT# | |-JPL-ILAN/Microvax-> SVC (Clarke'S Science Vax Cluster) -Internet-> LASP (PISCES::) -Internet-> Other Team sites (JPL, LPL) # Note: Phase II processing may be very different from the current modes ADDENDUM to Data Management, 1 May 2000 The above description was in place for Pre-Jupiter operations. The JPL end, especially their data management archive system is now quite different, as shown below. The DTV is only available to the JPL Gll operations ACE and the SFOC has been replaced with the JPL Multi-Mission flight data base operation. LASP Remote Querry -> JPL Unix GLL deamon -> JPL Multi-mission Data Base |-> returns data to LASP Unix machine "ANSA" On ANSA, IDL s/w decodes Phase II s/c packets into IDL readable UVS/EUV data files that are then transfered to the Vax machines and archived. Workshop Pg 4 - Jan 19,94 KES DATA AND INFORMATION ACCOUNTS GENERAL * Data accounts are "access limited"; only pre-validated accounts are permitted READ access; only data managers have WRITE access * Calibration or general use files must be submitted, with documentation, for placement on these accounts * Protect your passwords NASA is particularily sensitive: the SPACECRAFT IS AT RISK * Sequence information is on a separate account * Data management and SPICE Toolkit software reside on separate accounts * Most account directories have READ.ME files containing helpful information; data accounts have summary information files * An attempt is being made to store all pertinent information electronically * Formated and unformated data files are on separate directories # see below * There is a documented Data Management Plan; there is currently little program documentation beyond in-line documentation. # see below ADDENDUM TO Data Accounts, 1 May 2000 # We now separate all (binary, browse and text) data and information by instrument, ie in EUV and UVS directories # Considerable documentation is now available, in the INFO directories and in data product labels, in the PDS archive CDs and elsewhere Workshop Pg 6 - Jan 21,94 KES FILE NAMING CONVENTIONS The following conventions were in effect for the early, pre-Jupiter operations period. With Phase II operations for Jupiter and the extended missions the formats became simplier due to the limited number of data types and products. (5/2000: see discussion in User Handbook, above.) DATA FILES UVSyydoyhhmm_doyhhmm.DAT - 24 hour process file UVSyydoyhhmm_doyhhmm.AACS - AACS for above file UVSyydoyhhmm_doyhhmm.TC - UVS temperature data for a 24 hour process file nn_V2_paname_(NODxx).DAT - Extracted, edited Observation data (nn=encounter period,obs=paname,xx=s/w vers) nn_V2_paname_(NODxx).AACS - AACS data for above UVS_paname_NOD.DAT - Extracted Observation (named 'paname' for Profile Activity/OAPEL name) data file (_NOD = no Decompression of F-channel data, if present) UVS_paname_NOD.AACS - the associated AACS data for above file's time period EUVyydoyhhmm_doyhhmm.DAT - 24 hour process file: data records EUVyydoyhhmm_doyhhmm.SURF - 24 hour process file: Surface plot matrix (FLTARR(#_SECTORS,128)) EUVyydoyhhmm_doyhhmm.WIB - 24 hour process file: WIB (Wavelength Integration Buffer) array and SIB (Sector Integration Buffer) array (FLTARR(129)) EUVyydoyhhmm_doyhhmm.LIS - 24 hour process file: Error listing from Surface and WIB/SIB processing EUV_paname.DAT - Extracted Observation (named 'paname') data file EUVrrrrrrr_mf.MRO - EUV cruise Memory Readout file, with header info ***NEW rr,mf=RIM,minor frame of MRO EUV_rrrrrr_mf.MRO - Same, early RIM values MROxxxxxx.MROH - EUV cruise Memory Readout file, without header info ***OLD MROxxxxxx.MRO - EUV cruise Memory Readout file, with header info ***OLD SEQUENCE FILES SEF_yymmdd.UNI_VE12 - The original SEF (Sequence of Events File) generated on yy-mm-dd SEF_yymmdd.FLAG_VE12 - The above, full SEF file with pertinent items flagged SEF_yymmdd.STRIP_VE12 - The above SEF file striped down to pertinent items ORPRO_yymmdd.UNI_VE12 - The original ORPRO (Orbit Profile) ORPLN_yymmdd.UNI_VE12 - The original ORPLN (Orbit Plan) more... SPICE KERNEL FILES: The GGGS software tool looks for SPICE kernel files by spefic file names, especially SPK_iii.BSP and CK_iii.PLT and CKiii.RTR. The last nine files of a directory index with these names are used so one must be careful to re-name the JPL files with appropriate names. This especially became critical with the YY role-over from '99' to '00' since '99' is later in the alphabet from '00'. ### SPK_yydoyhh_doyhh.BSP - S and P kernel file with begin and end UT time in Years/DOY/HH (Current naming) SPK_GLL92-14A-S18-3.BSP;1 - The Galileo Tour 14A-S18 update #3 Use this SPK for Jup orbit planning. Named SPKs indicate special observations GLL901204.BSP - JPL naming for Binary S and P (BSP) kernal files - start kernel time (yymmdd) originally was naming convention. SPK_GLL901204.BSP_1 - LASP naming for SPK with imbeded JPL name (Recent GGGS convention may force the use of the JPL name) GLL901204.TSP - JPL naming for Text format (ASCII) S and P kernal files GLL901204.TIP - A text file documenting the creation specifics of the .BSP kernel CK_yydoyhr_doyhh.PLT - C-kernel file for the Scan Platform CK_yydoyhr_doyhh.PLT_BCK Actual date with begin and end UT time. CK_yydoyhr_doyhh.PLT_EV6 Some of these have _Load# added to .PLT CKyydoyA.PLT,CKyydoyB.PLT Start time, usually half and encounter day is in A/B file (Current JPL/LASP name) CK_MIPS_E1_CSMITHED.PLT_BCK;1 - Specific C-kernel; name indicates process CK_VENUS.PLT_95381;1 - C-kernel (early name) w/load+JPL name CKyydoyA.PLT_10185 - JPL and SVC Catalog Platform C-kernel naming indicating yy/doy/(A or B) where A=00: to 11:59:00.0 hours and B=12: to 23:59:00.0 hours and a file serial number. SVC Catalog uses these - we will too but with a cross reference file: FILE_INFO.LIS which will indicate begin and end times SSI00012.BC_1 - SSI "smithed" Scan Platform C-kernel with Serial Number (?) CK_yydoyhr_doyhh.SCAN_PRE - C-kernel file for the Scan Platform Predict data with begin and end UT time CK_yydoyhr_doyhh.ROTOR_PRE - C-kernel file for the Rotor PREDICT data with begin and end UT time CK_yydoyhr_doyhh.RTR - C-kernel file for the Rotor Actual data with begin and end UT time (Current naming) CKEE4V2.ZAX;1 - C-kernel special ROTOR file w/ z-axis value supplied by JPL hand editing of Nav data Phase II format names CKC22Q.PLT;1 - C-Kernel, 'Q'=QuickLook, Scan Platform CKC22AJD.PLT;1 - C-Kernel, 'AJD'=seqID therefore Predict CKC22F.PLT;2 - C-Kernel, 'F'=Final, Scan Platform SPK_S000407A.BSP;1 - SPK-Kernel, '000407'=yymmdd,'A'=version There are other SPICE/GGGS files with naming conventions besides these data files. These are known as the "constants" files and include: GLL00012.TSC_1;1 - Gives body numbers, other planet refs GLL00012.TPC_1;1 - Information to convert s/c clock to time GLL24001.TI - A file specifying the EUV (inst #24,Ver1) GLL34001.TI - A file specifying the UVS (inst #34,Ver1) LEAPSECONDS.REF - A file giving the dates of leapseconds LEAPSECONDS.TIP Pg 7 - Feb 7,91 KES THE DATA ACCOUNTS disk:directory type ---------------------------------------------------------------------------- DISKK:[GLL_RAW.LRSP] Raw data (transferred from SVC vax LRSP::) SAVED_FILES.TAPE lists everything on archive tapes DISKK:[GLL_RAW.SANTA] Raw, processed data, and software from SANTA prototype for Earth 1 - BEWARE DISKK:[GLL_RAW.EUV] EUV Encounter mode *.DAT Data files *.SURF,*.WIB,*.LIS output/processed data DISKH:[GLL_RAW] A_READ.ME General info on the sub-directory contents DATA_STATUS.LIS Lists data files currently on disks with some processing info DISKH:[GLL_RAW.CALIBRATION] Calibration files READ_ABOUT_CALIBS.ME Sorry, no documentation of these files yet FLIGHT_F_CAL_1.DAT;1 F-channel Flight Wavelength and Sensitivity FLIGHT_G_CAL_1.DAT;2 G-channel Flight Wavelength and Sensitivity FLIGHT_N_CAL_1.DAT;1 N-channel Flight Wavelength and Sensitivity GLL_F_SOLAR_SPECTRUM.DAT;1 Solar Spectrum adjusted to F-channel resolu GLL_G_SOLAR_SPECTRUM.DAT;2 Solar Spectrum adjusted to G-channel resolu SANDEL_PIXEL_FIX_FPN5.DAT;1 Sandel's Hot Pixel (Version #5) corrections UVS_DEAD_TIME.DOC;1 McClintock's UVS F-channel Count Correction DISKH:[GLL_RAW.EUV] Empty, all EUV data moved to DISKK: DISKH:[GLL_RAW.INFO] Data related general information HEADER.INFO Lists EDR/AACS file Header word references (Sorry, currently out of date!) SAGEOM.INFO Gives SAGEOM parameter definitions DISKH:[GLL_RAW.LRSP] Empty, all raw data moved to DISKK: DISKH:[GLL_RAW.MROH] EUV Cruise MROs filename.MROH & filename.MRO general data files ALLSPIN_DUALSPIN.LIS lists times of these spin modes (effects EUV sector size) SITURN.LIS lists times of -Z axis adjustments EUV_MRO.MAP a cross-reference for MRO dump locations vs (sample x pixel) values TOM_CRUISE.PRO The Cruise analysis program (Barth's name!) START.DAT,STOP.DAT, Cruise analysis tables MRO_FILELIST.LIS (EUV Power On, Off times, file names) more... Pg 8 - Feb 7,91 KES THE DATA ACCOUNTS (Continued) DISKH:[GLL_RAW.SAGEOM] SAGEOM Predicts (Tables) DISKH:[GLL_RAW.SOLAR] EUV Solar Lyman-alpha Index values READ.ME Documentation information GLL_LYA.DAT IDL format Index file DISKH:[GLL_RAW.SPICE_KERNALS] SPICE kernels FILE_INFO.LIS Lists kernel file names vs UT begin and end times DISKH:[GLL_RAW.TC] UVS temperature data DISKH:[GLL_RAW.UVS] UVS spectra data *.DAT data files *.AACS AACS data for times of data files COMMAND, SEQUENCE, AND DOCUMENT ACCOUNTS DISKH:[GLLSEQ.*] Planning, Sequence and History Information [main] Command construction (cook-book) examples [.load] each mission load period on a separate directory [.GENERAL_INFO] Electronic SRD (Science Requirements Doc) updates, mission planning requests, OAP (Orbit Activity Plan) info [.HISTORY] Mission History directory CMD_ARCHIVE.DOC Archive of all EUV and UVS commands [.LIB] Files containing copies of PA (Profile Activity) documentation, on-board Library Sequences, FPN (EUV Fixed Pattern Noise table) loads, memory loads DISKH:[GALILEO.DOC] Galileo Mission Document Inventory JPL.DOC File lists what 625- documents we have here at LASP/campus more... Pg 9 - Feb 7,91 KES THE SOFTWARE ACCOUNTS DISKH:[GLL_RAW.NAIF_TOOLKIT] Second of three Toolkit deliveries (Oct,90); has no C-kernel or Galileo specific software. Use the one on [GEOM] DISKH:[GLL_RAW.SOFTWARE] General purpose analysis software Sorry, no documentation yet and mostly still in development DISKG:[GEOM.NAIF.TOOLKIT...] All NAIF (Navigation and Ancillary Information Facility) supplied SPICE Toolkit software See the SPICE TOOLKIT ACCOUNT pages for much more detail DISKK:[GWIZ...] The Galileo Geometry and Graphics Software DISKK:[GWIZ.gggs_2_6] (GGGS) visualization Tool resides here. Version 2.6 is the standard, others perform specific tasks (needing large buffers). The Unix version is on Vixen. THE BROWSE CATALOG DISKH:[GLLCAT] The INGRESS programs, browse files, etc; BEWARE: this is a prototype and has not been documented or recently updated THE SVC SPICE KERNEL AND TOOLKIT CATALOG PRINCE::DUA1:[GSC] To use the catalog you must have a PRINCE account. Ask for help if you want to browse this system instead of ours. Pg 12 - Feb 7,91 KES THE SPICE TOOLKIT ACCOUNT DISKG:[GEOM] | +---------------+----------------+ | | [.NAIF] [.BUILD] VAX_INSTALL.TXT PORTING.TXT VAX_LIBSUM.TXT | +-----------------+ | | [.TOOLKIT] [.DATA] | | GLL00002.TLS (Text) Leap Seconds | GLL00002.TPC Planetary Constants | GLL00003.TPC new Planetary Constants | GLL00003.TSC Spacecraft Clock | GLL_LONG_2.TSP S & P kernel sample | GLL25001.TI I-kernel, Instrument #25 | GLL28001.TI | GLL29001.TI | GLL34001.TI " " for UVS | GLL36001.TI | GLL37001.TI | +--------+--+---------+---------+-----------+---------+ | | | | | | [.SPICELIB] [.SPACIT] [.SIMPLE] [.SPTEST] [.COOKBOOK] [.VISTA] | | (A description of the contents of each of these | product directories is given below this | structure.) +------------+ | | | [.REQ] [.SOURCE] [.TXT] | *.REQ + | [.VAX] *.FOR SPICELIB.OLB MAKE_SPICELIB.COM The contents of each program product directory is listed below. more... Pg 10 - Feb 7,91 KES THE SPICE TOOLKIT ACCOUNT SPACIT - A program to convert Text formated data file to Binary formated files, and reverse (for non-Vax network transfer) and a useful tool for browsing kernel data files. [HOME.NAIF.TOOLKIT.SPACIT] | + | [.VAX] SPACIT.MAIN *.FOR MAKE_SPACIT.COM SPACIT.UG SPACIT.EXE SPTEST - A program to test S & P kernel data files [HOME.NAIF.TOOLKIT.SPTEST] | + | [.VAX] SPTEST.MAIN GEN.3 GLL_TEST1.TSP TEST.3 MAKE_SPTEST.COM SPTEST.UG SPTEST.EXE VISTA - A catalog type program to assist in finding Toolkit software routines that match the user selected browse choices. [HOME.NAIF.TOOLKIT.VISTA] | [.VAX] VISTA.MAIN *.FOR MAKE_VISTA.COM VISTA.COM VISTBL.DAT VISTA.EXE more... Pg 11 - Feb 7,91 KES THE SPICE TOOLKIT ACCOUNT COOKBOOK - A group of cookbook routines. See the Required reeding documents. [HOME.NAIF.TOOLKIT.COOKBOOK] | + | [.VAX] FSTSPK.MAIN STATES.MAIN SUBPT.MAIN TIME.MAIN FSTSPK.UG STATES.UG SUBPT.UG TIME.UG COOK_01.TC COOK_01.TLS COOK_01.TSC COOK_01.TSP MAKE_COOKBOOK.COM FSTSPK.EXE STATES.EXE SUBPT.EXE TIME.EXE Pg 13 - Feb 7,91 KES GEOMETRY KNOWLEDGE PREDICTS * We have some SAGEOM tables of body distances and angles There is no generation documentation supplied with these * POINTER provides knowledge but is readily available in a usable form to LASP science designers * Eventually will be able to use SPICE# predict kernels to develop observation design tables/graphics AFTER THE FACT * AACS (Attitude and Articulation Control Subsystem) information in EDRs (Experiment Data Records) * one minor frame resolution (at RTI=0) * Still some unknowns about axis reference frames, magnitudes (signed or un-signed integers); lack of documentation (is it written down and if so then where? * Still need to correlate with predicted knowledge; have at least seen "limit cycling" of Rotor (Ra,Dec) on the order of 0.1 degree at about 10 deg in Dec. * Will be able to cross check with EUV sectoring * The 12 parameters of AACS are as follows: 1 = Rotor attitude -- RA (0-360 deg) 2 = Rotor Attitude -- DEC (-90 to +90 deg) 3 = Rotor Attitude -- TWIST (0-360 deg) 4 = platform attitude -- RA (0-360 deg) 5 = Platform Attitude -- DEC (-90 to +90 deg) 6 = Platform Attitude -- TWIST (0-360 deg) 7 = Platform Rate -- CONE (-90 to +90 deg) 8 = Platform Rate -- CROSS CONE (-90 to +90 deg) 9 = Rotor Spin Motion Delta assume (0-360 deg) 10 = Rotor Spin Position Angle assume (0-360 deg) 11 = S/C Relative Cone (0-360 deg) 12 = S/C Relative Clock (0-360 deg) * SPICE# Kernels for spacecraft location, body locations and pointing knowledge * We now (appear) to have all necessary kernel and toolkit software * We are building and testing software and geometry data sets * During Phase 1 the AACS knowledge was returned every minor frame, or 2/3 sec. During Phase 2, only encounter periods returned AACS parameters every 2/3s. and then only SOME of these. During cruise loads the frequency for the few AACS values was once per five RIMS, roughly 5 minutes. AACS files were generally not created during Phase 2 and SPICE kernels were used for position and pointing. # SPICE stands for the 5 necessary vectors to determine spacecraft location and look direction geometry knowledge: S - Spacecraft position vector P - Planet (body) position vectors and constants I - Instrument knowledge, like Field of View size and orientation C - The "C matrix" which represents the scan platform look vector E - Event knowledge, such as tape recorder usage therefore jiggle Pg 18 - Feb 7,91 KES DOCUMENTATION REFERENCES [1] Galileo UVS Functional Requirement Document GLL-625-205, 4-2034, Rev A of 10 April 1989. [2] Galileo EUV Functional Requirement Document GLL-625-205, 4-2024, 14 August 1989. [3] "Galileo UVS Calibration Report, Preliminary Version" by William McClintock, dated March, 1989. [4] UVS/EUV instrument paper, Draft version, 6 Feb, 1991. by Charles W. Hord, et al. Submitted to Space Science Reviews. [5] Galileo EUV Data System Functional Specification by Fred O'Neil, Revision E of November 3, 1989. [6] SPICE KERNEL ``Required Reading'' files, released by NAIF, available on the Toolkit directory: ZODIAC::DISKG:[GEOM.NAIF.TOOLKIT.SPICELIB.TXT]*.REQ [7] READ.ME files on various accounts [8] Galileo Science Requirements Document, especially Sections 2, 4, and 5. GLL-625-50, Revision D, 18 January, 1989. [9] HOW_TO files, [.GEN_TEMPLATE] files and PDS 'Label' files supply additional documentation INTERNAL * Remember to leave a `paper trail': document what you do and keep at least a copy in your own records. Example: Real Time Command Requests * Put the date (spelled out) and your initials on any work * Distribute copies to appropriate groups * Update the documentation when changes are made Example: OAPEL designs Pg 21 - Feb 7,91 KES THE EUV INSTRUMENT FUNCTIONAL DESCRIPTION * Voyager UVS Spectrometer Detector Some Electronics: Timing and Control, Accumulator Logic * Added Microprocessor and RAM New FDS (Voyager's Flight Data System) to Micro interface, Analog Multiplexor, CDS (Command and Data Subsystem) Bus New Low Voltage Power Supply OPTICAL PATH (See Figure) * Cover is (permanently) deployed (Dec, 1989) * Optical path to detector is "open" * Field of View is a slit: 0.87 by 0.17 degrees * Slit is oriented so that short side sweeps as Rotor turns (long axis is parallel to -Z axis) MICROPROCESSOR SOFTWARE * Micro is an RCA 1802 * 4k bytes RAM * Program takes 1279 bytes * Buffer usage depends on mode * Interrupt driven * Returns 12 bytes of data each 2/3 of a second * Instrument's natural time period is 20.8 milliseconds; the amount of time to read all pixel locations once * Always operated in Pulse Count Mode (never Pulse Integration) * High Voltage levels are selectable to adjust sensitivity * 16 analog engineering values are multiplexed to one channel monitored by the CDS and placed in the engineering packet of the telemetry, once per RIM. Items listed in Functional Requirements document Table 1. * Orientation/sectoring EUV uses AACS sector definition: Spin angle=0 when -X axis crosses North Ecliptic Pole and monitors AACS spin angle to control sky sector knowledge EUV thinks starting sector 0 is 45 degrees before North Pole * Encounter Mode The detector address (pixels 0 to 127) of each photon event is returned The top bit of each byte is used for coding sky sector crossings A Wavelength Integration Buffer (WIB) and Sector Integration Buffer (SIB) are kept on-board (16-bit registers) and are read out periodically in the Housekeeping data more... Pg 20 - Feb 7,91 KES THE EUV INSTRUMENT (CONTINUED) * Cruise Mode Analog engineering and housekeeping continue to be returned 1264 bytes for data buffer and FPNT (Fixed Pattern Noise Table) Buffer space is divided up to hold [(number of pixels X number of sky sectors) X (sector size integration factor)]. See table in EUV Software reference. BEWARE: make sure you get the latest copy, earlier table is invalid. Pixels are selected by loading the FPNT with consecutive numbers in the table locations of the desired pixels. Desired photon events are placed into buffer; others are discarded Data acquisition is accomplished by `memory dump' (called Memory Readout, or MRO) to the CDS engineering telemetry stream MROs include the Fixed Pattern Noise Table in order to document which pixels are selected and are thus contained in the buffered data COMMANDING * The EUV command PA (Profile Activity) has changed since launch to accomodate new microprocessor software capable of Cruise Mode operation (necessary when downlink rate does not contain Low Rate Science (LRS) packets, the normal telemetry allocation; below 9600 bits per second.) * Originally had to command Cruise Mode with a Direct Memory Load (DML) command in order to set the Encounter/Cruise bit = 1 * Seven parameters are necessary: Pulse Mode : always use 1 for Pulse Counting High Voltage : 3 is the normal (range is 0 to 7 but a Fight Rule limit is 4; 0 = High Volts Off) Cruise/Encounter : default is Encounter Mode (=1) Start Integration Spin Position : a hex value up to 7F (avoid 0) Sector Size : a hex value up to 7E (avoid 0) Number of Sectors : a hex value up to 7E (avoid 0) See also the PDS instrument template file for the latest version of this information: GLLUVS1:[GLL_RAW.PDS_ARCHIVE.GEN_TEMPLATES]EUV_INST.TEMPLATE Pg 25A - Jan 28,94 KES THE UVS INSTRUMENT FUNCTIONAL DESCRIPTION OPTICAL PATH (See Figure) * Two Fields of View: N & G are (physically) 1.3 x 0.1 deg N & G are (effectively) 1.0 x 0.1 deg F is (physically) 0.4 x 0.1 deg F is (effectively) ___ x 0.1 deg * Slit is oriented so that short side sweeps as Cone changes (long axis is parallel to -Y axis) MICROPROCESSOR SOFTWARE * Micro is an RCA 1802 * 512 bytes RAM * Program takes all but one byte which is used to designate current program version (5.1 as of launch) * 84 byte circular buffer to telemetry: must have LRS (Low Rate Science, =9.6 bits/sec downlink) to take data * Returns 144 bytes of data each second * Instrument's natural time period is 7.6 milliseconds: up to 6.0 msec for integration and 1.6 for data transfer and gratting step; Integrate first then step. * High Voltage overrides are provided for electronic failures * Cold Start mode is hardwired to provided for electronic failures * 18 analog engineering values are incorporated in data stream each Scan (4.333 sec) before data are read (`the Fidutial') * Full Scan or Mini-scan modes (the old `four position' is replaced with mini-scan mode * 84 zeroes are put out by instrument at RIM start (in eformatted data files these appear as 84 "-1" values, at END of previous RIM.) COMMANDING See Functional Requirements for all parameters except those used for scan positions (summary on next page); use following pages for Version 5.1 changes to allow variable wavelength selection and mini-scan positioning. more... Pg 25 - Feb 7,91 KES THE UVS INSTRUMENT (cont) REFORMAT EFFECTS ON UVS DATA * A header of 40 integer values containing time and status is added based on JPL file and spectra alignment (see DISKH:[GLL_RAW.INFO]EHEADER.DOC) for content details * program finds the first data (either a fidutial or data before a fid.) and aligns the data in the output records so that the fidutial (fidutial = the 18 UVS housekeeping values) is the first data in the integer record. The order is as follows a) places (up to) 546 data values into a 600 value integer (2-byte) rec, after the 40 header values b) the first 18 values are the UVS housekeeping (see 4-2034 in the Functional Requirements document) b) adjusts time in header of record to indicate when the first VALID value (seen in the telemetry stream) was actually recorded by the UVS detector; a "-1" value indicates no data for that spectral data position was obtained from t/m * UP vs DOWN grating is NOT corrected for (because it efects time knowledge, ie., time would run backwards through the integer array) * NO F-channel de-compression occurs (a function to do this is available in DISKH:[GLL_RAW.CALIBRATION] * 14 integer records occur for each RIM of time * The instruments puts out 84 zero values at the beginning of each RIM time pulse; these 84 values end up in the output records as the LAST 84 values of a set of 14 spectra (actually as 84 -1 values) with the same RIM time. See also the PDS instrument template file for the latest version of this information: GLLUVS1:[GLL_RAW.PDS_ARCHIVE.GEN_TEMPLATES]UVS_INST.TEMPLATE more... Pg 25 - Feb 8,91 KES LESSONS LEARNED 1) EUV oversampling at Venus and Earth * FPN was not in soon enough nor blocked sufficient counts for amount of sky that was sectored * Way underestimated the amount of `background', suspect: from Van Allen belts * Did get to internal saturation: not just a t/m rate problem 2) Good news and bad: All UVS N-channel lost due to solar sensor shut off 3) Lack of planning knowledge to interpret data: what happening when and additional geometry parameters 4) Lack of EDR training at LASP, disk space problems 5) Comet Austin problem 6) MRO to 24 problem 7) EUV hit during SP to ST 8) All tape recorder knowledge in the hands of S/C therefore no `ground truth' for sequence planning or playback knowledge by DMT >>? DMT 9) UVS grating drive death: Gene McNutt felt that running the grating drive during cruise was the best way to assure that the mechanism did not sieze during the long quiet period so we ran the grating during most of the six years from launch to Jupiter. What we did not foretell however, was that this long period of power-on state to the two optical diodes in the grating drive assembly probably contributed to their eventual loss of sensitivity. Jupiter radiation was most likely also a contributing factor. Eventually the drive optics were no longer able to differentiate the sine/ cosine curve voltage response and the drive was unable to step to the commanded position. Pg 26 - Feb 14,91 KES To: Galileo UVS/EUV team From: Karen Simmons Date: Feb 14,91 Subject: SPICE geometry files We are creating geometry listings from SPICE kernel software for various link observations during Venus and Earth 1 encounters. We are placing these listings on a new directory: DISKH:[GLL_RAW.SPICE_OUTPUT] The file naming convention is as follows: linkname_RIMbeg_RIMend.dtimkey_LIS where linkname = the name one the link associated with this observation (as SYSCAN) RIMbeg = the beginning RIM time RIMend = the ending RIM time dtimkey = an abbreviation for time resolution presented in the file: mf = every minor frame (0.666 sec) mjf = at Major Frames (60.666 sec), or greater Someplace down the line we will be creating IDL Associate files and figuring out a better organization for these products. Suggestions are welcome. Pg 27 - Feb 14,91 KES STUDENT TASKS Tape Manipulation EDR Injestion Tape seal color coding WHITE - Pre-launch SPANed files for both UVS and EUV RED - EUV Final EDRs BLUE - EUV Compressed Final EDRs YELLOW - UVS Final EDRS GREEN - UVS Compressed Final EDRs PURPLE - Sequencing ORANGE - Personal S/W Archives BLACK - BEIGE - SPICE Kernels Tape labeling incl rec'd date or purschase date SPICE Kernel Archiving Label Nomenclature Checking the Kernel Catalog Copy SP Kernels and archiving to tape Copy C Kernelsand archiving to tape Copy Rotor Kernels and archiving to tape Updating Kernal Contents Notebook MRO Processing Editing the MRO_INFO.DAT file (?s/w does this now) end-of-Appendix xx