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 271 records · Page 15
All sourcesNASA NTRSDOE OSTI
NASA NTRS2009

Flashline Mars Arctic Research Station (FMARS) 2009 Expedition Crew Perspectives

The Flashline Mars Arctic Research Station (FMARS), located on the rim of the Haughton Crater on Devon Island in the Canadian Arctic, is a simulated Mars habitat that provides operational constraints similar to those which will be faced by future human explorers on Mars. In July 2009, a six-member crew inhabited the isolated habitation module and conducted the twelfth FMARS mission. The crew members conducted frequent EVA operations wearing mock space suits to conduct field experiments under realistic Mars-like conditions. Their scientific campaign spanned a wide range of disciplines and included many firsts for Mars analog research. Among these are the first use of a Class IV medical laser during a Mars simulation, helping to relieve crew stress injuries during the mission. Also employed for the first time in a Mars simulation at FMARS, a UAV (Unmanned Aerial Vehicle) was used by the space-suited explorers, aiding them in their search for mineral resources. Sites identified by the UAV were then visited by geologists who conducted physical geologic sampling. For the first time, explorers in spacesuits deployed passive seismic equipment to monitor earthquake activity and characterize the planet's interior. They also conducted the first geophysical electromagnetic survey as analog Mars pioneers to search for water and characterize geological features under the surface. The crew collected hydrated minerals and attempted to produce drinkable water from the rocks. A variety of equipment was field tested as well, including new cameras that automatically geotag photos, data-recording GPS units, a tele-presence rover (operated from Florida), as well as MIT-developed mission planning software. As plans develop to return to the Moon and go on to Mars, analog facilities like FMARS can provide significant benefit to NASA and other organizations as they prepare for robust human space exploration. The authors will present preliminary results from these studies as well as their perspectives on topics including human factors, logistics, EVA operations, and the use of social media throughout the mission.

Cusack, Stacy↗
NASA NTRS2016

Station Program Note Pull Automation

Upon commencement of my internship, I was in charge of maintaining the CoFR (Certificate of Flight Readiness) Tool. The tool acquires data from existing Excel workbooks on NASA's and Boeing's databases to create a new spreadsheet listing out all the potential safety concerns for upcoming flights and software transitions. Since the application was written in Visual Basic, I had to learn a new programming language and prepare to handle any malfunctions within the program. Shortly afterwards, I was given the assignment to automate the Station Program Note (SPN) Pull process. I developed an application, in Python, that generated a GUI (Graphical User Interface) that will be used by the International Space Station Safety & Mission Assurance team here at Johnson Space Center. The application will allow its users to download online files with the click of a button, import SPN's based on three different pulls, instantly manipulate and filter spreadsheets, and compare the three sources to determine which active SPN's (Station Program Notes) must be reviewed for any upcoming flights, missions, and/or software transitions. Initially, to perform the NASA SPN pull (one of three), I had created the program to allow the user to login to a secure webpage that stores data, input specific parameters, and retrieve the desired SPN's based on their inputs. However, to avoid any conflicts with sustainment, I altered it so that the user may login and download the NASA file independently. After the user has downloaded the file with the click of a button, I defined the program to check for any outdated or pre-existing files, for successful downloads, to acquire the spreadsheet, convert it from a text file to a comma separated file and finally into an Excel spreadsheet to be filtered and later scrutinized for specific SPN numbers. Once this file has been automatically manipulated to provide only the SPN numbers that are desired, they are stored in a global variable, shown on the GUI, and transferred over to a new Excel worksheet for comparison. I managed to get my application to acquire the CSWG (Computer Safety Working Group) and the SPNWG (Space Station Working Group) SPN's with just two mouse clicks for each pull, as opposed to several from the original process. When all three pulls are performed, an Excel sheet containing all three different results will be generated for the user to compare and determine which SPN's will be presented or reviewed the following month. The experience from this internship has been spectacular. As a high school senior who will begin attending college in the fall, this internship has been both educationally and occupationally beneficial. The internship has allowed me the opportunities to learn new programming languages, effectively network with NASA personnel from a variety of departments at JSC, and allowed me to learn new professional skills and etiquette. My internship at NASA's Johnson Space Center has further motivated me to pursue a Master's degree in Software Engineering and strive for a prosperous career with NASA as a civil servant.

