Search NASA⌕ Search

SEARCH · Search NASA

Results for “trajectory planning”

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 487 records · Page 27

Multi-Agent Motion Planning using Deep Learning for Space Applications

State-of-the-art motion planners cannot scale to a large number of systems. Motion planning for multiple agents is an NP (non-deterministic polynomial-time) hard problem, so the computation time increases exponentially with each addition of agents. This computational demand is a major stumbling block to the motion planner's application to future NASA missions involving the swarm of space vehicles. We applied a deep neural network to transform computationally demanding mathematical motion planning problems into deep learning-based numerical problems. We showed optimal motion trajectories can be accurately replicated using deep learning-based numerical models in several 2D and 3D systems with multiple agents. The deep learning-based numerical model demonstrates superior computational efficiency with plans generated 1000 times faster than the mathematical model counterpart.

Madani, Ramtin↗

Navigation of the GRAIL Spacecraft Pair Through the Extended Mission at the Moon

The GRAIL extended mission (XM) dramatically expands the scope of GRAIL's gravity science investigation by flying the pair of spacecraft at the lowest orbit the flight team can safely support. From the perspective of the Navigation team, the low orbit altitude introduces new challenges. At this lower altitude, navigation is more sensitive to higher-order terms of the gravity field so that orbit determination solutions are more difficult and there is less certainty of achieving maneuver targets. This paper reports on the strategy and performance of the Navigation system for GRAIL's XM. On a weekly basis, the Navigation team provided reference trajectory updates, designed three maneuvers, and reconstructed the execution of those maneuvers. In all, the XM involved 55 planned maneuvers; five were canceled. The results of the Navigation team's efforts, in terms of maintaining the reference-trajectory targets, satisfying requirements, and achieving desired separation distances, are assessed.

orbit↗

Generalized Linear Targeting For Cislunar Flight

An important element of Artemis and NASA’s campaign to explore the Moon is the autonomous onboard two-level targeter (TLT) used during all cislunar flight phases. The function of the TLT is to autonomously recompute the burn targets for the upcoming burn (or multiple burns) in response to navigation and vehicle dispersion providing a solution that meets all of the trajectory constraints. Although the TLT has been utilized previously as a ground-based planning tool, and flown onboard during the Artemis I mission, it’s complexity and iterative nature make is difficult to incorporate into and support rapid analyses such as robust optimal trajectory design applications where speed is essential. In this paper, a set of generalized linear targeting algorithms that mimics many of the properties of the TLT is derived. The generalized algorithms can handle single or multiple impulsive maneuvers, with multiple constraints at multiple fixed or variable times. A linear targeting algorithm for finite burn maneuvers is also derived. The generalized linear targeting algorithms are exceptionally fast and easy to implement in Monte Carlo analysis, linear covariance (LinCov) analysis, and robust optimal trajectory design. Several cislunar flight examples are provided.

Linear Covariance Analysis↗

Encke-Beta Predictor for Orion Burn Targeting and Guidance

The state vector prediction algorithm selected for Orion on-board targeting and guidance is known as the Encke-Beta method. Encke-Beta uses a universal anomaly (beta) as the independent variable, valid for circular, elliptical, parabolic, and hyperbolic orbits. The variable, related to the change in eccentric anomaly, results in integration steps that cover smaller arcs of the trajectory at or near perigee, when velocity is higher. Some burns in the EM-1 and EM-2 mission plans are much longer than burns executed with the Apollo and Space Shuttle vehicles. Burn length, as well as hyperbolic trajectories, has driven the use of the Encke-Beta numerical predictor by the predictor/corrector guidance algorithm in place of legacy analytic thrust and gravity integrals.

Robinson, Shane↗

An Overview of Trajectory Design Operations for the Microwave Anisotropy Probe (MAP) Mission

