Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “mission software”

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 595 records · Page 33
All sourcesNASA NTRSDOE OSTI
DOE OSTI2021

A survey of software implementations used by application codes in the Exascale Computing Project

The US Department of Energy Office of Science and the National Nuclear Security Administration initiated the Exascale Computing Project (ECP) in 2016 to prepare mission-relevant applications and scientific software for the delivery of the exascale computers starting in 2023. The ECP currently supports 24 efforts directed at specific applications and six supporting co-design projects. These 24 application projects contain 62 application codes that are implemented in three high-level languages—C, C++, and Fortran—and use 22 combinations of graphical processing unit programming models. The most common implementation language is C++, which is used in 53 different application codes. The most common programming models across ECP applications are CUDA and Kokkos, which are employed in 15 and 14 applications, respectively. This article provides a survey of the programming languages and models used in the ECP applications codebase that will be used to achieve performance on the future exascale hardware platforms.

97 MATHEMATICS AND COMPUTING↗
NASA NTRS1992

MISSION: Mission and Safety Critical Support Environment. Executive overview

For mission and safety critical systems it is necessary to: improve definition, evolution and sustenance techniques; lower development and maintenance costs; support safe, timely and affordable system modifications; and support fault tolerance and survivability. The goal of the MISSION project is to lay the foundation for a new generation of integrated systems software providing a unified infrastructure for mission and safety critical applications and systems. This will involve the definition of a common, modular target architecture and a supporting infrastructure.

Mckay, Charles↗
NASA NTRS2006

Software Reuse Within the Earth Science Community

Scientific missions in the Earth sciences frequently require cost-effective, highly reliable, and easy-to-use software, which can be a challenge for software developers to provide. The NASA Earth Science Enterprise (ESE) spends a significant amount of resources developing software components and other software development artifacts that may also be of value if reused in other projects requiring similar functionality. In general, software reuse is often defined as utilizing existing software artifacts. Software reuse can improve productivity and quality while decreasing the cost of software development, as documented by case studies in the literature. Since large software systems are often the results of the integration of many smaller and sometimes reusable components, ensuring reusability of such software components becomes a necessity. Indeed, designing software components with reusability as a requirement can increase the software reuse potential within a community such as the NASA ESE community. The NASA Earth Science Data Systems (ESDS) Software Reuse Working Group is chartered to oversee the development of a process that will maximize the reuse potential of existing software components while recommending strategies for maximizing the reusability potential of yet-to-be-designed components. As part of this work, two surveys of the Earth science community were conducted. The first was performed in 2004 and distributed among government employees and contractors. A follow-up survey was performed in 2005 and distributed among a wider community, to include members of industry and academia. The surveys were designed to collect information on subjects such as the current software reuse practices of Earth science software developers, why they choose to reuse software, and what perceived barriers prevent them from reusing software. In this paper, we compare the results of these surveys, summarize the observed trends, and discuss the findings. The results are very similar, with the second, larger survey confirming the basic results of the first, smaller survey. The results suggest that reuse of ESE software can drive down the cost and time of system development, increase flexibility and responsiveness of these systems to new technologies and requirements, and increase effective and accountable community participation.

Marshall, James J.↗
NASA NTRS2003

Developing An Autonomy Infusion Infrastructure for Robotic Exploration

Future robotic exploration missions will require autonomy in order to accomplish mission goals for operational efficiency and science return. For example, it will require three communication cycles for the Mars Exploration Rovers, Spirit and Opportunity, to place an instrument on a science target. Reducing this time necessitates highly accurate navigation, obstacle avoidance, target tracking, target analysis, manipulation, and fault diagnosis. Technologies to address these and other operational elements are currently being developed at NASA and within academia. However, infusion into missions has always been a difficult task for researchers. In order to keep risk down, mission managers are reluctant to include new technologies unless they have undergone extensive testing and verification under flight-realistic conditions. Furthermore, infusion of new technologies into missions is made more difficult by the variety of software frameworks under which these technologies are developed. Missions would like to see competing solutions demonstrated on a common platform so that they can compare performance and choose the solution best suited to their application.

Bualat, Maria G.↗
NASA NTRS2017

Increasing Crew Autonomy for Long Duration Exploration Missions: Self-Scheduling

