Performance verification of the lunar descent program - P66 auto, task E-72C
Results of simulated runs to evaluate lunar module descent performance of P66 automatic control and guidance system
SEARCH · Search NASA
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.
Results of simulated runs to evaluate lunar module descent performance of P66 automatic control and guidance system
Many PWR spent fuels have been transferred between the neighboring nuclear power plants at Kori, Hanbit, Hanwul site, and from nuclear power plant to the KAERI(Korea Atomic Energy Research Institute) for the research purpose in Korea. In case of the PHWR type spent fuels, these have been transferred from the spent fuel pool to an on-site dry storage facility. Total radioactivity of spent fuels has to be calculated before transport in advance by the regulation requirement. In case of PWR, KN-12 transport cask can transfer 12 spent fuel assemblies at one time and in case of PHWR, Hi-STAR 63 transport cask can transfer 120 spent fuel assemblies at one time. Therefore, total radioactivity of all transported spent fuel assemblies that are transported generally are calculated by using the ORIGEN-ARP to meet this regulatory requirement. Basically, ORIGEN-ARP calculates the one fuel assembly at one time. SCALE code including this code provides the batch mode to perform the multi-calculations of the source term. In this study, in order to use the batch mode of ORIGEN-ARP, ARP-auto program was developed to generate input files and batch file of ORIGEN-ARP automatically and to make the summary file extracting the result from output files of ORIGEN-ARP. This code enhances the efficiency at the field. The working time to complete the calculation of source terms of 120 spent fuel assemblies take only 20 minutes. In order to confirm the credibility of this code, total radioactivity of 12 spent fuel assemblies of 17x17 Westinghouse type were calculated and compared to the previous result. The initial enrichments of these spent fuels are 3.46 ∼ 3.50 w/o and burnups are 29 ∼ 43 GWD/MTU. As the results, the relative errors are about 0.9 ∼ 3.0%. (authors)
A new classification of Infrared spectra collected by the Infrared Astronomical Satellite (IRAS) is presented. The spectral classes were discovered automatically by a program called Auto Class 2. This program is a method for discovering (inducing) classes from a data base, utilizing a Bayesian probability approach. These classes can be used to give insight into the patterns that occur in the particular domain, in this case, infrared astronomical spectroscopy. The classified spectra are the entire Low Resolution Spectra (LRS) Atlas of 5,425 sources. There are seventy-seven classes in this classification and these in turn were meta-classified to produce nine meta-classes. The classification is presented as spectral plots, IRAS color-color plots, galactic distribution plots and class commentaries. Cross-reference tables, listing the sources by IRAS name and by Auto Class class, are also given. These classes show some of the well known classes, such as the black-body class, and silicate emission classes, but many other classes were unsuspected, while others show important subtle differences within the well known classes.
Program to draw flowcharts automatically from PERT, Fortran II, Fortran IV, or FAP cards
The Composite Armored Vehicle (CAV) is an advanced technology demonstrator of an all-composite ground combat vehicle. The CAV upper hull is made of a tough light-weight S2-glass/epoxy laminate with embedded ceramic tiles that serve as armor. The tiles are bonded to a rubber mat with a carefully selected, highly viscoelastic adhesive. The integration of armor and structure offers an efficient combination of ballistic protection and structural performance. The analysis of this anisotropic construction, with its inherent discontinuous and periodic nature, however, poses several challenges. The present paper describes a shell-based 'element-layering' technique that properly accounts for these effects and for the concentrated transverse shear flexibility in the rubber mat. One of the most important advantages of the element-layering technique over advanced higher-order elements is that it is based on conventional elements. This advantage allows the models to be portable to other structural analysis codes, a prerequisite in a program that involves the computational facilities of several manufacturers and government laboratories. The element-layering technique was implemented into an auto-layering program that automatically transforms a conventional shell model into a multi-layered model. The effects of tile layer homogenization, tile placement patterns, and tile gap size on the analysis results are described.
This is the final report for the referenced TCF award which ran from Oct. 2019 through Jan. 2024 in conjunction with the industry partner Swift Solar. The long duration of the program was due to several factors including the pandemic and a technical work stoppage due to changes in the scope. Additionally, Swift’s business focus shifted during the course of the program. As a result of these factors, this program underwent two distinct modifications that dramatically changed the work scope. The following report is organized into three separate sections, each of which addresses a distinct work scope. Those scope changes, what necessitated them, and any new tasks/milestones are given, briefly, at the top of each section. The work performed was research on the hybrid halide perovskites (HHP), both the absorber material itself as well as other material layers that are required in a full device stack. At the start of the period of performance, there were two distinct challenges that we sought to address: (1) a wide band gap absorber (>1.6 eV), and (2) a recombination layer for tandem devices that provided good sequestration of the individual cell absorber materials in their respective device layers. NREL had previously published, and patented, advancements in both of these areas and they were the focus of much of the work throughout the program. The auto manufacturing space is evolving quickly. Sales of various electrified vehicles (xEVs) continue to grow steadily, which has medium to long-term ramifications for the thousands of U.S. manufacturers and hundreds of thousands of workers that contribute to the domestic automotive supply chain. In tandem with this growth in xEV sales, domestic clean energy manufacturing is surging (both for the xEV supply chain and other technologies), with public incentives spurring billions in private sector investment. Moreover, the next 2–3 years will see new and expanded industrial facilities come online to make products like hydrogen electrolyzers, solar panels, batteries, advanced electronics—and will create new supply chain needs and business opportunities as they do. DOE’s Office of Manufacturing and Energy Supply Chains (MESC) and Argonne National Laboratory developed this report to help automotive manufacturers—alongside various business support partners— understand these trends and their response options, and to make the most of current federal assistance programs for manufacturers. These market changes may create opportunities for small- and medium-sized manufacturers (SMMs) to expand production, grow profit margins, and diversify their businesses. For instance, SMMs could take advantage of engineering and process design similarities with new end-use industries that might enable greater business growth and stability as markets continue to change.
Purpose: Although reduction of the cine EPID acquisition frame rate through multiple frame averaging may reduce hardware memory burden and decrease image noise, it can hinder the continuity of soft-tissue motion leading to poor auto-tracking results. The impact of motion blurring and image noise on the tracking performance was investigated. Methods: Phantom and patient images were acquired at a frame rate of 12.87Hz on an AS1000 portal imager. Low frame rate images were obtained by continuous frame averaging. A previously validated tracking algorithm was employed for auto-tracking. The difference between the programmed and auto-tracked positions of a Las Vegas phantom moving in the superior-inferior direction defined the tracking error (δ). Motion blurring was assessed by measuring the area change of the circle with the greatest depth. Additionally, lung tumors on 1747 frames acquired at eleven field angles from four radiotherapy patients are manually and automatically tracked with varying frame averaging. δ was defined by the position difference of the two tracking methods. Image noise was defined as the standard deviation of the background intensity. Motion blurring and image noise were correlated with δ using Pearson correlation coefficient (R). Results: For both phantom and patient studies, the auto-tracking errors increased at frame rates lower than 4.29Hz. Above 4.29Hz, changes in errors were negligible with δ<1.60mm. Motion blurring and image noise were observed to increase and decrease with frame averaging, respectively. Motion blurring and tracking errors were significantly correlated for the phantom (R=0.94) and patient studies (R=0.72). Moderate to poor correlation was found between image noise and tracking error with R -0.58 and -0.19 for both studies, respectively. Conclusion: An image acquisition frame rate of at least 4.29Hz is recommended for cine EPID tracking. Motion blurring in images with frame rates below 4.39Hz can substantially reduce the accuracy of auto-tracking. This work is supported in part by the Varian Medical Systems, Inc.
A navigation and communications network is proposed to support an anticipated need for infrastructure in the Earth-Moon system. Periodic orbits will host the constellations while a novel, autonomous navigation strategy will guide the spacecraft along their path strictly based on satellite-to-satellite telemetry. In particular, this paper investigates the second stage of a larger constellation optimization scheme for multi-spacecraft systems. That is, following an initial orbit down-selection process, this analysis provides insights into the ancillary problem of spacecraft placement. Two case studies are presented that consider configurations of up to four spacecraft for a halo orbit and a cycler trajectory.
This lecture combines the theoretical background of schema based program synthesis with the hands-on study of a powerful, open-source program synthesis system (Auto-Bayes). Schema-based program synthesis is a popular approach toward program synthesis. The lecture will provide an introduction into this topic and discuss how this technology can be used to generate customized algorithms. The synthesis of advanced numerical algorithms requires the availability of a powerful symbolic (algebra) system. Its task is to symbolically solve equations, simplify expressions, or to symbolically calculate derivatives (among others) such that the synthesized algorithms become as efficient as possible. We will discuss the use and importance of the symbolic system for synthesis. Any synthesis system is a large and complex piece of code. In this lecture, we will study Autobayes in detail. AutoBayes has been developed at NASA Ames and has been made open source. It takes a compact statistical specification and generates a customized data analysis algorithm (in C/C++) from it. AutoBayes is written in SWI Prolog and many concepts from rewriting, logic, functional, and symbolic programming. We will discuss the system architecture, the schema libary and the extensive support infra-structure. Practical hands-on experiments and exercises will enable the student to get insight into a realistic program synthesis system and provides knowledge to use, modify, and extend Autobayes.
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.
Cognitive Radio will revolutionize American transportation. Through smart technology, it will anticipate user needs; detect available bandwidths and frequencies then seamlessly connect vehicles, infrastructures, and consumer devices; and it will support the Department of Transportation IntelliDrive Program, helping researchers, auto manufacturers, and Federal and State officials advance the connectivity of US transportation systems for improved safety, mobility, and environmental conditions. Using cognitive radio, a commercial vehicle will know its driver, onboard freight and destination route. Drivers will save time and resources communicating with automatic toll booths and know ahead of time whether to stop at a weigh station or keep rolling. At accident scenes, cognitive radio sensors on freight and transportation modes can alert emergency personnel and measure on-site, real-time conditions such as a chemical leak. The sensors will connect freight to industry, relaying shipment conditions and new delivery schedules. For industry or military purposes, cognitive radio will enable real-time freight tracking around the globe and its sensory technology can help prevent cargo theft or tampering by alerting shipper and receiver if freight is tampered with while en route. For the average consumer, a vehicle will tailor the transportation experience to the passenger such as delivering age-appropriate movies via satellite. Cognitive radio will enhance transportation safety by continually sensing what is important to the user adapting to its environment and incoming information, and proposing solutions that improve mobility and quality of life.
Demand Response (DR) can be defined as actions taken to reduce electric loads when contingencies, such as emergencies and congestion, occur that threaten supply-demand balance, or market conditions raise supply costs. California utilities have offered price and reliability DR based programs to customers to help reduce electric peak demand. The lack of knowledge about the DR programs and how to develop and implement DR control strategies is a barrier to participation in DR programs, as is the lack of automation of DR systems. Most DR activities are manual and require people to first receive notifications, and then act on the information to execute DR strategies. Levels of automation in DR can be defined as follows. Manual Demand Response involves a labor-intensive approach such as manually turning off or changing comfort set points at each equipment switch or controller. Semi-Automated Demand Response involves a pre-programmed demand response strategy initiated by a person via centralized control system. Fully-Automated Demand Response does not involve human intervention, but is initiated at a home, building, or facility through receipt of an external communications signal. The receipt of the external signal initiates pre-programmed demand response strategies. We refer to this as Auto-DR (Piette et. al. 2005). Auto-DR for commercial and industrial facilities can be defined as fully automated DR initiated by a signal from a utility or other appropriate entity and that provides fully-automated connectivity to customer end-use control strategies. One important concept in Auto-DR is that a homeowner or facility manager should be able to 'opt out' or 'override' a DR event if the event comes at time when the reduction in end-use services is not desirable. Therefore, Auto-DR is not handing over total control of the equipment or the facility to the utility but simply allowing the utility to pass on grid related information which then triggers facility defined and programmed strategies if convenient to the facility. From 2003 through 2006 Lawrence Berkeley National Laboratory (LBNL) and the Demand Response Research Center (DRRC) developed and tested a series of demand response automation communications technologies known as Automated Demand Response (Auto-DR). In 2007, LBNL worked with three investor-owned utilities to commercialize and implement Auto-DR programs in their territories. This paper summarizes the history of technology development for Auto-DR, and describes the DR technologies and control strategies utilized at many of the facilities. It outlines early experience in commercializing Auto-DR systems within PG&E DR programs, including the steps to configure the automation technology. The paper also describes the DR sheds derived using three different baseline methodologies. Emphasis is given to the lessons learned from installation and commissioning of Auto-DR systems, with a detailed description of the technical coordination roles and responsibilities, and costs.
SPAR, a computer program developed by Lewis, is used to optimize the design of body panels by Chrysler Corporation. The program is interactive, easy to use, and fast.
Recently, advances in processor architecture have become the driving force for new programming models in the computing industry, as ever newer multicore processor designs with increasing number of cores are introduced on schedules regimented by marketing demands. As a result, collaborative parallel (rather than simply concurrent) implementations of important applications, programming languages, models, and even algorithms have been forced to adapt to these architectures to exploit the available raw performance. We believe that this optimization regime is flawed. In this paper, we present an alternate approach that, rather than starting with an existing hardware/software solution laced with hidden assumptions, defines the computational problems of interest and invites architects, researchers and programmers to implement novel hardware/software co-designed solutions. Our work builds on the previous ideas of computational dwarfs, motifs, and parallel patterns by selecting a representative set of essential problems for which we provide: An algorithmic description; scalable problem definition; illustrative reference implementations; verification schemes. This testbed will enable comparative research in areas such as parallel programming models, languages, auto-tuning, and hardware/software codesign. For simplicity, we focus initially on the computational problems of interest to the scientific computing community but proclaim the methodology (and perhaps a subset of the problems) as applicable to other communities. We intend to broaden the coverage of this problem space through stronger community involvement.
MUPPET is a tool for OpenMP programs that identifies program modifications, called mutations, aimed at improving program performance. Existing performance optimization techniques, including profiling-based and auto-tuning techniques, fail to indicate program modifications at the source level thus preventing their portability across compilers. MUPPET aims to help HPC developers reason about performance defects and missed opportunities to improve performance at the source code level.
Recently, advances in processor architecture have become the driving force for new programming models in the computing industry, as ever newer multicore processor designs with increasing number of cores are introduced on schedules regimented by marketing demands. As a result, collaborative parallel (rather than simply concurrent) implementations of important applications, programming languages, models, and even algorithms have been forced to adapt to these architectures to exploit the available raw performance. We believe that this optimization regime is flawed. In this paper, we present an alternate approach that, rather than starting with an existing hardware/software solution laced with hidden assumptions, defines the computational problems of interest and invites architects, researchers and programmers to implement novel hardware/software co-designed solutions. Our work builds on the previous ideas of computational dwarfs, motifs, and parallel patterns by selecting a representative set of essential problems for which we provide: An algorithmic description; scalable problem definition; illustrative reference implementations; verification schemes. This testbed will enable comparative research in areas such as parallel programming models, languages, auto-tuning, and hardware/software codesign. For simplicity, we focus initially on the computational problems of interest to the scientific computing community but proclaim the methodology (and perhaps a subset of the problems) as applicable to other communities. We intend to broaden the coverage of this problem space through stronger community involvement.
Formal certification is based on the idea that a mathematical proof of some property of a piece of software can be regarded as a certificate of correctness which, in principle, can be subjected to external scrutiny. In practice, however, proofs themselves are unlikely to be of much interest to engineers. Nevertheless, it is possible to use the information obtained from a mathematical analysis of software to produce a detailed textual justification of correctness. In this paper, we describe an approach to generating textual explanations from automatically generated proofs of program safety, where the proofs are of compliance with an explicit safety policy that can be varied. Key to this is tracing proof obligations back to the program, and we describe a tool which implements this to certify code auto-generated by AutoBayes and AutoFilter, program synthesis systems under development at the NASA Ames Research Center. Our approach is a step towards combining formal certification with traditional certification methods.
This report summarizes the developments of an integrated simulation program for enabling simulation, auto-sizing, and optimization of geothermal heat pump systems. This work fulfills the following FY20 third milestone for WBS 2.5.5.3: Advanced Techno-Economic Modeling for Geothermal Heat Pump Applications in Residential, Commercial, and Industry Building.