Search NASA⌕ Search

SEARCH · Search NASA

Results for “Processing reliability”

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 145 records · Page 8
All sourcesNASA NTRSDOE OSTI
NASA NTRS2022

Reliability-Aware Requirements Development for Autonomy Software

Autonomy is the ability of a system to make decisions and take actions in the presence of uncertainty. Validating autonomy, therefore, is a matter of validating that the system makes intelligent decisions even when there might be discrepancies between the observed and the expected state of the world as well as when the possible outcome of each of the possible courses of action is uncertain. During the requirements engineering phase, the functions, including those that are required to be autonomous and their expected behavior are specified. However, in the case of autonomous software system, it is challenging to specify all possible scenarios that the software may encounter. Additionally, since autonomous behaviors cannot always be fully predetermined, it is difficult to reason about their completeness and correctness. While these challenges are also faced with non-autonomous system, they are more prevalent for autonomous system due to their complexity and emergent behavior. Our efforts have been three-fold. On one hand, we have developed a goal-based method for requirements decomposition. We have embedded this approach into a higher-level systems engineering framework and then developed methods for decision and reliability analysis within this framework. And finally, we use simulation analysis to validate the more theoretical methods and provide a feedback mechanism. The decision analysis approach (DA) helps in identifying and mitigating the run-time risks, by bringing to the forefront the uncertainties, decisions, interactions, and other factors that may cause autonomous software to make erroneous decisions. The DA framework is used to quantify, for each decision that the software can make, failure risk due to uncertainties. The information about the key decisions and circumstances that can cause autonomous system to make incorrect decisions are used to generate test scenarios to be run in a simulator to ensure that the system can handle error-prone circumstances. The results or outcomes from decisions, based on the simulated scenarios, can then be leveraged to further gain insight of the assured system. We combine a goal-based approach with simulation analysis to facilitate requirements development for autonomous systems and further provide a method for run-time systems level reliability considerations during the autonomous software development process. The DA and the reliability analysis methods provide a formalism for the consideration of uncertainty in the run time decision-making process for autonomous software. This formalism considers the uncertainty involved in the outcome of different courses of action, in terms of performance and cost, as well as a method to consider the system level reliability implications. System level reliability considerations for autonomous software decision making contribute to the satisfaction of the system level goals over the lifecycle of a given mission. We demonstrate our approach using a hypothetical rover path planning example. The requirements for our rover simulator are based on existing literature about Mars rovers and lessons learned from real world observations at JPL. The specifics of the autonomy design for the Mars rovers, that have not been previously cleared for external release, are not used for our demonstrations.

Lindvall, Mikael↗
NASA NTRS2017

Reliably Detectable Flaw Size for NDE Methods that Use Calibration

Probability of detection (POD) analysis is used in assessing reliably detectable flaw size in nondestructive evaluation (NDE). MIL-HDBK-1823 and associated mh1823 POD software gives most common methods of POD analysis. In this paper, POD analysis is applied to an NDE method, such as eddy current testing, where calibration is used. NDE calibration standards have known size artificial flaws such as electro-discharge machined (EDM) notches and flat bottom hole (FBH) reflectors which are used to set instrument sensitivity for detection of real flaws. Real flaws such as cracks and crack-like flaws are desired to be detected using these NDE methods. A reliably detectable crack size is required for safe life analysis of fracture critical parts. Therefore, it is important to correlate signal responses from real flaws with signal responses form artificial flaws used in calibration process to determine reliably detectable flaw size.

Koshti, Ajay M.↗
NASA NTRS2015

Using Classical Reliability Models and Single Event Upset (SEU) Data to Determine Optimum Implementation Schemes for Triple Modular Redundancy (TMR) in SRAM-Based Field Programmable Gate Array (FPGA) Devices

Space applications are complex systems that require intricate trade analyses for optimum implementations. We focus on a subset of the trade process, using classical reliability theory and SEU data, to illustrate appropriate TMR scheme selection.

Field Programmable Gate Array (FPGA)↗
NASA NTRS1981

Use of ceramics in point-focus solar receivers

