Radio Science handbook Volume 3 Table of Contents 1. Introduction........................................ Page 1-1 2. Observation Description.................................. 2-1 3. Instrument Description and Configuration................. 3-1 4. Team Organization & Responsibilities .................... 4-1 5. Pre-Pass Preparations ................................... 5-1 6. Real-Time Operations..................................... 6-1 7. Post-Pass Operations..................................... 7-1 8. Data Processing and Validation........................... 8-1 9. Computer Support......................................... 9-1 Appendix A. End-to-End System Diagrams..................... A-1 Appendix B. Useful Formulae................................ B-1 Appendix C. Abbreviations and Acronyms..................... C-1 Appendix D. Directory...................................... D-1 Appendix E. Data Products Log.............................. E-1 Appendix F. Medicina & Kashima & RASM File Transfer........ F-1 Appendix G. Schedule of Activities......................... G-1 SECTION 1 INTRODUCTION 1.0 The Radio Science Handbook 1.1 The Radio Science Almanac 1.2 The Radio Science Library 1.0 The Radio Science Handbook The Radio Science Handbook is an internal reference document prepared and used by the Radio Science Support Team for planning, preparation, real-time operations, post- activity operations, and analysis of the activities listed on the cover page. It contains information, plans, strategies, and procedures to guide and assist the team members to achieve the goals identified for the activities being supported. It also contains descriptions of the various functions and roles, capabilities and facilities of the Radio Science Support Team. This Handbook does not replace Flight Project or DSN documents and procedures. The Project Sequence Of Events (and associated redlines) and the DSN's Network Operations Plan and Keyword File are intended to be the controlling documents for Radio Science activities. Since the Voyager Neptune encounter operations plan, the following volumes have been published by the RSST: 625-460 on February 1, 1990: Radio Science Operations Plan for the Ultrastable Oscillator/Redshift Observations and Venus Range Fix Experiment volume 1 on 15 November 1990: Galileo Earth 1 Flyby/Mass Determination Ulysses First Opposition Test Galileo Redshift Observations/USO Tests volume 2 on June 14, 1991: Ulysses Solar Corona Experiment Galileo Redshift Observations/USO Tests volume 3 on January 10, 1992: Galileo Radio Scintillation Experiment Galileo Redshift Observations/USO Tests Ulysses Jupiter Encounter/IPTO Experiment Ulysses Gravitational Wave Experiment Experiments not addressed above will be included in future volumes of the Handbook. 1.1 The Radio Science Almanac The Radio Science Almanac, shown in Figure 1-1, is a gross schedule of the major Radio Science observation opportunities spanning the period from the Voyager Neptune Encounter through 1993, including the Galileo, Ulysses, and Mars Observer opportunities. The Almanac is used for reference during planning of future Radio Science activities and resource allocation within the support team. Shown in Figure 1-2 is a Galileo Mission Overview which is used to further assist in the planning of Radio Science activities for the Galileo Project through 1997. 1.2 The Radio Science Library The following documents contain information relevant to the Radio Science activities of interest. These documents may be found in the Radio Science Library (230-103A). 1.2.1 Project and DSN Interface Documents 1. Deep Space Network Operations Plan, Project Galileo, document 870-7, Rev. B, Change 2, Sept. 15 1989. 2. Deep Space Network/Flight Project Interface Design Handbook, document 810-5, Rev. D, July 15 1988. 3. Deep Space Network Systems Requirements Detailed Interface Design, document 820-13, Rev. A. 4. Galileo Science Requirements Document, PD 625-50, Rev D, Jan. 18, 1989. 5. Galileo SIRD, PD 625-501, Rev. A, May 1988. 6. Galileo Mission Operations System Functional Requirements, Radio Science System, No MOS-GLL-4-233A, 27 August 1984. (A 1990 update is in preparation). 7. Galileo Orbiter Functional Requirements Document, GLL 3-300B May 9, 1989. 8. Ulysses Radio Science Requirements document, ISPM-PI-2138, issue 4, Updated for 1990 launch. 9. Ulysses SIRD, document 628-6 Rev A April 29, 1989 1.2.2 Articles Relevant to the Science Experiments 1. B. Bertotti, R. Ambrosini, S. W. Asmar, J. P. Brenkle, G. Comoretto, G. Giampieri, L. Iess, A. Messeri, H. D. Wahlquist, "The Gravitational Wave Experiment," Astronomy and Astrophysics suppl. ser. 1, January 1992. 2. Berotti, B. 1983 "The Search for Gravitational Waves with ISPM," in The International Solar Polar Mission - Its scientific Investigation, K. P. Wenzel, R. G. Mardsen and B. Battrick, eds. ESA SP-1050. 3. Thorne, K. S. 1987 "Gravitational Radiation," in Three Hundred Years of Gravitation, S. W. Hawking and W. Israel, eds. Cambridge University Press. 4. T. P. Krisher, J. D. Anderson, J. K. Campbell, "Test of the Gravitational Redshift Effects at Saturn," Physical Review Letters, 19 March 1990, Vol. 64 No. 12. 5. S. W. Asmar, P. Eshe, D. Morabito, "Evaluation of Radio Science Instrument: A Preliminary Report on the USO Performance, 10 August 1990, JPL IOM 3394-90-061. 6. M. K. Bird, S. W. Asmar, J. P. Brenkle, P. Edenhofer, M. Patzold, and H. Volland, "The Coronal-Sounding Experiment," Astronomy and Astrophyiscs suppl. ser. 1, January 1992. 7. R. Woo, "A Synoptic Study of Doppler Scintillation Transients in the Solar Wind," Journal of Geophysical Research, 1 May 1988, vol. 93, No. A5, pp. 3919-3926. 8. J. W. Armstrong, "Spacecraft Gravitational Wave Experiments," Gravitational Wave Data Analysis, B. F. Schutz, ed., 1989, pp. 153- 172. SECTION 2 OBSERVATION DESCRIPTION 2.0 Introduction 2.1 Galileo Gravitational Wave Experiment 2.2 Galileo Solar Wind Scintillation Exp. 2.3 Galileo Redshift Observations/USO Tests 2.4 Galileo Earth Mass Determination 2.5 Ulysses Solar Corona Experiment 2.6 Ulysses Io Plasma Torus Occultation 2.7 Ulysses Gravitational Wave Experiment 2.0 Introduction Radio Science investigators examine the small changes in the phase and/or amplitude of the radio signal propagating from a spacecraft to an Earth receiving station in order to study the atmospheric and ionospheric structure of planets and satellites, planetary gravitational fields, shapes, and masses, planetary rings, ephemerides of planets, solar plasma and magnetic fields, and aspects of the theory of general relativity like gravitational waves, gravitational redshift, etc. The Radio Science experiments described below have been implemented, are in progress, or are planned for the near future for the Galileo and Ulysses projects. Mars Observer and Cassini Radio Science experiments will be described in future volumes of this document. Section 4 list investigators involved in these experiments. This section was prepared with assistance from Drs. J. Armstrong, B. Bertotti, M. Bird, F. Estabrook, L. Iess, T. Krisher, and R. Woo. For quick reference, appendix G shows the exact schedule of tracking times for the experiments list on the cover. Appendix E lists the logs of data acquired for recent experiments. 2.1 Galileo Gravitational Wave Experiment The Galileo Gravitational Wave Experiment will be the most sensitive attempt to date to detect low frequency (i.e., less than ~0.1 Hz) gravitational waves. These gravitational waves are propagating gravitational fields, "ripples" in the curvature of space- time that carry energy and momentum and propagate away from their sources at finite speed. All relativistic theories of gravity agree on the existence of these waves. Theories differ, however, regarding essential properties of the radiation (e.g., number of polarization states, propagation speed). In Einstein's General Relativity, gravitational waves have two polarization states, propagate at the speed of light, and have space-time curvature (or apparent change of relative distances) transverse to the wave propagation direction. The strength of a gravitational wave is characterized by the fractional distance change between test masses caused by the wave: the dimensionless "strain amplitude", h = delta l/l. Gravitational waves can in principle be produced in the laboratory (e.g., by a massive bar spinning about an axis perpendicular to its length) but the resulting signal is far too weak to be detectable with any foreseeable technology. Much stronger gravitational waves are produced by astrophysical sources where there is coherent motion of very massive objects under extremely violent dynamical conditions. These astrophysical gravitational waves are still difficult to detect because they interact so weakly with matter. This property--the extremely weak interaction with matter--means, however, that they propagate unchanged from their sources: detailed information about the time evolution of sources during violent events is preserved, unconfused by subsequent absorption or scattering. (This contrasts with electromagnetic waves, which can be screened or scattered by intervening matter. Even neutrinos produced in supernovae are scattered many times while leaving the cores of those explosions.) Relativistic motion of bulk matter and strong gravitational fields are central to most theoretical views about violent activity in supernovae, galactic nuclei, and quasars. When gravitational waves from these objects are detected, we will have the first observations of the interiors of strong-gravity, high-velocity regions. Different astrophysical sources produce gravitational waves with different temporal behavior. Bursts (which last for at most a few cycles) are produced on a variety of time scales by, e.g., formation or collisions of black holes. Periodic waves (superpositions of one or more sinusoids that are approximately constant in amplitude and frequency over a typical observing time) could be produced, e.g., by binary neutron stars or black holes. Stochastic waves (random fluctuations that persist for times long with respect to the observing interval) could have been produced as a relic of inhomogeneity in the structure of the Big Bang itself. Different detection methods are used, depending on the time scale of the radiation. Various noise sources (notably seismic noise) cause ground-based detectors to be most sensitive to high-frequency (kilohertz) waves. In contrast, space-based detectors are sensitive at low-frequencies because of the large characteristic scale of the experiments (mass separations ~astronomical units) and because of the relatively low "environmental noise" in space. This means that space- based detectors are sensitive to very different astrophysical sources than are laboratory detectors. On these ~10-10,000 second time scales the relevant sources are, e.g., background gravitational waves from the Big Bang, formation and vibrations of supermassive holes in galactic nuclei, and coalescence of massive binary black holes. The Galileo Gravitational Wave Experiment uses the earth and the Galileo spacecraft as free test masses. The Doppler tracking system of the NASA Deep Space Network, driven by an ultra-high- quality frequency standard on the ground, monitors a coherently transponded X-band microwave link with Galileo. In doing so it continuously measures the relative dimensionless velocity (delta v/c) between the Earth and spacecraft. A gravitational wave passing through the solar system produces strain (delta l/l) on the earth- spacecraft system. The result is that the gravitational waveform is replicated three times in the Doppler tracking time series. This three-pulse response is an important signature of a gravitational wave and allows discrimination against phase noise sources in the Doppler measurement system that have different response functions. To maximize the sensitivity of the Galileo Gravitational Wave Experiment to cosmic gravitational waves, extreme care must be taken to minimize effects of perturbing noise sources. These considerations lead to the following experimental requirements: (1) Tracking should be done near solar opposition where the effects of charged particles on the solar wind which randomly perturb the phase of the radio signal ("solar wind phase scintillations") are minimized. (2) Tracking should be done with the X-band uplink capability of the DSN and Galileo. Since solar wind phase scintillation noise scales as (1/radio frequency)2, use of X-band uplink and downlink reduces the plasma noise by more than a factor of 10 compared with previous generation (S-band) experiments. (3) Tracking should be done with hydrogen-maser-quality frequency reference systems. Clock stability is crucial to the sensitivity of the overall experiment and the highest-quality frequency standard should be used to drive the electronics at the stations. (4) Tracking should be two- or three-way, and as continuous as possible. The Doppler mode should be 2- or 3-way so as to reference the experiment to the high-precision ground frequency standard. The tracking should be as continuous as possible to maximize the chance of being "on" during a burst and to give long, relatively complete, records to use in the search for periodic or stochastic waves. (5) Stations should be chosen and configured for maximum sensitivity. This means using the 34-m HEF stations and adjusting tracking operations so as to make the data as stable as possible. (6) Both open- and closed-loop data should be taken. The open-loop data allow the Doppler to be extracted in post-processing in several different ways, building confidence in the reality of candidate events. (7) When possible, there should be an independent, real time assessment of station performance, e.g., with the stability analyzer. This independent assessment of station stability can be used as a "veto" signal, if it detects transient stability problems in the station. Also, the sensitivity of searches for gravitational wave backgrounds can be improved when there is an independent assessment of station stability. (8) The spacecraft should be in as quiet a mode as is feasible. Spacecraft dynamics or perturbations in the radio system that cause noise in the measurements should be minimized. (9) Engineering telemetry relating to spacecraft events, spacecraft spin rate, and state of the radio system need to be taken for correlation with candidate events in the Doppler time series. The Galileo spacecraft and the 34-m HEF X-band uplink combine to make this experiment much more sensitive than previous searches. The improved sensitivity means that candidate noise sources that were ignorable in previous generation experiments now need to be considered. Spacecraft events that affect the Doppler observable need to be recorded and integrated with the Doppler data to act as "veto signals" in the analysis. (10) Tropospheric and ionospheric calibration data, to the extent available, should be gathered to assess the effect of these propagation noise sources and, if possible, calibrate and remove them. (11) "Calibration signals" should occasionally be introduced into the data to verify performance. A possible way to do this is to occasionally (perhaps once per pass, for a duration of about 5 minutes), introduce known, systematic variations in the phase by moving the subreflector to a new position and then moving it back to its (fixed) position for the rest of the pass. 2.2 GALILEO SOLAR WIND SCINTILLATION EXPERIMENT Although the most interesting region of the solar wind is that surrounding the Sun, it has not yet been observed directly by spacecraft measurements. Until missions such as Solar Probe are flown, we must rely on remote sensing techniques with planetary spacecraft such as Galileo to probe the inner heliosphere. Radio scintillation and scattering measurements conducted during the Galileo superior conjunctions represent a powerful and essentially only tool for studying the complicated solar wind structure near the Sun. The Galileo solar wind radio scintillation experiment is based on observations of radio scattering phenomena that arise from the propagation of radio waves through the turbulent plasma of the solar wind. These consist of Doppler and amplitude scintillations (fluctuations), as well as broadening of Galileo's monochromatic S- band signal (spectral broadening). Characteristics of these phenomena and the deduced solar wind structure are obtained from the processing of wideband DSP recordings of the Galileo radio signal. Successful DSP recordings are, therefore, important to the scintillation experiment. Interplanetary disturbances, which are manifested as transients in the scintillation and spectral broadening measurements, are of particular interest in the Galileo experiment. Correlations with events observed on the Sun (e.g., flares) and at spacecraft located near 1 AU (e.g., Pioneer Venus) will be made. These correlative studies are clearly most effective if continuous radio scintillation data are available. For this reason, prolonged periods of near- continuous tracking of Galileo have been arranged. During the approximately ±1 month period surrounding superior conjunction, the Galileo radio signal will be probing the solar wind within about 0.3 AU of the Sun. 2.3 Galileo Redshift Observations & USO Tests The Redshift Observations are performed to measure the frequency shift caused by the motion of the spacecraft as it moves in and out of the solar (or planetary) gravitational field. One of the four predicted effects of Einstein's theory of General Relativity is the change of a clock rate (an oscillator frequency) in a varying gravitational potential. The Galileo Ultra Stable Oscillator (USO) is the signal source for these observations and has sufficient inherent stability to allow detection of this phenomenon. The Galileo VEEGA trajectory provides a unique opportunity to detect the USO frequency shift as it flies through the changing solar and planetary gravitational fields. The objectives of the Redshift Observations and USO tests are: 1. Make a direct scientific measurement of the redshift phenomenon described above. 2. Make engineering measurements of the USO frequency and frequency stability for calibration of the Radio Science instrument. 3. Exercise the operational aspects of the Radio Science system in the Project and at the Deep Space Network. 4. Train the Project (including the Radio Science Support Team) and the DSN in the operations required in preparation for the Jupiter Encounter. 5. Exercise the Radio Science software and analysis tools. Prior to the observations, the orbiter will be commanded to use the USO as the frequency reference for the downlink radio signal for a period of about two hours. The frequency and frequency stability of the carrier will be estimated. When the data are received by the RSST, either in the form of tracking ATDFs and, for some passes, open-loop ODRs, they will then be processed to produce frequency residuals. From these, phase noise and frequency stability (Allan variance) can be determined. 2.4 Galileo Earth Mass Determination As part of Galileo's Venus-Earth-Earth Gravity Assist (VEEGA) trajectory, the spacecraft will fly by Earth twice at which time the Galileo Radio Science Team will attempt to measure the mass of the Earth (GM) using the radio link, specifically by measuring the Doppler and range. During the Earth flyby, the velocity vector of the Galileo spacecraft will change such that the heliocentric energy of the spacecraft will be increased. The amount the velocity vector is changed (or the amount the trajectory is bent) is a function of the spacecraft approach velocity, the Earth flyby distance and the Earth gravitational potential. The gravitational potential is determined by the product of the gravitational constant, G, and the Earth Mass divided by the distance; thus -GM/r. The spacecraft's Earth approach and departure state vectors are determined from the tracking data acquired before and after closest approach. To separate the effects of the Earth gravitational potential, - GM/r, and flyby distance, r, tracking data near perigee is required. The Doppler and range tracking data provide a nearly direct measure of flyby distance which leaves the Earth GM as a derived quantity. Unfortunately, most of the two-way tracking data near perigee may be lost due to operational limitations, so the Galileo Earth mass determination will probably not provide a significant improvement in the estimate of the Earth GM compared to previous spacecraft launch trajectory estimates and Earth orbiting satellite estimates. 2.5 Ulysses Solar Corona Experiment The Ulysses Solar Corona Experiment (SCE), conducted during the solar conjunctions, performs coronal-sounding measurements (see reference in section 1.2). The SCE utilizes dual frequency (S- and X- bands) Doppler and range data to determine the density, velocity, and turbulance spectrum of the Sun's atmosphere to distances well below 10 solar radii. Radio-sounding observations are sensitive to plasma parameters in the main acceleration regime of the solar wind. The Doppler and ranging data will be used to derive the three dimensional distribution of the coronal electron density. The large scale structure can be inferred from the total electron content obtained from the dual frequency ranging. The dual-frequency Doppler is more sensitive to relative changes in the electron content. The dual-frequency Doppler data will also be used to characterize the level and spectral index of coronal turbulence. Another plasma parameter obtained from radio sounding is the velocity. The most reliable measurements of this type are obtained from cross correlation of radio scintillation using multiple signal ray paths. It is anticipated that the interplanetary vestiges of a coronal mass ejection will be occasionally detected as significant perturbation in the ranging and Doppler data. 2.6 Ulysses Io Plasma Torus Occultation Experiment The Ulysses spacecraft will be occulted by the Io Plasma Torus (IPT) during its Jupiter encounter on February 8, 1992. The Ulysses dual-frequency radio subsystem can be utilized to measure the electron content of the IPT. This can be inverted using appropriate models to derive the electron density distributions for the two cross sections (front and rear lobes of the IPT, respectively) cut by the signal ray path. The attached figures show the experiment geometry. The only previous performance of this experiment occurred during the Voyager 1 flyby on March 5, 1979. The clear signature of the IPT obtained at that opportunity is found in Eshleman et. al., 1979 and Levy et. al., 1981. A more comprehensive post-analysis of the data revealed the IPT on both the ingress and egress legs of the Voyager trajectory. Some consideration was given to the possibility of staging an occultation by Io's disk itself - a feat that was accomplished thus far only by Pioneer 10. Unfortunately, this would have imposed severe restrictions on spacecraft operations during encounter and would have slightly degraded the post-Jupiter heliocentric orbit parameters. 2.7 Ulysses Gravitational Wave Experiment The experiment is described in detail in reference 1 of section 1.2.2. The Ulysses Gravitational Wave Experiment is designed to attempt detection of low frequency (i.e., in the mHz band) gravitational waves. Possible astrophysical sources in this frequency band are: collapse and collisions of black holes in the nuclei of galaxies and quasars; periodic wave trains emanating from massive orbiting binary black holes; or an isotropic background of cosmological origin. For this experiment, Doppler tracking is most sensitive to waves whose characteristic time scale * is shorter than the round-trip-light-time, T. Since one expects all the above sources to be stronger at lower frequencies, it is important to extend the measurement to as low a frequency as possible. Also, at frequencies lower that 1/T, the effect of the fluctuations in the interplanetary plasma are better compensated by the incomplete radio frequency link available on Ulysses. These considerations point to two crucial experimental requirements: (1) The tracking should be divided in continuous periods of longest possible duration by overlapping station passes. Particular care must be taken in the station handover procedures to minimize gaps in the data. (2) Both X- and S-band should be available during the test to partially eliminate the plasma noise, which is greater at lower frequencies. This will be done also by using a special algorithm being developed which allows a prediction of uplink plasma content from the measured downlink content. The Ulysses Radio Science experiments will use the 70-m (DSS 14, 43, 63) and 34-m STD (DSS 12, 42, 61) stations (will not use 34 meter HEF stations because Ulysses does not utilize X-band uplink and the Radio Science experiments will be in the two-way mode). The data observables are closed-loop Doppler, range, DRVID, and open-loop data from each station; except for DSS 12 which is not equipped with open-loop data acquisition capability. SECTION 3 INSTRUMENT DESCRIPTION AND CONFIGURATION 3.0 Introduction 3.1 The Galileo Spacecraft 3.2 The Ulysses Spacecraft 3.3 The Deep Space Network 3.4 Other Facilities 3.5 DSS Calibration and Configuration 3.0 Introduction This section describes the instrumentation used in support of the Radio Science activities. The Radio Science instrument is distributed between the spacecraft and the Ground Data System (GDS). The latter includes several subsystems at the Deep Space Communication Complexes (DSCCs) as well as several facilities at JPL used for Radio Science communications and data monitoring. 3.1 The Galileo Spacecraft The Galileo spacecraft is shown on Figure 3-1. The Galileo telecommunications subsystem is shown is Figure 3-2. It handles three types of data: command, telemetry, and radiometric. The latter provides the capability to navigate the orbiter as well as perform Radio Science observations. The subsystem is equipped with two redundant transponders with dual frequency (S- and X-bands) uplink and downlink capabilities. The subsystem may be operated in the coherent mode, in which the downlink signal is referenced to the uplink signal, or the non- coherent mode, where an ultrastable oscillator (USO) onboard the spacecraft provides the downlink signal reference. In the absence of an uplink signal, the subsystem will switch to the one-way mode. Commands to the spacecraft also determine the mode as well as the selection one of the following: spacecraft modulated telemetry alone, ranging alone, spacecraft telemetry and ranging, or carrier alone. A tape recorder onboard the spacecraft will store data for playback at a later time during periods when no ground station coverage is available. The HGA is aligned with the spin axis of the spacecraft and is pointed at the Earth by the attitude control system. Low Gain Antenna 1 (LGA-1) is located at the end of the HGA feed and is thus aligned with the spin axis. Low Gain antenna 2 (LGA-2) is located at the end of a boom as shown in Figure 3-1. When the signal is transmitted through LGA-2, a sinusoidal signature in the received Doppler is induced since the spacecraft is spinning with the antenna being located 3.58 meters off the spin axis. Figure 3-4 shows the radio frequency system of the Ulysses spacecraft. The system includes two S-band low gain antennas (LGA) for near-Earth communications and an S- and X-band high gain parabolic antenna (HGA) for deep space communications. The antennae are coupled to two redundant transponders, a 5 W S-band power amplifier and an X- band exciter. The 20 W X-band output is produced by one of the two redundant TWTAs. The system has a considerable amount of cross- coupling. Each receiver may drive either, or both, modulators. Each X- band exciter may drive either of the two TWTAs. The output of the modulator is switched to drive either the S-band power amplifier or the X- band exciter, but not both. For modes where simultaneous S- and X-band downlinks are required, a chosen receiver drives the modulators of both transponders. One transponder then drives the S-band power amplifier and the other transponder drives the X-band exciter and a TWTA. The transponders function in one of two modes: the coherent mode, in which the downlink signal is referenced to the uplink signal, and the non-coherent mode, where a free-running oscillator onboard the spacecraft provides the downlink signal reference. Commands to the spacecraft determine the selection one of the following: spacecraft modulated telemetry alone, ranging alone, spacecraft telemetry and ranging, or carrier alone. Simultaneous ranging and commanding is not an operational mode of the Ulysses spacecraft. A tape recorder onboard the spacecraft will store telemetry data during periods when no ground station coverage is available for playback at a later time. The HGA is aligned with the spin axis of the spacecraft and is pointed to Earth by control of the spin axis in inertial space. Typically, a daily attitude manoeuver is performed. To perform this control, one reference is given by a sun-sensor while the other is given from CONSCAN processing of the uplink radio signal from Earth. For this reason, the S-band feed of the antenna is slightly offset from the spin axis. There is a minimum limit on the sun-probe-earth angle that can be tolerated thus forcing operational strategies for attitude control during conjunctions and oppositions. For the Radio Science experiments, the radio system will be configured in the two- way coherent mode and both the S-band and X- band links will be activated simultaneously (thermal limitations onboard the spacecraft may operationally prevent activating dual links at certain times). In this configuration, both transponders receive the same S-band uplink signal which is referenced to a highly stable Hydrogen maser frequency standard at the DSS, and transmit coherent S- band and X-band downlink signals. The dual frequency coherent link is used by the experimenters to measure the differential range and Doppler to determine the total electron content along the spacecraft to Earth line of sight. The data are also used to measure the rate of change of the total electron content in the interplanetary and ionospheric plasma to correct the Doppler for these effects. 3.3 The Deep Space Network The Deep Space Communication Complexes (DSCCs) are an integral part of the Radio Science instrument, along with the other receiving stations and the spacecraft's Radio Frequency Subsystem. Their system performance directly determines the degree of success of the Radio Science investigations and their system calibration determines the degree of accuracy in the results of the experiments. The following paragraphs describe those functions performed by the individual subsystems of a DSCC. Figures 3-5 through 3- 10 show the various systems relevant to the Radio Science activities. 3.3.1 DSCC MONITOR AND CONTROL SUBSYSTEM The DSCC Monitor and Control Subsystem (DMC) is part of the Monitor and Control System (MON) which also includes the ground communications Central Communications Terminal and the Network Operations Control Center (NOCC) Monitor and Control Subsystem. The DMC is the center of activity at a DSCC. The DMC receives and archives most of the information from the NOCC needed by the various DSCC subsystems during their operation. Control of most of the DSCC subsystems as well as the handling and displaying of any responses to control directives and configuration and status information received from each of the subsystems is done through the DMC. The effect of this is to centralize the control, display and archiving functions necessary to operate a DSCC. Communication between the various subsystems is done using a Local Area Network (LAN) hooked up to each subsystem via a Network Interface Unit (NIU). The DMC operations are divided into two separate areas: the Complex Monitor and Control (CMC) and the Link Monitor and Control (LMC). The primary purpose of the CMC processor for Radio Science support is to receive and store all predict sets transmitted from NOCC such as Radio Science, antenna pointing, tracking, receiver, and uplink predict sets and then, at a later time, distribute them to the appropriate subsystems via the LAN. Those predict sets can be stored in the CMC for a maximum period of three days under normal conditions. The CMC also receives, processes and displays event/alarm messages and maintains an operator log and produces tape labels for the DSP. Assignment and configuration of the LMCs is done through the CMC and to a limited degree the CMC can perform some of the functions performed by a LMC. There is one on-line CMC, one backup CMC, and three LMCs at each DSCC. The backup CMC can function as an additional LMC if necessary. The LMC processor provides the operator interface for monitor and control of a link which is a group of equipment required to support a spacecraft pass. For Radio Science, a link might include the DSCC Spectrum Processing Subsystem (DSP) (which, in turn, can control the SSI), or the Tracking Subsystem. The LMC also maintains an operator log which includes the operator directives and subsystem responses. One important Radio Science specific function the LMC performs is receipt and transmission of the system temperature and signal level data from the PPM for display at the LMC console as well as placing this information in the Monitor 5-9 blocks. These blocks are recorded on magnetic tape as well as displayed in the MCCC displays. The LMC is required to operate without interruption for the duration of the Radio Science data acquistion period. The Area Routing Assembly (ARA), which is part of the Digital Communications Subsystem, controls all data communication between the stations and JPL. The ARA receives all required data and status messages from the LMC/CMC and can record them to tape as well as transmit them to JPL via the data lines. The ARA also receives predicts and other data from JPL and passes them on to the CMC. 3.3.2 DSCC ANTENNA MECHANICAL SUBSYSTEM The multi-mission Radio Science activities require support from the 70-m, the 34-m HEF, and the 34-m STD antenna subnets. The antenna at each DSCC will function as a large aperture collector which, by double reflection, causes the incoming RF energy to enter the feed horns. The large collecting surface of the antenna focuses the incoming energy onto a subreflector, which is adjustable in the axial and angular positions. These adjustments are made to optimize the channeling of energy from the primary reflector to the subreflector and then to the feedhorns. The 70-m and 34-m HEF antennas have "shaped" primary and secondary reflectors, whose forms are that of a modified paraboloid. This customization allows more uniform illumination of one reflector by the other. Conversely, the 34-m STD primary reflectors are classical paraboloids, while the subreflectors are similarly standard hyperboloids. On the 70-m and 34-m STD antennas, the subreflector reflects the received energy from the antenna onto the dichroic plate, a device which reflects S-band energy to the S-band feedhorn and passes X-band energy through to the X-band feedhorn. In the 34-m HEF, there is one "common aperture feed", which accepts both frequencies, and therefore no plate. RF energy to be transmitted into space by the horns is focused by reflectors into narrow cylindrical beams, pointed with high precision (either to the dichroic plate or directly to the subreflector) by a series of drive motors and gear trains that can rotate the movable components and their support structures. The different antennas can be pointed by several common means. Two pointing modes commonly used during a tracking pass are 1) CONSCAN on, or 2) CONSCAN off (blind pointing). With CONSCAN on, once the a closed-loop receiver has acquired a signal from the spacecraft to provide feedback, the radio source is tracked by conically scanning around it. Pointing angle adjustments are computed from signal strength information supplied by the receiver. In this mode, the Antenna Pointing Assembly (APA) generates a circular scan pattern which is sent to the Antenna Control Subsystem (ACS). The ACS adds the scan pattern to the corrected pointing angle predicts. Software in the receiver-exciter controller computes the received signal level and sends it to the APA. The correlation of the scan position of the antenna with the received signal level variations allows the APA to compute offset changes which are sent to the ACS. Thus, within the capability of the closed-loop control system, the scan center is pointed precisely at the apparent direction of the spacecraft signal. An additional function of the APA is to provide antenna position angles and residuals, antenna control mode/status information and predict-correction parameters to the Area Routing Assembly (ARA) via the LAN, which then sends this information to JPL via the GCF for antenna status monitoring. However, during periods when excessive signal level dynamics or low received signal levels are expected (e.g., in an occultation experiment), CONSCAN cannot be used. Under these conditions, blind pointing (CONSCAN off) is used, and pointing angle adjustments rely on a predetermined Systematic Error Correction (SEC) model. Independent of the CONSCAN state, subreflector motion in at least the z-axis may introduce phase variations in the received Radio Science data. For that reason, during certain experiments, the subreflector in the 70-m and 34-m HEFs may be frozen in the z-axis at an elevation angle selected to minimize the phase change and signal degradation. This can be done via operator OCIs from the LMC to the subreflector Controller (SRC) which resides in the alidade room of the antennas. The SRC passes the commands to motors that drive the subreflector to the desired position. Unlike the two antennas mentioned above, the 34-m STD is not an Az-El pointed antenna, but a HA-DEC antenna. The same positioning of the subreflector of the 34-m STD does not create the same effect as for the 70-m and 34-m HEF. Pointing angles for all three antenna types are computed by the NSS from an ephemeris provided by the Project and converted into antenna pointing predicts for each station. These predicts are received and archived by the CMC. Before each track, they are transferred to the APA, which transforms the direction cosines of the predicts into Az-El coordinates for the 70-m and 34-m HEF, and into HA-DEC coordinates for the 34-m STD. The LMC operator then downloads the antenna Az-El or HA-DEC (respectively) predict points to the antenna-mounted ACS computer along with a selected pointing SEC model. The pointing predicts consist of time-tagged Az-El or HA-DEC points at selected time intervals, and also include polynomial coefficients for interpolation between the points. The ACS automatically interpolates the predict points, corrects the pointing predicts for refraction and subreflector position, and adds the proper systematic error correction and any manually entered antenna offsets. The ACS then sends angular position commands for each axis at the rate of once per second. In the 70-m and 34-m HEF, rate commands are generated from the position commands at the servo controller and are subsequently used to steer the antenna. In the 34-m STD, motors, not servos, are used to steer the antenna, so there is no feedback once the antenna has been told where to point. When not using binary predicts (the routine mode for spacecraft tracking), the antennas can be pointed using planetary mode, a simpler mode which uses right ascension (RA) and declination (DEC) values. These change very slowly with respect to the celestial frame. Values are provided to the station in text form for manual entry. The ACS quadratically interpolates RA and DEC three points on one-day centers. Other than predict and planetary, a third mode, sidereal, is available and is usually used to track radio sources fixed with respect to the celestial frame as in radio astronomy applications. Regardless of the mode being used to track a spacecraft, a 70-m antenna has a special, high-accuracy pointing capability called Precision mode. A pointing control loop derives the main Az-El pointing servo drive error signals from a two-axis autocollimator mounted on the Intermediate Reference Structure. The autocollimator projects a light beam to a precision mirror mounted on the Master Equatorial drive system, a much smaller structure, independent of the main antenna, which is exactly positioned in HA and DEC with shaft encoders. The autocollimator detects elevation/cross-elevation errors between the two reference surfaces by measuring the angular displacement of the reflected light beam. This error is compensated for in the antenna servo by moving the antenna in the appropriate (Az- El) direction. If not using the optical link Precision mode, a less accurate computer mode can be used where the servo utilizes the Az-El axis encoder readout for positioning, as done in the 34-m HEF. 3.3.3 DSCC ANTENNA MICROWAVE SUBSYSTEM 3.3.3.1 70-m Anetennas Each 70-m station has three feed cones installed on a structure at the center of the main reflector. The feeds are positioned 120 degrees apart on a circle. Selection of the feed is made by rotation of the subreflector. A dichroic mirror assembly, half on the S-band cone and half on the X-band cone, permit simultaneous use of the S- and X-band frequencies. The third cone is devoted to R&D and more specialized work. The Antenna Microwave Subsystem (AMS) accepts the received S- and X- band signals at the feedhorn and transmits them through the polarizer plates to the orthomode transducer. The polarizer plates are adjusted so that the signals are directed to either of a set of redundant amplifiers for each frequency. For X-band, these amplifiers are Block IIA X-band Travelling Wave Masers (TWMs), and for S-band there are two Block IVA S-band TWMs. 3.3.3.2 34-m STD Antennas These antennas have two feed horns, for S- and X-band energy, respectively. These horns are mounted on a cone which is fixed in relation to the subreflector. A dichroic plate mounted above the horns directs energy from the subreflector into the proper horn. The AMS directs the received S- and X-band signals through the polarizer plates and on to amplification. There are two Block III S- band TWMs and two Block I X-band TWMs. 3.3.3.3 34-m HEF Antennas Unlike the other antennas, the 34-m HEF uses a single feed horn for both X- and S-band. Simultaneous S- and X-band receive, as well as X-band transmit, is possible however, due to the presence of an S/X "combiner", which acts as a diplexer. As in the general case, the next component in the AMS on the X-band path is a polarizer, and then the orthomode transducer; for S-band, RCP or LCP is user selected through a switch, and not simultaneous, so neither device is present. X-band amplification can be selected from one of two Block II X-band TWMs or from a single X-band HEMT Low Noise Amplifier (LNA). S-band amplification is provided by one FET LNA. 3.3.4 DSCC RECEIVER-EXCITER SUBSYSTEM The Receiver-Exciter Subsystem is composed of three groups of equipment: the closed-loop receiver group, the open-loop receiver group, and the RF monitor group. This subsystem is controlled by the Receiver-Exciter Controller (REC) which communicates directly with the DMC for predicts and OCI reception and status reporting. The exciter generates the S-band signal, (or X-band signal for 34-m HEF only), which is provided to the Transmitter Subsystem for the spacecraft uplink signal. It is tunable under the command of the Digitally Controlled Oscillator (DCO) which receives predicts from the Metric Data Assembly (MDA). The diplexer in the signal paths between the transmitters and the feed horns for all three antennas (used for simultaneous transmission and reception) may be configured such that it is out of the received signal path (in listen-only or bypass mode) in order to improve the signal-to-noise ratio in the receiver system. 3.3.4.1 Closed-Loop Receivers The Block IV receiver-exciter at the 70-m stations allows for two receiver channels, each capable of L-band, S-band or X-band reception, and an S-band exciter for generation of uplink signals through the low-power or high-power transmitter. The Block III receiver-exciter at the 34-m STD stations allows for two receiver channels, each capable of S-band or X-band reception and an exciter used to generate an uplink signal through the low-power transmitter. The receiver-exciter at the 34-m HEF stations allows for one channel only. The closed-loop receivers provide the capability for rapid acquisition of a spacecraft signal and telemetry lockup. In order to accomplish acquisition within a short time, the receivers are predict driven to automatically search for, acquire, and track the downlink. Rapid acquisition precludes manual tuning even though the latter remains as a backup capability. The subsystem utilizes FFT analyzers for rapid acquisition. The predicts are NSS generated, transmitted to the CMC which sends them to the Receiver-Exciter Subsystem where two sets could be stored. The receiver starts acquisition at uplink time plus one round-trip-light-time or at operator specified times. In addition, the receivers can be operated from the LMC without a local operator attending them. The receivers send performance and status data, displays, and event messages to the LMC. Either the exciter synthesizer signal or the SIM synthesizer signal is used as the reference for the Doppler extractor, depending on the spacecraft being tracked (and Project guidelines). The SIM synthesizer is not ramped, instead, it uses one constant frequency, Track Synthesizer Frequency, (TSF) which is an average frequency for the entire pass. The closed-loop receiver AGC loop can be configured to one of three settings; narrow, medium or wide. It will be configured such that the expected amplitude changes are accommodated with minimum distortion. The loop bandwidth (2BLo) will be configured such that the expected phase changes can be accommodated while maintaining the best possible loop SNR. 3.3.4.2 Radio Science Open-Loop Receiver The Radio Science Open-Loop Receiver (OLR) is a dedicated four channel, narrow-band receiver which provides amplified and downconverted video band signals to the DSCC Spectrum Processing Subsystem (DSP). The OLR utilizes a fixed first Local Oscillator (LO) frequency and a tunable second LO frequency to minimize phase noise and improve frequency stability. The OLR consists of an RF-to-IF downconverter located in the antenna, an IF selection switch (IVC), and a Radio Science IF-VF downconverter (RIV) located in the SPC. The RF-IF in the 70-m antenna are equipped for four IF channels: XRCP, SRCP, XLCP, and SLCP. The 34-m HEF stations are equipped with a two-channel RF-IF: S- band and X-band. The IVC switches between IFs from the 70-m and 34-m HEF stations. The RIV contains the tunable second LO, a set of video bandpass filters, IF attenuators, and a controller (RIC). The LO tuning is done via DSP control of the POCA/PLO combination based on a predict set. The POCA is a Programmable Oscillator Control Assembly and the PLO is a Programmable Local Oscillator (commonly called the DANA synthesizer). The bandpass filters are selectable via the DSP. The RIC provides an interface between the DSP and the RIV. It is controlled from the LMC via the DSP. The RIC selects the filter and attenuator settings and provides monitor data to the DSP. The RIC could also be manually controlled from the front panel in case the electronic interface to the DSP is lost. Figures 3-7 and 3-8 (A,B,C) show block diagrams of the open-loop receiver. Calibrations will be performed on the OLR and the DSP NBOC using estimates of the peak signal levels expected during the experiments as described in section 3.5. 3.3.4.3 RF Monitor: SSI and PPM The RF monitor group of the Receiver-Exciter Subsystem provides spectral measurements using the Spectral Signal Indicator (SSI), and measurements of the received channel system temperature and spacecraft signal level using the Precision Power Monitor (PPM). The SSI provides a local display of the received signal spectra at a dedicated terminal at the DSCC and routes these same data to the DSP which routes them to NOCC for remote display at JPL for real-time monitoring and RIV/DSP configuration verification. These displays are used to validate Radio Science System data at the DSS, NOCC, and Mission Support Areas. The SSI configuration is controlled by the DSP and a duplicate of the SSI spectrum appears on the LMC via the DSP. During real-time operations, the SSI data also serve as a quick look science data type for the Radio Science experiments. The PPM measures system noise temperatures (SNT) using a Noise Adding Radiometer (NAR) and downlink signal levels using the Signal Level Estimator (SLE). The PPM accepts its input from the closed-loop receiver. SNT is measured by injecting known amounts of noise power into the signal path and comparing the total power with the noise injection "on" against the total power with the noise injection "off". That operation is based on the fact that receiver noise power is directly proportional to temperature, and thus measuring the relative increase in noise power due to the presence of a calibrated thermal noise source allows direct calculation of SNT. Signal level is measured by calculating an FFT to estimate the SNR between the signal level and the receiver noise floor whose power is known from the SNT measurements. There is one PPM controller at the SPC which is used to control all SNT measurements. The SNT integration time can be selected to represent the time required for a measurement of 30 K to have a 1- sigma uncertainty of 0.3 K or 1%. 3.3.5 DSCC TRANSMITTER SUBSYSTEM The Transmitter Subsystem accepts the S-band frequency exciter signal from the Block III or Block IV Receiver-Exciter Subsystem exciter and amplifies it to the required transmitted output level. The amplified signal is routed via the diplexer through the feedhorn to the antenna and then focused and beamed to the spacecraft. The Transmitter Subsystem power capabilities range from 18 kW to 400 kW. Power levels above 18 kW are available only at 70-m stations. 3.3.6 DSCC TRACKING SUBSYSTEM The Tracking Subsystem's primary functions are to acquire and maintain the communications link with the spacecraft and to generate and format radiometric data containing Doppler and range. A block diagram of the DSN tracking system appears in Figures 3-9 and 3-10. The DSCC Tracking Subsystem (DTK) receives the carrier signals and ranging spectra from the Receiver-Exciter Subsystem. The Doppler cycle counts are counted, formatted, and transmitted to JPL in real- time. Ranging data are also transmitted to JPL in real-time. Also contained in these blocks is the AGC information from the Receiver- Exciter Subsystem. The Radio Metric Data Conditioning Team (RMDCT) at JPL produces an ATDF tape which contains Doppler and ranging data. In addition, the Tracking Subsystem receives from the CMC frequency predicts (used to compute frequency residuals and noise estimates), receiver tuning predicts (used to tune the closed-loop receivers), and uplink tuning predicts (used to tune the exciter). From the LMC, it receives configuration and control directives as well as configuration and status information on the transmitter, microwave and frequency and timing subsystems. The Metric Data Assembly (MDA) controls all of the DTK functions supporting the uplink and downlink activities. The MDA receives uplink predicts and controls the uplink tuning by commanding the DCO. The MDA also controls the SRA. It formats the Doppler and range measurements and provides them to the GCF for transmission to NOCC. The Sequential Ranging Assembly (SRA) measures the round trip light time (RTLT) of a radio signal traveling from a ground tracking station to a spacecraft and back. >From the RTLT, phase, and Doppler data, the spacecraft range is measured. A coded signal is modulated on an S-band carrier and transmitted to the spacecraft where it is detected and transponded back to the station. As a result, the signal received at the tracking station is delayed by its round trip through space and shifted in frequency by the Doppler effect due to the relative motion between the spacecraft and the tracking station on Earth. 3.3.7 DSCC SPECTRUM PROCESSING SUBSYSTEM (DSP) The DSCC Spectrum Processing Subsystem (DSP) located at the SPC digitizes and records on magnetic tapes the narrowband output data from the RIV. It consists of a Narrow Band Occultation Converter (NBOC) containing four Analog-to-Digital Converters (ADCs), a ModComp CLASSIC computer processor called the Spectrum Processing Assembly (SPA) and two to six magnetic tape drives. The DSP is operated through the LMC. Using the SPA-R software, the DSP allows for real-time frequency and time offsets (while in RUN mode) and, if necessary, snap tuning between the two frequency ranges transmitted by the spacecraft: coherent and noncoherent. The DSP receives Radio Science frequency predicts from the CMC, allows for multiple predict set archival (up to 60 sets) at the SPA and allows for manual predict generation and editing. It accepts configuration and control data from the LMC, provides display data to the LMC and transmits the signal spectra from the SSI as well as status information to NOCC and the Project Mission Support Area (MSA) via the GCF data lines. The DSP records the digitized narrowband samples and the supporting header information (i.e., time tags, POCA frequencies, etc.) on 9-track computer compatible magnetic tapes in 6250 or 1600 bpi GCR format. The data format on the tape (called Original Data Record, ODR) is defined in document 820-13 module RSC-11-10A. Through the DSP-RIC interface, the DSP controls the RIV's filter selection and attenuation levels. It also receives RIV performance monitoring via the RIC. In case of failure of the DSP-RIC interface, the RIV can be controlled manually from the front panel. All the RIV and DSP control parameters and configuration directives are stored in the SPA in a macro-like file called an "experiment directive" table. A number of default directives exist in the DSP for the major Radio Science experiments. Operators can create their own table entries. The items controlled by the directive are shown in section 3.5. Items such as verification of the configuration of the prime open-loop recording subsystem, the selection of the required predict sets, and proper system performance prior to the recording periods will be checked in real-time at JPL via the NOCC displays using primarily the remote SSI display at NOCC and the NRV displays. Because of this, transmission of the DSP/SSI monitor information is enabled prior to the start of recording. The specific run time and tape recording times will be identified in the SOE. The DSP can be used to duplicate ODRs. It also has the capability to play back a certain section of the recorded data after the conclusion of the recording periods. 3.3.8 DSCC FREQUENCY AND TIMING SUBSYSTEM The Frequency and Timing Subsystem (FTS) provides all frequency and timing references required by the other DSCC subsystems. It contain four frequency standards of which one is prime and the other three are backups. Selection of the prime standard is done via the CMC. Of these four standards, there are two Hydrogen masers followed by clean-up loops (CUL) and two Cesium standards. These four standards all feed the Coherent Reference Generator (CRG) which provides the frequency references used by the rest of the complex. It also provides the frequency reference to the Master Clock Assembly (MCA) which in turn provides time to the Time Insertion and Distribution assembly (TID) which provides UTC and SIM-time to the complex. The monitoring capabilities of the DSCC FTS at JPL are limited to the MDA calculated Doppler pseudo-residuals, the Doppler noise, the SSI, and via the GPS. The GPS receivers receive a one-pulse-per-second pulse from the station's (Hydrogen maser referenced) FTS and a pulse from a GPS satellite at scheduled times. After compensating for the satellite signal delay, the timing offset is reported to JPL where a database is kept. The clock offsets reported in the JPL database between the clocks at the three DSN sites are given in microseconds, where each reading is a mean reading of measurements from several GPS satellites and the time tag associated with it is a mean time of the measurements. The clock offsets provided include those of SPC 10 relative to UTC(NIST), SPC 40 relative to SPC 10,...,etc. 3.4 Other Facilities 3.4.1 GROUND COMMUNICATIONS FACILITY The Ground Communications Facility (GCF) provides the communication networks needed to support the communication requirements of the Radio Science System. These facilities exist at the DSCC and JPL and are briefly described in the following paragraphs. 3.4.2 GCF DATA SUBSYSTEM Communication with DSN complexes takes place over the Ground Communication Facility (GCF) data lines. See section 9 for a discussion of the normal configuration of these lines. These lines transmit Radio Science open-loop tuning predicts from the NOCC to the DSS (and CTA-21) and sends Radio Science, Tracking and Monitor and Control Subsystems status and configuration data from the DSCC to the NOCC in real-time. After the completion of a Radio Science recording period, this subsystem can be used to send Radio Science data from the DSCC to the NOCC. 3.4.3 GCF DATA RECORDS SUBSYSTEM The GCF Data Records Generator (DRG) formats the incoming closed-loop data from the DSCC and provides them to the RMDCT team which converts the Doppler and range data into computer-compatible tapes called Archival Tracking Data Files (ATDF). 3.4.4 VOICE NET COMMUNICATIONS The Ground Communications Facility voice nets provide both the means of controlling worldwide spacecraft tracking operations and for relaying information required to verify proper operation of the various ground and spacecraft subsystems. Section 6 contains a description of the voice nets as it is planed for the Radio Science activities 3.4.5 RODAN INTERFACE Data lines from GCF to RODAN allow the RSST to capture and display Radio Science data from the GCF lines. See Section 9 for a more complete description. 3.4.6 NETWORK OPERATIONS CONTROL CENTER (NOCC) The NOCC generates and transmits information to each DSCC prior to tracking support. It also receives, displays, logs and distributes data generated at the DSCC during tracking support. 3.4.7 NOCC SUPPORT SUBSYSTEM The NOCC Support Subsystem (NSS) generates Radio Science, antenna pointing, tracking, receiver, and uplink predicts. The NSS also provides DSCC schedules and transmits a subset of the Project's SOE to be used at the stations during tracking support. 3.4.8 NOCC DISPLAY SUBSYSTEM The NOCC Display Subsystem generates DTV graphic and alphanumeric status and configuration displays. The NOCC Display Subsystem provides these displays to the Network Operations Control Center and the Project's Mission Support Area. The specific subsystems involved are the NRV RTM which generates graphic displays of SSI data and alphanumeric displays of the DSP status and tuning information, the NTK RTM which generates alphanumeric displays of closed-loop data and the Video Assembly Processor (VAP) which generates graphic displays of selected data types. The display subsystem at NOCC provides real-time visibility at JPL during real-time activities. The NRV remote SSI display, the NRV DSP status displays, the VAP Radio Science graphic displays, the NTK tracking alphanumeric displays and the NMP monitor alphanumeric displays are all expected to be used to support the experiments. 3.4.9 MISSION CONTROL COMPUTER CENTER (MCCC) The MCCC routes all Radio Science utilized NOCC displays, and the Real Time Display System (RTDS) via the MCCC distribution system. The MCCC RTDS provides displays of the data contained in the Monitor 5-9 blocks. These data contain system temperature, AGC and signal level estimates as well as the receiver/exciter subsystem and antenna subsystem configuration information. 3.4.10 MISSION SUPPORT AREA The Radio Science Multi-Mission Support Area contains the real- time control center for the Radio Science System. Voice lines and DTV display capability are provided to the Project's real-time operations personnel to aid in operations monitoring. Hardcopies of displays may be requested from the NOCC. 3.5 DSS Calibration and Configuration 3.5.1 Open-Loop Receiver Attenuation Calibration The open-loop receiver attenuator calibrations are performed to establish the output of the open-loop receivers at a level that will not saturate the input signal to the analog-to-digital converters. To achieve this goal, the calibration is done using a test signal generated by the exciter/translator that is set to the peak predicted signal level for the upcoming pass. Then the output level of the receiver's video band spectrum envelope is adjusted to the level determined by the third equation below (to 5 sigma). Note that the SNR in the second equation is in dB, and the SNR in the third equation is not. Use the fourth equation to compute changes in RMS voltage levels. (see equation 3.5.1) 3.5.2 Station Configuration The station configuration during the Radio Science activities is governed by volume 2 of the Deep Space Network Operations Plan (NOP). This table, however, shows the recommended configuration of the DSCC Spectrum Processing Assembly (DSP) and open-loop system for the purpose of internal documentation by the Radio Science Support Team. 3.5.2.1 Galileo Solar Wind Scintillation Experiment Configuration: The Doppler sample rate is one per 10 seconds. The required frequency and timing reference is the Hydrogen maser. The DSP should be configured as shown in the Table 3-1. 3.5.2.2 Galileo Redshift Observation/USO Test Configuration: The Doppler sample rate is one per second. The required frequency and timing reference is the Hydrogen maser. The DSP should be configured as shown in the Table 3-2. 3.5.2.3 Ulysses IPTO Experiment Configuration: The Doppler sample rate is one per second. The required frequency and timing reference is the Hydrogen maser. The DSP should be configured as shown in the Table 3-3. 3.5.2.4 Ulysses Gravitational Wave Experiment Configuration: The Doppler sample rate is one per second. The required frequency and timing reference is the Hydrogen maser. The DSP should be configured as shown in the Table 3-2. Table 3-1: Radio Science DSP Configuration - Solar Wind Exp. Parameter DIRECTIVE Setting Notes ------------------------------------------------------------------ 70-m (DSS: 14, 43, or 63) Filter number DEFFL 1 1 1 1 82/100 Hz BW Filter offset RIVOF -150 in Hz NBOC mode MODE 1 Sample rate NBRAT 200 samp/sec IVC switch CFG PRIME Chan. assignment NBCHN NBOC ch=RIV ch A = 2 SRCP B = 2 SRCP C = 4 SLCP D = 4 SLCP Output to SSI SSS B Bit resolution NBRES 8 Tape density, bpi DENS 6250 458.3 min/tape ................................................................. 34-m STD (DSS: 42, or 61) Filter number DEFFL 1 1 1 1 82/100 Hz BW Filter offset RIVOF -150 in Hz NBOC mode MODE 1 Sample rate NBRAT 200 samp/sec IVC switch CFG Not applicable Chan. assignment NBCHN NBOC ch=MMR ch A = 4 SRCP B = 4 SRCP C = 4 SRCP D = 4 SRCP Output to SSI SSS B Bit resolution NBRES 8 Tape density, bpi DENS 6250 458.3 min/tape Table 3-2: Radio Science DSP Configuration - Generic Parameter DIRECTIVE Setting Notes ------------------------------------------------------------------ 70-m (DSS: 14, 43, or 63) Filter number DEFFL 1 1 1 1 82/100 Hz BW Filter offset RIVOF -150 in Hz NBOC mode MODE 1 Sample rate NBRAT 200 samp/sec IVC switch CFG PRIME Chan. assignment NBCHN NBOC ch=RIV ch A = 1 XRCP B = 2 SRCP C = 3 XLCP D = 4 SLCP Output to SSI SSS B Bit resolution NBRES 8 Tape density, bpi DENS 6250 458.3 min/tape ................................................................. 34-m HEF (DSS: 15, 45, or 65) Filter number DEFFL 1 1 1 1 82/100 Hz BW Filter offset RIVOF -150 in Hz NBOC mode MODE 1 Sample rate NBRAT 200 samp/sec IVC switch CFG CROSS Chan. assignment NBCHN NBOC ch=RIV ch A = 1 XRCP B = 2 SRCP C = 1 XRCP D = 2 SRCP Output to SSI SSS B Bit resolution NBRES 8 Tape density, bpi DENS 6250 458.3 min/tape ................................................................. 34-m STD (DSS: 42, or 61) Filter number DEFFL 1 1 1 1 82/100 Hz BW Filter offset RIVOF -150 in Hz NBOC mode MODE 1 Sample rate NBRAT 200 samp/sec IVC switch CFG Not applicable Chan. assignment NBCHN NBOC ch=MMR ch A = 3 XRCP B = 4 SRCP C = 3 XRCP D = 4 SRCP Output to SSI SSS B Bit resolution NBRES 8 Tape density, bpi DENS 6250 458.3 min/tape Table 3-3: Radio Science DSP Configuration - IPTO Exp. Parameter DIRECTIVE Setting Notes ------------------------------------------------------------------ 70-m (DSS: 14, 43, or 63) Filter number DEFFL 2 2 2 2 415/500 Hz BW Filter offset RIVOF -750 in Hz NBOC mode MODE 1 Sample rate NBRAT 1000 samp/sec IVC switch CFG PRIME Chan. assignment NBCHN NBOC ch=RIV ch A = 1 XRCP B = 2 SRCP C = 3 XLCP D = 4 SLCP Output to SSI SSS B Bit resolution NBRES 8 Tape density, bpi DENS 6250 300 min/tape SECTION 4 TEAM ORGANIZATION & RESPONSIBILITIES 4.0 Introduction 4.1 RSST Individual Responsibilities 4.2 RST Flight Project Interfaces 4.3 RST DSN Interfaces 4.0 Introduction The Radio Science Support Team (RSST) provides coordination for all flight project activities supporting Radio Science experiments. The RSST operates as a single, comprehensive focal point for experiment-related Project functions and provides long range planning for experiment interfaces with multi-mission organizations. It serves as the sole operational interface between the Radio Science investigators and the other elements of the Flight Projects and the Deep Space Network. The RSST represents the interests of the investigators (especially ones not resident at JPL) at meetings relevant to the investigation. Specifically, the RSST: 1. Plans the implementation of the Radio Science experiments along with the investigators, defines the requirements on all aspects of the experiments and resolves intra and inter- experiment conflicts. 2. Submits and integrates Radio Science requirements into the plans of the flight project, DSN, and other multi-mission organizations. 3. Provides specifications for spacecraft and DSN equipment based on the experiment's needs for hardware, software and procedures, monitors the development of the equipment and participates in testing the hardware or the output product. 4. Reviews (and, when requested, participates in the negotiations leading to) the schedule of station tracking coverage. 5. Develops and integrates spacecraft and ground operation sequences for the acquisition of experiment data by interfacing with the mission control team, spacecraft team, navigation team, and other elements of the projects. 6. Coordinates the process of data acquisition by conducting real- time operations and collecting the data observables. 7. Logs, archives, and validates the data products in order to prepare the data observables for scientific analysis. The Radio Science Support Team is part of the Radio Science Systems Group, Telecommunications Systems Section. The group currently supports Radio Science experiments on the Galileo, Ulysses, Mars Observer and Cassini flight projects. The group also provides support as needed for Radio Science experiments on Voyager, Magellan, Giotto (reactivation mission) and Pioneer Venus. Figure 4.1 shows the organization of the Radio Science Systems Group. 4.1 RSST Individual Responsibilities 4.1.1 Science Coordinator/Experiment Representative The Science Coordinator/Experiment Representative (SC/ER) coordinates all the RSST tasks listed above, provides overall team direction, coordinates the teams's needs and resources, and ensures that schedules and staff plans are adequate to achieve the maximum return of quality data for the Radio Science experiments. The SC/ER develops the observation strategy, performs mission analysis trade-off studies, performs inter- experiment science integration, and provides sequence inputs. During real-time operations, the SC/ER monitors the progress of the experiment and provides recommendations to the operations personnel to optimize its performance. For some flight projects, if the Science Coordinator or Experiment Representative is also an investigator he/she may be called Investigation Scientist or Coordinating Scientist. 4.1.2 Instrument Engineer The Radio Science Instrument Engineer's primary responsibilities are to develop, maintain, and interpret instrument (spacecraft and Ground Data System) requirements, monitor, and when appropriate participate in the planning, design, scheduling and implementation of the instrument's components by interfacing with appropriate organizations (e.g., the DSN, Project spacecraft team). The Instrument Engineer performs instrument trade-off studies, designs the instrument operation configuration and verifies that all instrument and data interfaces satisfy team requirements. It is also the responsibility of the Instrument Engineer to test the data products during and after instrument implementation to ensure that the quality meets team requirements. He/she, along with the Software System Engineer, develops the software tools necessary for data validation and processing. The Instrument Engineer is the lead data analyst for the USO, telecommunication subsystem, and DSN systems stability. The Instrument Engineer also assists in Radio Science operations, and real-time monitoring. 4.1.3 Operations Engineer The Radio Science Operations Engineer's primary responsibility is the verification of the proper conduct of pre-pass, real-time, and post-pass operations of the Radio Science data acquisition activities. Specifically, he verifies the presence and accuracy of the activity's Sequence Of Events (SOE) and predictions required by the station. He handles communications regarding action or information required from the DSN station with the Project's Mission Controller (ACE), or Ground Controller (GC), via the appropriate voice nets. He insures the availability of data displays needed for monitoring the activity, and insures that the Radio Science real-time support area and related facilities are equipped and staffed for real-time monitoring 4.1.4 Software System Engineer The Radio Science Software System Engineer's primary responsibilities include evaluation of existing Radio Science software, identifying software development tasks, overseeing development, implementation, testing, documentation, and delivery of software. He reports to the various projects on the software development status via periodic presentations. The secondary responsibilities include using the Radio Science software for data analysis and validation, and assisting in Radio Science operations. 4.1.5 Computer Engineer The Radio Science Computer Engineer is responsible for the proper operation of the RSST computing equipment and peripherals. His primary responsibility is the administration and upgrading of the RODAN computer facility (described in section 9) including interfaces (e.g., RODAN-GCF lines). Secondary responsibilities include the proper operation of the Real-time Monitoring System (RMS) and, eventually, administration and upgrading of the SUN workstations. The Computer Engineer also assists in Radio Science operations. 4.1.6 Data Products Engineer The Radio Science Data Products Engineer's primary responsibility is to receive, log, validate, archive, and distribute to Investigators the Radio Science data products (described in section 8). She also maintains data interface agreements. Secondary responsibilities include performing system back-ups and related tasks on the RODAN computer. 4.1.7 Radio Science Analyst The Radio Science Analyst conducts specialized scientific and engineering analysis needed for the planning, implementation, or data processing of Radio Science experiments. The Analyst also assists in Radio Science operations. 4.2 RST Flight Project Interfaces 4.2.1 Galileo MDT and Ulysses SOT The Galileo Mission Design Team (MDT) is responsible for coordinating the spacecraft configuration for all engineering and science activities which are eventually transferred to the Mission Control Team (MCT) for generation of the Galileo SFOS and ISOE products. The Ulysses Spacecraft Operations Team is responsible for coordinating the spacecraft configuration for all engineering and science activities which are eventually transferred to the Ulysses SEGs operator for generation of the Ulysses SFOS and ISOE products. 4.2.2 Galileo MCT and Ulysses SEGs Operators The Galileo Mission Control Team (MCT) and Ulysses SEGs Operators are the source of the respective SFOSs and ISOEs. It is the responsibility of the Radio Science Team to insure that these products reflect the expected Radio Science data acquisition parameters and schedules. 4.2.3 Galileo and Ulysses ACEs The Galileo ACE and Ulysses ACE are the primary interface for the Radio Science Team to affect real-time changes to SOE's and station configuration for the purpose of Radio Science data acquisition. 4.3 RST DSN Interfaces 4.3.1 Network Operations Project Engineer The Galileo and Ulysses NOPEs are responsible for the overall operational support of the Deep Space Network for their respective flight projects. The NOPEs prepare and issue the Network Operations Plan which defines the configuration of all DSN systems for their respective flight projects including those relevant to Radio Science. 4.3.2 The Ops Chief The Ops Chief is the DSN's lead person for all DSN operations in support of flight projects. 4.3.3 NAT TRK The NAT TRK serves as the real-time analyst for all incoming Tracking, VLBI, and Radio Science data and for all outgoing prediction data transfers for all stations and all flight projects. 4.3.4 TRACK CON The Track Controller is responsible for the real-time control of one or more stations supporting a Flight Project tracking pass. 4.3.5 COMM Chief The Comm Chief is responsible for the configuration and operation of the GCF communications between all DSCC's and the NOCC. The Comm Chief is also responsible for ensuring that the proper data lines are connected to the RODAN computer at the request of the RSST. 4.3.5 DSN Radio Science Design Team The Radio Science Design Team (RSDT) oversees the implementation of DSN systems directly used for the acquisition of Radio Science data. It is headed by the DSN Radio Science System Engineer and has as members representatives of the Radio Science Teams for all Flight Projects as well as members of the organizations responsible for the implementation of hardware and software of DSN systems relevant to Radio Science. Table 4-1 Key Radio Science Personnel Radio Science Support Team Sami Asmar Ulysses Coordinating Scientist 3-0662 Carole Hamilton Group Supervisor 4-2081 Mick Connally Mars Observer Experiment Rep. 4-3826 Ann Devereaux Ground Instrument Engineer 4-1386 Paula Eshe Data Products Engineer 3-0663 Randy Herrera Galileo Science Coordinator 3-0664 Tony Horton Operations Engineer 3-1142 David Morabito Software System Engineer 3-0665 Massimo Tinto Analyst 4-0798 Gerard Benenyan Display Software Engineer 3-1073 Dwayne Chong Pioneer Venus Orbiter Support 4-8514 Deep Space Network Pat Beyer Galileo TDS Manager 4-0055 Dennis Enari Ulysses TDS Manager 4-0074 Marv Traxler Mars Observer TDS Manager 4-0070 Bob O'Connor Galileo NOPE 584-4422 Roy Rose Ulysses NOPE 584-4418 Thorl Howe Mars Observer NOPE 584-4444 Sal Abbate R.S. Sys. Cog. Ops. Eng. 584-4461 Shlomo Dolinsky Radio Science System Engineer 4-6824 Comm Chief ............................................... 3-5800 Data Chief ............................................... 3-7974 NATTRK ................................................... 3-7810 Ops Chief ................................................ 3-7990 Ops Con .................................................. 3-7907 Support Chief ............................................ 3-0505 Track Controller ......................................... 3-5858 Flight Projects Galileo ACE .............................................. 3-5890 Ulysses ACE .............................................. 3-0559 Radio Science Operations area ............................ 3-0666 Table 4-2 Radio Science Investigators & Staff Galileo Radio Propagation Taylor Howard Stanford Univ. Von Eshleman Stanford Univ. David Hinson Stanforf Univ. Arv Kliore JPL Gunnar Lindal JPL Richard Woo JPL Michael Bird Univ. Bonn, Germany Peter Edenhofer Univ. Bochum, Germany Martin Pätzold DLR Herbert Porsche DLR Hans Volland Univ. Bonn, Germany Celestial Mechanics John D. Anderson JPL Frank Estabrook JPL John W. Armstrong JPL James Campbell JPL Timothy Krisher JPL Eunice Lau JPL Ulysses Solar Corona Michael Bird Univ. Bonn, Germany Peter Edenhofer Univ. Bochum, Germany Martin Pätzold DLR, Germany Hans Volland Univ. Bonn, Germany Gravitational Waves Bruno Bertotti Univ. Pavia, Italy Sami Asmar JPL Luciano Iess CNR-IFSI, Italy Hugo Wahlquist JPL Gianni Comoretto Osser. Astro. Arcetri, Firenze, Italy Giacomo Giampieri Univ. Pavia, Italy Alfonso Messeri CNR-IFSI, Italy Roberto Ambrosini Ist. Radioastronomia, Bologna, Italy Table 4-2 Radio Science Investigators & Staff - cont'd Mars Observer G. Leonard Tyler Stanford Univ. Georges Balmino CNES, France David Hinson Stanford Univ. William Sjogren JPL David E. Smith GSFC Richard Woo JPL Richard Simpson Stanford Univ. Cassini Arv J. Kliore JPL John D. Anderson JPL Bruno Bertotti Univ. Pavia, Italy Nicole Borderies JPL F. Michael Flasar GSFC Robert G. French Wellesley Col. Luciano Iess CNR-IFSI, Italy Essam A. Marouf SJSU Andrew F. Nagy Univ. Michigan Hugo Wahlquist JPL SECTION 5 PRE-PASS PREPARATIONS 5.0 Introduction 5.1 Predictions 5.2 ISOE Process 5.3 Station Configuration & Calibration 5.4 RODAN-GCF Line Activation Procedure 5.0 Introduction This section describes the pre-pass operations for the Radio Science activities. Here, products that are essential for real-time support will be identified. All products relative to real-time support are ideally ready and available several days prior to the scheduled activity. Some of these products are: Integrated Sequence of Events (ISOE), Space Flight Operation Schedule (SFOS), closed-loop receiver predicts plus open- loop Radio Science predictions should they be required 5.1 Predictions The process of generating frequency tuning, tracking, and antenna pointing predictions is performed by the DSN's Network Support Subsystem (NSS). The predictions actually used at the stations are in the form of computer files which are produced on the NSS computer, and later transmitted to the station by the NATTRK. Closed-loop receiver predictions will be generated for all Radio Science activities. These include standard tracking predictions which are used by the MDA to compute Doppler pseudoresiduals, and frequency tuning predicts used to tune the closed-loop receivers for initial acquisition. Radio Science (DSP) predictions will be required for those Galileo and Ulysses passes where the DSP has been allocated for open- loop recording. The NSS generates antenna pointing predictions for all passes. 5.2 ISOE Process The ISOE and its corresponding DSN Keyword File are the controlling documents for any Radio Science activity. The DSN Keyword File is transmitted to the station by the DSN, and ideally should contain all ground events necessary for station support during each pass. The Mission Control Team (MCT) is responsible for supporting ISOE redline activities. Redline support may be required for unexpected events affecting the Radio Science activities. 5.3 Station Configuration & Calibration Prior to every pass, the station dedicates a portion of time for equipment configuration and calibration. Of particular interest is the calibration of the open-loop receiver attenuation. Table 3-3 contains additional information on open-loop system calibrations. 5.4 RODAN-GCF Line Activation Procedure A very important step in the pre-pass period is the configuration of and activation of the RODAN GCF lines for real-time monitoring support using the Radio Science display system. The procedure is as follows: PERSON ACTION RSST 1. In preparation of up-coming RS activities the SFOS and SOE must be reviewed. 2. As real-time support approaches, review the RODAN interface drawing to establish the required line connections for the supporting DSCCS. 3. Then call the Comm Chief at 3-5800 or 3-5801 and the Ops Chief at 3-7990 or 3-7999 to request the connection(s). Note: Call Comm Chief first to inform him what the line configurations are. However, the Ops Chief must then be informed of the request since he and only he is to provide the direction to the Comm Chief. So, the point is to make a parallel request of the connections going to the Comm Chief first with the configuration information, and then to the OPCH who will then instruct the Comm Chief to carry out the directive. Asking for 56 Kb and 224 Kb line connections: For the 56 Kb line connection ask for INBOUND DUPLEX from SPC 10, 40 or 60 on RODAN's 1, 2 and/or 4. When using RODAN 4, make sure that the modem switch in the RODAN room is in the 56 kb line position. For 224 kb line connection ask for INBOUND SIMPLEX from SPC 10, 40 or 60 on RODAN 3 or 4. Check with Comm that AB switch position is set to RODAN 3. GCF/COMM 4. Comm Chief proceeds to patch the appropriate line(s) in 230 with the appropriate RODAN lines. RSST 5. Give the Comm personnel a reasonable amount time to make these connections - say 5 to 10 minutes. GCF/RSST 6. Both sides coordinate to verify that the Carrier and traffic lights are on at the modem. Note: The Carrier lights should always be On. When the traffic light is On prior to the support, this indicates that the modem may be receiving test blocks from the GCF system, or is already connected to a DSCC line. RSST/GCF 7. Troubleshooting: Once GCF verifies that the Transmit traffic light is on at his modem and all switches are set correctly, then all that he can do at his end is to seat and re-seat the patch cord or swap connections to another modem pair. At our end we can ensure that switches are in the correct position - check behind the modem for the "Normal" operation mode. The "Digital Loopback" mode is for internal testing with Comm. RSST/GCF 8. At the end of the RS support, an RSST person can call the Comm Chief to release the line(s) because RS activities have ended for this pass. GCF 9. Comm normalize the line(s) for future support. It is desired to have the lines set to the following nominal configurations between passes: RODAN 1 56K Doppler DSCC 10 2 56K Duplex DSCC 40 3 224K Simplex (any DSCC) 4 56K Duplex DSCC 60 5 N/A SECTION 6 REAL-TIME OPERATIONS 6.0 Introduction 6.1 Radio Science Real-Time Operations 6.2 Voice Net Communications 6.3 Sequence Of Events Confirmations 6.4 Tracking System Operations 6.5 Radio Science System Operations 6.6 Graphics Displays And Pass Products 6.0 Introduction This section describes those events which occur during the real- time operations period. These involve elements of the Radio Science Team (RST), Mission Control Team (MCT), Network Operations Control Team (NOCT), and the Deep Space Station (DSS). Some activities may involve non-DSN stations as well (e.g., the Medicina VLBI station). 6.1 Radio Science Real-Time Operations Real-time operations have been broken into three parts: events prior to acquisition, events during the recording period, and events following the recording period. 6.1.1 Events Prior To Data Acquistion During this period, activities include checking the correct configuration of the RODAN GCF lines, availability and correctness of the SFOS, ISOE and any redlines to the ISOE, and preparing the Multi- Mission Log Sheet (see Figure 6-1). 6.1.2 Events During the Recording Period During this period, validation of the Radio Science data begins by visual inspection of the displays immediately after the data acquisition begins. The ISOE, its redlines, predict hardcopy (if available), the Network Operatins Plan (NOP), and the Log Sheet checklist are tools to assist in the validation process. When open- loop data are being recorded, or whenever the station's Spectral Signal Indicator (SSI) is being used, the validation process should emphasize usage of the SSI, whenever possible, in the receiver mode as well as the ODAN mode. Table 6-1 describes the different configurations of the SSI for the S- and X-band receiver channels as well as the output channels of the four ADCs. 6.1.3 Events Following the Recording Period Following the recording period, timely delivery of the products should begin (See Section 7). It is not always necessary, but sometimes a good idea, to remind the TrackCon to remind the station personnel to mail the ODRs with the next consolidated shipment. 6.2 Voice Net Communications A description of the voice nets is presented in Table 6-2. In order to ensure that the voice communication during the Radio Science data acquisition period proceed smoothly, all personnel using the voice nets must properly identify themselves prior to asking questions or making requests. The call sign to be used by Radio Science personnel is "Galileo Radio Science" or "Ulysses Radio Science." 6.3 Sequence of Events Confirmations The Integrated Sequence of Events (ISOE), its redlines, and its corresponding DSN Keyword file will be the controlling documents for the conduct of the real-time operations during all Radio Science activities. It is important that all operations groups (RSST, MCT, NOCC and the participating DSCC) follow the same script. During the pass, it is recommended that positive reporting of each item be exercised. Confirmation of each event will provide visibility into the status of the ground data system at each station. 6.4 Tracking System Operations The MDA (closed-loop doppler and/or range) is standard for all Tracks. The appropriate channel should be enabled (when applicable S- and X-band) and the correct Doppler sample rate should be consistent with ISOE. Whenever the Sequential Ranging Assembly (SRA) is required for the pass, it should be configured according to the NOP. 6.5 Radio Science System Operations DSP operations are dependent upon the experiment requirements and will be scheduled on that basis. The DSP should be configured according to the NOP (the recommended configuration also appears in section 3). The SSI will be used to monitor the performance of the Radio Science System during periods of open-loop data recording. 6.6 Graphics Displays and Pass Products The DTV displays available to the RST in the multi-mission Radio Science area are a data source for monitoring the operations of the pass. The Operations Engineer communicates with the ACE, and/or NATTRK to coordinate the selection of displays. Table 6 - 1 Station SSI Identification Display SSI Port Signal Source RCV1 1 Closed-Loop Receiver RCV2 2 Closed-Loop Receiver RCV3 3 Closed-Loop Receiver RCV4 4 Closed-Loop Reciever SRCP 5 S-band RCP from OLR SLCP 6 S-band LCP from OLR XRCP 7 X-band RCP from OLR XLCP 8 X-band LCP from OLR ODAN/B 9 S-band NBOC Output ODAN/A 9 X-band NBOC Output SP15 11 S-band from MMR SP14 12 X-band from MMR TABLE 6-2 VOICE NET COMMUNICATION INTER-8: Standard Project operational net to NOCC for communication between Ulysses ACE and OPCH INTER-5: Standard Project operational net to NOCC for communication between Galileo ACE and OPCH GDSCC-1: Standard NOCC-to-DSN Complex control net (Goldstone) CDSCC-1: Standard NOCC-to-DSN Complex control net (Canberra) MDSCC-1: Standard NOCC-to-DSN Complex control net (Madrid) FAC COORD: OPS CON - Facilities coordination CMTRY: Commentary (and music) SECTION 7 POST-PASS OPERATIONS 7.0 Introduction 7.1 Data Product Delivery 7.2 Quick-Look Data Analysis During the GWE 7.3 Other Post-pass Activities 7.0 Introduction Post-pass operations for each Radio Science activity will begin upon completion of the Radio Science event. During this period, Radio Science related activities will consist of data product delivery (tapes, files, playback etc.) to the RSST, validation of data products, and the processing of the data. The RSST may require post-pass calibrations if problems arise during the pass. The processing and analysis of the data are discussed in Section 8. Section 7.1 specifies procedures and operation schedules for the delivery of data products. Section 7.2 describes other possible post-pass actvities. 7.1 Data Product Delivery For the four types of activities discussed in this handbook, there are different sets of products required. The Galileo USO test data product delivery strategy and schedules are given in Table 7-1. The Galileo Solar Wind Scintillation Experiment data product delivery strategy and schedules are given in Table 7-2. The Ulysses Jupiter Encounter data product delivery strategy and schedules are given in Table 7-3. The Ulysses Second Opposition data product delivery strategy and schedules are given in Table 7-4. These tables along with the following subsections describe each of the products as they relate to the specific activities. The format and interface agreement numbers for the data products are specified in Table 7-5 for Galileo and in Table 7-6 for Ulysses. 7.1.1 OPEN-LOOP DATA The open-loop data are recorded at the DSCC site on a 9-track 6250 bpi tape known as an ODR (Original Data Record). The tape contains up to four channels of digitized receiver data from the OLR as well as POCA tuning, timing, and configuration and status information. When applicable, the DSP ODR tape(s) will be logged and delivered to the RSST via the appropriate means. Upon completion of recording of each tape, the tape ID number, the start and stop recording times, the tape drive ID number, the station ID, and the pass number should be written onto the label of each tape. It is recommended that station operators be informed to write the tape recording densiyy onto the tape labels. The tape(s) is to be shipped to JPL in the next available consolidated shipment. Once at JPL, the tape is to be delivered to the NDC (230-104DD) to be checked in then delivered to the RSST (Attn: P. Eshe) where it will then be given an RSST tape ID. Under special circumstances, the RSST may desire to process open-loop data immediately after a pass, rather than wait for the arrival of the open-loop ODRs. Arrangements should then be made for playback of the open-loop data after a pass. These IDRs will be manufactured by the NDP and delivered to the RSST after completion of the playback. 7.1.2 CLOSED-LOOP TRACKING DATA Closed-loop tracking data in the form of an ATDF will be requested from the Radio Metric Data Conditioning Team (RMDCT) via a request memo which specifies the spacecraft ID, and the start and stop UTC times of the desired data. If only a portion of the data are required between the start and stop times, then the request memo will specify a list of the desired passes, each specified by station ID and start and stop UTC times. For tha case of USO tests, the request memo will be issued for each USO test and will specify that only one-way data are desired. The RDMCT will then produce the ATDF which then can be picked up by or delivered to hte RSST. For the case of the Galileo Solar Wind Scintillation Experiment, the Ulysses Second Opposition, and the Ulysses Jupiter Encounter, a request memo will be made to borrow and duplicate the RDMCT ATDF tapes and then return them within five working days. 7.1.3 SPACECRAFT TRAJECTORY DATA (CRSPOSTA FILES) The Celestial Reference Set (CRSPOSTA) file contains spacecraft trajectory vectors for use in the data processing of the Radio Science data. For each pass or set of passes, a CRSPOSTA file manufactured from the best available navigation solution will be required. The RSST will communicate its for the file to Project NAV via a request memo. GNAV will deliver the requested CRSPOSTA files into a permanently catalogued file on the UNISYS 1100B system. The RSST will transfer the file over to the PRIME computer using the Ethernet connection. In the event the Ethernet is down for an extended period of time, the RSST will initiate the proper tape movements to and from IPC in order to access the file. The CRSPOSTA files will not be validated by the RSST. For Galileo, the present SIS (210-12) specifies the NAVIO format as the output CRS product to be delivered to the Orbiter Engineering Team (OET) and Radio Science. However, in practice, Radio Science receives the file in an ASCII format (CRSPOSTA), and OET receives it in a different data format. The CRSPOSTA files residing on the UNISYS B system can be transferred to the PRIME using FTP as shown below; 1) Go to the directory on the PRIME in which you want the CRSPOSTA file(s) to be copied. 2) Type "FTP". Then, "OPEN UNIB" (note if this doesn't work, then directly use the node number "OPEN 128.149.54.2"). 3) Enter the login information. 4) Get the file by typing "GET" followed by the UNISYS file name, followed by the PRIME filename, for example; GET CRS.RS-89-349/CRS-D1 RS-89-349/CRS-D1 5) When the FTP prompt appears after successful transfer, go back to (4) for the next file transfer, or do a "BYE" to exit. Note that sometimes the files residing on the UNISYS are not yet in ASCII format. In this case, you must directly log onto the UNISYS B system and perform the following steps prior to the file transfer: @ASG,UP filename @EMBED CRS.navelementname,filename The @EMBED command will take the delivered NAV file (which is the element "navelementname" which was placed by NAV into the Radio Science permanently catalogued file "CRS") and recover the ASCII into the assigned file named "filename" which can then be transferred. For example: @ASG,UP FILE1. @EMBED CRS.RS-89-349/CRS-D1,FILE1. The CRSPOSTA files from the Ulysses NAV team (UNAV) will be made available on the development VAX, GROUCHO. UNAV will notify Radio Science via SPAN mail (or phone call) when these files are available and where they are located on GROUCHO. Since an account on GROUCHO is needed in order to use FTP, these files cannot be directly FTPed to RODAN. Therefore the following procedure must be used: 1) Log onto a VAX for which you have an account (e.g. JPLGP). 2) transfer the file from GROUCHO to your VAX using the VAX COPY command as follows: COPY GROUCH::disk:[directory]filename yourfilename where "disk" is name of the disk (e.g. USER$DISK2), "directory" is the directory name (e.g. TPM.ULYS.CRS), and "filename" is the name of the CRSPOSTA file residing on GROUCHO, and "yourfilename" is the name of the file you choose on your VAX. 3) Then FTP the file from the VAX to the desired partition in RODAN. note that you may have to perform the FTP while logged onto RODAN if it doesn't work from your VAX. 7.1.4 NOCC PASSFOLDER The NOCC hardcopy data which may be requested by the RSST consists of the complete passfolder including the Controller's Log (Network Operations Log), Tracking System Pass Summary (NATTRK Log), tracking and/or Radio Science frequency predictions, etc. These logs will be made available to the RSST per request. 7.1.5 RADIOMETRIC TRACKING CALIBRATION DATA Radiometric Tracking Calibration Data will be available on a permanently catalogued file residing on the UNISYS. These data include the changes induced in the various tracking data types based on media measurements. 7.1.6 SMALL FORCES HISTORY FILE A Small Forces History File ( Attitude History File) will be required for the Ulysses Jupiter Encounter and Ulysses Second Opposition Test in order to calibrate out the effects of the spacecraft spin. This file contains delta velocities which are induced by accelerations such as those due to Precision Manuevers executed by the Ulysses spacecraft which occur between provided time tags. The file also contains the right ascension and declination of the spacecraft spin axis and the spacecraft rotation spin rate as inferred from the telemetry. This file is generated by ESOC flight dynamics and is deliverable by UNAV. 7.1.7 DPTRAJ LISTING A DPTRAJ listing may be requested anytime before, during or after the acquistion of Ulysses Gravitational Wave data. These listings (or files) contain specifically requested quantities of interest (e.g., topocentric data). 7.2 Other Post-pass Activities Currently, there are no requirements for post-pass calibrations for the Radio Science passes. It is important however that any post-pass calibrations be performed with the same equipment used during the recording period. If any equipment had changed due to failures or if spare parts were used, then that information should be obtainable through the NOPE. Any post-test calibration tapes should be included in the shipment of all other tapes (ODRs). Playback of open-loop data will not be required under normal circumstances. However, data playback may be requested through the NOPE of the appropriate project if special circumstances warrant it. If this is the case, then the appropriate GCF wideband line along with the DSP and an LMC may be scheduled for some period following the test. The playback request would normally specify adequate playback time to include the complete playback of the Radio Science data. IDRs containing the playback data will be generated on the DRG in NDPA and will be picked up by a RSST representative. There are no requirements for any post-pass System Performance Tests (SPTs). However, one may be requested if deemed necessary during specific passes. The DSP may be requested after the test for any specially requested tape duplication, data playback, and/or post-pass calibrations. TABLE 7-1. Data Product Delivery Strategy and Schedule Galileo USO Tests PRODUCT DELIVERY STRATEGY DELIVERY SCHEDULE ATDF(S) Request memo to G. Goltz, Within seven days. RMDCT. When notified, tape can be picked up by an RSST rep. ODR(S) Only if open-loop data were Within a month acquired. The station will after event ship the ODR(s) to JPL NDC 230-104DD(Attn. P. Eshe) CRSPOSTA A request memo is sent to Within a few days FILE J. Johanneson, GNAV. Will of request memo. notify via forms delivered in mail, specifying file names and file locations. NOCC Phone request made to ROSA Within seven Passfolder Anguiano (507-215) working days Passfolder then mailed to following the pass. P. Eshe. TABLE 7-2. Data Product Delivery Strategy and Schedule Galileo Gravitational Wave Experiment PRODUCT DELIVERY STRATEGY DELIVERY SCHEDULE ATDF(S) Request to G. Goltz, RDMCT Within two days of RSST to borrow, duplicate pass, RSST may pick and return tape. up tape, and return within 5 working days. ODR(S) The station will ship the In the next ODR(s) to JPL NDC 230-104DD consolidated (Attn. P. Eshe) shipment CRSPOSTA A request memo is sent to Within a few days FILE J. Johanneson, GNAV. Will of request memo. notify via forms delivered in mail, specifying file names and file locations. NOCC Phone request made to Rosa Within seven Passfolder Anguiano (507-215). working days Passfolder then mailed to following the pass. P. Eshe. Table 7-3. Data Product Delivery Strategy and Schedule Ulysses Jupiter Encounter PRODUCT DELIVERY STRATEGY DELIVERY SCHEDULE ODR(s) The station will ship the Within one month of ODR(s) to JPL NDC (230- end of a pass 104DD) (Attn. P. Esshe). Playback To be generated only if Within one week IDR(s) specially requested. (normally two days) Request to R. Rose. IDR(s) of end of pass. to be delivered to P. Eshe from DSN NOCC NDPA ATDF(s) Request to G. Goltz, RDMCT Within two days of RSST to borrow, duplicate pass, RSST may pick and return tape. up tape, and return within 5 working days. NOCC Phone request made to Rosa Within seven Passfolder Anguiano (507-215). working days Passfolder then mailed to following the pass P. Eshe. Radio. Trk. Request memo sent to H. Royden, Within one week. Calib, Data DSN TRK. Small Request memo to T. McElrath, To be available Forces UNAV. Access from NAV VAX within TBD days. Hist. File GROUCHO. DPTRAJ Request memo to T. Within one working Listing McElrath, UNAV. Can access day of UNAV from NAV VAX GROUCHO via receiving request. FTP or request paper listings. As need basis. CRSPOSTA FILE A request memo is sent to Tim Within a few (TBD) McElrath, UNAV. Will place files days of request on NAV VAX GROUCHO and notify via memo. SPAN mail. Table 7-4. Data Product Delivery Strategy and Schedule Ulysses Second Opposition Test PRODUCT DELIVERY STRATEGY DELIVERY SCHEDULE ODR(s) The station will ship the Within one month (backup) duplicate ODR(s) to JPL NDC end of a pass. (230-340A) (Attn. P. Eshe). Playback To be generated only if Within one week IDR(s) specially requested. (normally two days) Request to R. Rose. IDR(s) of end of a pass. to be delivered to P. Eshe from DSN NOCC NDPA. ATDF(S) Request to G. Goltz, RDMCT Within two days of RSST to borrow, duplicate pass, RSST may pick and return tape. up tape, and return within 5 working days. NOCC Phone request made to Rosa Within seven Passfolder Anguiano (507-215). working days Passfolder then mailed to following the pass P. Eshe. Radio. Trk. Request memo sent to H. Royden, Within one week. Calib, Data DSN TRK. Small Request memo to T. To be available Forces McElrath, UNAV. Access from within TBD days. Hist. File NAV VAX GROUCHO. DPTRAJ Request memo to T. Within one working Listing McElrath, UNAV. Can access day of UNAV from NAV VAX GROUCHO via receiving request. FTP or request paper listings. As need basis. CRSPOSTA FILE A request memo is sent to Tim Within a few (TBD) McElrath, UNAV. Will place files days of request on NAV VAX GROUCHO and notify via memo. SPAN mail. Table 7-5. Galileo Data Product Interface Agreements DATA PRODUCT SOURCE USER FORMAT # IFA # Archival Tracking DSN RSS SIS 1001-14 NAV-1 Data File (ATDF) Original Data DSN RSS DSN 820-13 DSN-22 Record (ODR) RSC 11-10A SIS 233-03 Playback DSN RSS DSN 820-13 DSN-21 Intermediate IDR-12-1A Data Record (IDR) SIS 233-09 Spacecraft NAV RSS SIS 210-12 NAV-32 Trajectory Data (CRSPOSTA) Experiment Data DMT RSS SIS 224-04 DMT-39 Record (EDR) NOCC Passfolder DSN RSS Paper DSN-24 Real-Time Command DSN? RSS TBD TBD Hardcopy Logs Table 7-6. Ulysses Data Product Interface Agreements DATA PRODUCT SOURCE USER FORMAT # IFA # Archival Tracking DSN/TRK RSS DSN 820-13 1tm Data File (ATDF) TRK 2-25 Original Data DSN/TRK RSS DSN 820-13 1taa Record (ODR) RSC 11-10A Playback DSN/TRK RSS DSN 820-13 1taa Intermediate IDR-12-1A Data Record (IDR) TELECOM Performance DSN/NSS RSS Listing 1td Prediction Data (TPAP) Radiometric Track DSN/TRK RSS 7sd 1tu Calibration Data NOCC Passfolder DSN RSS Hardcopy 1tee Items Small Forces NAV RSS 3sh 3tt History File DPTRAJ Listing NAV RSS 3si 3tu REGRES File NAV RSS 3sg TBD Spacecraft NAV RSS TBD TBD Trajectory Data (CRSPOSTA) Spacecraft Range FLT RSS FR 3-500 7tb Delay APP. A NAV SECTION 8 DATA PROCESSING AND VALIDATION 8.0 Introduction 8.1 Data Records Subsystem (DRS) 8.2 Planning and Analysis Subsystem (PAS) 8.0 Introduction This section is primarily concerned with what is done with Radio Science data after it is delivered to the RSST. The Radio Science software system is broken down into two subsystems: the Data Records Subsystem (DRS) and the Planning and Analysis Subsystem (PAS). The DRS is concerned primarily with data archiving and validation. The PAS is primarily concerned with experiment planning and analysis of data. There are four program sets which have been or are planned to be formally delivered to the Galileo Project (and some will also be used by Ulysses). These are RCLVAL and ROLVAL in the DRS, and STBLTY and LMSPEC in the PAS. RCLVAL was formally delivered to the Galileo project in 1990 and is described in Section 8.1.4. ROLVAL was formally delivered to the Galileo project in March 1992 and is described in Section 8.1.5. LMSPEC (used for evaluating limbtrack maneuvers for Galileo occultation events during Jupiter orbital operations in 1995-1996) was formally delivered to the Galileo project in 1984, but is not applicable for this edition of the handbook. ROLVAL is planned to be formally delivered to the Galileo project in March 1992. The remaining program, STBLTY, is planned to be delivered in the 1993-1994 time frame. The existing Voyager software code for the programs in the Radio Science software system has served as a base for the Galileo/Ulysses software development. The original Voyager versions have remain intact in their original directories, while the new versions have been or will be developed in the appropriate partition on RODAN. 8.1 Data Records Subsystem (DRS) The RSST Data Records Subsystem (DRS) includes the software and procedures required to ensure that the data collected in support of Radio Science observations are usable by the Radio Science Investigators. The following subsections describe the RSST Data Records Subsystem. 8.1.1 DATA SOURCES The Radio Science data sources are the DSCC, the NOCC, the Multi-Mission Radio Data Conditioning Team (MMNAV), the Galileo Navigation Team (GNAV), the Ulysses Navigation Team (UNAV). The data types generated by each of these entities are described in detail in Section 7. 8.1.2 DATA PROCESSING AND LIBRARY FACILITIES The facilities required to transport and process the various Radio Science data types are scattered throughout the JPL organization. These facilities include the DSN Network Data Center (NDC) in Building 230-109 through which all DSN data must be released to the Project, the Information Processing Center (IPC) 1100 computer and library, the UNAV VAX GROUCHO and the Radio Occultation Data Analysis (RODAN) PRIME computer Facility in Building 230. 8.1.3 DATA DESTINATIONS After completion of all data preparation processes, the data products must be archived at JPL and shipped to the appropriate the Galileo Radio Science Team (RST) or the Ulysses Investigators. The details of the delivery procedures for each of the Radio Science data products are described in Section 7. 8.1.4 CLOSED-LOOP TRACKING DATA VALIDATION (RCLVAL) Validation processing for the closed-loop tracking data for both Galileo and Ulysses employs the program RCLVAL. This program was formally delivered to the Galileo Project in 1990 and is used to perform the validation of closed-loop Radio Science data which are delivered on tapes known as ATDFs. The data validated include Doppler pseudo-residuals and signal strengths (AGCs). RCLVAL is also used to flag the times the data fell within or without specified tolerance limits, to flag the times of the data gaps, and to flag the times and values of doppler sample rate and "flagged" signal mode changes. Plots of doppler pseudo-residuals and AGCs can also be generated by the program and archived. 8.1.5 OPEN-LOOP DATA VALIDATION (ROLVAL) The ROLVAL software set is used to perform validation processing of open-loop data tapes (ODRs and/or playback IDRs) for Galileo and Ulysses. These are being developed and tested using the open-loop data acquired from some Galileo USO passes and the Ulysses First Opposition passes. ROLVAL was formally delivered to the Galileo Project in March 1992. The programs which constitute the ROLVAL program set as well as their validation functions are described below: ROLHDR - produces plots and header dumps of POCA frequencies, time tags, rms voltage sample values, and a min max rms values. Also flags changes in various header quantities as well as the times and these changes occurred. ROLFFT - performs signal presence verification by producing plots of power spectral density according to specifications provided by the user. ROLSMP - produces plots of digitized sample values versus time and histograms of sample values. 8.1.6 DATA PRODUCT COPYING AND ARCHIVING In addition to the validation programs described above, the DRS also employs utility programs to perform data product copying and archiving for all incoming data products (ODRs/IDRs, ATDFs, CRSPOSTA files, media calibration files, etc.). 8.1.7 DATA TRANSFER FROM TAPE TO "OBERON" For the Galileo Solar Wind Scintillation Experiment, the open- loop ODR tapes will be transferred to files on the RODAN computer. The files will then be electronically transferred to the Investigator's computer "OBERON" using FTP. 8.2 Planning and Analysis Subsystem (PAS) The Planning and Analysis Subsystem (PAS) is concerned primarily with experiment planning and analysis of Radio Science data. 8.2.1 STABILITY ANALYSIS PROCESSING (STBLTY) The ODRs/IDRs and/or ATDFs from selected Radio Science activities will be processed using the program set "STBLTY" which evaluates the frequency stability and phase noise of the signal received from the spacecraft, as well as estimating the frequency and frequency rate of the USO. The spacecraft trajectory from the CRSPOSTA files is used by the program set to estimate the "predicted" or "model" frequency which is then differenced from the observed frequency which is extracted from the open-loop or closed-loop data. The frequency stability or Allan variance is then estimated from the resulting residuals. STBLTY is currently being used to measure the stability of Radio Science data involving the Galileo USO as the signal source, as well as estimating the USO frequency. STBLTY is currently being modified to more accurately estimate two-way doppler residuals. In addition, it is expected to handle different open-loop data signal detection scenarios depending upon signal conditions. STBLTY consists of several programs, each of which performs a specific task. Figure 8-1 is a block diagram illustrating the interconnection between the component programs making up the STBLTY program set as it relates to the processing of one-way (USO) data. Figure 8-2 is a block diagram for the corresponding two-way data processing case. Listed below are the descriptions of each program. FILTER - is used to produce a filter file for input to the NBDECIM program, based on the desired filter specifications of the user. FILTER designs a linear phase finite impulse response (FIR) filter using the Remez Exchange Algorithm. The user provides the program with the desired filter center frequency, bandwidth, and decimation factor, and the program outputs the reversed ordered time series impulse response corresponding to the specified filter and decimation factor. NBDECIM - reads the samples from an ODR or playback IDR, and then filters and decimates the data for each channel. The input time series is convolved with the appropriate impulse response time series output from FILTER in order to get the output filtered/decimated time series. The first N samples of each interval of input data are processed this way and the output series is written onto an output file. DETPHS - performs detection of the signal from the open-loop data file output from NBDECIM. It uses a least-squares algorithm to get estimated parameters. It is appropriate to use DETPHS on data where there are dynamic signal conditions such as occultation events. PLLDEC - is a digital phase-locked-loop program which reads either ODRs or playback IDRs, and performs signal detection. It is operationally easier to use then NBDECIM/DETPHS (doesn't require FILTER file). It is appropriate to run PLLDEC on data from events with strong and relatively static signal conditions. GETTRAJ - reads input file containing spacecraft centered trajectory EME50 vectors delivered from NAV, and outputs a file containing heliocentric position and velocity vectors of a specified earth-based DSN station and spacecraft. OCEP - combines, displays and edits all Radio Science data. Inputs include closed-loop tracking data from ATDFs, or open- loop data output from the digital filtering and detection programs (NBDECIM-DETPHS or PLLDEC). OCEP reconstructs the observed sky frequencies from the input doppler frequencies (from an input ATDF) or from the DSP recorded frequencies and POCA tuning frequencies (from input files generated by the open-loop detection software which in turn used the ODR tapes as input). RESID - computes frequency residuals from observed frequencies (OCEP output) and predicted frequencies (GETTRAJ output). STBLTY - reads in residuals computed from RESID and performs stability analysis. Computes Allan variance, phase noise, absolute frequency, and frequency drift rate. Writes summary information onto a database for one-way data. USOSMRY - displays parameters and statistics from the USO data base. SECTION 9 REAL-TIME COMPUTER SUPPORT 9.0 Introduction 9.1 Overview 9.2 Startup and Takedown Procedures 9.3 PRIME DISPLAY Software 9.4 SUN Workstation "display" Software 9.5 RODAN Upgrade 9.6 Computer Security 9.0 Introduction The Radio Science computer support activities include data collection, data archiving, and real-time displays on the PRIME 4050 Computer and/or a SUN workstation. The Radio Science Real-time Monitoring System (RMS) is a real-time display system that displays real-time information necessary for monitoring the instrument and experiment. The displays provided by Radio Science are different from the displays provided by the NOCC, although there is some overlap. Both systems may be used during Radio Science activities. An overview of the RODAN computer system is presented in Section 9.1. Start-up and takedown procedures are discussed in Section 9.2. The display system on the PRIME 4050 computer is discussed in Section 9.4. FInally, computer security is discussed in Section 9.5. 9.1 Overview The present overall structure of the RODAN computer system is shown in Figure 9-1. This multi-mission computing facility is used to support Radio Science experiments. The personnel who administer this facility are provided by the Radio Science Systems Group in Section 339. The heart of the RODAN is a PRIME 4050 computer and its peripheral devices which include two 6250/1600 bpi tape drives, a 1.3 Gbyte DAT drive, two disks of 496 and 315 MB memory capacity, a laser printer and an array processor. The array processor is a Floating Point Systems AP-120B (64 kiloword memory) vector hardware processor and math library software package. The PRIME computer supports 15 PCs/user terminals located in buildings 230 and 161, and an HP 9000 workstation located in building 161. The Real-time Monitoring System (RMS) receives data sent from one or more DSN stations. The data arrive into the basement of building 230 over the GCF lines and, from there thru splitters, are sent to the first floor Radio Science area where RODAN is located. The data is sent to RODAN on four receive-only lines at either 56 or 224 kb/s. An HP 9220 computer functions as RODAN's front- end data acquisition filter and transfers the selected data to the PRIME via an IEEE 488 parallel interface. The data can be displayed on various terminals hooked up to the PRIME and can be sent over the Radio Science subnet to be picked up by the Radio Science workstations, a SUN 4/60 and a SUN 4/330 both sharing 654 Mb of memory, or by a SUN 4/110 workstation to used by the Galileo TELECOM group (once they can connect to the Ethernet). 9.1.1 GCF LINES TO RODAN The digital lines which carry real-time data into the RODAN from the DSN's GCF are "receive only" and are tapped off of lines thru splitters located between DataSets and the Digital Matrix Switch. The output of these splitters go directly to modems in the Building 230 basement which are hard-wired via twisted pair lines to a second set of modems located in the RODAN computer room. The output of these modems conform to EIA RS-449/422A standards; these are connected to the input ports of RODAN's front-end data acquisition/filter computer. These standards are expected to be replaced by the T1 standard some time around 1992. 9.1.2 Data Fow Within RODAN, data proceed sequentially through successive proccesses until they are logged onto disk by the FARMER process (refer to Figure 9-1). These disk files constitute a data base that is accessed as needed by the display programs. The data are also forked within RODAN and a copy is sent out via TCO packets in a broadcast to the Radio Science subnet, which acts as a mutliple feed/link to each Radio Science workstation connected to the subnet. The data flow is described in the following subsystems and processes. 9.1.2.1 HP Serial Interface Five Programmable Serial Interfaces (Hewlett-Packard 98691As) have been modified for use with the DSN's communication protocols. Each interface includes a Z80 microprocessor which manages twenty 4800-bit blocks in a shared circular buffer with the MC68000 CPU in the HP 9220 computer. 9.1.2.2 HP 9220 A Hewlett-Packard 9220 computer reads data from the interfaces and checks to see if the data type is one of interest to RODAN. If so, it is then transferred to RODAN via a IEEE-488 parallel interface. 9.1.2.3 HPIN HPIN is a phantom process (non-interactive background process) in the PRIME computer that receives data from the IEEE interface. HPIN places these data blocks into a 100 block circular buffer in shared memory to allow access by the FARMER and ROUTERTCP processes. It generates warning messages if no data are received. 9.1.2.4 FARMER and ROUTERTCP FARMER identifies the selected data streams, and unpacks and archives each data stream to a data base disk file. ROUTERTCP, likewise, identifies selected data for the workstations and sends these data out on the Radio Science subnet in a broadcast format to the workstations. 9.1.2.5 PRIME Displays There are several CPL files which display the RMS data graphically and in tabular form on the PRIME; each of these "programs" is an executable file written in PRIMOS Command Procedure Language(CPL). These particular CPL files contain input data for the DISPLAY program residing in the TSS UFD. Each CPL file provides a set of displays from among 49 available choices offered by DISPLAY.RUN (see Table 9-1). 9.1.2.6 Radio Science Workstations Two SUN workstations, the 4/330 (GODZILLA) and the 4/60 (GAMURA), are connected to the Radio Science subnet, each executing an indepedent copy of the RMS display software for workstations. A user may have up to ten graphics windows open at any one one time. The number and types of displays available, see Section 9.4. 9.2 Startup and Takedown Procedures This section describes how to start up the data acquisition portion of the RMS, and how to take it down at the end of the pass. If you intend to run only the display generators and are not responsible for starting and stopping the RMS, then you need not read this section. (Note that emergency startup and shutdown procedures for the PRIME are provided in a white notebook labeled "RODAN Handbook" which resides next to the console in the RODAN computer room.) 9.2.1 STARTUP SEQUENCE The RMS system startup involves the execution of a series of processes ont the PRIME and a dedicated process on the HP front-end. Though eiher the HP front-end or the PRIME can be started first, it is recommended that the PRIME be activated first, followed by the HP front-end. If the PRIME is started first (i.e., the IEEE-488 controller is initialized followed by the execution of HPIN, FARMER, and various display programs), the HPIN will generate DMA timeout warning messages until it sees data coming from the HP front-end (NOTE: HPIN generated DMA timeout messages are also generated if data are coming in slowly). FARMER is an infinite-loop polling routine which checks the circular buffer for the next available data; hence, FARMER waits on HPIN, and various display routines wait on FARMER. If the HP front-end is started first, then finding the PRIME not receptive, it will hang as soon as it tries to send packets to the PRIME via the IEEE-488 interface. This will initially cause buffer overflow errors when data blocks start tranferring to the PRIME. Once HPIN on the PRIME is started, normal operations will commence. On the PRIME computer, HPIN, FARMER, and any display programs must be started in that order. HPIN is normally always running as a system phantom, so there is no need to either start or stop it. Each process shares a system resource with the preceeding process; moreover, the former initializes the shared interface, and the latter does not. Hence, the order in which these routines are started is essential for successful RMS startup. If HPIN should, for some reason, log itself out, the COMO file "TSS>HPIN.COMO" should also be renamed and/or printed out prior to restarting the process in order to preserve the information documented in this file. 9.2.1.1 HP Setup The Hewlett-Packard 9220 computer, used as the front-end of the RMS, is located at the bottom of the FPS Array Processor rack. 9.2.1.1.1 G.C.F. Lines Figure 9-2 is a block diagram description of the interconnection of the RODAN lines between the GCF in building 230/B3 and the Radio Science RODAN computer system located in building 230/103A. Five GCF lines are routed to RODAN, with the following descriptions and codes: RODAN DESCRIPTION CODE 1 56K DUPLEX 20 2 56K DUPLEX 21 3 224 SIMPLEX 22 4 56K/224K 23 SWITCHABLE 5 CURRENTLY 24 NOT FUNCTIONAL RODAN-4 is a switchable link with a dual position switch at the front of the modem, 56Kbps/224 Kbps. The RODAN 3 and RODAN 5 lines both connect to GCF but only one can carry data to the Radio Science computer at a time, the control depending on the toggle located in the basement of building 230. Currently only RODAN 3 can carry valid data to the Radio Science computer, as RODAN 5 is "nonfunctional". The configuration of each line may be confirmed or modified for any of the three DSN complexes by calls to the OPS Chief (X37990) and COMM Chief (X35800). Refer to Section 6 for specific details of the procedure for setting up RODAN lines. Once the procedure is initiated, you can verify that the proper lines are connected by observing the reception of the particular data type on the FARMER display screen on the PRIME or the MONITOR display screen on the HP. 9.2.1.2.1 Power Switches Turn on the power switches for the main box, the floppy disk drives, the printer and the monitor . 9.2.1.2.2 TSS Operational Disk Insert the 3 1/2 inch disk with the blue label that says "TSS: stand alone T.S.S. Operational Disk" into the disk drive (HP 9122) with the label facing up and then power up the main box. This will initiate a cold boot. Wait for the cold boot to finish (the screen will show "Command:. . . ." in the top left, and the disk activity light will go out). If the HP is already on but the system needs rebooting for any reason, then press "SHIFT RST" while the disk is in the drive. This will reboot the system from the disk. If the H.P. does not boot properly, then try cycling power. The disk should stay in the drive or next to it at all times. (The RODAN System Administrator has backup copies of this disk.) These disks should always be write protected. (The red thingy should be pushed down so that it is NOT visible through the hole from the top). 9.2.1.2.4 Program Startup Execute the filter program by pressing "X" (execute) then type "FILTER [CR]". Type the three select codes of the interfaces which are to be used (e.g., "20 [CR] 21 [CR] 22 [CR]"). See Section 9.2.1.2.3 for the correspondence between the lines and the codes. If you choose an unconnected interface, or if there is a hardware problem you will immediately get a message: "! NO RECEIVE CLOCK !!!!!!!!" Check that the data are coming over the line, and that you have typed the correct select codes. You can determine whether data and clock are present on the GCF line by looking at the LED lights on the front panels of the Data Sets. Both Carrier and Traffic LEDs must be lit. For RODAN-4, set the clock speed to either 224 Kbps or 56 Kbps depending on the incoming clock speed. You can verify the proper interface select code by looking at the back of the HP to check which interface the cable is plugged into. The relevant interfaces are numbered 20 through 24 and are in the left half of the backplane. These codes should correspond to the RODAN lines as listed in Section 9.2.1.1.1. Only if the problem cannot be located locally should you call the OPS Chief and report that the line is not working properly. The most likely problem, if the HP is set up properly, is that a cable may not have been completely plugged in when the line was connected by the COMM Chief. If you wish, you may execute the MONITOR program on the HP to get some indication of the kind of data blocks present on all of the lines. Execute it the same way as FILTER. Programs are stopped by pressing the "SHIFT" key simultaneously with the "STOP" key. This returns you to the same command line you get after a cold boot. (Note that data will not be logged by FARMER if MONITOR is running on the HP.) 9.2.1.2 HPIN If the HPIN process, usually called "SYSTEM (HPIN.CPL)", is not currently running on the PRIME, then you can start the HPIN phantom process by typing "PH TSS>HPIN". (WARNING!: Do not start HPIN without first verifying that it is not currently running on the PRIME. A duplicate HPIN process could hang up the system). The status of the phantom can be checked to some extent with "STAT USER", and "STAT SUM". The formaer should show a phantom named HPIN with device GP0 assigned. The latter should show the semephore number 1 with a value between 177634 and 0. (The number is a negative, 16 bit integer displayed in octal. The value is the number of data blocks in shared memory waiting for the FARMER process to read them.) 9.2.1.3 FARMER Login at a Tektronix 4107 terminal as user "FARMER". After you are logged in, type "FARMER[CR]" to start this process. The program will then ask the you for a configuration file. The configuration file is a listing of parameters in a specific order that FARMER uses to determine which data it should accept. These files which reside in the TSS directory have names such as GLL_14, GLL_43, GLL_63 and GLL_ALL. The first three files will accept data from a single 70-m station tracking Galileo. The latter file will accept data from all 70-m stations which are tracking Galileo. All of these files will only accept data related to Galileo passes. Other files are will be setup to accept data for Ulysses Radio Science activities or other type Galileo passes. Enter the filename. FARMER will then prompt for the name of the subdirectory into which the data will be logged. Type in an appropriate subdirectory name (e.g., GLL_USO_DOY233). 9.2.1.4 Display Startup See Section 9.3 for a detailed description of the setting up and running of the DISPLAY software using a terminal connected to the PRIME computer. See Section 9.4 for a detailed description of setting up and operating the display system on the SUN workstations. 9.2.2 TAKE-DOWN PROCEDURES Display programs can be stopped by entering the appropriate response given in the menus. At the end of a pass, the FARMER process should be stopped by typing control-P, followed by "LO" to logout the terminal. HPIN normally runs continuously as a system phantom, so it need not be stopped. If applicable, the proper notification for the release of RODAN lines should be communicated to the COM Chief or OPS Chief. 9.3 PRIME DISPLAY Software This section describes how to run the DISPLAY program on the PRIME. Once the FARMER process has begun to collect and archive data in the disk database, either an NEC graphics terminal, or a Tektronix 4107 terminal can be used to run the DISPLAY program on the PRIME. The procedures for the NEC and Tektronix 4107 terminals are identical, and are described in Section 9.3.1. It is planned that the PRIME DISPLAY software may be modified in the future to function on the IBM PCs using PCPLOT with Tek 4105 terminal emulation. 9.3.1 NEC/TEKTRONIX 4107 CONSIDERATIONS This section describes running the DISPLAY software with an NEC terminal using a specially modified real-time version of the ESC140 terminal emulator. This is due to the one graphics page limitation of the Tektronix 4107 terminal; however, viewing multiple pages on the Tektronix 4107 terminals is still possible. In the case of NEC terminals, eight-inch floppy disks configured to auto-load the proper version of ESC140 are available. Labels for the special function keys on the keyboard are also available. The NEC has internal display memory for three graphics displays, and a text display, all completely independent. The user can select any one graphics display and/or the text display without affecting the running of the display program. The Tektronix 4107 terminal has only one graphics display page as previously mentioned; to view other pages, the user must use the "V" option discussed in Section 9.3.3.3. 9.3.2 BASIC PROGRAM OPERATION To start the program, type in "DISPLAY" while attached to the top level TSS directory. DISPLAY will ask a few basic questions such as what spacecraft ID (77 for Galileo; 55 for Ulysses) and station or complex you want to look at. These questions are self-explanatory and will not be described in detail. Table 10-1 provides a list of all available data types along with the corresponding data number. The data number is one of the inputs which DISPLAY will request while setting up each plot. After entering all the required data specifications, DISPLAY will set up the text and/or graphic pages, and then backfill each of the graphs to the present point (real-time). After initially backfilling each of the grids, real-time display processing resumes. If the user does not wish to wait for the backfilling to complete, then enter a control-P (to cancel the backfilling), and enter the real-time command (R) and all graphs will start displaying immediately in real-time. The control-P break always resets any backfilling in progress. Instead of running DISPLAY directly, the user may desire to have often-used display configurations stored in a CPL file. Examples of CPL files for specific display configurations follow (e.g., to display open-loop data, type "CPL RTOL" then"CR"): FILE: RTOL.CPL (for open-loop data) PAGE 1: GRID 1: SSI Spectrum stacked right GRID 2: SSI Spectrum PAGE 2: GRID 1: DSP RMS Voltages (S-band) GRID 2: DSP RMS Voltages (X-band) PAGE 3: GRID 1: SSI Peak Frequency History (All inputs) GRID 2: SSI Peak Power History (All inputs) TEXT PAGE: NRV STATUS FILE: RTTRK.CPL (for closed-loop TRK data) PAGE 1: GRID 1: S-band AGC GRID 2: X-band AGC PAGE 2: GRID 1: S-band Pseudoresiduals GRID 2: X-band Pseudoresiduals Page 3: GRID 1: Number of S-band cycle slips GRID 2: Number of X-band cycle slips FILE: RTSS.CPL (for SSI only) PAGE 1: GRID 1: SSI (All inputs) GRID 2: SSI Peak Power History (All inputs) FILE: RTSNT.CPL (for system noise temperature from MON data) PAGE 1: GRID 1: SNT (RCVR A) GRID 2: SNT (RCVR B) FILE: RTTXT.CPL (for text NRV display) TEXT PAGE: NRV STATUS 9.3.3 PLOT CONTROL Once a display program has been started and configured, you can control what data are displayed and what portion of the data file is plotted. 9.3.3.1 General Display programs spend their time trying to update the display, rather than waiting for commands. Before a display will accept a command from the keyboard, you must attract its attention with the break key, or control-P. It should respond by printing a menu of available commands in the top left corner of the screen. Once you have the menu displayed, you can type any one of the commands described here; note however, that the display will not update while the program is waiting for a command. 9.3.3.2 NEC/ESC140 Display Control There is a row of special function keys across the top of the NEC keyboard. Only three of them are used by the RMS. These control the local displays on the NEC and do not affect the PRIME. The key labeled "TEXT ON/OFF" toggles visibility of the text page on/off. On the Tektronics 4107, the "Dialog" key provides a similar function. The key labeled "GRAPH ON/OFF" toggles visibility of all graphs on/off. On the Tektronics 4107, the "Graph" command toggle after a control-P provides a similar function. The key labeled "ALT GR PAGE" cycles through the three graphics pages on the NEC (The Tektronics 4107 requires use of the "V" command). This key is purely a local display function. It has no effect on program operation. DO NOT hit the "RESET" key during RMS program execution or you will have to quit the current program and start it over again to get the proper displays. 9.3.3.3 Command Menu The following describes the commands that the user may enter after getting the attention of the program with the "BREAK" key or control-P. The arguments enclosed in brackets "[*]" need not be entered if the command applies to the current graphics page, chosen by a "V" command. C CONTINUE - tells the program to return to display processing and exit the command window. Q QUIT - stops the program F [n] FRAME - provides a blow-up of an existing grid(s). To change the page format, set "n" to: 0: original page format (two grids) 1: select grid #1, disregard #2 2: select grid #2, disregard #1 A space is required before the n-value. Use the left button on the mouse to select the opposite corners of the desired rectangular, blow-up region in the grid. If you wish not to change a grid, press the middle button on the mouse. L [n] LIMIT - specify grid limits. n has the same meaning as in Frame. Enter "/" to use the current limit. When specifying an X-axis time-range, the day (DOY) of the first time limit by default is the day of the last data point updated prior to entering the command mode. A space is required before the n-value. M MOVE - specify a time to which the displays are to move. The user will be prompted for the desired time in year, day of year and then hour, minutes, and seconds. R REAL-TIME - similar to the "CONTINUE" command except that all displays are brought quickly to real-time. P [x] PRINT - produces hardcopy on the QMS laser writer of text or graph at the current page. For text copy, use the command "P t". For a copy of a graph, set "x" to the number of the grid desired, "1" or "2". If only one grid is on the graph page, then no "x" specification is necessary. A space is required before the x-value. V p VIEWPAGE - specifies the graphics page for which the subsequent user commands apply. "p" is set to the number of the desired graphics page; 1, 2 or 3. Cgtc COLOR - specifies the color to use for a particular trace on a grid. "g" specifies the grid number, "t" specifies the trace number on the specified grid, and "c" is the number of the desired color 0-9, e.g., "C113" Dgts DISCRETE SYMBOL - specifies the symbol to use for discrete point plotting. "g" specifies the grid number, "t" specifies the trace number. "s" is the desired symbol, such as a plus sign, e.g., "D11+" D[n] DISCRETE - toggles the grid in/out of discrete plotting mode. "n" specifies a particular grid on a page. If two grids exist on a page and "n" is not specified, then both grids are toggled. T[n] TIC - toggle the grid tic marks on/off. This only takes effect when a grid is refreshed. "n" has the same meaning as in "D[n]" above. A[n] AUTO-Y - toggles the auto-scaling on/off for a particular grid. If this is set and a data point falls out of range, then the grid will be erased and the vertical limits reset to accommodate the new point. "n" has the same meaning as it does in "D[n]" above. Y[n] Y-VALUE - toggles the y-value report function on/off. If "on", the y-value of every point plotted is reported in the grid on the left side in the same data color as the data trace. "n" has the same meaning as in "D[n]" B BELL - toggles the terminal audible bell on/off. 9.4 SUN Workstation Displays This section discusses how to set up and run the "display" software on the Sun workstations. This automated procedure will initialize the SUN display environment with three terminal emulation windows, two graphics pages, and one page consisting of a combination of a graphics page and a text page. 9.4.1 THINGS TO DO BEFORE RUNNING THE DISPLAYS 1) In RODAN, attach to the "router" subdirectory. Edit your configuration file (e.g., "ws_40") to specify exactly the data you desire to receive. The contents of this configuration file must match a subset of the contents of the configuration file residing in the "TSS" subdirectory in RODAN (except for the first two lines of the file residing in the router subdirectory which specifies the strat and stop time of the data reception). Example of a configuration file: 90/045/23:30:00 90/046/12:00:00 77 DOP 14 X 77 DOP 14 S 77 ANG 14 77 M59 14 77 DOP 43 X 77 DOP 43 S 77 ANG 43 77 M59 43 77 DOP 63 X 77 DOP 63 S 77 ANG 63 77 M59 63 77 SSI 40 77 NRV 40 || ---------- Note two spaces between data type and station/complex ID Line 1: specifies the YEAR/DAY/HOURS:MINUTES:SECONDS - this is the start time of the database collection run. Line 2: specifies the YEAR/DAY/HOURS:MINUTES:SECONDS - this is the end time of the database collection run. Line 3-14: Specify the data types that are desired for collection. These can be in any order and any number of data types (please observe proper spacing between fields). The first item is the spacecraft ID (77 for Galileo, 55 for Ulysses). The next item is the data block type (see Table 9- 1 for the data types contained in each block type). The next item is station or complex ID. Then the last item is frequency band (S or X) for applicable data block types. 2) In SUN "GODZILLA" - in "home/tss", edit the configuration file to reflect start, stop times and all of the data types that are desired to be received and archived. 3) The data base area on the computer disk needs to be initialized prior to reception of data. This process allocates all or part of 50 MB "virtual memory" as a time dependent linear storage space. This ensures that sufficient space is available as well as opens up data space for any pre-date data. Initiaize "virtual memory" - by either running "get_live_data", or "load from tape/disk" utilities. These can be invoked through "DATA BASE UTILITIES" (see Section 9.4.3). 9.4.2 INVOKING AND RUNNING THE "display" SOFTWARE 1) Make sure that you have configures your system for the 50MB virtual space (see Section 9.4.1). (Please note: GODZILLA is already configured for this, upon LOGIN. No user action is required if using GODZILLA.) 2) Login as user "tss" at GODZILLA. 3) Enter the proper password (obtain from workstation system administrator). 4) Upon entering the password, the computer shall place the user in the directory containing all of the executable code, configuration files, and utilities necessary for running the "display" software. (Unusual condition: When running the "display" software for the very first time or after a "boot-up", the program will detect that the "virtual memory" space is empty or is uninitialized. The "display" software will automatically invoke "Data Base Utilities" to allow the user to proceed with data base initialization. See Section 9.4.3 for below on how to use the other options.) 5) A window titled "STARTUP MENU" will be displayed which contains choices (See Figure 9-3, Item A). Select "new display" by pointing the mouse to this item and clicking the LEFT mouse button. This will invoke the "display" program. 6) Upon selecting "new display", a menu will appear in the upper right hand corner of the display titled: "Main Selection Menu" (see Figure 9-4, Item A). Depending on user desires, you can proceed to the first selection "CREATE A NEW PLOT", which will process information that is already in the data base. To choose another data base, or initialize a new "live" data monitoring seeeion, first invoke the "Data Base Utilities", and then select the source of data desired. This selected data will be filled into the data base and the user will be ready to select "CREATE A NEW PLOT" in the "Main Selection Menu", to view these data in a plot form. The most common action taken by the user, will be to select "Data Base Utilities". Upon selecting "Data Base Utilities", the user will be presented with the following choices (see Figure 9-5, Item A): "get live data" "load from tape/disk" "save to tape/disk" "list sub-directories" "Report about present data base" "Quit" 7) Select the appropriate choice listed above in item 6. Each of these items are described in detail in Section 9.4.3 8) If "get live data" (see Section 9.4.3.1) was selected, then the the user must set up "routertcp" (see Section 9.4.4). 9) When "get live data" (see Section 9.4.3.1) or "load from tape/disk" (see Section 9.4.3.2) above is chosen, and the appropriate data set is loaded in, the user can then select the option "CREATE A NEW PLOT" from the main selection menu (see Figure 9-4, Item A). 10) Next, when the "Data Type Selection Menu" appears, the user can select from among the various data types. Selections from this menu automatically detect what data types are available in the "virtual memory" and display them (see Figure 9-7, item A). 11) After selecting a data type, the user can then select from among the various "Plot Types" or data to be displayed in a plot, which is the next menu (see Figure 9-10). 12) after the plot is created and appears on the screen, the main selection menu will appear again. The user can then choose another quantity to plot by repeating steps 8-10. The various plots created can be moved around or manipulated by using the various mouse commands described in Section 9.4.5. 13) When done with any RMS activities, the user can then quit or close out each window. If the user wants to terminate display software and log out, then this can be done by placing the mouse on the background and clicking the RIGHT mouse button. Another menu will appear. Move the mouse to the EXIT SUNVIEW item and click the mouse (see Figure 9-11). This will return the user to the operating system. The user can then log out by typing "exit" followed by a "CR". 9.4.3 Data Base utilities Each of the data base utility items will be discussed in detail in this section. 9.4.3.1 "get live data" This selection is used for acquiring and displaying "real-time" live data. When this choice is invoked (by pointing to this selection with a mouse, and pressing the LEFT mouse button), a program is accessed which initiates a socket communication link that will enable reception of data from the PRIME computer. At this point, the program will execute an infinite loop, waiting for data to commence transmitting. The user needs to login to "PRIME" and initiate the "routertcp" program (see Section 9.4.4). (Note: The "routertcp" program is configured to send data to "GODZILLA" only - the present host for "display" software. If a different "host" or computer is required to run "display" software, then the "routertcp" software needs to be modified and recompiled.) If the database already contains data, the user will be prompted to make a decision: "Do you wish to resume using the same data base? (y or n only)" If the user selects "y", then the database will not be cleared and new data will be appended to the existing data base. Please note that every data base is configured to accept data for a specific time range. If your new data requires a storage location which falls beyond the specified time limits of the data base, then data will be lost. If the user selects "n", the user is prompted: "Is it OK to delete the existing data base? (y or n only)". This is a safety step and lets the user save data before destroying or clearing the data base. If "n" is selected, the program displays: "Save the data base and try again". After which, the "get live data" option will then terminate. The user should now make a new selection from the top panel. If the user types in "y" then the database will be cleared and the following message will appear: "Enter name of stream file which specifies desired GCF data: (for example:ws_40)" The user is being prompted for a configuration file (e.g. "ws_40"). This file can have any name. An example of this file is given below: 90/045/23:30:00 90/046/12:00:00 77 DOP 14 X 77 DOP 14 S 77 ANG 14 77 M59 14 77 DOP 43 X 77 DOP 43 S 77 ANG 43 77 M59 43 77 DOP 63 X 77 DOP 63 S 77 ANG 63 77 M59 63 77 SSI 40 77 NRV 40 | ---------- Note one space between data type and station/complex ID The software shall make a calculation of space allocation based on the specified data types and requested time span in the configuration file. If the "virtual memory" limits are exceeded, the user will be presented with an error message: "(init, data): shmget : Not enough memory " The user must either reduce the time span coverage (modify the start and end times to include a shorter span) or reduce the number of data types. After the configuration file is edited, the user may try again. When the program is satisfied with the configuration file parameters, it shall proceed with creating, initializing and partitioning the "virtual memory" to accommodate the data monitoring run. The software is then invoked to start an infinite loop to receive data. At this point, the user needs to open a new window, or from another terminal, the user must login to "RODAN" and initiate the dissemination program. ( see section 9.4.4) When the "RODAN" ROUTERTCP process starts sending data, its reception at "GODZILLA" shall become evident, as data packet messages are displayed in the utilities panel. These packet received messages will appear as follows: SOURCE INET ADDRESS 80952B39 SETUP_SOCKET 1 SOCKET 0 BIND 0 ADDRES -2137707759 " " " (see Figure 9-6, Item B for rest of received messages) These messages indicates that the system is functioning normally. The user may then close the window in order to reduce cluttering the display. (Note: do not "quit" the window, just "close" it) This can be done by pointing the mouse pointer at the top bar of the window, and clicking the RIGHT button on the mouse. A menu shall appear with one of the choices being "close". This will reduce the window to an icon. The "Display" software will go into full action. The first menu shall appear labelled: "MAIN MENU". This will allow you to continue on to create plots. A stand-alone utility "gauge" shall be automatically invoked and will appear as an icon. Point the mouse on the "guage" icon and press the LEFT button. The icon shall open up into a window, displaying the available data and the data types. The "gauge" acts the same way as a "fuel gauge" as it shows how much of the allocated data space in the "virtual space" is filled. This can also serve as a warning device, in case the data space is filling up for a particular data type. ( see the "MAIN MENU" for a list of the available choices.) 9.4.3.2 "load from tape/disk" The next selection on the "DATA BASE UTILITIES" is the "load from tape/disk". This option allows the user to access a previously saved data base for perusal or examination. Select this option by pointing the mouse pointer to this choice and clicking the LEFT button. The existing data base that is in the "virtual memory" will be displayed and the user will be prompted: "Do you wish to delete the existing data base? (y or n only)" An "n" response will give the user further prompting: "Want to add to the existing data base? (y or n only) " A "y" answer shall bypass initialization or deletion of the "virtual memory" space and a "n" response shall void this process and terminate loading any new data from any file or tape. A message "Try again" shall appear and th whole process will be aborted. The User may invoke new action by selecting from among the available choices on the panel. This is a safety measure to give the user a chance to save the existing data base into a file or a directory on disk. This can be done by exercising the "save to tape/disk" option. If a "y" answer is given to the first question, a program that removes all shared memory segment or data base segment from the "virtual memory" is invoked and then the user is prompted: "Extract data base from TAPE or FILE? (t or f only) " If "f" is selected, the user is prompted for the name of the subdirectory which contains the desired archived data. The "f" or FILE response indicates that the user desires a data base that is stored on the hard disk. The data base files are actually separate files with distinctly coded file names for each data type. For example /home/tss/gll23343 contains the following data files: 51 ANG.sc77.dss43 184 M59.sc77.dss43 832 NRV.sc77.dss40 1784 SDOP.sc77.dss43 1104 SSI.sc77.dss40 1 XDOP.sc77.dss43 After the user specifies the subdirectory name, the data base is loaded into the "virtual memory" and the program displays: "This process is completed, and the window can now be destroyed." The "Data Base Utilities" window can be deleted, by pointing the mouse pointer to the top frame of the "DATA BASE UTILITIES" and pressing the RIGHT mouse button. A menu shall appear and one of the choices is "quit". Select this option to destroy the window. Alternatively, this window can be deleted by pointing the mouse on the "quit" item in the "data base utilities" menu and clicking the RIGHT button. In response to the prompt; "Extract data base from TAPE or FILE? (t or f only)" if "t" is selected, software is invoked which will allow the user to load a previous data base from the tape cartridge. The program shall prompt the user as follows: "Install tape and press RETURN when ready " When the user presses the return key, the files shall automatically be extracted from the tape and placed into the "virtual memory" and onto the disk under a created directory name having the same nameas the directory it was archived under. 9.4.3.3 "save to tape/disk" If the user selects "save to tape/disk" choice, this means that the user is requesting an archiving utility. The data may be archived to either a hard disk sub-directory or onto a tape. When this choice is selected, the user is prompted as follows: "give new name for a sub-directory to put archive:" (e.g. gll_run) All data in "virtual memory" collected data shall be archived into the subdirectory specified by the user. Next, the user has a choice to backup the files on to the tape. The user will be prompted: "do you wish to put (gll_run) archive on tape? (y or n only)" An "n" response will terminate this option and the user can make another selection on the "Data Base Utilities" panel. A "y" response will initiate a program prompt: "install tape and press RETURN when ready " The tape drive for "GODZILLA" is located in the RODAN computer room, on top of the SUN workstation. As you enter and face the far wall, it is located in the far right hand corner of the room. The database files shall automatically be backed up onto the tape cartridge. If there is no tape present or the tape drive is not responding, the following error message will be displayed: "tar: /dev/rst8: I/O error Wish to try tar... again? ( y or n only ) " "tar" (tape archiving and restoring utility) is the name of the backup utility supplied with the UNIX operating system. Depending on the user response, the archiving utility will try again to back-up the data files on to the tape. The tar utility will list on the screen each file that is successfully recorded on tape. After tape writing completes, or if it is desired to examine the contents of a tape, the following command will list the contents of the tape: tar -tvf /dev/rst0 9.4.3.4 "list sub-directories" This option will list all of the sub-directories which may contain data. It is usually desired to invoke this option first to see what data directories are available on the disk prior to invoking any of the other options. 9.4.3.4 "Report about present data base" This option displays the status of the current "virtual memory" data base. 9.4.3.5 "Quit" This option shalll terminate the "Data Base Utilities" menu and close the window. 9.4.4 Making RODAN Run 1) Login to RODAN through a NEC terminal OR you can use a shell window in SUNVIEW to access RODAN. 2) Accessing RODAN through a shell window in "sunview". Point the mouse to the background (grey) location on the screen and press down the RIGHT mouse button. A menu will appear and one of the choices will be "Shells". Move the mouse to the right of the submenu, and select "Shell Tool". A window will appear in the middle of the screen (see Figure 9-12). Type in "telnet rodan [CR]" The computer will respond as follows: Trying 128.149.43.57 ... Connected to rodan. Escape character is '^]'. Telnet Rev. 2.1-22.0 connected You are connected to the Network Terminal Server Copyright (c) 1987, Prime Computer, Inc., All Rights Reserved. OK, Type in: login router Computer responds: Password? Type in: Password (Obtain from the RODAN System Administrator.) Computer responds: ROUTER (user 32) logged in Monday, 14 May 90 21:44:52. Welcome to PRIMOS version 22.0 Copyright (c) Prime Computer, Inc. 1988. Last login Friday, 11 May 90 19:40:36. OK, Type in: a router[CR] (attach to directory "router") In case ther are error messages or the program aborts, do the following: c all (CR) (close all. close all open files) rls -all (CR) (release unneeded resources) delte doyxxx(CR) (delete file) If there were several attempts to create an archiving directory named "doyxxx" for the incoming data for a particular day, there may be a left-over directory file of the same name. The above delete command will remove these files so that the RODAN software will be allowed to automatically create the intended files. If things appear to be really fouled-up, type in the following sequence: ice[CR] (reinitialize the command environment) a router[CR] (attach back to router directory) We are now ready to initiate data dissemination. Return to the SUN software (by moving the mouse to a "SUN" window, and initiate "get_live_data" option). After answering all the questions (see "get_live_data" description), the "SUN" software shall initiate a socket program to start receiving data. Now return to RODAN (move the mouse pointer into the "RODAN" window), and type: routertsp (CR) Computer responds: Enter name of file containing stream parameter Type in : ws_40 (CR) The name of this configuration file (e.g., ws_40) need not be identical to the name of the "farmer" configuration file. However its contents must match a subset of the contents of the "farmer" configuration file. Note: You can interrupt or cancel execution of any program on the PRIME by typing: (cntl)p Rodan should start sending data packets, and "SUN" window shall display reception of those data packets. You are now on your way to receiving Great Science Data (GSD)! The RODAN computer shall respond with something similar to the following: SOURCE INET ADDRESS 80952B39 SETUP_SOCKET 1 SOCKET 0 BIND 0 ADDRES -2137707759 " " " " (See Figure 9-6 item A for remainder of message.) If the telnet connection is broken between a window ant the PRIME, then, by pressing the "pause" button on the workstation keyboard, the user is placed back to the point where the user may login. For further details on setting up and running RODAN software, see the RODAN System Administrator. 9.4.5 MANIPULATING WORKSTATION DISPLAYS USING THE MOUSE After logging onto the workstation and setting up the displays, the following more commonly used mouse commands can be utilized to manipulate the display windows (see the "Display Test Software Operations Manual" by G. Benenyan for a description of the full set of WS commands): To make a plot larger or smaller: Position mouse to corner or edge of plot. Hold down "control" key and click & hold CENTER mouse button simultaneously. Move mouse to desired location. Release CENTER mouse button. To move a graph: Position mouse to corner or side of plot, and press CENTER mouse button and continue to hold it down. Move mouse to desired location. Release CENTER mouse button. To change start time: Move mouse to top bar of window, press LEFT mouse button, move to the desired location on top bar, and release left mouse button. To take effect, position mouse to 'jump' and click LEFT mouse button. To change time span: move mouse to second bar, press LEFT mouse button, move to desired location on second bar, and release LEFT mouse button. To take effect, position mouse to 'jump' and click LEFT mouse button. To change the vertical scale of a graph: Position the mouse to the top bar of graph, press and release the RIGHT mouse button, go to "modify graph" and press and release the RIGHT mouse button. Position mouse on number for which a change is desired and press and release the LEFT mouse button. To change the number, click the delete key appropriately, then enter in desired value and hit return key. Do the same thing with the next number. To allow the modifications to take effect, position the mouse pointer to "accept parameter" and then click the LEFT button. To display values of a particular data point (X,Y), position mouse to top of plot, hold down right mouse button, go to "Compute XY", and release right mouse button. Move mouse to point on plot and click the RIGHT mouse button. To place a plot in front of another plot, position mouse at edge of plot and click the LEFT mouse button. To obtain a hardcopy of the plot, point the mouse onto the top bar of the graphics window, and press the RIGHT button. One of the choices displayed will be "Print". Upon selection of this item, the plot window will automatically be resized to full screen, temporarily making the plot monochrome. A snapshot of the screen will then be taken by invoking a "screendump". It will take approximately three minutes to get a hardcopy. The window will then be restored to its original location and state after the "snapshot" is taken. To plot discrete points instead of a continuous line, or vice versa, position the mouse to top bar of plot and click the RIGHT mouse button. When the menu appears, select "modify plot" (position and click the RIGHT mouse button). The graph parameters window will then appear. Position mouse to value displayed next to "Plot-mode" and click LEFT mouse button. Hit delete key appropriately then enter desired value ("-1" for continuous line, "43" for "+" sign, or any other ASCII decimal equivalent for desired plotting symbol). Position mouse to "Accept parameters" and click LEFT mouse button to accept. 9.4.6 Sample Runs 9.4.6.1 Sample Run one the user desires to create a "doppler residuals" plot featuring spacecraft 55 SDOP data from DSS 42. A previous data base already exists in memory and is ready for use. The following example illustrates each step of this sample run: 1) Login: tss(CR) 2) Password: (Enter password) 3) Point mouse and press LEFT button on "new display" selection (menu located at the upper left hand area of screen). 4) Another menu shall appear- "Main Selection Menu". Point mouse and press and release LEFT button on "CREATE A NEW PLOT" selection(menu located at upper right hand area of the screen). 5) Another menu shall appear - "Data Type Selection Menu". Point mouse and press and release LEFT button on "SDOP 42-55" selection (menu located at the upper right hand area of the screen). 6) Another menu shall appear - "SDOP Selection Menu". Point mouse and press and release LEFT button on "DOP_RESID" selection (menu located at the upper right hand area of the screen). A plot shall appear with the desired data type, reflecting the most recent data present in the database. Also, the "Main Selection Menu" shall appear. To select other data from the data base for display, use the two "sliding bars" on top of the display plo. This is used to manipulate the "X-axis" or the time scale. The first sliding bar indicates the START time of the data you desire plotted. The second "sliding bar" indicates the time span of the data you desire plotted in "hours:minutes". Point the mouse inside the "sliding bar" and press the LEFT button. You may hold down the LEFT button and "drag" the sliding bar to the desired location. The Day/time indicator located to the left of the sliding bar, provides proper feedback as to the "START" time selection. The "Span" sliding bar operates in the same way. To implement the new settings, point the mouse on the "Jump" selection located to the left of the sliding bars, and press the LEFT button. 7) Backing out or terminating the session; Point the mouse and press LEFT button on the "ERASE DESKTOP" in the "Main Selection Menu" located at the upper right hand corner of the screen. This shall erase all of the plots that are still on the screen. Next, point the mouse on the "Exit Program" selection and press the LEFT button. The computer shall ask you for confirmation. Confirm by clicking the LEFT mouse button without moving the pointer, and the "display" software shall terminate. Next, point mouse in the "background' area of the screen (non-window area), press LEFT mouse button. A menu shall appear, where one of the choices, is - "Exit Sunview". Select this option. The commputer, again, shall ask you for confirmation. Confirm. You will be out of the "sunview" windowing enviorment. All that remains to do, is to logout. Type in "exit(CR)" and you are finished. 9.4.6.2 Sample Run 2 The user desires to start a new data base and start receiving "live" data. Ensure that the correct configuration file resides in the "/home/tss" directory (e.g "ws_40"). Ensure that the proper configuration file resides in the RODAN "router" directory ( e.g. "wss_40"). The user desires tp create a "doppler residuals" plot, featuring spacecraft 55 SDOP data from DSS 42. Each step of this sample run is described as follows: 1) Login: tss(CR) 2) Password: (Enter password) 3) Point mouse and press LEFT button on "new display" selection (menu located at the upper left hand area of screen). 4) Another menu shall appear - "Main Selection Menu". Point mouse and press LEFT button on "DATA BASE UTILITIES" selection (menu located at the upper right hand area of the screen). 5) Another menu shall appear in the middle of the screen - "DATA BASE UTILITIES". Point mouse and press the LEFT button on "get live data". Configuration of the present data base shall be listed, and the user shall be prompted: Do you wish to resume using the same data base? (y or n only) Enter: n(CR) Is it ok to delete the existing data base? (y or n only) Enter: y(CR) Enter name of stream file which specfies desired GCF data: (for example: ws_40 (CR) Enter: ws_40(CR) Something similar to the following shall appear: start time = 90/267/16: 0: 0 start time = 90/267/23:30: 0 SSI 40 77 shm segment size (Kbyte): 5912 NRV 40 77 shm segment size (Kbyte): 1104 XDOP 43 77 shm segment size (Kbyte): 3168 SDOP 43 77 shm segment size (Kbyte): 3168 ANG 43 77 shm segment size (Kbyte): 72 M59 43 77 shm segmrnt size (Kbyte): 296 Total shared memory used: 13736 Kbyte initiating tcp socket" Now, go to your RODAN terminal, and start up "routertcp". Information should start flowing to your computer, and you can "close" your "DATA BASE UTILITIES" window, by pointing mouse to the top black bar of the window and pressing the RIGHT button. A menu shall appear, where one of the choices is - "close". Select this option. This will reduce the window to a small icon. The "Main Selection Menu" shall appear at the upper right hand corner of the screen. Point the mouse to the "CREATE A NEW PLOT" selection then press and release the LEFT button. 6)Another menu shall appear - "Data Type Selection Menu". Point mouse then press an release LEFT button on "SDOP 42-55" selection (menu located at the upper right hand area of the screen). 7)Another menu shall appear - "SDOP Selection Menu". Point mouse and press on "DOP_RESID" selection (menu located at the upper right hand area of the screen). A plot shall appear with the desired data type, reflecting the most recent data in the database. To select other data from the database for display, use the two "sliding bars" on top of the display plot. This is used to manipilate the "X-axis" or the "time scale". The first sliding bar indicates the START time of the data you desire to be plotted. The second "sliding bar" indicates the time span of the data you desire to be plotted in "hours:minutes". Point the mouse inside of the "sliding bar", then press the LEFT button. You may hold down the LEFT button and "drag" the sliding bar to the desired location. Day/time indicator, to the left of the sliding bar, provides proper feedback as to your "START" time selection. "Span" sliding bar operates in the same way. To implement the new settings, point mouse and press LEFT button on the "Jump" selection, located to the left of the sliding bars. To modify "Y-scale", point mouse to the top black bar of the window frame that you desire to change. Press RIGHT mouse button. A menu shall appear, with one of the choices being "Modify graph". Select this option by point mouse to it, and pressing the Right mouse button. A menu shall appear that contains all kinds of parameters that can be changed. About the third row down, there are two parametr labeled: "_Data_Min", and "Y_Data_Max". These are the lower and upper limits of the Y-scale of your plot. To change them, point mouse on to the data portion of the field that you desire to change, and press the LEFT mouse buttin. The field shall invert in color, to indicate that it was selected. Now, press "Delete" key on the keyboard, to first erase the previous value, then enter the new value as desired. Next, point mouse to "Accept parameters" menu choice on the top of the "Graph Parameter Window", and press the LEFT mouse button. The menu shall disappear and the graph shall redraw with the new parameter changes taking effect. 9.5 Computer Security The following computer security practices must be adherred to: A) Passwords 1) Avoid trivial passwords like your names, user id, or a keyboard character sequence. 2) Passwords should be at least six characters long. 3) Preferably, passwords should be formed of two random alphanumeric words separated by a special character (e.g., &, *, $, #, @). 4) They should not be revealed to or used by anyone other than the assignee. 5) Passwords are not to be displayed on terminal screens when entered. Passwords are to be prompted for during each log on. Passwords should not be specified in any automated logon files. 6) Passwords should be changed at least every 90 days. B) Terminals are not to be left unattended while logged on. If possible, terminals should have an "auto logout" implemented. C) Do not attempt unauthorized access of computer systems or networks for any purpose. D) Floppy disks and other removable media containing sensitive (i.e., important) data are to be locked up when not in use. E) Backup protection is to be provided for all sensitive or critical files and programs. If possible, automated backup should be implemented. F) Leased and purchased microcomputer program products that are proprietary are to be protected against unauthorized use (e.g., execution on an unauthorized computer system) and illegal duplication. G) All terminals should be locked up during off-hours or a keyboard lockout (physical switch) should be put in place. TABLE 9-1 AVAILABLE DATA TYPES FOR RMS Data Number Data Type 0 TEXT: NRV TIME TAGS 1 TEXT: DSP/SSI STATUS DISPLAY 2 TEXT: M59 REPORT OF CONSCAN MODE/LOOP 000 DOP: AGC 001 DOP: PSEUDO RESIDS 002 DOP: DOPPLER COUNT 003 DOP: DIFFERENTIAL DOPPLER COUNT 004 DOP: DOPPLER REFERENCE FREQUENCY 005 DOP: NOISE 006 DOP: # CYCLE SLIPS 007 DOP: INTEGRATED DIFFERENTIAL DOPPLER FREQ (SB) 008 DOP: PSEUDO DOPPLER FREQUENCY 009 DOP: RECEIVED FRENQUENCY 010 DOP: RF RESIDS 011 DOP: CUMULATIVE PHASE DIFF 100 ANG: AZIMUTH ANGLE 101 ANG: ELEVATION ANGLE 102 ANG: AZIMUTH RESIDUALS 103 ANG: ELEVATION RESIDUALS 500 SSI: SPECTRUM, ALL INPUTS 501 SSI: SPECTRUM, ALL ODAN INPUTS 506 SSI: SPECTRUM, ALL RIV INPUTS 511 SSI: SPECTRUM, ALL "SPXX" INPUTS 530 SSI: PEAK FREQ HIST, ALL INPUTS 531 SSI: PEAK FREQ HIST, ALL ODAN INPUTS 536 SSI: PEAK FREQ HIST, ALL RIV INPUTS 541 SSI: PEAK FREQ HIST, ALL "SPXX" INPUTS 560 SSI: PEAK POWER HIST, ALL INPUTS 561 SSI: PEAK POWER HIST, ALL ODAN INPUTS 566 SSI: PEAK POWER HIST, ALL RIV INPUTS 571 SSI: PEAK POWER HIST, ALL "SPXX" INPUTS 590 SSI: STACKED RIGHT, ALL INPUTS 591 SSI: STACKED LEFT, ALL INPUTS 600 NRV: MIN/MAX, ALL 4 CHANNELS 601 NRV: DSP RMS, ALL 4 CHANNELS 602 NRV: RIC RMS, ALL 4 CHANNELS 603 NRV: POCA READBACK 604 NRV: DSP RMS: CHS 1,3 (X-BAND) 605 NRV: DSP RMS: CHS 2,4 (S-BAND) 800 M59: SYSTEM NOISE TEMP, RCVR A TABLE 9-1 801 M59: SYSTEM NOISE TEMP, RCVR B 802 M59: SIGNAL LEVEL INDICATOR, RCVR A 803 M59: SIGNAL LEVEL INDICATOR, RCVR B 804 M59: AZIMUTH ANGLE 805 M59: ELEVATION ANGLE 806 M59: AGC SIGNAL LEVEL, RCVR A 807 M59: AGC SIGNAL LEVEL, RCVR B 808 M59: SNT VERSUS ELEV. ANGLE, RCVR A 809 M59: SNT VERSUS ELEV. ANGLE, RCVR B TABLE 9-2 Key Parameters for X.25 Protocol Operation Parameter Value Description Modulo 8 Allowable Frames Outstanding N1 1027 Bytes Maximum Length of Information Frame N2 5 Number of Retransmission Retries T1 2 seconds Frame Response Time (Acknowledgement) T3 40 seconds Inactivity Time-Out (Time Between Transmissions) CRC Formula X16 + X15 + X2 + 1 Levels Protocol PVC=1 Permanent Virtual Circuit Command/Response NG=3, RODAN=1 Address APPENDIX A END-TO-END SYSTEM DIAGRAMS APPENDIX B USEFUL FORMULAE B-1: Reconstruction of the antenna frequency from the recorded frequency using the open-loop receiver filters: B-2: Estimation of POCA frequency from the predicted S-band frequency and estimation of the S-band frequency from the predicted POCA frequency: B-3: Calculation of the signal position in the SSI: B-4: SSI update interval: B-5: Spacecraft downlink and uplink frequencies: NOTE: All frequencies are in Hz. APPENDIX C Abbreviations and Acronyms A/D Analog-to-Digital Converter ACE Galileo/Ulysses/MO Mission Controller ADC Analog-to-Digital Converter AGC Automatic Gain Control signal level AMMOS Advanced Multi-Mission Operations System AOS Acquisition Of Signal at a DSS APA Antenna Pointing Assembly APC Advanced Personal Computer (NEC Computer) ARA Area Routing Assembly ARD Antenna Reference Distribution ASAP Standard Radio Science Time Requirement ATDF Archival Tracking Data File (closed-loop data tape) ATR All The Rest AUX OSC Auxiliary oscillator in a spacecraft BLK III Closed-loop receiver (design phase III) BLK IV Closed-loop receiver (design phase IV) BOA Beginning of Activity BOT Beginning of Track BPI Bits Per Inch BPF Band Pass Filter C/A Closest Approach CBM Cured By Magic (see DR) CCR Closed Cycle Refrigerator (for the maser) CCS Computer Command Subsystem CDU Command Detector Unit CEP Critical Events Period CMC Complex Monitor and Control COH Coherent downlink CONSCAN Conical Scanning of a Radio source used to accurately point the Antenna CPL Command Procedure Language (for PRIME computer) CRG Coherent Reference Generator CRS CTA-21 Radio Science Subsystem CRS Celestial Reference Set (Spacecraft Trajectory Vectors) CRSPOSTA CRS ASCII Format CUL Clean Up Loop D/A Digital-to-Analog Converter DAC Digital-to-Analog Converter DAS Data Acquisition System dBc Decibel relative to carrier dBc/Hz dBc per Hertz, magnitude relative to carrier spectral density DC Direct Current (frequency equals zero) DCO Digitally Controlled Oscillator DDP Digital Display Processor DL Predicted one-way downlink frequency DMC DSCC Monitor and Control DMT Data Management Team DOY Day Of Year (UTC) DR Discrepency Report (see CBM) DRA Digital Recording Assembly DRG Data Records Generator DRS Radio Science Software Data Records Subsystem DSCC Deep Space Communications Complex DSN Deep Space Network DSP DSCC Spectrum Processor DSS Deep Space Station DTK DSCC Tracking Subsystem DTR Digital Tape Recorder (spacecraft) DTV Digitial TV monitoring display device EOA End of Activity EOT End of Track ER Experiment Representative ERT Earth Received Time FDS Flight Data System FFT Fast Fourier Transform FPS Floating Point Systems (maker of the Array Processor used by the RSST) FRO Frequency Offset FTP File Transfer Protocol FTS Frequency and Timing Subsystem GC Ulysses Ground Controller (Ulysses ACE) GCF Ground Communications Facility GCR Group Coded Recording GDS Ground Data System GLL Galileo Project GNAV Galileo Navigation Team GPS Global Positioning System GSD Great Science Data! GWE Gravitational Wave Experiment (Ulysses) HB Radio Science HandBook HGA High-Gain Antenna (spacecraft) IA Interface Agreement ICD Interface Control Document IDR Intermediate Data Records tape (playback tape) IF Intermediate Frequency IMOP Integrated Mission Operations Profile (Galileo) IMOP What I do after I spill something. IOM InterOffice Memorandum IPC Information Processing Center (JPL computer facility) IPS Inches Per Second ISOE Integrated Sequence of Events IVC IF Selection Switch JPL Jet Propulsion Laboratory L(f) Single sideband phase noise spectral density as a function of offset frequency (f) from carrier LAN Local Area Network LCP Left-handed Circularly Polarized LGA Low Gain Antenna (Spacecraft) LMC Link Monitor and Control LNA Low Noise Amplifier LO Local Oscillator LOS Loss Of Signal at a DSS LPF Low Pass Filter MCA Master Clock Assembly MCCC Mission Control Computer Center MCT Mission Control Team MDA Metric Data Assembly MGC Manual Gain Control MI Modulation Index MISD Mission Director's Voice Net MMR Multi-Mission Receiver (at 34-m STD stations) MO Mars Observer MO Modus Operandi (the way we do things) MONIDR Monitor Intermediate Data Record MOU Memorandum of Understanding MSA Mission Support Area MTS MCCC Telemetry Subsystem NAR Noise Adding Radiometer NATTRK Network Analysis Team Tracking Analyst NAV Project Navigation Team NB Narrow-Band NBOC Narrow-Band Occultation Converter NCOH Non-Coherent downlink NDC Network Data Center NDPA Network Data Processing Area NDPT Network Data Processing Team NDS Network Display Subsystem NIU Network Interface Unit NMP Network Monitor Processor display system NOA Network Operations Analyst NOCC Network Operations Control Center NOCG Network Operations Control Group NOCT Network Operations Control Team NOP Network Operations Plan NOPE Network Operations Project Engineer NOSG Network Operations Scheduling Group NRV NOCC Radio Science/VLBI Display Subsystem NRZ Non-Return to Zero NSP NASA Support Plan NSS NOCC Support Subsystem NTK Network Tracking Display System OCI Operator Control Input OD Orbit Determination by the Project's Navigation Team ODF Orbit Data File ODR Original Data Record OEA Operations Engineering Analysis OIA Operational Interface Agreement O/L Open-Loop OLR Open-Loop Receiver OOPS Technical term used by RSST for errors in HB OPCH DSN Operations Chief ORT Operational Readiness Test ORT a morsel left over from a meal OVT Operational Verification Test OWLT One-Way Light Time PAS Radio Science Software Planning and Analysis Subsystem PBNBIDR Playback Narrow Band Intermediate Data Records PC Personal Computer PDB Project Data Base PE Phase Encoded PIDR Parkes Intermediate Data Record PLL Phase-Lock Loop PLO Programmed Local Oscillator POCA Programmable Oscillator Control Assembly PPM Precision Power Monitor PRA Planetary Ranging Assembly RASM Remote Access Sensing Mailbox RAYPATH DSN program used to generate light-time file modeling atmospheric effects and used as an input for the generation of predictions RCP Right-handed Circularly Polarized RF Radio Frequency RFS Radio Frequency Subsystem (spacecraft) RIC RIV Controller RIV Radio Science IF-VF Converter Assembly RMDCT Radio Metric Data Conditioning Team RMS Real-time Monitoring System (formally TSS) RODAN Radio Occultation Data Analysis Computer Facility ROLS Radio Occultation Limbtrack Systems ROVER Wide-band backup recording system (obsolete) RSWG Radio Science Working Group RSS Radio Science System RSST Radio Science Support Team (Not Galileo Remote Sensing Science Teams; SSI, NIMS PPR and UVS) RSSS Radio Science Support System (alias RODAN) RST Radio Science Team (Investigators and RSST) RTDS Real-Time Display System RTLT Round-Trip Light-Time RTM Real-Time Monitor (supplies data to NOCC graphics/display systems) SCE Solar Corona Experiment (Ulysses) SCET SpaceCraft Event Time SCOE System Cognizant Operations Engineer SCT SpaceCraft Team SDT Science Data Team SEF Sequence of Events File SEG1 Sequence of Events Generation program (generates SFOS, ISOE and DSN keyword file) SEL Station Event List SEP Sun-Earth Probe Angle SEQGEN SEQuence of events GENeration program (generates SEFs) SFOS Space Flight Operations Schedule SIRD Support Instrumentation Requirements Documents SIS Software Interface Specification SLE Signal Level Estimator SNR Signal-to-Noise Ratio SNT System Noise Temperature SOE Sequence of Events SOM Software Operations Manual SOP Standard Operations Procedures SPA Spectrum Processor Assembly SPC Signal Processing Center SPD S-band Polarization Diversity (microwave subsystem) SPE Static Phase Error SPR System Performance Record SPT System Performance Test SRA Sequential Ranging Assembly SRD Science Requirements Document SSA Solid State Amplifier (spacecraft S-band downlink) SSB Single Sideband SSI Spectral Signal Indicator (not Solid-State Imaging!) SSS SSI Input Channel Selection (DSP OCI) TBD To Be Determined, since we don't know the answer TBS To Be Subjected to further scrutiny TCG Time Code Generator TCM Trajectory Correction Maneuver TCT Time Code Translator TLC Tracking Loop Capacitor TMO Time Offset (OCI) TMU Telemetry Modulation Unit TSS Test Support System (now called RMS) TWM Traveling Wave Maser TWNC Two-Way Non-Coherent switch (spacecraft) TWNC Too Wishy-washy, Nebulous and Confusing TWT Traveling Wave Tube TWTA Traveling Wave Tube Amplifier (spacecraft) TWX Teletype message TXR DSS transmitter ULS Ulysses Project UNAV Ulysses Navigation Team USO Ultra-Stable Oscillator UTC Universal Time, Coordinated VAP Video Assembly Processor VCO Voltage Controlled Oscillator VEEGA Venus-Earth-Earth-Gravity-Assist VF Video Frequency VTR Video Tape Recorder XA Doppler-compensated ground-transmitter DCO frequency for spacecraft receiver's best-lock frequency XRO X-band receiver only (microwave subsystem) determination experiment APPENDIX D DIRECTORY John W. Armstrong Mail Stop 238-737 Work Phone (818) 354-3151 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 354-2825 NASAMAIL: JWARMSTRONG E-mail: john@oberon.jpl.nasa.gov john@jpl06.jpl.nasa.gov John D. Anderson Mail Stop 301-230K Work Phone (818) 354-3956 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-0028 NASAMAIL: JDANDERSON Sami W. Asmar Mail Stop 230-103 Work Phone (818) 393-0662 Jet Propulsion Laboratory Home Phone (818) 797-0298 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 JEMS: ASMAR NASAMAIL: SASMAR SPAN: 5127::SASMAR (JPLGP::SASMAR) Georges Balmino GRGS, 18, Av. Edouard Belin Work No. (33) 61.21.44.27 31055 Toulouse Cedex Home No. ( ) France Fax No. (33) 61.25.30.98 NASAMAIL: GBALMINO Gerard Benenyan Mail Stop 230-103 Work Phone (818) 393-1073 Jet Propulsion Laboratory Home Phone (818) 507-8805 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 E-mail: gerard@godzilla.jpl.nasa.gov Bruno Bertotti Dipartimento di Fisica Work Phone (39) 382-392435 Nucleare e Teorica Home Phone (39) 382-525479 Universita di Pavia via Bassi 6, 27100 Pavia Fax No. (39) 382-52693839 Italy SPAN E-mail: 39275::BERTOTTI Michael K. Bird Radioastronomisches Institut Work No. (49) 228-733651 Universitaet Bonn Home No. (49) 228-255994 Auf dem Hugel 71 D- 5300 Bonn Fax No. (49) 228-525229 Germany E-mail: UNF200@DBNRHRZ1.BITNET SPAN: SOLAR::MBIRD James K. Campbell Mail Stop 264-211 Work Phone (818) 354-5768 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number ( ) - NASAMAIL: JIMCAMPBELL SPAN: JKC%NAIF.JPL.NASA.GOV@SDSC.EDU Mick Connally Mail Stop 161-228 Work Phone (818) 354-3826 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 NASAMAIL: MCONNALLY Ann S. Devereaux Mail Stop 161-228 Work Phone (818) 354-1386 Jet Propulsion Laboratory Home Phone (818) 441-5677 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 Peter Edenhofer Institut fur Hoch- und Work No. (49) 234-7002901 Hochstfrequenztechnik Home No. (49) 89-578812 Ruhr Universtaet, Postfach 2148 463 Bochum-Querenburg Fax No. (49) 234-7002339 Germany Von Eshleman Center for Radar Astronomy Work No. (415) 723-3531 Stanford University Home No. ( ) - Stanford, CA 94305-4055 Fax No. (415) 723-9251 Paula M. Eshe Mail Stop 230-103 Work Phone (818) 393-0663 Jet Propulsion Laboratory Home Phone (818) 798-3935 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 GLL MSA Fax(818) 393-0631 E-mail: poo@rodan.jpl.nasa.gov Frank B. Estabrook Mail Stop 169-327 Work Phone (818) 354-3247 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 354-8895 NASAMAIL: FESTABROOK E-mail: frank@oberon.jpl.nasa.gov Carole L. Hamilton Mail Stop 161-228 Work Phone (818) 354-2081 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 JEMS: CAROLE HAMILTON NASAMAIL: CHAMILTON Randy G. Herrera Mail Stop 230-103 Work Phone (818) 393-0664 Jet Propulsion Laboratory Home Phone (818) 577-8705 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 GLL MSA Fax(818) 393-0631 E-mail: RGH@RODAN.JPL.NASA.GOV David Hinson Center For Radar Astronomy Work No. (415) 723-3534 Stanford University Home No. ( ) - Stanford, CA 94305-4055 Fax No. (415) 723-9251 NASAMAIL: DHINSON Tony Horton Mail Stop 230-103 Work Phone (818) 393-1142 Jet Propulsion Laboratory Home Phone (714) 338-6580 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 JEMS: TONY HORTON Taylor Howard Center for Radar Astronomy Work No. (415) 723-3537 Stanford University Home No. ( ) Stanford, CA 94305-4055 Fax No. (415) 723-9251 E-mail: Luciano Iess Istituto di Fisica Spazio Work No. (39) 6-9416801 Interplanetario-CNR Home No. (39) 6-9448330 via G. Galilei 2, C.P. 27 00044 Frascati Fax No. (39) 6-9426814 Italy SPAN: 40264::IESS IFSI::IESS Arv J. Kliore Mail Stop 161-228 Work Phone (818) 354-6164 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 NASAMAIL: AKLIORE Timothy P. Krisher Mail Stop 301-150 Work Phone (818) 354-7577 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-0028 JEMS: TIM KRISHER E-MAIL: TPK@GROUCH.JPL.NASA.GOV Gunnar F. Lindal Mail Stop 161-228 Work Phone (818) 354-2422 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 NASAMAIL: GLINDAL David D. Morabito Mail Stop 230-103 Work Phone (818) 393-0665 Jet Propulsion Laboratory Home Phone (818) 249-5996 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 JEMS: MORABITO SPAN: PRINCE::DMORABITO Martin Pätzold DLR-Institut für Hochfrequenztechnik Work No. (49) 8153-28-395 Oberpfaffenhofen Home No. (49) 8153-89-131 8031 Wessling Germany Fax No. (49) 8153-28-1135 E-mail: HF13@DLRVM.BITNET Herbert Porsche DLR-Institut für Hochfrequenztechnik Work No. (49) 8153-28-505 Oberpfaffenhofen Home No. (49) 8152-7483 8031 Wessling Germany Fax No. (49) 8153-28-1135 Richard A. Simpson Center for Radar Astronomy Work No. (415) 723-3525 Stanford University Home No. ( ) - Stanford, CA 94305-4055 Fax No. (415) 723-9251 NASAMAIL: RSIMPSON William L. Sjogren Mail Stop 301-150G Work Phone (818) 354-4868 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-6558 NASAMAIL: WSJOGREN David E. Smith Code 621 Work No. (301) 286-8671 Goddard Space Flight Center Home No. ( ) - Greenbelt MD 20771 Fax No. (301) 286-9200 NASAMAIL: (C:USA,ADMD:TELEMAIL,PRMD:GSFC,O:GSFCMAIL,UN:DAVIDSMITH) Massimo Tinto Mail Stop 161-228 Work Phone (818) 354-0798 Jet Propulsion Laboratory Home Phone (818) 449-2007 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 393-4643 E-Mail: G. Leonard Tyler Center for Radar Astronomy Work No. (415) 723-3535 Stanford University Home No. ( ) - Stanford CA 94305-4055 Fax No. (415) 723-9251 NASAMAIL: LTYLER Hans Volland Radioastronomisches Institut Work No. (49) 228-733674 Universitaet Bonn Home No. (49) 228-460268 Auf dem Hugel 71 D-5300 Bonn Fax No. (49) 228-525229 Germany Hugo Wahlquist Mail Stop 169-327 Work Phone (818) 354-2538 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 354-8895 E-mail: hugo@oberon.jpl.nasa.gov hugo@jpl06.jpl.nasa.gov Richard Woo Mail Stop 238-737 Work Phone (818) 354-3945 Jet Propulsion Laboratory Home Phone ( ) - 4800 Oak Grove Drive Pasadena, CA 91109 Fax Number (818) 354-2825 NASAMAIL: RWOO APPENDIX E DATA PRODUCTS LOG ULYSSES FIRST SOLAR CONJUNCTION, C1 DATA PRODUCTS EXPERIMENT DOY DSS START STOP ATDF NBODR PBIDR PF TAPE TAPE TAPE 146 61 0940 1240 ULSA0027 NO YES 147 42 0319 0524 ULSA0027 NO YES 148 43 0303 0509 ULSA0027 ULSO0065 NO 149 42 0310 0515 ULSA0027 NO YES 149 61 1600 1805 ULSA0027 NO YES 150 61 1040 1245 ULSA0027 NO YES 151 42 0305 0510 ULSA0027 NO YES 152 42 0305 0510 ULSA0027 NO YES 152 12 1840 2045 ULSA0027 NO NO 153 61 1345 1550 ULSA0027 NO YES 154 12 1846 2051 ULSA0027 NO YES 155 12 1846 2051 ULSA0027 NO YES 156 61 1036 1241 ULSA0027 NO YES 156 12 2321 157/0126 ULSA0027 NO YES 157 12 1841 2046 ULSA0027 NO YES 158 61 1341 1546 ULSA0028 NO YES 159 61 1342 1547 ULSA0028 NO YES 160 61 1337 1542 ULSA0028 NO YES 161 61 1249 1454 ULSA0028 NO YES 162 61 1334 1539 ULSA0028 NO YES 163 61 1329 1634 ULSA0028 NO YES 164 43 0639 0844 ULSA0028 ULSO0066 YES 164 12 1819 2024 ULSA0028 NO YES 165 61 1016 1221 ULSA0028 NO YES 191 42 0616 0816 ULSA0029 NO YES 192 42 0624 0824 ULSA0029 NO YES 193 42 0607 0807 ULSA0029 NO YES 194 42 0337 0537 ULSA0029 NO YES 195 61 0927 1127 ULSA0029 NO YES 196 61 1237 1437 ULSA0029 NO YES 197 61 1730 1930 ULSA0029 NO YES 198 61 1237 1437 ULSA0029 NO YES 199 42 0607 0808 ULSA0029 NO YES 200 42 0608 0808 ULSA0029 NO YES 200 12 1923 2123 ULSA0029 NO YES 201 42 0028 0228 ULSA0029 NO YES 202 42 0238 0438 ULSA0029 NO YES 202 61 1238 1438 ULSA0029 NO YES 203 42 0215 0415 ULSA0029 NO YES 204 42 0338 0538 ULSA0029 NO YES 218 63 1300 2005 ULSA0029 ULSO0166- YES ULSA0030 ULSO0170 219 43 0110 0550 ULSA0030 ULSO0095 ULSP0001 YES ULSO0096 219 61 0925 1951 ULSA0030 NO YES 220 43 0305 0810 ULSA0031 ULSO0097 YES 221 43 0200 0710 ULSA0031 ULSO0098 ULSP0002 YES 221 14 1940 2330 ULSA0032 ULSO0091 YES 221 43 2345 222/0620 ULSA0032 ULSO0099 YES 222 14 1955 223/0050 ULSA0033 ULSO0092 ULSP0003 YES ULSP0004 223 43 0105 0805 ULSA0033 ULSO0100 YES 223 14 2045 224/0105 ULSA0034 ULSO0093 YES 224 43 0120 0805 ULSA0034 ULSO0101 YES 224 63 1120 1835 ULSA0035 ULSO0171- ULSP0005 YES ULSO0176 ULSP0006 224 14 1840 2230 ULSA0035 ULSO0071 YES 225 63 1335 1835 ULSA0036 ULSO0177- YES ULSO0180 225 14 1840 226/0015 ULSA0036 ULSO0072 YES ULSO0094 226 63 1440 1835 ULSA0036 ULSO0181- YES ULSA0037 ULSO0185 226 14 1840 227/0115 ULSA0037 ULSO0073 YES 227 63 1235 1950 ULSAOO37 ULSO0186- YES ULSA0038 ULSO0190 227 12 1955 2320 ULSA0038 NO YES 227 43 2325 228/0727 ULSA0038 ULSO0102- YES ULSO0105 228 63 1441 1817 ULSA0039 ULSO0191- YES ULSO0194 228 14 1822 229/0237 ULSA0039 ULSO0074- YES ULSO0079 229 63 1441 1852 ULSA0040 ULSO0195- YES ULSO0197 229 14 1857 230/0047 ULSA0040 ULSO0080- YES ULSO0084 230 43 0052 0517 ULSA0041 ULSO0106- YES ULSO0108 230 63 0747 1807 ULSA0041 ULSO0198- YES ULSA0042 ULSO0204 230 14 1812 2117 ULSA0042 ULSO0085 YES ULSO0086 231 63 1237 1802 ULSA0042 ULSO0205- YES ULSO0208 231 14 1807 232/0002 ULSA0042 ULSO0087- YES ULSA0043 ULSO0090 232 63 1441 1652 ULSA0043 ULSO0209 YES 232 14 1657 233/0247 ULSA0043 ULSO0109- YES ULSA0044 ULSO0114 233 63 1441 1752 ULSA0044 ULSO0210- YES ULSO0212 233 14 1757 234/0047 ULSA0044 ULSO0115- YES ULSO0119 234 63 1441 1902 ULSA0044 ULSO0213- YES ULSO0215 234 14 1907 2302 ULSA0045 ULSO0120- YES ULSO0122 234 43 2307 235/0647 ULSA0045 ULSO0135- YES ULSO0139 235 63 1441 1942 ULSA0046 ULSO0216- YES ULSO0219 235 43 2302 236/0647 ULSA0046 ULSO0140- YES ULSO0144 236 63 1441 1742 ULSA0046 NO YES 236 14 1747 2252 ULSA0046 ULSO0123- YES ULSA0047 ULSO0126 236 43 2257 237/0742 ULSA0047 ULSO0145 YES ULSA0048 237 63 0747 1752 ULSA0048 ULSO0220- YES ULSA0049 ULSO0229 237 14 1757 2302 ULSA0049 ULSO0127- YES ULSO0129 238 63 0737 1917 ULSA0049 ULSO0230- YES ULSA0050 ULSO0238 238 14 1922 239/0102 ULSA0050 ULSO0130- YES ULSA0051 ULSO0134 239 43 0107 0702 ULSA0051 ULSO0146- YES ULSO0149 239 63 1322 1750 ULSA0051 ULSO0239 YES 239 14 1755 2242 ULSA0051 ULSO0150 YES ULSA0052 239 43 2247 240/0047 ULSA0052 ULSO0151 YES 240 63 1322 1916 ULSA0052 ULSO0240- YES ULSO0241 240 14 1921 241/0147 ULSA0053 ULSO0152 YES 241 63 1322 1916 ULSA0053 ULSO0242 YES 241 12 1921 2237 ULSA0053 NO YES 241 43 2242 242/0622 ULSA0053 ULSO0162 YES ULSA0054 242 14 1744 2239 ULSA0054 ULSO0153 YES 242 43 2244 243/0624 ULSA0055 ULSO0163 YES 243 63 1324 1734 ULSA0055 ULSO0243 YES 243 14 1739 244/0104 ULSA0056 ULSO0154 YES 244 63 1324 1724 ULSA0056 ULSO0244 YES 244 14 1729 245/0104 ULSA0057 ULSO0155 YES 245 63 1454 1754 ULSA0057 ULSO0245 YES 245 14 1734 246/0114 ULSA0058 ULSO0156 YES ULSO0157 246 14 1854 247/0019 ULSA0058 ULSO0158 YES 246 43 2309 247/0614 ULSA0058 ULSO0164 YES ULSA0059 247 14 1829 248/0014 ULSA0059 ULSO0159 YES 248 43 0024 0514 ULSA0060 ULSO0165 YES 248 61 0939 1344 ULSA0060 NO YES 248 14 1449 2244 ULSA0060 ULSO0160 YES ULSO0161 ULYSSES FIRST SOLAR CONJUNCTION 1991 S/C 55 ODR TAPES TAPE ID. DSS DOY START STOP COMMENTS ULSO0065 43 148 03:08:59 05:19:01 ULSO0066 43 164 06:39:51 08:44:50 ULSO0067 43 208 22:50:00 209/00:21:09 NO S-BAND ULSO0068 43 209 00:24:00 07:05:01 NO S-BAND ULSO0069 43 209 23:45:18 210/01:15:50 NO S-BAND ULSO0070 43 210 01:19:01 07:54:19 NO S-BAND ULSO0071 14 224 18:40:02 21:15:01 ULSO0072 14 225 18:40:50 18:42:16 ULSO0073 14 226 18:40:57 227/00:00:01 ULSO0074 14 228 18:22:02 19:42:38 ULSO0075 14 228 19:45:48 21:05:47 ULSO0076 14 228 21:05:47 22:25:47 ULSO0077 14 228 22:25:47 23:45:47 ULSO0078 14 228 23:45:47 229/01:05:47 ULSO0079 14 229 01:05:47 01:20:00 ULSO0080 14 229 18:57:12 20:17:12 ULSO0081 14 229 20:17:12 21:37:12 ULSO0082 14 229 21:37:12 22:57:15 NO DATA ULSO0083 14 229 23:07:33 230/00:27:33 ULSO0084 14 230 00:27:33 00:47:10 ULSO0085 14 230 18:12:14 19:32:14 ULSO0086 14 230 19:41:52 20:00:01 ULSO0087 14 231 18:07:00 19:27:00 ULSO0088 14 231 19:27:00 20:47:00 ULSO0089 14 231 20:47:00 22:07:00 BAD TAPE ULSO0090 14 231 22:07:00 22:35:01 ULSO0091 14 221 19:40:04 23:00:01 ULSO0092 14 222 19:55:37 223/00:50:35 ULSO0093 14 223 20:45:42 224/01:05:40 ULSO0094 14 225 18:42:16 23:00:01 ULSO0095 43 219 01:10:14 01:21:02 ULSO0096 43 219 01:31:27 04:45:03 ULSO0097 43 220 03:05:20 07:10:01 ULSO0098 43 221 01:40:34 07:20:03 ULSO0099 43 222 01:36:46 05:45:04 ULSO0100 43 223 01:05:02 07:00:01 ULSO0101 43 224 01:20:41 07:05:01 ULSO0102 43 228 03:00:01 03:06:03 ULSO0103 43 228 03:06:21 03:44:35 ULSO0104 43 228 03:54:06 05:14:06 ULSO0105 43 228 05:14:06 06:10:02 ULSO0106 43 230 00:52:10 02:12:10 ULSO0107 43 230 02:12:10 03:32:10 BAD TAPE ULSO0108 43 230 03:32:10 04:00:01 ULSO0109 14 232 18:12:51 19:32:51 ULSO0110 14 232 19:32:51 20:52:51 ULSO0111 14 232 20:52:51 22:12:51 ULSO0112 14 232 22:12:51 23:32:51 ULSO0113 14 232 23:32:51 233/00:52:51 ULSO0114 14 233 00:52:51 01:30:00 ULSO0115 14 233 17:57:30 19:17:30 ULSO0116 14 233 19:17:30 20:37:30 ULSO0117 14 233 20:37:30 21:57:30 ULSO0118 14 233 21:57:30 23:17:30 ULSO0119 14 233 23:17:30 23:30:01 ULSO0120 14 234 19:07:30 20:27:30 ULSO0121 14 234 20:27:30 21:47:30 ULSO0122 14 234 21:47:30 23:03:03 ULSO0123 14 236 17:47:42 19:07:42 ULSO0124 14 236 19:07:42 20:27:42 ULSO0125 14 236 20:27:42 21:47:42 ULSO0126 14 236 21:47:42 22:52:40 ULSO0127 14 237 17:57:04 19:17:04 ULSO0128 14 237 19:17:04 20:37:04 ULSO0129 14 237 20:37:04 21:45:01 ULSO0130 14 238 19:22:50 20:42:50 ULSO0131 14 238 20:42:50 22:02:50 ULSO0132 14 238 22:02:50 23:22:50 ULSO0133 14 238 23:22:50 239/00:42:50 ULSO0134 14 239 00:42:50 01:02:48 ULSO0135 43 234 23:07:33 235/00:27:33 ULSO0136 43 235 00:27:33 01:47:33 ULSO0137 43 235 01:47:33 03:07:33 ULSO0138 43 235 03:07:33 04:27:33 ULSO0139 43 235 04:27:33 05:30:01 ULSO0140 43 235 23:02:37 236/00:22:37 ULSO0141 43 236 00:22:37 01:42:37 ULSO0142 43 236 01:42:37 03:02:37 ULSO0143 43 236 03:02:37 04:22:37 ULSO0144 43 236 04:22:37 05:30:01 ULSO0145 43 236 22:57:40 23:45:01 ULSO0146 43 239 01:07:02 02:27:02 ULSO0147 43 239 02:27:02 03:47:02 ULSO0148 43 239 03:47:02 05:07:02 ULSO0149 43 239 05:07:02 05:45:01 ULSO0150 14 239 17:55:04 22:43:01 ULSO0151 43 239 22:45:02 23:30:01 ULSO0152 14 240 19:21:56 241/00:30:01 ULSO0153 14 242 17:44:05 22:39:02 ULSO0154 14 243 17:39:08 23:40:01 ULSO0155 14 244 17:29:11 23:40:01 ULSO0156 14 245 17:34:14 23:18:42 ULSO0157 14 245 23:18:42 246/01:14:12 ULSO0158 14 246 18:54:04 247/00:19:01 ULSO0159 14 247 18:29:20 248/00:14:18 ULSO0160 14 248 14:49:23 22:27:43 ULSO0161 14 248 22:27:43 22:44:21 ULSO0162 43 241 22:43:00 242/05:05:01 ULSO0163 43 242 22:45:34 243/05:05:07 ULSO0164 43 246 23:09:00 247/06:15:01 ULSO0165 43 248 00:24:19 05:14:19 ULSO0166 63 218 12:33:54 14:27:58 ULSO0167 63 218 14:36:27 15:56:28 ULSO0168 63 218 15:56:28 17:16:31 ULSO0169 63 218 17:16:31 18:36:34 ULSO0170 63 218 18:36:34 19:00:38 ULSO0171 63 224 11:20:06 11:46:42 ULSO0172 63 224 11:46:43 13:06:43 ULSO0173 63 224 13:06:43 14:26:43 ULSO0174 63 224 14:26:43 15:46:43 ULSO0175 63 224 15:46:43 17:06:43 ULSO0176 63 224 17:06:43 17:45:08 ULSO0177 63 225 13:35:57 14:55:57 ULSO0178 63 225 14:55:57 16:15:57 ULSO0179 63 225 16:15:57 17:35:57 ULSO0180 63 225 17:35:57 18:35:50 ULSO0181 63 226 13:35:25 14:55:25 ULSO0182 63 226 14:55:25 16:15:25 ULSO0183 63 226 16:15:25 16:27:30 ULSO0184 63 226 16:27:44 17:47:44 ULSO0185 63 226 17:47:44 18:00:55 ULSO0186 63 227 12:35:57 13:55:57 ULSO0187 63 227 13:55:57 15:15:57 ULSO0188 63 227 15:15:57 16:35:57 ULSO0189 63 227 16:35:57 17:55:57 ULSO0190 63 227 17:55:57 18:50:24 ULSO0191 63 228 14:31:09 15:31:24 ULSO0192 63 228 15:32:52 16:52:52 ULSO0193 63 228 16:52:52 18:12:52 ULSO0194 63 228 18:12:52 18:20:03 ULSO0195 63 229 14:01:05 15:21:05 ULSO0196 63 229 15:21:05 16:41:05 ULSO0197 63 229 16:41:05 17:52:34 ULSO0198 63 230 07:52:25 09:12:25 ULSO0199 63 230 09:12:25 10:32:25 ULSO0200 63 230 10:32:25 11:52:25 ULSO0201 63 230 11:52:25 13:12:25 ULSO0202 63 230 13:12:25 14:32:25 ULSO0203 63 230 14:32:25 15:52:25 ULSO0204 63 230 15:52:25 16:59:59 ULSO0205 63 231 12:41:24 14:01:24 ULSO0206 63 231 14:01:24 15:21:24 ULSO0207 63 231 15:21:24 16:41:24 ULSO0208 63 231 16:41:24 18:01:24 ULSO0209 63 232 14:41:29 15:50:19 ULSO0210 63 233 13:21:16 14:41:16 ULSO0211 63 233 14:41:16 16:01:16 ULSO0212 63 233 16:01:16 16:46:23 ULSO0213 63 234 14:41:38 16:01:38 ULSO0214 63 234 16:01:38 17:21:38 ULSO0215 63 234 17:21:38 18:07:07 ULSO0216 63 235 13:36:42 14:29:26 ULSO0217 63 235 14:29:27 15:49:27 ULSO0218 63 235 15:49:27 17:09:27 ULSO0219 63 235 17:09:27 18:29:27 ULSO0220 63 237 07:48:32 09:08:32 ULSO0221 63 237 09:08:32 10:28:32 ULSO0222 63 237 10:28:32 11:48:32 ULSO0223 63 237 11:48:32 13:08:32 ULSO0224 63 237 13:08:32 14:28:32 ULSO0225 63 237 14:28:32 15:48:32 ULSO0226 63 237 15:48:32 15:49:44 ULSO0227 63 237 15:48:32 15:58:52 ULSO0228 63 237 15:59:07 17:19:07 ULSO0229 63 237 17:19:07 18:24:24 ULSO0230 63 238 07:25:16 08:45:16 ULSO0231 63 238 08:45:16 10:05:16 ULSO0232 63 238 10:05:16 11:25:16 ULSO0233 63 238 11:25:16 12:45:16 ULSO0234 63 238 12:45:16 14:05:16 ULSO0235 63 238 14:05:16 15:25:16 ULSO0236 63 238 15:25:16 16:45:16 ULSO0237 63 238 16:45:16 18:05:16 ULSO0238 63 238 18:05:16 18:15:03 ULSO0239 63 239 13:17:54 16:45:49 ULSO0240 63 240 13:23:02 13:49:38 ULSO0241 63 240 13:50:20 18:10:31 ULSO0242 63 241 13:16:00 18:05:05 ULSO0243 63 243 13:19:38 17:38:18 ULSO0244 63 244 13:24:43 17:26:06 ULSO0245 63 245 14:51:10 17:55:39 ULYSSES FIRST SOLAR CONJUNCTION 1991 S/C 55 ATDF TAPES TAPE ID. START TIME STOP TIME ULSA0027 146/00:03:13 157/23:59:19 ULSA0028 156/07:56:28 191/08:54:52 ULSA0029 190/23:11:42 218/16:00:00 ULSA0030 218/14:30:00 219/15:54:08 ULSA0031 220/00:29:00 221/07:20:05 ULSA0032 221/16:50:23 222/05:46:55 ULSA0033 222/16:47:22 223/07:02:35 ULSA0034 223/17:32:42 224/07:06:12 ULSA0035 224/08:55:55 225/02:31:48 ULSA0036 225/11:04:06 226/16:44:59 ULSA0037 226/15:00:00 227/17:13:46 ULSA0038 227/15:30:00 228/06:35:28 ULSA0039 228/10:58:43 229/13:40:29 ULSA0040 229/12:11:00 230/01:16:00 ULSA0041 229/23:37:11 230/15:59:24 ULSA0042 230/14:30:00 231/20:00:00 ULSA0043 231/20:01:00 233/00:00:00 ULSA0044 232/22:30:00 234/19:05:00 ULSA0045 234/16:15:00 235/05:30:00 ULSA0046 235/10:56:12 236/17:44:00 ULSA0047 236/16:20:00 237/05:00:00 ULSA0048 237/03:00:00 237/16:30:00 ULSA0049 237/15:00:00 238/12:00:00 ULSA0050 238/10:30:00 239/00:00:00 ULSA0051 238/22:30:00 240/19:45:00 ULSA0052 239/18:25:00 241/19:19:00 ULSA0053 240/17:56:00 242/23:06:00 ULSA0054 241/21:27:00 243/22:40:00 ULSA0055 242/21:10:00 243/17:35:00 ULSA0056 243/16:05:00 244/17:24:50 ULSA0057 244/16:00:00 245/20:00:00 ULSA0058 245/16:17:13 247/00:20:45 ULSA0059 246/21:38:00 248/00:17:42 ULSA0060 247/22:50:00 248/22:50:00 APPENDIX F MEDICINA & KASHIMA AND RASM FILE TRANSFER APPENDIX G SCHEDULE OF ACTIVITIES Distribution: S. Abbate 507-215 J. Ajello 264-744 (2 copies) J. Anderson 301-230 N. Angold 264-114 J. Armstrong 238-737 S. Asmar 230-103 P. Beech 264-456 G. Benenyan 230-203 C. Berner 230-110 B. Bertotti Italy P. Beyer 303-404 M. Bird Germany S. Bolton 264-744 (2 copies) N. Borderies 301-150 J. Breidenthal 161-228 R. Burt 303-403 K. Buxbaum 264-765 R. Carlson 183-603 (2 copies) D. Chong 161-228 T. Clarke 264-744 (2 copies) M. Connally 161-228 A. Devereaux 161-228 S. Dolinsky 303-308 J. Dunne 264-419 (2 copies) D. Enari 303-404 P. Eshe 230-103 V. Eshleman Stanford U. F. Estabrook 169-327 R. Garcia Perez 246-114 R. Gershman 264-765 H. Gordon 301-125L R. Green 238-540 C. Hamilton 161-228 R. Herrera 230-103 E. Herrington 264-114 D. Hinson Stanford U. T. Horton 230-103 R. Horttor 161-228 T. Howard Stanford U. L. Iess Italy T. Johnson 183-501 K. Klaasen 168-222 (2 copies) A. Kliore 161-228 T. Krisher 301-150 G. Lindal 161-228 J. Ludwinski 264-765 (2 copies) T. Martin 264-765 (2 copies) D. Meyer 264-456 D. Morabito 230-103 N. Murphy 264-744 (2 copies) J. Nash 230-110 R. O'Conner 507-120 R. Ouellet 264-114 E. Page 169-506 M. Pätzold Germany T. Pham 161-228 C. Polansky 264-744 (2 copies) V. Pollmeier 301-276 R. Rose 507-120 E. Smith 169-506 W. Smythe 264-765 (2 copies) S. Standley 264-114 J. Taylor 161-228 E. Theilig 264-765 M. Tinto 161-228 W. Tucker 507-120 H. Wahlquist 169-327 W. Weber 238-540 P. Wenzel ESA R. Woo 238-737 Vellum File TDS managers wishing to send copies to DSCC 10, 40, 60, and NOCC Ops Chief can request extra copies from the editors. Galileo Science Team Chiefs please circulate second copy to team members. RADIO SCIENCE HANDBOOK VOLUME 3