Study of a soft lander/support module for Mars missions. Volume 1 - Summary Final summary report
Soft lander support module for Mars missions - summary
SEARCH · Search NASA
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.
Soft lander support module for Mars missions - summary
Tiros VII satellite operational attitude data and orbital elements
TIROS VIII operational definitive attitude data
Mission planning for lunar and planetary exploration
A long-lived space-based system that converts on-orbit solar and/or nuclear energy to a suitable form for distribution to using space systems is described. Mission applications, requirements, issues, problems, benefits, and technology thrusts are identified for the multipurpose power platform. Power levels of at least 10-100Kw are required for space manufacturing, satellites, and space station operations. Two Mw are needed for a proposed passive radar system. Propulsion system requirements are in the 100Kw-100Mw range.
Enabling technology needs and other requirements to support space industrialization include: large space structures; fabrication and joining processes; single stage to orbit and heavy lift launch vehicles; nuclear and solar space power systems; robotics, manipulators, and teleoperators; biotechnology in space; artificial gravity; the utilization of lunar materials for construction; and the extraction of oxygen and metals from lunar resources. New initiatives (FY 1978) directly supportive or partly related to space industrialization are listed.
Preliminary (1977-1983), intermediate (1982-1988), and long term (1989+) phases of the search for extraterrestrial intelligence (SETI) program are examined as well as the benefits to be derived in radioastronomy and the problems to be surmounted in radio frequency interference. The priorities, intrinsic value, criteria, and strategy for the search are discussed for both terrestrial and lunar-based CYCLOPS and for a space SETI system located at lunar liberation point L4. New initiatives related to antenna independent technology, multichannel analyzers, and radio frequency interference shielding are listed. Projected SETI program costs are included.
Major strategies for exploring the solar system focus on the return of information and the return of matter. Both the planetary exploration facility, and an orbiting automated space station, and the sample return and exploration facility have similar requirements. The single most essential need to enable intensive study of the outer solar system is nuclear propulsion and power capability. New initiatives in 1978 related to the reactor, data and sample acquisition and return, navigation, and environmental protection are examined.
The benefits to be obtained from cost-effective global observation of the earth, its environment, and its natural and man-made features are examined using typical spacecraft and missions which could enhance the benefits of space operations. The technology needs and areas of interest include: (1) a ten-fold increase in the dimensions of deployable and erectable structures to provide booms, antennas, and platforms for global sensor systems; (2) control and stabilization systems capable of pointing accuracies of 1 arc second or less to locate targets of interest and maintain platform or sensor orientation during operations; (3) a factor of five improvements in spacecraft power capacity to support payloads and supporting electronics; (4) auxiliary propulsion systems capable of 5 to 10 years on orbit operation; (5) multipurpose sensors; and (6) end-to-end data management and an information system configured to accept new components or concepts as they develop.
Technology requirements for an integrated space transportation system capability which will allow the nation to use space efficiently, reliably, and routinely in the years between 1985 and 2000 with a significant return on invested resources will build on the currently defined space transportation system using shuttle, the IUS, and the advanced upper stage such as the solar electric propulsion system. Contributing technologies should include those which support (1) total reusability with minimal refurbishment; (2) responsiveness to high launch rate requirements when operation and energy are the predominant recurring costs; and (3) maximum flexibility in operation between earth and LEO and between LEO and GEO. Initiatives undertaken to advance the heavy lift to launch vehicles, single stage to orbit vehicles, and orbit transfer vehicles are listed.
Only a few efforts are currently underway to develop an adequate technology base for the various themes. Particular attention must be given to software commonality and evolutionary capability, to increased system integrity and autonomy; and to improved communications among the program users, the program developers, and the programs themselves. There is a need for quantum improvement in software development methods and increasing the awareness of software by all concerned. Major thrusts identified include: (1) data and systems management; (2) software technology for autonomous systems; (3) technology and methods for improving the software development process; (4) advances related to systems of software elements including their architecture, their attributes as systems, and their interfaces with users and other systems; and (5) applications of software including both the basic algorithms used in a number of applications and the software specific to a particular theme or discipline area. The impact of each theme on software is assessed.
All themes require some form of advanced propulsion capabilities to achieve their stated objectives. Requirements cover a broad spectrum ranging from a new generation of heavy lift launch vehicles to low thrust, long lift system for on-orbit operations. The commonality extant between propulsive technologies was established and group technologies were grouped into vehicle classes by functional capability. The five classes of launch vehicles identified by the space transportation theme were augmented with a sixth class, encompassing planetary and on-orbit operations. Propulsion technologies in each class were then ranked, and assigned priority numbers. Prioritized technologies were matched to theme requirements.
The research and technology base program was examined to determine those tasks which either enabled or enhanced a theme and should be incorporated into that theme, and to identify new and promising R&T candidates which should be incorporated into the R&T base to meet essential long range space technology goals not addressed by the various themes. Candidates in the ongoing tasks category generally reflect the reorientation or pursuit of an ongoing RTOP on specific theme objectives, primarily involving the development and ground testing of new technology components and systems. Thirty-eight recommended candidate tasks are listed.
The engineering test program for the lander and the orbiter are presented. The engineering program was developed to achieve confidence that the design was adequate to survive the expected mission environments and to accomplish the mission objective.
Extended abstracts from the fourth workshop on the technical and scientific aspects of mesosphere stratosphere troposphere (MST) radar are presented. Individual sessions addressed the following topics: meteorological applications of MST and ST radars, networks, and campaigns; the dynamics of the equatorial middle atmosphere; interpretation of radar returns from clear air; techniques for studying gravity waves and turbulence, intercomparison and calibration of wind and wave measurements at various frequencies; progress in existing and planned MST and ST radars; hardware design for MST and ST radars and boundary layer/lower troposphere profilers; signal processing; and data management.
The fifth High-Lift Prediction Workshop (HLPW-5), which involved the high-lift version of the NASA common research model in several configurations, assessed various computational fluid dynamics methods, including Reynolds-averaged Navier-Stokes (RANS) and hybrid large-eddy simulations. This paper summarizes RANS solutions computed on fixed grids. Case 1, a verification case, considered a simple wing-body configuration and focused on grid convergence of lift, drag, and pitching moment coefficients. Case 2 is a configuration buildup case that focused on predicting the effects of increasing geometric complexity. For buildup configurations with slats, flaps, and a nacelle/pylon (configurations 2.2, 2.3, and 2.4), wind-tunnel data were provided by ONERA. Case 3 focused on the reference landing configuration at four Reynolds-number conditions. For Case 1, grid-converged RANS solutions were achieved using the standard Spalart-Allmaras (SA) turbulence model and the SA model with a quadratic constitutive relation and a rotation correction. Agreement between RANS solutions was observed for the simplest configuration 2.1 of Case 2 with the standard SA model. For other configurations, agreement between RANS solutions was hampered by insufficient iterative and grid convergence, especially at high angles of attack. In comparison with the experiment, RANS solutions qualitatively showed the correct configuration buildup trend but underpredicted lift and overpredicted both drag and pitching moment at high angles of attack.
Regression verification techniques are used to prove equivalence of syntactically similar programs. Checking equivalence of large programs, however, can be computationally expensive. Existing regression verification techniques rely on abstraction and decomposition techniques to reduce the computational effort of checking equivalence of the entire program. These techniques are sound but not complete. In this work, we propose a novel approach to improve scalability of regression verification by classifying the program behaviors generated during symbolic execution as either impacted or unimpacted. Our technique uses a combination of static analysis and symbolic execution to generate summaries of impacted program behaviors. The impact summaries are then checked for equivalence using an o-the-shelf decision procedure. We prove that our approach is both sound and complete for sequential programs, with respect to the depth bound of symbolic execution. Our evaluation on a set of sequential C artifacts shows that reducing the size of the summaries can help reduce the cost of software equivalence checking. Various reduction, abstraction, and compositional techniques have been developed to help scale software verification techniques to industrial-sized systems. Although such techniques have greatly increased the size and complexity of systems that can be checked, analysis of large software systems remains costly. Regression analysis techniques, e.g., regression testing [16], regression model checking [22], and regression verification [19], restrict the scope of the analysis by leveraging the differences between program versions. These techniques are based on the idea that if code is checked early in development, then subsequent versions can be checked against a prior (checked) version, leveraging the results of the previous analysis to reduce analysis cost of the current version. Regression verification addresses the problem of proving equivalence of closely related program versions [19]. These techniques compare two programs with a large degree of syntactic similarity to prove that portions of one program version are equivalent to the other. Regression verification can be used for guaranteeing backward compatibility, and for showing behavioral equivalence in programs with syntactic differences, e.g., when a program is refactored to improve its performance, maintainability, or readability. Existing regression verification techniques leverage similarities between program versions by using abstraction and decomposition techniques to improve scalability of the analysis [10, 12, 19]. The abstractions and decomposition in the these techniques, e.g., summaries of unchanged code [12] or semantically equivalent methods [19], compute an over-approximation of the program behaviors. The equivalence checking results of these techniques are sound but not complete-they may characterize programs as not functionally equivalent when, in fact, they are equivalent. In this work we describe a novel approach that leverages the impact of the differences between two programs for scaling regression verification. We partition program behaviors of each version into (a) behaviors impacted by the changes and (b) behaviors not impacted (unimpacted) by the changes. Only the impacted program behaviors are used during equivalence checking. We then prove that checking equivalence of the impacted program behaviors is equivalent to checking equivalence of all program behaviors for a given depth bound. In this work we use symbolic execution to generate the program behaviors and leverage control- and data-dependence information to facilitate the partitioning of program behaviors. The impacted program behaviors are termed as impact summaries. The dependence analyses that facilitate the generation of the impact summaries, we believe, could be used in conjunction with other abstraction and decomposition based approaches, [10, 12], as a complementary reduction technique. An evaluation of our regression verification technique shows that our approach is capable of leveraging similarities between program versions to reduce the size of the queries and the time required to check for logical equivalence. The main contributions of this work are: - A regression verification technique to generate impact summaries that can be checked for functional equivalence using an off-the-shelf decision procedure. - A proof that our approach is sound and complete with respect to the depth bound of symbolic execution. - An implementation of our technique using the LLVMcompiler infrastructure, the klee Symbolic Virtual Machine [4], and a variety of Satisfiability Modulo Theory (SMT) solvers, e.g., STP [7] and Z3 [6]. - An empirical evaluation on a set of C artifacts which shows that the use of impact summaries can reduce the cost of regression verification.
NASA's Office of Aeronautics and Space Technology (OAST) conducted a workshop on technology for space station evolution 16-19 Jan. 1990. The purpose of this workshop was to collect and clarify Space Station Freedom technology requirements for evolution and to describe technologies that can potentially fill those requirements. These proceedings are organized into an Executive Summary and Overview and five volumes containing the technology discipline presentations. The Executive Summary and Overview contains an executive summary for the workshop, the technology discipline summary packages, and the keynote address. The executive summary provides a synopsis of the events and results of the workshop and the technology discipline summary packages.