SEARCH · Search NASA

Results for “Transfer Learning”

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 325 records · Page 18

All sources NASA NTRS DOE OSTI

NASA NTRS1991

Collision avoidance for CTV: Requirements and capabilities

Collision avoidance must be ensured during Cargo Transfer Vehicle (CTV) operations near the space station. The design of the Collision Avoidance Maneuver (CAM) will involve analysis of CTV failure modes during rendezvous and proximity operations as well as analysis of possible problems external to the CTV, but that would require CTV to execute a CAM. In considering the requirements and design of the CAM for the CTV, the CAM design for the Orbital Maneuvering Vehicle (OMV) is a useful reference point from which some lessons can be learned and many CTV design options can be set forth.

Nosek, Thomas↗

NASA NTRS1996

NASA/DOD Aerospace Knowledge Diffusion Research Project: Survey of Reader Preferences Concerning the Format of NASA Langley-Authored Technical Reports - Paper 58

The U.S. government technical report is a primary means by which the results of federally funded research and development (R&D) are transferred to the U.S. aerospace industry. However, little is known about this information product in terms of its actual use, importance, and value in the transfer of federally funded R&D. Little is also known about the intermediary-based system that is used to transfer the results of federally funded R&D to the U.S. aerospace industry. To help establish a body of knowledge, the U.S. government technical report is being investigated as part of the NASA/DOD Aerospace Knowledge Diffusion Research Project. In this paper, we summarize the literature on the U.S. government technical report and present the results of a survey of U.S. aerospace engineers and scientists that solicited their opinions concerning the format of NASA Langley Research Center (LaRC)-authored technical reports. To learn more about the preferences of U.S. aerospace engineers and scientists concerning the format of NASA LaRC-authored technical reports, we surveyed 133 report producers (i.e., authors) and 137 report users in March-April 1996. Questions covered such topics as (1) the order in which report components are read, (2) components used to determine if a report would be read, (3) those components that could be deleted, (4) the placement of such components as the symbols list, (e) the de-sirability of a table of contents, (5) the format of reference citations, (6) column layout and right margin treatment, and (7) and person and voice. Mail (self-reported) surveys were used to collect the data. The response rates for report producers (i.e., authors) was 68% and for users was 62%.

Pinelli, Thomas E.↗

NASA NTRS1997

NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 65: Survey of Reader Preferences Concerning the Format of NASA Langley-Authored Technical Reports

The U.S. government technical report is a primary means by which the results of federally funded research and development (R&D) are transferred to the U.S. aerospace industry. However, little is known about this information product in terms of its actual use, importance, and value in the transfer of federally funded R&D. Little is also known about the intermediary-based system that is used to transfer the results of federally funded R&D to the U.S. aerospace industry. To help establish a body of knowledge, the U.S. government technical report is being investigated as part of the NASA/DoD Aerospace Knowledge Diffusion Research Project. In this article, we summarize the literature on the U.S. government technical report and present the results of a survey of U.S. aerospace engineers and scientists that solicited their opinions concerning the format of NASA Langley Research Center (LaRC)-authored technical reports. To learn more about the preferences of U.S. aerospace engineers and scientists concerning the format of NASA LaRC-authored technical reports, we surveyed 133 report producers (i.e., authors) and 137 report users in March-April 1996. Questions covered such topics as: (a) the order in which report components are read; (b) components used to determine if a report would be read; (c) those components that could be deleted; (d) the placement of such components as the symbols list; (e) the desirability of a table of contents; (f) the format of reference citations; (g) column layout and right margin treatment; and (h) writing style in terms of person and voice. Mail (self-reported) surveys were used to collect the data. The response rates for report producers (i.e., authors) was 68% and for users was 62%.

Pinelli, Thomas E.↗

NASA NTRS1985

The Characterization of Surface Variegation Effects on Remote Sensing

Improvements in remote sensing capabilities hinge very directly upon attaining an understanding of the physical processes contributing to the measurements. In order to devise new measurement strategies and to learn better techniques for processing remotely gathered data, it is necessary to understand and to characterize the complex radiative interactions of the atmosphere-surface system. In particular, it is important to understand the role of atmospheric structure, ground reflectance inhomogeneity and ground bidirectional reflectance type. The goals, then, are to model, analyze, and parameterize the observable effects of three dimensional atmospheric structure and composition and two dimensional variations in ground albedo and bidirectional reflectance. To achieve these goals, a Monte Carlo radiative transfer code is employed to model and analyze the effects of many of the complications which are present in nature.

Pearce, W. A.↗

NASA NTRS2011

