SEARCH · Search NASA

Results for “Team software development”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 307 records · Page 17

All sources NASA NTRS DOE OSTI

NASA NTRS2010

MPS Editor - An Integrated Sequencing Environment

In today's operations environment, the teams are smaller and need to be more efficient while still ensuring the safety and success of the mission. In addition, teams often begin working on a mission in its early development phases and continue on the team through actual operations. For these reasons the operations teams want to be presented with a software environment that integrates multiple needed software applications as well as providing them with context sensitive editing support for entering commands and sequences of commands. At Jet Propulsion Laboratory, the Multi-Mission Planning and Sequencing (MPS) Editor provided by the Multi-Mission Ground Systems and Services (MGSS) supports those operational needs.

Streiffert, Barbara A.↗

NASA NTRS2016

Surface Operations Simulator and Scheduler (SOSS) Presentation

NASA - KAIA (Korea Agency for Infrastructure Technology Advancement) - KARI (Korea Aerospace Research Institute) collaboration surface air traffic management research has been ongoing since May 2015. In the first year collaboration, NASA's SOSS software has been transferred to KAIA and KARI teams to provide fast time simulation capability. Incheon International Airport model has been developed for SOSS.

surface traffic management↗

NASA NTRS2014

Evolution of Software-Only-Simulation at NASA IV and V

Software-Only-Simulations have been an emerging but quickly developing field of study throughout NASA. The NASA Independent Verification Validation (IVV) Independent Test Capability (ITC) team has been rapidly building a collection of simulators for a wide range of NASA missions. ITC specializes in full end-to-end simulations that enable developers, VV personnel, and operators to test-as-you-fly. In four years, the team has delivered a wide variety of spacecraft simulations that have ranged from low complexity science missions such as the Global Precipitation Management (GPM) satellite and the Deep Space Climate Observatory (DSCOVR), to the extremely complex missions such as the James Webb Space Telescope (JWST) and Space Launch System (SLS).This paper describes the evolution of ITCs technologies and processes that have been utilized to design, implement, and deploy end-to-end simulation environments for various NASA missions. A comparison of mission simulators are discussed with focus on technology and lessons learned in complexity, hardware modeling, and continuous integration. The paper also describes the methods for executing the missions unmodified flight software binaries (not cross-compiled) for verification and validation activities.

Embedded↗

NASA NTRSDate not supplied

Autonomous Ocean World Exploration: Advancement of a Software Testbed

The search for life signs and potentially habitable bodies in our solar system and beyond is one of NASA’s top priorities. The prime destinations for such exploration are bodies containing liquid water, such as Jupiter’s moon Europa and Saturn’s moon Enceladus. Initial missions to these “ocean worlds” will be robotic, and because of long communication lags and blackouts, harsh environments, and limited battery life, a high degree of onboard autonomy will be required. To this end NASA has developed the Ocean Worlds Autonomy Testbed for Exploration, Research, and Simulation (OceanWATERS), a software testbed for surface mission autonomy. Under grants from NASA’s Autonomous Robotics Research for Ocean Worlds (ARROW) and Concepts for Ocean worlds Life Detection Technology (COLDTech) programs, collectively 6 research teams at universities and companies across the United States have developed autonomy solutions using OceanWATERS, tackling a variety of surface mission challenges and employing state-of-the-art AI-based solutions. This paper provides a self-contained high-level description of OceanWATERS while detailing enhancements made since its 2020 release. It provides a high-level summary of the projects undertaken by participants in the ARROW and COLDTech programs and how these efforts have helped shape OceanWATERS. Finally, potential future work and directions for the testbed are listed.

K Michael Dalal↗

NASA NTRS2011

FPA Depot - Web Application

