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.
The tabular display report generator (TABDIS) program is described. The program functions as a document generation tool that provides tabular displays of data stored on a data file which has been generated by a user program. The main features of the program are outlined and all necessary inputs are detailed.
Tabular adaptive predictive model for trajectory following control of nonlinear plant with switched two-level input
A tabular outline of comparative data is presented for 340 basic dimensional, morphological, and structural parameters and related aspects for three craters of the flat-floored, central uplift type, two of which are natural terrestrial impact craters and one is a large-scale experimental explosion crater. The three craters are part of a general class, in terms of their morphology and structural deformation that is represented on each of the terrestrial planets including the moon. One of the considered craters, the Flynn Creek Crater, was formed by a hypervelocity impact event approximately 360 m.y. ago in what is now north central Tennessee. The impacting body appears to have been a carbonaceous chondrite or a cometary mass. The second crater, the Steinheim Crater, was formed by an impact event approximately 14.7 m.y. ago in what is now southwestern Germany. The Snowball Crater was formed by the detonation of a 500-ton TNT hemisphere on flat-lying, unconsolidated alluvium in Alberta, Canada.
Properties of astronomical time scales (ET and UT) are considered, with particular emphasis on correctly determining of-date longitude as the sum of inertial mean longitude of the sun relative to the mean equinox of a fixed epoch (1950.0), and the general precession in longitude accumulated since the epoch. The inertial mean longitude and motion (relative to the mean equinox) are derived from tabular ephemerides such as the Jet Propulsion Laboratories' DE 102 and DE 96, by comparisons with subroutines based on Newcomb's perturbation theory. An unresolved inconsistency of approximately 1 second per century among the mean inertial motion of DE 102, IAU precession speed (1976), and the classical Newcomb of-date mean motion is found. Interpretation difficulties arising from the use of different systems of Ephemeris Time are also discussed.
We describe PVS's capabilities for representing tabular specifications of the kind advocated by Parnas and others, and show how PVS's Type Correctness Conditions (TCCs) are used to ensure certain well-formedness properties. We then show how these and other capabilities of PVS can be used to represent the AND/OR tables of Leveson and the Decision Tables of Sherry, and we demonstrate how PVS's TCCs can expose and help isolate errors in the latter. We extend this approach to represent the mode transition tables of the Software Cost Reduction (SCR) method in an attractive manner. We show how PVS can check these tables for well-formedness, and how PVS's model checking capabilities can be used to verify invariants and reachability properties of SCR requirements specifications, and inclusion relations between the behaviors of different specifications. These examples demonstrate how several capabilities of the PVS language and verification system can be used in combination to provide customized support for specific methodologies for documenting and analyzing requirements. Because they use only the standard capabilities of PVS, users can adapt and extend these customizations to suit their own needs. Those developing dedicated tools for individual methodologies may find these constructions in PVS helpful for prototyping purposes, or as a useful adjunct to a dedicated tool when the capabilities of a full theorem prover are required. The examples also illustrate the power and utility of an integrated general-purpose system such as PVS. For example, there was no need to adapt or extend the PVS model checker to make it work with SCR specifications described using the PVS TABLE construct: the model checker is applicable to any transition relation, independently of the PVS language constructs used in its definition.
For several decades the NASA Glenn Research Center has been providing a file of thermodynamic data for use in several computer programs. These data are in the form of least-squares coefficients that have been calculated from tabular thermodynamic data by means of the NASA Properties and Coefficients (PAC) program. The source thermodynamic data are obtained from the literature or from standard compilations. Most gas-phase thermodynamic functions are calculated by the authors from molecular constant data using ideal gas partition functions. The Coefficients and Properties (CAP) program described in this report permits the generation of tabulated thermodynamic functions from the NASA least-squares coefficients. CAP provides considerable flexibility in the output format, the number of temperatures to be tabulated, and the energy units of the calculated properties. This report provides a detailed description of input preparation, examples of input and output for several species, and a listing of all species in the current NASA Glenn thermodynamic data file.
For several decades the NASA Glenn Research Center has been providing a file of thermodynamic data for use in several computer programs. These data are in the form of least-squares coefficients that have been calculated from tabular thermodynamic data by means of the NASA Properties and Coefficients (PAC) program. The source thermodynamic data are obtained from the literature or from standard compilations. Most gas-phase thermodynamic functions are calculated by the authors from molecular constant data using ideal gas partition functions. The Coefficients and Properties (CAP) program described in this report permits the generation of tabulated thermodynamic functions from the NASA least-squares coefficients. CAP provides considerable flexibility in the output format, the number of temperatures to be tabulated, and the energy units of the calculated properties. This report provides a detailed description of input preparation, examples of input and output for several species, and a listing of all species in the current NASA Glenn thermodynamic data file.
Data handling system, using digital computer, for making orbital calculations
Bang-bang control using adaptive-predictive model applied to least-square error trajectory control of settling-time nonlinear systems
One way velocity increments obtainable from one and two stage propulsive configurations for expended and reusable modes - tables
Direct trajectories to Jupiter and Saturn - data tabulations
The trajectory data are presented chronologically and are organized by holding the arrival date constant while varying the Earth departure date in increments of 10 days. Upon completion of the specified range of Earth departure dates, the arrival date is incremented and the range of departure dates is repeated. The range of departure and arrival dates and the corresponding increments are given in Table 5-1 for each launch opportunity. It should be noted that the interval in arrival date is increased in the long flight time region where the variation of the trajectory parameters is relatively small. The criteria used for the selection of these dates are, in general: (i) the minimum Earth departure hyperbolic excess speed (across the Earth departure window) shall not exceed 0.65 EMOS and (2) the periapsis radius at Jupiter shall not be less than 0.95 planet radii.
A systematic verification of Landsat data classifications of the Portland, Oregon metropolitan area has been undertaken on the basis of census tract data. The degree of systematic misclassification due to the Bayesian classifier used to process the Landsat data was noted for the various suburban, industrialized and central business districts of the metropolitan area. The Landsat determinations of residential land use were employed to estimate the number of automobile trips generated in the region and to model air pollution hazards.
The trajectory data are presented chronologically and are organized by holding the arrival date constant while varying the Earth departure date in increments of 10 days. Upon completion of the specified range of Earth departure dates, the arrival date is incremented and the range of departure dates is repeated. For long trip times, where the variation of the trajectory parameters is relatively small, the size of the increment of the arrival date is increased. The range of departure and arrival dates and their corresponding increments are given i n Table 4-1 for each launch opportunity. The criterion for the selection of these dates is that they encompass the region in which the Earth departure hyperbolic excess speed is less than or equal to 0.65 EMOS.
The trajectory data are presented chronologically and are organized by holding the arrival date constant while varying the Earth departure date in increments of 10 days. Upon completion of the specified range of Earth departure dates, the arrival date is incremented and the range of departure dates is repeated. For long trip times, where the variation of the trajectory parameters is relatively small, the size of the increment of the arrival date is increased. The range of departure and arrival dates and their corresponding increments are given in Table 5-1 for each launch opportunity. The criterion for the selection of these dates is that they encompass the region in which the Earth departure hyperbolic excess speed is less than or equal to 0.65 EMOS. There are two lines of print for each trajectory (departure-date/arrival date pair). In the first line the two left most columns contain the dates of departure and arrival. The next 18 columns of the first line can be divided into three groups: six columns of data related to departure, six columns pertinent to the heliocentric phase of the mission, and six columns related to arrival at the target planet. The second line of print contains, respectively, the Delta V requirements for departure and arrival, the total Delta V requirement, the heliocentric transfer trajectory type, and four parameters defining conditions at arrival. The value computed for the arrival Delta V is for entry into a circular orbit. The radius selected for this orbit, while necessarily somewhat arbitrary, is representative of the broad range of orbit radii which tend to minimize the arrival Delta V for the range of excess speeds between 0.1 and 0.8 EMOS. The value selected for Uranus and Neptune is 3 planet radii. Significant reductions in the computed Delta V can be realized by assuming entry into an elliptical orbit having a periapsis radius equal to the selected circular-orbit radius. The magnitude of the reduction can be determined from Figures 2-6 and 2-8 i n Section 2.
The benefits of automatic-application code generation are widely accepted within the software engineering community. These benefits include raised abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at Kennedy Space Center recognized the need for PLC code generation while developing the new ground checkout and launch processing system, called the Launch Control System (LCS). Engineers developed a process and a prototype software tool that automatically translates a high-level representation or specification of application software into ladder logic that executes on a PLC. All the computer hardware in the LCS is planned to be commercial off the shelf (COTS), including industrial controllers or PLCs that are connected to the sensors and end items out in the field. Most of the software in LCS is also planned to be COTS, with only small adapter software modules that must be developed in order to interface between the various COTS software products. A domain-specific language (DSL) is a programming language designed to perform tasks and to solve problems in a particular domain, such as ground processing of launch vehicles. The LCS engineers created a DSL for developing test sequences of ground checkout and launch operations of future launch vehicle and spacecraft elements, and they are developing a tabular specification format that uses the DSL keywords and functions familiar to the ground and flight system users. The tabular specification format, or tabular spec, allows most ground and flight system users to document how the application software is intended to function and requires little or no software programming knowledge or experience. A small sample from a prototype tabular spec application is shown.
The tabular calibration method used at the Solar Energy Research Institute (SERI) for primary reference cells is derived and described in detail. An uncertainty analysis shows that the tabular method should have a total uncertainty of + or - 1.0 percent; data from five years of calibrations are then shown to support this analysis. Results from SERI's tabular method are compared with terrestrial calibrations performed by the NASA Lewis Research Center in the late 1970s.
A number of new aircraft concepts have recently been proposed which tightly couple the propulsion system design and operation with the overall vehicle design and performance characteristics. These concepts include propulsion technology such as boundary layer ingestion, hybrid electric propulsion systems, distributed propulsion systems and variable cycle engines. Initial studies examining these concepts have typically used a traditional decoupled approach to aircraft design where the aerodynamics and propulsion designs are done a-priori and tabular data is used to provide inexpensive look ups to the trajectory ana-ysis. However the cost of generating the tabular data begins to grow exponentially when newer aircraft concepts require consideration of additional operational parameters such as multiple throttle settings, angle-of-attack effects on the propulsion system, or propulsion throttle setting effects on aerodynamics. This paper proposes a new modeling approach that eliminated the need to generate tabular data, instead allowing an expensive propulsion or aerodynamic analysis to be directly integrated into the trajectory analysis model and the entire design problem optimized in a fully coupled manner. The new method is demonstrated by implementing a canonical optimal control problem, the F-4 minimum time-to-climb trajectory optimization using three relatively new analysis tools: Open M-DAO, PyCycle and Pointer. Pycycle and Pointer both provide analytic derivatives and Open MDAO enables the two tools to be combined into a coupled model that can be run in an efficient parallel manner that helps to cost the increased cost of the more expensive propulsion analysis. Results generated with this model serve as a validation of the tightly coupled design method and guide future studies to examine aircraft concepts with more complex operational dependencies for the aerodynamic and propulsion models.