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,423 records · Page 79

Data Management System (DMS) testbed user's manual development, volumes 1 and 2

A critical review of the network communication services contained in the Tinman User's Manual for Data Management System Test Bed (Tinman DMS User's Manual) is presented. The review is from the perspective of applying modern software engineering principles and using the Ada language effectively to ensure the test bed network communication services provide a robust capability. Overall the material on network communication services reflects a reasonably good grasp of the Ada language. Language features are appropriately used for most services. Design alternatives are offered to provide improved system performance and a basis for better application software development. Section two contains a review and suggests clarifications of the Statement of Policies and Services contained in Appendix B of the Tinman DMS User's Manual. Section three contains a review of the Network Communication Services and section four contains concluding comments.

Mcbride, John G.↗

Faster Aerodynamic Simulation With Cart3D

A NASA-developed aerodynamic simulation tool is ensuring the safety of future space operations while providing designers and engineers with an automated, highly accurate computer simulation suite. Cart3D, co-winner of NASA's 2002 Software of the Year award, is the result of over 10 years of research and software development conducted by Michael Aftosmis and Dr. John Melton of Ames Research Center and Professor Marsha Berger of the Courant Institute at New York University. Cart3D offers a revolutionary approach to computational fluid dynamics (CFD), the computer simulation of how fluids and gases flow around an object of a particular design. By fusing technological advancements in diverse fields such as mineralogy, computer graphics, computational geometry, and fluid dynamics, the software provides a new industrial geometry processing and fluid analysis capability with unsurpassed automation and efficiency.

Source record↗

Reconstruction of interactions in the ProtoDUNE-SP detector with Pandora

The Pandora Software Development Kit and algorithm libraries provide pattern-recognition logic essential to the reconstruction of particle interactions in liquid argon time projection chamber detectors. Pandora is the primary event reconstruction software used at ProtoDUNE-SP, a prototype for the Deep Underground Neutrino Experiment far detector. ProtoDUNE-SP, located at CERN, is exposed to a charged-particle test beam. This paper gives an overview of the Pandora reconstruction algorithms and how they have been tailored for use at ProtoDUNE-SP. In complex events with numerous cosmic-ray and beam background particles, the simulated reconstruction and identification efficiency for triggered test-beam particles is above 80% for the majority of particle type and beam momentum combinations. Specifically, simulated 1 GeV/c charged pions and protons are correctly reconstructed and identified with efficiencies of 86.1$\pm 0.6$% and 84.1$\pm 0.6$%, respectively. The efficiencies measured for test-beam data are shown to be within 5% of those predicted by the simulation.

43 PARTICLE ACCELERATORS↗

High-Performance Design Patterns for Modern Fortran

This paper presents ideas for using coordinate-free numerics in modern Fortran to achieve code flexibility in the partial differential equation (PDE) domain. We also show how Fortran, over the last few decades, has changed to become a language well-suited for state-of-the-art software development. Fortran’s new coarray distributed data structure, the language’s class mechanism, and its side-effect-free, pure procedure capability provide the scaffolding on which we implement HPC software. These features empower compilers to organize parallel computations with efficient communication. We present some programming patterns that support asynchronous evaluation of expressions comprised of parallel operations on distributed data. We implemented these patterns using coarrays and the message passing interface (MPI). We compared the codes’ complexity and performance. The MPI code is much more complex and depends on external libraries. The MPI code on Cray hardware using the Cray compiler is 1.5–2 times faster than the coarray code on the same hardware. The Intel compiler implements coarrays atop Intel’s MPI library with the result apparently being 2–2.5 times slower than manually coded MPI despite exhibiting nearly linear scaling efficiency. As compilers mature and further improvements to coarrays comes in Fortran 2015, we expect this performance gap to narrow.

Haveraaen, Magne↗

Displacement driven balancing of a diamond turning machine flycutter