Delgado, Ivan↗
NASA NTRS2006

Spitzer Space Telescope Sequencing Operations Software, Strategies, and Lessons Learned

The Space Infrared Telescope Facility (SIRTF) was launched in August, 2003, and renamed to the Spitzer Space Telescope in 2004. Two years of observing the universe in the wavelength range from 3 to 180 microns has yielded enormous scientific discoveries. Since this magnificent observatory has a limited lifetime, maximizing science viewing efficiency (ie, maximizing time spent executing activities directly related to science observations) was the key operational objective. The strategy employed for maximizing science viewing efficiency was to optimize spacecraft flexibility, adaptability, and use of observation time. The selected approach involved implementation of a multi-engine sequencing architecture coupled with nondeterministic spacecraft and science execution times. This approach, though effective, added much complexity to uplink operations and sequence development. The Jet Propulsion Laboratory (JPL) manages Spitzer s operations. As part of the uplink process, Spitzer s Mission Sequence Team (MST) was tasked with processing observatory inputs from the Spitzer Science Center (SSC) into efficiently integrated, constraint-checked, and modeled review and command products which accommodated the complexity of non-deterministic spacecraft and science event executions without increasing operations costs. The MST developed processes, scripts, and participated in the adaptation of multi-mission core software to enable rapid processing of complex sequences. The MST was also tasked with developing a Downlink Keyword File (DKF) which could instruct Deep Space Network (DSN) stations on how and when to configure themselves to receive Spitzer science data. As MST and uplink operations developed, important lessons were learned that should be applied to future missions, especially those missions which employ command-intensive operations via a multi-engine sequence architecture.

missions operations↗
NASA NTRS1988

Ion propulsion system design and throttling strategies for planetary missions

This paper describes recent advances in ion propulsion system design which promise to increase the propulsion system reliability by reducing the overall system complexity. The greatest simplification in the overall propulsion system operation is accomplished through a change in the ion engine throttling strategy. By using three grid optics it is possible to effect engine throttling at a constant beam curent over at least a 3.8 to 1 variation in input power. Throttling at a constant beam current results in a single discharge chamber operating point and eliminates the need for active propellant flow controllers and complex engine throttling software. Detailed mission analysis calculations for a CNSR mission performed using this constant beam current throttling strategy indicate only a small reduction in delivered payload and increase in required propellant relative to a conventional throttling profile based on varying the beam curent.

Garner, Charles E.↗
NASA NTRS2018

An Open Avionics and Software Architecture to Support Future NASA Exploration Missions

Final Document is attached. The presentation describes an avionics and software architecture that has been developed through NASAs Advanced Exploration Systems (AES) division. The architecture is open-source, highly reliable with fault tolerance, and utilizes standard capabilities and interfaces, which are scalable and customizable to support future exploration missions. Specific focus areas of discussion will include command and data handling, software, human interfaces, communication and wireless systems, and systems engineering and integration. Final Paper, not the Abstract, is attached.

Avionics↗
NASA NTRS1991

Issues associated with establishing control zones for international space operations

Cooperative missions in Earth orbit can be facilitated by developing a strategy to regulate the manner in which vehicles interact in orbit. One means of implementing such a strategy is to utilize a control zones technique that assigns different types of orbital operations to specific regions of space surrounding a vehicle. Considered here are issues associated with developing a control zones technique to regulate the interactions of spacecraft in proximity to a manned vehicle. Technical and planning issues, flight hardware and software issues, mission management parameter, and other constraints are discussed. Also covered are manned and unmanned vehicle operations, and manual versus automated flight control. A review of the strategies utilized by the Apollo Soyuz Test Project and the Space Station Freedom Program is also presented.

Nader, Blair A.↗
NASA NTRS1992

Issues in developing control zones for international space operations

