SEARCH · Search NASA

Results for “user acceptance”

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 271 records · Page 15

All sources NASA NTRS DOE OSTI

NASA NTRS1978

Body Building Boons From Apollo

The Exer-Genie program utilizes familiar types of exercise, such as isometrics (pushing or pulling against an immovable object) and isotonics (motive exercises such as calisthenics or weight lifting) but with the important added factor of controlled resistance. The device is an arrangement of hand grips and nylon cord wrapped around an aluminum shaft. Controlled friction determines the resistance and the user can set the amount of resistive force to his own physical conditioning needs. Since Apollo days, the Exer-Genie and a similar device called the Apollo Exerciser have found wide acceptance among professional, collegiate and high school athletic teams, and among the growing number of individuals interested in physical fitness. These devices are efficient and economical replacements for conventional conditioning equipment and extremely versatile, allowing more than 100 basic exercises for shaping up specific muscle groups.

Source record↗

NASA NTRS1990

Path programmable logic: A structured design method for digital and/or mixed analog integrated circuits

The design of Integrated Circuits has evolved past the black art practiced by a few semiconductor companies to a world wide community of users. This was basically accomplished by the development of computer aided design tools which were made available to this community. As the tools matured into different components of the design task they were accepted into the community at large. However, the next step in this evolution is being ignored by the large tool vendors hindering the continuation of this process. With system level definition and simulation through the logic specification well understood, why is the physical generation so blatantly ignored. This portion of the development is still treated as an isolated task with information being passed from the designer to the layout function. Some form of result given back but it severely lacks full definition of what has transpired. The level of integration in I.C.'s for tomorrow, whether through new processes or applications will require higher speeds, increased transistor density, and non-digital performance which can only be achieved through attention to the physical implementation.

Taylor, B.↗

NASA NTRS2000

Optical Performance Modeling of FUSE Telescope Mirror

We describe the Metrology Data Processor (METDAT), the Optical Surface Analysis Code (OSAC), and their application to the image evaluation of the Far Ultraviolet Spectroscopic Explorer (FUSE) mirrors. The FUSE instrument - designed and developed by the Johns Hopkins University and launched in June 1999 is an astrophysics satellite which provides high resolution spectra (lambda/Delta(lambda) = 20,000 - 25,000) in the wavelength region from 90.5 to 118.7 nm The FUSE instrument is comprised of four co-aligned, normal incidence, off-axis parabolic mirrors, four Rowland circle spectrograph channels with holographic gratings, and delay line microchannel plate detectors. The OSAC code provides a comprehensive analysis of optical system performance, including the effects of optical surface misalignments, low spatial frequency deformations described by discrete polynomial terms, mid- and high-spatial frequency deformations (surface roughness), and diffraction due to the finite size of the aperture. Both normal incidence (traditionally infrared, visible, and near ultraviolet mirror systems) and grazing incidence (x-ray mirror systems) systems can be analyzed. The code also properly accounts for reflectance losses on the mirror surfaces. Low frequency surface errors are described in OSAC by using Zernike polynomials for normal incidence mirrors and Legendre-Fourier polynomials for grazing incidence mirrors. The scatter analysis of the mirror is based on scalar scatter theory. The program accepts simple autocovariance (ACV) function models or power spectral density (PSD) models derived from mirror surface metrology data as input to the scatter calculation. The end product of the program is a user-defined pixel array containing the system Point Spread Function (PSF). The METDAT routine is used in conjunction with the OSAC program. This code reads in laboratory metrology data in a normalized format. The code then fits the data using Zernike polynomials for normal incidence systems or Legendre-Fourier polynomials for grazing incidence systems. It removes low order terms from the metrology data, calculates statistical ACV or PSD functions, and fits these data to OSAC models for the scatter analysis. In this paper we briefly describe the laboratory image testing of FUSE spare mirror performed in the near and vacuum ultraviolet at John Hopkins University and OSAC modeling of the test setup performed at NASA/GSFC. The test setup is a double-pass configuration consisting of a Hg discharge source, the FUSE off-axis parabolic mirror under test, an autocollimating flat mirror, and a tomographic imaging detector. Two additional, small fold flats are used in the optical train to accommodate the light source and the detector. The modeling is based on Zernike fitting and PSD analysis of surface metrology data measured by both the mirror vendor (Tinsley) and JHU. The results of our models agree well with the laboratory imaging data, thus validating our theoretical model. Finally, we predict the imaging performance of FUSE mirrors in their flight configuration at far-ultraviolet wavelengths.

