Search NASA⌕ Search

SEARCH · Search NASA

Results for “reasoning about programs”

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 109 records · Page 6

Comparison of two computer programs by predicting turbulent mixing of helium in a ducted supersonic airstream

Two parabolic flow computer programs, SHIP (a finite-difference program) and COMOC (a finite-element program), are used for predicting three-dimensional turbulent reacting flow fields in supersonic combustors. The theoretical foundation of the two computer programs are described, and then the programs are applied to a three-dimensional turbulent mixing experiment. The cold (nonreacting) flow experiment was performed to study the mixing of helium jets with a supersonic airstream in a rectangular duct. Surveys of the flow field at an upstream were used as the initial data by programs; surveys at a downstream station provided comparison to assess program accuracy. Both computer programs predicted the experimental results and data trends reasonably well. However, the comparison between the computations from the two programs indicated that SHIP was more accurate in computation and more efficient in both computer storage and computing time than COMOC.

Pan, Y. S.↗

Implementing an Applied Science Program

The work implied in the NASA Applied Science Program requires a delicate balancing act for the those doing it. At the implementation level there are multiple tensions intrinsic to the program. For example each application of an existing product to a decision support process requires deep knowledge about the data and deep knowledge about the decision making process. It is highly probable no one person has this range of knowledge. Otherwise the decision making process would already be using the data. Therefore, a team is required. But building a team usually requires time, especially across agencies. Yet the program mandates efforts of relatively short duration. Further, those who know the data are scientists, which makes them essential to the program. But scientists are evaluated on their publication record. Anything which diverts a scientist from the research for his next publication is an anathema to him and potential death to their career. Trying to get another agency to use NASA data does not strike most scientists as material inherently suitable for publication. Also, NASA wishes to rapidly implement often substantial changes to another agency's process. For many reasons, such as budget and program constraints, speed is important. But the owner of a decision making process is tightly constrained, usually by law, regulation, organization and custom. Changes when made are slow, cautious, even hesitant, and always done according a process specific to the situation. To manage this work MSFC must balance these and other tensions. Some things we have relatively little control over, such as budget. These we try to handle by structural techniques. For example by insisting all of our people work on multiple projects simultaneously we inherently have diversification of funding for all of our people. In many cases we explicitly use some elements of tension to be productive. For example the need for the scientists to constantly publish is motivation to keep tasks short and to the immediate point. As another example, the DSS agency and it personnel are treated as integral to the effort at every step. Thus, their ways of doing things, their problems and their assets become part of the solution. MSFC also manages the Applied Science work' within a strategic framework.' First, the scientists are necessarily at the core of all of this work as well as all of the work within the larger' organization. We therefore strive to keep a roughly 50-50 balance between the work done on tasks funded directly by the research side of NASA's Science Mission Directorate and funding from the applied side. Done at both the organization level and the level of the individual, this keeps the scientist both happy and productive over the long term. We also try diligently to remove as much burden from the scientist as practical by employing people such as the authors and others to do tasks not requiring; scientific knowledge. We also have designed our effort to take full use of external partners. We actively seek and support, including fund, people from multiple organizations to join us as committed collaborators. In this we use today's money and today's problem to help us diversify and strengthen for tomorrow. MSFC also considers the Applied Science work holistically. Each element is viewed as a step in a larger process. At a management level we can chose to emphasize or encourage certain areas which service long term goals. Thus, if we think work in a particular area should be developed, we can start with the smaller, less costly elements and grow.

Rickman, Doug↗

Automated Environment Generation for Software Model Checking

A key problem in model checking open systems is environment modeling (i.e., representing the behavior of the execution context of the system under analysis). Software systems are fundamentally open since their behavior is dependent on patterns of invocation of system components and values defined outside the system but referenced within the system. Whether reasoning about the behavior of whole programs or about program components, an abstract model of the environment can be essential in enabling sufficiently precise yet tractable verification. In this paper, we describe an approach to generating environments of Java program fragments. This approach integrates formally specified assumptions about environment behavior with sound abstractions of environment implementations to form a model of the environment. The approach is implemented in the Bandera Environment Generator (BEG) which we describe along with our experience using BEG to reason about properties of several non-trivial concurrent Java programs.

Tkachuk, Oksana↗

Computer Program for the Design and Off-Design Performance of Turbojet and Turbofan Engine Cycles