Over the last three years, we have been investigating the operational concept of crew self-scheduling as a method of increasing crew autonomy for future exploration missions. Through Playbook, a planning and scheduling software tool, we have incrementally increased the ability for Earth analog mission crews to modify their schedules. Playbook allows the crew to add new activities from scratch, add new activities or groups of activities through a Task List, and reschedule or reassign flexible activities. The crew is also able to identify if plan modifications create violations, i.e., plan constraints not being met. This paper summarizes our observations with qualitative evidence from four NASA Extreme Environment Mission Operations (NEEMO) analog missions that supported self-scheduling as a feasible operational concept.

crew autonomy↗
NASA NTRS2017

Increasing Crew Autonomy for Long Duration Exploration Missions: Self-Scheduling

Over the last three years, we have been investigating the operational concept of crew self-scheduling as a method of increasing crew autonomy for future exploration missions. Through Playbook, a planning and scheduling software tool, we have incrementally increased the ability for Earth analog mission crews to modify their schedules. Playbook allows the crew to add new activities from scratch, add new activities or groups of activities through a Task List, and reschedule or reassign flexible activities. The crew is also able to identify if plan modifications create violations, i.e., plan constraints not being met. This paper summarizes our observations with qualitative evidence from four NASA Extreme Environment Mission Operations (NEEMO) analog missions that supported self-scheduling as a feasible operational concept.

planning and scheduling↗
NASA NTRS2019

High-Performance Spaceflight Computing (HPSC) Middleware Overview

High Performance Spacecraft Computing (HPSC) is a joint project between the National Aeronautics and Space Administration (NASA) and Air Force Research Lab (AFRL) to develop a high-performance multi-core radiation hardened flight processor. HPSC offers a new flight computing architecture to meet the needs of NASA missions through 2030 and beyond. Providing on the order of 100X the computational capacity of current flight processors for the same amount of power, the multicore architecture of the HPSC processor, or "Chiplet" provides unprecedented flexibility in a flight computing system by enabling the operating point to be set dynamically, trading among needs for computational performance, energy management and fault tolerance. The HPSC Chiplet is being developed by Boeing under contract to NASA, and is expected to provide prototypes in 2021. The HPSC Chiplet prototypes will be delivered with an evaluation board, system emulators, comprehensive system software, and a software development kit. In addition to the vendor deliverables, the AFRL is funding the development of a flexible Middleware to be developed by NASA Jet Propulsion Laboratory and NASA Goddard Space Flight Center. The HPSC Middleware provides a suite of thirteen high level services to manage the compute, memory and I/O resources of this complex device.This presentation will provide an overview of the HPSC project, including a hardware overview, system software overview, Middleware overview, and mission use cases. The hardware overview will provide a look at the 8 core High Performance Processing Subsystem (HPPS), the Real Time Processing Subsystem (RTPS), the Chiplet Configuration Management Subsystem, on chip peripherals, and high speed I/O. The system software overview will introduce the boot loaders, operating systems, device drivers, and software development environment. The Middleware overview will provide insight into the high-level services that will be provided to help mission developers manage the many resources and configurations made possible with the Chiplet. Finally, the presentation will provide a brief look at the mission use cases that can be enabled with this next generation architecture.

middleware↗
NASA NTRS2011

Implementation and Simulation Results using Autonomous Aerobraking Development Software

An Autonomous Aerobraking software system is currently under development with support from the NASA Engineering and Safety Center (NESC) that would move typically ground-based operations functions to onboard an aerobraking spacecraft, reducing mission risk and mission cost. The suite of software that will enable autonomous aerobraking is the Autonomous Aerobraking Development Software (AADS) and consists of an ephemeris model, onboard atmosphere estimator, temperature and loads prediction, and a maneuver calculation. The software calculates the maneuver time, magnitude and direction commands to maintain the spacecraft periapsis parameters within design structural load and/or thermal constraints. The AADS is currently tested in simulations at Mars, with plans to also evaluate feasibility and performance at Venus and Titan.

Maddock, Robert W.↗
NASA NTRSDate not supplied

Phase-Free Orbital Element Model Designed to Enable Rapid Assessment of Eclipse and Radiation Profiles for Low-Thrust Spiral Transfers Around the Earth