The main science objective of the Microwave Anisotropy Probe (MAP) mission is to produce an accurate full-sky map of the cosmic microwave background temperature fluctuations - anisotropy. MAP will collect these measurements from a lissajous orbit about the Sun-Earth/Moon L2 Lagrange Point. The NASA Goddard Space Flight Center (GSFC) Flight Dynamics Analysis Branch provided mission analysis, maneuver planning and maneuver calibration for the MAP spacecraft. This paper will provide an overview of the MAP trajectory design, a summary of the maneuvers executed. Differences from the pre-launch nominal plan will also be discussed. During the MAP phasing loops, MAP performed three calibration maneuvers in order to characterize the performance of the primary sets of thrusters - +X, +Z, and -Z. The calibration maneuvers were designed to minimize their impact on the trajectory. Four maneuvers were performed to set up the gravity assist of the Moon - required to propel MAP out to its orbit about L2. These maneuvers were performed at the three phasing loop perigees and at 18 hours after the final perigee. It became necessary to alter some of the perigee maneuvers in order to shape the gravity assist. This shaping was done to help meet some mission goals. In particular, the gravity assist was changed slightly in order to remove lunar shadows in both the cruise out to L2 and in the first revolution about L2. This amounted to a change in the phasing loop AV of less than 1 m/s. After the gravity assist, two mid-course correction (MCC) maneuvers were performed in order to fine-tune the trajectory. MCC1 was used to clean up and errors which resulted from the gravity assist. MCC2 was performed in order to mitigate a large stationkeeping maneuver following a crucial instrument calibration period during the cruise phase. MAP executed it's first stationkeeping maneuver in January 16th and is ready for a second calibration period during late Winter / early Spring. Further information concerning subsequent stationkeeping maneuver will be added as they become available.

Cuevas, Osvaldo O.↗

Robust Trajectory Design for Rendezvous in a Near Rectilinear Halo Orbit

Future NASA Artemis missions will require complex docking plans between the Orion capsule and Lunar Gateway that meet predetermined safety constraints while minimizing fuel usage and state uncertainty at rendezvous. In this paper, linear covariance analysis is applied to a first order relative form of Near-Rectilinear Halo Orbit dynamics to determine the nominal trajectories and state dispersions associated with various maneuver profiles in the Sun-referenced Local Vertical Local Horizontal reference frame of the lunar Gateway. These maneuver profiles are optimized using a particle swarm optimizer and direct search algorithm to find trajectories that satisfy approach corridor, free drift, velocity magnitude, under-burn, and maneuver transfer time safety constraints to 3-sigma certainty.

Linear Covariance Analysis↗

Tracking and data system support for the Pioneer project. Volume 3: Pioneer 10 from 1 April 1972 through the Jupiter encounter period, January 1974

The Tracking and Data Systems support of the Pioneer 10 mission from April 1, 1972 through the Jupiter encounter period which ended January 5, 1974 is described. The period covered involves operations in the interplanetary environment from the time of completion of the second trajectory correction to the start of Jupiter encounter; the implementation, planning, and testing that lead to the Jupiter encounter; and the operations during the 60 day encounter period.

Miller, R. B.↗

Continuation of data analysis from the ion mass spectrometer on the ISIS-2 spacecraft

The spectrometer measures the composition and number density of the positive ion species in the ionosphere as well as the ion flux normal to the spacecraft trajectory. The measurement of high latitude ionospheric dynamics is reported. Plans for an empirical composition model of the polar ionosphere at 1400 km altitude consisting of maps of the major constituent are also reported.

Hoffman, J. H.↗

A survey of interplanetary trajectory options for a chemically propelled manned Mars vehicle

A single chemically propelled vehicle has been proposed for a manned earth-Mars transportation system. In this investigation, all potential direct and Venus swingby interplanetary transfers over the time span 2010-2025 are considered. Two promising mission strategies have emerged: a 1.6-1.8 year Venus swingby mission, ad a 2.0-2.5 year direct mission. Both of these strategies include a 60-day Mars stopover and are efficient from a weight standpoint. In an aerobraking scenario, it was found that the velocities during both Mars and earth entry are greatly dependent upon the interplanetary trajectory and should be of significant concern at the mission planning stage.

Braun, Robert D.↗

Galileo

