Search NASA⌕ Search

SEARCH · Search NASA

Results for “Migration of legacy systems”

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 19 records

FAA/AES - NASA/DIP Technical Interchange Meeting

The purpose of this Technical Interchange Meeting (TIM) is to hold our second of several discussions on select DIP and AES-topics. The first AES- DIP Technical Interchange Meeting was an in-person event in Washington DC. This is a followup meeting to deep dive into some of the areas discussed during the 1st TIM

monitoring↗

An Approach to Integrated Spectrum Efficient Network Enhanced Telemetry (iSENET))

As the integrated Network Enhanced Telemetry (iNET) program moves forward in resolving systems engineering design and architecture definition, critical technology "gaps" and a migration path to realizing the integration of this technology are needed to insure a smooth transition from the current legacy point to point telemetry links to a network oriented telemetry system. Specifically, identified by the DoD aeronautical telemetry community is the need for a migration to a network solution for command, control, and transfer of test data by optimizing the physical, data link, and network layers. In this paper, we present a network-centric telemetry approach based on variants of 802.11 that leverages the open standards as well as the previous Advanced Range Telemetry (ARTM) work on the physical layer waveform. Specifically, we present a burst modem approach based on the recent AOFDM 802.11a work, a TDMA-like MAC layer approach based on 802.11e, and then add additional MAC layer features to allow for the multi-hop aeronautical environment using a variant of the current working standards of 802.11s. The combined benefits of the variants obtained from 802.11a, 802.11e, and 802.11s address the needs for both spectrum efficiency in the aeronautical environment and the iNET program.

TDMA↗

Adding Concrete Syntax to a Prolog-Based Program Synthesis System

Program generation and transformation systems manipulate large, pa- rameterized object language fragments. Support for user-definable concrete syntax makes this easier but is typically restricted to certain object and meta languages. We show how Prolog can be retrofitted with concrete syntax and describe how a seamless interaction of concrete syntax fragments with an existing legacy meta-programming system based on abstract syntax is achieved. We apply the approach to gradually migrate the schemas of the AUTOBAYES program synthesis system to concrete syntax. Fit experiences show that this can result in a considerable reduction of the code size and an improved readability of the code. In particular, abstracting out fresh-variable generation and second-order term construction allows the formulation of larger continuous fragments and improves the locality in the schemas.

Fischer, Bernd↗

New Metadata Capabilities within NASA's Common Metadata Repository (CMR)

This talk will convey the new capabilities and features of the UMM-Variables and the UMM-Services metadata model within the Common Metadata Repository (CMR) and how community engagement through the ESDIS Standards Office (ESO) review shaped the new versions of the models. The Unified Metadata Model (UMM) provides a common metadata model to unify legacy systems (i.e. GCMD (Global Change Master Directory), ECHO (Earth Observing System (EOS) Clearinghouse)) with new systems (i.e. CMR). The rationale and migration process of the Service Entry Resource Format (SERF) to the UMM-S will also be conveyed. The talk will conclude with discussing issues and lessons learned from the review process and how future reviews will be conducted to ensure a more targeted, meaningful review with a faster turn-around time for triage and implementation.

Earth Observing System↗

SANs and Large Scale Data Migration at the NASA Center for Computational Sciences

Evolution and migration are a way of life for provisioners of high-performance mass storage systems that serve high-end computers used by climate and Earth and space science researchers: the compute engines come and go, but the data remains. At the NASA Center for Computational Sciences (NCCS), disk and tape SANs are deployed to provide high-speed I/O for the compute engines and the hierarchical storage management systems. Along with gigabit Ethernet, they also enable the NCCS's latest significant migration: the transparent transfer of 300 Til3 of legacy HSM data into the new Sun SAM-QFS cluster.

Salmon, Ellen M.↗

Controlling Infrastructure Costs: Right-Sizing the Mission Control Facility