Lines of code (LOC) analysis is one of the methods used to measure programmer productivity and estimate schedules of programming projects. The Launch Control System (LCS) had previously used this method to estimate the amount of work and to plan development efforts. The disadvantage of using LOC as a measure of effort is that one can only measure 30% to 35% of the total effort of software projects involves coding [8]. In the application, instead of using the LOC we are using function point for a better estimation of hours in each software to develop. Because of these disadvantages, Jamie Szafran of the System Software Branch of Control And Data Systems (NE-C3) at Kennedy Space Canter developed a web application called Function Point Analysis (FPA) Depot. The objective of this web application is that the LCS software architecture team can use the data to more accurately estimate the effort required to implement customer requirements. This paper describes the evolution of the domain model used for function point analysis as project managers continually strive to generate more accurate estimates.

Avila, Edwin M. Martinez↗

NASA NTRS2018

6DOF Testing of the SLS Inertial Navigation Unit

The Navigation System on the NASA Space Launch System (SLS) Block 1 vehicle performs initial alignment of the Inertial Navigation System (INS) navigation frame through gyrocompass alignment (GCA). Because the navigation architecture for the SLS Block 1 vehicle is a purely inertial system, the accuracy of the achieved orbit relative to mission requirements is very sensitive to initial alignment accuracy. The assessment of this sensitivity and many others via simulation is a part of the SLS Model-Based Design and Model-Based Requirements approach. As a part of the aforementioned, 6DOF Monte Carlo simulation is used in large part to develop and demonstrate verification of program requirements. To facilitate this and the GN&C flight software design process, an SLS-Program-controlled Design Math Model (DMM) of the SLS INS was developed by the SLS Navigation Team. The SLS INS model implements all of the key functions of the hardware-namely, GCA, inertial navigation, and FDIR (Fault Detection, Isolation, and Recovery)-in support of SLS GN&C design requirements verification. Despite the strong sensitivity to initial alignment, GCA accuracy requirements were not verified by test due to program cost and schedule constraints. Instead, the system relies upon assessments performed using the SLS INS model. In order to verify SLS program requirements by analysis, the SLS INS model is verified and validated against flight hardware. In lieu of direct testing of GCA accuracy in support of requirement verification, the SLS Navigation Team proposed and conducted an engineering test to, among other things, validate the GCA performance and overall behavior of the SLS INS model through comparison with test data. This paper will detail dynamic hardware testing of the SLS INS, conducted by the SLS Navigation Team at Marshall Space Flight Center's 6DOF Table Facility, in support of GCA performance characterization and INS model validation. A 6-DOF motion platform was used to produce 6DOF pad twist and sway dynamics while a simulated SLS flight computer communicated with the INS. Tests conducted include an evaluation of GCA algorithm robustness to increasingly dynamic pad environments, an examination of GCA algorithm stability and accuracy over long durations, and a long-duration static test to gather enough data for Allan Variance analysis. Test setup, execution, and data analysis will be discussed, including analysis performed in support of SLS INS model validation.

Geohagan, Kevin↗

NASA NTRSDate not supplied

Digital Lunar Exploration Sites (DLES)

It has been almost 50 years since humans last set foot on the Moon. With NASA’s Artemis program, the United States and its international and commercial partners are embarking on a new endeavor to explore the lunar surface. Before we return, we will have simulated every aspect of these future missions. Many of these models and simulations (M&S) will rely on well-known and commonly-used technologies, some of which trace their origins back to the Apollo program. However, M&S has advanced significantly, as have the underlying computational capabilities. As a result, we are able to model many more aspects of the Artemis vehicles and support systems with significantly improved detail and confidence. Accurately and efficiently modeling the lunar environment will be critical to simulating the Artemis elements and mission activities. This includes characterizing and modeling lunar topography, smaller craters, exposed surface rocks, lunar regolith, surface lighting, and ambient thermal environment. These are all necessary for understanding fundamental behaviors and performance of vehicles and support systems in the lunar environment and are often determining factors in the selection of exploration sites and defining mission profiles. The Astromaterials Research and Exploration Sciences (ARES) team in the Exploration Integration and Science Directorate at NASA’s Johnson Space Center (JSC) and the NASA Exploration Systems Simulations (NExSyS) team in the Simulation and Graphics Branch at JSC are developing and maintaining the Digital Lunar Exploration Sites (DLES) data, documentation, and software packages. This data is being fed directly into a diverse collection of graphics and simulation environments, where it is used to construct the closest known truth for numerous potential Lunar South Pole landing sites. DLES is available to projects across NASA and particularly the Artemis program to support coordinated digital representations of the lunar environment. This paper describes the fundamental need for DLES, the science data sets that are going into DLES, some of the processes used to integrate this data into DLES products, the basic products that constitute DLES, and some examples of DLES in use.