Introduction of Parallel GPGPU Acceleration Algorithms for the Solution of Radiative Transfer

General-purpose computing on graphics processing units (GPGPU) is a recent technique that allows the parallel graphics processing unit (GPU) to accelerate calculations performed sequentially by the central processing unit (CPU). To introduce GPGPU to radiative transfer, the Gauss-Seidel solution of the well-known expressions for 1-D and 3-D homogeneous, isotropic media is selected as a test case. Different algorithms are introduced to balance memory and GPU-CPU communication, critical aspects of GPGPU. Results show that speed-ups of one to two orders of magnitude are obtained when compared to sequential solutions. The underlying value of GPGPU is its potential extension in radiative solvers (e.g., Monte Carlo, discrete ordinates) at a minimal learning curve.

Godoy, William F.↗

NASA NTRS2016

Station Program Note Pull Automation

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

Delgado, Ivan↗

NASA NTRS1993

Experience, lessons learned and methodology in the design of space systems to accommodate total dose and SEU effects

We now have considerable experience with successfully designing science systems to function properly, even during and after exposure to ionizing radiation approaching one Megarad, and during large solar particle events with substantial high Z fluxes such as the events that happened in August, 1972 and in the fall of 1989. Nevertheless, with changing device dimensions and properties, newer technologies and new applications, new problems arise. Some recent basic research has shed light on these problems and pointed the way to better diagnostic tests. In the case of single event upsets, clearly one cannot always accurately predict upset probabilities simply by knowing the quiescent Linear Energy Transfer (LET) threshold and the asymptotic cross-section of the device.

Trainor, James H.↗

NASA NTRS2006

Developing Formal Correctness Properties from Natural Language Requirements

This viewgraph presentation reviews the rationale of the program to transform natural language specifications into formal notation.Specifically, automate generation of Linear Temporal Logic (LTL)correctness properties from natural language temporal specifications. There are several reasons for this approach (1) Model-based techniques becoming more widely accepted, (2) Analytical verification techniques (e.g., model checking, theorem proving) significantly more effective at detecting types of specification design errors (e.g., race conditions, deadlock) than manual inspection, (3) Many requirements still written in natural language, which results in a high learning curve for specification languages, associated tools and increased schedule and budget pressure on projects reduce training opportunities for engineers, and (4) Formulation of correctness properties for system models can be a difficult problem. This has relevance to NASA in that it would simplify development of formal correctness properties, lead to more widespread use of model-based specification, design techniques, assist in earlier identification of defects and reduce residual defect content for space mission software systems. The presentation also discusses: potential applications, accomplishments and/or technological transfer potential and the next steps.

requirements engineering↗

NASA NTRS2011

NASA Flight Planning Branch Space Shuttle Lessons Learned

Planning products and procedures that allowed the mission Flight Control Teams and the Astronaut crews to plan, train and fly every Space Shuttle mission were developed by the Flight Planning Branch at the NASA Johnson Space Center in Houston, Texas. As the Space Shuttle Program came to a close, lessons learned were collected from each phase of the successful execution of these Space Shuttle missions. Specific examples of how roles and responsibilities of console positions that develop the crew and vehicle attitude timelines have been analyzed and will be discussed. Additionally, the relationships and procedural hurdles experienced through international collaboration have molded operations. These facets will be explored and related to current and future operations with the International Space Station and future vehicles. Along with these important aspects, the evolution of technology and continual improvement of data transfer tools between the Space Shuttle and ground team has also defined specific lessons used in improving the control team s effectiveness. Methodologies to communicate and transmit messages, images, and files from the Mission Control Center to the Orbiter evolved over several years. These lessons were vital in shaping the effectiveness of safe and successful mission planning and have been applied to current mission planning work in addition to being incorporated into future space flight planning. The critical lessons from all aspects of previous plan, train, and fly phases of Space Shuttle flight missions are not only documented in this paper, but are also discussed regarding how they pertain to changes in process and consideration for future space flight planning.

Clevenger, Jennifer D.↗

NASA NTRSDate not supplied

Transient Optimization for the Betterment of Turbine Electrified Energy Management

