Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “TRAJECTORIES”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

Rapid Preliminary Design of Interplanetary Trajectories Using the Evolutionary Mission Trajectory Generator

This set of tutorial slides is an introduction to the Evolutionary Mission Trajectory Generator (EMTG), NASA Goddard Space Flight Center's autonomous tool for preliminary design of interplanetary missions. This slide set covers the basics of creating and post-processing simple interplanetary missions in EMTG using both high-thrust chemical and low-thrust electric propulsion along with a variety of operational constraints.

optimization↗
NASA NTRS2015

Modeling of Complex and Diverse Aircraft Trajectories with the Trajectory Synthesizer Generalized Profile Interface

A flexible method to describe and generate aircraft trajectories called GenProf was developed for the Center TRACON Automation System (CTAS) software research platform. Generally CTAS is used to prototype new air traffic management decision support tools and concepts. Beyond this purpose, the GenProf methodology has enabled a variety of research and validation tasks to be performed. This paper briefly describes the methodology and details these applications.

trajectory modelling↗
NASA NTRS1988

Trajectory computation during a maneuver: Thrust estimation with the Goddard Trajectory Determination System (GTDS)

Existing thrust modeling capabilities of the Goddard Trajectory Determination System (GTDS) have been enhanced to allow calibration of the onboard propulsion system. These enhancements provide one or more thrust scale factors, based on estimation using the batch least-squares technique, for the case of along-track thrust and the case of attitude-dependent thrust. The enhancements are evaluated using simulated tracking measurements for a test spacecraft and using actual tracking measurements for the Earth Radiation Budget Satellite (ERBS). The effects of tracking measurement noise and distribution on the accuracy of the estimation are investigated and found to be significant. Results and conclusions of the analysis are presented.

Beri, A. C.↗
NASA NTRS1993

MASTRE trajectory code update to automate flight trajectory design, performance predictions, and vehicle sizing for support of shuttle and shuttle derived vehicles: Programmers manual

The information required by a programmer using the Minimum Hamiltonian AScent Trajectory Evaluation (MASTRE) Program is provided. This document enables the programmer to either modify the program or convert the program to computers other than the VAX computer. Documentation for each subroutine or function based on providing the definitions of the variables and a source listing are included. Questions concerning the equations, techniques, or input requirements should be answered by either the Engineering or User's manuals. Three appendices are also included which provide a listing of the Root-Sum-Square (RSS) program, a listing of subroutine names and definitions used in the MASTRE User Friendly Interface Program, and listing of the subroutine names and definitions used in the Mass Properties Program. The RSS Program is used to aid in the performance of dispersion analyses. The RSS program reads a file generated by the MASTRE Program, calculates dispersion parameters, and generates output tables and output plot files. UFI Program provides a screen user interface to aid the user in providing input to the model. The Mass Properties Program defines the mass properties data for the MASTRE program through the use of user interface software.

Source record↗
NASA NTRS2007

NASA's Core Trajectory Sub-System Project: Using JBoss Enterprise Middleware for Building Software Systems Used to Support Spacecraft Trajectory Operations

NASA's Johnson Space Center (JSC) / Flight Design and Dynamics Division (DM) has prototyped the use of Open Source middleware technology for building its next generation spacecraft mission support system. This is part of a larger initiative to use open standards and open source software as building blocks for future mission and safety critical systems. JSC is hoping to leverage standardized enterprise architectures, such as Java EE, so that its internal software development efforts can be focused on the core aspects of their problem domain. This presentation will outline the design and implementation of the Trajectory system and the lessons learned during the exercise.

Stensrud, Kjell C.↗
NASA NTRS2014

Definition ofthe Design Trajectory and Entry Flight Corridor for the NASA Orion Exploration Mission 1 Entry Trajectory Using an Integrated Approach and Optimization

One of the key design objectives of NASA's Orion Exploration Mission 1 (EM- 1) is to execute a guided entry trajectory demonstrating GN&C capability. The focus of this paper is defining the flyable entry corridor for EM-1 taking into account multiple subsystem constraints such as complex aerothermal heating constraints, aerothermal heating objectives, landing accuracy constraints, structural load limits, Human-System-Integration-Requirements, Service Module debris disposal limits and other flight test objectives. During the EM-1 Design Analysis Cycle 1 design challenges came up that made defining the flyable entry corridor for the EM-1 mission critical to mission success. This document details the optimization techniques that were explored to use with the 6-DOF ANTARES simulation to assist in defining the design entry interface state and entry corridor with respect to key flight test constraints and objectives.

McNamara, Luke W.↗
NASA NTRSDate not supplied

End-to-End Trajectory Optimization Using Copernicus and Program to Optimize Simulated Trajectories II

As current and future NASA missions become increasingly more complex, the need to ensure requirements are met across the many phases of flight is more pertinent. Accurately modeling the individual phases of flight is difficult alone, but verifying that the overall mission is characterized properly presents additional challenges. In previous works, there have been successful demonstrations of interfacing multiple software applications to provide a more detailed end-to-end optimized simulation. The work herein will focus on leveraging two NASA built tools that have been successfully utilized on NASA missions: Copernicus and the Program to Optimize Simulated Trajectories II (POST2).

Anthony Williams↗
NASA NTRS2017

Flight Deck Surface Trajectory-Based Operations (STBO): A Four-Dimensional Trajectory (4DT) Simulation

