Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “custom 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 847 records · Page 47
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

Simulation Technology at NASA

NASA Ames Research Center is home to several high-fidelity research flight and air-traffic control simulation facilities which, together with an experienced workforce, produce high-quality research data and findings that have proven to be applicable in the real world. These assets include the Vertical Motion Simulator (VMS), Crew Vehicle Systems Research Facility (CVSRF), Future Flight Central (FFC) air traffic control tower simulator, and several air-traffic control (ATC) simulators. The VMS combines a high-fidelity simulation capability with an adaptable simulation environment, enabling customization for numerous human-in-the-loop research applications. The distinctive feature of the VMS is its unparalleled large amplitude, high-fidelity motion capability. In over 30 years of continuous operation, the VMS has contributed significantly to the body of knowledge in a range of disciplines directly benefiting several aerospace programs and flight safety, including the design and development of flight control systems for the Joint Strike Fighter, Space Shuttle Orbiter, and rotorcraft. It continues to be used for researching new vehicle configurations, vehicle control and safety, transfer-of-training, etc., by NASA, other government agencies, and Industry.The CVSRF includes two motion-based flight simulators: a Boeing 747-400 full flight simulator and the reconfigurable Advanced Concepts Flight Simulator (ACFS). These simulators are primarily used to research air-traffic management concepts and procedures, advanced navigation and avionics concepts, and cockpit human factors. FFC is a full-sized control tower simulator with a 360-degree external field-of-view display system and reconfigurable system architecture. FFC and the ATC simulators are used for testing air-traffic management automation and decision support tools and demonstrate their feasibility in a realistic environment prior to technology transfer for implementation in the National Airspace System (NAS).To support integrated simulations and flight-tests for NASA's Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) Project, NASA developed a distributed test environment incorporating Live, Virtual, Constructive, (LVC) concepts. Development of the software enabling the LVC is conducted primarily at the Distributed Simulation Research Lab (DSRL) at NASA Ames. The LVC components provide the core infrastructure supporting simulation of UAS operations by integrating live and virtual aircraft in a realistic air traffic environment. This provides the ability to conduct tests more efficiently by promoting the use of existing distributed assets. The LVC infrastructure was used in several human-in-the-loop simulations to evaluate acceptance of Detect and Avoid (DAA) advisories used by UAS pilots to maintain well clear of other virtual traffic and to negotiate maneuvers with air traffic control. It is currently being used to support testing of self-separation algorithms between unmanned and manned aircraft in live flight. Further simulations with more comprehensive air traffic scenarios mixing live and virtual aircraft is planned.In the current fiscal environment, maintaining and upgrading these high-fidelity simulation assets and retaining the skilled workforce necessary to meet future research needs is the primary non-technical challenge.

CVSRF↗
NASA NTRS2014

Geostationary Coastal and Air Pollution Events (GeoCAPE) Wide Angle Spectrometer (WAS)

The GeoCAPE Wide Angle Spectrometer (WAS) Study was a revisit of the COEDI Study from 2012. The customer primary goals were to keep mass, volume and cost to a minimum while meeting the science objectives and maximizing flight opportunities by fitting on the largest number of GEO accommodations possible. Riding on a commercial GEO satellite minimizes total mission costs. For this study, it is desired to increase the coverage rate,km2min, while maintaining ground sample size, 375m, and spectral resolution, 0.4-0.5nm native resolution. To be able to do this, the IFOV was significantly increased, hence the wide angle moniker. The field of view for COEDI was +0.6 degrees or (2048) 375m ground pixels. The WAS Threshold (the IDL study baseline design) is +2.4 degrees IDL study baseline design) is +2.4 degrees.

pointing and jitter↗
NASA NTRS2002

"We Freeze to Please": A History of NASA's Icing Research Tunnel and the Quest for Flight Safety

