Search NASA⌕ Search

SEARCH · Search NASA

Results for “Software development”

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 1,171 records · Page 65

Nuclear Power Plant Ontology in OWL Format

This document describes an ontology for Nuclear Power Plant sites for use in software developed by Peng Yue of George Mason University, the intelligent Geospatial Feature Discovery System (iGFDS). The ontology was developed from unclassified and open sources available on the Web, primarily from Wikipedia. Figures 1 and 2 are screenshots of the Protégé application showing the classes of the Nuclear Power Plant Ontology which was developed in the OWL format. The ontology contains supplemental information that is not shown in these screenshots and that appears as “comments” in the Annotations window. For example, “SteamGenerator” and “SecondaryCoolant” only apply to “PWR” reactors. The ontology is based on general professional knowledge of Nuclear Power Plant operation and contains a number of components necessary for understanding and modeling the functionality of a Nuclear Power Plant. The content of the ontology is not limited to equipment and buildings that can be typically observed in the imagery. The things that can be seen are often the higher level items (CoolingTower, TurbineBuilding, ContainmentBuilding, etc.). It should be pointed out that PWR plants will be much easier to identify, generally, compared to BWR plants, due to the characteristic containment structure. The information on the TransformerYard was obtained from other sources not associated specifically with Nuclear Power Plants This ontology has to be viewed as a starting point of development ontologies for assisting with identification of Nuclear Power Plant sites with the GMU software. It can be a model for ontologies for other industrial sites. The classes and relations in the ontology have to be rearranged in a way that is most suitable for feature detection. Also the classes pertaining to visible components or signs of operation of a nuclear power plant will have to be linked to classes and properties of the objects in imagery that can be detected by image processing algorithms. Note that the current ontology does not contain statements about anything that is not present at a Nuclear Power Plant site, for example, “a Nuclear Power Plant DOES NOT HAVE a large pile of coal or other raw materials”, which would help logically to differentiate it from other types of power plants.

Ward, Richard C.↗

Multiple IMU system development, volume 1

A redundant gimballed inertial system is described. System requirements and mechanization methods are defined and hardware and software development is described. Failure detection and isolation algorithms are presented and technology achievements described. Application of the system as a test tool for shuttle avionics concepts is outlined.

Landey, M.↗

SEASAT A satellite scatterometer

The analyses performed in the early period of the program which formed the basis of the sensor design is reviewed, along with the sensor design. The test program is outlined, listing all tests performed and the environmental exposure (simulated) for each, as applicable. Ground support equipment designed and built for assembly integration and field testing is described. The software developed during the program and the algorithms/flow diagrams which formed the bases for the software are summarized.

Bianchi, R.↗

Nasa-wide Standard Administrative Systems

Factors to be considered in developing agency-wide standard administrative systems for NASA include uniformity of hardware and software; centralization vs. decentralization; risk exposure; and models for software development.

Schneck, P.↗

Information System Life-Cycle And Documentation Standards (SMAP DIDS)

Although not computer program, SMAP DIDS written to provide systematic, NASA-wide structure for documenting information system development projects. Each DID (data item description) outlines document required for top-quality software development. When combined with management, assurance, and life cycle standards, Standards protect all parties who participate in design and operation of new information system.

Source record↗

A comparison of software for the modeling and control of flexible systems

A researcher proposes a cooperative effort among specialists who use or develop software for simulating and analyzing the control of flexible aerospace systems. A comparison of existing software for modeling control systems and flexible structures, applied to several example problems would be quite valuable. The comparison would indicate computational efficiency and capabilities with respect to handling nonlinearities and graphical output. Because of the diversity of applications of such software, the researcher believes that the proposed cooperative effort can transcend projects involving specific applications. Comparisons of software capability and efficiency can be made and gaps can be identified. In this way the results of the cooperative effort can provide guidance for individual projects. Several charts which outline the objectives and approach of the proposed cooperative effort are given here.

Taylor, Lawrence W., Jr.↗

Improving software quality - The use of formal inspections at the Jet Propulsion Laboratory

The introduction of software formal inspections (Fagan Inspections) at JPL for finding and fixing defects early in the software development life cycle are reviewed. It is estimated that, by the year 2000, some software efforts will rise to as much as 80 percent of the total. Software problems are especially important at NASA as critical flight software must be error-free. It is shown that formal inspections are particularly effective at finding and removing defects having to do with clarity, correctness, consistency, and completeness. A very significant discovery was that code audits were not as effective at finding defects as code inspections.

Bush, Marilyn↗

An instrument to measure the charge, and energy spectrum (20-1000 GeV/a) of the cosmic ray species oxygen to iron

