Search NASASearch

Engineering topics

Jacob Williams

Publications and source records attributed to Jacob Williams.

End-to-End Mission Design & Trajectory Optimization

Need: A need exists for a generalized, robust, user-friendly and accessible end-to-end mission design optimization tool. Solution: Our solution to developing this capability was to interface two JSC tools—Copernicus and Genesis. Each of these tools has a specific area of the mission design process that it excels at. By utilizing them both, we can gain performance benefits not seen by either on their own. - Copernicus is a trajectory design and optimization software used for in-space trajectories around multiple bodies. - Genesis is a flight mechanics tool used to model ascent, entry, descent, and landing trajectories around a single planetary body. Year 1 was focused on combining these 2 software packages—allowing Copernicus to incorporate the ascent/descent capabilities of Genesis into the optimization problem—and developing this end-to-end mission design capability. Year 2 we focused on increasing the robustness of this capability by building the initial guess generator (IGG), which produces initial guesses based on simplifying assumptions and the physics of the problem. Year 3 of our project focused on utilizing the end-to-end mission design and optimization capabilities developed in the previous 2 years to analyze specific mission scenarios—scaling up from proof of concept to real analyses—capturing any resulting performance benefits, as well as addressing the Big Data challenges we’re faced with—namely, how we’re going to manage and interpret all the data that’s generated.

Kristin Nichols

Executive Summary for CIF22 Project: End-to-End Mission Design & Trajectory Optimization

The goal of this project was the integration of NASA's Copernicus and Genesis trajectory design tools to create a new capability for end-to-end mission design and optimization of all flight phases, including Earth ascent, lunar ascent, rendezvous, and lunar descent. This capability is a critical component needed for the next generation of complex human spaceflight design and operations (Orion, HLS, Gateway, Mars) and can serve as a pathfinder for developing a future autonomous, onboard trajectory optimizer. The result was the creation of a new Copernicus/Genesis plugin, which allows a Genesis trajectory (e.g., ascent or descent) to be incorporated into a Copernicus mission, enabling an end-to-end optimization. Inputs from Copernicus are sent to Genesis, which runs and produces output sent back to Copernicus. Thus, the full power of the Genesis tool is available in Copernicus and can be used for a wide variety of applications.

Jacob Williams

Copernicus Spacecraft Trajectory Design and Optimization Program

Copernicus is a spacecraft trajectory design and optimization application developed at the NASA Johnson Space Center. Copernicus is written in Fortran and uses many features of the latest language standards. The tool is used for a wide range of projects at NASA, including the upcoming Artemis missions to flight test the Orion spacecraft and then return humans to the Moon. This presentation gives a brief overview of the software, its history, how it was designed, and how it is used.

Copernicus

Multi-Impulse to Time Optimal Finite Burn Trajectory Conversion

A novel algorithm is presented that provides an improvement over a traditional parameter optimization method when solving time-optimal, finite-burn pseudo-rendezvous spacecraft trajectory problems. A hybrid optimization procedure is described that converts a set of multiple-impulses, representing high- or low-thrust maneuvers, to an exact time-optimal finite-burn trajectory for a thrust limited, constant exhaust velocity spacecraft. The Hybrid Method applies a control law derived from the Euler-Lagrange system of equations within the classical Indirect Method to a modern Direct Method. An iterative adjoint-control transformation and an evolving constraint vector are introduced to solve the optimal control two-point boundary value problem. This method requires no prior knowledge of the solution, which adds simplicity to the trajectory design process and aids automation. Examples are shown for low-thrust apogee raise maneuvers, non-coplanar Earth orbit transfers, and a modified Deep Space 1 low-thrust trajectory. A numerically significant improvement to objective cost is shown across all application problems compared to a traditional solution method, as well as a significant improvement to convergence speed for a select class of problems.

Joshua A Fogel

Artemis I Trajectory Design and Optimization

