SEARCH · Engineering Papers

Results for “execution time”

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 937 records · Page 52

All sources NASA NTRS DOE OSTI

NASA NTRS2004

High-Fidelity Full System Simulations

High-fidelity full system simulations have the potential for revolutionizing the way complex systems, such as propulsion systems for aerospace vehicles, are designed, developed, manufactured, and operated. Significant time and cost savings will result from simulations that will resolve deleterious component interactions early in the design process. In addition, innovative new system configurations will result from the use of new tools that enable designers to challenge traditional rules and practices. The major challenges to developing and implementing high-fidelity systems simulations are in reducing the time and effort required to build, execute, and analyze data for the high complex simulations. In addition, large scale testing with unique instrumentation is required to validate the simulations. The solution to these problems reside in the application of advanced information technologies to assist the user to effectively manage, process, and synthesize the vast amount of data. The following presentation describes in more detail the benefits of high-fidelity full system simulations, the challenges to developing and implementing large scale simulations, and one approach that is being followed by the NASA Glenn Research Center to overcome these challenges. In addition, topics for discussion by the panel and audience are suggested.

Lytle, John K.↗

NASA NTRS2007

Community Coordinated Modeling Center Support of Operations: Real-Time Simulations and V & V.

In support of Operations Community Coordinated Modeling Center (CCMC) performing validation and verification of space weather models. To identify suitable metrics the CCMC focus on parameters most useful to operations that CCMC resident models can provide. The real time simulations carried out at CCMC are an essential tool to test model performance and stability by using input conditions that may occur in nature at any time. Since 2001, the magnetospheric MHD model BATSRUS has been run in real time using ACE real time data. CCMC staff developed an experimental real-time system that controls uploading of the real-time ACE data, monitors continuous model execution, initiates automatic recovery procedure in case of data gaps or hardware failures, synchronizes BATSRUS and FRC runs, and periodically runs IDL based visualization software.

Kuznetsova, M.↗

NASA NTRS2011

SpaceCube 2.0: An Advanced Hybrid Onboard Data Processor

The SpaceCube 2.0 is a compact, high performance, low-power onboard processing system that takes advantage of cutting-edge hybrid (CPU/FPGA/DSP) processing elements. The SpaceCube 2.0 design concept includes two commercial Virtex-5 field-programmable gate array (FPGA) parts protected by gradiation hardened by software" technology, and possesses exceptional size, weight, and power characteristics [5x5x7 in., 3.5 lb (approximately equal to 12.7 x 12.7 x 17.8 cm, 1.6 kg) 5-25 W, depending on the application fs required clock rate]. The two Virtex-5 FPGA parts are implemented in a unique back-toback configuration to maximize data transfer and computing performance. Draft computing power specifications for the SpaceCube 2.0 unit include four PowerPC 440s (1100 DMIPS each), 500+ DSP48Es (2x580 GMACS), 100+ LVDS high-speed serial I/Os (1.25 Gbps each), and 2x190 GFLOPS single-precision (65 GFLOPS double-precision) floating point performance. The SpaceCube 2.0 includes PROM memory for CPU boot, health and safety, and basic command and telemetry functionality; RAM memory for program execution; and FLASH/EEPROM memory to store algorithms and application code for the CPU, FPGA, and DSP processing elements. Program execution can be reconfigured in real time and algorithms can be updated, modified, and/or replaced at any point during the mission. Gigabit Ethernet, Spacewire, SATA and highspeed LVDS serial/parallel I/O channels are available for instrument/sensor data ingest, and mission-unique instrument interfaces can be accommodated using a compact PCI (cPCI) expansion card interface. The SpaceCube 2.0 can be utilized in NASA Earth Science, Helio/Astrophysics and Exploration missions, and Department of Defense satellites for onboard data processing. It can also be used in commercial communication and mapping satellites.

Lin, Michael↗

NASA NTRS2011

Exploration Planetary Surface Structural Systems: Design Requirements and Compliance

The Lunar Surface Systems Project developed system concepts that would be necessary to establish and maintain a permanent human presence on the Lunar surface. A variety of specific system implementations were generated as a part of the scenarios, some level of system definition was completed, and masses estimated for each system. Because the architecture studies generally spawned a large number of system concepts and the studies were executed in a short amount of time, the resulting system definitions had very low design fidelity. This paper describes the development sequence required to field a particular structural system: 1) Define Requirements, 2) Develop the Design and 3) Demonstrate Compliance of the Design to all Requirements. This paper also outlines and describes in detail the information and data that are required to establish structural design requirements and outlines the information that would comprise a planetary surface system Structures Requirements document.