The formation of ice on wings and other control surfaces of airplanes is one of the oldest and most vexing problems that aircraft engineers and scientists continue to face. While no easy, comprehensive answers exist, the staff at NASAs Icing Research Tunnel (IRT) at the Glenn Research Center in Cleveland has done pioneering work to make flight safer for experimental, commercial, and military customers. The National Advisory Committee for Aeronautics (NACA) initiated government research on aircraft icing in the 1930s at its Langley facility in Virginia. Icing research shifted to the NACA's Cleveland facility in the 1940s. Initially there was little focus on icing at either location, as these facilities were more concerned with aerodynamics and engine development. With several high-profile fatal crashes of air mail carriers, however, the NACA soon realized the need for a leading research facility devoted to icing prevention and removal. The IRT began operation in 1944 and, despite renovations and periodic attempts to shut it down, has continued to function productively for almost 60 years. In part because icing has proved so problematic over time, IRT researchers have been unusually open-minded in experimenting with a wide variety of substances, devices, and techniques. Early icing prevention experiments involved grease, pumping hot engine exhaust onto the wings, glycerin soap, mechanical and inflatable "boots," and even corn syrup. The IRT staff also looked abroad for ideas and later tried a German and Soviet technique of electromagnetism, to no avail. More recently, European polymer fluids have been more promising. The IRT even periodically had "amateur nights" in which a dentist's coating for children's teeth proved unequal to the demands of super-cooled water droplets blown at 100 miles per hour. Despite many research dead-ends, IRT researchers have achieved great success over the years. They have developed important computer models, such as the LEWICE software, and made significant contributions to prevent ice buildup on turbine-powered commercial aircraft, helicopters, and military planes.

Leary, William M.↗
NASA NTRS2018

Next-Generation NASA Earth-Orbiting Relay Satellites: Fusing Optical and Microwave Communications

NASA is currently considering architectures and concepts for the generation of relay satellites that will replace the Tracking and Data Relay Satellite (TDRS) constellation, which has been flying since 1983. TDRS-M, the last of the second TDRS generation, launched in August 2017, extending the life of the TDRS constellation beyond 2030. However, opportunities exist to re-engineer the concepts of geosynchronous Earth relay satellites. The needs of the relay satellite customers have changed dramatically over the last 34 years since the first TDRS launch. There is a demand for greater bandwidth as the availability of the traditional RF spectrum for space communications diminishes and the demand for ground station access grows. The next generation of NASA relay satellites will provide for operations that have factored in these new constraints. In this paper, we describe a heterogeneous constellation of geosynchronous relay satellites employing optical and RF communications. The new constellation will enable new optical communications services formed by user-to-space relay, space relay-to-space relay and space relay-to-ground links. It will build upon the experience from the Lunar Laser Communications Demonstration from 2013 and the Laser Communications Relay Demonstration to be launched in 2019.Simultaneous to establishment of the optical communications space segment, spacecraft in the TDRS constellation will be replaced with RF relay satellites with targeted subsets of the TDRS capabilities. This disaggregation of the TDRS service model will allow for flexibility in replenishing the needs of legacy users as well as addition of new capabilities for future users. It will also permit the U.S. government access to launch capabilities such as rideshare and to hosted payloads that were not previously available.In this paper, we also explore how the next generation of Earth relay satellites provides a significant boost in the opportunities for commercial providers to the communications space segment. For optical communications, the backbone of this effort is adoption of commercial technologies from the terrestrial high-bandwidth telecommunications industry into optical payloads. For RF communications, the explosion of software-defined radio, high-speed digital signal processing technologies and networking from areas such as 5G multicarrier will be important. Future commercial providers will not be limited to a small set of large aerospace companies. Ultimately, entirely government-owned and -operated satellite communications will phase out and make way for commercial business models that satisfy NASA's satellite communications requirements. The competition being provided by new entrants in the space communications business may result in a future in which all NASA communications needs can be satisfied commercially.

Space Communications↗
NASA NTRS2018

Next-Generation NASA Earth-Orbiting Relay Satellites: Fusing Microwave and Optical Communications