One of the research and development efforts in the Solar Thermal Energy Systems Project at the Jet Propulsion Laboratory has been focused on application of ceramic components for advanced point-focus solar receivers. The impetus for this effort is a need for high efficiency, low cost solar receivers which operate in a temperature regime where use of metal components is impractical. The current status of the work on evaluation of ceramic components at JPL and elsewhere is outlined and areas where lack of knowledge is currently slowing application of ceramics are discussed. Future developments of ceramic processing technology and reliability assurance methodology should open up applications for the point-focus solar concentrator system in fuels and chemicals production, in thermochemical energy transport and storage, in detoxification of hazardous materials and in high temperature process heat as well as for electric power generation.

Smoak, R. H.↗
NASA NTRS1973

Fabrication of capsule assemblies, phase 3

Thirteen capsule assemblies were fabricated for evaluation of fuel pin design concepts for a fast spectrum lithium cooled compact space power reactor. These instrumented assemblies were designed for real time test of prototype fuel pins. Uranium mononitride fuel pins were encased in AISI 304L stainless steel capsules. Fabrication procedures were fully qualified by process development and assembly qualification tests. Instrumentation reliability was achieved utilizing specially processed and closely controlled thermocouple hot zone fabrication and by thermal screening tests. Overall capsule reliability was achieved with an all electron beam welded assembly.

Keeton, A. R.↗
NASA NTRS2016

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗
NASA NTRS2012

A Systems Modeling Approach for Risk Management of Command File Errors

The main cause of commanding errors is often (but not always) due to procedures. Either lack of maturity in the processes, incompleteness of requirements or lack of compliance to these procedures. Other causes of commanding errors include lack of understanding of system states, inadequate communication, and making hasty changes in standard procedures in response to an unexpected event. In general, it's important to look at the big picture prior to making corrective actions. In the case of errors traced back to procedures, considering the reliability of the process as a metric during its' design may help to reduce risk. This metric is obtained by using data from Nuclear Industry regarding human reliability. A structured method for the collection of anomaly data will help the operator think systematically about the anomaly and facilitate risk management. Formal models can be used for risk based design and risk management. A generic set of models can be customized for a broad range of missions.

probabilistic risk↗
NASA NTRS1975

Power processing for electric propulsion

The potential of achieving up to 30 per cent more spacecraft payload or 50 per cent more useful operating life by the use of electric propulsion in place of conventional cold gas or hydrazine systems in science, communications, and earth applications spacecraft is a compelling reason to consider the inclusion of electric thruster systems in new spacecraft design. The propulsion requirements of such spacecraft dictate a wide range of thruster power levels and operational lifetimes, which must be matched by lightweight, efficient, and reliable thruster power processing systems. This paper will present electron bombardment ion thruster requirements; review the performance characteristics of present power processing systems; discuss design philosophies and alternatives in areas such as inverter type, arc protection, and control methods; and project future performance potentials for meeting goals in the areas of power processor weight (10 kg/kW), efficiency (approaching 92 per cent), reliability (0.96 for 15,000 hr), and thermal control capability (0.3 to 5 AU).

Finke, R. C.↗
NASA NTRS2002

Characterization of 2219 Aluminum Produced by Electron Beam Freeform Fabrication

Researchers at NASA Langley Research Center are developing a new electron beam freeform fabrication (EB F(sup 3)) technique to fabricate metal parts. This process introduces metal wire into a molten pool created by a focused electron beam. Potential aerospace applications for this technology include ground-based fabrication of airframe structures and on-orbit construction and repair of space components and structures. Processing windows for reliably producing high quality 2219 aluminum parts using the EB F(sup 3) technique are being defined. The effects of translation speed, wire feed rate, and beam power on the resulting microstructures and mechanical properties are explored. Tensile properties (ultimate tensile strength, yield strength, and elongation) show little effect over the range of processing conditions tested. Basic processing-microstructure-property correlations are drawn for the EB F(sup 3) process.

Taminger, Karen M. B.↗
NASA NTRS2012

Rolling Bearing Steels - A Technical and Historical Perspective