Saha, Timo T.↗

NASA NTRS2015

Sample Acquisition and Analytical Chemistry Challenges to Verifying Compliance to Aviators Breathing Oxygen (ABO) Purity Specification

NASA has been developing and testing two different types of oxygen separation systems. One type of oxygen separation system uses pressure swing technology, the other type uses a solid electrolyte electrochemical oxygen separation cell. Both development systems have been subjected to long term testing, and performance testing under a variety of environmental and operational conditions. Testing these two systems revealed that measuring the product purity of oxygen, and determining if an oxygen separation device meets Aviator's Breathing Oxygen (ABO) specifications is a subtle and sometimes difficult analytical chemistry job. Verifying product purity of cryogenically produced oxygen presents a different set of analytical chemistry challenges. This presentation will describe some of the sample acquisition and analytical chemistry challenges presented by verifying oxygen produced by an oxygen separator - and verifying oxygen produced by cryogenic separation processes. The primary contaminant that causes gas samples to fail to meet ABO requirements is water. The maximum amount of water vapor allowed is 7 ppmv. The principal challenge of verifying oxygen produced by an oxygen separator is that it is produced relatively slowly, and at comparatively low temperatures. A short term failure that occurs for just a few minutes in the course of a 1 week run could cause an entire tank to be rejected. Continuous monitoring of oxygen purity and water vapor could identify problems as soon as they occur. Long term oxygen separator tests were instrumented with an oxygen analyzer and with an hygrometer: a GE Moisture Monitor Series 35. This hygrometer uses an aluminum oxide sensor. The user's manual does not report this, but long term exposure to pure oxygen causes the aluminum oxide sensor head to bias dry. Oxygen product that exceeded the 7 ppm specification was improperly accepted, because the sensor had biased. The bias is permanent - exposure to air does not cause the sensor to return to its original response - but the bias can be accounted for by recalibrating the sensor. After this issue was found, continuous measurements of water vapor in the oxygen product were made using an FTIR. The FTIR cell is relatively large, so response time is slow - but moisture measurements were repeatable and accurate. Verifying ABO compliance for oxygen produced by commercial cryogenic processes has a different set of sample acquisition and analytical chemistry challenges. Customers want analytical chemists to conserve as much as possible. Hygrometers are not exposed to hours of continuous flow of oxygen, so they don't bias, but small amounts of contamination in valves can cause a "fail". K bottles are periodically cleaned and recertified - after cleaning residual moisture can cause a "fail". Operators let bottle pressure drop to room pressure, introduce outside air into the bottle, and the subsequent fill will "fail". Outside storage of K‐bottles has allowed enough in‐leakage, so contents will "fail".

Graf, John↗

NASA NTRS2005

Development of the Architectural Simulation Model for Future Launch Systems and its Application to an Existing Launch Fleet

A significant portion of lifecycle costs for launch vehicles are generated during the operations phase. Research indicates that operations costs can account for a large percentage of the total life-cycle costs of reusable space transportation systems. These costs are largely determined by decisions made early during conceptual design. Therefore, operational considerations are an important part of vehicle design and concept analysis process that needs to be modeled and studied early in the design phase. However, this is a difficult and challenging task due to uncertainties of operations definitions, the dynamic and combinatorial nature of the processes, and lack of analytical models and the scarcity of historical data during the conceptual design phase. Ultimately, NASA would like to know the best mix of launch vehicle concepts that would meet the missions launch dates at the minimum cost. To answer this question, we first need to develop a model to estimate the total cost, including the operational cost, to accomplish this set of missions. In this project, we have developed and implemented a discrete-event simulation model using ARENA (a simulation modeling environment) to determine this cost assessment. Discrete-event simulation is widely used in modeling complex systems, including transportation systems, due to its flexibility, and ability to capture the dynamics of the system. The simulation model accepts manifest inputs including the set of missions that need to be accomplished over a period of time, the clients (e.g., NASA or DoD) who wish to transport the payload to space, the payload weights, and their destinations (e.g., International Space Station, LEO, or GEO). A user of the simulation model can define an architecture of reusable or expendable launch vehicles to achieve these missions. Launch vehicles may belong to different families where each family may have it own set of resources, processing times, and cost factors. The goal is to capture the required resource levels of the major launch elements and their required facilities. The model s output can show whether or not a certain architecture of vehicles can meet the launch dates, and if not, how much the delay cost would be. It will also produce aggregate figures of missions cost based on element procurement cost, processing cost, cargo integration cost, delay cost, and mission support cost. One of the most useful features of this model is that it is stochastic where it accepts statistical distributions to represent the processing times mimicking the stochastic nature of real systems.