Cooperative missions in earth orbit can be facilitated by developing a strategy to regulate the manner in which vehicles interact in orbit. One means of implementing such a strategy is to utilize a control zones technique that assigns different types of orbital operations to specific regions of space surrounding a vehicle. Considered here are issues associated with developing a control zones technique to regulate the interactions of spacecraft in proximity to a manned vehicle. Technical and planning issues, flight hardware and software issues, mission management parameter, and other constraints are discussed. Also covered are manned and unmanned vehicle operations, and manual versus automated flight control. A review of the strategies utilized by the Apollo Soyuz Test Project and the Space Station Freedom Program is also presented.

Nader, Blair A.↗
NASA NTRS2016

ICAROUS - Integrated Configurable Algorithms for Reliable Operations Of Unmanned Systems

NASA's Unmanned Aerial System (UAS) Traffic Management (UTM) project aims at enabling near-term, safe operations of small UAS vehicles in uncontrolled airspace, i.e., Class G airspace. A far-term goal of UTM research and development is to accommodate the expected rise in small UAS traffic density throughout the National Airspace System (NAS) at low altitudes for beyond visual line-of-sight operations. This paper describes a new capability referred to as ICAROUS (Integrated Configurable Algorithms for Reliable Operations of Unmanned Systems), which is being developed under the UTM project. ICAROUS is a software architecture comprised of highly assured algorithms for building safety-centric, autonomous, unmanned aircraft applications. Central to the development of the ICAROUS algorithms is the use of well-established formal methods to guarantee higher levels of safety assurance by monitoring and bounding the behavior of autonomous systems. The core autonomy-enabling capabilities in ICAROUS include constraint conformance monitoring and contingency control functions. ICAROUS also provides a highly configurable user interface that enables the modular integration of mission-specific software components.

Consiglio, María↗
NASA NTRS2016

ICAROUS: Integrated Configurable Architecture for Unmanned Systems

NASA's Unmanned Aerial System (UAS) Traffic Management (UTM) project aims at enabling near-term, safe operations of small UAS vehicles in uncontrolled airspace, i.e., Class G airspace. A far-term goal of UTM research and development is to accommodate the expected rise in small UAS traffic density throughout the National Airspace System (NAS) at low altitudes for beyond visual line-of-sight operations. This video describes a new capability referred to as ICAROUS (Integrated Configurable Algorithms for Reliable Operations of Unmanned Systems), which is being developed under the auspices of the UTM project. ICAROUS is a software architecture comprised of highly assured algorithms for building safety-centric, autonomous, unmanned aircraft applications. Central to the development of the ICAROUS algorithms is the use of well-established formal methods to guarantee higher levels of safety assurance by monitoring and bounding the behavior of autonomous systems. The core autonomy-enabling capabilities in ICAROUS include constraint conformance monitoring and autonomous detect and avoid functions. ICAROUS also provides a highly configurable user interface that enables the modular integration of mission-specific software components.

Consiglio, Maria C.↗
NASA NTRS1992

SPIKE: Application for ASTRO-D mission planning

SPIKE is a mission planning software system developed by a team of programmers at the STScI for use with the Hubble Space Telescope (HST). SPIKE has been developed for the purpose of automating observatory scheduling to increase the effective utilization and ultimately, scientific return from orbiting telescopes. High-level scheduling strategies using both rule-based and neural network approaches have been incorporated. Graphical displays of activities, constraints, and schedules are an important feature of the system. Although SPIKE was originally developed for the HST, it can be used for other astronomy missions including ground-based observatories. One of the missions that has decided to use SPIKE is ASTRO-D, a Japanese X-ray satellite for which the U.S. is providing a part of the scientific payload. Scheduled to fly in Feb. 1993, its four telescopes will focus X-rays over a wide energy range onto CCD's and imaging gas proportional counters. ASTRO-D will be the first X-ray imaging mission operating over the 0.5-12 keV band with high energy resolution. This combination of capabilities will enable a varied and exciting program of astronomical research to be carried out. ASTRO-D is expected to observe 5 to 20 objects per day and a total of several thousands per year. This requires the implementation of an efficient planning and scheduling system which SPIKE can provide. Although the version of SPIKE that will be used for ASTRO-D mission is almost identical to that used for the HST, there are a few differences. For example, ASTRO-D will use two ground stations for data downlinks, instead of the TDRSS system for data transmission. As a consequence ASTRO-D is constrained by limited on-board data storage capacity to schedule high data-rate observations during periods of frequent high bit rate observations accordingly. We will demonstrate the ASTRO-D version of SPIKE to show what SPIKE can provide and how efficiently it creates an observational schedule.

