SEARCH · Search NASA

Results for “base editing”

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 235 records · Page 13

All sources NASA NTRS DOE OSTI

NASA NTRS2001

Science Education Supporting Weather Broadcasters On-Air and in the Classroom with NASA "Mini-Education Supplements"

NASA-Goddard Space Flight Center has initiated a new project designed to expand on existing news services and add value to classrooms through the development and distribution of two-minute 'mini-supplements' which give context and teach about current weather and Earth research phenomena. The innovative mini-supplements provide raw materials for weather forecasters to build news stories around NASA related missions without having to edit the more traditional and cumbersome long-form video format. The supplements cover different weather and climate topics and include NASA data, animations, video footage, and interviews with scientists. The supplements also include a curriculum package with educational lessons, educator guide, and hand-on activities. One goal is to give on-air broadcasters who are the primary science educators for the general public what they need to 'teach' about the science related to NASA research behind weather and climate news. This goal achieves increasing public literacy and assures higher accuracy and quality science reporting by the media. The other goal is to enable on-air broadcasters to serve as distributors of high quality, standards-based educational curricula and supplemental material when they visit 8-12 grade classrooms. The focus of 'pilot effort' centers around the success of NASA's Tropical Rainfall Measuring Mission (TRMM) but is likely expandable to other NASA earth or space science missions.

Shepherd, J. Marshall↗

NASA NTRSDate not supplied

Crew Autonomy Through Self-Scheduling: Operational Characterization

NASA’s future long-duration exploration missions (LDEMs) will encounter increasing communication transmission delays as they move farther from Earth-based ground stations. This necessitates a new approach, as crews can no longer rely on real-time support from ground planners and must self-schedule their own operational timelines effectively and efficiently. To enable this transition, our team has developed Playbook, a mission planning and scheduling tool. Our research focuses on quantifying scheduling performance using Playbook to inform the design and development of future features to streamline timeline creation. We also aim to propose standards and guidelines for autonomous crews in LDEMs. In the past year, we have focused on further validating and quantifying the effects of countermeasure aids on self-scheduling performance. There are two software aids in Playbook (self-scheduling platform): Suggested Fixes, which propose an edit to resolve violations within a timeline, and No-Go Zones, which highlight where activities should not be scheduled on a timeline. We have made significant progress in HERA Campaign 7 (C7) data collection, increasing the number of days crew must self-schedule from 4 to 8. As a result, almost 20% of the mission is self-scheduled by the analog astronauts. We have also started data collection on a controlled lab experiment designed to quantify performance effects due to the countermeasures. We expect to present the preliminary results from both efforts. Finally, we have conducted an exploratory analysis of NASA’s HERA Campaign 6 (C6), investigating the mission-level impacts of self-scheduling. We derived basic patterns and descriptive statistics to better characterize crew autonomy through self-scheduling. We also assessed if there are any individual indicators of preference for self-scheduling, such as experience or predilection for autonomy. Preliminary analysis indicates that the HERA C6 crew self-scheduled one out of four flexible activities, indicating unprompted adoption of self-scheduling as a concept of operation for crew autonomy.

analog↗

NASA NTRS1980

Automation of the Mark 3 field system

The software and hardware components which will enable hands off operation are described. The operation of the field system begins with the scheduling of observations. An interactive program, SKED, provides displays of mutual visibility, automatic calculation of telescope slewing times, and the ability to list and edit the schedule. The output of SKED is a schedule file containing commands in the Standard Notation for Astronomy Procedures (SNAP) language which the field system uses for controlling events during the experiment. The most important features of SNAP include sophisticated time sequencing of events, automatic logging of all commands and responses, and the ability to define often used sequences of commands as procedures. A control program, BOSS, running in an HP 1000 minicomputer, reads the SNAP commands from a schedule file and interprets them in terms of commands and requests to devices. Interactive command input is possible through the operator's display terminal. Communication with all of the Mark 3 electronics modules is done via a small general purpose interface board (a microprocessor based ASCII transceiver) which has been installed in each module. Additional devices are controlled and monitored using the IEEE 488 General Purpose Interface Bus.