Johnson Space Center's Mission Control Center is a space vehicle, space program agnostic facility. The current operational design is essentially identical to the original facility architecture that was developed and deployed in the mid-90's. In an effort to streamline the support costs of the mission critical facility, the Mission Operations Division (MOD) of Johnson Space Center (JSC) has sponsored an exploratory project to evaluate and inject current state-of-the-practice Information Technology (IT) tools, processes and technology into legacy operations. The general push in the IT industry has been trending towards a data-centric computer infrastructure for the past several years. Organizations facing challenges with facility operations costs are turning to creative solutions combining hardware consolidation, virtualization and remote access to meet and exceed performance, security, and availability requirements. The Operations Technology Facility (OTF) organization at the Johnson Space Center has been chartered to build and evaluate a parallel Mission Control infrastructure, replacing the existing, thick-client distributed computing model and network architecture with a data center model utilizing virtualization to provide the MCC Infrastructure as a Service. The OTF will design a replacement architecture for the Mission Control Facility, leveraging hardware consolidation through the use of blade servers, increasing utilization rates for compute platforms through virtualization while expanding connectivity options through the deployment of secure remote access. The architecture demonstrates the maturity of the technologies generally available in industry today and the ability to successfully abstract the tightly coupled relationship between thick-client software and legacy hardware into a hardware agnostic "Infrastructure as a Service" capability that can scale to meet future requirements of new space programs and spacecraft. This paper discusses the benefits and difficulties that a migration to cloud-based computing philosophies has uncovered when compared to the legacy Mission Control Center architecture. The team consists of system and software engineers with extensive experience with the MCC infrastructure and software currently used to support the International Space Station (ISS) and Space Shuttle program (SSP).

Martin, Keith↗

Retrofitting the AutoBayes Program Synthesis System with Concrete Syntax

AutoBayes is a fully automatic, schema-based program synthesis system for statistical data analysis applications. Its core component is a schema library. i.e., a collection of generic code templates with associated applicability constraints which are instantiated in a problem-specific way during synthesis. Currently, AutoBayes is implemented in Prolog; the schemas thus use abstract syntax (i.e., Prolog terms) to formulate the templates. However, the conceptual distance between this abstract representation and the concrete syntax of the generated programs makes the schemas hard to create and maintain. In this paper we describe how AutoBayes is retrofitted with concrete syntax. We show how it is integrated into Prolog and describe how the seamless interaction of concrete syntax fragments with AutoBayes's remaining legacy meta-programming kernel based on abstract syntax is achieved. We apply the approach to gradually mitigate individual schemas without forcing a disruptive migration of the entire system to a different First experiences show that a smooth migration can be achieved. Moreover, it can result in a considerable reduction of the code size and improved readability of the code. In particular, abstracting out fresh-variable generation and second-order term construction allows the formulation of larger continuous fragments.

Fischer, Bernd↗

Hierarchical Storage Management at the NASA Center for Computational Sciences: From UniTree to SAM-QFS

This paper presents the data management issues associated with a large center like the NCCS and how these issues are addressed. More specifically, the focus of this paper is on the recent transition from a legacy UniTree (Legato) system to a SAM-QFS (Sun) system. Therefore, this paper will describe the motivations, from both a hardware and software perspective, for migrating from one system to another. Coupled with the migration from UniTree into SAM-QFS, the complete mass storage environment was upgraded to provide high availability, redundancy, and enhanced performance. This paper will describe the resulting solution and lessons learned throughout the migration process.

Salmon, Ellen↗

Performance Analysis of TCP Enhancements in Satellite Data Networks

This research examines two proposed enhancements to the well-known Transport Control Protocol (TCP) in the presence of noisy communication links. The Multiple Pipes protocol is an application-level adaptation of the standard TCP protocol, where several TCP links cooperate to transfer data. The Space Communication Protocol Standard - Transport Protocol (SCPS-TP) modifies TCP to optimize performance in a satellite environment. While SCPS-TP has inherent advantages that allow it to deliver data more rapidly than Multiple Pipes, the protocol, when optimized for operation in a high-error environment, is not compatible with legacy TCP systems, and requires changes to the TCP specification. This investigation determines the level of improvement offered by SCPS-TP's Corruption Mode, which will help determine if migration to the protocol is appropriate in different environments. As the percentage of corrupted packets approaches 5 %, Multiple Pipes can take over five times longer than SCPS-TP to deliver data. At high error rates, SCPS-TP's advantage is primarily caused by Multiple Pipes' use of congestion control algorithms. The lack of congestion control, however, limits the systems in which SCPS-TP can be effectively used.

Broyles, Ren H.↗

Important Changes to User Access at the NASA CDDIS

The Crustal Dynamics Data Information System (CDDIS) supports data archiving and distribution activities for the space geodesy and geodynamics community. The main objectives of the system are to make space geodesy and geodynamics related data and derived products available in a central archive, to maintain information about the archival of these data, to disseminate these data and information in a timely manner to a global scientific research community, and to provide user based tools for the exploration and use of the archive. Since its inception, the user community has utilized anonymous ftp for accessing and downloading files from the CDDIS archive. Although this protocol allows users to easily automate file downloads, many organizations, data systems, and users have already migrated from ftp or are actively pursuing a move away from the protocol due to problems from a system and security standpoint. Furthermore, U.S. Government agencies have become increasingly concerned about this legacy protocol and ensuring data integrity for the user community have begun recently to disallow the use of the ftp protocol. The CDDIS, operated by NASA GSFC, must therefore address these concerns and provide alternative methods for access to its archive for continued easy and automated download of its contents. This poster will discuss the upcoming changes at CDDIS and provide examples on transitioning from anonymous ftp.