Isobe, T.↗
NASA NTRS2004

NASA's Swarm Missions: The Challenge of Building Autonomous Software

The days of watching a massive manned cylinder thrust spectacularly off a platform into space might rapidly become ancient history when the National Aeronautics and Space Administration (NASA) introduces its new millenium mission class. Motivated by the need to gather more data than is possible with a single spacecraft, scientists have developed a new class of missions based on the efficiency and cooperative nature of a hive culture. The missions, aptly dubbed nanoswarm will be little more than mechanized colonies cooperating in their exploration of the solar system. Each swarm mission can have hundreds or even thousands of cooperating intelligent spacecraft that work in teams. The spacecraft must operate independently for long periods both in teams and individually, as well as have autonomic properties - self-healing, -configuring, -optimizing, and -protecting- to survive the harsh space environment. One swarm mission under concept development for 2020 to 2030 is the Autonomous Nano Technology Swarm (ANTS), in which a thousand picospacecraft, each weighing less than three pounds, will work cooperatively to explore the asteroid belt. Some spacecraft will form teams to catalog asteroid properties, such as mass, density, morphology, and chemical composition, using their respective miniature scientific instruments. Others will communicate with the data gatherers and send updates to mission elements on Earth. For software and systems development, this is uncharted territory that calls for revolutionary techniques.

Truszkowski, Walt↗
NASA NTRS2006

A Predictive Approach to Eliminating Errors in Software Code

NASA s Metrics Data Program Data Repository is a database that stores problem, product, and metrics data. The primary goal of this data repository is to provide project data to the software community. In doing so, the Metrics Data Program collects artifacts from a large NASA dataset, generates metrics on the artifacts, and then generates reports that are made available to the public at no cost. The data that are made available to general users have been sanitized and authorized for publication through the Metrics Data Program Web site by officials representing the projects from which the data originated. The data repository is operated by NASA s Independent Verification and Validation (IV&V) Facility, which is located in Fairmont, West Virginia, a high-tech hub for emerging innovation in the Mountain State. The IV&V Facility was founded in 1993, under the NASA Office of Safety and Mission Assurance, as a direct result of recommendations made by the National Research Council and the Report of the Presidential Commission on the Space Shuttle Challenger Accident. Today, under the direction of Goddard Space Flight Center, the IV&V Facility continues its mission to provide the highest achievable levels of safety and cost-effectiveness for mission-critical software. By extending its data to public users, the facility has helped improve the safety, reliability, and quality of complex software systems throughout private industry and other government agencies. Integrated Software Metrics, Inc., is one of the organizations that has benefited from studying the metrics data. As a result, the company has evolved into a leading developer of innovative software-error prediction tools that help organizations deliver better software, on time and on budget.

Source record↗
NASA NTRS1990

Research in software allocation for advanced manned mission communications and tracking systems

An assessment of the planned processing hardware and software/firmware for the Communications and Tracking System of the Space Station Freedom (SSF) was performed. The intent of the assessment was to determine the optimum distribution of software/firmware in the processing hardware for maximum throughput with minimum required memory. As a product of the assessment process an assessment methodology was to be developed that could be used for similar assessments of future manned spacecraft system designs. The assessment process was hampered by changing requirements for the Space Station. As a result, the initial objective of determining the optimum software/firmware allocation was not fulfilled, but several useful conclusions and recommendations resulted from the assessment. It was concluded that the assessment process would not be completely successful for a system with changing requirements. It was also concluded that memory requirements and hardware requirements were being modified to fit as a consequence of the change process, and although throughput could not be quantitized, potential problem areas could be identified. Finally, inherent flexibility of the system design was essential for the success of a system design with changing requirements. Recommendations resulting from the assessment included development of common software for some embedded controller functions, reduction of embedded processor requirements by hardwiring some Orbital Replacement Units (ORUs) to make better use of processor capabilities, and improvement in communications between software development personnel to enhance the integration process. Lastly, a critical observation was made regarding the software integration tasks did not appear to be addressed in the design process to the degree necessary for successful satisfaction of the system requirements.

