Search NASA⌕ Search

SEARCH · Search NASA

Results for “Missions Data”

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 37 records · Page 2

Using EventScope with Mars Mission Data to Create Geoscience Curricula

EventScope is an educational software application that incorporates Mars mission data to teach geologic and scientific concepts using 3D (three-dimensional) models of planetary surfaces. It serves as a supplement to middle school science curricula. Additional information is contained in the original extended abstract.

McElfresh, S. B. Z.↗

What Do Our Users Want? Perspectives on Understanding and Meeting User Needs for Multi-Mission Data Services

The Sun-Earth Connection Active Archive (SECAA) project of NASA's Space Physics Data Facility operates a range of unique and heavily used multi-mission data services in support of the large-scale science objectives of the Great Observatory, including services such as CDAWeb, the CDAWeb Plus client, SSCWeb, OMNIweb and the CDF data format. In developing and operating these services, we have encountered and continue to struggle with a wide range of issues such as balancing scope and functionality with simplicity and ease of use, understanding the effectiveness of our choices and identifying areas most important for further improvement. In this paper, we will review our key services and then discuss some of our observations and new approaches to understanding and meeting user data service requirements. Some observations are obvious but may still have substantial implications; e.g. functionality without information content is of little user interest, which has led to our recent emphasis on development of web services interfaces, so the content and functionality we already serve is readily and fully available as a building block for new services. Some observations require careful design and tradeoffs; e.g. users will complain when they are offered interfaces with limited options but users are also easily intimidated and become lost when offered extensive options for customization. Some observations remain highly challenging; e.g. a comprehensive multi-mission, multi-source view of all data and services available easily produces a daunting list, but a more selective view can easily lead users to overlook available and relevant data. It is often difficult to obtain and meaningfully interpret measures of true productive usage and overall user satisfaction, even with a variety of techniques including statistics, citations, case studies, user feedback and advisory committees. Most of these issues will apply to and may even be more acute for distributed implementation architectures.

McGuire, Robert E.↗

High-degree Gravity Models from GRAIL Primary Mission Data

We have analyzed Ka‒band range rate (KBRR) and Deep Space Network (DSN) data from the Gravity Recovery and Interior Laboratory (GRAIL) primary mission (1 March to 29 May 2012) to derive gravity models of the Moon to degree 420, 540, and 660 in spherical harmonics. For these models, GRGM420A, GRGM540A, and GRGM660PRIM, a Kaula constraint was applied only beyond degree 330. Variance‒component estimation (VCE) was used to adjust the a priori weights and obtain a calibrated error covariance. The global root‒mean‒square error in the gravity anomalies computed from the error covariance to 320×320 is 0.77 mGal, compared to 29.0 mGal with the pre‒GRAIL model derived with the SELENE mission data, SGM150J, only to 140×140. The global correlations with the Lunar Orbiter Laser Altimeter‒derived topography are larger than 0.985 between l = 120 and 330. The free‒air gravity anomalies, especially over the lunar farside, display a dramatic increase in detail compared to the pre‒GRAIL models (SGM150J and LP150Q) and, through degree 320, are free of the orbit‒track‒related artifacts present in the earlier models. For GRAIL, we obtain an a posteriori fit to the S‒band DSN data of 0.13 mm/s. The a posteriori fits to the KBRR data range from 0.08 to 1.5 micrometers/s for GRGM420A and from 0.03 to 0.06 micrometers/s for GRGM660PRIM. Using the GRAIL data, we obtain solutions for the degree 2 Love numbers, k20=0.024615+/-0.0000914, k21=0.023915+/-0.0000132, and k22=0.024852+/-0.0000167, and a preliminary solution for the k30 Love number of k30=0.00734+/-0.0015, where the Love number error sigmas are those obtained with VCE.

Primary 1↗

Evaluating near-surface soil moisture using Heat Capacity Mapping Mission data