Lunar↗

NASA NTRS2004

Genetic Optimization and Simulation of a Piezoelectric Pipe-Crawling Inspection Robot

Using the DarwinZk development software, a genetic algorithm (GA) was used to design and optimize a pipe-crawling robot for parameters such as mass, power consumption, and joint extension to further the research of the Miniature Inspection Systems Technology (MIST) team. In an attempt to improve on existing designs, a new robot was developed, the piezo robot. The final proposed design uses piezoelectric expansion actuators to move the robot with a 'chimneying' method employed by mountain climbers and greatly improves on previous designs in load bearing ability, pipe traversing specifications, and field usability. This research shows the advantages of GA assisted design in the field of robotics.

Hollinger, Geoffrey A.↗

NASA NTRS1999

Multidisciplinary Optimization Branch Experience Using iSIGHT Software

The Multidisciplinary Optimization (MDO) Branch at NASA Langley Research Center is investigating frameworks for supporting multidisciplinary analysis and optimization research. An optimization framework call improve the design process while reducing time and costs. A framework provides software and system services to integrate computational tasks and allows the researcher to concentrate more on the application and less on the programming details. A framework also provides a common working environment and a full range of optimization tools, and so increases the productivity of multidisciplinary research teams. Finally, a framework enables staff members to develop applications for use by disciplinary experts in other organizations. Since the release of version 4.0, the MDO Branch has gained experience with the iSIGHT framework developed by Engineous Software, Inc. This paper describes experiences with four aerospace applications: (1) reusable launch vehicle sizing, (2) aerospike nozzle design, (3) low-noise rotorcraft trajectories, and (4) acoustic liner design. All applications have been successfully tested using the iSIGHT framework, except for the aerospike nozzle problem, which is in progress. Brief overviews of each problem are provided. The problem descriptions include the number and type of disciplinary codes, as well as all estimate of the multidisciplinary analysis execution time. In addition, the optimization methods, objective functions, design variables, and design constraints are described for each problem. Discussions on the experience gained and lessons learned are provided for each problem. These discussions include the advantages and disadvantages of using the iSIGHT framework for each case as well as the ease of use of various advanced features. Potential areas of improvement are identified.

Padula, S. L.↗

NASA NTRS2000

Ground Data System Risk Mitigation Techniques for Faster, Better, Cheaper Missions

With the advent of faster, cheaper, and better missions, NASA Projects acknowledged that a higher level of risk was inherent and accepted with this approach. It was incumbent however upon each component of the Project whether spacecraft, payload, launch vehicle, or ground data system to ensure that the mission would nevertheless be an unqualified success. The Small Explorer (SMEX) program's ground data system (GDS) team developed risk mitigation techniques to achieve these goals starting in 1989. These techniques have evolved through the SMEX series of missions and are practiced today under the Triana program. These techniques are: (1) Mission Team Organization--empowerment of a closeknit ground data system team comprising system engineering, software engineering, testing, and flight operations personnel; (2) Common Spacecraft Test and Operational Control System--utilization of the pre-launch spacecraft integration system as the post-launch ground data system on-orbit command and control system; (3) Utilization of operations personnel in pre-launch testing--making the flight operations team an integrated member of the spacecraft testing activities at the beginning of the spacecraft fabrication phase; (4) Consolidated Test Team--combined system, mission readiness and operations testing to optimize test opportunities with the ground system and spacecraft; and (5). Reuse of Spacecraft, Systems and People--reuse of people, software and on-orbit spacecraft throughout the SMEX mission series. The SMEX ground system development approach for faster, cheaper, better missions has been very successful. This paper will discuss these risk management techniques in the areas of ground data system design, implementation, test, and operational readiness.