NASA is currently considering architectures and concepts for the generation of relay satellites that will replace the Tracking and Data Relay Satellite (TDRS) constellation, which has been flying since 1983. TDRS-M, the last of the second TDRS generation, launched in August 2017, extending the life of the TDRS constellation beyond 2030. However, opportunities exist to re-engineer the concepts of geosynchronous Earth relay satellites. The needs of the relay satellite customers have changed dramatically over the last 34 years since the first TDRS launch. There is a demand for greater bandwidth as the availability of the traditional RF spectrum for space communications diminishes and the demand for ground station access grows. The next generation of NASA relay satellites will provide for operations that have factored in these new constraints. In this paper, we describe a heterogeneous constellation of geosynchronous relay satellites employing optical and RF communications. The new constellation will enable new optical communications services formed by user-to-space relay, space relay-to-space relay and space relay-to-ground links. It will build upon the experience from the Lunar Laser Communications Demonstration from 2013 and the Laser Communications Relay Demonstration to be launched in 2019.Simultaneous to establishment of the optical communications space segment, spacecraft in the TDRS constellation will be replaced with RF relay satellites with targeted subsets of the TDRS capabilities. This disaggregation of the TDRS service model will allow for flexibility in replenishing the needs of legacy users as well as addition of new capabilities for future users. It will also permit the U.S. government access to launch capabilities such as rideshare and to hosted payloads that were not previously available. In this paper, we also explore how the next generation of Earth relay satellites provides a significant boost in the opportunities for commercial providers to the communications space segment. For optical communications, the backbone of this effort is adoption of commercial technologies from the terrestrial high-bandwidth telecommunications industry into optical payloads. For RF communications, the explosion of software-defined radio, high-speed digital signal processing technologies and networking from areas such as 5G multicarrier will be important. Future commercial providers will not be limited to a small set of large aerospace companies. Ultimately, entirely government-owned and -operated satellite communications will phase out and make way for commercial business models that satisfy NASAs satellite communications requirements. The competition being provided by new entrants in the space communications business may result in a future in which all NASA communications needs can be satisfied commercially.

Space Communications↗
NASA NTRS2018

Addressing Human Error in International Space Station Flight Control Teams: Advances in Ground Training for Science Operators

In flight control, as with any human in the loop system, operator error is an inevitable reality. On the International Space Station (ISS) where crew time and physical resources are precious and often irreplaceable, operator errors can result in significant, irreversible consequences. Flight controllers at the Payload Operations Integration Center (POIC) located at NASA’s Marshall Space Flight Center (MSFC) in Huntsville, Alabama know this reality well. At the POIC, operator errors can be caused by a variety of factors, from poor hardware or software design to environmental factors such as time pressure or fatigue. The most difficult errors to address, however, are those which result from ineffective teamwork.Academic research in teamwork has resulted in the identification of many factors which make cross-functional teaming difficult, including leadership, trust building, and communication challenges. These factors, especially when combined with the challenging environmental factors flight control teams must contend with daily, make the goal of minimizing operator errors in payload operations challenging to achieve. To address such teamwork errors, trainers at the POIC have drawn best practices from high reliability industries such as commercial aviation, healthcare, and nuclear power plants, as well as from our sister ISS control center in Houston, Texas, to develop and institute a new training program focused specifically on teamwork skills.This training program, called the Team Skills Curriculum, is based on the concept of Crew Resource Management (CRM) which was developed by NASA in the 1970s for the commercial aviation industry in response to a series of aviation disasters resulting from ineffective teamwork. CRM was later tailored by the Johnson Space Center (JSC) for use in astronaut and flight control training. The result, called Space Flight Resource Management (SFRM) was formally introduced into manned spaceflight training in the late 90s. SFRM has evolved over the years, but the focus has remained on helping operators develop the skills needed to work as part of an effective team. Using these concepts as well as the latest research in cross-functional teaming and data on specific errors occurring at the POIC, trainers in the integrated flight control training branch created a custom training program for both new and certified payload operations specialists.

Harris, Samantha S.↗
NASA NTRS2009

Efficient Multidisciplinary Analysis Approach for Conceptual Design of Aircraft with Large Shape Change