Four dates of Heat Capacity Mapping Mission (HCMM) data were analyzed in order to evaluate HCMM thermal data use in estimating near-surface soil moisture in a complex agricultural landscape. Because of large spatial and temporal ground cover variations, HCMM radiometric temperatures alone did not correlate with soil water content. The radiometric temperatures consisted of radiance contributions from different canopies and their respective soil backgrounds. However, when surface soil temperatures were empirically estimated from HCMM temperatures and percent cover of each pixel, a highly significant correlation was obtained between the estimated soil temperatures and near-surface soil water content.

Heilman, J. L.↗

Standard format data units - Tools for automatic exchange of space mission data

A set of standard formatting rules for the data sets, and a standard computer-readable language with which to describe the data, are two tools which are used to create the Standard Format Data Unit (SFDU). The NASA/JPL proposal for creation and utilization of SFDUs is presented, and its relationship to recommendations from the Consultative Committee for Space Data Systems (CCSDS) is discussed. Several current and planned implementations of the SFDU concept among major space flight projects are identified. The purpose of creating the concept of an SFDU is to allow members of the science community to share national and global resource data independently of project or program. The feedback from SFDU implementation efforts is considered an essential part of the CCSDS activity. Even though the CCSDS specifically deals with space data systems, the SFDU concept can be applied to practically every data system on an open network. The SFDU is in the early phase of CCSDS standard definition work, and must go through several other phases before being formally recommended as an international standard.

Willett, J. B.↗

Mission planning and execution within the mission data system

Not only has the number of launched spacecraft per year exploded over the past few years, but also spacecraft are getting progressively more complex, as flyby missions give way to remote orbiters, which in turn give way to rovers and other in situ explorers. To address the software issues in this expanding mission set, JPL started the Mission Data System (MDS) project, an effort to make flight software engineering more straightforward and less prone to error through the eplicit modeling of spacecraft state. This paper presents how MDS performs mission planning and execution in the context of explicitly managing spacecraft state.

MDS↗

Catalog of Viking mission data

This catalog announces the present/expected availability of scientific data acquired by the Viking missions and contains descriptions of the Viking spacecraft, experiments, and data sets. An index is included listing the team leaders and team members for the experiments. Information on NSSDC facilities and ordering procedures, and a list of acronyms and abbreviations are included in the appendices.

Vostreys, R. W.↗

Architecture and Dynamics of Kepler's Multi-Transiting Planet Systems.III. Comprehensive Investigation Using All Four Years of Kepler Mission Data

We study the orbital architectures of planetary systems orbiting within ∼1 AU of their stars by analyzing the ensemble of Kepler systems having two or more planet candidates. We use data from the entire Kepler mission, and in many cases we apply improved analysis techniques (e.g., replacing histograms by top-hat Kernel Density Estimators that avoid the loss of information resulting from choosing a particular phase for the bin boundaries) to extend and enhance the studies of Lissauer et al. (2011, ApJS 197, 8) and Fabrycky et al. (2014, ApJ 790, 146).These data show ~ 1700 transiting planet candidates in > 600 multiple-planet systems, far more than were available for our previous two studies. The increased numbers and better information about planetary radii and the properties of stellar hosts made possible by Gaia DR2 allow more statistically-robust analyses of the entire ensemble of Kepler multis as well as independent analyses of subsets of the population. We are thus able to contrast the dynamical configurations of small and large planets, short-period and longer-period planets, and planets orbiting various types of host stars. We reinforce our previous findings that most pairs of planets within the same system are neither in nor near low-order mean motion resonances and that there is a substantial excess of planets having period ratios slightly larger than those of first-order mean-motion resonances. However, neglecting three systems whose planets are locked in 3- body resonances and summing over all first-order mean motion resonances, the deficit of planet pairs with period ratios just narrow of resonance is as large as the excess of planets wide of resonance (within statistical uncertainties), suggesting that overall there is no overall excess of planet pairs in the vicinity of resonance. Other aspects of our study, including estimates of the typical relative inclinations of planetary orbits and their variations as functions of orbital period, planet sizes and stellar properties, are in progress, with results expected to be available for presentation by the time of the conference.

Lissauer, Jack↗

Introduction to mission data system

MDS state-based architecture. A system compromises project assets in the context of some external environments that influences them. The function of mission software is to monitor and control a system to meet operators' intents.

MDS mission data system↗