Dorsey, John T.↗

NASA NTRS2018

A Pilot Study to Determine MBSE Utility for Process Modeling of Complex Interfaces

Modeling a full system or a complete interface between systems in a MBSE environment is a very large task and not all organizations will benefit enough from using MBSE to offset the effort that is required to do this. Completely modeling a system or interface is not necessary to evaluate the utility of MBSE for a specific application or organization. A small pilot can be executed over a short period of time that only models small portions of a system or interface and, if structured properly, this pilot can successfully demonstrate the utility of MBSE for an organization before having to invest a larger amount of resources to fully implement and deploy MBSE. This paper documents one such pilot that was conducted for NASA’s Launch Services Program.

MBSE↗

NASA NTRS2018

A Pilot Study to Determine MBSE Utility for Process Modeling of Complex Interfaces

MBSE↗

NASA NTRS2018

A Pilot Study to Determine MBSE Utility for Process Modeling of Complex Interfaces

MBSE↗

NASA NTRS2016

Overview of Sense and Avoid/Separation Assurance Interoperability (SSI)

The UAS in the NAS project is studying the minimum operational performance standards for unmanned aerial systems (UAS's) detect-and-avoid (DAA) system in order to operate in the National Airspace System. The project is executing a series of fast-time simulation, human-in-the-loop experiments, and flight test in support of this effort. Officials of the Swiss Government (Peter Winter, Director of Aeronautical Systems, and Michel Godinat, Head of the Certification Office) are visiting NASA to become more familiar with the advances being made to integrate UAS into civilian airspace. This briefing will review the activities and results over the past 3 years within the Separation AssuranceSense-and-Avoid Interoperability team.

Santiago, Confesor↗

NASA NTRS2016

Simulation and Flight Test Data Collection to Support Phase 1 Detect-and-Avoid MOPS

The UAS Integration into the NAS (UASNAS) project is studying the minimum operational performance standards for unmanned aerial system (UAS) detect-and-avoid (DAA) systems in order to operate in the National Airspace System (NAS). The project is executing a series of fast-time simulation, human-in-the-loop experiments, and flight tests in support of this effort. Armstrong Flight Research Center is hosting a VIP Day in conjunction with the UAS-NAS Project's Flight Test 4 activity, and the Ames Project Engineer (or designate) will be presenting a briefing. This briefing will review the data collection and analysis activities for Flight Test 4 within the Separation assurance-Sense-and-avoid Interoperability (SSI) team.

data analysis↗

NASA NTRS2016

Simulation and Flight Test Data Collection Review for Supporting Phase 1 Detect and Avoid MOPS

RTCA Special Committee 228 is a consortium of government, industry, and academic organizations tasked to develop minimum operational performance standards for UAS detect and avoid systems. The UAS in the NAS (National Airspace System) project is studying the minimum operational performance standards for unmanned aerial systems (UAS's) detect-and-avoid (DAA) system in order to operate in the National Airspace System. Over the past 3 years, the project has executed a series of fast-time simulation, human-in-the-loop experiments, and flight tests in support of this effort. The purpose of this briefing is to summarize the models developed and data collected to overcome UAS integration barriers, so UAS can remain well clear of all traffic.

Santiago, Confesor↗

NASA NTRS1999

An Integrated Architecture for Cooperation Rovers

The paper presents a rover execution architecture for controlling multiple, cooperating rovers. The overall goal of this architecture is to coordinate multiple rovers in performing complex tasks for planetary science.

multi-rover↗

NASA NTRS1985

Planning fuel-conservative descents in an airline environmental using a small programmable calculator: Algorithm development and flight test results

A simple, airborne, flight-management descent algorithm was developed and programmed into a small programmable calculator. The algorithm may be operated in either a time mode or speed mode. The time mode was designed to aid the pilot in planning and executing a fuel-conservative descent to arrive at a metering fix at a time designated by the air traffic control system. The speed model was designed for planning fuel-conservative descents when time is not a consideration. The descent path for both modes was calculated for a constant with considerations given for the descent Mach/airspeed schedule, gross weight, wind, wind gradient, and nonstandard temperature effects. Flight tests, using the algorithm on the programmable calculator, showed that the open-loop guidance could be useful to airline flight crews for planning and executing fuel-conservative descents.

Knox, C. E.↗

NASA NTRSDate not supplied

Improvements to Stitching Controls for Manufacturing Advanced Stitched Composites

Stitched composites have been extensively studied and have been shown to have benefits over unstitched composites for stiffened structures, including improved damage tolerance, reduced weight, and fewer fasteners. These benefits make stitched composites attractive from a performance perspective, however, the nature of stitching the preforms prior to infusion includes additional manufacturing steps and equipment compared to conventional resin infusion. Stitching of composite material structures at NASA Langley Research Center (LaRC) is performed at the Integrated Structural Assembly of Advanced Composites (ISAAC) facility using control algorithms developed by the lead author. Two deficiencies have been identified in the current control algorithms, and mitigations for these deficiencies were developed within the Hi-Rate Composite Aircraft Manufacturing (HiCAM) project and are presented herein. First, decoupling stitch translation and rotation takes more time for stitching since two robot operation control steps are executed for each stitch. Therefore, a method was developed to determine when to decouple the translation and rotation for stitching, which reduces stitch time by decoupling the operation control steps only when necessary to execute the stitch properly. Second, a correction to the sideslip stitching approach that eliminates a significant portion of the pre- and post-stitching activities was developed. The developed method adjusts the sideslip stitch angle based on the rotations of previous stitches to ensure that the width of the stitching seam remains constant along its length. Constant seam width eliminates observed overlap of the insertion and catcher thread portions for highly curved paths, which maintains the desired uniformity of through-the-thickness architecture along the seam and eliminates the local degradation of properties where the insertion needle is too close to, or crosses, the catcher needle portion of the seam.

stitching↗

NASA NTRS2010

Portable Health Algorithms Test System

A document discusses the Portable Health Algorithms Test (PHALT) System, which has been designed as a means for evolving the maturity and credibility of algorithms developed to assess the health of aerospace systems. Comprising an integrated hardware-software environment, the PHALT system allows systems health management algorithms to be developed in a graphical programming environment, to be tested and refined using system simulation or test data playback, and to be evaluated in a real-time hardware-in-the-loop mode with a live test article. The integrated hardware and software development environment provides a seamless transition from algorithm development to real-time implementation. The portability of the hardware makes it quick and easy to transport between test facilities. This hard ware/software architecture is flexible enough to support a variety of diagnostic applications and test hardware, and the GUI-based rapid prototyping capability is sufficient to support development execution, and testing of custom diagnostic algorithms. The PHALT operating system supports execution of diagnostic algorithms under real-time constraints. PHALT can perform real-time capture and playback of test rig data with the ability to augment/ modify the data stream (e.g. inject simulated faults). It performs algorithm testing using a variety of data input sources, including real-time data acquisition, test data playback, and system simulations, and also provides system feedback to evaluate closed-loop diagnostic response and mitigation control.

Melcher, Kevin J.↗

NASA NTRS1998

A Hybrid Procedural/Deductive Executive for Autonomous Spacecraft

The New Millennium Remote Agent (NMRA) will be the first AI system to control an actual spacecraft. The spacecraft domain places a strong premium on autonomy and requires dynamic recoveries and robust concurrent execution, all in the presence of tight real-time deadlines, changing goals, scarce resource constraints, and a wide variety of possible failures. To achieve this level of execution robustness, we have integrated a procedural executive based on generic procedures with a deductive model-based executive. A procedural executive provides sophisticated control constructs such as loops, parallel activity, locks, and synchronization which are used for robust schedule execution, hierarchical task decomposition, and routine configuration management. A deductive executive provides algorithms for sophisticated state inference and optimal failure recover), planning. The integrated executive enables designers to code knowledge via a combination of procedures and declarative models, yielding a rich modeling capability suitable to the challenges of real spacecraft control. The interface between the two executives ensures both that recovery sequences are smoothly merged into high-level schedule execution and that a high degree of reactivity is retained to effectively handle additional failures during recovery.

Pell, Barney↗

DOE OSTI2023

Evolution of Energy Efficiency Programs Over Time: The Case of Standby Power

Issued in 2001, Presidential Executive Order 13221 directed federal agencies to purchase products with low standby power, with the goal of 1) reducing energy consumption in federal facilities, and 2) drawing attention to the problem of high standby power consumption, with guidance provided by the Federal Energy Management Program (FEMP). At that time, standby power was newly recognized as an increasing building energy load. Since then, procurement of products with low standby power have been set in place in acquisition processes, and the purchasing power of the federal government continues to influence manufacturers’ design decisions related to standby power. In recent years, FEMP has shifted effort from direct manufacturer outreach for data collection, to integrating low standby requirement into broader acquisition programs including Energy Star and Electronic Product Environmental Assessment Tool (EPEAT). Another milestone has been the labeling of low standby products on the GSA Advantage website to simplify and enhance compliance. Looking forward into the program’s future, this question arises “How do we design programs over time to reflect market and technology changes, by adjusting programmatic requirements while maintaining effectiveness?” This paper discusses that question for the case of standby power, which transitioned from covering a single to multiple environmental attributes, both in the context of the program’s past and future.