The conceptual and preliminary design processes for aircraft with large shape changes are generally difficult and time-consuming, and the processes are often customized for a specific shape change concept to streamline the vehicle design effort. Accordingly, several existing reports show excellent results of assessing a particular shape change concept or perturbations of a concept. The goal of the current effort was to develop a multidisciplinary analysis tool and process that would enable an aircraft designer to assess several very different morphing concepts early in the design phase and yet obtain second-order performance results so that design decisions can be made with better confidence. The approach uses an efficient parametric model formulation that allows automatic model generation for systems undergoing radical shape changes as a function of aerodynamic parameters, geometry parameters, and shape change parameters. In contrast to other more self-contained approaches, the approach utilizes off-the-shelf analysis modules to reduce development time and to make it accessible to many users. Because the analysis is loosely coupled, discipline modules like a multibody code can be easily swapped for other modules with similar capabilities. One of the advantages of this loosely coupled system is the ability to use the medium- to high-fidelity tools early in the design stages when the information can significantly influence and improve overall vehicle design. Data transfer among the analysis modules are based on an accurate and automated general purpose data transfer tool. In general, setup time for the integrated system presented in this paper is 2-4 days for simple shape change concepts and 1-2 weeks for more mechanically complicated concepts. Some of the key elements briefly described in the paper include parametric model development, aerodynamic database generation, multibody analysis, and the required software modules as well as examples for a telescoping wing, a folding wing, and a bat-like wing. The paper also includes the verification of a medium-fidelity aerodynamic tool used for the aerodynamic database generation with a steady and unsteady high-fidelity CFD analysis tool for a folding wing example.

Chwalowski, Pawel↗
NASA NTRS2007

Integrated Aerodynamic/Structural/Dynamic Analyses of Aircraft with Large Shape Changes

The conceptual and preliminary design processes for aircraft with large shape changes are generally difficult and time-consuming, and the processes are often customized for a specific shape change concept to streamline the vehicle design effort. Accordingly, several existing reports show excellent results of assessing a particular shape change concept or perturbations of a concept. The goal of the current effort was to develop a multidisciplinary analysis tool and process that would enable an aircraft designer to assess several very different morphing concepts early in the design phase and yet obtain second-order performance results so that design decisions can be made with better confidence. The approach uses an efficient parametric model formulation that allows automatic model generation for systems undergoing radical shape changes as a function of aerodynamic parameters, geometry parameters, and shape change parameters. In contrast to other more self-contained approaches, the approach utilizes off-the-shelf analysis modules to reduce development time and to make it accessible to many users. Because the analysis is loosely coupled, discipline modules like a multibody code can be easily swapped for other modules with similar capabilities. One of the advantages of this loosely coupled system is the ability to use the medium-to high-fidelity tools early in the design stages when the information can significantly influence and improve overall vehicle design. Data transfer among the analysis modules are based on an accurate and automated general purpose data transfer tool. In general, setup time for the integrated system presented in this paper is 2-4 days for simple shape change concepts and 1-2 weeks for more mechanically complicated concepts. Some of the key elements briefly described in the paper include parametric model development, aerodynamic database generation, multibody analysis, and the required software modules as well as examples for a telescoping wing, a folding wing, and a bat-like wing.

Samareh, Jamshid A.↗
NASA NTRS2010

Reconfigurable Hardware for Compressing Hyperspectral Image Data

High-speed, low-power, reconfigurable electronic hardware has been developed to implement ICER-3D, an algorithm for compressing hyperspectral-image data. The algorithm and parts thereof have been the topics of several NASA Tech Briefs articles, including Context Modeler for Wavelet Compression of Hyperspectral Images (NPO-43239) and ICER-3D Hyperspectral Image Compression Software (NPO-43238), which appear elsewhere in this issue of NASA Tech Briefs. As described in more detail in those articles, the algorithm includes three main subalgorithms: one for computing wavelet transforms, one for context modeling, and one for entropy encoding. For the purpose of designing the hardware, these subalgorithms are treated as modules to be implemented efficiently in field-programmable gate arrays (FPGAs). The design takes advantage of industry- standard, commercially available FPGAs. The implementation targets the Xilinx Virtex II pro architecture, which has embedded PowerPC processor cores with flexible on-chip bus architecture. It incorporates an efficient parallel and pipelined architecture to compress the three-dimensional image data. The design provides for internal buffering to minimize intensive input/output operations while making efficient use of offchip memory. The design is scalable in that the subalgorithms are implemented as independent hardware modules that can be combined in parallel to increase throughput. The on-chip processor manages the overall operation of the compression system, including execution of the top-level control functions as well as scheduling, initiating, and monitoring processes. The design prototype has been demonstrated to be capable of compressing hyperspectral data at a rate of 4.5 megasamples per second at a conservative clock frequency of 50 MHz, with a potential for substantially greater throughput at a higher clock frequency. The power consumption of the prototype is less than 6.5 W. The reconfigurability (by means of reprogramming) of the FPGAs makes it possible to effectively alter the design to some extent to satisfy different requirements without adding hardware. The implementation could be easily propagated to future FPGA generations and/or to custom application-specific integrated circuits.

