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 775 records · Page 43

SU-E-T-212: Influence of the Modulation Index On Daily Quality Assurance in Rapid Arc Treatments

Purpose: At our Institute some measured parameters for daily quality assurance (DQA) of dynamic arc therapy plans showed an unexpected behavior, therefore an investigation of the influence of the magnitude of modulation was conducted. Methods: In our clinical practice all DQAs of dynamic arc therapy plans are measured and analyzed prior to treatments using commercial software. For this study these plans were additionally exported to our in-house software written in MATLAB.The developed software extracted the leaf position, gantry angle, cumulative meterset weight of each control point (CP) and the total number of Monitor Units (MU) of each arc. Based on this information we calculated the leaf travel distance, irradiated segment area, number of MUs and dose rate for each CP. These data allowed us to calculate the modulation indexes (MI) of the plans, applying five different definitions of MI. The results were then correlated to the results of our DQA measurements.To validate the software, additional plans of known MIs were created and analyzed. For confirmation, the calculated parameters were compared to the segmented treatment table (STT) coming from the treatment planning system. Results: All calculated CP-parameters matched the STT by 99% or better. For linac 1, the comparison of the MI evaluation and the DQA results showed a slight tendency: 91.3% failed DQA plans had a MI lower than the average value. For this definition we consider that the lower the MI the higher the modulation. The results of the linac 2 present no significant relevance due to the low sample sizes for each DQA software. Conclusion: Available data and given definitions of the modulation index do not bring conclusive results; one cannot find a clear and distinct correlation with the failure of the DQA. The ongoing analysis with an increased sample size might lead to another conclusion.

07 ISOTOPE AND RADIATION SOURCES↗

MO-FG-303-04: A Smartphone Application for Automated Mechanical Quality Assurance of Medical Accelerators

Purpose: The mechanical quality assurance (QA) of medical accelerators consists of a time consuming series of procedures. Since most of the procedures are done manually – e.g., checking gantry rotation angle with the naked eye using a level attached to the gantry –, it is considered to be a process with high potential for human errors. To remove the possibilities of human errors and reduce the procedure duration, we developed a smartphone application for automated mechanical QA. Methods: The preparation for the automated process was done by attaching a smartphone to the gantry facing upward. For the assessments of gantry and collimator angle indications, motion sensors (gyroscope, accelerator, and magnetic field sensor) embedded in the smartphone were used. For the assessments of jaw position indicator, cross-hair centering, and optical distance indicator (ODI), an optical-image processing module using a picture taken by the high-resolution camera embedded in the smartphone was implemented. The application was developed with the Android software development kit (SDK) and OpenCV library. Results: The system accuracies in terms of angle detection error and length detection error were < 0.1° and < 1 mm, respectively. The mean absolute error for gantry and collimator rotation angles were 0.03° and 0.041°, respectively. The mean absolute error for the measured light field size was 0.067 cm. Conclusion: The automated system we developed can be used for the mechanical QA of medical accelerators with proven accuracy. For more convenient use of this application, the wireless communication module is under development. This system has a strong potential for the automation of the other QA procedures such as light/radiation field coincidence and couch translation/rotations.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

Los Alamos National Security, LLC Request for Information on how industry may partner with the Laboratory on KIVA software.

KIVA is a family of Fortran-based computational fluid dynamics software developed by LANL. The software predicts complex fuel and air flows as well as ignition, combustion, and pollutant-formation processes in engines. The KIVA models have been used to understand combustion chemistry processes, such as auto-ignition of fuels, and to optimize diesel engines for high efficiency and low emissions. Fuel economy is heavily dependent upon engine efficiency, which in turn depends to a large degree on how fuel is burned within the cylinders of the engine. Higher in-cylinder pressures and temperatures lead to increased fuel economy, but they also create more difficulty in controlling the combustion process. Poorly controlled and incomplete combustion can cause higher levels of emissions and lower engine efficiencies.

33 ADVANCED PROPULSION SYSTEMS↗

Status of the phenomena representation, 3D modeling, and cloud-based software architecture development

Early in 2013, researchers at the Idaho National Laboratory outlined a technical framework to support the implementation of state-of-the-art probabilistic risk assessment to predict the safety performance of advanced small modular reactors. From that vision of the advanced framework for risk analysis, specific tasks have been underway in order to implement the framework. This report discusses the current development of a several tasks related to the framework implementation, including a discussion of a 3D physics engine that represents the motion of objects (including collision and debris modeling), cloud-based analysis tools such as a Bayesian-inference engine, and scenario simulations. These tasks were performed during 2015 as part of the technical work associated with the Advanced Reactor Technologies Program.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Alternatives for jet engine control

Tensor model order reduction, recursive tensor model identification, input design for tensor model identification, software development for nonlinear feedback control laws based upon tensors, and development of the CATNAP software package for tensor modeling, identification and simulation were studied. The last of these are discussed.

Sain, M. K.↗

Development of software fault-tolerance techniques

As computers become more widely used, and in particular as they become used in more safety critical applications, the reliability of the computer system and its software becomes more important. There is also an increasing need for high levels of reliability in applications involving very large numbers of inexpensive units where recall of the units would be disproportionately expensive. The nature of faults and the assumptions made by different approaches to correct operation are considered. The recovery block approach is described and a probabilistic analysis of its effectiveness, with and without correlated design errors is provided. Mechanisms for generating acceptance tests from specifications, and for providing recovery in the presence of asynchrony, are described. An analysis of, and design for, the provision of recovery blocks in the microprogram of the Bendix BDX930 processor is provided. An example of the use of recovery blocks in a simple operating system is also provided.