Gas turbine engine transients are associated with degraded compressor operability, which must be addressed by the engine control system and accounted for in the engine design. Failure to do so may result in events such as compressor stall/surge and combustor blow out. Transient operability concerns constrain the engine design and can result in sacrifices of efficiency and/or thrust responsiveness. The traditional approach to transient operability management is control logic that limits the fuel flow command. A companion paper presents a strategy for optimizing the transient fuel flow control logic taking into consideration transient operability and thrust responsiveness. The study covered here extends this idea to an electrified gas turbine engine that employs a power/energy management concept known as Turbine Electrified Energy Management (TEEM). TEEM uses an electric power system interfaced with the engine (hence the term ‘electrified gas turbine engine’) to further improve transient operability and alleviate associated design constraints. There can be costs associated with implementing TEEM in terms of power and energy requirements that impact the size of the electrical power system. However, the results of this study show that through optimization of the transient limit logic, power and energy requirements needed to implement TEEM can be significantly reduced. Among the conclusions that can be drawn from the results of the illustrative application covered herein are: (1) there is a reduction in the electric machine power requirement to manage operability during accelerations by 200 to 400 hp, and (2) power transfer from the low pressure spool (LPS) to the high pressure spool (HPS) is the most effective option for improving operability during decelerations, followed by the options of only injecting power on the HPS or only extracting power from the LPS.

transient↗

NASA NTRSDate not supplied

Transient Optimization for the Betterment of Turbine Electrified Energy Management

transient↗

NASA NTRS2014

Fuzzy Neuron: Method and Hardware Realization

This innovation represents a method by which single-to-multi-input, single-to-many-output system transfer functions can be estimated from input/output data sets. This innovation can be run in the background while a system is operating under other means (e.g., through human operator effort), or may be utilized offline using data sets created from observations of the estimated system. It utilizes a set of fuzzy membership functions spanning the input space for each input variable. Linear combiners associated with combinations of input membership functions are used to create the output(s) of the estimator. Coefficients are adjusted online through the use of learning algorithms.

Krasowski, Michael J.↗

NASA NTRS2014

In-Situ and Remote-Sensing Data Fusion Using Machine Learning Techniques to Infer Urban and Fire Related Pollution Plumes

Airmass type characterization is key in understanding the relative contribution of various emission sources to atmospheric composition and air quality and can be useful in bottom-up model validation and emission inventories. However, classification of pollution plumes from space is often not trivial. Sub-orbital campaigns, such as SEAC4RS (Studies of Emissions, Atmospheric Composition, Clouds and Climate Coupling by Regional Surveys) give us a unique opportunity to study atmospheric composition in detail, by using a vast suite of in-situ instruments for the detection of trace gases and aerosols. These measurements allow identification of spatial and temporal atmospheric composition changes due to various pollution plumes resulting from urban, biogenic and smoke emissions. Nevertheless, to transfer the knowledge gathered from such campaigns into a global spatial and temporal context, there is a need to develop workflow that can be applicable to measurements from space. In this work we rely on sub-orbital in-situ and total column remote sensing measurements of various pollution plumes taken aboard the NASA DC-8 during 2013 SEAC4RS campaign, linking them through a neural-network (NN) algorithm to allow inference of pollution plume types by input of columnar aerosol and trace-gas measurements. In particular, we use the 4STAR (Spectrometer for Sky-Scanning, Sun-Tracking Atmospheric Research) airborne measurements of wavelength dependent aerosol optical depth (AOD), particle size proxies, O3, NO2 and water vapor to classify different pollution plumes. Our method relies on assigning a-priori ground-truth labeling to the various plumes, which include urban pollution, different fire types (i.e. forest and agriculture) and fire stage (i.e. fresh and aged) using cluster analysis of aerosol and trace-gases in-situ and auxiliary (e.g. trajectory) data and the training of a NN scheme to fit the best prediction parameters using 4STAR measurements as input. We explore our misclassification rates as related to our ground-truth labels, and with multi-layered pollution plume cases. The next step in our analysis is to optimize parameter selection for a scheme that can be applied to space-borne aerosol and trace-gas observation platforms such as OMI, and future geostationary satellites such as TEMPO and GEO-CAPE.

Neural-network↗

NASA NTRS2005

Learning Lessons from the X-37 Project

The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite's White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with and turnaround maintenance performed. The fight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development. NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This recent partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of the X-37 effort, the team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff research and development and provides valuable experience to implement the exploration vision.

Turner, Susan↗

NASA NTRS2005

Learning Lessons from the X-37 Project

The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite s White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with landing and turnaround maintenance performed. The Flight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development (R&D). NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of this effort, the X-37 team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff R&D and provides valuable experience to implement the Vision for Space Exploration.

Turner, Susan↗

NASA NTRS2020

High-capacity ATHLETE Offloader Mobility Constructor Concept for Human Surface Exploration