Aranki, Nazeeh↗
NASA NTRS2002

Ground Operations of the ISS GNC Babb-Mueller Atmospheric Density Model

The ISS GNC system was updated recently with a new software release that provides onboard state determination capability. Prior to this release, only the Russian segment maintained and propagated the onboard state, which was periodically updated through Russian ground tracking. The new software gives the US segment the capability for maintaining the onboard state, and includes new GPS and state vector propagation capabilities. Part of this software package is an atmospheric density model based on the Babb-Mueller algorithm. Babb-Mueller efficiently mimics a full analytical density model, such as the Jacchia model. While lacchia is very robust and is used in the Mission Control Center, it is too computationally intensive for use onboard. Thus, Babb-Mueller was chosen as an alternative. The onboard model depends on a set of calibration coefficients that produce a curve fit to the lacchia model. The ISS GNC system only maintains one set of coefficients onboard, so a new set must be uplinked by controllers when the atmospheric conditions change. The onboard density model provides a real-time density value, which is used to calculate the drag experienced by the ISS. This drag value is then incorporated into the onboard propagation of the state vector. The propagation of the state vector, and therefore operation of the BabbMueller algorithm, will be most critical when GPS updates and secondary state vector sources fail. When GPS is active, the onboard state vector will be updated every ten seconds, so the propagation error is irrelevant. When GPS is inactive, the state vector must be updated at least every 24 hours, based on current protocol. Therefore, the Babb-Mueller coefficients must be accurate enough to fulfill the state vector accuracy requirements for at least one day. A ground operations concept was needed in order to manage both the on board Babb-Mueller density model and the onboard state quality. The Babb-Mueller coefficients can be determined operationally in two ways. The first method is to calibrate the coefficients in real-time, where a set of custom coefficients is generated for the real-time atmospheric conditions. The second approach is to generate pre-canned sets of coefficients that encompass the expected atmospheric conditions over the lifetime of the vehicle. These predetermined sets are known as occurrences. Even though a particular occurrence will not match the true atmospheric conditions, the error will be constrained by limiting the breadth of each occurrence. Both methods were investigated and the advantages and disadvantages of each were considered. The choice between these implementations was a trade-off between the additional accuracy of the real-time calibration and the simpler development for the approach using occurrences. The operations concept for the frequency of updates was also explored, and depends on the deviation in solar flux that still achieves the necessary accuracy of the coefficients. This was determined based on historical solar flux trends. This analysis resulted in an accurate and reliable implementation of the Babb-Mueller coefficients and how flight controllers use them during realtime operations.

Brogan, Jonathan↗
NASA NTRS2019

Prototyping Operational Autonomy for Space Traffic Management

Current state of the art in Space Traffic Management (STM) relies on a handful of providers for surveillance and collision prediction, and manual coordination between operators. Neither is scalable to support the expected 10x increase in spacecraft population in less than 10 years, nor does it support automated manuever planning. We present a software prototype of an STM architecture based on open Application Programming Interfaces (APIs), drawing on previous work by NASA to develop an architecture for low-altitude Unmanned Aerial System Traffic Management. The STM architecture is designed to provide structure to the interactions between spacecraft operators, various regulatory bodies, and service suppliers, while maintaining flexibility of these interactions and the ability for new market participants to enter easily. Autonomy is an indispensable part of the proposed architecture in enabling efficient data sharing, coordination between STM participants and safe flight operations. Examples of autonomy within STM include syncing multiple non-authoritative catalogs of resident space objects, or determining which spacecraft maneuvers when preventing impending conjunctions between multiple spacecraft. The STM prototype is based on modern micro-service architecture adhering to OpenAPI standards and deployed in industry standard Docker containers, facilitating easy communication between different participants or services. The system architecture is designed to facilitate adding and replacing services with minimal disruption. We have implemented some example participant services (e.g. a space situational awareness provider/SSA, a conjunction assessment supplier/CAS, an automated maneuver advisor/AMA) within the prototype. Different services, with creative algorithms folded into then, can fulfil similar functional roles within the STM architecture by flexibly connecting to it using pre-defined APIs and data models, thereby lowering the barrier to entry of new players in the STM marketplace. We demonstrate the STM prototype on a multiple conjunction scenario with multiple maneuverable spacecraft, where an example CAS and AMA can recommend optimal maneuvers to the spacecraft operators, based on a predefined reward function. Such tools can intelligently search the space of potential collision avoidance maneuvers with varying parameters like lead time and propellant usage, optimize a customized reward function, and be implemented as a scheduling service within the STM architecture. The case study shows an example of autonomous maneuver planning is possible using the API-based framework. As satellite populations and predicted conjunctions increase, an STM architecture can facilitate seamless information exchange related to collision prediction and mitigation among various service applications on different platforms and servers. The availability of such an STM network also opens up new research topics on satellite maneuver planning, scheduling and negotiation across disjoint entities.

