SEARCH · Engineering Papers

Results for “sequence 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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 109 records · Page 6

All sources NASA NTRS DOE OSTI

NASA NTRS2012

Irreducible Tests for Space Mission Sequencing Software

As missions extend further into space, the modeling and simulation of their every action and instruction becomes critical. The greater the distance between Earth and the spacecraft, the smaller the window for communication becomes. Therefore, through modeling and simulating the planned operations, the most efficient sequence of commands can be sent to the spacecraft. The Space Mission Sequencing Software is being developed as the next generation of sequencing software to ensure the most efficient communication to interplanetary and deep space mission spacecraft. Aside from efficiency, the software also checks to make sure that communication during a specified time is even possible, meaning that there is not a planet or moon preventing reception of a signal from Earth or that two opposing commands are being given simultaneously. In this way, the software not only models the proposed instructions to the spacecraft, but also validates the commands as well.To ensure that all spacecraft communications are sequenced properly, a timeline is used to structure the data. The created timelines are immutable and once data is as-signed to a timeline, it shall never be deleted nor renamed. This is to prevent the need for storing and filing the timelines for use by other programs. Several types of timelines can be created to accommodate different types of communications (activities, measurements, commands, states, events). Each of these timeline types requires specific parameters and all have options for additional parameters if needed. With so many combinations of parameters available, the robustness and stability of the software is a necessity. Therefore a baseline must be established to ensure the full functionality of the software and it is here where the irreducible tests come into use.

sequencing test↗

NASA NTRS2006

Leveraging Existing Mission Tools in a Re-Usable, Component-Based Software Environment

Emerging methods in component-based software development offer significant advantages but may seem incompatible with existing mission operations applications. In this paper we relate our positive experiences integrating existing mission applications into component-based tools we are delivering to three missions. In most operations environments, a number of software applications have been integrated together to form the mission operations software. In contrast, with component-based software development chunks of related functionality and data structures, referred to as components, can be individually delivered, integrated and re-used. With the advent of powerful tools for managing component-based development, complex software systems can potentially see significant benefits in ease of integration, testability and reusability from these techniques. These benefits motivate us to ask how component-based development techniques can be relevant in a mission operations environment, where there is significant investment in software tools that are not component-based and may not be written in languages for which component-based tools even exist. Trusted and complex software tools for sequencing, validation, navigation, and other vital functions cannot simply be re-written or abandoned in order to gain the advantages offered by emerging component-based software techniques. Thus some middle ground must be found. We have faced exactly this issue, and have found several solutions. Ensemble is an open platform for development, integration, and deployment of mission operations software that we are developing. Ensemble itself is an extension of an open source, component-based software development platform called Eclipse. Due to the advantages of component-based development, we have been able to vary rapidly develop mission operations tools for three surface missions by mixing and matching from a common set of mission operation components. We have also had to determine how to integrate existing mission applications for sequence development, sequence validation, and high level activity planning, and other functions into a component-based environment. For each of these, we used a somewhat different technique based upon the structure and usage of the existing application.

Greene, Kevin↗

NASA NTRS1984

The USL NASA PC R and D interactive presentation development system

The Interactive Presentation Development System (IPFS) is a highly interactive system for creating, editing, and displaying video presentation sequences, e.g., for developing and presenting displays of instructional material similiar to overhead transparency or slide presentations. However, since this system is PC-based, users (instructors) can step through sequences forward or backward, focusing attention to areas of the display with special cursor pointers. Additionally, screen displays may be dynamically modified during the presentation to show assignments or to answer questions, much like a traditional blackboard. This system is now implemented at the University of Southwestern Louisiana for use within the piloting phases of the NASA contract work.

Dominick, Wayne D.↗

NASA NTRSDate not supplied

Assessing Huygens Probe Entry, Descent, and Landing at Titan Simulation using Dragonfly Atmosphere Model

