Search NASA⌕ Search

SEARCH · Search NASA

Results for “parts program requirements”

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 289 records · Page 16
All sourcesNASA NTRSDOE OSTI
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 NTRS1977

A user's guide for V174, a program using a finite difference method to analyze transonic flow over oscillating wings

The design and usage of a pilot program using a finite difference method for calculating the pressure distributions over harmonically oscillating wings in transonic flow are discussed. The procedure used is based on separating the velocity potential into steady and unsteady parts and linearizing the resulting unsteady differential equation for small disturbances. The steady velocity potential which must be obtained from some other program, is required for input. The unsteady differential equation is linear, complex in form with spatially varying coefficients. Because sinusoidal motion is assumed, time is not a variable. The numerical solution is obtained through a finite difference formulation and a line relaxation solution method.

Butler, T. D.↗
NASA NTRS1979

A users guide for A344: A program using a finite difference method to analyze transonic flow over oscillating airfoils

The design and usage of a pilot program for calculating the pressure distributions over harmonically oscillating airfoils in transonic flow are described. The procedure used is based on separating the velocity potential into steady and unsteady parts and linearizing the resulting unsteady differential equations for small disturbances. The steady velocity potential which must be obtained from some other program, was required for input. The unsteady equation, as solved, is linear with spatially varying coefficients. Since sinusoidal motion was assumed, time was not a variable. The numerical solution was obtained through a finite difference formulation and either a line relaxation or an out of core direct solution method.

Weatherill, W. H.↗
NASA NTRS1991

Surface-Shading Program

Surface Shading computer program, SURF, developed in support of work of Computational Fluid Dynamics (CFD). Part of CFD graphics software. Accepts input in form of grid and solution files otherwise normally fed to Ames Research Center's version of PLOT3D software from "flow solver" programs. Interactively creates wire-frame, shaded, and function-map parts viewed and then transferred to Ames Research Graphic (ARCGRAPH) standard files, animated with GAS (COSMIC Program ARC-12379). Written in C programming language and requires Silicon Graphics "include" files (e.g., stdio.h, gl.h).

Plessel, Todd↗
NASA NTRS1990

Cryogenic fluid management program at MSFC

Cryogenic fluid management (CFM) is an important aspect in the design and operation of spacecraft propellant systems. Consequently, it represents a key technology in the development of future vehicles for orbital transfer, lunar transit and manned interplanetary (i.e., Mars) missions. Because of Marshall Space Flight Center's (MSFC's) leading role in the definition of such vehicles, the center is currently managing and conducting a variety of tests to support development of this technology. The purpose of this paper is to summarize these activities and present their status within the context of CFM technology requirements. The first section reviews MSFC's role, identifies the major emphases and thrusts of its program, and presents the overall schedule. The final part comprises the bulk of the report, and describes at length the objectives, approach and status of each project.

Schmidt, G. R.↗
NASA NTRS1995

Figures of Merit for Aeronautics Programs and Addition to NASA LARC Fire Station

This report accounts details of two research projects for the Langley Aerospace Research Summer Scholars (LARSS) program. The first project, with the Office of Mission Assurance, involved subjectively predicting the probable success of two aeronautics programs by means of a tool called a Figure of Merit. The figure of merit bases program success on the quality and reliability of the following factors: parts, complexity of research, quality programs, hazards elimination, and single point failures elimination. The second project, for the Office of Safety and Facilities Assurance, required planning, layouts, and source seeking for an addition to the fire house. Forecasted changes in facility layout necessitate this addition which will serve as housing for the fire fighters.

Harper, Belinda M.↗
NASA NTRS2003

Scientific and Technical Development of the Next Generation Space Telescope

The Next Generation Space Telescope (NGST) is part of the Origins program and is the key mission to discover the origins of galaxies in the Universe. It is essential that scientific requirements be translated into technical specifications at the beginning of the program and that there is technical participation by astronomers in the design and modeling of the observatory. During the active time period of this grant, the PI participated in the NGST program at GSFC by participating in the development of the Design Reference Mission, the development of the full end-to-end model of the observatory, the design trade-off based on the modeling, the Science Instrument Module definition and modeling, the study of proto-mission and test-bed development, and by participating in meetings including quarterly reviews and support of the NGST SWG. This work was documented in a series of NGST Monographs that are available on the NGST web site.

