Search NASA⌕ Search

SEARCH · Search NASA

Results for “Data System”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 469 records · Page 26

Scaling the Pipe: NASA EOS Terra Data Systems at 10

Standard products from the five sensors on NASA's Earth Observing System's (EOS) Terra satellite are being used world-wide for earth science research and applications. This paper describes the evolution of the Terra data systems over the last decade in which the distributed systems that produce, archive and distribute high quality Terra data products were scaled by two orders of magnitude.

Wolfe, Robert E.↗

Tracking and data system support for the Mariner Mars 1971 mission. Volume 2: First trajectory correction maneuver through orbit insertion

The Deep Space Tracking and Data System activities in support of the Mariner Mars 1971 project from the first trajectory correction maneuver on 4 June 1971 through cruise and orbit insertion on 14 November 1971 are presented. Changes and updates to the TDS requirements and to the plan and configuration plus detailed information on the TDS flight support performance evaluation and the preorbital testing and training are included. With the loss of Mariner 8 at launch, a few changes to the Mariner Mars 1971 requirements, plan, and configuration were necessitated. Mariner 9 is now assuming the former mission plan of Mariner 8, including the TV mapping cycles and a 12-hr orbital period. A second trajectory correction maneuver was not required because of the accuracy of the first maneuver. All testing and training for orbital operations were completed satisfactorily and on schedule. The orbit insertion was accomplished with excellent results.

Textor, G. P.↗

Radio science ground data system for the Voyager-Neptune encounter, part 1

The Voyager radio science experiments at Neptune required the creation of a ground data system array that includes a Deep Space Network complex, the Parkes Radio Observatory, and the Usuda deep space tracking station. The performance requirements were based on experience with the previous Voyager encounters, as well as the scientific goals at Neptune. The requirements were stricter than those of the Uranus encounter because of the need to avoid the phase-stability problems experienced during that encounter and because the spacecraft flyby was faster and closer to the planet than previous encounters. The primary requirement on the instrument was to recover the phase and amplitude of the S- and X-band (2.3 and 8.4 GHz) signals under the dynamic conditions encountered during the occultations. The primary receiver type for the measurements was open loop with high phase-noise and frequency stability performance. The receiver filter bandwidth was predetermined based on the spacecraft's trajectory and frequency uncertainties.

Kursinski, E. R.↗

An end-to-end command and control concept for NASA data systems

Spacecraft command and control are currently taking on the characteristics of general computer-to-computer interprocess communication. The evolution of these systems during the 1980s will give NASA a true general-purpose end-to-end data request capability for the first time. This concept is presented in outline, with consideration of many of the detailed analyses and subsystem tradeoffs being performed as part of the NEEDS (NASA End-to-End Data System) program.

Desjardins, R.↗

Space station data system analysis/architecture study. Task 2: Options development, DR-5. Volume 2: Design options

The primary objective of Task 2 is the development of an information base that will support the conduct of trade studies and provide sufficient data to make key design/programmatic decisions. This includes: (1) the establishment of option categories that are most likely to influence Space Station Data System (SSDS) definition; (2) the identification of preferred options in each category; and (3) the characterization of these options with respect to performance attributes, constraints, cost and risk. This volume contains the options development for the design category. This category comprises alternative structures, configurations and techniques that can be used to develop designs that are responsive to the SSDS requirements. The specific areas discussed are software, including data base management and distributed operating systems; system architecture, including fault tolerance and system growth/automation/autonomy and system interfaces; time management; and system security/privacy. Also discussed are space communications and local area networking.

Source record↗

Data automation system.

Data automation system /DAS/ on Mariner IV MARS probe involving real and nonreal time for experiments during cruise and encounter flights

REAL TIME↗

Tracking and data system support for the Pioneer project. Volume 3: Pioneer 10 from 1 April 1972 through the Jupiter encounter period, January 1974

The Tracking and Data Systems support of the Pioneer 10 mission from April 1, 1972 through the Jupiter encounter period which ended January 5, 1974 is described. The period covered involves operations in the interplanetary environment from the time of completion of the second trajectory correction to the start of Jupiter encounter; the implementation, planning, and testing that lead to the Jupiter encounter; and the operations during the 60 day encounter period.