The rapid computer program is designed to be run in a stand-alone mode or operated within a larger program. The computation is based on a simplified one-dimensional gas turbine cycle. Each component in the engine is modeled thermo-dynamically. The component efficiencies used in the thermodynamic modeling are scaled for the off-design conditions from input design point values using empirical trends which are included in the computer code. The engine cycle program is capable of producing reasonable engine performance prediction with a minimum of computer execute time. The current computer execute time on the IBM 360/67 for one Mach number, one altitude, and one power setting is about 0.1 seconds. about 0.1 seconds. The principal assumption used in the calculation is that the compressor is operated along a line of maximum adiabatic efficiency on the compressor map. The fluid properties are computed for the combustion mixture, but dissociation is not included. The procedure included in the program is only for the combustion of JP-4, methane, or hydrogen.

Morris, S. J.↗

Design knowledge capture for a corporate memory facility

Currently, much of the information regarding decision alternatives and trade-offs made in the course of a major program development effort is not represented or retained in a way that permits computer-based reasoning over the life cycle of the program. The loss of this information results in problems in tracing design alternatives to requirements, in assessing the impact of change in requirements, and in configuration management. To address these problems, the problem was studied of building an intelligent, active corporate memory facility which would provide for the capture of the requirements and standards of a program, analyze the design alternatives and trade-offs made over the program's lifetime, and examine relationships between requirements and design trade-offs. Early phases of the work have concentrated on design knowledge capture for the Space Station Freedom. Tools are demonstrated and extended which helps automate and document engineering trade studies, and another tool is being developed to help designers interactively explore design alternatives and constraints.

Boose, John H.↗

OSHA Bloodborne Pathogens Standards Exposure Control Plan

The Hummer Associates Exposure Control Plan is designed to reduce significant occupational exposure to bloodborne pathogens and infectious materials for Hummer Associates health care personnel. Under universal precautions, all patients and all body fluids are considered potentially infectious for bloodborne pathogens. Medical personnel need not be at increased risk if universal precautions are correctly understood and followed. This program covers all employees who could reasonably anticipate contact with blood or other potentially infectious materials during the performance of their job responsibilities. Although HIV and hepatitis B are mentioned most often, this program applies to all bloodborne diseases. The two main components needed to implement this program are universal precautions and engineering/work practice controls. This program covers all employees who may have occupational exposure to blood or other potentially infectious materials. Other aspects of this program are discussed.

Luhrs, Caro Elise↗

Analysis of pressure-broadened ozone spectra in the 3 micron region

The Molecular Spectroscopy Lab at NASA-Langley has been involved in a long term effort to carefully characterize the infrared spectra of small molecules of atmospheric interest, including methane, water vapor, ozone, and their isotopic counterparts. High resolution gas phase infrared spectra are obtained using both a tunable diode laser system, and the McMath Fourier transform spectrometer at the Kitt Peak Solar Observatory. Spectra are obtained at various pressures and temperatures for pure gas samples, and for samples containing mixtures of the species of interest in nitrogen, oxygen, or air. From these spectra, using a nonlinear least squares fitting technique, spectral parameters of position, intensity, and half-width were determined for varying laboratory conditions that approximate atmospheric conditions experienced in remote sensing situations. These parameters are of interest in theoretical studies of these species, as well as in allowing more accurate interpretation of remote sensing data. The current work involves the analysis of a series of McMath FTIR spectra of ozone broadened by mixing with air, nitrogen, or oxygen. Each spectrum covers the region from 2396 to 4057/cm. Each vibrational band is analyzed by first diving its region into small intervals containing a few well isolated absorption lines of reasonable intensity. Each of these small intervals is fit by multiple iterations of the nonlinear least square program until residuals are minimized to a reasonable value which corresponds to the noise level of the measured spectrum. Intervals for the 3 nu(sub 3) ozone band in the region from 3000 to 3060 wavenumbers are being examined.

Prochaska, Eleanor S.↗

TraceContract: A Scala DSL for Trace Analysis

In this paper we describe TRACECONTRACT, an API for trace analysis, implemented in the SCALA programming language. We argue that for certain forms of trace analysis the best weapon is a high level programming language augmented with constructs for temporal reasoning. A trace is a sequence of events, which may for example be generated by a running program, instrumented appropriately to generate events. The API supports writing properties in a notation that combines an advanced form of data parameterized state machines with temporal logic. The implementation utilizes SCALA's support for defining internal Domain Specific Languages (DSLs). Furthermore SCALA's combination of object oriented and functional programming features, including partial functions and pattern matching, makes it an ideal host language for such an API.

log file analysis↗

Evaluation of human engineering design standard (MSFC-STD-267A) in the design of manned space vehicles