Starting about 1920 it becomes easier to track the growth of bearing materials technology. Until 1955, with few exceptions, comparatively little progress was made in this area. AISI 52100 and some carburizing grades (AISI 4320, AISI 9310) were adequate for most applications. The catalyst to quantum advances in high-performance rolling-element bearing steels was the advent of the aircraft gas turbine engine. With improved bearing manufacturing and steel processing together with advanced lubrication technology, the potential improvements in bearing life can be as much as 80 times that attainable in the late 1950s or as much as 400 times that attainable in 1940. This paper summarizes the chemical, metallurgical and physical aspects of bearing steels and their effect on rolling bearing life and reliability. The single most important variable that has significantly increased bearing life and reliability is vacuum processing of bearing steel. Differences between through hardened, case carburized and corrosion resistant steels are discussed. The interrelation of alloy elements and carbides and their effect on bearing life are presented. An equation relating bearing life, steel hardness and temperature is given. Life factors for various steels are suggested and discussed. A relation between compressive residual stress and bearing life is presented. The effects of retained austenite and grain size are discussed.

Zaretsky, Erwin V.↗
NASA NTRS2002

Virtually Out of This World!

Ames Research Center granted Reality Capture Technologies (RCT), Inc., a license to further develop NASA's Mars Map software platform. The company incorporated NASA#s innovation into software that uses the Virtual Plant Model (VPM)(TM) to structure, modify, and implement the construction sites of industrial facilities, as well as develop, validate, and train operators on procedures. The VPM orchestrates the exchange of information between engineering, production, and business transaction systems. This enables users to simulate, control, and optimize work processes while increasing the reliability of critical business decisions. Engineers can complete the construction process and test various aspects of it in virtual reality before building the actual structure. With virtual access to and simulation of the construction site, project personnel can manage, access control, and respond to changes on complex constructions more effectively. Engineers can also create operating procedures, training, and documentation. Virtual Plant Model(TM) is a trademark of Reality Capture Technologies, Inc.

Source record↗
NASA NTRS1988

Semi-Markov adjunction to the Computer-Aided Markov Evaluator (CAME)

The rule-based Computer-Aided Markov Evaluator (CAME) program was expanded in its ability to incorporate the effect of fault-handling processes into the construction of a reliability model. The fault-handling processes are modeled as semi-Markov events and CAME constructs and appropriate semi-Markov model. To solve the model, the program outputs it in a form which can be directly solved with the Semi-Markov Unreliability Range Evaluator (SURE) program. As a means of evaluating the alterations made to the CAME program, the program is used to model the reliability of portions of the Integrated Airframe/Propulsion Control System Architecture (IAPSA 2) reference configuration. The reliability predictions are compared with a previous analysis. The results bear out the feasibility of utilizing CAME to generate appropriate semi-Markov models to model fault-handling processes.

Rosch, Gene↗
NASA NTRS1990

State reduction for semi-Markov reliability models

Semi-Markov processes have proved to be an effective and convenient tool to construct models of systems that achieve reliability by redundancy and reconfiguration. These models are able to depict complex system architectures and to capture the dynamics of fault arrival and system recovery. A disadvantage of this approach is that the models can be extremely large, which poses both a model construction and a computational problem. Techniques are needed to reduce the model size. Because these systems are used in critical applications where failure can be expensive, there must be an analytically derived bound for the error produced by the model reduction technique. Automatic model generation programs have been written to help the reliability analyst produce models of complex systems. Because of the importance of these programs, the model reduction technique needs to be precise and easily implemented. This paper presents a model reduction technique called trimming that can be applied to a popular class of systems. An error bound for the trimming procedure is derived that uses readily available system parameters. The trimming procedure is precisely described and appears easy to implement in a model generation program.

Reduced order systems↗
NASA NTRS1993

Workshop on the Space Environment: The Effects on the Optical Properties of Airless Bodies

Reflectance spectrophotometry and polarimetry are major tools in remote sensing studies of surfaces of solar system bodies. The interpretations of such measurements are often based on laboratory studies of meteoritic, lunar, and terrestrial materials. However, the optical properties of regoliths are known to be affected by the space environment. Thus, some of the major questions addressed in the workshop include identity of the soil component responsible for alteration of the optical properties, the process that produced this component, and how reliably the effects of these processes could be extrapolated to other bodies of the solar system.

Hapke, B.↗
NASA NTRS1976

A mature Bosch CO2 reduction technology