space traffic management↗
NASA NTRS2014

Geostationary Coastal and Air Pollution Events (GeoCAPE) Filter Radiometer (FR)

The GeoCAPE Filter Radiometer (FR) Study is a different instrument type than all of the previous IDL GeoCape studies. The customer primary goals are to keep mass, volume and cost to a minimum while meeting the science objectives and maximizing flight opportunities by fitting on the largest number of GEO accommodations possible. Minimize total mission costs by riding on a commercial GEO satellite. For this instrument type, the coverage rate, km 2 min, was significantly increased while reducing the nadir ground sample size to 250m. This was accomplished by analyzing a large 2d area for each integration period. The field of view will be imaged on a 4k x 4k detector array of 15 micrometer pixels. Each ground pixel is spread over 2 x 2 detector pixels so the instantaneous field of view (IFOV) is 2048 X 2048 ground pixels. The baseline is, for each field of view 50 sequential snapshot images are taken, each with a different filter, before indexing the scan mirror to the next IFOV. A delta would be to add additional filters.

Geo Cape↗
NASA NTRS2014

Transition Marshall Space Flight Center Wind Profiler Splicing Algorithm to Launch Services Program Upper Winds Tool

NASAs LSP customers and the future SLS program rely on observations of upper-level winds for steering, loads, and trajectory calculations for the launch vehicles flight. On the day of launch, the 45th Weather Squadron (45 WS) Launch Weather Officers (LWOs) monitor the upper-level winds and provide forecasts to the launch team via the AMU-developed LSP Upper Winds tool for launches at Kennedy Space Center (KSC) and Cape Canaveral Air Force Station. This tool displays wind speed and direction profiles from rawinsondes released during launch operations, the 45th Space Wing 915-MHz Doppler Radar Wind Profilers (DRWPs) and KSC 50-MHz DRWP, and output from numerical weather prediction models.The goal of this task was to splice the wind speed and direction profiles from the 45th Space Wing (45 SW) 915-MHz Doppler radar Wind Profilers (DRWPs) and KSC 50-MHz DRWP at altitudes where the wind profiles overlap to create a smooth profile. In the first version of the LSP Upper Winds tool, the top of the 915-MHz DRWP wind profile and the bottom of the 50-MHz DRWP were not spliced, sometimes creating a discontinuity in the profile. The Marshall Space Flight Center (MSFC) Natural Environments Branch (NE) created algorithms to splice the wind profiles from the two sensors to generate an archive of vertically complete wind profiles for the SLS program. The AMU worked with MSFC NE personnel to implement these algorithms in the LSP Upper Winds tool to provide a continuous spliced wind profile.The AMU transitioned the MSFC NE algorithms to interpolate and fill data gaps in the data, implement a Gaussian weighting function to produce 50-m altitude intervals in each sensor, and splice the data together from both DRWPs. They did so by porting the MSFC NE code written with MATLAB software into Microsoft Excel Visual Basic for Applications (VBA). After testing the new algorithms in stand-alone VBA modules, the AMU replaced the existing VBA code in the LSP Upper Winds tool with the new algorithms. They then tested the code in the LSP Upper Winds tool with archived data. The tool will be delivered to the 45 WS after the 50-MHz DRWP upgrade is complete and the tool is tested with real-time data. The 50-MHz DRWP upgrade is expected to be finished in October 2014.

Space launch↗
NASA NTRS2005

Rover Sequencing and Visualization Program

