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

New Challenges in Model Checking

In the last 25 years, the notion of performing software verification with logic model checking techniques has evolved from intellectual curiosity to accepted technology with significant potential for broad practical application. In this paper we look back at the main steps in this evolution and illustrate how the challenges have changed over the years, as we sharpened our theories and tools. Next we discuss a typical challenge in software verification that we face today - and that perhaps we can look back on in another 25 years as having inspired the next logical step towards a broader integration of model checking into the software development process.

software verification↗

Region templates: Data representation and management for high-throughput image analysis

Compartment fires exhibit unique features associated with smoke accumulation and restricted air ventilation. The objective of the present study is to evaluate the ability of CFD-based fire models to simulate these features and in particular the effects of flame extinction that results from under-ventilated fire conditions. The study is performed using FireFOAM; FireFOAM is an advanced fire modeling software developed by FM Global and is based on a general-purpose open-source software called OpenFOAM. A new flame extinction model based on the concept of a critical value of the flame Damköhler number is incorporated into FireFOAM. The performance of the extinction model is evaluated via comparisons with a previously developed experimental database corresponding to a reduced-scale, heptane-fueled, compartment fire configuration. The numerical simulations also include a description of fuel evaporation driven by the computed gas-to-liquid heat feedback. Comparisons between experimental data and numerical results provide a suitable test bed to evaluate the ability of CFD-based fire models to describe the transition from over- to under-ventilated fire conditions, as well as the transition from extinction-free conditions to conditions in which the flame experiences partial or total quenching.

Energy & Fuels↗

Evolving impact of Ada on a production software environment

Many aspects of software development with Ada have evolved as our Ada development environment has matured and personnel have become more experienced in the use of Ada. The Software Engineering Laboratory (SEL) has seen differences in the areas of cost, reliability, reuse, size, and use of Ada features. A first Ada project can be expected to cost about 30 percent more than an equivalent FORTRAN project. However, the SEL has observed significant improvements over time as a development environment progresses to second and third uses of Ada. The reliability of Ada projects is initially similar to what is expected in a mature FORTRAN environment. However, with time, one can expect to gain improvements as experience with the language increases. Reuse is one of the most promising aspects of Ada. The proportion of reusable Ada software on our Ada projects exceeds the proportion of reusable FORTRAN software on our FORTRAN projects. This result was noted fairly early in our Ada projects, and experience shows an increasing trend over time.

Mcgarry, F.↗

Analysis and Recommendation of Alpha-Beta Continuous Air Monitor Alarm Setpoints for the RPL Stack Exhaust

The Radiochemical Processing Laboratory (RPL) alpha-beta continuous air monitor (CAM) is used for real-time detection of “artificial” alpha-beta particulates from the stack exhaust. The CAM interfaces with software developed by the Pacific Northwest National Laboratory—called the “PNNL OS3300 Alpha-Beta Monitoring Software”—that provides real-time estimates of alpha-beta air concentrations and integrated activities that are calculated from measured CAM counts. The OS3300 software has alarm setpoints that can be used to provide an early indication of larger releases, that if allowed to persist, could approach defined dose limits. This report performs a detailed review of historical and current alarm setpoints used at RPL, including discussion of the technical basis used in their development, analysis of alarm frequencies using measured historical data, and performs a detailed dose assessment using more realistic release scenarios, meteorology, and adjustment factors used in estimating released stack activity. Based on the results, the alpha and beta air concentration alarm setpoints will remain 1.77 × 10 -8 µCi/ml and 3.47 × 10 -8 µCi/ml, respectively; and the alpha and beta integrated activity alarm setpoints will remain 70.22 µCi and 137.63 µCi, respectively. These setpoints achieve the right operational balance in identifying larger releases from planned radiological work at RPL, without being overly conservative so as to cause nuisance alarming. Furthermore, implied doses associated with these setpoints are below defined and regulatory limits.

325RPL↗

LK Scripting Language [SWR-16-07]

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↗

Streaming Analytics Machine (SAM) v. 0.0.1

This is software developed in the course of my dissertation work, which was funded by Sandia. The software includes a library (the Streaming Analytics Machine or SAM) for expressing machine learning and subgraph matching over streaming data sources. It also includes a utility that will convert from a high-level language, the Streaming Analytics Language (SAL) to SAM. SAND2019-4322 M

Goodman, Eric↗

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↗