Catena, John J.↗

NASA NTRS1998

[MODIS Investigation]

The objectives of the last six months were: Continue analysis of Hawaii Ocean Time-series (HOT) bio-optical mooring data, Recover instrumentation from JGOFS cruises in the Southern Ocean and analyze data Maintain documentation of MOCEAN algorithms and software for use by MOCEAN and GLI teams Continue chemostat experiments on the relationship of fluorescence quantum yield to environmental factors. Continue to develop and expand browser-based information system for in situ bio-optical data Work Analysis of Field Data from Hawaii We are continuing to analyze bio-optical data collected at the Hawaii Ocean Time Series mooring. The HOT bio-optical mooring was recovered in May 1998. After retrieving the data, the sensor package was serviced and redeployed. We now have over 18 months of data. These are being analyzed as part of a larger study of mesoscale processes at this JGOFS time series site. We have had some failures in the data logger which have affected the fluorescence channels. These are being repaired. We also had an instrument housing failure, and minor modifications have been made to avoid subsequent problems. In addition, Ricardo Letelier is funded as part of the SeaWiFS calibrator/validation effort (through a subcontract from the University of Hawaii, Dr. John Porter), and he is collecting bio-optical and fluorescence data as part of the HOT activity.

Abbott, Mark R.↗

NASA NTRS2003

Transient Simulation of the Integrated Powerhead Demonstrator (IPD) Rocket Engine

The IPD rocket engine is the product of a joint Air Force/NASA program to demonstrate the concept of a full-flow staged combustion power cycle. In this type of rocket engine cycle, both the entire fuel flow and the entire oxidizer flow are combusted in one of two pre-bumers and used to drive two turbopumps, thus utilizing the flow work of the total propellant flow. The basis of the IPD engine program relies on integrating newly developed and pre-existing hardware to demonstrate the component and material technologies to make this concept feasible, while simultaneously saving development time and costs. To provide insight to the project team and contractors during engine development and test phases, the engine system was modeled at MSFC using the Rocket Engine Transient Simulation (ROCETS) software to analyze system performance and determine component integration issues. The ROCETS software is used extensively a MSFC to perform steady-state power-balances and transient simulations of thermodynamic power and general fluid systems. The software is favored for its capability to solve large systems of non-linear equations, its librarie of fluid properties and flow devices, its flexibility to modify existing code to improve the physics-derived approximations of real fluid thermodynamic behavior, and the ability to add unique system constraints. The purpose of this paper is to present the methodology used to model the IPD engine system, detail the pitfalls encountered with the software, and explain the approximations made to more accurately represent engine component and fluid behavior. Engine system performance output from the model will be presented and explained in comparison with real fluid and component behavior.

Guidos, Mike↗

NASA NTRS2018

Software System for the Mars 2020 Mission Sampling and Caching Testbeds