Burg, Richard↗
NASA NTRS2007

Integration and Testing Challenges of Small Satellite Missions: Experiences from the Space Technology 5 Project

The Space Technology 5(ST5) payload was successfully carried into orbit on an OSC Pegasus XL launch vehicle, which was carried aloft and dropped from the OSC Lockheed L-1011 from Vandenberg Air Force Base March 22,2006, at 9:03 am Eastern time, 6:03 am Pacific time. In order to reach the completion of the development and successful launch of ST 5, the systems integration and test(I&T) team determined that a different approach was required to meet the project requirements rather than the standard I&T approach used for single, room-sized satellites. The ST5 payload, part of NASA's New Millennium Program headquartered at JPL, consisted of three micro satellites (approximately 30 kg each) and the Pegasus Support Structure (PSS), the system that connected the spacecrafts to the launch vehicle and deployed the spacecrafts into orbit from the Pegasus XL launch vehicle. ST5 was a technology demonstration payload, intended to test six (6) new technologies for potential use for future space flights along with demonstrating the ability of small satellites to perform quality science. The main technology was a science grade magnetometer designed to take measurements of the earth's magnetic field. The three spacecraft were designed, integrated, and tested at NASA Goddard Space Flight Center with integration and environmental testing occurring in the Bldg. 7-1 0-15-29. The three spacecraft were integrated and tested by the same I&T team. The I&T Manager determined that there was insufficient time in the schedule to perform the three I&T spacecraft activities in series used standard approaches. The solution was for spacecraft #1 to undergo integration and test first, followed by spacecraft #2 and #3 simultaneously. This simultaneous integration was successful for several reasons. Each spacecraft had a Lead Test Conductor who planned and coordinated their spacecraft through its integration and test activities. One team of engineers and technicians executed the integration of all three spacecraft, learning and gaining knowledge and efficiency as spacecraft #1 integration and testing progressed. They became acutely familiar with the hardware, operation and processes for I&T, thus each team member had the experience and knowledge to safely execute I&T for spacecraft #2 and #3 together. The integration team was very versatile and each member could perform many different activities or work any spacecraft, when needed. Daily meetings between the three Lead TCs and technician team allowed the team to plan and implement activities efficiently. The three (3) spacecraft and PSS were successfully integrated and tested, shipped to the launch site, and ready for launch per the I&T schedule that was planned three years previously.

Sauerwein, Timothy A.↗
NASA NTRS2010

Making Games Not Work: Paradoxes Embedded in Game-Based Training and Concepts for Overcoming Them

An interest in game-based training solutions is natural. All one has to do is watch someone fully engaged in a modern game to see the potential of harnessing that attention for training. However, the reality of game-based training has not fully satisfied these expectations. This paper explains two paradoxes that must be overcome for games to support training. These paradoxes are a result of the realities of the basic human condition clashing with the requirements of learning theory. 80th paradoxes arise from the concept of "engagement" that is central to games. The first comes from a more robust definition of engagement, which is the condition of Flow or Optimal Experience. Flow is the state game developers want to see in users. One aspect of Flow is loss of sense of self as the individual becomes immersed in the experience. The paradox arises because this loss of self directly contradicts the learning requirement of self-reflection. The second paradox comes from theories of play, which state in part that play requires a level of individual freedom. The contradiction arises when game-based play must be harnessed to an organizational training program or regimen. The paper will discuss these paradoxes in the context of an effort to design a game-based training modality to train combat medics and will close with a review of compensating strategies identified by the designers. The paper will provide information important to anyone interested in conceptualizing and designing game-based training.

Jones, Phillip N.↗
NASA NTRSDate not supplied

Additive Manufactured Hardware Qualification and Certification at NASA

Additive Manufacturing (AM) is certainly changing the space industry and providing new opportunities to travel to low earth orbit and explore our universe New design opportunities –not previously possible –for new high performance metal alloys, light-weighting, managing thermal, structural, and dynamic loads are being enabled by AM. Additively manufactured parts are already being inserted for complext system for NASA programs in critical applications –“ready to fly” Human exploration of space, especially deep space, requires extreme reliability Qualification of AM design/parts/process and Flight Certification

