Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 127 records · Page 7

User's guide to program FLEXSTAB

A manual is presented for correctly submitting program runs in aerodynamics on the UNIVAC 1108 computer system. All major program modules are included. Control cards are documented for the user's convenience, and card parameters are included in order to provide some idea as to reasonable time estimates for the program modules.

Cavin, R. K., III↗

Practices for Demonstrating Energy Savings from Commercial PACE Projects

Nearly three-fourths of U.S. states have authorized local governments to use voluntary special assessments on commercial properties to finance energy improvements that boost economic development, create jobs, increase property values and advance energy goals. Commercial Property Assessed Clean Energy (C-PACE) financing allows building owners to repay the borrowed capital — from private or public sources — over time using their property as security. Berkeley Lab is supporting the Department of Energy’s Commercial PACE Working Group by developing a series of C-PACE issue briefs. The second brief in this series, Practices for Demonstrating Energy Savings from Commercial PACE Projects, looks at common practices for demonstrating energy savings to support state and local governments that sponsor C-PACE programs and want to track their energy impacts. This brief reviews: -The value proposition and trade-offs of conducting energy impact assessments for C-PACE programs; -Methods to quantify energy savings impacts from energy efficiency building improvements; and -Available resources and tools to support energy impact assessments. C-PACE programs may benefit from energy impact assessments for many reasons, including: -Validating the public benefits of the programs -Demonstrating that C-PACE can deliver participant benefits -Illustrating program impacts on public policy goals -Generating data to help improve program performance Many C-PACE programs are collecting data on project energy savings impacts, and these data can be leveraged to further support decision making and program implementation. Potential drawbacks to energy impact assessments may include added cost and burdens on property owners (e.g., the need to collect building energy consumption data). Where these burdens are considerable, they might slow program uptake. State and local governments can balance the benefits of energy impact assessments with the range of costs and accuracy inherent to available assessment methodologies. Additionally, depending on the policy context in the state or local government, a C-PACE program may be able to leverage existing efforts (e.g., building energy benchmarking programs) to reduce impact assessment costs, align with building owner practices and expectations, and efficiently assess program impact.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

Liquid Flyback Booster Pre-Phase A Study Assessment

Mw concept of a flyback booster has been around since early in the Shuttle program. The original two-stage Shuttle concepts used a manned flyback booster. These boosters were eliminated from the program for funding and size reasons. The current Shuttle uses two Redesigned Solid Rocket Motors (RSRMs), which are recovered and refurbished after each flight; this is one of the major cost factors of the program. Replacement options have been studied over the past ten years. The conclusion reached by the most recent study is that the liquid flyback booster (LFBB) is the only competitive option from a life-cycle cost perspective. The purpose of this study was to assess the feasibility and practicality of LFBBs. The study provides an expansion of the recommendations made during the during the aforementioned study. The primary benefits are the potential for enhanced reusability and a reuction of recurring costs. The potential savings in vehicle turnaround could offset the up-front costs. Development of LFBBs requires a commitment to the Shuttle program for 20 to 30 years. LFBBs also offer enhanced safety and abort capabilities. Currently, any failure of an RSRM can be considered catastrophic since them we no intact abort capabilities during the burn of the RSRMS. The performance goal of the LFBBs was to lift a fully loaded Orbiter under optimal conditions, so as not to be the limiting factor of the performance capability of the Shuttle. In addition, a final benefit is the availability of growth paths for applications other than the Shuttle.

Peterson, W.↗

Liquid flyback booster pre-phase: A study assessment