Rabadi, Ghaith↗

NASA NTRS1994

New Developments and Research Findings: NASA Hydrazine Arcjets

In 1984, the market for commercial geosynchronous communications satellites (comsats) was expanding and there was strong competition between spacecraft builders for market share. The propellant required for the north-south stationkeeping (NSSK) function was a major mission limiter, and the small chemical and resistojet systems then in use were at or near their physical limits. Thus, conditions were right for the development of a high performance NSSK system, and after an extensive survey of both propulsion technologies and the aerospace community, the NASA program chose hydrazine arcjets for development. A joint government/industry development program ensued which culminated in the acceptance of arcjet technology. NASA efforts included fundamental feasibility assessments, hardware development and verification, and multiple efforts aimed at the demonstration of critical operational characteristics of arcjet systems. Throughout the program, constant contact with the user community was maintained to determine system requirements. Both contracted and cooperative programs with industry were supported. First generation, kW-class arcjets are now operational for NSSK on the Telstar 401 satellite launched in December of 1993 and are baselined for use on multiple future satellite series (Intelsat 8, AsiaSat, Echostar). Arcjet development efforts are now focusing on the development of both high performance (600 s), 2 kW thrusters for application on next generation comsats and low power (Pe approximately 0.5 kW) for a variety of applications on power limited satellites. This paper presents a review of the NASA's role in the development of hydrazine arcjets with a focus on approaches, lessons learned, and the future.

Curren, Francis M.↗

NASA NTRS1996

ACTS (Advanced Communications Technology Satellite) Propagation Experiment: Preprocessing Software User's Manual

The preprocessing software manual describes the Actspp program originally developed to observe and diagnose Advanced Communications Technology Satellite (ACTS) propagation terminal/receiver problems. However, it has been quite useful for automating the preprocessing functions needed to convert the terminal output to useful attenuation estimates. Prior to having data acceptable for archival functions, the individual receiver system must be calibrated and the power level shifts caused by ranging tone modulation must be received. Actspp provides three output files: the daylog, the diurnal coefficient file, and the file that contains calibration information.

Crane, Robert K.↗

NASA NTRS2017

Airborne Trajectory Management (ABTM): A Blueprint for Greater Autonomy in Air Traffic Management