The reduction of CO2 is one of the steps in closing the oxygen loop for long-duration manned space missions. Several units utilizing the Bosch process, which catalytically reduces CO2 with hydrogen, have been built and operated during the past decade. Each contributed substantial information affecting subsequent designs. Early challenges were primarily concerned with carbon control, materials durability, and reliability of reaction initiation. These were followed by concern about power consumption, expendable weight, volume, and process rate control. Suitable materials and techniques for carbon containment and process reliability have been demonstrated. Power requirements have been reduced by almost an order of magnitude. Methods for significant reductions in expendable weight and volume have been developed. The technology is at a state of maturity directly applicable to designs for space missions.

King, C. D.↗
NASA NTRS1990

Lightning electromagnetic radiation field spectra in the interval from 0.2 to 20 MHz

New Fourier transforms of wideband time-domain electric fields (E) produced by lightning (recorded at the Kennedy Space Center during the summers of 1985 and 1987) were recorded in such a way that several different events in each lightning flash could be captured. Average HF spectral amplitudes for first return strokes, stepped-leader steps, and 'characteristic pulses' are given for significantly more events, at closer ranges, and with better spectral resolution than in previous literature reports. The method of recording gives less bias toward the first large event in the flash and thus yields a large sample of a wide variety of lightning processes. As a result, reliable composite spectral amplitudes are obtained for a number of different processes in cloud-to-ground lightning over the frequency interval from 0.2 to 20 MHz.

Willett, J. C.↗
NASA NTRS2018

Mechanisms of Oxide Formation in the Self-Reacting Friction Stir Weld Process

The initial objective of this study was to evaluate the effect of an extended delay time between preweld cleaning and the completion of a self-reacting friction stir welding (SRFSW) process on the resulting quality of various thickness panels of AA2219-T87. The current NASA standard specifies no more than a 48 hour delay between preweld cleaning and actual welding. The concern is whether increasing the cleaning delay time results in development of the residual oxide defect (ROD) in SRFSW. This concern emanates from the possibility of increased time correlating with increased oxide layer thickness on the faying surfaces. Oxide content on the faying surfaces has been reported to correlate with the occurrence of the ROD which reduces mechanical properties. When the SRFSW process was first adopted by the NASA Marshall Space Flight Center (MSFC), unexpected low tensile values that resulted were attributed to oxides within the weld that appeared to follow the former faying surface contours. Mitigation of the ROD was achieved through a combination of modifications to the processing parameters, tool designs, and incorporation of a weld seam offset. Two operations are involved in preweld cleaning: the first is removal of oil and grease, and the second is removal of surface oxides. In arc welding, improper cleaning of the faying surfaces of aluminum welded joints can increase the sensitivity toward development of defects. As the aluminum is locally melted, these contaminants contribute toward the development of porosity, inclusions, entrapped oxides, and other discontinuities which can degrade the strength of the weld joint. For weldment of large structures, the weld joint is typically cleaned, fit-up, and tack welded prior to the final full penetration welding pass. Because of the stringent joint fit-up requirements for mismatch and peaking for launch vehicle structures, the joint fit-up can sometimes contribute to lengthy delays between cleaning and tack welding, especially for circumferential weld joints on large diameter components. When the conventional friction stir welding (CFSW) process was introduced at the NASA MSFC, there was no procedure for cleaning prior to the solid-state joining process. As the process expanded to include SRFSW, preparation of the faying, crown, and root surfaces were implemented to overcome the ROD. Although the solid-state process is not expected to reach temperatures high enough for dissociation of the native oxide layer, concern remained regarding the redeposition of the native oxide layer within the stir zone. NASA has previously established the allowable time at 48 hours between preweld cleaning and a SRFSW process. The effect of potential 2 contamination resulting from an extended delay to 188 hours was subsequently evaluated for SRFSWs using tensile testing and metallographic imaging. Tensile specimens were tested at room temperature (RT), and at cryogenic conditions of liquid nitrogen (LN2) and liquid hydrogen. No detrimental effect on weld quality, as determined by weld strength, was reported for cleaning delays of 48, 120, 168, 240 or 288 hours. While no trends were established in this study, which extended the delay from 48 to 188 hours, there were a few outliers in terms of ultimate tensile strength (UTS). According to M. Fisher's 2014 Boeing Company Memo no. EYBF-MAF-14-029, all outliers were above the minimum acceptance criteria, but out of family with respect to the average values. As the robustness and reliability of any process ultimately depends on the average values as well as the outliers, an understanding of the cause of these outliers will ultimately improve the process. This report examines those outliers and their possible causes.

Schneider, J. A.↗