The purpose of the Galileo missions is to make observations of Jupiter and its satellites using an orbiting spacecraft and an atmospheric entry probe. The mission will determine the chemical composition and physical state of the Jovian atmosphere and its satellites, and the topology and behavior of the magnetic field and energetic particle flux of Jupiter. The mission plan calls for a Venus Earth Earth Gravity Assist (VEEGA) trajectory having a launch to end of mission duration of approximately 8 years. The Galileo spacecraft was placed in Earth orbit by the Space Transportation System (STS) on October 18, 1989. The Inertial Upper Stage (IUS) placed the spacecraft on a trajectory to encounter Venus on February 10, 1990. Information is given in tabular form for coverage goals, Deep Space Network (DSN) support, frequency assignments, telemetry, command, and tracking support responsibility.

Ausman, N. E.↗

Dynamical structure of extreme ultraviolet macrospicules

We describe the substructures forming the macrospicules and their temporal evolution, as revealed by the application of an image enhancement algorithm to extreme ultraviolet (EUV) observations of macrospicules. The enhanced images uncover, for the first time, the substructures forming the column-like structures within the macrospicules and the low-lying arches at their base. The spatial and temporal evolution of macrospicules clearly show continuous interaction between these substructures with occasional ejection of plasma following a ballistic trajectory. We comment on the importance of these results for planning near future space observations of macrospicules with better temporal and spatial resolution.

Karovska, Margarita↗

Methodology for Generating Conflict Scenarios by Time Shifting Recorded Traffic Data

A methodology is presented for generating conflict scenarios that can be used as test cases to estimate the operational performance of a conflict probe. Recorded air traffic data is time shifted to create traffic scenarios featuring conflicts with characteristic properties similar to those encountered in typical air traffic operations. First, a reference set of conflicts is obtained from trajectories that are computed using birth points and nominal flight plans extracted from recorded traffic data. Distributions are obtained for several primary properties (e.g., encounter angle) that are most likely to affect the performance of a conflict probe. A genetic algorithm is then utilized to determine the values of time shifts for the recorded track data so that the primary properties of conflicts generated by the time shifted data match those of the reference set. This methodology is successfully demonstrated using recorded traffic data for the Memphis Air Route Traffic Control Center; a key result is that the required time shifts are less than 5 min for 99% of the tracks. It is also observed that close matching of the primary properties used in this study additionally provides a good match for some other secondary properties.

Paglione, Mike↗

Automated Conflict Resolution For Air Traffic Control

The ability to detect and resolve conflicts automatically is considered to be an essential requirement for the next generation air traffic control system. While systems for automated conflict detection have been used operationally by controllers for more than 20 years, automated resolution systems have so far not reached the level of maturity required for operational deployment. Analytical models and algorithms for automated resolution have been traffic conditions to demonstrate that they can handle the complete spectrum of conflict situations encountered in actual operations. The resolution algorithm described in this paper was formulated to meet the performance requirements of the Automated Airspace Concept (AAC). The AAC, which was described in a recent paper [1], is a candidate for the next generation air traffic control system. The AAC's performance objectives are to increase safety and airspace capacity and to accommodate user preferences in flight operations to the greatest extent possible. In the AAC, resolution trajectories are generated by an automation system on the ground and sent to the aircraft autonomously via data link .The algorithm generating the trajectories must take into account the performance characteristics of the aircraft, the route structure of the airway system, and be capable of resolving all types of conflicts for properly equipped aircraft without requiring supervision and approval by a controller. Furthermore, the resolution trajectories should be compatible with the clearances, vectors and flight plan amendments that controllers customarily issue to pilots in resolving conflicts. The algorithm described herein, although formulated specifically to meet the needs of the AAC, provides a generic engine for resolving conflicts. Thus, it can be incorporated into any operational concept that requires a method for automated resolution, including concepts for autonomous air to air resolution.

Erzberger, Heinz↗

Cassini's Maneuver Automation Software (MAS) Process: How to Successfully Command 200 Navigation Maneuvers