The aviation users of the National Airspace System (NAS) - the airlines, General Aviation (GA), the military and, most recently, operators of Unmanned Aircraft Systems (UAS) - are constrained in their operations by the design of the current paradigm for air traffic control (ATC). Some of these constraints include ATC preferred routes, departure fix restrictions and airspace ground delay programs. As a result, most flights cannot operate on their most efficient business trajectories and a great many flights are delayed even getting into the air, which imposes a significant challenge to maintaining efficient flight and network operations. Rather than accepting ever more sophisticated scheduling solutions to accommodate the existing constraints in the airspace, a series of increasingly capable airborne technologies, integrated with planned improvements in the ground system through the Federal Aviation Administration (FAA) Next Generation Air Traffic Management System (NextGen) programs, could produce much greater operational flexibility for flight path optimization by the aviation system users. These capabilities, described in research coming out of NASA's Aeronautics Research Mission Directorate, can maintain or improve operational safety while taking advantage of air and ground NextGen technologies in novel ways. The underlying premise is that the nation's physical airspace is still abundant and underused, and that the delays and inefficient flight operations resulting from artificial structure in airspace use and procedural constraints on those operations may not be necessary for safe and efficient flight. This article is not an indictment of today's NAS or the people who run it. Indeed, it is an exceptional achievement that Air Traffic Management (ATM) - the complex human/machine conglomeration of communications, navigation and surveillance equipment and the rules and procedures for controlling traffic in the airspace - has both the capacity and enables the degree of efficiency in air travel that it does. But it is also true that sixty years of the "radar religion" (i.e., reliance on radar-based command and control) has produced several generations of ATM system operators and researchers who believe that introducing automation within the existing functional structure of ATM is the only way to "modernize" the system. Even NextGen, which began as a proposal for "transformational" change in the way ATC is performed, has morphed over the last decade and a half to become just the inclusion of Global Positioning System (GPS) for navigation, Automatic Dependent Surveillance Broadcast (ADS-B) for surveillance, and Data Communications (Data Comm) for communications, while still operating in rigidly structured airspace with human controllers being responsible for separation and traffic flow management (TFM) within defined sectors of airspace, using the same horizontal separation standards that have been in use since raw primary radar was introduced in the 1950s. No system as massive as the current NAS ATM can be replaced with a better system while simultaneously meeting the transportation and other aviation needs of the nation. A new generation of more flexible operations must emerge and yet coexist in harmony with the current operation (i.e., share the same airspace without segregation), thereby enabling a long-term transformation to take place in the way increasing numbers of flights are handled. Market forces will be the ultimate driver of this transformation, and investment realities mandate that real benefits must accrue to the first operators to adopt these new capabilities. In fact, the kinds of missions envisioned in the emerging world of UAS operations, unachievable under conventional ATM, demand that this transformation take place. Airborne Trajectory Management (ABTM) is proposed as a series of transformational steps leading to vastly increased flexibility in flight operations and capacity in the airspace to accommodate many varied airspace uses while improving safety. As will be described, ABTM enables the gradual emergence of a new paradigm for user-based trajectory management in ATM that brings tangible benefits to equipped operators at every step while leveraging the air and ground investments of NextGen. There are five steps in this ABTM transformation.1 NASA has extensively studied the first and last of these steps, and a roadmap of increasing capabilities and benefits is proposed for bridging between these operational concepts.

Cotton, William B.↗

NASA NTRS1976

TPGITF user's manual

The primary purpose of TPG interface (TPGITF) software is to create test patterns, according to a mathematical model, for a real device. In order for the device actually to be tested or to be accurately simulated, a means is required to transform the TPGITF generated test into forms acceptable as input to logic test equipment or to a software logic simulator. The MACRODATA-200 Logic Test System and the LOGSIM logic simulator are the particular systems supported by the TPGITF software. A description is presented of the TPGITF software processor. It is assumed that the reader is familiar with the TPG, LOGSIM, and TOIL systems. Flow charts are given.

Pitts, E. R.↗

NASA NTRS2008

Statistical Short-Range Guidance for Peak Wind Speed Forecasts at Edwards Air Force Base, CA

The peak winds near the surface are an important forecast element for Space Shuttle landings. As defined in the Shuttle Flight Rules (FRs), there are peak wind thresholds that cannot be exceeded in order to ensure the safety of the shuttle during landing operations. The National Weather Service Spaceflight Meteorology Group (SMG) is responsible for weather forecasts for all shuttle landings. They indicate peak winds are a challenging parameter to forecast. To alleviate the difficulty in making such wind forecasts, the Applied Meteorology Unit (AMTJ) developed a personal computer based graphical user interface (GUI) for displaying peak wind climatology and probabilities of exceeding peak-wind thresholds for the Shuttle Landing Facility (SLF) at Kennedy Space Center. However, the shuttle must land at Edwards Air Force Base (EAFB) in southern California when weather conditions at Kennedy Space Center in Florida are not acceptable, so SMG forecasters requested that a similar tool be developed for EAFB. Marshall Space Flight Center (MSFC) personnel archived and performed quality control of 2-minute average and 10-minute peak wind speeds at each tower adjacent to the main runway at EAFB from 1997- 2004. They calculated wind climatologies and probabilities of average peak wind occurrence based on the average speed. The climatologies were calculated for each tower and month, and were stratified by hour, direction, and direction/hour. For the probabilities of peak wind occurrence, MSFC calculated empirical and modeled probabilities of meeting or exceeding specific 10-minute peak wind speeds using probability density functions. The AMU obtained and reformatted the data into Microsoft Excel PivotTables, which allows users to display different values with point-click-drag techniques. The GUT was then created from the PivotTables using Visual Basic for Applications code. The GUI is run through a macro within Microsoft Excel and allows forecasters to quickly display and interpret peak wind climatology and likelihoods in a fast-paced operational environment. A summary of how the peak wind climatologies and probabilities were created and an overview of the GUT will be presented.