This paper presents the overall trajectory design and optimization process for NASA’s Artemis I mission to send an uncrewed Orion vehicle to a lunar Distant Retrograde Orbit (DRO). The on-orbit trajectory begins at the Space Launch System (SLS) core separation and ends at the Orion service module Earth Entry Interface (EI) point. The details of the trajectory optimization process are presented, including design of nominal and extended mission options, launch windows, and abort options. Novel design techniques are also discussed to account for contingencies, such as using auxiliary thrusters to protect against main engine failure and applying trajectory shaping to mitigate or reduce eclipse durations.

Artemis I

End-to-End Mission Design & Trajectory Optimization

The ability to compute end-to-end mission optimized trajectories is a critical component needed for the next generation of complex human spaceflight design and operations (Orion, HLS, Gateway, Mars). This project created a new interface for two of NASA’s trajectory tools: Copernicus and Genesis, enabling them to be used together for end-to-end mission design and optimization of all flight phases, including Earth ascent, lunar ascent, rendezvous, and lunar descent. This capability can also serve as a pathfinder for developing a future autonomous, onboard trajectory optimizer.

Software

Artemis I Off-Nominal-Trajectory Design and Optimization

In order to achieve the Artemis I mission objectives to human-rate the Orion spacecraft even under off-nominal conditions, trajectories were developed to handle contingency scenarios: alternate missions for contingencies before or during the Trans-Lunar Injection burn, recoveries to return Orion to the nominal trajectory after a delayed or partial burn, and abort trajectories to return the spacecraft to Earth after a critical failure. In addition, disposal trajectories were generated for situations where recovery was not an option. Details are given on the trajectory characteristics, solution families, the generation of the trajectories, and operations considerations.

Artemis I

A History of Orion Mission Design, Copernicus Software Development, and the Artemis I Trajectory

This paper describes the history of the on-orbit trajectory design and optimization for the Orion spacecraft at NASA JSC, from the initial design through the execution of the Artemis I test flight. In parallel, the Copernicus trajectory optimization tool was also being developed and was the main tool used for Orion trajectory design during this period. Finally, the paper gives an overview of the Artemis I trajectory that was flown during the Artemis I mission from November 16 - December 11, 2022.

Orion

A New Eclipse Algorithm for use in Spacecraft Trajectory Optimization

This paper presents a new eclipse algorithm, which determines if a spacecraft is in sunlight or shadow, that is simple to define, fast to compute, smooth and continuous in all regions external to the eclipsing body, and suitable for use in a spacecraft trajectory optimization problem. Details of the design evolution are presented, including the specifics of the algorithm's implementation in the trajectory design of NASA's Artemis I mission to a lunar DRO. Some alternate uses and discussion of future work is also presented.

Orion

A New Architecture for Parallelization of Complex Spacecraft Trajectory Optimization Scans

This paper describes CopScanner, a new component of the Copernicus ecosystem for spacecraft trajectory design and optimization. CopScanner is a Python library being developed at the NASA JSC which enables easy parallelization of Copernicus scans. CopScanner is currently being developed and implemented for production of Copernicus trajectory scans for upcoming Artemis Missions (Artemis II and beyond). On the backend, CopScanner utilizes Dask, an open-source Python library for parallel computing which enables parallelization over both multi-core local machines and large-scale distributed computing clusters. CopScanner abstracts the trajectory scanning process into a DAG which is constructed using a chain of individual subscans. Each node in the DAG executes a python module, called the callable, for which there are built-in defaults, or users may specify their own. Support for custom callables makes CopScanner a versatile trajectory optimization software. All output files and associated metadata from a CopScanner scan are compressed and stored in a two-file output, collectively called the FileStore, consisting of a SQLite database and a compressed JSON MessagePack file, for which CopScanner provides a Python class for interaction.

Quentin Moore

End-to-End Mission Design & Trajectory Optimization

The ability to compute end-to-end mission optimized trajectories is a critical component needed for the next generation of complex human spaceflight design and operations (Orion, HLS, Gateway, Mars). This project created a new interface for two of NASA’s trajectory tools: Copernicus and Genesis, enabling them to be used together for end-to-end mission design and optimization of all flight phases, including Earth ascent, lunar ascent, rendezvous, and lunar descent. This capability can also serve as a pathfinder for developing a future autonomous, onboard trajectory optimizer.

Software