To keep Cassini on its complex trajectory, more than 200 orbit trim maneuvers (OTMs) have been planned from July 2004 to July 2010. With only a few days between many of these OTMs, the operations process of planning and executing the necessary commands had to be automated. The resulting Maneuver Automation Software (MAS) process minimizes the workforce required for, and maximizes the efficiency of, the maneuver design and uplink activities. The MAS process is a well-organized and logically constructed interface between Cassini's Navigation (NAV), Spacecraft Operations (SCO), and Ground Software teams. Upon delivery of an orbit determination (OD) from NAV, the MAS process can generate a maneuver design and all related uplink and verification products within 30 minutes. To date, all 112 OTMs executed by the Cassini spacecraft have been successful. MAS was even used to successfully design and execute a maneuver while the spacecraft was in safe mode.

Yang, Genevie Velarde↗

Conflict Resolution for Wind-Optimal Aircraft Trajectories in North Atlantic Oceanic Airspace with Wind Uncertainties

Air traffic in the North Atlantic oceanic airspace (NAT) experiences very strong winds caused by jet streams. Flying wind-optimal trajectories increases individual flight efficiency, which is advantageous when operating in the NAT. However, as the NAT is highly congested during peak hours, a large number of potential conflicts between flights are detected for the sets of wind-optimal trajectories. Conflict resolution performed at the strategic level of flight planning can significantly reduce the airspace congestion. However, being completed far in advance, strategic planning can only use predicted environmental conditions that may significantly differ from the real conditions experienced further by aircraft. The forecast uncertainties result in uncertainties in conflict prediction, and thus, conflict resolution becomes less efficient. This work considers wind uncertainties in order to improve the robustness of conflict resolution in the NAT. First, the influence of wind uncertainties on conflict prediction is investigated. Then, conflict resolution methods accounting for wind uncertainties are proposed.

wind uncertainties↗

InSight's Reconstructed Aerothermal Environments

The InSight Mars Lander successfully landed on the surface on November 26, 2018. This poster will describe the methodologies and margins used in developing the aerothermal environments for design of the thermal protection systems (TPS), as well as a prediction of as-flown environments based on the best estimated trajectory. The InSight mission spacecraft design approach included the effects of radiant heat flux to the aft body from the wake for the first time on a US Mars Mission, due to overwhelming evidence in ground testing for the European ExoMars mission (2009/2010) [1] and 2010 tests in the Electric Arc Shock Tube (EAST) facility [2]. The radiant energy on an aftbody was also recently confirmed via measurement on the Schiaparelli mission [3]. In addition, the InSight mission expected to enter the Mars atmosphere during the dust storm season, so the heatshield TPS was designed to accommodate the extra recession due to the potential dust impact. This poster will compare the predicted aerothermal environments using the reconstructed best estimated trajectory to the design environments. Design Approach: The InSight spacecraft was planned to be a near-design-to-print copy of the Phoenix spacecraft. The determination of the heatshield TPS requirements was approached as if it was a new design due to the new requirement of flying through a dust storm. The baseline for aftbody was build-to-print, and all analyses focused on ensuring adequate margin. This proved to be a challenge because the Phoenix aftbody was designed to withstand only convective heating and the InSight aftbody was evaluated for both convective and radiative heating. Aerothermal environments were predicted using the Langley Aerothermodynamic Upwind Relaxation Algorithm (LAURA) and the Data Parallel Line Relaxation (DPLR) CFD codes, and the Nonequilibrium Radiative Transport and Spectra Program (NEQAIR) utilizing bounding design trajectories derived from Monte Carlo analyses from the Program to Optimize Simulated Trajectories II (POST2). In all cases, super-catalytic flowfields were assigned to ensure the most conservative heating results. Two trajectories were evaluated: 1) the trajectory with the maximum heat flux was utilized to determine the flowfield characteristics and the viability of the selection of TPS materials; and 2) the trajectory with the maximum heat load was used to determine the required thicknesses of the TPS materials. Evaluation of the MEDLI data [4], along with ground test data [5] led to the determination of whether or not the flow would transition from laminar to turbulent on the heatshield, which also determined the TPS sizing location for the heatshield. Aerothermal margins were added for the convective heating and developed for the radiative heating. TPS material sizing was determined with the Reaction Kinetic Ablation Program (REKAP) and the Fully Implicit Ablation and Thermal Analysis program (FIAT) using a three-branched approach to account for aerothermal, material response, and material properties uncertainties. In addition, the heatshield recession was augmented by an analysis of the effect of entry through a potential dusty atmosphere using a methodology developed in References [6] and [7]. These analyses resulted in an increase to the Phoenix heatshield TPS thickness. Reconstruction Efforts: Once the best estimated trajectory is reconstructed by the team, the LAURA/HARA (High-Temperature Aerothermo-dynamic Radiation model) and DPLR/NEQAIR code pairs will be used to predict the as-flown aerothermal conditions. In these runs, fully-catalytic flowfields will be assigned because it is a more physically accurate description of the chemistry in the flow. Once again, determination of the onset of turbulence on the heatshield will be evaluated. The as-flown aerothermal environments will then be compared to the design environments.