Dragonfly is a New Frontiers Program mission that will deliver a rotorcraft to Saturn's moon, Titan. This mission follows Huygens as the previous mission that successfully landed a vehicle on Titan. A flight mechanics simulation of Dragonfly's Entry, Descent, and Landing sequence has been developed using the Program to Optimize Simulated Trajectories II. The simulation incorporates several subsystem models, including aerodynamics, gravity, and mass properties, to fully capture the multi-body six degree of freedom dynamics. Among all the subsystem models that inform the Entry, Descent, and Landing dynamics, the atmosphere model of Titan is a critical component. The atmosphere model characterizes the density, temperature, pressure, and winds that the entry vehicle experiences during the descent. This impacts several aspects of the descent such as the peak heating, aerodynamics, parachute release conditions, the dynamics of the vehicle and parachutes, and the landing ellipse. In the course of developing Dragonfly, an updated model of the Titan atmosphere has been created corresponding to Dragonfly's arrival in the mid-2030s, approximately one Titan year after the Huygens mission successfully landed a probe on Titan. This work leverages previous work done to investigate Huygens EDL sequence to assess the atmosphere model developed for Dragonfly. This is done by utilizing the updated Titan atmosphere model, the Dragonfly atmosphere model, within the Huygens POST2-based flight simulation with the goal of characterizing the differences between the atmospheric models and assessing how the Dragonfly atmosphere model impacts Huygens entry dynamics.

Huygens↗

NASA NTRSDate not supplied

Assessing Huygens Probe Entry, Descent, and Landing at Titan Simulation using Dragonfly Atmosphere Model

Entry Descent Landing↗

NASA NTRS2016

Development of a Mars Environmental Control and Life Support System (ECLSS).

ECLS systems for very long-duration human missions to Mars will be designed to operate reliably for many years and will never be returned to Earth. The need for high reliability is driven by unsympathetic abort scenarios. Abort from a Mars mission could be as long as 450 days to return to Earth. Simply put, the goal of an ECLSS is to duplicate the functions the Earth provides in terms of human living and working on our home planet but without the benefit of the Earth's large buffers - the atmospheres, the oceans and land masses. With small buffers a space-based ECLSS must operate as a true dynamic system rather than independent processors taking things from tanks, processing them, and then returning them to product tanks. Key is a development process that allows for a logical sequence of validating successful development (maturation) in a stepwise manner with key performance parameters (KPPs) at each step; especially KPPs for technologies evaluated in a full systems context with human crews on Earth and on space platforms such as the ISS. This paper will explore the implications of such an approach to ECLSS development and the roles of ground and space-based testing necessary to develop a highly reliable life support system for long duration human exploration missions. Historical development and testing of ECLS systems from Mercury to the International Space Station (ISS) will be reviewed. Current work as well as recommendations for future work will be described.

Henninger, Donald L.↗

NASA NTRS2016

Integrated Human-in-the-Loop Ground Testing - Value, History, and the Future

Systems for very long-duration human missions to Mars will be designed to operate reliably for many years and many of these systems will never be returned to Earth. The need for high reliability is driven by the requirement for safe functioning of remote, long-duration crewed systems and also by unsympathetic abort scenarios. Abort from a Mars mission could be as long as 450 days to return to Earth. The key to developing a human-in-the-loop architecture is a development process that allows for a logical sequence of validating successful development in a stepwise manner, with assessment of key performance parameters (KPPs) at each step; especially important are KPPs for technologies evaluated in a full systems context with human crews on Earth and on space platforms such as the ISS. This presentation will explore the implications of such an approach to technology development and validation including the roles of ground and space-based testing necessary to develop a highly reliable system for long duration human exploration missions. Historical development and systems testing from Mercury to the International Space Station (ISS) to ground testing will be reviewed. Current work as well as recommendations for future work will be described.

Henninger, Donald L.↗

NASA NTRS2011

Vacuum Nuller Testbed (VNT) Performance, Characterization and Null Control: Progress Report

Herein we report on the development. sensing and control and our first results with the Vacuum Nuller Testbed to realize a Visible Nulling Coronagraph (VNC) for exoplanet coronagraphy. The VNC is one of the few approaches that works with filled. segmented and sparse or diluted-aperture telescope systems. It thus spans a range of potential future NASA telescopes and could be Hown as a separate instrument on such a future mission. NASA/Goddard Space Flight Center (GSFC) has a well-established effort to develop VNC technologies. and has developed an incremental sequence of VNC testbeds to advance this approach and the enabling technologies associated with it. We discuss the continued development of the vacuum Visible Nulling Coronagraph testbed (VNT). Tbe VNT is an ultra-stable vibration isolated testbed that operates under closed-loop control within a vacuum chamber. It will be used to achieve an incremental sequence of three visible-light nulling milestones with sequentially higher contrasts of 10(sup 8), 10(sup 9) and ideally 10(sup 10) at an inner working angle of 2*lambda/D. The VNT is based on a modified Mach-Zehnder nulling interferometer, with a "W" configuration to accommodate a hex-packed MEMS based deformable mirror, a coherent fiber bundle and achromatic phase shifters. We discuss the initial laboratory results, the optical configuration, critical technologies and the null sensing and control approach.