Alison Park↗
NASA NTRS1984

Design enhancement tools in MSC/NASTRAN

Design sensitivity is the calculation of derivatives of constraint functions with respect to design variables. While a knowledge of these derivatives is useful in its own right, the derivatives are required in many efficient optimization methods. Constraint derivatives are also required in some reanalysis methods. It is shown where the sensitivity coefficients fit into the scheme of a basic organization of an optimization procedure. The analyzer is to be taken as MSC/NASTRAN. The terminator program monitors the termination criteria and ends the optimization procedure when the criteria are satisfied. This program can reside in several plances: in the optimizer itself, in a user written code, or as part of the MSC/EOS (Engineering Operating System) MSC/EOS currently under development. Since several excellent optimization codes exist and since they require such very specialized technical knowledge, the optimizer under the new MSC/EOS is considered to be selected and supplied by the user to meet his specific needs and preferences. The one exception to this is a fully stressed design (FSD) based on simple scaling. The gradients are currently supplied by various design sensitivity options now existing in MSC/NASTRAN's design sensitivity analysis (DSA).

Wallerstein, D. V.↗
NASA NTRS1971

Study of Alternate Space Shuttle Concepts. Volume 2. Part 1: Concept Analysis and Definition

Three different space shuttle systems have been defined and analyzed. The first is a stage-and-one-half system optimized to meet program requirements. The second is a two-stage, fully reusable system also designed to meet program requirements. The third is a convertible system which operates initially as a stage-and-one-half system and is subsequently converted to a two-stage, fully reusable system by reconfiguration of the orbiter vehicle and development of a booster vehicle. The design and performance of this third system must necessarily be compromised somewhat to facilitate the conversion. For each system, the applicable requirements, ground rules, and assumptions are defined. The characteristics of each system are listed and a detailed description and analysis of the system are presented. Finally, a cost analysis for the system is given.

Source record↗
NASA NTRS1974

Earth Observatory Satellite system definition study. Report no. 5: System design and specifications. Part 2: Ground system element specifications

The Ground System requirements for the Land Resources Management (LRM) type-A and type-B missions of the Earth Observatory Satellite (EOS) program are presented. Specifications for the Thematic Mapper data processing are provided (LRM A mission). The specifications also cover the R and D instruments (Thematic Mapper and High Resolution Pointable Imager) data processing for the LRM type-B mission.

Source record↗
NASA NTRS1994

Propagating orientation constraints for the Hubble Space Telescope

An observing program on the Hubble Space Telescope (HST) is described in terms of exposures that are obtained by one or more of the instruments onboard the HST. Many requested exposures might specify orientation requirements and accompanying ranges. Orientation refers to the amount of roll (in degrees) about the line of sight. The range give the permissible tolerance (also in degrees). These requirements may be (1) absolute (in relation to the celestial coordinate system), (2) relative to the nominal roll angle for HST during that exposure, or (3) relative (in relation to other exposures in the observing program). The TRANSformation expert system converts proposals for astronomical observations with HST into detailed observing plans. Part of the conversion involves grouping exposures into higher level structures based on exposure characteristics. Exposures constrained to be at different orientations cannot be grouped together. Because relative orientation requirements cause implicit constraints, orientation constraints have to be propagated. TRANS must also identify any inconsistencies that may exist so they can be corrected. We have designed and implemented an orientation constraint propagator as part of TRANS. The propagator is based on an informal algebra that facilitates the setting up and propagation of the orientation constraints. The constraint propagator generates constraints between directly related exposures, and propagates derived constraints between exposures that are related indirectly. It provides facilities for path-consistency checking, identification of unsatisfiable constraints, and querying of orientation relationships. The system has been successfully operational as part of TRANS for over seven months. The solution has particular significance to space applications in which satellite/telescope pointing and attitude are constrained and relationships exist between multiple configurations.

Bose, Ashim↗
NASA NTRS2011

NASA Risk Management Handbook