The major conclusion of the detailed examination of the human factors engineering design standard is that it is unsuitable for future spacecraft design. The standard, published in 1966, was not intended to be a zero or reduced gravity standard and was directed primarily toward ground support equipment and technology. Futhermore, ambiguities, conflicts, and unenforceable requirements contribute to the difficulty. The role of man in future space missions and its impact on human engineering standards are also discussed, and it is concluded that greater standardization is vital to the success of future missions. A survey of NASA/MSFC contractors was made, and it was found that MSFC-STD-267A is largely ignored and the most significant problems are inaccessibility and nonspecificity of the data. The resistance of contract management and designer and of program managers is a primary reason for poor human engineering design. Specific recommendations for improvement of format and organization, including an interim solution, are given.

Rogers, J. G.↗

Assessment of the environmental aspects of the DOE phosphoric acid fuel cell program

The likely facets of a nationwide phosphoric acid fuel cell (PAFC) power plant commercial system are described. The beneficial and adverse environmental impacts produced by the system are assessed. Eleven specific system activities are characterized and evaluated. Also included is a review of fuel cell technology and a description of DOE's National Fuel Cell Program. Based on current and reasonably foreseeable PAFC characteristics, no environmental or energy impact factor was identified that would significantly inhibit the commercialization of PAFC power plant technology.

Lundblad, H. L.↗

Slave finite element for non-linear analysis of engine structures. Volume 2: Programmer's manual and user's manual

The programming aspects of SFENES are described in the User's Manual. The information presented is provided for the installation programmer. It is sufficient to fully describe the general program logic and required peripheral storage. All element generated data is stored externally to reduce required memory allocation. A separate section is devoted to the description of these files thereby permitting the optimization of Input/Output (I/O) time through efficient buffer descriptions. Individual subroutine descriptions are presented along with the complete Fortran source listings. A short description of the major control, computation, and I/O phases is included to aid in obtaining an overall familiarity with the program's components. Finally, a discussion of the suggested overlay structure which allows the program to execute with a reasonable amount of memory allocation is presented.

Witkop, D. L.↗

Putting time into proof outlines

A logic for reasoning about timing of concurrent programs is presented. The logic is based on proof outlines and can handle maximal parallelism as well as resource-constrained execution environments. The correctness proof for a mutual exclusion protocol that uses execution timings in a subtle way illustrates the logic in action.

Schneider, Fred B.↗

User interface support

Space construction will require heavy investment in the development of a wide variety of user interfaces for the computer-based tools that will be involved at every stage of construction operations. Using today's technology, user interface development is very expensive for two reasons: (1) specialized and scarce programming skills are required to implement the necessary graphical representations and complex control regimes for high-quality interfaces; (2) iteration on prototypes is required to meet user and task requirements, since these are difficult to anticipate with current (and foreseeable) design knowledge. We are attacking this problem by building a user interface development tool based on extensions to the spreadsheet model of computation. The tool provides high-level support for graphical user interfaces and permits dynamic modification of interfaces, without requiring conventional programming concepts and skills.

Lewis, Clayton↗

The X2000 Program: An Institutional Approach to Enabling Smaller Spacecraft

NASA's X2000 Program is important for many reasons - It develops the technology that will enable new types of deep space space exploration - It is a new, faster and cheaper process for technology infusion into NASA missions - It transfers these capabilities to US industry so they are available for future spacecraft. Many of these new capabilities are relevant to Earth missions as well X2000 will work with the NASA Goddard Space Flight Center (and others) to help make these capabilities available to a larger community.

Deutsch, Les↗

Origin of Dips in 4U1915-05

This grant supported our participation in a proposal submitted by Didier Barret to conduct a study of the dipping LMXB 4U1915-05. In this Final Report, we summarize the Scientific Objectives of this investigation and the results achieved. Data analysis is still in progress and publication of results will be forthcoming.Our objectives in this work have been to study: 1. Spectra of dips in 4 Ul916-05: This low mass x-ray binary (LMXB) is a 50min binary system and the first to show x-ray dip behaviour. Our XMM observation was proposed to study the x-ray spectra of the dips to better constrain their physical properties. Of primary interest is the variation of the absorbing column density as a function of flux in the dip. We wish to isolate the absorption from Compton scattering components in the dip spectra, and to use the large throughput of XMM to better constrain short timescale variations of the spectrum in the dips. 2. Period of the dips and long-term ephemeris: We also seek to improve upon the long- term ephemeris of the dips by combining these more recent XMM data with earlier RXTE data to update the ephemeris for dips and the determination of the dip period to further test whether the dip period represents the true binary period of this LMXB. We shall extend the ephemeris published by Chou, Grindlay and Bloser 2001, ApJ, 549, 1135) to test the assertion of Retter, Chou et a1 2002, MNRAS, 330, 37 that the dips are indeed the binary period and not a precession period. 1 3 Results Achieved The observations for this program were delayed, presumably for reasons related to the general difficulty of scheduling XMM targets in this region moderately close to the Cygnus region. 4'171916-05 was finally observed (2lksec) on April 24, 2002, but the data have not been delivered. A second observation was conducted on September 9, 2002 (18ksec) and the data are still being analyzed. 4 Papers Presented and Published A paper is in preparation for Astronomy and Astrophysics in which the full results of this investigation will be reported. 1. Barret, D. et a1 2003, Astron. and Astophys.,in press. 2