Melliar-Smith, P. M.↗

Space station data system analysis/architecture study. Task 2: Options development, DR-5. Volume 3: Programmatic options

Task 2 in the Space Station Data System (SSDS) Analysis/Architecture Study is the development of an information base that will support the conduct of trade studies and provide sufficient data to make design/programmatic decisions. This volume identifies the preferred options in the programmatic category and characterizes these options with respect to performance attributes, constraints, costs, and risks. The programmatic category includes methods used to administrate/manage the development, operation and maintenance of the SSDS. The specific areas discussed include standardization/commonality; systems management; and systems development, including hardware procurement, software development and system integration, test and verification.

Source record↗

Improving a data-acquisition software system with abstract data type components

Abstract data types and object-oriented design are active research areas in computer science and software engineering. Much of the interest is aimed at new software development. Abstract data type packages developed for a discontinued software project were used to improve a real-time data-acquisition system under maintenance. The result saved effort and contributed to a significant improvement in the performance, maintainability, and reliability of the Goldstone Solar System Radar Data Acquisition System.

Howard, S. D.↗

GCS programmer's manual

A variety of instructions to be used in the development of implementations of software for the Guidance and Control Software (GCS) project is described. This document fulfills the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, 'Software Considerations in Airborne Systems and Equipment Certification' requirements for document No. 4, which specifies the information necessary for understanding and programming the host computer, and document No. 12, which specifies the software design and implementation standards that are applicable to the software development and testing process. Information on the following subjects is contained: activity recording, communication protocol, coding standards, change management, error handling, design standards, problem reporting, module testing logs, documentation formats, accuracy requirements, and programmer responsibilities.

Lowman, Douglas S.↗

Risk management and expert system development methodology

A risk-based expert-system development methodology has been developed to provide guidance to managers and technical personnel and to serve as a standard for developing expert systems. Expert-system development differs from conventional software development in that the information needed to prepare system requirements for expert systems is not known at the outset of a project and is obtained by knowledge engineering methods. The paper describes the expert-system life cycle, development methodology, and the approach taken in this methodology to manage and reduce the risks in expert system development. Also examined are the risks of using and of not using a methodology, the studies undertaken to validate the provisions of the expert system development methodology, and the results of these validation studies.

Hull, Larry↗

Guide to object-oriented analysis and design

The purpose of this guide is to provide Marshall Space Flight Center personnel with guidelines for the use of object-oriented analysis and design and to describe how it can be accomplished within the framework of existing development directives, including the Software Development Plan. It is not intended as a detailed tutorial. The reader is referred to the Coad and Yourdon texts in the References.

Harrison, Harry C.↗

Selection of behavioral tasks and development of software for evaluation of rhesus monkey behavior during spaceflight

The results of several experiments were disseminated professionally during this semiannual period. These peer-reviewed papers that were accepted for publication represent the growth of our research areas, as follow-up experiments to previously published work in cognition and enrichment have been completed and are being published. The presentations not only reflect the latest interesting results that we have obtained, but also serve as a testament to the intense interest that is being expressed for our test system and findings.

Rumbaugh, Duane M.↗

Software packager user's guide

Software integration is a growing area of concern for many programmers and software managers because the need to build new programs quickly from existing components is greater than ever. This includes building versions of software products for multiple hardware platforms and operating systems, building programs from components written in different languages, and building systems from components that must execute on different machines in a distributed network. The goal of software integration is to make building new programs from existing components more seamless -- programmers should pay minimal attention to the underlying configuration issues involved. Libraries of reusable components and classes are important tools but only partial solutions to software development problems. Even though software components may have compatible interfaces, there may be other reasons, such as differences between execution environments, why they cannot be integrated. Often, components must be adapted or reimplemented to fit into another application because of implementation differences -- they are implemented in different programming languages, dependent on different operating system resources, or must execute on different physical machines. The software packager is a tool that allows programmers to deal with interfaces between software components and ignore complex integration details. The packager takes modular descriptions of the structure of a software system written in the package specification language and produces an integration program in the form of a makefile. If complex integration tools are needed to integrate a set of components, such as remote procedure call stubs, their use is implied by the packager automatically and stub generation tools are invoked in the corresponding makefile. The programmer deals only with the components themselves and not the details of how to build the system on any given platform.

Callahan, John R.↗

Expert system for scheduling simulation lab sessions

Implementation and results of an expert system used for scheduling session requests for the Systems Engineering Simulator (SES) laboratory at the NASA Johnson Space Center (JSC) are discussed. Weekly session requests are received from astronaut crew trainers, procedures developers, engineering assessment personnel, software developers, and various others who wish to access the computers, scene generators, and other simulation equipment available to them in the SES lab. The expert system under discussion is comprised of a data acquisition portion - two Pascal programs run on a personal computer - and a CLIPS program installed on a minicomputer. A brief introduction to the SES lab and its scheduling background is given. A general overview of the system is provided, followed by a detailed description of the constraint-reduction process and of the scheduler itself. Results from a ten-week trial period using this approach are discussed. Finally, a summary of the expert system's strengths and shortcomings are provided.

Lund, Chet↗