Noll, Carey E.↗

Design and Implementation of a Scenario Development Process for a 2040 Trajectory-Based Operations Simulation

The National Aeronautics and Space Administration (NASA) is supporting research to transition from a legacy, air traffic management (ATM) system to Trajectory-Based Operations (TBO) environment targeting the 2035-2045 timeframe by creating simulation scenarios for current and future studies. TBO in the National Airspace System (NAS) focuses on modernizing the current operating paradigm to increase efficiency, predictability, resilience, and flexibility while migrating toward greater operational autonomy across the airspace. These simulation scenarios offer a wide dissemination and use of system-level constraints and aircraft state/intent data, routine use of data communications to request complex trajectory modifications and to receive clearances, and aircraft that are flying on 4-D trajectories with flexibility when desired, but structure where required. This report describes the end-to-end development of scenarios for the NASA Langley Research Center simulation environment to represent a 2040 Trajectory-Based Operations airspace for air transport operations research.

Trajectory-Based Operations↗

Making Technology Ready: Integrated Systems Health Management

This paper identifies work needed by developers to make integrated system health management (ISHM) technology ready and by programs to make mission infrastructure ready for this technology. This paper examines perceptions of ISHM technologies and experience in legacy programs. Study methods included literature review and interviews with representatives of stakeholder groups. Recommendations address 1) development of ISHM technology, 2) development of ISHM engineering processes and methods, and 3) program organization and infrastructure for ISHM technology evolution, infusion and migration.

Malin, Jane T.↗

Multicore Considerations for Legacy Flight Software Migration

In this paper we will discuss potential benefits and pitfalls when considering a migration from an existing single core code base to a multicore processor implementation. The results of this study present options that should be considered before migrating fault managers, device handlers and tasks with time-constrained requirements to a multicore flight software environment. Possible future multicore test bed demonstrations are also discussed.

legacy flight software↗

Integrating Ground System Tools From Multiple Technologies Into a Single System Environment

With rapid technology changes and new and improved development techniques, it becomes extremely difficult to try to add capabilities to existing ground systems without wanting to replace the entire system. Replacing entire systems is not usually cost effective so there is a need to be able to slowly improve systems without long development times that introduce risk due to large amounts of change. The Marshall Space Flight Center s (MSFC) Payload Operations Integration Center (POIC) ground system provides command, telemetry, and payload planning systems in support of the International Space Station. Our systems have continuously evolved with technology changes due to hardware end of life issues, and also due to user requirement changes. As changes have been implemented, we have tried to take advantage of some of the latest technologies while at the same time maintaining certain legacy capabilities that are not cost affective to replace. One of our biggest challenges is to integrate all of these implementations into a single system that is usable, maintainable, and scalable. Another challenge is to provide access to our tools in such a way that users are not aware of all the various implementation methods and tools being used. This approach not only makes our system much more usable, it allows us to continue to migrate capabilities and to add capabilities without impacting system usability. This paper will give an overview of the tools used for MSFC ISS payload operations and show an approach for integrating various technologies into a single environment that is maintainable, flexible, usable, cost effective, and that meets user needs.

Ritter, George H.↗

By Hand or Not By-Hand: A Case Study of Alternative Approaches to Parallelize CFD Applications

While parallel processing promises to speed up applications by several orders of magnitude, the performance achieved still depends upon several factors, including the multiprocessor architecture, system software, data distribution and alignment, as well as the methods used for partitioning the application and mapping its components onto the architecture. The existence of the Gorden Bell Prize given out at Supercomputing every year suggests that while good performance can be attained for real applications on general purpose multiprocessors, the large investment in man-power and time still has to be repeated for each application-machine combination. As applications and machine architectures become more complex, the cost and time-delays for obtaining performance by hand will become prohibitive. Computer users today can turn to three possible avenues for help: parallel libraries, parallel languages and compilers, interactive parallelization tools. The success of these methodologies, in turn, depends on proper application of data dependency analysis, program structure recognition and transformation, performance prediction as well as exploitation of user supplied knowledge. NASA has been developing multidisciplinary applications on highly parallel architectures under the High Performance Computing and Communications Program. Over the past six years, the transition of underlying hardware and system software have forced the scientists to spend a large effort to migrate and recede their applications. Various attempts to exploit software tools to automate the parallelization process have not produced favorable results. In this paper, we report our most recent experience with CAPTOOL, a package developed at Greenwich University. We have chosen CAPTOOL for three reasons: 1. CAPTOOL accepts a FORTRAN 77 program as input. This suggests its potential applicability to a large collection of legacy codes currently in use. 2. CAPTOOL employs domain decomposition to obtain parallelism. Although the fact that not all kinds of parallelism are handled may seem unappealing, many NASA applications in computational aerosciences as well as earth and space sciences are amenable to domain decomposition. 3. CAPTOOL generates code for a large variety of environments employed across NASA centers: MPI/PVM on network of workstations to the IBS/SP2 and CRAY/T3D.