Payne, CT↗

NASA NTRS2012

A Geometric Analysis to Protect Manned Assets from Newly Launched Objects - COLA Gap Analysis

A safety risk was identified for the International Space Station (ISS) by The Aerospace Corporation following the launch of GPS IIR-20 (March 24, 2009), when the spent upper stage of the launch vehicle unexpectedly crossed inside the ISS notification box shortly after launch. This event highlighted a 56-hour vulnerability period following the end of the launch Collision Avoidance (COLA) process where the ISS would be unable to react to a conjunction with a newly launched object. Current launch COLA processes screen each launched object across the launch window to determine if an object's nominal trajectory is predicted to pass within 200 km of the ISS (or any other manned/mannable object), resulting in a launch time closure. These launch COLA screens are performed from launch through separation plus I 00 minutes. Once the objects are in orbit, they are cataloged and evaluated as part of routine on-orbit conjunction assessment processes. However, as the GPS IIR-20 scenario illustrated, there is a vulnerability period in the time line between the end of launch COLA coverage and the beginning of standard on-orbit COLA assessment activities. The gap between existing launch and on-orbit COLA processes is driven by the time it takes to track and catalog a launched object, identify a conjunction, and plan and execute a collision avoidance maneuver. For the ISS, the total time required to accomplish an of these steps is 56 hours. To protect human lives, NASA/JSC has requested that an US launches take additional steps to protect the ISS during this "COLA gap" period. The uncertainty in the state of a spent upper stage can be quite large after all bums are complete and all remaining propellants are expelled to safe the stage. Simply extending the launch COLA process an additional 56 hours is not a viable option as the 3-sigma position uncertainty will far exceed the 200 km miss-distance criterion. Additionally, performing a probability of collision (Pc) analysis over this period is also not practical due to the limiting effects of these large orbit state uncertainties. An estimated upper bound for Pc for a typical spent upper stage if nominally aligned for a direct broadside collision with the ISS is only on the order of 10-6. For a smaller manned object such as a Soyuz capsule, the risk level decreases to an order of 10'8 . In comparison, the Air Force Range policy (AFI 91-217) for launch COLAs would only eliminate launch opportunities when conjunctions with objects exceed a Pc of 10'5 This paper demonstrates a conservative geometry-based methodology that may be used to determine if launch opportunities pose a threat to the ISS during the COLA gap period. The NASA Launch Services Program at Kennedy Space Center has developed this COLA gap analysis method and employed it fQr three NASA missions to identify potential ISS conjunctions and corresponding launch window closures during the 56-hour at-risk period. In the analysis, for each launch opportunity, the nominal trajectory of the spent upper stage and the orbit state of the ISS are propagated over the 56 hour period. Each time the upper stage crosses the orbit plane of the ISS, the relative radial and argument of latitude separations are calculated. A window cutout is identified if these separation differences fall within a mission-specific violation box, which is determined from the evaluation of a Monte Carlo dispersions analysis that quantifies the potential variation in the upper stage radial and argument of latitude differences. This paper details the results of these analyses and their impacts to each mission.

Hametz, Mark E.↗

NASA NTRS2005

The NASA Exploration Design Team; Blueprint for a New Design Paradigm

NASA has chosen JPL to deliver a NASA-wide rapid-response real-time collaborative design team to perform rapid execution of program, system, mission, and technology trade studies. This team will draw on the expertise of all NASA centers and external partners necessary. The NASA Exploration Design Team (NEDT) will be led by NASA Headquarters, with field centers and partners added according to the needs of each study. Through real-time distributed collaboration we will effectively bring all NASA field centers directly inside Headquarters. JPL's Team X pioneered the technique of real time collaborative design 8 years ago. Since its inception, Team X has performed over 600 mission studies and has reduced per-study cost by a factor of 5 and per-study duration by a factor of 10 compared to conventional design processes. The Team X concept has spread to other NASA centers, industry, academia, and international partners. In this paper, we discuss the extension of the JPL Team X process to the NASA-wide collaborative design team. We discuss the architecture for such a process and elaborate on the implementation challenges of this process. We further discuss our current ideas on how to address these challenges.

Team X↗