Vandenbere, N. R.↗

NASA NTRS2015

Software Development: 3D Animations and Creating User Interfaces for Realistic Simulations

My fall 2015 semester was spent at the Lyndon B. Johnson Space Center working in the Integrated Graphics, Operations, and Analysis Laboratory (IGOAL). My first project was to create a video animation that could tell the story of OMICS. OMICS is a term being used in the field of biomedical science to describe the collective technologies that study biological systems, such as what makes up a cell and how it functions with other systems. In the IGOAL I used a large 23 inch Wacom monitor to draw storyboards, graphics, and line art animations. I used Blender as the 3D environment to sculpt, shape, cut or modify the several scenes and models for the video. A challenge creating this video was to take a term used in biomedical science and describe it in such a way that an 8th grade student can understand. I used a line art style because it would visually set the tone for what we thought was an educational style. In order to get a handle on the perspective and overall feel for the animation without overloading my workspace, I split up the 2 minute animation into several scenes. I used Blender's python scripting capabilities which allowed for the addition of plugins to add or modify tools. The scripts can also directly interact with the objects to create naturalistic patterns or movements. After collecting the rendered scenes, I used Blender's built-in video editing workspace to output the animation. My second project was to write software that emulates a physical system's interface. The interface was to simulate a boat, ROV, and winch system. Simulations are a time and cost effective way to test complicated data and provide training for operators without having to use expensive hardware. We created the virtual controls with 3-D Blender models and 2-D graphics, and then add functionality in C# using the Unity game engine. The Unity engine provides several essential behaviors of a simulator, such as the start and update functions. A framework for Unity, which was developed in the lab, provided a way to place the different widgets on the virtual console dock and have them resize correctly based on the window dimensions.. My task in this project was to create the controls and visualizations for the data coming in from the simulator for the boat portion of the project. I wrote a class for each control window to handle the functionality of that widget. I implemented 11 widgets that make up the ship portion of the simulator. The members of the lab were each masters of their craft and I'm glad I had the opportunity to learn from them. I learned to plan strategically so I could finish this project on time. I allotted time for storyboarding, development, and refinement. In regards to animating I learned to use modifiers like lattice, boolean and build deformers. I also learned how to animate with drivers, how to use the dope sheet, and how to use the graph editor. In coding I learned to limit the chances for bugs by privatizing functions that should be exclusive to their class. I learned how to use the GIT repository to commit, stash and pull the latest build. I learned a bit of everything because I had the chance to see the entire application development process from the artwork, to the implementation.

Gordillo, Orlando Enrique↗

NASA NTRS2003

An Introduction to Atmospheric Radiation: Review for the Bulletin of AMS

Whether you like a certain geophysical book or not, largely depends on your background. The field of radiative transfer and atmospheric radiation, in particular, combines people with a wide range of mathematical skills: from theoretical astrophysicists and nuclear physicists to meteorologists and ecologists. There is always a delicate balance between physical explanations and their mathematical interpretations. This balance is very personal and is based on your background. I came to the field of atmospheric radiative transfer as a mathematician with little knowledge of atmospheric physics. After being in the field for more than a decade, I still have gaps in my atmospheric science education. Thus I assess a radiative transfer book fi-om two main criteria: how well does it describe the material that is familiar to me (the radiative transfer equation and its numerical solutions) and how well does it help me to fill the gaps in my personal knowledge. So I present this review fi-om the perspective of a former mathematician working in the field of atmospheric radiation. . After being asked to review the book, my first intention was to compare the new edition with the previous one (Liou, 1980). In doing so, you can clearly follow the progress made in the field of atmospheric radiation over the past two decades. If there are few changes (as in Fundamental Radiative Transfer) or no changes at all (as in the Maxwell s equations), then the field has not seen much development. To the contrary, many differences between the two editions illustrate areas of major progress in the field, such as evidenced in Thermal Ineared Radiative Transfer and even in the creations of completely new fields like Three-Dimensional Radiative Transfer or Light Scattering by Nonspherical Particles. Obviously, the major changes happened not in the theory, which is at least half a century old, but in data quality and completely new measurements (mostly due to new satellite data) with higher accuracy and more reliability. The new edition illustrates this progress well.