The Rover Sequencing and Visualization Program (RSVP) is the software tool for use in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight-code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover-predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (IDD) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities. Thus, RSVP, being highly data driven, may be tailored to other missions with minimal effort. In addition, RSVP uses a distributed, message-passing architecture to allow multitasking, and collaborative visualization and sequence development by scattered team members.

Cooper, Brian↗
NASA NTRS2005

Update on Rover Sequencing and Visualization Program

The Rover Sequencing and Visualization Program (RSVP) has been updated. RSVP was reported in Rover Sequencing and Visualization Program (NPO-30845), NASA Tech Briefs, Vol. 29, No. 4 (April 2005), page 38. To recapitulate: The Rover Sequencing and Visualization Program (RSVP) is the software tool to be used in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (robotic arm) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities.

Cooper, Brian↗
NASA NTRS2022

Kamodo’s Model-Agnostic Satellite Flythrough: Lowering the Utilization Barrier for Heliophysics Model Outputs

Heliophysics model outputs are increasingly accessible, but typically are not usable by the majority of the community unless directly collaborating with the relevant model developers. Prohibitive factors include complex file output formats, cryptic metadata, unspecified and often customized coordinate systems, and non-linear coordinate grids. Some pockets of progress exist, giving interfaces to various simulation outputs, but only for a small set of outputs and typically not with open-source, freely available packages. Additionally, the increasing array of tools built upon these sporadic interfaces are typically model-specific. We present Kamodo’s model-agnostic satellite flythrough capabilities as the solution to the utilization barrier for heliophysics model outputs. Developed at the Community Coordinated Modeling Center, these flythrough capabilities are built in Python upon a network of model-agnostic interfaces developed in collaboration with model developers, providing interpolation results the community can trust. Kamodo’s flythrough capabilities present the user with a growing variety of flythrough tools based upon a rapidly expanding library of heliophysics model outputs in several domains, currently including a variety of Ionosphere-Thermosphere-Mesosphere and global magnetosphere model outputs. Each capability is designed to be easily accessible via simplistic model-agnostic syntax, with the entire package freely available in the cloud on Github. Here, we describe the tools developed, include several sample applications for common science questions, demonstrate interoperability with selected packages, and summarize ongoing developments.

Software↗
NASA NTRS2005

Formal Safety Certification of Aerospace Software

In principle, formal methods offer many advantages for aerospace software development: they can help to achieve ultra-high reliability, and they can be used to provide evidence of the reliability claims which can then be subjected to external scrutiny. However, despite years of research and many advances in the underlying formalisms of specification, semantics, and logic, formal methods are not much used in practice. In our opinion this is related to three major shortcomings. First, the application of formal methods is still expensive because they are labor- and knowledge-intensive. Second, they are difficult to scale up to complex systems because they are based on deep mathematical insights about the behavior of the systems (t.e., they rely on the "heroic proof"). Third, the proofs can be difficult to interpret, and typically stand in isolation from the original code. In this paper, we describe a tool for formally demonstrating safety-relevant aspects of aerospace software, which largely circumvents these problems. We focus on safely properties because it has been observed that safety violations such as out-of-bounds memory accesses or use of uninitialized variables constitute the majority of the errors found in the aerospace domain. In our approach, safety means that the program will not violate a set of rules that can range for the simple memory access rules to high-level flight rules. These different safety properties are formalized as different safety policies in Hoare logic, which are then used by a verification condition generator along with the code and logical annotations in order to derive formal safety conditions; these are then proven using an automated theorem prover. Our certification system is currently integrated into a model-based code generation toolset that generates the annotations together with the code. However, this automated formal certification technology is not exclusively constrained to our code generator and could, in principle, also be integrated with other code generators such as RealTime Workshop or even applied to legacy code. Our approach circumvents the historical problems with formal methods by increasing the degree of automation on all levels. The restriction to safety policies (as opposed to arbitrary functional behavior) results in simpler proof problems that can generally be solved by fully automatic theorem proves. An automated linking mechanism between the safety conditions and the code provides some of the traceability mandated by process standards such as DO-178B. An automated explanation mechanism uses semantic markup added by the verification condition generator to produce natural-language explanations of the safety conditions and thus supports their interpretation in relation to the code. It shows an automatically generated certification browser that lets users inspect the (generated) code along with the safety conditions (including textual explanations), and uses hyperlinks to automate tracing between the two levels. Here, the explanations reflect the logical structure of the safety obligation but the mechanism can in principle be customized using different sets of domain concepts. The interface also provides some limited control over the certification process itself. Our long-term goal is a seamless integration of certification, code generation, and manual coding that results in a "certified pipeline" in which specifications are automatically transformed into executable code, together with the supporting artifacts necessary for achieving and demonstrating the high level of assurance needed in the aerospace domain.