Beck, R. A.↗

Dawn Orbit Determination Team: Modeling and Fitting of Optical Data at Vesta

The Dawn spacecraft was launched on September 27th, 2007. Its mission is to consecutively rendezvous with and observe the two largest bodies in the main asteroid belt, Vesta and Ceres. It has already completed over a year's worth of direct observations of Vesta (spanning from early 2011 through late 2012) and is currently on a cruise trajectory to Ceres, where it will begin scientific observations in mid-2015. Achieving this data collection required careful planning and execution from all Dawn operations teams. Dawn's Orbit Determination (OD) team was tasked with reconstruction of the as-flown trajectory as well as determination of the Vesta rotational rate, pole orientation and ephemeris, among other Vesta parameters. Improved knowledge of the Vesta pole orientation, specifically, was needed to target the final maneuvers that inserted Dawn into the first science orbit at Vesta. To solve for these parameters, the OD team used radiometric data from the Deep Space Network (DSN) along with optical data reduced from Dawn's Framing Camera (FC) images. This paper will de-scribe the initial determination of the Vesta ephemeris and pole using a combination of radiometric and optical data, and also the progress the OD team has made since then to further refine the knowledge of Vesta's body frame orientation and rate with these data.

imagery↗

Magellan Post Launch Mission Operation Report

Magellan was successfully launched by the Space Shuttle Atlantis from the Kennedy Space Center at 2:47 p.m. EDT on May 4, 1989. The Inertial Upper Stage (IUS) booster and attached Magellan Spacecraft were successfully deployed from Atlantis on Rev. 5 as planned, at 06:14 hrs Mission Elapsed Time (MET). The two IUS propulsion burns which began at 07:14 hrs MET and were completed at 07:22 hrs MET, placed the Magellan Spacecraft almost perfectly on its preplanned trajectory to Venus. The IUS was jettisoned at 07:40 hrs MET and Magellan telemetry was immediately acquired by the Deep Space Network (DSN). A spacecraft trajectory correction maneuver was performed on May 21 and the spacecraft is in the planned standard cruise configuration with all systems operating nominally. An initial attempt was made to launch Atlantis on April 28, 1989, but the launch was scrubbed at T-31 sec due to a failure of the liquid hydrogen recirculation pump on Space Shuttle Main Engine #1. The countdown had proceeded smoothly until T-20 min when the Magellan radio receiver "locked-on" the MIL 71 Unified S-Band (USB) transmission as the transmitter power was increased fro 2 kw to 10 kw in support of the orbiter launch. During the planned hold at T-9 min, the USB was confirmed as the source of the receiver "lock" and Magellan's launch readiness was reaffirmed. In addition a five-minute extension of the T-9 hold occurred when a range safety computer went off-line, creating a loss of redundancy in the range safety computer network. Following resumption of the countdown, both the orbiter and Magellan flows proceeded smoothly until the launch was scrubbed at T-31 sec.

Source record↗