The development of the Sampling and Caching Subsystem (SCS) of the Mars 2020 Rover Mission is highly dependent on testing of prototype hardware and software operating in explicit conditions as part of integrated testbeds. To achieve relevant integration of hardware and software while maintaining rapid algorithm development capabilities and high testing throughput, the Controls and Autonomy for Sample Acquisition and Handling (CASAH) software system was developed. CASAH is an implementation of the Intelligent Robotics System Architecture (IRSA),which mimics JPL Flight Software (FSW) in that it is divided into hierarchical modules that run separate processes that communicate via message passing, each module is assigned an owner that is a single developer, and the operator initiates requests via a text-based interface that interprets sequences of commands.IRSA enables a modular breakdown of CASAH that follows that of 2020 Flight Software,so developers can take an algorithm from a module in CASAH and re-code it into the same module in FSW. As deployment of CASAH has grown to ten testbeds - each with different hardware and objectives - bottom-up design decisions have been intentionally made to keep the system lightweight and maintainable by a very small team. To date, CASAH has been used to run 1393 different tests. This work describes CASAH, the testbeds and functionality it supports, the tools used to manage the development and sharing of code, and the features of the software. Lessons learned over the past three years of development and deployment are provided.

Vieira, Peter↗

NASA NTRS2016

EVA Wiki - Transforming Knowledge Management for EVA Flight Controllers and Instructors

The EVA (Extravehicular Activity) Wiki was recently implemented as the primary knowledge database to retain critical knowledge and skills in the EVA Operations group at NASA's Johnson Space Center by ensuring that information is recorded in a common, searchable repository. Prior to the EVA Wiki, information required for EVA flight controllers and instructors was scattered across different sources, including multiple file share directories, SharePoint, individual computers, and paper archives. Many documents were outdated, and data was often difficult to find and distribute. In 2011, a team recognized that these knowledge management problems could be solved by creating an EVA Wiki using MediaWiki, a free and open-source software developed by the Wikimedia Foundation. The EVA Wiki developed into an EVA-specific Wikipedia on an internal NASA server. While the technical implementation of the wiki had many challenges, the one of the biggest hurdles came from a cultural shift. Like many enterprise organizations, the EVA Operations group was accustomed to hierarchical data structures and individually-owned documents. Instead of sorting files into various folders, the wiki searches content. Rather than having a single document owner, the wiki harmonized the efforts of many contributors and established an automated revision control system. As the group adapted to the wiki, the usefulness of this single portal for information became apparent. It transformed into a useful data mining tool for EVA flight controllers and instructors, and also for hundreds of other NASA and contract employees. Program managers, engineers, astronauts, flight directors, and flight controllers in differing disciplines now have an easier-to-use, searchable system to find EVA data. This paper presents the benefits the EVA Wiki has brought to NASA's EVA community, as well as the cultural challenges it had to overcome.

Johnston, Stephanie↗

NASA NTRS2015

Dynamic Emulation of NASA Missions for IVandV: A Case Study of JWST and SLS

Software-Only-Simulations are an emerging but quickly developing field of study throughout NASA. The NASA Independent Verification Validation (IVV) Independent Test Capability (ITC) team has been rapidly building a collection of simulators for a wide range of NASA missions. ITC specializes in full end-to-end simulations that enable developers, VV personnel, and operators to test-as-you-fly. In four years, the team has delivered a wide variety of spacecraft simulations ranging from low complexity science missions such as the Global Precipitation Management (GPM) satellite and the Deep Space Climate Observatory (DSCOVR), to the extremely complex missions such as the James Webb Space Telescope (JWST) and Space Launch System (SLS).

Emulation↗

NASA NTRS2016

EVA Wiki - Transforming Knowledge Management for EVA Flight Controllers and Instructors