Dreher, Joseph↗

NASA NTRS1992

ROSAT data analysis with EXSAS

For the x-ray observatory ROSAT, data from survey and pointed mission phases taken with different focal plane instruments and according to a complex mission timeline have to be handled. Data analysis therefore puts high demands on appropriate software tools. With EXSAS - the Extended Scientific Analysis System developed with an effort of 20 man years by the German ROSAT Scientific Data Center - a comfortable system for the reduction of data from the ROSAT x-ray and XUV instruments has been made available. EXSAS comprises a large collection of application modules as typically required in analyzing data of this wavelength regime and runs as a specific context in the wide-spread ESO-MIDAS environment. EXSAS, completely written in FORTRAN 77, takes full advantage of all the standards used in MIDAS and therefore, reflects the same portability (different UNIX installations and VMS). If required, the FORTRAN code also enables users to adapt the software in an easy way to their specific needs. To maintain independence from the specifics of different operating systems also on the data input side, all ROSAT data redistributed in the widely accepted FITS format. Although EXSAS has been developed specifically for data analysis of the ROSAT instruments, its structural design is sufficiently general to serve equally well also data from other X-ray and XUV instruments. EXSAS analysis modules are grouped into 4 application packages dealing with Data Preparation and Instrument Correction, Spatial Analysis, Spectral Analysis and Timing Analysis. A special EXSAS header, read and updated by each application, maintains the general information transfer on the origin, the history and the parameter space of the data stored in tables and images. About 100 genuine commands (most of which offer several additional options) allow to interactively explore the functionality of the system. Up to now 40 institutes all over the world have requested the EXSAS software. Maintenance and regular updates of the software and the comprehensive documentation are provided by the ROSAT Scientific Data Center at Garching.

Zimmermann, H. U.↗

NASA NTRS1997

Current Status and Application of Hazard Definition Technology

A research is performed: to define wake non-encounter & hazard, to provide requirements for sensors, and to obtain input from the user community. This research includes: validating wake encounter simulation models, establishing a metric to quantify the upset potential of a wake encounter, applying hazard metric and simulation models to the commercial fleet for development of candidate acceptable encounter limits, and applying technology to near term problems to evaluate current status of technology. The following lessons are learned from this project: technology is not adequate to determine absolute spacing requirements; time, not distance, determines the duration of the wake hazard; Optimum standards depend on the traffic; Wing span is an important parameter for characterizing both generator and follower; and Short span "biz jets" are easily rolled.

Greene, George C.↗

NASA NTRS1998

Real-Time Payload Control and Monitoring on the World Wide Web

World Wide Web (W3) technologies such as the Hypertext Transfer Protocol (HTTP) and the Java object-oriented programming environment offer a powerful, yet relatively inexpensive, framework for distributed application software development. This paper describes the design of a real-time payload control and monitoring system that was developed with W3 technologies at NASA Ames Research Center. Based on Java Development Toolkit (JDK) 1.1, the system uses an event-driven "publish and subscribe" approach to inter-process communication and graphical user-interface construction. A C Language Integrated Production System (CLIPS) compatible inference engine provides the back-end intelligent data processing capability, while Oracle Relational Database Management System (RDBMS) provides the data management function. Preliminary evaluation shows acceptable performance for some classes of payloads, with Java's portability and multimedia support identified as the most significant benefit.

Sun, Charles↗

NASA NTRS2008

Certifying Auto-Generated Flight Code