Lyon, Richard G.↗

NASA NTRS1978

The point mutation process in proteins

An optimized scoring matrix for residue-by-residue comparisons of distantly related protein sequences has been developed. The scoring matrix is based on observed exchanges and mutabilities of amino acids in 1572 closely related sequences derived from a cross-section of protein groups. Very few superimposed or parallel mutations are included in the data. The scoring matrix is most useful for demonstrating the relatedness of proteins between 65 and 85% different.

Schwartz, R. M.↗

NASA NTRS2010

Visible Nulling Coronagraphy Testbed Development for Exoplanet Detection

Three of the recently completed NASA Astrophysics Strategic Mission Concept (ASMC) studies addressed the feasibility of using a Visible Nulling Coronagraph (VNC) as the prime instrument for exoplanet science. The VNC approach is one of the few approaches that works with filled, segmented and sparse or diluted aperture telescope systems and thus spans the space of potential ASMC exoplanet missions. NASA/Goddard Space Flight Center (GSFC) has a well-established effort to develop VNC technologies and has developed an incremental sequence of VNC testbeds to advance the this approach and the technologies associated with it. Herein we report on the continued development of the vacuum Visible Nulling Coronagraph testbed (VNT). The VNT is an ultra-stable vibration isolated testbed that operates under high bandwidth closed-loop control within a vacuum chamber. It will be used to achieve an incremental sequence of three visible light nulling milestones of sequentially higher contrasts of 10(exp 8) , 10(exp 9) and 10(exp 10) at an inner working angle of 2*lambda/D and ultimately culminate in spectrally broadband (>20%) high contrast imaging. Each of the milestones, one per year, is traceable to one or more of the ASMC studies. The VNT uses a modified Mach-Zehnder nulling interferometer, modified with a modified "W" configuration to accommodate a hex-packed MEMS based deformable mirror, a coherent fiber bundle and achromatic phase shifters. Discussed will be the optical configuration laboratory results, critical technologies and the null sensing and control approach.

Lyon, Richard G.↗

NASA NTRS1978

Evaluation of options for process sequences

A methodology is being developed to ease the comparative evaluation of competing options in the process sequence for the manufacture of photovoltaic solar energy utilization systems. This evaluation will largely involve process economic analyses but will place equal emphasis on other characteristics, including energy consumption and environmental effects of the process options. Early analyses have been performed for the energy consumption in the arc furnace reduction of SiO2, for the costs and energy consumption in CZ crystal pulling and various slicing processes, and for the total energy consumption of process sequence through the completed module.

Wolf, M.↗

NASA NTRS1999

A new version of the RDP (Ribosomal Database Project)