BUGS-4 (Bristol University Gas Scintillator-4) made its maiden engineering flight from Fort Summer (NM) on the 29th of September 1993. The instrument was consumed by fire after striking a power line during landing following 24 hours at float. The analysis of the telemetered data from this sophisticated instrument is a demanding task. Early analysis was compromised by electronic artifacts. Unravelling these problems has been difficult and time consuming, especially as the flight hardware was burned beyond salvage, but is is an essential preliminary to analysis. During this report period we have concentrated on a small sub-set of data (the first 30,000 events; 90 minutes at float), and developed software algorithms to correct systematic errors. Using these corrected events we have begun to develop the analysis algorithms. Although the analysis is preliminary, and restricted to the first 30,000 events, the results are encouraging, and suggest the design concepts are well matched to this application. Further work will refine the analysis, and allow quantitative evaluation of the concepts employed in BUGS-4 for applicability to future instruments. We believe this work will justify fabrication of a new instrument employing techniques deployed on BUGS-4.

Gregory, J. C.↗

The Development of a User Inclusion Strategy for CLCS Display Design

This report summarizes a ten week effort to evaluate the software development process in the Checkout and Launch Control System (CLCS) for the presence of user inclusion in the design operation. A background is presented that highlights the value of achieving usability through user inclusion, progress-to-date is described, and future work is suggested so that a user inclusive design environment can be accomplished.

Jacko, Julie A.↗

LK Scripting Language

The LK scripting language is a simple and fast computer programming language designed for easy integration with existing software to enable automation of tasks. The LK language is used by NREL’s System Advisor Model (SAM), the SAM Software Development Kit (SDK), and SolTrace products. LK is easy extensible and adaptable to new software due to its small footprint and is designed to be statically linked into other software. It is written in standard C++, is cross-platform (Windows, Linux, and OSX), and includes optional portions that enable direct integration with graphical user interfaces written in the open source C++ wxWidgets Version 3.0+ toolkit.

Source record↗

General-Purpose Electronic System Tests Aircraft

Versatile digital equipment supports research, development, and maintenance. Extended aircraft interrogation and display system is general-purpose assembly of digital electronic equipment on ground for testing of digital electronic systems on advanced aircraft. Many advanced features, including multiple 16-bit microprocessors, pipeline data-flow architecture, advanced operating system, and resident software-development tools. Basic collection of software includes program for handling many types of data and for displays in various formats. User easily extends basic software library. Hardware and software interfaces to subsystems provided by user designed for flexibility in configuration to meet user's requirements.

Glover, Richard D.↗

Software Innovation in a Mission Critical Environment

Operating in mission-critical environments requires trusted solutions, and the preference for "tried and true" approaches presents a potential barrier to infusing innovation into mission-critical systems. This presentation explores opportunities to overcome this barrier in the software domain. It outlines specific areas of innovation in software development achieved by the Johnson Space Center (JSC) Engineering Directorate in support of NASA's major human spaceflight programs, including International Space Station, Multi-Purpose Crew Vehicle (Orion), and Commercial Crew Programs. Software engineering teams at JSC work with hardware developers, mission planners, and system operators to integrate flight vehicles, habitats, robotics, and other spacecraft elements for genuinely mission critical applications. The innovations described, including the use of NASA Core Flight Software and its associated software tool chain, can lead to software that is more affordable, more reliable, better modelled, more flexible, more easily maintained, better tested, and enabling of automation.

Fredrickson, Steven↗

RELAP-7 Numerical Stabilization: Entropy Viscosity Method

The RELAP-7 code is the next generation nuclear reactor system safety analysis code being developed at the Idaho National Laboratory (INL). The code is based on the INL's modern scientific software development framework, MOOSE (Multi-Physics Object Oriented Simulation Environment). The overall design goal of RELAP-7 is to take advantage of the previous thirty years of advancements in computer architecture, software design, numerical integration methods, and physical models. The end result will be a reactor systems analysis capability that retains and improves upon RELAP5's capability and extends the analysis capability for all reactor system simulation scenarios. RELAP-7 utilizes a single phase and a novel seven-equation two-phase flow models as described in the RELAP-7 Theory Manual (INL/EXT-14-31366). The basic equation systems are hyperbolic, which generally require some type of stabilization (or artificial viscosity) to capture nonlinear discontinuities and to suppress advection-caused oscillations. This report documents one of the available options for this stabilization in RELAP-7 -- a new and novel approach known as the entropy viscosity method. Because the code is an ongoing development effort in which the physical sub models, numerics, and coding are evolving, so too must the specific details of the entropy viscosity stabilization method. Here the fundamentals of the method in their current state are presented.

42 ENGINEERING↗

Lessons learned in deploying software estimation technology and tools

Developing a software product involves estimating various project parameters. This is typically done in the planning stages of the project when there is much uncertainty and very little information. Coming up with accurate estimates of effort, cost, schedule, and reliability is a critical problem faced by all software project managers. The use of estimation models and commercially available tools in conjunction with the best bottom-up estimates of software-development experts enhances the ability of a product development group to derive reasonable estimates of important project parameters. This paper describes the experience of the IBM Software Solutions (SWS) Toronto Laboratory in selecting software estimation models and tools and deploying their use to the laboratory's product development groups. It introduces the SLIM and COSTAR products, the software estimation tools selected for deployment to the product areas, and discusses the rationale for their selection. The paper also describes the mechanisms used for technology injection and tool deployment, and concludes with a discussion of important lessons learned in the technology and tool insertion process.

Panlilio-Yap, Nikki↗