Warnagiris, Tom↗
NASA NTRS2018

Building a Community of Open Source Contributors

In 2014, a software development team from NASA's Ames Research Center (ARC), working in collaboration with mission teams at the Jet Propulsion Laboratory (JPL), set out to build a new software system for data visualization for missions. Our functional goal was to build a modular multi-mission software system that empowered users to build and compose their own visualizations of data across mission domains, with no programming required from the users to assemble these displays. Beyond the basic functional requirements for missions, we specified a requirement to make the software open source. This requirement was included to enable flexible use, and reduce or eliminate the proprietary nature of software that can impede collaboration. By making it open source, we also benefit from increased productivity and draw on the innovation of the open source developer community. We want to build and empower a community of contributors and enable broad use both inside and outside the space community to glean insights from cross domain usage. The open source software is called Open Mission Control Technologies, it is available on GitHub (https://github.com/nasa/openmct).

Open Source↗
NASA NTRS2005

An Expert System for Autonomous Spacecraft Control

The Autonomous Sciencecraft Experiment (ASE), part of the New Millennium Space Technology 6 Project, is flying onboard the Earth Orbiter 1 (EO-1) mission. The ASE software enables EO-1 to autonomously detect and respond to science events such as: volcanic activity, flooding, and water freeze/thaw. ASE uses classification algorithms to analyze imagery onboard to detect chang-e and science events. Detection of these events is then used to trigger follow-up imagery. Onboard mission planning software then develops a response plan that accounts for target visibility and operations constraints. This plan is then executed using a task execution system that can deal with run-time anomalies. In this paper we describe the autonomy flight software and how it enables a new paradigm of autonomous science and mission operations. We will also describe the current experiment status and future plans.

utonomy flight software↗
DOE OSTI2024

“Development of Interactive Chemistry in E3SM v2” Final Report (3/1/2023-2/29/2024)

We are pleased to report that the proposed milestones and tasks under this subcontract, or those modified subsequently by the Technical Representative based on project needs, have been met. In general, the accomplishments under this subcontract exceeded the originally proposed milestones and effort, and went from code development to scientific results and high-profile publications, to mission critical software development for the E3SM project.

54 ENVIRONMENTAL SCIENCES↗
NASA NTRS1974

Earth Observatory Satellite system definition study. Report 5: System design and specifications. Volume 4: Mission peculiar spacecraft segment and module specifications

The specifications for the Earth Observatory Satellite (EOS) peculiar spacecraft segment and associated subsystems and modules are presented. The specifications considered include the following: (1) wideband communications subsystem module, (2) mission peculiar software, (3) hydrazine propulsion subsystem module, (4) solar array assembly, and (5) the scanning spectral radiometer.

Source record↗
NASA NTRS1985

Space Shuttle navigation validation

The validation of the guidance, navigation, and control system of the Space Shuttle is explained. The functions of the ascent, on-board, and entry mission phases software of the navigation system are described. The common facility testing, which evaluates the simulations to be used in the navigation validation, is examined. The standard preflight analysis of the operational modes of the navigation software and the post-flight navigation analysis are explained. The conversion of the data into a useful reference frame and the use of orbit parameters in the analysis of the data are discussed. Upon entry the data received are converted to flags, ratios, and residuals in order to evaluate performance and detect errors. Various programs developed to support navigation validation are explained. A number of events that occurred with the Space Shuttle's navigation system are described.

Ragsdale, A.↗