Marshak, Alexander↗

NASA NTRS1990

Analysis of altimetry over inland seas

Satellite-based altimetric data taken by GEOS-3 and SEASAT over the Black Sea and Caspian Sea are analyzed and a least squares collocation technique is used to predict the geoid undulation on a .25-degree by .25-degree grid and to transform these geoid undulations to free air gravity anomalies. This project entailed processing satellite altimeter data over inland seas for recovery of area mean gravity information. Gravity information in this area of the world is not readily available, so the possibility of obtaining it from the processing of altimeter observations is attractive. The principal objective was to complete and extend analyses done in a previous study, verify those results, and document the results and techniques. A secondary objective was to improve the algorithms and results, if possible. The approach used involved editing geoid height data to remove overland data; evaluating geoid height differences at crossover points; removing orbit errors from geoid heights using crossover differences; gridding geoid height data at .25-degree by .25-degree intervals; and estimating the gravity anomalies from gridded geoid heights using the collocation technique.

Au, A. Y.↗

NASA NTRS2006

Using Flow Regime Lightning and Sounding Climatologies to Initialize Gridded Lightning Threat Forecasts for East Central Florida

Each morning, the forecasters at the National Weather Service in Melbourne, FL (NWS MLB) produce an experimental cloud-to-ground (CG) lightning threat index map for their county warning area (CWA) that is posted to their web site (http://www.srh.weather.gov/mlb/ghwo/lightning.shtml) . Given the hazardous nature of lightning in East Central Florida, especially during the warm season months of May September, these maps help users factor the threat of lightning, relative to their location, into their daily plans. The maps are color-coded in five levels from Very Low to Extreme, with threat level definitions based on the probability of lightning occurrence and the expected amount of CG activity. On a day in which thunderstorms are expected, there are typically two or more threat levels depicted spatially across the CWA. The locations of relative lightning threat maxima and minima often depend on the position and orientation of the low-level ridge axis, forecast propagation and interaction of sea/lake/outflow boundaries, expected evolution of moisture and stability fields, and other factors that can influence the spatial distribution of thunderstorms over the CWA. The lightning threat index maps are issued for the 24-hour period beginning at 1200 UTC each day with a grid resolution of 5 km x 5 km. Product preparation is performed on the AWIPS Graphical Forecast Editor (GFE), which is the standard NWS platform for graphical editing. Currently, the forecasters create each map manually, starting with a blank map. To improve efficiency of the forecast process, NWS MLB requested that the Applied Meteorology Unit (AMU) create gridded warm season lightning climatologies that could be used as first-guess inputs to initialize lightning threat index maps. The gridded values requested included CG strike densities and frequency of occurrence stratified by synoptic-scale flow regime. The intent is to improve consistency between forecasters while allowing them to focus on the mesoscale detail of the forecast, ultimately benefiting the end-users of the product. Several studies took place at the Florida State University (FSU) and NWS Tallahassee (TAE) in which they created daily flow regimes using Florida 1200 UTC synoptic soundings and CG strike densities, or number of strikes per specified area. The soundings used to determine the flow regimes were taken at Miami (MIA), Tampa (TBW), and Jacksonville (JAX), FL, and the lightning data for the strike densities came from the National Lightning Detection Network (NLDN). The densities were created on a 2.5 km x 2.5 km grid for every hour of every day during the warm seasons in the years 1989-2004. The grids encompass an area that includes the entire state of Florida and adjacent Atlantic and Gulf of Mexico waters. Personnel at FSU and NWS TAE provided this data and supporting software for the work performed by the AMU.

Lambert, Winifred↗

NASA NTRS2007

Using Flow Regime Lightning and Sounding Climatologies to Initialize Gridded Lightning Threat Forecasts for East Central Florida

Each morning, the forecasters at the National Weather Service in Melbourne, FL (NWS MLB) produce an experimental cloud-to-ground (CG) lightning threat index map for their county warning area (CWA) that is posted to their web site (httl://www.srh.weather.gov/mlb/ghwo/lightning.shtml) . Given the hazardous nature of lightning in East Central Florida, especially during the warm season months of May September, these maps help users factor the threat of lightning, relative to their location, into their daily plans. The maps are color-coded in five levels from Very Low to Extreme, with threat level definitions based on the probability of lightning occurrence and the expected amount of CG activity. On a day in which thunderstorms are expected, there are typically two or more threat levels depicted spatially across the CWA. The locations of relative lightning threat maxima and minima often depend on the position and orientation of the low-level ridge axis, forecast propagation and interaction of sea/lake/outflow boundaries, expected evolution of moisture and stability fields, and other factors that can influence the spatial distribution of thunderstorms over the CWA. The lightning threat index maps are issued for the 24-hour period beginning at 1200 UTC each day with a grid resolution of 5 km x 5 km. Product preparation is performed on the AWIPS Graphical Forecast Editor (GFE), which is the standard NWS platform for graphical editing. Until recently, the forecasters created each map manually, starting with a blank map. To improve efficiency of the forecast process, NWS MLB requested that the Applied Meteorology Unit (AMU) create gridded warm season lightning climatologies that could be used as first-guess inputs to initialize lightning threat index maps. The gridded values requested included CG strike densities and frequency of occurrence stratified by synoptic-scale flow regime. The intent was to improve consistency between forecasters while allowing them to focus on the mesoscale detail of the forecast. Several studies took place at the Florida State University (FSU) and NWS Tallahassee (TAE) in which they created daily flow regimes using Florida 1200 UTC synoptic soundings and CG strike densities, or number of strikes per specified area. The soundings used to determine the flow regimes were taken at Miami (MIA), Tampa (TBW), and Jacksonville (JAX), FL, and the lightning data for the strike densities came from the National Lightning Detection Network (NLDN). The densities were created on a 2.5 km x 2.5 km grid for every hour of every day during the warm seasons in the years 1989-2004. The grids encompass an area that includes the entire state of Florida and adjacent Atlantic and Gulf of Mexico waters. Personnel at FSU and NWS TAE provided this data and supporting software for the work performed by the AMU.

Lambert, Winifred↗

NASA NTRS1994

Galileo mission planning for Low Gain Antenna based operations

The Galileo mission operations concept is undergoing substantial redesign, necessitated by the deployment failure of the High Gain Antenna, while the spacecraft is on its way to Jupiter. The new design applies state-of-the-art technology and processes to increase the telemetry rate available through the Low Gain Antenna and to increase the information density of the telemetry. This paper describes the mission planning process being developed as part of this redesign. Principal topics include a brief description of the new mission concept and anticipated science return (these have been covered more extensively in earlier papers), identification of key drivers on the mission planning process, a description of the process and its implementation schedule, a discussion of the application of automated mission planning tool to the process, and a status report on mission planning work to date. Galileo enhancements include extensive reprogramming of on-board computers and substantial hard ware and software upgrades for the Deep Space Network (DSN). The principal mode of operation will be onboard recording of science data followed by extended playback periods. A variety of techniques will be used to compress and edit the data both before recording and during playback. A highly-compressed real-time science data stream will also be important. The telemetry rate will be increased using advanced coding techniques and advanced receivers. Galileo mission planning for orbital operations now involves partitioning of several scarce resources. Particularly difficult are division of the telemetry among the many users (eleven instruments, radio science, engineering monitoring, and navigation) and allocation of space on the tape recorder at each of the ten satellite encounters. The planning process is complicated by uncertainty in forecast performance of the DSN modifications and the non-deterministic nature of the new data compression schemes. Key mission planning steps include quantifying resource or capabilities to be allocated, prioritizing science observations and estimating resource needs for each, working inter-and intra-orbit trades of these resources among the Project elements, and planning real-time science activity. The first major mission planning activity, a high level, orbit-by-orbit allocation of resources among science objectives, has already been completed; and results are illustrated in the paper. To make efficient use of limited resources, Galileo mission planning will rely on automated mission planning tools capable of dealing with interactions among time-varying downlink capability, real-time science and engineering data transmission, and playback of recorded data. A new generic mission planning tool is being adapted for this purpose.

Gershman, R.↗

NASA NTRSDate not supplied

Py MILab: Capturing, Analyzing and Storing Test Data

Integrated Computational Materials Engineering (ICME) has recently received widespread attention due to its promises in reducing dependence on physical testing for engineering design by relying on simulation, reducing both time and cost to market for various applications. ICME however requires validated multiscale material models, which is heavily dependent on available test data with full material and test pedigree, including material processing, test and measurement equipment, raw data collection, and analysis methodology and results. Populating searchable information management systems with such rich data sets is often burdensome for data producers, resulting in a lack of findable data for modelers to validate and verify their models. To overcome these cultural barriers to ICME, NASA has developed of various database-integration toolsets that perform both data management activities within the organization’s best practices with additional functionality that relieves the effort of the data producer and promotes adoption of information management system. One such tool currently under development is Py MILab, an automatic framework for automatic capturing, analysis, maintenance, and storage of material test data. Py MILab uses a modular approach for capturing raw data, analyzing the data, and storing the data in a database, interfaced by neutral file structures, to promote plug-and-play capabilities for various analysis types. TMAnalysis is a Python-based tool that performs automatic data reduction and analysis of uniaxial thermomechanical test data. The TMAnalysis toolset can be implemented within the Analysis module of Py MILab, and thus requires a populated neutral file form the Raw Data Module of Py MILab and outputs a Analysis neutral file compatible with the Database Module of Py MILab. TMAnalysis is able to perform automatic segmentation of multistage tests and perform data analysis and reduction, including determination of point-wise properties in tension, compression, and shear, analysis of stress relaxation tests, creep analysis and zone identification, and combination of these stage types for tests with complex loading histories. The TMAnalysis code is accompanied with a graphical user interface (GUI) that allows users to easily analyze test data in bulk, verify the automatic, consistent analysis performed by the backend code, and edit stage segmentation if necessary before producing the output neutral files, ensuring data is properly analyzed and maintained with full traceability.

Data management↗

NASA NTRS1988

Object-oriented fault tree evaluation program for quantitative analyses

Object-oriented programming can be combined with fault free techniques to give a significantly improved environment for evaluating the safety and reliability of large complex systems for space missions. Deep knowledge about system components and interactions, available from reliability studies and other sources, can be described using objects that make up a knowledge base. This knowledge base can be interrogated throughout the design process, during system testing, and during operation, and can be easily modified to reflect design changes in order to maintain a consistent information source. An object-oriented environment for reliability assessment has been developed on a Texas Instrument (TI) Explorer LISP workstation. The program, which directly evaluates system fault trees, utilizes the object-oriented extension to LISP called Flavors that is available on the Explorer. The object representation of a fault tree facilitates the storage and retrieval of information associated with each event in the tree, including tree structural information and intermediate results obtained during the tree reduction process. Reliability data associated with each basic event are stored in the fault tree objects. The object-oriented environment on the Explorer also includes a graphical tree editor which was modified to display and edit the fault trees.

Patterson-Hine, F. A.↗

NASA NTRS1997

Using Common Graphics Paradigms Implemented in a Java Applet to Represent Complex Scheduling Requirements

The experiments planned for the International Space Station promise to be complex, lengthy and diverse. The scarcity of the space station resources will cause significant competition for resources between experiments. The scheduling job facing the Space Station mission planning software requires a concise and comprehensive description of the experiments' requirements (to ensure a valid schedule) and a good description of the experiments' flexibility (to effectively utilize available resources). In addition, the continuous operation of the station, the wide geographic dispersion of station users, and the budgetary pressure to reduce operations manpower make a low-cost solution mandatory. A graphical representation of the scheduling requirements for station payloads implemented via an Internet-based application promises to be an elegant solution that addresses all of these issues. The graphical representation of experiment requirements permits a station user to describe his experiment by defining "activities" and "sequences of activities". Activities define the resource requirements (with alternatives) and other quantitative constraints of tasks to be performed. Activities definitions use an "outline" graphics paradigm. Sequences define the time relationships between activities. Sequences may also define time relationships with activities of other payloads or space station systems. Sequences of activities are described by a "network" graphics paradigm. The bulk of this paper will describe the graphical approach to representing requirements and provide examples that show the ease and clarity with which complex requirements can be represented. A Java applet, to run in a web browser, is being developed to support the graphical representation of payload scheduling requirements. Implementing the entry and editing of requirements via the web solves the problems introduced by the geographic dispersion of users. Reducing manpower is accomplished by developing a concise representation which eliminates the misunderstanding possible with verbose representations and which captures the complete requirements and flexibility of the experiments.

Jaap, John↗

NASA NTRS2016

Pilot Critical Incident Reports as a Means to Identify Human Factors of Remotely Piloted Aircraft

It has been estimated that aviation accidents are typically preceded by numerous minor incidents arising from the same causal factors that ultimately produced the accident. Accident databases provide in-depth information on a relatively small number of occurrences, however incident databases have the potential to provide insights into the human factors of Remotely Piloted Aircraft System (RPAS) operations based on a larger volume of less-detailed reports. Currently, there is a lack of incident data dealing with the human factors of unmanned aircraft systems. An exploratory study is being conducted to examine the feasibility of collecting voluntary critical incident reports from RPAS pilots. Twenty-three experienced RPAS pilots volunteered to participate in focus groups in which they described critical incidents from their own experience. Participants were asked to recall (1) incidents that revealed a system flaw, or (2) highlighted a case where the human operator contributed to system resilience or mission success. Participants were asked to only report incidents that could be included in a public document. During each focus group session, a note taker produced a de-identified written record of the incident narratives. At the end of the session, participants reviewed each written incident report, and made edits and corrections as necessary. The incidents were later analyzed to identify contributing factors, with a focus on design issues that either hindered or assisted the pilot during the events. A total of 90 incidents were reported. Human factor issues included the impact of reduced sensory cues, traffic separation in the absence of an out-the-window view, control latencies, vigilance during monotonous and ultra-long endurance flights, control station design considerations, transfer of control between control stations, the management of lost link procedures, and decision-making during emergencies. Pilots participated willingly and enthusiastically in the study, and generally had little difficulty recalling critical incidents. The results suggest that pilot interviews can be a productive method of gathering information on incidents that might not otherwise be reported. Some of the issues described in the reports have received significant attention in the literature, or are analogous to human factors of manned aircraft. In other cases, incident reports involved human factors that are poorly understood, and have not yet been the subject of extensive study. Although many of the reported incidents were related to pilot error, the participants also provided examples of the positive contribution that humans make to the operation of highly-automated systems.

unmanned aircraft systems↗

NASA NTRS2016

C2-Related Incidents Reported by UAS Pilots

unmanned aircraft systems↗

NASA NTRS2017

Development and Testing of Harpoon-Based Approaches for Collecting Comet Samples (Video Supplement)

This video supplement contains a set of videos created during the approximately 10-year-long course of developing and testing the Goddard Space Flight Center (GSFC) harpoon-based approach for collecting comet samples. The purpose of the videos is to illustrate various design concepts used in this method of acquiring samples of comet material, the testing used to verify the concepts, and the evolution of designs and testing. To play the videos this PDF needs to be opened in the freeware Adobe Reader. They do not seem to play while within a browser. While this supplement can be used as a stand-alone document, it is intended to augment its parent document of the same title, Development and Testing of Harpoon-Based Approaches for Collecting Comet Samples (NASA/CR-2017-219018; this document is accessible from the website: https://ssed.gsfc.nasa.gov/harpoon/SAS_Paper-V1.pdf). The parent document, which only contains text and figures, describes the overall development and testing effort and contains references to each of the videos in this supplement. Thus, the videos are primarily intended to augment the information provided by the text and figures in the parent document. This approach was followed to allow the file size of the parent document to remain small enough to facilitate downloading and storage. Some of the videos were created by other organizations, Johns Hopkins University Applied Physics Laboratory (JHU APL) and the German Aerospace Center called, the Deutsches Zentrum für Luft- und Raumfahrt (DLR), who are partnering with GSFC on developing this technology. Each video is accompanied by text that provides a summary description of its nature and purpose, as well as the identity of the authors. All videos have been edited to only show key parts of the testing. Although not all videos have sound, the sound has been retained in those that have it. Also, each video has been given one or more title screens to clarify what is going in different phases of the video.

Purves, Lloyd↗

NASA NTRS1997

Walking to Olympus: An EVA Chronology

Spacewalkers enjoy a view of Earth once reserved for Apollo, Zeus, and other denizens of Mt. Olympus. During humanity's first extravehicular activity (EVA), Alexei Leonov floated above Gibraltar, the rock ancient seafarers saw as the gateway to the great unknown Atlantic. The symbolism was clear, Leonov stepped past a new Gibraltar when he stepped into space. More than 32 years and 154 EVAs later, Jerry Linenger conducted an EVA with Vladimir Tsibliyev as part of International Space Station Phase 1. They floated together above Gibraltar. Today the symbolism has new meaning: humanity is starting to think of stepping out of Earth orbit, space travel's new Gibraltar, and perhaps obtaining a new olympian view, a close-up look at Olympus Mons on Mars. Walking to Olympus: An EVA Chronology chronicles the 154 EVAs conducted from March 1965 to April 1997. It is intended to make clear the crucial role played by EVA in the history of spaceflight, as well as to chronicle the large body of EVA "lessons learned." Russia and the U.S. define EVA differently. Russian cosmonauts are said to perform EVA any time they are in vacuum in a space suit. A U.S. astronaut must have at least his head outside his spacecraft before he is said to perform an EVA. The difference is based in differing spacecraft design philoso- phies. Russian and Soviet spacecraft have always had a specialized airlock through which the EVA cosmonaut egressed, leaving the main habitable volume of the spacecraft pressurized. The U.S. Gemini and Apollo vehicles, on the other hand, depressurized their entire habitable volume for egress. In this document, we apply the Russian definition to Russian EVAS, and the U.S. definition to U.S. EVAS. Thus, for example, Gemini 4 Command Pilot James McDivitt does not share the honor of being first American spacewalker with Ed White, even though he was suited and in vacuum when White stepped out into space. Non-EVA spaceflights are listed in the chronology to provide context and to display the large num- ber of flights in which EVA played a role. This approach also makes apparent significant EVA gaps, for example, the U.S. gap between 1985 and 1991 following the Challenger accident. This NASA History Monograph is an edited extract from an extensive EVA Chronology and Reference Book being produced by the EVA Project Office, NASA Johnson Space Center, Houston, Texas. The larger work will be published as part of the NASA Formal Series in 1998. The authors gratefully acknowledge the assistance rendered by Max Ary, Ashot Bakunts, Gert-Jan Bartelds, Frank Cepollina, Andrew Chaikin, Phillip Clark, Richard Fullerton, Steven Glenn, Linda Godwin, Jennifer Green, Greg Harris, Clifford Hess, Jeffrey Hoffman, David Homan, Steven Hopkins, Nicholas Johnson, Eric Jones, Neville Kidger, Joseph Kosmo, Alexei Lebedev, Mark Lee, James LeBlanc, Dmitri Leshchenskii, Jerry Linenger, Igor Lissov, James McBarron, Clay McCullough, Joseph McMann, Story Musgrave, Dennis Newkirk, James Oberg, Joel Powell, Lee Saegesser, Andy Salmon, Glen Swanson, Joseph Tatarewicz, Kathy Thornton, Chris Vandenberg, Charles Vick, Bert Vis, David Woods, Mike Wright, John Young, and Keith Zimmerman. Special thanks to Laurie Buchanan, John Charles, Janet Kovacevich, Joseph Loftus, Sue McDonald, Martha Munies, Colleen Rapp, and Jerry Ross. Any errors remain the responsibility of the authors.

Portree, David S. F.↗

NASA NTRS1989

Space physics analysis network node directory (The Yellow Pages): Fourth edition

The Space Physics Analysis Network (SPAN) is a component of the global DECnet Internet, which has over 17,000 host computers. The growth of SPAN from its implementation in 1981 to its present size of well over 2,500 registered SPAN host computers, has created a need for users to acquire timely information about the network through a central source. The SPAN Network Information Center (SPAN-NIC) an online facility managed by the National Space Science Data Center (NSSDC) was developed to meet this need for SPAN-wide information. The remote node descriptive information in this document is not currently contained in the SPAN-NIC database, but will be incorporated in the near future. Access to this information is also available to non-DECnet users over a variety of networks such as Telenet, the NASA Packet Switched System (NPSS), and the TCP/IP Internet. This publication serves as the Yellow Pages for SPAN node information. The document also provides key information concerning other computer networks connected to SPAN, nodes associated with each SPAN routing center, science discipline nodes, contacts for primary SPAN nodes, and SPAN reference information. A section on DECnet Internetworking discusses SPAN connections with other wide-area DECnet networks (many with thousands of nodes each). Another section lists node names and their disciplines, countries, and institutions in the SPAN Network Information Center Online Data Base System. All remote sites connected to US-SPAN and European-SPAN (E-SPAN) are indexed. Also provided is information on the SPAN tail circuits, i.e., those remote nodes connected directly to a SPAN routing center, which is the local point of contact for resolving SPAN-related problems. Reference material is included for those who wish to know more about SPAN. Because of the rapid growth of SPAN, the SPAN Yellow Pages is reissued periodically.

Peters, David J.↗

NASA NTRS2009

Desktop Application Program to Simulate Cargo-Air-Drop Tests

The DSS Application is a computer program comprising a Windows version of the UNIX-based Decelerator System Simulation (DSS) coupled with an Excel front end. The DSS is an executable code that simulates the dynamics of airdropped cargo from first motion in an aircraft through landing. The bare DSS is difficult to use; the front end makes it easy to use. All inputs to the DSS, control of execution of the DSS, and postprocessing and plotting of outputs are handled in the front end. The front end is graphics-intensive. The Excel software provides the graphical elements without need for additional programming. Categories of input parameters are divided into separate tabbed windows. Pop-up comments describe each parameter. An error-checking software component evaluates combinations of parameters and alerts the user if an error results. Case files can be created from inputs, making it possible to build cases from previous ones. Simulation output is plotted in 16 charts displayed on a separate worksheet, enabling plotting of multiple DSS cases with flight-test data. Variables assigned to each plot can be changed. Selected input parameters can be edited from the plot sheet for quick sensitivity studies.

Cuthbert, Peter↗