The spindle balancing operation is critical to the performance of precision lathes and should be conducted anytime the configuration of the spindle or its tooling is modified such that an unbalanced condition may occur. Within the machine tool community, accelerometers are typically used as the feedback device during the balancing operation. At Lawrence Livermore National Laboratory (LLNL), we have nearly 40 years of history using displacement sensors, such as capacitance gauges, in place of accelerometers when balancing precision spindles. The process of balancing a precision machine spindle using displacement sensors is presented in the context of two work examples. In this case, the details of the one-dimensional balancing operation performed after replacing a flycutter on the spindles of two unique large optic diamond turning machines is discussed. The pros and cons of accelerometer driven balancing and displacement driven balancing are also presented. In the accelerometer context, the level of balance achieved for our work example is less than 100 micro-g or a total indicator reading (TIR) of 1.6 µm. The process of balancing has been enhanced over the years as advances have been made in software, data acquisition systems, and instrumentation. The balancing system is described including details about instrumentation, set-up, how phase and spindle structure stiffness is calculated, and how the LLNL developed software that guides the user through the process by suggesting corrective action.

42 ENGINEERING↗

Phobos lander coding system: Software and analysis

The software developed for the decoding system used in the telemetry link of the Phobos Lander mission is described. Encoders and decoders are provided to cover the three possible telemetry configurations. The software can be used to decode actual data or to simulate the performance of the telemetry system. The theoretical properties of the codes chosen for this mission are analyzed and discussed.

Cheung, K.-M.↗

The interactive digital video interface

A frequent complaint in the computer oriented trade journals is that current hardware technology is progressing so quickly that software developers cannot keep up. A example of this phenomenon can be seen in the field of microcomputer graphics. To exploit the advantages of new mechanisms of information storage and retrieval, new approaches must be made towards incorporating existing programs as well as developing entirely new applications. A particular area of need is the correlation of discrete image elements to textural information. The interactive digital video (IDV) interface embodies a new concept in software design which addresses these needs. The IDV interface is a patented device and language independent process for identifying image features on a digital video display and which allows a number of different processes to be keyed to that identification. Its capabilities include the correlation of discrete image elements to relevant text information and the correlation of these image features to other images as well as to program control mechanisms. Sophisticated interrelationships can be set up between images, text, and program control mechanisms.

Doyle, Michael D.↗

Autonomous Frequency-Domain System-Identification Program

Autonomous Frequency Domain Identification (AU-FREDI) computer program implements system of methods, algorithms, and software developed for identification of parameters of mathematical models of dynamics of flexible structures and characterization, by use of system transfer functions, of such models, dynamics, and structures regarded as systems. Software considered collection of routines modified and reassembled to suit system-identification and control experiments on large flexible structures.

Yam, Yeung↗

DADiSP processing guide

A guide for DADiSP software, intended for use by the Lambda Point Experiment (LPE) Team during and after the United States Microgravity Payload (USMP)-1 mission, is presented. DADiSP is a Data Analysis and Display Software developed and marketed by DSP Development Corporation, Cambridge, Massachusetts. This guide is intended to be used in addition to the DADiSP Worksheet User Manual and Reference Manual which are supplied by the company with the software. Technical support for DADiSP is available from DSP at (617) 577-1133. Access to DADiSP on Acceleration Characterization and Analysis Project (ACAP) EGSE is being provided to the LPE team during USMP-1 for off-line processing of SAMS data.

Rogers, Melissa J. B.↗

Flight Dynamics Mission Support and Quality Assurance Process

This paper summarizes the method of the Computer Sciences Corporation Flight Dynamics Operation (FDO) quality assurance approach to support the National Aeronautics and Space Administration Goddard Space Flight Center Flight Dynamics Support Branch. Historically, a strong need has existed for developing systematic quality assurance using methods that account for the unique nature and environment of satellite Flight Dynamics mission support. Over the past few years FDO has developed and implemented proactive quality assurance processes applied to each of the six phases of the Flight Dynamics mission support life cycle: systems and operations concept, system requirements and specifications, software development support, operations planing and training, launch support, and on-orbit mission operations. Rather than performing quality assurance as a final step after work is completed, quality assurance has been built in as work progresses in the form of process assurance. Process assurance activities occur throughout the Flight Dynamics mission support life cycle. The FDO Product Assurance Office developed process checklists for prephase process reviews, mission team orientations, in-progress reviews, and end-of-phase audits. This paper will outline the evolving history of FDO quality assurance approaches, discuss the tailoring of Computer Science Corporations's process assurance cycle procedures, describe some of the quality assurance approaches that have been or are being developed, and present some of the successful results.