Yan, Jerry C.↗

Effective Visualization of Radar Data for Users Impacted By Color Vision Deficiency

Color Vision Deficiency (CVD) is a decreased ability to discern between particular colors. Eight percent of genetic males and half a percent of genetic females have some form of CVD, with many in the radar community falling into this group. When presenting data on a two-dimensional plane, it is common to use colors to represent values via a colormap. Colormap choice in the radar community is influenced by the ability to highlight scientifically interesting features in data, institutional choices, and domain dominance of legacy colormaps. The problem with these current colormaps is that many do not project well for those with CVD (i.e., green next to red). In working with the CVD community to address this problem, multiple colormaps for moments such as equivalent reflectivity factor and Doppler velocity were created for users with forms of CVD such as deuteranomaly, protanomaly, protanopia, and deuteranopia using Python tools such as colorspacious and viscm. We show how these colormaps can improve interpretability for four cases: a mesoscale convective system, a pyrocumulonimbus storm, a wintertime mid-latitude cyclone, and widespread storms with a large bird migration. These new radar equivalent reflectivity factor, Doppler velocity, and polarization colormaps are designed to highlight rain, frozen precipitation, non-meteorological targets, velocity-based items, be perceptually uniform, and visually friendly for those with CVD.

Zachary Sherman↗

An Upgrade of the Imaging for Hypersonic Experimental Aeroheating Testing (IHEAT) Software

The Imaging for Hypersonic Experimental Aeroheating Testing (IHEAT) code is used at NASA Langley Research Center to analyze global aeroheating data on wind tunnel models tested in the Langley Aerothermodynamics Laboratory. One-dimensional, semi-infinite heating data derived from IHEAT are used to design thermal protection systems to mitigate the risks due to the aeroheating loads on hypersonic vehicles, such as re-entry vehicles during descent and landing procedures. This code was originally written in the PV-WAVE programming language to analyze phosphor thermography data from the two-color, relativeintensity system developed at Langley. To increase the efficiency, functionality, and reliability of IHEAT, the code was migrated to MATLAB syntax and compiled as a stand-alone executable file labeled version 4.0. New features of IHEAT 4.0 include the options to batch process all of the data from a wind tunnel run, to map the two-dimensional heating distribution to a three-dimensional computer-aided design model of the vehicle to be viewed in Tecplot, and to extract data from a segmented line that follows an interesting feature in the data. Results from IHEAT 4.0 were compared on a pixel level to the output images from the legacy code to validate the program. The differences between the two codes were on the order of 10-5 to 10-7. IHEAT 4.0 replaces the PV-WAVE version as the production code for aeroheating experiments conducted in the hypersonic facilities at NASA Langley.

Mason, Michelle L.↗

Features of the Upgraded Imaging for Hypersonic Experimental Aeroheating Testing (IHEAT) Software

The Imaging for Hypersonic Experimental Aeroheating Testing (IHEAT) software is used at the NASA Langley Research Center to analyze global aeroheating data on wind tunnel models tested in the Langley Aerothermodynamics Laboratory. One-dimensional, semi-infinite heating data derived from IHEAT are used in the design of thermal protection systems for hypersonic vehicles that are exposed to severe aeroheating loads, such as reentry vehicles during descent and landing procedures. This software program originally was written in the PV-WAVE(Registered Trademark) programming language to analyze phosphor thermography data from the two-color, relative-intensity system developed at Langley. To increase the efficiency, functionality, and reliability of IHEAT, the program was migrated to MATLAB(Registered Trademark) syntax and compiled as a stand-alone executable file labeled version 4.0. New features of IHEAT 4.0 include the options to perform diagnostic checks of the accuracy of the acquired data during a wind tunnel test, to extract data along a specified multi-segment line following a feature such as a leading edge or a streamline, and to batch process all of the temporal frame data from a wind tunnel run. Results from IHEAT 4.0 were compared on a pixel level to the output images from the legacy software to validate the program. The absolute differences between the heat transfer data output from the two programs were on the order of 10(exp -5) to 10(exp -7). IHEAT 4.0 replaces the PV-WAVE(Registered Trademark) version as the production software for aeroheating experiments conducted in the hypersonic facilities at NASA Langley.

Mason, Michelle L.↗