The Gateway Power and Propulsion Element (PPE) will be the first low-thrust solar electric ion propulsion mission to transfer from a highly elliptical Earth-bound orbit to a southern near-rectilinear halo orbit (NRHO) at the Earth-Moon L2 point. Due to the low thrust nature of the transfer orbit, it is desirable to locate viable trajectories that minimize the time spent in the Van Allen radiation belts to reduce solar array degradation and keep radiation dosages below design limits. In addition to radiation, low thrust trajectories which spiral around the Earth will pass through at least one or more seasons of Earth eclipses. The solar electric propulsion system relies on sunlight to generate the power necessary to operate the ion thrusters. Therefore, it is advantageous to find trajectories which also minimize the amount of time spent in eclipse and avoid excessive battery draw-down periods. We present an analytical method which rapidly approximates low-thrust spiral trajectories, fit to high-fidelity simulated data and parameterized to allow for changes in vehicle thrust characteristics, that is post-processed to determine eclipse profiles and time spent in the belts using a novel approach that estimates the geometry of the belts using a first-order dipole approximation of the Earth’s magnetic field. This method can be used to find satisfactory launch dates and orbit orientations that can serve as initial guesses when optimizing such missions in high-fidelity software.

low thrust trajectory design↗
NASA NTRSDate not supplied

Phase-Free Orbital Element Model Designed to Enable Rapid Assessment of Eclipse and Radiation Profiles for Low-Thrust Spiral Transfers Around the Earth

The Gateway Power and Propulsion Element (PPE) will be the first low-thrust solar electric ion propulsion mission to transfer from a highly elliptical Earth-bound orbit to a southern near-rectilinear halo orbit (NRHO) at the Earth-Moon L2 point. Due to the low thrust nature of the transfer orbit, it is desirable to locate viable trajectories that minimize the time spent in the Van Allen radiation belts to reduce solar array degradation and keep radiation dosages below design limits. In addition to radiation, low thrust trajectories which spiral around the Earth will pass through at least one or more seasons of Earth eclipses. The solar electric propulsion system relies on sunlight to generate the power necessary to operate the ion thrusters. Therefore, it is advantageous to find trajectories which also minimize the amount of time spent in eclipse and avoid excessive battery draw-down periods. We present an analytical method which rapidly approximates low-thrust spiral trajectories, fit to high-fidelity simulated data and parameterized to allow for changes in vehicle thrust characteristics, that is post-processed to determine eclipse profiles and time spent in the belts using a novel approach that estimates the geometry of the belts using a first-order dipole approximation of the Earth’s magnetic field. This method can be used to find satisfactory launch dates and orbit orientations that can serve as initial guesses when optimizing such missions in high-fidelity software.

low thrust trajectory design↗
NASA NTRS2005

A Reliable Service-Oriented Architecture for NASA's Mars Exploration Rover Mission

The Collaborative Information Portal (CIP) was enterprise software developed jointly by the NASA Ames Research Center and the Jet Propulsion Laboratory (JPL) for NASA's highly successful Mars Exploration Rover (MER) mission. Both MER and CIP have performed far beyond their original expectations. Mission managers and engineers ran CIP inside the mission control room at JPL, and the scientists ran CIP in their laboratories, homes, and offices. All the users connected securely over the Internet. Since the mission ran on Mars time, CIP displayed the current time in various Mars and Earth time zones, and it presented staffing and event schedules with Martian time scales. Users could send and receive broadcast messages, and they could view and download data and image files generated by the rovers' instruments. CIP had a three-tiered, service-oriented architecture (SOA) based on industry standards, including J2EE and web services, and it integrated commercial off-the-shelf software. A user's interactions with the graphical interface of the CIP client application generated web services requests to the CIP middleware. The middleware accessed the back-end data repositories if necessary and returned results for these requests. The client application could make multiple service requests for a single user action and then present a composition of the results. This happened transparently, and many users did not even realize that they were connecting to a server. CIP performed well and was extremely reliable; it attained better than 99% uptime during the course of the mission. In this paper, we present overviews of the MER mission and of CIP. We show how CIP helped to fulfill some of the mission needs and how people used it. We discuss the criteria for choosing its architecture, and we describe how the developers made the software so reliable. CIP's reliability did not come about by chance, but was the result of several key design decisions. We conclude with some of the important lessons we learned form developing, deploying, and supporting the software.

Mak, Ronald↗
NASA NTRS1967

Mission design for flight safety.

Manned space flight safety through mission trajectory design, considering hardware, software and operational constraints

MANNED SPACE FLIGHT↗
NASA NTRS2022

The Sun Radio Interferometer Space Experiment (SunRISE) Mission