Oh, InHwan↗

Comparison of the NASCAP/GEO, POLAR, SEE Charging Handbook, and NASCAP-2K.1 Spacecraft Charging Codes

The NASA Charging Analyzer Program (NASCAP) spacecraft charging software developed by Maxwell Technologies has been widely used for the past fifteen to twenty years in satellite design and investigation of spacecraft charging related anomalies. Individual versions of the NASCAP software are available for use in low inclination, low Earth orbit environments (NASCAP[LEO) and geostationary orbit environments (NASCAP/GEO). In addition, the Potentials of Large objects in the Auroral Region (POLAR) code is available for use in LEO polar orbit environments. NASCAP/GEO and POLAR were both written in the 1980's using algorithms appropriate for the computers of the time. They solve the Poisson-Vlasov system for currents and densities assuming limited speed and memory of computer systems standard for the day. In addition, use of the charging models requires individual input files that are not readily transported into the various codes to facilitate comparison of results by the user.

Neergaard, Linda E.↗

From Shuttle Main Engine to the Human Heart: A Presentation to the Federal Lab Consortium for Technology Transfer

A NASA engineer received a heart transplant performed by Drs. DeBakey and Noon after suffering a serious heart attack. 6 months later that engineer returned to work at NASA determined to use space technology to help people with heart disease. A relationship between NASA and Drs. DeBakey and Noon was formed and the group worked to develop a low cost, low power implantable ventricular assist device (VAD). NASA patented the method to reduce pumping damage to red blood cells and the design of a continuous flow heart pump (#5,678,306 and #5,947,892). The technology and methodology were licensed exclusively to MicroMed Technology, Inc.. In late 1998 MicroMed received international quality and electronic certifications and began clinical trials in Europe. Ventricular assist devices were developed to bridge the gap between heart failure and transplant. Early devices were cumbersome, damaged red blood cells, and increased the risk of developing dangerous blood clots. Application emerged from NASA turbopump technology and computational fluid dynamics analysis capabilities. To develop the high performance required of the Space Shuttle main engines, NASA pushed the state of the art in the technology of turbopump design. NASA supercomputers and computational fluid dynamics software developed for use in the modeling analysis of fuel and oxidizer flow through rocket engines was used in the miniaturization and optimization of a very small heart pump. Approximately 5 million people worldwide suffer from chronic heart failure at a cost of 40 billion dollars In the US, more than 5000 people are on the transplant list and less than 3000 transplants are performed each year due to the lack of donors. The success of ventricular assist devices has led to an application as a therapeutic destination as well as a bridge to transplant. This success has been attributed to smaller size, improved efficiency, and reduced complications such as the formation of blood clots and infection.

Fogarty, Jennifer A.↗

Mechanistic source terms for the XE-100 reactor XSTERM Code Development Approach - 18587

X-Energy is developing the Xe-100 pebble bed modular High Temperature Gas Reactor (HTGR) as an advanced nuclear power source. To achieve its safety objectives, the Xe-100 reactor relies on materials inherent characteristics and passive safety features. Key features include the inherent high temperature characteristics of TRISO-coated fuel particles, graphite moderator, and helium coolant, along with passive heat removal capability of a low-power-density core. This paper will describe the approach adopted by X-Energy to develop and validate mechanistic source terms for the Xe-100. The Mechanistic Source Term (MST) approach for the Xe-100 reactor will build upon that of the prior DOE Next Generation Nuclear Program (NGNP) (Refs. 1, 2, 3 and 4). MST development is closely related to Fuel Qualification (FQ), Licensing Basis Event (LBE) selection and Probabilistic Risk Assessment (PRA). This paper provides a brief overview of the MST road map process. Software plays a crucial role in establishing and quantifying MSTs required for licensing the Xe-100. An insight into X-Energy s comprehensive, integrated software development program for calculating time-dependent radionuclide releases from the Xe-100 over a wide range of events is provided. (authors)

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

Disposal Systems Evaluations and Tool Development - Engineered Barrier System Evaluation (Work Package LL1015080425)

The Disposal Systems Evaluation Framework (DSEF) will use a logical process for developing one or more disposal system concepts (also referred to as repository system in this report) for any given waste form and geologic setting combination. In the Features, Events, and Processes (FEPs) group of work packages, there are seven categories of waste forms and eight categories of geologic setting being studied. The DSEF will also establish a Used Fuel Disposition Campaign (UFDC) knowledge management system to organize high-level information, data, and assumptions, thereby facilitating consistency in high-level system simulation and economic analyses. This system likely will be housed with the INL-based documentation system. Attention is given to lessons oearned from the systems used at the Waste Isolation Pilot Plant (WIPP) and the Yucca Mountain Project (YMP). Where reference material from other programs (e.g., international) is used or cited, the knowledge-management system imports the reference material directly or refer to it in bibliography form. Alternative data sets (e.g., from other programs) will also be utilized to evaluate their influence on DSEF analyses for given waste form and disposal-system combinations. The knowledge-management system can also be used to maintain the results of DSEF realizations, enabling the comparison and ranking of various waste-form/disposal-system-environment/disposal-system-design options. Finally, the UFDC knowledge-management system will be able to provide a compendium of 'templates' that can be utilized, in a labor-efficient fashion, to build parallel DSEF analyses (e.g., 'one offs'). The DSEF will not be a stand-alone, push-the-button and wait for the results, item of software. it will use osftware (probably EXCEL, initially), to guide the team members through a logical process of evaluating combinations of waste-form, disposal-syste-environment, and disposal-system design. In later stages, it will utilize software developed in the field of knowledge engineering and knowledge-management systems (Umeki et al. 2009). At certain points in the logical process, the DSEF software will point the evaluate to other software tools to do analyses needed to move the process forward. In the development of the DSEF, they will be mindful to make it no more complex than necessary to evaluate the system being considered. The DSEF will organize and document the work such that multiple realizations for different combinations can be compared and contrasted.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

A Python Library for Radiance Matrix-based Simulation Control and EnergyPlus Integration

Radiance matrix-based methods enable efficient parametric simulations, allowing users to vary sky conditions, fenestration systems, and other model parameters at a minimal cost to computation. However, the steep learning curve and complex workflow hinder the widespread adoption of matrix-based methods. The frads Python library with a series of command-line tools was developed to automate the entire matrix-based simulation process, lowering entry barriers and reducing human error. Co-simulation between EnergyPlus and Radiance was also enabled using the Python library from EnergyPlus. Key Innovations • Command-line based automation of Radiance matrix-based simulation methods • Python library facilitates broader adoption of Radiance matrix-based simulation methods • Radiance EnergyPlus run-time integration enabling the modeling of advanced control systems Practical Implications The frads library, with associated command-line tools, provides practitioners with the capability to easily adopt and use Radiance matrix-based simulation methods for various daylighting, solar control, and energy-related evaluations. Frads' current form is designed for 1) users familiar with a command-line interface and 2) software developers to integrate the matrix-based methods into existing software packages.

Wang, Taoning↗

WE-G-9A-01: Radiation Oncology Outcomes Informatics

The construction of databases and support software to enable routine and systematic aggregation, analysis and reporting of patient outcomes data is emerging as an important area. “How have results for our patients been affected by the improvements we have made in our practice and in the technologies we use?” To answer this type of fundamental question about the overall pattern of efficacy observed, it is necessary to systematically gather and analyze data on all patients treated within a clinic. Clinical trials answer, in great depth and detail, questions about outcomes for the subsets of patients enrolled in a given trial. However, routine aggregation and analysis of key treatment parameter data and outcomes information for all patients is necessary to recognize emergent patterns that would be of interest from a public health or practice perspective and could better inform design of clinical trials or the evolution of best practice principals. To address these questions, Radiation Oncology outcomes databases need to be constructed to enable combination essential data from a broad group of data types including: diagnosis and staging, dose volume histogram metrics, patient reported outcomes, toxicity metrics, performance status, treatment plan parameters, demographics, DICOM data and demographics. Developing viable solutions to automate aggregation and analysis of this data requires multidisciplinary efforts to define nomenclatures, modify clinical processes and develop software and database tools requires detailed understanding of both clinical and technical issues. This session will cover the developing area of Radiation Oncology Outcomes Informatics. Learning Objectives: Audience will be able to speak to the technical requirements (software, database, web services) which must be considered in designing an outcomes database. Audience will be able to understand the content and the role of patient reported outcomes as compared to traditional toxicity measures. Audience will be understand approaches, clinical process changes, consensus building efforts and standardizations which must be addressed to succeed in a multi-disciplinary effort to aggregate data for all patients. Audience will be able to discuss technical and process issues related to pooling data among institutions in the context of collaborative studies among the presenting institutions.

60 APPLIED LIFE SCIENCES↗

Quality control for community-based sea-ice model development

A new collaborative organization for sea-ice model development, the CICE Consortium, has devised quality control procedures to maintain the integrity of its numerical codes' physical representations, enabling broad participation from the scientific community in the Consortium's open software development environment. Using output from five coupled and uncoupled configurations of the Los Alamos Sea Ice Model, CICE, we formulate quality control methods that exploit common statistical properties of sea-ice thickness, and test for significant changes in model results in a computationally efficient manner. New additions and changes to CICE are graded into four categories, ranging from bit-for-bit amendments to significant, answer-changing upgrades. These modifications are assessed using criteria that account for the high level of autocorrelation in sea-ice time series, along with a quadratic skill metric that searches for hemispheric changes in model answers across an array of different CICE configurations. These metrics also provide objective guidance for assessing new physical representations and code functionality.

58 GEOSCIENCES↗

Engineering Computational Practices (Rev. 1)

This manual will attempt to motivate the use of an automated build system for the purposes of computational science and engineering. As part of this motivation, the surrounding computational practices of version control, documen tation, compute environment management, and regression testing will also be addressed as applied to the practice of computational engineering. Specifically, this manual intends to motivate the adoption of these traditional software engineering practices for use in research and production engineering simulation projects. This manual is not the first such effort in the greater scientific computing community. In fact, the authors relied heavily on the lesson plans of the Software Carpentry, established to teach computing skills to researchers in 1998. As the intention for this manual is to lay out fundamental practices of engineering computing, it will not attempt to fully teach the underlying concepts and will instead reference the well designed lesson plans of the Software Carpentry. Where possible, this manual will explain to general computing practices and concepts and limit discussion of specific software implementations to examples or vehicles for practice in concrete application. The specific software taught by the Software Carpentry curriculum is an excellent starting point to learn the core concepts of computational engi neering. However, the authors have found that applications to engineering simulation and analysis require translation of these software development concepts into the language and workflows of computational engineers. Adopting these computational tools may require engineers to re-imagine their workflows in some combination of traditional engineer ing and software concepts. It has also been necessary to extend existing software build systems for engineering practices beyond the simple wrap ping of engineering software execution. Where necessary, examples of specific software and their method of extension to engineering simulations will be given, with reference to the User Manual for recommended practical use. Where this manual relies on specific implementation examples, it should be understood that the practicing engineer may find that different software is more amenable to their specific work. It is always the overall collection of computational practices is more important than any specific software implementation. The ability to recognize which concepts are implemented by a software package will make a practicing engineer agile to changing project needs, computing resources, numeric solvers, programming languages, and even available funding.

42 ENGINEERING↗