Using cross-cabled, winch-tendon four-bar frames, a new Artemis-class ATHLETE system is a multi-limbed robotic mobility platform that is designed for surface traverse, precision placement, and offloading of heavy habitats and other large human exploration payloads from high-decked landers. Building upon lessons learned from the All-Terrain Hex-Limbed Extra-Terrestrial Explorer (ATHLETE) robotic mobility system developed for Constellation Lunar Surface Systems and Evolvable Mars Campaign, a high-capacity articulated crane / lift vehicle concept has been devised that would be equipped with multi-limb six-degree-of-freedom dexterity for a variety of tasks supporting planetary surface human exploration missions and outposts. The Artemis-class ATHLETE vehicle would use any combination of three to six wheel-onlimb combinations to provide a wide “outrigger” stance to transfer loads from a high center-of-gravity on sloped terrain to low stable carry configurations for long-distance traverses, and be capable of precision docking of payloads to previously positioned elements. The new vehicle concept improves upon previous Constellation-class ATHLETE versions by allowing modular hot-swapping of individual limbs to improve maintenance and flexibility. The extreme-capacity independent limbs can individually function as single cranes, and can be delivered separately via multiple lander manifests for later congregation into self-driving “Tri-ATHLETE” vehicles after delivery to the surface. This paper provides mission architecture targets and vehicle masses for stepped payload capacity values in Earth, Mars, and Lunar gravity environments, and discusses a variety of swappable tools, including wheeled mobility attachments, grippers, excavation tools, repair fixtures, ISRU extraction, winches, block & tackle rigging combinations, 3D printheads, and construction aids.

Wilcox, Brian↗

NASA NTRS1993

California Student Get Away Special Payload GAS-450

The California Student Get Away Special Payload GAS-450, recently went into orbit on the STS-57 Mission, Space Shuttle, Endeavour, 21 June 1993, 6:14 AM and landed on the 29 June 1993 at Kennedy Space Center (KSC). Fifty students from 13 California Central Coast Schools and one in San Francisco designed and built 13 active experiments (6 modules) for this mission. Preliminary analysis of our completely reusable payload bus system indicated that the structure, power system, microprocessor, and sensor systems in each experiment module worked flawlessly. The experiments themselves performed exceptionally well with a 60 percent success ratio. The students are thoroughly documenting their own experiments and results via a standard research paper guideline generated by the GAS-450 technical staff. Lessons learned (program management and technical) are documented at the end of the paper. If any other organization needs payload/experiment development or NASA documentation assistance, then please contact us. We can help make your idea a space tested reality. Three years of intense effort culminated on 3 February 1993, the GSFC field operations team at Kennedy Space Center performed the final pressure decay and electrical tests upon the fully integrated GAS-450 flight canister. Subsequently, the payload was integrated with its parent GAS Bridge Assembly in mid-February and the bridge was transferred to the KSC orbiter team in late February 1993. The STS-57 mission originally scheduled to launch on the 29 April 1993 slipped until 21 June 1993. Our Payload shared the cargo bay with ten other GAS Canisters, the EUREKA experiment, the SHOOT experiment, and the SPACEHAB-1 module. The SIL technical staff retrieved the GAS-450 payload after flight from the NASA Spin Test Facility at KSC and shipped it back to California on the 22 July 1993 for student analysis at Allan Hancock College this summer.

Ray, Glen↗

NASA NTRS2002

MDP: Reliable File Transfer for Space Missions

This paper presents work being done at NASA/GSFC by the Operating Missions as Nodes on the Internet (OMNI) project to demonstrate the application of the Multicast Dissemination Protocol (MDP) to space missions to reliably transfer files. This work builds on previous work by the OMNI project to apply Internet communication technologies to space communication. The goal of this effort is to provide an inexpensive, reliable, standard, and interoperable mechanism for transferring files in the space communication environment. Limited bandwidth, noise, delay, intermittent connectivity, link asymmetry, and one-way links are all possible issues for space missions. Although these are link-layer issues, they can have a profound effect on the performance of transport and application level protocols. MDP, a UDP-based reliable file transfer protocol, was designed for multicast environments which have to address these same issues, and it has done so successfully. Developed by the Naval Research Lab in the mid 1990's, MDP is now in daily use by both the US Post Office and the DoD. This paper describes the use of MDP to provide automated end-to-end data flow for space missions. It examines the results of a parametric study of MDP in a simulated space link environment and discusses the results in terms of their implications for space missions. Lessons learned are addressed, which suggest minor enhancements to the MDP user interface to add specific features for space mission requirements, such as dynamic control of data rate, and a checkpoint/resume capability. These are features that are provided for in the protocol, but are not implemented in the sample MDP application that was provided. A brief look is also taken at the status of standardization. A version of MDP known as NORM (Neck Oriented Reliable Multicast) is in the process of becoming an IETF standard.

Rash, James↗