The purpose of this handbook is to provide guidance for implementing the Risk Management (RM) requirements of NASA Procedural Requirements (NPR) document NPR 8000.4A, Agency Risk Management Procedural Requirements [1], with a specific focus on programs and projects, and applying to each level of the NASA organizational hierarchy as requirements flow down. This handbook supports RM application within the NASA systems engineering process, and is a complement to the guidance contained in NASA/SP-2007-6105, NASA Systems Engineering Handbook [2]. Specifically, this handbook provides guidance that is applicable to the common technical processes of Technical Risk Management and Decision Analysis established by NPR 7123.1A, NASA Systems Engineering Process and Requirements [3]. These processes are part of the \Systems Engineering Engine. (Figure 1) that is used to drive the development of the system and associated work products to satisfy stakeholder expectations in all mission execution domains, including safety, technical, cost, and schedule. Like NPR 7123.1A, NPR 8000.4A is a discipline-oriented NPR that intersects with product-oriented NPRs such as NPR 7120.5D, NASA Space Flight Program and Project Management Requirements [4]; NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements [5]; and NPR 7120.8, NASA Research and Technology Program and Project Management Requirements [6]. In much the same way that the NASA Systems Engineering Handbook is intended to provide guidance on the implementation of NPR 7123.1A, this handbook is intended to provide guidance on the implementation of NPR 8000.4A. 1.2 Scope and Depth This handbook provides guidance for conducting RM in the context of NASA program and project life cycles, which produce derived requirements in accordance with existing systems engineering practices that flow down through the NASA organizational hierarchy. The guidance in this handbook is not meant to be prescriptive. Instead, it is meant to be general enough, and contain a sufficient diversity of examples, to enable the reader to adapt the methods as needed to the particular risk management issues that he or she faces. The handbook highlights major issues to consider when managing programs and projects in the presence of potentially significant uncertainty, so that the user is better able to recognize and avoid pitfalls that might otherwise be experienced.

Dezfuli, Homayoon↗
NASA NTRS1973

Feasibility study of an Integrated Program for Aerospace-vehicle Design (IPAD) system. Volume 5: Design of the IPAD system. Part 2: System design. Part 3: General purpose utilities, phase 1, task 2

Viable designs are presented of various elements of the IPAD framework software, data base management system, and required new languages in relation to the capabilities of operating systems software. A thorough evaluation was made of the basic systems functions to be provide by each software element, its requirements defined in the conceptual design, the operating systems features affecting its design, and the engineering/design functions which it was intended to enhance.

Garrocq, C. A.↗
NASA NTRS1995

AMCC casting development. Volume 1: Executive Summary

The Advanced Combustion Chamber Casting (AMCC) has been a technically challenging part due to its size, configuration, and alloy type. The height and weight of the wax pattern assembly necessitated the development of a hollow gating system to ensure structural integrity of the shell throughout the investment process. The complexity in the jacket area of the casting required the development of an innovative casting technology that PCC has termed 'TGC' or Thermal Gradient Control. This method, of setting up thermal gradients in the casting during solidification, represents a significant process improvement for PCC and has been successfully implemented on other programs. Metallurgical integrity of the final four castings was very good. Only the areas of the parts that utilized 'TGC Shape & Location System #2' showed any significant areas of microshrinkage when evaluated by non-destructive tests. Alumina oxides detected by FPI on the 'float' surfaces (top sid surfaces of the casting during solidification) of the part were almost entirely less than the acceptance criteria of .032 inches in diameter. Destructive chem mill of the castings was required to determine the effect of the process variables used during the processing of these last four parts (with the exception of the 'Shape & Location of TGC' variable).

Source record↗
NASA NTRS1975

Life sciences laboratory breadboard simulations for shuttle

Breadboard simulations of life sciences laboratory concepts for conducting bioresearch in space were undertaken as part of the concept verification testing program. Breadboard simulations were conducted to test concepts of and scope problems associated with bioresearch support equipment and facility requirements and their operational integration for conducting manned research in earth orbital missions. It emphasized requirements, functions, and procedures for candidate research on crew members (simulated) and subhuman primates and on typical radioisotope studies in rats, a rooster, and plants.

Taketa, S. T.↗