The concept of a flyback booster has been around since early in the shuttle program. The original two-stage shuttle concepts used a manned flyback booster. These boosters were eliminated from the program for funding and size reasons. The current shuttle uses two Redesigned Solid Rocket Motors (RSRM's), which are recovered and refurbished after each flight; this is one of the major cost factors of the program. Replacement options have been studied over the past ten years. The conclusion reached by the most recent study is that the liquid flyback booster (LFBB) is the only competitive option from a life-cycle cost perspective. The purpose of this study was to assess the feasibility and practicality of LFBB's. The study provides an expansion of the recommendations made during the aforementioned study. The primary benefits are the potential for enhanced reusability and a reduction of recurring costs. The potential savings in vehicle turnaround could offset the up-front costs. Development of LFBB's requires a commitment to the shuttle program for 20 to 30 years. LFBB's also offer enhanced safety and abort capabilities. Currently, any failure of an RSRM can be considered catastrophic, since there are no intact abort capabilities during the burn of the RSRM's. The performance goal of the LFBB's was to lift a fully loaded orbiter under optimal conditions, so as not to be the limiting factor of the performance capability of the shuttle. In addition, a final benefit is the availability of growth paths for applications other than shuttle.

Peterson, W.↗

Verification and Planning Based on Coinductive Logic Programming

Coinduction is a powerful technique for reasoning about unfounded sets, unbounded structures, infinite automata, and interactive computations [6]. Where induction corresponds to least fixed point's semantics, coinduction corresponds to greatest fixed point semantics. Recently coinduction has been incorporated into logic programming and an elegant operational semantics developed for it [11, 12]. This operational semantics is the greatest fix point counterpart of SLD resolution (SLD resolution imparts operational semantics to least fix point based computations) and is termed co- SLD resolution. In co-SLD resolution, a predicate goal p( t) succeeds if it unifies with one of its ancestor calls. In addition, rational infinite terms are allowed as arguments of predicates. Infinite terms are represented as solutions to unification equations and the occurs check is omitted during the unification process. Coinductive Logic Programming (Co-LP) and Co-SLD resolution can be used to elegantly perform model checking and planning. A combined SLD and Co-SLD resolution based LP system forms the common basis for planning, scheduling, verification, model checking, and constraint solving [9, 4]. This is achieved by amalgamating SLD resolution, co-SLD resolution, and constraint logic programming [13] in a single logic programming system. Given that parallelism in logic programs can be implicitly exploited [8], complex, compute-intensive applications (planning, scheduling, model checking, etc.) can be executed in parallel on multi-core machines. Parallel execution can result in speed-ups as well as in larger instances of the problems being solved. In the remainder we elaborate on (i) how planning can be elegantly and efficiently performed under real-time constraints, (ii) how real-time systems can be elegantly and efficiently model- checked, as well as (iii) how hybrid systems can be verified in a combined system with both co-SLD and SLD resolution. Implementations of co-SLD resolution as well as preliminary implementations of the planning and verification applications have been developed [4]. Co-LP and Model Checking: The vast majority of properties that are to be verified can be classified into safety properties and liveness properties. It is well known within model checking that safety properties can be verified by reachability analysis, i.e, if a counter-example to the property exists, it can be finitely determined by enumerating all the reachable states of the Kripke structure.

Bansal, Ajay↗

TMIS-design knowledge capture

The Boeing Advanced Technology Center is conducting research towards the goal of building a corporate memory facility that will provide techniques for capturing and using decision history and rationale throughout the lifecycle of a major NASA program. 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 lifecycle 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, we are studying the problem 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.

Boose, John H.↗

Analytical and experimental investigation of aircraft metal structures reinforced with filamentary composites. Phase 1: Concept development and feasibility

The analytical and experimental investigations are described in the first phase of a program to establish the feasibility of reinforcing metal aircraft structures with advanced filamentary composites. The interactions resulting from combining the two types of materials into single assemblies as well as their ability to function structurally were studied. The combinations studied were boron-epoxy reinforced aluminum, boron-epoxy reinforced titanium, and boron-polyimide reinforced titanium. The concepts used unidirectional composites as reinforcement in the primary loading direction and metal for carrying the transverse loads as well as its portion of the primary load. The program established that several realistic concepts could be fabricated, that these concepts could perform to a level that would result in significant weight savings, and that there are means for predicting their capability within a reasonable degree of accuracy. This program also encountered problems related to the application of polyimide systems that resulted in their relatively poor and variable performance.

Oken, S.↗

Toward Automatic Scalability Analysis of Message Passing Programs: A Case Study

Scalability analysis forms an important component of any performance debugging cycle, for massively parallel machines. However, tools that help in performing such analysis for parallel programs are non-existent. The primary reason for lack of such tools is the complexity involved in capturing program dynamics such as communication-computation overlap, communication latencies and memory hierarchy reference patterns. In this paper, we highlight some simple techniques that can be used to study scalability of explicit message-passing parallel programs that consider the above issues. We start from the high level source code and use a methodology for deducing communication characteristics and its impact on the total execution time of the program. The approach is validated with the help of a pipelined method for solving scalar tri-diagonal systems, using both simulations and symbolic cost models on the Intel hypercube.

Sarukkai, Sekhar R.↗

Implementing embedded artificial intelligence rules within algorithmic programming languages

Most integrations of artificial intelligence (AI) capabilities with non-AI (usually FORTRAN-based) application programs require the latter to execute separately to run as a subprogram or, at best, as a coroutine, of the AI system. In many cases, this organization is unacceptable; instead, the requirement is for an AI facility that runs in embedded mode; i.e., is called as subprogram by the application program. The design and implementation of a Prolog-based AI capability that can be invoked in embedded mode are described. The significance of this system is twofold: Provision of Prolog-based symbol-manipulation and deduction facilities makes a powerful symbolic reasoning mechanism available to applications programs written in non-AI languages. The power of the deductive and non-procedural descriptive capabilities of Prolog, which allow the user to describe the problem to be solved, rather than the solution, is to a large extent vitiated by the absence of the standard control structures provided by other languages. Embedding invocations of Prolog rule bases in programs written in non-AI languages makes it possible to put Prolog calls inside DO loops and similar control constructs. The resulting merger of non-AI and AI languages thus results in a symbiotic system in which the advantages of both programming systems are retained, and their deficiencies largely remedied.

Feyock, Stefan↗

Rooftop Photovoltaics and Electric Vehicle Co-Adoption: Attitudes, Norms, Diffusion, and Economics

The overall objectives of the project were to (1) Identify personal and social norms, peer effects, demographics and contextual factors (such as household energy expenditures, experience with outages, charging infrastructure availability) that may facilitate or hinder Solar-EV co-adoption; (2) outline strategies for the design of programs and practices that will enable reasoned RPV and EV adoption and their co-adoption; and (3) assemble a dataset comprised of survey responses of RPV-EV co-adopters, RPV-only adopters, EV-only adopters, and non-adopters. These objectives were only partially fulfilled given the decision to terminate the project. The research team was able to complete the semi-structured interviews, the core BY1 task and summarize the results below. As well, once the team learned of the research project’s fate, it sought and obtained the DOE SETO Technical Manager’s approval to repurpose funds for BY2 tasks to the extent feasible. Rather than invest further resources in expanding the pool of potential survey respondents and having no budget to survey, the research team repurposed funds subject and undertook a more limited (geographically) survey, but also expanded to it to include contingent valuation questions. The analysis of the survey data will necessarily be delayed given the lack of budget support, although some information on the respondent sample is in the results. Given a lack of attention to co-adoption previously, the insights generated in this project should assist decision-makers and industry actors in the development of programs and practices that enable reasoned RPV adoption and EV adoption and their co-adoption.

14 SOLAR ENERGY↗

History and Logic Model NASA Goddard Space Flight Center Instrument and Payload Systems Engineering Technical Performance Study

Historically, some NASA missions have exceeded schedule and cost commitments. Studies suggest technical performance is a contributor. The 1980 NASA Project Management Study concluded, "one of the most significant contributors to cost and schedule growth is inadequate definition of technical and management aspects of a program..." (as cited in GAO/NSIAD-93-97, p. 11). The 1991 NASA Roles and Missions Report identified a "need for increased emphasis on technological readiness and requirements on the front end of a program" (as cited in GAO/NSIAD-93-97, p. 11). The 1992 NASA Program Costs Report stated that NASA officials identified, among other things, "insufficient definition studies... [and] program redesigns and technical complexities" as reasons for cost and schedule overruns (GAO/NSAID-93-97, p. 11). The 2002 Task Force on Acquisition of National Security Space Programs found "requirements definition and control issues, unhealthy cost bias in proposal evaluation, widespread lack of budget reserves required to implement high risk programs on schedule, and an overall underappreciation of the importance of appropriately staffed and trained system engineering staff to manage the technologically demanding and unique aspects of space programs" (DoD, 2003, p.i.) In 2007, The NASA Office of the Chief Engineer chartered the NASA Instrument Capability Study (NICS) “to determine whether NASA instrument developers are facing challenges that impact the capability to design and build quality instruments or whether there are flaws in the acquisition strategy evidenced by schedule delays, cost overruns, and increased technical risk via design deficiencies. The... team was also chartered to determine if occurrences [are]... isolated cases or if there are generic issues... If the issues [are] found to be generic, the team [is] to offer solutions to recover such capability" (NICS Report, 2008, p. vi). The 2008 NICS Report, led by Goddard Space Flight Center (GSFC), identified challenges to instrument technical performance consistent with findings from previous reports. In 2017, the Instrument Project Division (IPD) Implementation Study was initiated to determine if there was a change in meeting schedule and cost commitments after implementing certain NICS recommendations. In 2018, the Instrument Technical Performance Study was initiated to determine the current state of Instrument Technical Performance in the GSFC Payload & Instrument Systems Engineering Branch. The purpose of the combined studies is to answer the question, "Is there a relationship between meeting NASA scientific instrument technical success and meeting schedule and cost commitments? If yes, what is the relationship?" References Department of Defense Office of the Under Secretary of Defense for Acquisition, Technology, and Logistics. (2003). The report of the defense science board/ air force scientific advisory board joint task force on acquisition of national security space programs. Washington DC. Government Accounting Office. (1992). NASA program costs: Space missions require substantially more funding than initially estimated. GAO/NSIAD-93-97. Washington DC. National Aeronautics and Space Administration, National Oceanic and Atmospheric Agency, Department of Defense. (2008). The NASA instrument capability study final report. NP-2008-11-058-GSFC. Washington DC.

Robbins, Geraldine↗

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment making feasible the operation of tens or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗

A Portable Battery for Objective, Nonobtrusive Measures of Human Performance

A need exists for a standardized battery of human performance tests in order to measure the effects of various treatments. The present paper reports on progress in such a program, funded jointly by NASA and the Navy. Three batteries are available which differ in length (7.5, 15, and 30 minutes), and number of tests in the battery (3, 10, and 15). All tests are implemented on a portable, lap-held, briefcase-sized microprocessor (NEC PC 8201A). Performances measured include information processing, memory, visual perception, reasoning, motor skills, etc. Current programs are underway to determine norms, reliabilities, stabilities, factor structure of tests, comparisons with marker tests, apparatus suitability, etc.

Kennedy, Robert S.↗

A study of the sonic-boom characteristics of a blunt body at a Mach number of 6

An experimental and analytical study of the sonic boom static pressure signatures generated by a blunt body at mach 6 has shown that finite difference computer programs can be used to give reasonable estimates of the signatures. The calculated near field static pressure signature was extrapolated to the far field by a program using the method of characteristics. A comparison of this extrapolated signature with the signature predicted by far field sonic boom theory (linearized) shows that peak overpressures are about the same, at least up to mach, but the far field theory overestimates the length of the signature.

Ashby, G. C., Jr.↗

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.↗