Model-based design and automated code generation are being used increasingly at NASA. Many NASA projects now use MathWorks Simulink and Real-Time Workshop for at least some of their modeling and code development. However, there are substantial obstacles to more widespread adoption of code generators in safety-critical domains. Since code generators are typically not qualified, there is no guarantee that their output is correct, and consequently the generated code still needs to be fully tested and certified. Moreover, the regeneration of code can require complete recertification, which offsets many of the advantages of using a generator. Indeed, manual review of autocode can be more challenging than for hand-written code. Since the direct V&V of code generators is too laborious and complicated due to their complex (and often proprietary) nature, we have developed a generator plug-in to support the certification of the auto-generated code. Specifically, the AutoCert tool supports certification by formally verifying that the generated code is free of different safety violations, by constructing an independently verifiable certificate, and by explaining its analysis in a textual form suitable for code reviews. The generated documentation also contains substantial tracing information, allowing users to trace between model, code, documentation, and V&V artifacts. This enables missions to obtain assurance about the safety and reliability of the code without excessive manual V&V effort and, as a consequence, eases the acceptance of code generators in safety-critical contexts. The generation of explicit certificates and textual reports is particularly well-suited to supporting independent V&V. The primary contribution of this approach is the combination of human-friendly documentation with formal analysis. The key technical idea is to exploit the idiomatic nature of auto-generated code in order to automatically infer logical annotations. The annotation inference algorithm itself is generic, and parametrized with respect to a library of coding patterns that depend on the safety policies and the code generator. The patterns characterize the notions of definitions and uses that are specific to the given safety property. For example, for initialization safety, definitions correspond to variable initializations while uses are statements which read a variable, whereas for array bounds safety, definitions are the array declarations, while uses are statements which access an array variable. The inferred annotations are thus highly dependent on the actual program and the properties being proven. The annotations, themselves, need not be trusted, but are crucial to obtain the automatic formal verification of the safety properties without requiring access to the internals of the code generator. The approach has been applied to both in-house and commercial code generators, but is independent of the particular generator used. It is currently being adapted to flight code generated using MathWorks Real-Time Workshop, an automatic code generator that translates from Simulink/Stateflow models into embedded C code.

Denney, Ewen↗

NASA NTRS2011

Onboard Short Term Plan Viewer

Onboard Short Term Plan Viewer (OSTPV) is a computer program for electronic display of mission plans and timelines, both aboard the International Space Station (ISS) and in ISS ground control stations located in several countries. OSTPV was specifically designed both (1) for use within the limited ISS computing environment and (2) to be compatible with computers used in ground control stations. OSTPV supplants a prior system in which, aboard the ISS, timelines were printed on paper and incorporated into files that also contained other paper documents. Hence, the introduction of OSTPV has both reduced the consumption of resources and saved time in updating plans and timelines. OSTPV accepts, as input, the mission timeline output of a legacy, print-oriented, UNIX-based program called "Consolidated Planning System" and converts the timeline information for display in an interactive, dynamic, Windows Web-based graphical user interface that is used by both the ISS crew and ground control teams in real time. OSTPV enables the ISS crew to electronically indicate execution of timeline steps, launch electronic procedures, and efficiently report to ground control teams on the statuses of ISS activities, all by use of laptop computers aboard the ISS.

Hall, Tim↗

NASA NTRS1975

FORTRAN Automated Code Evaluation System (FACES) user's manual, version 2

A system which provides analysis services for FORTRAN based software systems not normally available from system software is presented. The system is not a compiler, and compiler syntax diagnostics are not duplicated. For maximum adaptation to FORTRAN dialects, the code presented to the system is assumed to be compiler acceptable. The system concentrates on acceptable FORTRAN code features which are likely to produce undesirable results and identifies potential trouble areas before they become execution time malfunctions.

Source record↗

NASA NTRS1972

Film type SO-168 radiation study

Investigations were performed to determine optimum exposure and processing procedures necessary to partially offset the effect of radiation to which film type SO-168 will be exposed during the Skylab Mission. This task became necessary when it was determined that original predictions of 2 to 3 RADS of radiation to which the film will be exposed were too low, and that levels as high as 3.5 to 4.0 RADS may be incurred, thus reducing image quality below an acceptable level. Tests results show that forced processing of type SO-168 film tended to reduce the density range to an unusable level, and that processing to a lower ASA value would provide greater image quality for the user.

Pierce, W. N.↗

NASA NTRS1992

User's manual for Interactive Data Display System (IDDS)

A computer graphics package for the visualization of three-dimensional flow in turbomachinery has been developed and tested. This graphics package, called IDDS (Interactive Data Display System), is able to 'unwrap' the volumetric data cone associated with a centrifugal compressor and display the results in an easy to understand two-dimensional manner. IDDS will provide the majority of the visualization and analysis capability for the ICE (Integrated CFD and Experiment) system. This document is intended to serve as a user's manual for IDDS in a stand-alone mode. Currently, IDDS is capable of plotting two- or three-dimensional simulation data, but work is under way to expand IDDS so that experimental data can be accepted, plotted, and compared with a simulation dataset of the actual hardware being tested.

Stegeman, James D.↗