The Sun Radio Interferometer Space Experiment (SunRISE) will provide an entirely new view on particle acceleration and transport in the inner heliosphere by creating the first low radio frequency interferometer in space to localize heliospheric radio emissions. By imaging and determining the location of decametric-hectometric (DH, 0.1 MHz–23 MHz) solar radio bursts, SunRISE will provide key information on particle acceleration mechanisms associated with coronal mass ejections (CMEs) and the magnetic field topology from active regions into interplanetary space. The SunRISE Observatory will consist of six space vehicles in a passive formation, in orbits designed to keep them within approximately 10 km of each other, and flying in a supersynchronous geosynchronous Earth orbit (GEO). Each space vehicle consists of a Solar DH-GNSS payload and a 6U form factor spacecraft. The SunRISE Observatory together with significant ground-based processing, will enable imaging of the Sun in a portion of the spectrum that is blocked by the ionosphere and cannot be observed from Earth. Key aspects that enable this mission are that only position knowledge of the space vehicles is required, not active control, and that the architecture involves a modest amount of on-board processing coupled with significant ground-based processing for navigation, position determination, and science operations. Mission-enabling advances in software-defined radios, GPS navigation and timing, and small spacecraft technologies, developed and flown on the DARPA High Frequency Research (DHFR) and the Community Initiative for Continuing Earth Radio Occultation (CICERO) have made this mission affordable and low-risk. The SunRISE mission will exploit the multiple spacecraft per aperture (MSPA) capability of NASA’s Deep Space Network (DSN), for more efficient data transfers of larger data volumes, and utilize commercial access to space, in which the SunRISE space vehicles will be carried to their target orbit as secondary payloads in conjunction with a larger host spacecraft intended for GEO.

Neilson, Tim↗
NASA NTRSDate not supplied

Ground Risk Informed Operational Planning for Small Unmanned Aerial Systems

Increasing quantities of small Unmanned Aerial Systems (sUAS) operations present many challenges in terms of safe adoption and integration into existing airspace. The ability to study and quantify the risk to third parties on the ground prior to flight is an important step toward enabling Beyond Visual Line of Sight (BVLOS) operations. The Ground Risk Assessment Service Provider (GRASP) software is a capability developed by NASA to assist with third-party risk quantification and risk-informed flight planning. In this paper, two nominal flight paths intended to represent an infrastructure inspection mission are evaluated using the software to demonstrate its utility. A method is also introduced for adding other NASA-developed capabilities into a single architecture to assess a broader set of operational risks associated with BVLOS operations. These capabilities include a navigation system performance prediction tool, a high fidelity vehicle dynamics model, high resolution wind field data, and other information pertinent to operators. Data produced by these capabilities are combined to enable use of the Performance Based Navigation (PBN) concept borrowed from conventional aviation, providing quantified flight path uncertainty for where the sUAS is likely to be relative to its nominal flight plan. Ground risk is assessed within this region of uncertainty, giving a higher level of confidence in the solution compared to an analysis of only the nominal flight path.

Ground Risk↗
NASA NTRS1994

SEQ-POINTER: Next generation, planetary spacecraft remote sensing science observation design tool

Since Mariner, NASA-JPL planetary missions have been supported by ground software to plan and design remote sensing science observations. The software used by the science and sequence designers to plan and design observations has evolved with mission and technological advances. The original program, PEGASIS (Mariners 4, 6, and 7), was re-engineered as POGASIS (Mariner 9, Viking, and Mariner 10), and again later as POINTER (Voyager and Galileo). Each of these programs were developed under technological, political, and fiscal constraints which limited their adaptability to other missions and spacecraft designs. Implementation of a multi-mission tool, SEQ POINTER, under the auspices of the JPL Multimission Operations Systems Office (MOSO) is in progress. This version has been designed to address the limitations experienced on previous versions as they were being adapted to a new mission and spacecraft. The tool has been modularly designed with subroutine interface structures to support interchangeable celestial body and spacecraft definition models. The computational and graphics modules have also been designed to interface with data collected from previous spacecraft, or on-going observations, which describe the surface of each target body. These enhancements make SEQ POINTER a candidate for low-cost mission usage, when a remote sensing science observation design capability is required. The current and planned capabilities of the tool will be discussed. The presentation will also include a 5-10 minute video presentation demonstrating the capabilities of a proto-Cassini Project version that was adapted to test the tool. The work described in this abstract was performed by the Jet Propulsion Laboratory, California Institute of Technology, under contract to the National Aeronautics and Space Administration.

Boyer, Jeffrey S.↗