Grindlay, Jonathan E.↗

A Proposed Strategy for the U.S. to Develop and Maintain a Mainstream Capability Suite ("Warehouse") for Automated/Autonomous Rendezvous and Docking in Low Earth Orbit and Beyond

The ability of space assets to rendezvous and dock/capture/berth is a fundamental enabler for numerous classes of NASA fs missions, and is therefore an essential capability for the future of NASA. Mission classes include: ISS crew rotation, crewed exploration beyond low-Earth-orbit (LEO), on-orbit assembly, ISS cargo supply, crewed satellite servicing, robotic satellite servicing / debris mitigation, robotic sample return, and robotic small body (e.g. near-Earth object, NEO) proximity operations. For a variety of reasons to be described, NASA programs requiring Automated/Autonomous Rendezvous and Docking/Capture/Berthing (AR&D) capabilities are currently spending an order-of-magnitude more than necessary and taking twice as long as necessary to achieve their AR&D capability, "reinventing the wheel" for each program, and have fallen behind all of our foreign counterparts in AR&D technology (especially autonomy) in the process. To ensure future missions' reliability and crew safety (when applicable), to achieve the noted cost and schedule savings by eliminate costs of continually "reinventing the wheel ", the NASA AR&D Community of Practice (CoP) recommends NASA develop an AR&D Warehouse, detailed herein, which does not exist today. The term "warehouse" is used herein to refer to a toolbox or capability suite that has pre-integrated selectable supply-chain hardware and reusable software components that are considered ready-to-fly, low-risk, reliable, versatile, scalable, cost-effective, architecture and destination independent, that can be confidently utilized operationally on human spaceflight and robotic vehicles over a variety of mission classes and design reference missions, especially beyond LEO. The CoP also believes that it is imperative that NASA coordinate and integrate all current and proposed technology development activities into a cohesive cross-Agency strategy to produce and utilize this AR&D warehouse. An initial estimate indicates that if NASA strategically coordinates the development of a robust AR&D capability across the Agency, the cost of implementing AR&D on a spacecraft could be reduced from roughly $70M per mission to as low as $7M per mission, and the associated development time could be reduced from 4 years to 2 years, after the warehouse is completely developed. Table 1 shows the clear long-term benefits to the Agency in term of costs and schedules for various missions. (The methods used to arrive at the Table 1 numbers is presented in Appendices A and B.)

Krishnakumar, Kalmanje S.↗

The systematic evolution of a NASA software technology, Appendix C

A long range program is described whose ultimate purpose is to make possible the production of software in NASA within predictable schedule and budget constraints and with major characteristics such as size, run-time, and correctness predictable within reasonable tolerances. As part of the program a pilot NASA computer center will be chosen to apply software development and management techniques systematically and determine a set which is effective. The techniques will be developed by a Technology Group, which will guide the pilot project and be responsible for its success. The application of the technology will involve a sequence of NASA programming tasks graduated from simpler ones at first to complex systems in late phases of the project. The evaluation of the technology will be made by monitoring the operation of the software at the users' installations. In this way a coherent discipline for software design, production maintenance, and management will be evolved.

Deregt, M. P.↗

Space Industrialization. Volume 2: Opportunities, Markets and Programs

The nature of space industrialization and the reasons for its promotion are examined. Increases in space industry activities to be anticipated from 1980 to 2010 are assessed. A variety of future scenarios against which space industrialization could evolve were developed and the various industrial opportunities that might constitute that evolution were defined. The needs and markets of industry activities were quantitatively and qualitatively assessed and messed. The various hardware requirements vs. time (space industry programs) as space industrialization evolves are derived and analyzed.

Source record↗