Miller, R. B.↗

A Space Data System Standard for Telerobotic Operations

The Telerobotics Working Group of the Mission Operations and Information Management Services Area of the Consultative Committee for Space Data Systems is drafting a document that will help bound the scope of an eventual international standard for telerobotic operations services. This paper will present the work in progress and provide background for how the international community is beginning to define standards in telerobotic operations that will help ensure the success of complex missions to explore beyond Earth orbit.

Mittman, David S.↗

Thermocouples electrically checked while connected to data system

Constant current source is connected across the input of the millivolt measuring system to monitor the electrical continuity and resistance of multiple thermocouple installations without disconnecting them from a data system. This technique monitored gage thermocouple leads during the assembly and preflight testing of the Project Fire reentry packages.

Source record↗

A Linearized Prognostic Cloud Scheme in NASAs Goddard Earth Observing System Data Assimilation Tools

A linearized prognostic cloud scheme has been developed to accompany the linearized convection scheme recently implemented in NASA's Goddard Earth Observing System data assimilation tools. The linearization, developed from the nonlinear cloud scheme, treats cloud variables prognostically so they are subject to linearized advection, diffusion, generation, and evaporation. Four linearized cloud variables are modeled, the ice and water phases of clouds generated by large-scale condensation and, separately, by detraining convection. For each species the scheme models their sources, sublimation, evaporation, and autoconversion. Large-scale, anvil and convective species of precipitation are modeled and evaporated. The cloud scheme exhibits linearity and realistic perturbation growth, except around the generation of clouds through large-scale condensation. Discontinuities and steep gradients are widely used here and severe problems occur in the calculation of cloud fraction. For data assimilation applications this poor behavior is controlled by replacing this part of the scheme with a perturbation model. For observation impacts, where efficiency is less of a concern, a filtering is developed that examines the Jacobian. The replacement scheme is only invoked if Jacobian elements or eigenvalues violate a series of tuned constants. The linearized prognostic cloud scheme is tested by comparing the linear and nonlinear perturbation trajectories for 6-, 12-, and 24-h forecast times. The tangent linear model performs well and perturbations of clouds are well captured for the lead times of interest.

Precipitation↗

Determination of an Optimal Commercial Data Bus Architecture for a Flight Data System

NASA/Marshall Space Flight Center (MSFC) is continually looking for methods to reduce cost and schedule while keeping the quality of work high. MSFC is NASA's lead center for space transportation and microgravity research. When supporting NASA's programs several decisions concerning the avionics system must be made. Usually many trade studies must be conducted to determine the best ways to meet the customer's requirements. When deciding the flight data system, one of the first trade studies normally conducted is the determination of the data bus architecture. The schedule, cost, reliability, and environments are some of the factors that are reviewed in the determination of the data bus architecture. Based on the studies, the data bus architecture could result in a proprietary data bus or a commercial data bus. The cost factor usually removes the proprietary data bus from consideration. The commercial data bus's range from Versa Module Eurocard (VME) to Compact PCI to STD 32 to PC 104. If cost, schedule and size are prime factors, VME is usually not considered. If the prime factors are cost, schedule, and size then Compact PCI, STD 32 and PC104 are the choices for the data bus architecture. MSFC's center director has funded a study from his discretionary fund to determine an optimal low cost commercial data bus architecture. The goal of the study is to functionally and environmentally test Compact PCI, STD 32 and PC 104 data bus architectures. This paper will summarize the results of the data bus architecture study.

Crawford, Kevin↗

Advanced concepts for telemetry data systems

The Consultative Committee for Space Data Standards (CCSDS) has defined Advanced Orbiting System (AOS) standards for the overall architectural framework of future packet telemetry systems. The standards encompass a CCSDS principal network covering the onboard space-link and ground systems, and furnishes an asynchronous (telemetry/internetworking) and isochronous (audio and video) data-transport services employing CCSDS packets and virtual channels. Attention is given to changes envisioned in ground telemetry processing systems currently in use, as well as to the application of CCSDS standards to future systems.

Pritchard, James A.↗