The Ribosomal Database Project (RDP-II), previously described by Maidak et al. [ Nucleic Acids Res. (1997), 25, 109-111], is now hosted by the Center for Microbial Ecology at Michigan State University. RDP-II is a curated database that offers ribosomal RNA (rRNA) nucleotide sequence data in aligned and unaligned forms, analysis services, and associated computer programs. During the past two years, data alignments have been updated and now include >9700 small subunit rRNA sequences. The recent development of an ObjectStore database will provide more rapid updating of data, better data accuracy and increased user access. RDP-II includes phylogenetically ordered alignments of rRNA sequences, derived phylogenetic trees, rRNA secondary structure diagrams, and various software programs for handling, analyzing and displaying alignments and trees. The data are available via anonymous ftp (ftp.cme.msu. edu) and WWW (http://www.cme.msu.edu/RDP). The WWW server provides ribosomal probe checking, approximate phylogenetic placement of user-submitted sequences, screening for possible chimeric rRNA sequences, automated alignment, and a suggested placement of an unknown sequence on an existing phylogenetic tree. Additional utilities also exist at RDP-II, including distance matrix, T-RFLP, and a Java-based viewer of the phylogenetic trees that can be used to create subtrees.

Non-NASA Center↗

NASA NTRS1972

Application of optimization techniques to near terminal area sequencing and flow control.

Development of an arrival air-traffic management system for a single runway. Traffic is segregated throughout most of the near terminal area according to performance characteristics. Nominal approach routes for each class of aircraft are determined by an optimization procedure. In this fashion, the nominal approach routes are dependent upon and, hence, determined by the near terminal area operating capabilities of each class of aircraft. The landing order and spacing of aircraft on the common approach path are determined so that a measure of total system deviation from the nominal landing times is minimized and safety standards are met. Delay maneuvers required to satisfy sequencing needs are then carried out in a manner dependent upon the particular class of aircraft being maneuvered. Finally, results are presented to illustrate the effects of the rate of arrivals upon a one-runway system serving three different classes of aircraft employing several different sequencing strategies and measures of total system deviation.

Straeter, T. A.↗

NASA NTRS1989

Chronology of volcanism and rift basin propagation - Rungwe volcanic province, East Africa

The spatial and temporal development of along-axis segmentation in youthful continental rifts was investigated using the results of field, remote sensing, and K-Ar geochronology studies conducted in four (Rukwa, Songwe, Usangu, and Karonga) rift basins within the Rungwe volcanic province in East Africa. Results indicated that the Rukwa and Karonga border fault segments formed between 7.25 and 5 m.y. ago, the Usangu border fault segment developed between 3 and 2 m.y. ago, and subsidence along the Songwe border fault segment had occurred by 0.5 Ma. It is shown that individual basins developed diachronously, each following a similar sequence: (1) initial border fault development; (2) asymmetric basin subsidence/flank uplift and the development of monoclines opposite the border faults; and (3) continued subsidence and tilting along intrabasinal faults with flexural upwarping of the rift flanks, enhancing basinal asymmetries.

Ebinger, C. J.↗

NASA NTRS1976

A critical examination of the flap-lag dynamics of helicopter rotor blades in hover and in forward flight

A critical examination of flap-lag stability of a centrally hinged, spring-restrained rigid blade in both hover and forward flight is presented. Several differences in the equations of motion for blade flap-lag stability in the existing literature are identified. A rigorous and systematic development of these equations for a rigid articulated blade in forward flight shows the existence of some linear aerodynamic coupling terms associated with blade steady-state flapping and lagging in the perturbation equations. The differences identified are shown to be associated with the order in which the flap and lag transformations are taken in developing the equations of motion. The implications of these differences on stability are examined, and it is shown that the pitch-lag coupling terms associated with a flap-lag hinge transformation sequence have a marked influence on flap-lag stability. Some qualitative considerations on the role of the assumed transformation sequence in the development of the flap-lag equations for a hingeless elastic blade are also given. On the basis of these considerations, it is shown that aerodynamic coupling terms associated with blade steady-state flapping and lagging similar to those found for the rigid blade will also appear in the equations for the elastic blade.

Kaza, K. R. V.↗

NASA NTRS2017

Beyond Nanopore Sequencing in Space: Identifying the Unknown

Astronaut Kate Rubins sequenced DNA on the International Space Station (ISS) for the first time in August 2016 (Figure 1A). A 2D sequencing library containing an equal mixture of lambda bacteriophage, Escherichia coli, and Mus musculus was prepared on the ground with a SQK_MAP006 kit and sent to the ISS frozen and loaded into R7.3 flow cells. After a total of 9 on-orbit sequencing runs over 6 months, it was determined that there was no decrease in sequencing performance on-orbit compared to ground controls (1). A total of ~280,000 and ~130,000 reads generated on-orbit and on the ground, respectively, identified 90% of reads that were attributed to 30% lambda bacteriophage, 30% Escherichia coli, and 30% M. musculus (Figure 1B). Extensive bioinformatics analysis determined comparable 2D and 1D read accuracies between flight and ground runs (Figure 1C), and data collected from the ISS were able to construct directed assemblies of E.coli and lambda genomes at 100% and M. musculus mitochondrial genome at 96.7%. These findings validate sequencing as a viable option for potential on-orbit applications such as environmental microbial monitoring and disease diagnosis. Current microbial monitoring of the ISS applies culture-based techniques that provide colony forming unit (CFU) data for air, water, and surface samples. The identity of the cultured microorganisms in unknown until sample return and ground-based analysis, a process that can take up to 60 days. For sequencing to benefit ISS applications, spaceflight-compatible sample preparation techniques are required. Subsequent to the testing of the MinION on-orbit, a sample-to-sequence method was developed using miniPCR™ and basic pipetting, which was only recently proven to be effective in microgravity. The work presented here details the in- flight sample preparation process and the first application of DNA sequencing on the ISS to identify unknown ISS-derived microorganisms.

Stahl, Sarah E.↗

NASA NTRS2018

The OpenSE Cookbook: A Practical, Recipe Based Collection of Patterns, Procedures, and Best Practices for Executable Systems Engineering for the Thirty Meter Telescope

The OpenSE Cookbook is an open-sourced collection of patterns, procedures, and best practices targeted for systems engineers who seek guidance on applying model-based and executable systems engineering (MBSE) using SysML. Its content has emerged from the system level modeling effort on the European Framework Program 6 (FP6) and the Thirty Meter Telescope (TMT). The TMT MBSE approach applied the Executable Systems Engineering Method (ESEM) and the open-source Engineering Environment (OpenMBEE) to specify, analyze, and verify requirements of TMT’s Alignment and Phasing System (APS) and the Narrow Field Infrared Adaptive Optics System (NFIRAOS). In these applications, implicit dependencies are made explicit in a formal model through the use of ESEM, OpenMBEE, and SysML modeling constructs. The value proposition for applying this MBSE approach was to establish precise requirements and fine-grained traceability to system designs, and to verify key requirements beginning early in development. The integration of ESEM and the OpenMBEE tooling infrastructure (providing linked-data and web-operability) is a significant added value for the MBSE approach. The APS is responsible for the overall pre-adaptive optics wavefront quality, using starlight to measure wavefront errors and align the TMT optics. In the formally integrated and executable SysML model, simulations are performed to analyze the impact of changed requirements and verify specified constraints for various operational scenarios. The APS team used several modeling patterns to capture information such as the requirements, the operational scenarios, involved subsystems and their interaction points, the estimated or required time durations, and the mass and power consumption. Adaptive optics systems are designed to sense real-time atmospheric turbulence and correct the telescope’s optical beam to remove its effect. The system model for the adaptive optics operational modes was developed to capture sequence behaviors and operational scenarios to run Monte-Carlo simulations for verifying acquisition time, observing efficiency, and operational behavior requirements. The model is particularly useful for investigating the effect of parallelization, identifying interface issues, and re-ordering sequence acquisition tasks. A former version of the Cookbook (which is now updated to MBSE challenges, goals, and lessons learned) included modeling guidelines and conventions for all system aspects, hierarchy levels, and views, which were developed during for the Active Phasing Experiment (APE), an opto-mechatronical system technology demonstrator for the Extremely Large Telescope (ELT). The Cookbook utilizes the above mentioned system models as real-world case-studies to demonstrate and document the applications of the recipes, providing also instructional examples and addressing the available tooling support. The Cookbook is accompanied by a number of SysML models and aodel libraries which facilitate model authoring and maintenance. The Cookbook covers the different aspects of Systems Engineering such as management of Requirements, Design (behavior and structure), Interfaces, Interdisciplinary Integration, Analysis, Trade Studies, and Technical Resources. This paper presents the background, motivation, architecture, and highlights some key content of the Cookbook. For example, interface management, error budget management, requirements verification, Monte Carlo driven analysis, and timing analysis of operational scenarios. The paper discusses how the capabilities of OpenMBEE contributed significantly to the adoption of executable systems engineering.

Brower, Eric↗

NASA NTRSDate not supplied

Design for Reliability (DfR) in Space Life Support

The engineering process of Design for Reliability (DfR) is well established in the automotive and aerospace industries. DfR should be useful in the future development of space life support systems. DfR is a sequence of tasks that develop system requirements and plan reliability analysis and testing. First and fundamentally, the reliability requirement is defined. Next the system reliability model is developed, often using a reliability block diagram. The overall system reliability requirement is allocated to the subsystems and an estimate of the attainable reliability is made. This expected reliability can be improved by simplifying the design by removing components or by replacing less reliable components. Improving reliability can require difficult compromises, such as reducing performance requirements, increasing budget, or extending testing. The actual system reliability can be determined only by testing, which should continue long enough to provide the required confidence in the measured value. New systems often have unexpected design errors that cause failures in early testing. The usual reliability improvement process of testing, finding the failure modes, and redesigning to remove them reduces the failure rate and is referred to as “reliability growth.” After redesign has been completed, the system should be further tested to determine the actual achieved reliability more accurately. If the final system failure rate is too high, redundant systems can be used to improve overall operational reliability. Adding redundancy simply to increase the one- or two-fault tolerance metric may sometimes reduce reliability. Reliability can be improved in three ways: redesigning the system to include more reliable subsystems and components, reliability growth testing and failure mode removal, and by using parallel redundant systems. DfR should combine these approaches to achieve the required reliability while managing performance, cost, and schedule.

Reliability↗