Denney, Ewen↗
NASA NTRS2011

Standards and Specifications for Ground Processing of Space Vehicles: From an Aviation-Based Shuttle Project to Global Application

Proprietary or unique designs and operations are expected early in any industry's development, and often provide a competitive early market advantage. However, there comes a time when a product or industry requires standardization for the whole industry to advance...or survive. For the space industry, that time has come. Here, we will focus on standardization of ground processing for space vehicles and their ground systems. With the retirement of the Space Shuttle, and emergence of a new global space race, affordability and sustainability are more important now than ever. The growing commercialization of the space industry and current global economic environment are driving greater need for efficiencies to save time and money. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability not achievable with traditional ELV's (Expendable Launch Vehicles). More crew/passenger vehicles are also being developed. All of this calls for more attention needed for ground processing-repeatedly before launch and after landing/recovery. RLV's should provide more efficiencies than ELV's, as long as MRO (Maintenance, Repair, and Overhaul) is well-planned-even for the unplanned problems. NASA's Space Shuttle is a primary example of an RLV which was supposed to thrive on reusability savings with efficient ground operations, but lessons learned show that costs were (and still are) much greater than expected. International standards and specifications can provide the commonality needed to simplify design and manufacturing as well as to improve safety, quality, maintenance, and operability. There are standards organizations engaged in the space industry, but ground processing is one of the areas least addressed. Challenges are encountered due to various factors often not considered during development. Multiple vehicle elements, sites, customers, and contractors pose various functional and integration difficulties. Resulting technical publication structures and methods are incongruent. Some processing products are still done on paper, some electronic, and many being converted in between. Business systems then are not fully compatible, and paper as well as electronic conversions are time-consuming and costly. NASA and its Shuttle contractors setup rules and systems to handle what has produced over 130 RLV launches, but they have had many challenges. Attempts have been made to apply aviation industry specifications to make the Shuttle more efficient with its ground processing. One efficiency project example was to make a Shuttle Maintenance Manual (SMM) based on the commercial ATA (Air Transport Association of America) Spec 100 for technical publications. This industry standard, along with others, has been a foundation for efficient global MRO of commercial airlines for years. A modified version was also made for some military aircraft. The SMM project found many similarities in Spec 100 which apply to the Shuttle, and room for expansion for space systems/structures not in aircraft. The SMM project team met with the ATA and representatives from NASA's X-33 and X-34 programs to discuss collaboration on a national space standard based on Spec 100. A pilot project was enabled for a subset of Shuttle systems. Full implementation was not yet achieved, X-33 and X-34 were cancelled, and the Shuttles were then designated for retirement. Nonetheless, we can learn from this project how to expand this concept to all space vehicle products. Since then, ATA has joined with ASD (AeroSpace and Defence Industries Association of Europe) and AIA (Aerospace Industries Association) to form a much-enhanced and expanded international specification: Sl000D, International Specification for Technical Publications. It includes air, land, and sea vehicles, missiles, support equipment, ordnance, and communications. It is used by a growing number of countries for commercial and government products. Its modular design is supported by a Common Source Dabase (CSDB), and COTS (commercial off-the-shelf) software is available for production of IETP's (Interactive Electronic Technical Publications). A few space industry products in Europe have begun to apply Sl000D already. Also, there are other related standards/specifications which have global implications. We have an opportunity to adapt Sl000D and possibly other standards for use with space vehicles and ground systems. Sl000D has plenty of flexibility to apply to any product needed. To successfully grow the viability of the space industry, all members, commercial and government, will need to engage cooperatively in developing and applying standards to move toward interoperability. If we leverage and combine the best existing space standards and specifications, develop new ones to address known gaps, and adapt the best applicable features from other industries, we can establish an infrastructure to not only accelerate current development, but also build longevity for a more cohesive international space community.

Ingalls, John↗