Within human factors there is burgeoning interest in the Human-Autonomy Teaming (HAT) concept as away to address the challenges of interacting with complex, increasingly autonomous systems. The HAT concept comes out of an aspiration to interact with increasingly autonomous automation as a team member, rather than simply use automation as a tool. The authors, and others, have proposed core tenets for HAT that include bi-directional communication, automation and system transparency, and advanced coordination between human and automated teammates via predefined, dynamic task sequences known as plays (Shively et al., 2017). It is believed that, with proper implementation, HAT should foster appropriate teamwork, thus increasing trust and reliance on the system, which in turn will reduce workload, increase situation awareness, and improve performance. To this end, HAT has been demonstrated and/or studied in multiple applications including search and rescue operations (Nourbakhsh et al., 2005), healthcare and medicine (Tsui Yanco, 2007), autonomous vehicles (Parasuraman, Barnes, Cosenzo, Mulgund, 2007), photography (Lachter, Brandt, Sadler, Shively, in press), and aviation (Shively et al., in press). The current paper presents one such effort to apply HAT. It details the design of a R-HAT Agent developed as part of a NASA Research Agreement awarded to Human-Autonomy Teaming Solutions Inc. (HATS Inc), and developed in collaboration with the Human-Autonomy Teaming Laboratory at NASA Ames Research Center. The role of this Agent is to mediate interaction between the automation and the human operator of an advanced ground dispatch station, with this mediation based upon previously mentioned core tenets for HAT and the many lessons learned from the HAT research literature. This dispatch station was developed to support a NASA project investigating a concept called Reduced Crew Operations (RCO; Lachter, Brandt, Battiste, Matessa, Johnson, in press). Part of the RCO concept involves a ground operator providing enhanced support to a large number of aircraft with a single pilot on the flight deck. When assisted by the Agent, operators can monitor and support or manage a large number of aircraft and use plays to respond in real-time to complicated, workload-intensive events (e.g., an airport closure). A play is a plan that encapsulates goals, tasks, and a task allocation strategy appropriate for a particular situation. In the current implementation, when a play is initiated by a user, the Agent determines what tasks need to be done and has the ability to autonomously execute them (e.g., determining diversion options and uplinking new routes to aircraft) when it is safe and appropriate. The R-HAT Agent has been designed to both support end users and research in RCO and HAT. Additionally, the Agent and its underlying architecture were developed with generalizability in mind as a modular piece of software applicable outside of RCO aviation in domains such as those mentioned above. This paper will also discuss future further development and testing of the R-HAT Agent.

Bakowski, Deborah L.↗
NASA NTRS2018

Concept of Operations for Management by Trajectory

This document describes Management by Trajectory (MBT), a concept for future air traffic management (ATM) in which every flight operates in accordance with a four-dimensional trajectory (4DT) that is negotiated between the airspace user and the Federal Aviation Administration (FAA) to respect the airspace user's goals while complying with National Airspace System (NAS) constraints. In the present-day NAS, the ATM system attempts to predict the trajectory for each flight based on the approved flight plan and scheduled or controlled departure time. However, once the aircraft starts to move, controllers tactically manage the aircraft to implement traffic management restrictions, separate otherwise conflicting aircraft, and address arising NAS constraints. Tactical controller actions are not directly communicated to the automation systems or other stakeholders. Furthermore, the initial trajectory prediction does not anticipate these disruptions or how they will impact the flight. Consequently, and compounded by gaps in required data and models, trajectory predictions are less accurate than possible, which affects Traffic Flow Management (TFM) performance. A cornerstone of the MBT concept is that all air vehicles have, at all times, an assigned 4DT from their current state to their destination. These assigned trajectories consist of trajectory constraints and descriptions. Pilots and air traffic controllers, with the aid of automation, operate the aircraft to comply with the assigned trajectory, unless first negotiating a revision. Equipped aircraft have substantial responsibility for complying with the assigned trajectory without controller intervention. To maximize the operational flexibility available to the airspace user, the assigned trajectory only imposes trajectory constraints as required to achieve the ATM goals of NAS constraint compliance and aircraft separation. Trajectory descriptions are added to the assigned trajectory to ensure sufficient predictability. To further improve trajectory prediction accuracy, airspace users supplement the assigned trajectory by broadcasting intent information and updating it as necessary. Air vehicle intent is a more detailed description of the airspace user's plan for how the flight will fly the assigned trajectory. Air vehicle intent can change freely, without negotiation, as long as it remains in compliance with the assigned trajectory. Aircraft assigned trajectories, air vehicle intent, and predicted trajectories are shared, creating a common view among stakeholders. A NAS Constraint Service gathers and publishes information about all known NAS constraints, enabling airspace users to be informed participants in trajectory negotiation. Trajectory constraints in the assigned trajectory are mapped to NAS constraints to facilitate identifying which aircraft are affected when NAS constraints change. To support efficient trajectory negotiation, all aircraft provide current information about air vehicle capabilities. Assigned trajectories are constructed to satisfy all known NAS constraints, improving trajectory stability and predictability. Uncertainty and disruptions are handled by modifying the assigned trajectory as far in advance as possible. By proactively negotiating changes to the assigned trajectory, rather than relying on controller-selected tactical actions such as vectors to resolve traffic conflicts or implement miles-in-trail restrictions, MBT keeps aircraft on closed trajectories that are fully known to all stakeholders. Since reactive air traffic control actions cannot be predicted in advance, the downstream trajectory cannot be accurately predicted until they happen. Reliable trajectory predictions allow the system to identify needed modifications to trajectories further in advance, where they can be negotiated and communicated as amendments (i.e., additional or altered trajectory constraints) to the assigned trajectory. Decision Support Tools (DSTs) aid controllers in rapidly defining and communicating closed trajectories to the aircraft and support all stakeholders in trajectory negotiation. Anticipated MBT benefit mechanisms include more accurate trajectory predictions, improved ATM performance and robustness to off-nominal conditions, increased flexibility and operational efficiency, reduced impediments to emerging classes of airspace users accessing NAS resources, reduced environmental impacts, and enhanced safety.

ConOps↗