An Object-Oriented Approach to Writing Computational Electromagnetics Codes

Presently, most computer software development in the Computational Electromagnetics (CEM) community employs the structured programming paradigm, particularly using the Fortran language. Other segments of the software community began switching to an Object-Oriented Programming (OOP) paradigm in recent years to help ease design and development of highly complex codes. This paper examines design of a time-domain numerical analysis CEM code using the OOP paradigm, comparing OOP code and structured programming code in terms of software maintenance, portability, flexibility, and speed.

Zimmerman, Martin↗

Combustion Research I.1 Sprays, Flow, Heat Transfer and Turbulent Mixing

LANL is working with the Partnership for Advance Combustion Engines (PACE) a DOE sponsored consortium of national laboratories for the research and development for creating smarter engine design tools for sustainable transportation. Much of that effort is focused on heat, mass and momentum transfer within and engine. LANL’s focus in 2019, in particular under PACE has been spray modeling and engine mixture formulation, development of conjugate heat transfer analysis (heat transfer to the environment surrounding the combustion chamber). Our efforts relay on the Fast, Easy, Accurate and Robust Continuum Engineering (FEARCE) software developed at LANL as the next generation of engine modeling software for turbulent reactive and multiphase flow, a 2019 R&D 100 winner. This work is relevant to the DOE Vehicle Technologies Office efforts at addressing national energy security as well. Less dependence on petroleum products leads to greater energy security. By Environmental Protection Agency standards, some vehicles are now reaching 42–50 mpg mark. These are conventional gasoline engines. With continued investment and research into new technical innovations, the potential exists to save more than 4 million barrels of oil per day or approximately $200 to $400 million per day. This would be a significant decrease in emissions and use of petroleum and a very large stimulus to the U.S. economy. Better understanding of fuel injection and fuel–air mixing, thermodynamic combustion losses, and combustion/emission formation processes enhances our ability to minimize fuel use and unwanted emissions. Helping to accomplish this understanding, the FEARCE modeling program is working to provide state-of-theart capability for accurately simulating combustion processes: to have a predictive methodology in a software helping industry and researchers not only meet national goals on fuel usage and emissions, but global goals. In addition, a predictive, robust, and accurate capability for simulating the engine combustion process helps to minimize time and labor for development of new engine technology.

33 ADVANCED PROPULSION SYSTEMS↗

SU-D-BRD-05: Online Framework for Plan Tracking and Automatic Checks in Radiation Therapy

Purpose: To develop an online framework that tracks a patient’s plan from initial simulation to treatment and that helps automate elements of the physics plan checks usually performed in the record and verify (RV) system and treatment planning system. Methods: We have developed PlanTracker, an online plan tracking system that automatically imports new patients tasks and follows it through treatment planning, physics checks, therapy check, and chart rounds. A survey was designed to collect information about the amount of time spent by medical physicists in non-physics related tasks. We then assessed these non-physics tasks for automation. Using these surveys, we directed our PlanTracker software development towards the automation of intra-plan physics review. We then conducted a systematic evaluation of PlanTracker’s accuracy by generating test plans in the RV system software designed to mimic real plans, in order to test its efficacy in catching errors both real and theoretical. Results: PlanTracker has proven to be an effective improvement to the clinical workflow in a radiotherapy clinic. We present data indicating that roughly 1/3 of the physics plan check can be automated, and the workflow optimized, and show the functionality of PlanTracker. When the full system is in clinical use we will present data on improvement of time use in comparison to survey data prior to PlanTracker implementation. Conclusion: We have developed a framework for plan tracking and automatic checks in radiation therapy. We anticipate using PlanTracker as a basis for further development in clinical/research software. We hope that by eliminating the most simple and time consuming checks, medical physicists may be able to spend their time on plan quality and other physics tasks rather than in arithmetic and logic checks. We see this development as part of a broader initiative to advance the clinical/research informatics infrastructure surrounding the radiotherapy clinic. This research project has been financially supported by Varian Medical Systems, Palo Alto, CA, through a Varian MRA.

60 APPLIED LIFE SCIENCES↗

RELAP-7 Closure Correlations

The RELAP-7 code is the next generation nuclear reactor system safety analysis code being developed at the Idaho National Laboratory (INL). The code is based on the INL’s modern scientific software development framework, MOOSE (Multi-Physics Object Oriented Simulation Environment). The overall design goal of RELAP-7 is to take advantage of the previous thirty years of advancements in computer architecture, software design, numerical integration methods, and physical models. The end result will be a reactor systems analysis capability that retains and improves upon RELAP5’s and TRACE’s capabilities and extends their analysis capabilities for all reactor system simulation scenarios. The RELAP-7 code utilizes the well-posed 7-equation two-phase flow model for compressible two-phase flow. Closure models used in the TRACE code has been reviewed and selected to reflect the progress made during the past decades and provide a basis for the colure correlations implemented in the RELAP-7 code. This document provides a summary on the closure correlations that are currently implemented in the RELAP-7 code. The closure correlations include sub-grid models that describe interactions between the fluids and the flow channel, and interactions between the two phases.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