The EVA Wiki was recently implemented as the primary knowledge database to retain critical knowledge and skills in the EVA Operations group at NASA's Johnson Space Center by ensuring that information is recorded in a common, easy to search repository. Prior to the EVA Wiki, information required for EVA flight controllers and instructors was scattered across different sources, including multiple file share directories, SharePoint, individual computers, and paper archives. Many documents were outdated, and data was often difficult to find and distribute. In 2011, a team recognized that these knowledge management problems could be solved by creating an EVA Wiki using MediaWiki, a free and open-source software developed by the Wikimedia Foundation. The EVA Wiki developed into an EVA-specific Wikipedia on an internal NASA server. While the technical implementation of the wiki had many challenges, one of the biggest hurdles came from a cultural shift. Like many enterprise organizations, the EVA Operations group was accustomed to hierarchical data structures and individually-owned documents. Instead of sorting files into various folders, the wiki searches content. Rather than having a single document owner, the wiki harmonized the efforts of many contributors and established an automated revision controlled system. As the group adapted to the wiki, the usefulness of this single portal for information became apparent. It transformed into a useful data mining tool for EVA flight controllers and instructors, as well as hundreds of others that support the EVA. Program managers, engineers, astronauts, flight directors, and flight controllers in differing disciplines now have an easier-to-use, searchable system to find EVA data. This paper presents the benefits the EVA Wiki has brought to NASA's EVA community, as well as the cultural challenges it had to overcome.

Johnston, Stephanie S.↗

NASA NTRS2016

EVA Wiki - Transforming Knowledge Management for EVA Flight Controllers and Instructors

The EVA Wiki was recently implemented as the primary knowledge database to retain critical knowledge and skills in the EVA Operations group at NASA's Johnson Space Center by ensuring that information is recorded in a common, easy to search repository. Prior to the EVA Wiki, information required for EVA flight controllers and instructors was scattered across different sources, including multiple file share directories, SharePoint, individual computers, and paper archives. Many documents were outdated, and data was often difficult to find and distribute. In 2011, a team recognized that these knowledge management problems could be solved by creating an EVA Wiki using MediaWiki, a free and open-source software developed by the Wikimedia Foundation. The EVA Wiki developed into an EVA-specific Wikipedia on an internal NASA server. While the technical implementation of the wiki had many challenges, one of the biggest hurdles came from a cultural shift. Like many enterprise organizations, the EVA Operations group was accustomed to hierarchical data structures and individually-owned documents. Instead of sorting files into various folders, the wiki searches content. Rather than having a single document owner, the wiki harmonized the efforts of many contributors and established an automated revision controlled system. As the group adapted to the wiki, the usefulness of this single portal for information became apparent. It transformed into a useful data mining tool for EVA flight controllers and instructors, as well as hundreds of others that support EVA. Program managers, engineers, astronauts, flight directors, and flight controllers in differing disciplines now have an easier-to-use, searchable system to find EVA data. This paper presents the benefits the EVA Wiki has brought to NASA's EVA community, as well as the cultural challenges it had to overcome.

Johnston, Stephanie S.↗

NASA NTRS2016

UAV Research at NASA Langley: Towards Safe, Reliable, and Autonomous Operations

Unmanned Aerial Vehicles (UAV) are fundamental components in several aspects of research at NASA Langley, such as flight dynamics, mission-driven airframe design, airspace integration demonstrations, atmospheric science projects, and more. In particular, NASA Langley Research Center (Langley) is using UAVs to develop and demonstrate innovative capabilities that meet the autonomy and robotics challenges that are anticipated in science, space exploration, and aeronautics. These capabilities will enable new NASA missions such as asteroid rendezvous and retrieval (ARRM), Mars exploration, in-situ resource utilization (ISRU), pollution measurements in historically inaccessible areas, and the integration of UAVs into our everyday lives all missions of increasing complexity, distance, pace, and/or accessibility. Building on decades of NASA experience and success in the design, fabrication, and integration of robust and reliable automated systems for space and aeronautics, Langley Autonomy Incubator seeks to bridge the gap between automation and autonomy by enabling safe autonomous operations via onboard sensing and perception systems in both data-rich and data-deprived environments. The Autonomy Incubator is focused on the challenge of mobility and manipulation in dynamic and unstructured environments by integrating technologies such as computer vision, visual odometry, real-time mapping, path planning, object detection and avoidance, object classification, adaptive control, sensor fusion, machine learning, and natural human-machine teaming. These technologies are implemented in an architectural framework developed in-house for easy integration and interoperability of cutting-edge hardware and software.

Davila, Carlos G.↗