Teleoperator system man-machine interface requirements for satellite retrieval and satellite servicing. Volume 1: Requirements

NASA Technical Reports Server (NTRS)

Malone, T. B.

1972-01-01

Requirements were determined analytically for the man machine interface for a teleoperator system performing on-orbit satellite retrieval and servicing. Requirements are basically of two types; mission/system requirements, and design requirements or design criteria. Two types of teleoperator systems were considered: a free flying vehicle, and a shuttle attached manipulator. No attempt was made to evaluate the relative effectiveness or efficiency of the two system concepts. The methodology used entailed an application of the Essex Man-Systems analysis technique as well as a complete familiarization with relevant work being performed at government agencies and by private industry.

Training Manual for Elements of Interface Definition and Control

NASA Technical Reports Server (NTRS)

Lalli, Vincent R. (Editor); Kastner, Robert E. (Editor); Hartt, Henry N. (Editor)

1997-01-01

The primary thrust of this manual is to ensure that the format and information needed to control interfaces between equipment are clear and understandable. The emphasis is on controlling the engineering design of the interface and not on the functional performance requirements of the system or the internal workings of the interfacing equipment. Interface control should take place, with rare exception, at the interfacing elements and no further. There are two essential sections of the manual. Chapter 2, Principles of Interface Control, discusses how interfaces are defined. It describes different types of interfaces to be considered and recommends a format for the documentation necessary for adequate interface control. Chapter 3, The Process: Through the Design Phases, provides tailored guidance for interface definition and control. This manual can be used to improve planned or existing interface control processes during system design and development. It can also be used to refresh and update the corporate knowledge base. The information presented herein will reduce the amount of paper and data required in interface definition and control processes by as much as 50 percent and will shorten the time required to prepare an interface control document. It also highlights the essential technical parameters that ensure that flight subsystems will indeed fit together and function as intended after assembly and checkout.

Natural interaction for unmanned systems

NASA Astrophysics Data System (ADS)

Taylor, Glenn; Purman, Ben; Schermerhorn, Paul; Garcia-Sampedro, Guillermo; Lanting, Matt; Quist, Michael; Kawatsu, Chris

2015-05-01

Military unmanned systems today are typically controlled by two methods: tele-operation or menu-based, search-andclick interfaces. Both approaches require the operator's constant vigilance: tele-operation requires constant input to drive the vehicle inch by inch; a menu-based interface requires eyes on the screen in order to search through alternatives and select the right menu item. In both cases, operators spend most of their time and attention driving and minding the unmanned systems rather than on being a warfighter. With these approaches, the platform and interface become more of a burden than a benefit. The availability of inexpensive sensor systems in products such as Microsoft Kinect™ or Nintendo Wii™ has resulted in new ways of interacting with computing systems, but new sensors alone are not enough. Developing useful and usable human-system interfaces requires understanding users and interaction in context: not just what new sensors afford in terms of interaction, but how users want to interact with these systems, for what purpose, and how sensors might enable those interactions. Additionally, the system needs to reliably make sense of the user's inputs in context, translate that interpretation into commands for the unmanned system, and give feedback to the user. In this paper, we describe an example natural interface for unmanned systems, called the Smart Interaction Device (SID), which enables natural two-way interaction with unmanned systems including the use of speech, sketch, and gestures. We present a few example applications SID to different types of unmanned systems and different kinds of interactions.

Atmosphere explorer missions C, D, and E. Spacecraft experiment interface definition study

NASA Technical Reports Server (NTRS)

1972-01-01

The Atmosphere Explorer Missions C, D, & E Spacecraft/Experiment Interface Definition Study is discussed. The objectives of the study included an analysis of the accommodation requirements of the experiments for the three missions, an assessment of the overall effect of these requirements on the spacecraft system design and performance, and the detailed definition of all experiment/spacecraft electrical, mechanical, and environmental interfaces. In addition, the study included the identification and definition of system characteristics required to ensure compatibility with the consolidated STADAN and MSFN communications networks.

An Object-Oriented Graphical User Interface for a Reusable Rocket Engine Intelligent Control System

NASA Technical Reports Server (NTRS)

Litt, Jonathan S.; Musgrave, Jeffrey L.; Guo, Ten-Huei; Paxson, Daniel E.; Wong, Edmond; Saus, Joseph R.; Merrill, Walter C.

1994-01-01

An intelligent control system for reusable rocket engines under development at NASA Lewis Research Center requires a graphical user interface to allow observation of the closed-loop system in operation. The simulation testbed consists of a real-time engine simulation computer, a controls computer, and several auxiliary computers for diagnostics and coordination. The system is set up so that the simulation computer could be replaced by the real engine and the change would be transparent to the control system. Because of the hard real-time requirement of the control computer, putting a graphical user interface on it was not an option. Thus, a separate computer used strictly for the graphical user interface was warranted. An object-oriented LISP-based graphical user interface has been developed on a Texas Instruments Explorer 2+ to indicate the condition of the engine to the observer through plots, animation, interactive graphics, and text.

Step 1:Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Collision Avoidance

NASA Technical Reports Server (NTRS)

2007-01-01

This document provides definition of technology human interface requirements for Collision Avoidance (CA). This was performed through a review of CA-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Access 5 CA work package were considered... Beginning with the HSI high-level functional requirement for CA, and CA technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge CA system status, and (2) the control capability needed by the pilot to obtain CA information and affect an avoidance maneuver. Fundamentally, these requirements provide the candidate CA technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how CA operations and functions should interface with the pilot to provide the necessary CA functionality to the UA-pilot system .Requirements and guidelines for CA are partitioned into four categories: (1) General, (2) Alerting, (3) Guidance, and (4) Cockpit Display of Traffic Information. Each requirement is stated and is supported with a rationale and associated reference(s).

Interface Shape Control Using Localized Heating during Bridgman Growth

NASA Technical Reports Server (NTRS)

Volz, M. P.; Mazuruk, K.; Aggarwal, M. D.; Croll, A.

2008-01-01

Numerical calculations were performed to assess the effect of localized radial heating on the melt-crystal interface shape during vertical Bridgman growth. System parameters examined include the ampoule, melt and crystal thermal conductivities, the magnitude and width of localized heating, and the latent heat of crystallization. Concave interface shapes, typical of semiconductor systems, could be flattened or made convex with localized heating. Although localized heating caused shallower thermal gradients ahead of the interface, the magnitude of the localized heating required for convexity was less than that which resulted in a thermal inversion ahead of the interface. A convex interface shape was most readily achieved with ampoules of lower thermal conductivity. Increasing melt convection tended to flatten the interface, but the amount of radial heating required to achieve a convex interface was essentially independent of the convection intensity.

Shuttle vehicle and mission simulation requirements report, volume 1

NASA Technical Reports Server (NTRS)

Burke, J. F.

1972-01-01

The requirements for the space shuttle vehicle and mission simulation are developed to analyze the systems, mission, operations, and interfaces. The requirements are developed according to the following subject areas: (1) mission envelope, (2) orbit flight dynamics, (3) shuttle vehicle systems, (4) external interfaces, (5) crew procedures, (6) crew station, (7) visual cues, and (8) aural cues. Line drawings and diagrams of the space shuttle are included to explain the various systems and components.

Formal design specification of a Processor Interface Unit

NASA Technical Reports Server (NTRS)

Fura, David A.; Windley, Phillip J.; Cohen, Gerald C.

1992-01-01

This report describes work to formally specify the requirements and design of a processor interface unit (PIU), a single-chip subsystem providing memory-interface bus-interface, and additional support services for a commercial microprocessor within a fault-tolerant computer system. This system, the Fault-Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance-free operation, or both. The need for high-quality design assurance in such applications is an undisputed fact, given the disastrous consequences that even a single design flaw can produce. Thus, the further development and application of formal methods to fault-tolerant systems is of critical importance as these systems see increasing use in modern society.

Step 1: Human System Integration Pilot-Technology Interface Requirements for Weather Management

NASA Technical Reports Server (NTRS)

2005-01-01

This document involves definition of technology interface requirements for Hazardous Weather Avoidance. Technology concepts in use by the Access 5 Weather Management Work Package were considered. Beginning with the Human System Integration (HIS) high-level functional requirement for Hazardous Weather Avoidance, and Hazardous Weather Avoidance technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of hazardous weather, and (2) the control capability needed by the pilot to obtain hazardous weather information. Fundamentally, these requirements provide the candidate Hazardous Weather Avoidance technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Hazardous Weather Avoidance operations and functions should interface with the pilot to provide the necessary Weather Management functionality to the UA-pilot system. Requirements and guidelines for Hazardous Weather Avoidance are partitioned into four categories: (1) Planning En Route (2) Encountering Hazardous Weather En Route, (3) Planning to Destination, and (4) Diversion Planning Alternate Airport. Each requirement is stated and is supported with a rationale and associated reference(s).

Project Interface Requirements Process Including Shuttle Lessons Learned

NASA Technical Reports Server (NTRS)

Bauch, Garland T.

2010-01-01

Most failures occur at interfaces between organizations and hardware. Processing interface requirements at the start of a project life cycle will reduce the likelihood of costly interface changes/failures later. This can be done by adding Interface Control Documents (ICDs) to the Project top level drawing tree, providing technical direction to the Projects for interface requirements, and by funding the interface requirements function directly from the Project Manager's office. The interface requirements function within the Project Systems Engineering and Integration (SE&I) Office would work in-line with the project element design engineers early in the life cycle to enhance communications and negotiate technical issues between the elements. This function would work as the technical arm of the Project Manager to help ensure that the Project cost, schedule, and risk objectives can be met during the Life Cycle. Some ICD Lessons Learned during the Space Shuttle Program (SSP) Life Cycle will include the use of hardware interface photos in the ICD, progressive life cycle design certification by analysis, test, & operations experience, assigning interface design engineers to Element Interface (EI) and Project technical panels, and linking interface design drawings with project build drawings

Flexible Architecture for FPGAs in Embedded Systems

NASA Technical Reports Server (NTRS)

Clark, Duane I.; Lim, Chester N.

2012-01-01

Commonly, field-programmable gate arrays (FPGAs) being developed in cPCI embedded systems include the bus interface in the FPGA. This complicates the development because the interface is complicated and requires a lot of development time and FPGA resources. In addition, flight qualification requires a substantial amount of time be devoted to just this interface. Another complication of putting the cPCI interface into the FPGA being developed is that configuration information loaded into the device by the cPCI microprocessor is lost when a new bit file is loaded, requiring cumbersome operations to return the system to an operational state. Finally, SRAM-based FPGAs are typically programmed via specialized cables and software, with programming files being loaded either directly into the FPGA, or into PROM devices. This can be cumbersome when doing FPGA development in an embedded environment, and does not have an easy path to flight. Currently, FPGAs used in space applications are usually programmed via multiple space-qualified PROM devices that are physically large and require extra circuitry (typically including a separate one-time programmable FPGA) to enable them to be used for this application. This technology adds a cPCI interface device with a simple, flexible, high-performance backend interface supporting multiple backend FPGAs. It includes a mechanism for programming the FPGAs directly via the microprocessor in the embedded system, eliminating specialized hardware, software, and PROM devices and their associated circuitry. It has a direct path to flight, and no extra hardware and minimal software are required to support reprogramming in flight. The device added is currently a small FPGA, but an advantage of this technology is that the design of the device does not change, regardless of the application in which it is being used. This means that it needs to be qualified for flight only once, and is suitable for one-time programmable devices or an application specific integrated circuit (ASIC). An application programming interface (API) further reduces the development time needed to use the interface device in a system.

Step 1: Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Command, Control, and Communications (C3)

NASA Technical Reports Server (NTRS)

2005-01-01

The document provides the Human System Integration(HSI) high-level functional C3 HSI requirements for the interface to the pilot. Description includes (1) the information required by the pilot to have knowledge C3 system status, and (2) the control capability needed by the pilot to obtain C3 information. Fundamentally, these requirements provide the candidate C3 technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how C3 operations and functions should interface with the pilot to provide the necessary C3 functionality to the UA-pilot system. Requirements and guidelines for C3 are partitioned into three categories: (1) Pilot-Air Traffic Control (ATC) Voice Communications (2) Pilot-ATC Data Communications, and (3) command and control of the unmanned aircraft (UA). Each requirement is stated and is supported with a rationale and associated reference(s).

Step 1: Human System Interface (HSI) Functional Requirements Document (FRD). Version 2

NASA Technical Reports Server (NTRS)

2006-01-01

This Functional Requirements Document (FRD) establishes a minimum set of Human System Interface (HSI) functional requirements to achieve the Access 5 Vision of "operating High Altitude, Long Endurance (HALE) Unmanned Aircraft Systems (UAS) routinely, safely, and reliably in the National Airspace System (NAS)". Basically, it provides what functions are necessary to fly UAS in the NAS. The framework used to identify the appropriate functions was the "Aviate, Navigate, Communicate, and Avoid Hazards" structure identified in the Access 5 FRD. As a result, fifteen high-level functional requirements were developed. In addition, several of them have been decomposed into low-level functional requirements to provide more detail.

Human factors issues in telerobotic systems for Space Station Freedom servicing

NASA Technical Reports Server (NTRS)

Malone, Thomas B.; Permenter, Kathryn E.

1990-01-01

Requirements for Space Station Freedom servicing are described and the state-of-the-art for telerobotic system on-orbit servicing of spacecraft is defined. The projected requirements for the Space Station Flight Telerobotic Servicer (FTS) are identified. Finally, the human factors issues in telerobotic servicing are discussed. The human factors issues are basically three: the definition of the role of the human versus automation in system control; the identification of operator-device interface design requirements; and the requirements for development of an operator-machine interface simulation capability.

Human Systems Integration Competency Development for Navy Systems Commands

DTIC Science & Technology

2012-09-01

cognizance of Applied Engineering /Psychology relative to knowledge engineering, training, teamwork, user interface design and decision sciences. KSA...cognizance of Applied Engineering /Psychology relative to knowledge engineering, training, teamwork, user interface design and decision sciences...requirements (as required). Fundamental cognizance of Applied Engineering / Psychology relative to knowledge engineering, training, team work, user

Towards the formal verification of the requirements and design of a processor interface unit: HOL listings

NASA Technical Reports Server (NTRS)

Fura, David A.; Windley, Phillip J.; Cohen, Gerald C.

1993-01-01

This technical report contains the Higher-Order Logic (HOL) listings of the partial verification of the requirements and design for a commercially developed processor interface unit (PIU). The PIU is an interface chip performing memory interface, bus interface, and additional support services for a commercial microprocessor within a fault tolerant computer system. This system, the Fault Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance-free operation, or both. This report contains the actual HOL listings of the PIU verification as it currently exists. Section two of this report contains general-purpose HOL theories and definitions that support the PIU verification. These include arithmetic theories dealing with inequalities and associativity, and a collection of tactics used in the PIU proofs. Section three contains the HOL listings for the completed PIU design verification. Section 4 contains the HOL listings for the partial requirements verification of the P-Port.

Application of power transistors to residential and intermediate rating photovoltaic array power conditioners

NASA Astrophysics Data System (ADS)

Steigerwald, R. L.; Ferraro, A.; Turnbull, F. G.

1983-04-01

Power conditioning systems that interface with photovoltaic arrays are presently investigated for the cases of 5-30 kW residential systems interfacing with a 240-V single-phase utility connection, and 30-200 kW intermediate systems interfacing with a 480-V three-phase utility connection. Both systems require an isolation transformer between the array and the utility interface. A tradeoff study is conducted for numerous transistor and thyristor circuits and configurations, with weighting criteria that include full- and part-load efficiency, size, weight, reliability, ease of control, injected harmonics, reactive power requirements, and parts cost. On the basis of study results, a 10-kW high frequency transistor inverter feeding a high frequency isolation transformer with a sinusoidally shaped current wave was selected.

Development of a graphical user interface for the global land information system (GLIS)

USGS Publications Warehouse

Alstad, Susan R.; Jackson, David A.

1993-01-01

The process of developing a Motif Graphical User Interface for the Global Land Information System (GLIS) involved incorporating user requirements, in-house visual and functional design requirements, and Open Software Foundation (OSF) Motif style guide standards. Motif user interface windows have been developed using the software to support Motif window functions war written using the C programming language. The GLIS architecture was modified to support multiple servers and remote handlers running the X Window System by forming a network of servers and handlers connected by TCP/IP communications. In April 1993, prior to release the GLIS graphical user interface and system architecture modifications were test by developers and users located at the EROS Data Center and 11 beta test sites across the country.

Hands-Free, Heads-Up Control System for Unmanned Ground Vehicles

DTIC Science & Technology

2011-08-10

interface evaluation Industry evaluated two commercial-off-the-shelf (COTS) brain computer interfaces from two companies – Neurosky and Emotiv ...useless, resulting in very low command recognition accuracy. In addition, latency issues plagued the system. Figure 6 Emotiv Headset The... Emotiv system, unlike the Neurosky, required great effort to use and calibrate. It requires 16 foam tips to be wet with saline solution and then

Earth Observatory Satellite system definition study. Report 2: Instrument constraints and interfaces

NASA Technical Reports Server (NTRS)

1974-01-01

The instrument constraints and interface specifications for the Earth Observatory Satellite (EOS) are discussed. The Land Use Classification Mission using a 7 band Thematic Mapper and a 4 band High Resolution Pointable Imager is stressed. The mission and performance of the instruments were reviewed and expanded to reflect the instrument as a part of the total remote sensing system. A preliminary EOS interface handbook is provided to describe the mission and system, to specify the spacecraft interfaces to potential instrument contractors, and to describe the instrument interface data required by the system integration contractor.

Using SysML to model complex systems for security.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Cano, Lester Arturo

2010-08-01

As security systems integrate more Information Technology the design of these systems has tended to become more complex. Some of the most difficult issues in designing Complex Security Systems (CSS) are: Capturing Requirements: Defining Hardware Interfaces: Defining Software Interfaces: Integrating Technologies: Radio Systems: Voice Over IP Systems: Situational Awareness Systems.

Constellation Program Human-System Integration Requirements. Revision E, Nov. 19, 2010

NASA Technical Reports Server (NTRS)

Dory, Jonathan

2010-01-01

The Human-Systems Integration Requirements (HSIR) in this document drive the design of space vehicles, their systems, and equipment with which humans interface in the Constellation Program (CxP). These requirements ensure that the design of Constellation (Cx) systems is centered on the needs, capabilities, and limitations of the human. The HSIR provides requirements to ensure proper integration of human-to-system interfaces. These requirements apply to all mission phases, including pre-launch, ascent, Earth orbit, trans-lunar flight, lunar orbit, lunar landing, lunar ascent, Earth return, Earth entry, Earth landing, post-landing, and recovery. The Constellation Program must meet NASA's Agency-level human rating requirements, which are intended to ensure crew survival without permanent disability. The HSIR provides a key mechanism for achieving human rating of Constellation systems.

Advanced life support study

NASA Technical Reports Server (NTRS)

1991-01-01

Summary reports on each of the eight tasks undertaken by this contract are given. Discussed here is an evaluation of a Closed Ecological Life Support System (CELSS), including modeling and analysis of Physical/Chemical Closed Loop Life Support (P/C CLLS); the Environmental Control and Life Support Systems (ECLSS) evolution - Intermodule Ventilation study; advanced technologies interface requirements relative to ECLSS; an ECLSS resupply analysis; the ECLSS module addition relocation systems engineering analysis; an ECLSS cost/benefit analysis to identify rack-level interface requirements of the alternate technologies evaluated in the ventilation study, with a comparison of these with the rack level interface requirements for the baseline technologies; advanced instrumentation - technology database enhancement; and a clean room survey and assessment of various ECLSS evaluation options for different growth scenarios.

GPS system simulation methodology

NASA Technical Reports Server (NTRS)

Ewing, Thomas F.

1993-01-01

The following topics are presented: background; Global Positioning System (GPS) methodology overview; the graphical user interface (GUI); current models; application to space nuclear power/propulsion; and interfacing requirements. The discussion is presented in vugraph form.

Magnetohydrodynamics (MHD) Engineering Test Facility (ETF) 200 MWe power plant. Design Requirements Document (DRD)

NASA Technical Reports Server (NTRS)

Rigo, H. S.; Bercaw, R. W.; Burkhart, J. A.; Mroz, T. S.; Bents, D. J.; Hatch, A. M.

1981-01-01

A description and the design requirements for the 200 MWe (nominal) net output MHD Engineering Test Facility (ETF) Conceptual Design, are presented. Performance requirements for the plant are identified and process conditions are indicated at interface stations between the major systems comprising the plant. Also included are the description, functions, interfaces and requirements for each of these major systems. The lastest information (1980-1981) from the MHD technology program are integrated with elements of a conventional steam electric power generating plant.

Space shuttle/food system study

NASA Technical Reports Server (NTRS)

1974-01-01

This document establishes the Functional, physical and performance interface requirements are studied between the space shuttle orbiter and the galley water system, the orbiter and the galley electrical system, and the orbiter and the galley structural system. Control of the configuration and design of the applicable interfacing items is intended to maintain compatibility between co-functioning and physically mating items and to assure those performance criteria that are dependent upon the interfacing items.

Orbital Spacecraft Consumables Resupply System (OSCRS): Monopropellant application to space station and OMV automatic refueling impacts of an ELV launch, volume 4

NASA Technical Reports Server (NTRS)

1987-01-01

The use of orbital spacecraft consumables resupply system (OSCRS) at the Space Station is investigated, its use with the orbital maneuvering vehicle, and launch of the OSCRS on an expendable launch vehicles. A system requirements evaluation was performed initially to identify any unique requirements that would impact the design of OSCRS when used at the Space Station. Space Station documents were reviewed to establish requirements and to identify interfaces between the OSCRS, Shuttle, and Space Station, especially the Servicing Facility. The interfaces between OSCRS and the Shuttle consists of an avionics interface for command and control and a structural interface for launch support and for grappling with the Shuttle Remote Manipulator System. For use of the OSCRS at the Space Station, three configurations were evaluated using the results of the interface definition to increase the efficiency of OSCRS and to decrease the launch weight by Station-basing specific OSCRS subsystems. A modular OSCRS was developed in which the major subsystems were Station-based where possible. The configuration of an OSCRS was defined for transport of water to the Space Station.

Inertial Upper Stage (IUS) software analysis

NASA Technical Reports Server (NTRS)

Grayson, W. L.; Nickel, C. E.; Rose, P. L.; Singh, R. P.

1979-01-01

The Inertial Upper Stage (IUS) System, an extension of the Space Transportation System (STS) operating regime to include higher orbits, orbital plane changes, geosynchronous orbits, and interplanetary trajectories is presented. The IUS software design, the IUS software interfaces with other systems, and the cost effectiveness in software verification are described. Tasks of the IUS discussed include: (1) design analysis; (2) validation requirements analysis; (3) interface analysis; and (4) requirements analysis.

User interface issues in supporting human-computer integrated scheduling

NASA Technical Reports Server (NTRS)

Cooper, Lynne P.; Biefeld, Eric W.

1991-01-01

Explored here is the user interface problems encountered with the Operations Missions Planner (OMP) project at the Jet Propulsion Laboratory (JPL). OMP uses a unique iterative approach to planning that places additional requirements on the user interface, particularly to support system development and maintenance. These requirements are necessary to support the concepts of heuristically controlled search, in-progress assessment, and iterative refinement of the schedule. The techniques used to address the OMP interface needs are given.

Communications interface for wireless communications headset

NASA Technical Reports Server (NTRS)

Culotta, Jr., Anthony Joseph (Inventor); Seibert, Marc A. (Inventor)

2004-01-01

A universal interface adapter circuit interfaces, for example, a wireless communications headset with any type of communications system, including those that require push-to-talk (PTT) signaling. The interface adapter is comprised of several main components, including an RF signaling receiver, a microcontroller and associated circuitry for decoding and processing the received signals, and programmable impedance matching and line interfacing circuitry for interfacing a wireless communications headset system base to a communications system. A signaling transmitter, which is preferably portable (e.g., handheld), is employed by the wireless headset user to send signals to the signaling receiver. In an embodiment of the invention directed specifically to push-to-talk (PTT) signaling, the wireless headset user presses a button on the signaling transmitter when they wish to speak. This sends a signal to the microcontroller which decodes the signal and recognizes the signal as being a PTT request. In response, the microcontroller generates a control signal that closes a switch to complete a voice connection between the headset system base and the communications system so that the user can communicate with the communications system. With this arrangement, the wireless headset can be interfaced to any communications system that requires PTT signaling, without modification of the headset device. In addition, the interface adapter can also be configured to respond to or deliver any other types of signals, such as dual-tone-multiple-frequency (DTMF) tones, and on/off hook signals. The present invention is also scalable, and permits multiple wireless users to operate independently in the same environment through use of a plurality of the interface adapters.

Mechanical Engineering Design Project report: Enabler control systems

NASA Technical Reports Server (NTRS)

Cullen, Christian; Delvecchio, Dave; Scarborough, Alan; Havics, Andrew A.

1992-01-01

The Controls Group was assigned the responsibility for designing the Enabler's control system. The requirement for the design was that the control system must provide a simple user interface to control the boom articulation joints, chassis articulation joints, and the wheel drive. The system required controlling hydraulic motors on the Enabler by implementing 8-bit microprocessor boards. In addition, feedback to evaluate positions and velocities must be interfaced to provide the operator with confirmation as well as control.

Evaluation of Different Speech and Touch Interfaces to In-Vehicle Music Retrieval Systems

PubMed Central

Garay-Vega, L.; Pradhan, A. K.; Weinberg, G.; Schmidt-Nielsen, B.; Harsham, B.; Shen, Y.; Divekar, G.; Romoser, M.; Knodler, M.; Fisher, D. L.

2010-01-01

In-vehicle music retrieval systems are becoming more and more popular. Previous studies have shown that they pose a real hazard to drivers when the interface is a tactile one which requires multiple entries and a combination of manual control and visual feedback. Voice interfaces exist as an alternative. Such interfaces can require either multiple or single conversational turns. In this study, each of 17 participants between the ages of 18 and 30 years old was asked to use three different music-retrieval systems (one with a multiple entry touch interface, the iPod™, one with a multiple turn voice interface, interface B, and one with a single turn voice interface, interface C) while driving through a virtual world. Measures of secondary task performance, eye behavior, vehicle control, and workload were recorded. When compared with the touch interface, the voice interfaces reduced the total time drivers spent with their eyes off the forward roadway, especially in prolonged glances, as well as both the total number of glances away from the forward roadway and the perceived workload. Furthermore, when compared with driving without a secondary task, both voice interfaces did not significantly impact hazard anticipation, the frequency of long glances away from the forward roadway, or vehicle control. The multiple turn voice interface (B) significantly increased both the time it took drivers to complete the task and the workload. The implications for interface design and safety are discussed. PMID:20380920

Propulsion/flight control integration technology (PROFIT) design analysis status

NASA Technical Reports Server (NTRS)

Carlin, C. M.; Hastings, W. J.

1978-01-01

The propulsion flight control integration technology (PROFIT) program was designed to develop a flying testbed dedicated to controls research. The preliminary design, analysis, and feasibility studies conducted in support of the PROFIT program are reported. The PROFIT system was built around existing IPCS hardware. In order to achieve the desired system flexibility and capability, additional interfaces between the IPCS hardware and F-15 systems were required. The requirements for additions and modifications to the existing hardware were defined. Those interfaces involving the more significant changes were studied. The DCU memory expansion to 32K with flight qualified hardware was completed on a brassboard basis. The uplink interface breadboard and a brassboard of the central computer interface were also tested. Two preliminary designs and corresponding program plans are presented.

Towards the formal verification of the requirements and design of a processor interface unit

NASA Technical Reports Server (NTRS)

Fura, David A.; Windley, Phillip J.; Cohen, Gerald C.

1993-01-01

The formal verification of the design and partial requirements for a Processor Interface Unit (PIU) using the Higher Order Logic (HOL) theorem-proving system is described. The processor interface unit is a single-chip subsystem within a fault-tolerant embedded system under development within the Boeing Defense and Space Group. It provides the opportunity to investigate the specification and verification of a real-world subsystem within a commercially-developed fault-tolerant computer. An overview of the PIU verification effort is given. The actual HOL listing from the verification effort are documented in a companion NASA contractor report entitled 'Towards the Formal Verification of the Requirements and Design of a Processor Interface Unit - HOL Listings' including the general-purpose HOL theories and definitions that support the PIU verification as well as tactics used in the proofs.

Space tug/shuttle interface compatibility study. Volume 1: Executive summary

NASA Technical Reports Server (NTRS)

1975-01-01

Shuttle interfaces required for space tug accommodation are primarily involved with supporting and servicing the tug during launch countdown, flight, and postlanding; deploying and retrieving the tug on orbit; and maintaining control over the tug when it is in or near the orbiter. Each of these interface areas was investigated to determine the best physical and operational method of accomplishing the required functions, with an overriding goal of establishing simple and flexible orbiter interface requirements suitable for tug, tug payloads, IUS and other cargo. It is concluded the orbiter payload accommodations and the MSFC baseline tug are generally interface compatible. Specific minor changes to tug and orbiter interfaces were identified to provide full compatibility. A system concept for supporting and deploying tug from orbiter is described.

User requirements for a patient scheduling system

NASA Technical Reports Server (NTRS)

Zimmerman, W.

1979-01-01

A rehabilitation institute's needs and wants from a scheduling system were established by (1) studying the existing scheduling system and the variables that affect patient scheduling, (2) conducting a human-factors study to establish the human interfaces that affect patients' meeting prescribed therapy schedules, and (3) developing and administering a questionnaire to the staff which pertains to the various interface problems in order to identify staff requirements to minimize scheduling problems and other factors that may limit the effectiveness of any new scheduling system.

TMS communications software. Volume 1: Computer interfaces

NASA Technical Reports Server (NTRS)

Brown, J. S.; Lenker, M. D.

1979-01-01

A prototype bus communications system, which is being used to support the Trend Monitoring System (TMS) as well as for evaluation of the bus concept is considered. Hardware and software interfaces to the MODCOMP and NOVA minicomputers are included. The system software required to drive the interfaces in each TMS computer is described. Documentation of other software for bus statistics monitoring and for transferring files across the bus is also included.

Advanced Mating System Development for Space Applications

NASA Technical Reports Server (NTRS)

Lewis, James L.

2004-01-01

This slide presentation reviews the development of space flight sealing and the work required for the further development of a dynamic interface seal for the use on space mating systems to support a fully androgynous mating interface. This effort has resulted in the advocacy of developing a standard multipurpose interface for use with all modern modular space architecture. This fully androgynous design means a seal-on-seal (SOS) system.

Development and performance of power processor system for 2-gigahertz, 200-watt amplifier for communications technology satellite

NASA Technical Reports Server (NTRS)

Siegert, C. E.; Gourash, F.; Vasicek, R. W.

1977-01-01

The electrical and environmental requirements for a power processor system (PPS) designed to supply the appropriate voltages and currents to a 200-watt traveling wave tube (TWT) for a communication technology satellite is described. A block diagram of the PPS, the interface requirements between the PPS and spacecraft, the interface requirements between the PPS and 200-watt TWT, and the environmental requirements of the PPS are presented. Also included are discussions of protection circuits, interlocking sequences, and transient requirements. Predictions of the flight performance, based on ground test data, are provided.

HAL/S-FC compiler system functional specification

NASA Technical Reports Server (NTRS)

1974-01-01

The functional requirements to be met by the HAL/S-FC compiler, and the hardware and software compatibilities between the compiler system and the environment in which it operates are defined. Associated runtime facilities and the interface with the Software Development Laboratory are specified. The construction of the HAL/S-FC system as functionally separate units and the interfaces between those units is described. An overview of the system's capabilities is presented and the hardware/operating system requirements are specified. The computer-dependent aspects of the HAL/S-FC are also specified. Compiler directives are included.

Information for the user in design of intelligent systems

NASA Technical Reports Server (NTRS)

Malin, Jane T.; Schreckenghost, Debra L.

1993-01-01

Recommendations are made for improving intelligent system reliability and usability based on the use of information requirements in system development. Information requirements define the task-relevant messages exchanged between the intelligent system and the user by means of the user interface medium. Thus, these requirements affect the design of both the intelligent system and its user interface. Many difficulties that users have in interacting with intelligent systems are caused by information problems. These information problems result from the following: (1) not providing the right information to support domain tasks; and (2) not recognizing that using an intelligent system introduces new user supervisory tasks that require new types of information. These problems are especially prevalent in intelligent systems used for real-time space operations, where data problems and unexpected situations are common. Information problems can be solved by deriving information requirements from a description of user tasks. Using information requirements embeds human-computer interaction design into intelligent system prototyping, resulting in intelligent systems that are more robust and easier to use.

Interface Anywhere: Development of a Voice and Gesture System for Spaceflight Operations

NASA Technical Reports Server (NTRS)

Thompson, Shelby; Haddock, Maxwell; Overland, David

2013-01-01

The Interface Anywhere Project was funded through Innovation Charge Account (ICA) at NASA JSC in the Fall of 2012. The project was collaboration between human factors and engineering to explore the possibility of designing an interface to control basic habitat operations through gesture and voice control; (a) Current interfaces require the users to be physically near an input device in order to interact with the system; and (b) By using voice and gesture commands, the user is able to interact with the system anywhere they want within the work environment.

Human machine interface display design document.

DOT National Transportation Integrated Search

2008-01-01

The purpose of this document is to describe the design for the human machine interface : (HMI) display for the Next Generation 9-1-1 (NG9-1-1) System (or system of systems) : based on the initial Tier 1 requirements identified for the NG9-1-1 S...

The Evolvable Advanced Multi-Mission Operations System (AMMOS): Making Systems Interoperable

NASA Technical Reports Server (NTRS)

Ko, Adans Y.; Maldague, Pierre F.; Bui, Tung; Lam, Doris T.; McKinney, John C.

2010-01-01

The Advanced Multi-Mission Operations System (AMMOS) provides a common Mission Operation System (MOS) infrastructure to NASA deep space missions. The evolution of AMMOS has been driven by two factors: increasingly challenging requirements from space missions, and the emergence of new IT technology. The work described in this paper focuses on three key tasks related to IT technology requirements: first, to eliminate duplicate functionality; second, to promote the use of loosely coupled application programming interfaces, text based file interfaces, web-based frameworks and integrated Graphical User Interfaces (GUI) to connect users, data, and core functionality; and third, to build, develop, and deploy AMMOS services that are reusable, agile, adaptive to project MOS configurations, and responsive to industrially endorsed information technology standards.

Orbiter CIU/IUS communications hardware evaluation

NASA Technical Reports Server (NTRS)

Huth, G. K.

1979-01-01

The DOD and NASA inertial upper stage communication system design, hardware specifications and interfaces were analyzed to determine their compatibility with the Orbiter payload communications equipment (Payload Interrogator, Payload Signal Processors, Communications Interface Unit, and the Orbiter operational communications equipment (the S-Band and Ku-band systems). Topics covered include (1) IUS/shuttle Orbiter communications interface definition; (2) Orbiter avionics equipment serving the IUS; (3) IUS communication equipment; (4) IUS/shuttle Orbiter RF links; (5) STDN/TDRS S-band related activities; and (6) communication interface unit/Orbiter interface issues. A test requirement plan overview is included.

Metis Hub: The Development of an Intuitive Project Planning System

DOE Office of Scientific and Technical Information (OSTI.GOV)

McConnell, Rachael M.; Lawrence Livermore National Lab.

2015-08-26

The goal is to develop an intuitive, dynamic, and consistent interface for the Metis Planning System by combining user requirements and human engineering concepts. The system is largely based upon existing systems so some tools already have working models that we can follow. However, the web-based interface is completely new.

Space Segment (SS) and the Navigation User Segment (US) Interface Control Document (ICD)

DOT National Transportation Integrated Search

1993-10-10

This Interface Control Document (ICD) defines the requirements related to the interface between the Space Segment (SS) of the Global Positioning System (GPS) and the Navigation Users Segment of the GPS. 2880k, 154p.

Designing the Instructional Interface.

ERIC Educational Resources Information Center

Lohr, L. L.

2000-01-01

Designing the instructional interface is a challenging endeavor requiring knowledge and skills in instructional and visual design, psychology, human-factors, ergonomic research, computer science, and editorial design. This paper describes the instructional interface, the challenges of its development, and an instructional systems approach to its…

DSMS Operations Concept

NASA Technical Reports Server (NTRS)

Spradlin, G.

2000-01-01

The concept provides an overview of operational roles and responsibilities in a service system environment. It describes changed and new interfaces between the customers and the service system, and variations on these interfaces as a function of the level of support required by the customer.

Advanced information processing system: Local system services

NASA Technical Reports Server (NTRS)

Burkhardt, Laura; Alger, Linda; Whittredge, Roy; Stasiowski, Peter

1989-01-01

The Advanced Information Processing System (AIPS) is a multi-computer architecture composed of hardware and software building blocks that can be configured to meet a broad range of application requirements. The hardware building blocks are fault-tolerant, general-purpose computers, fault-and damage-tolerant networks (both computer and input/output), and interfaces between the networks and the computers. The software building blocks are the major software functions: local system services, input/output, system services, inter-computer system services, and the system manager. The foundation of the local system services is an operating system with the functions required for a traditional real-time multi-tasking computer, such as task scheduling, inter-task communication, memory management, interrupt handling, and time maintenance. Resting on this foundation are the redundancy management functions necessary in a redundant computer and the status reporting functions required for an operator interface. The functional requirements, functional design and detailed specifications for all the local system services are documented.

Concept Design of the Payload Handling Manipulator System. [space shuttle orbiters

NASA Technical Reports Server (NTRS)

1975-01-01

The design, requirements, and interface definition of a remote manipulator system developed to handle orbiter payloads are presented. End effector design, control system concepts, and man-machine engineering are considered along with crew station requirements and closed circuit television system performance requirements.

Computer-Based Tools for Evaluating Graphical User Interfaces

NASA Technical Reports Server (NTRS)

Moore, Loretta A.

1997-01-01

The user interface is the component of a software system that connects two very complex system: humans and computers. Each of these two systems impose certain requirements on the final product. The user is the judge of the usability and utility of the system; the computer software and hardware are the tools with which the interface is constructed. Mistakes are sometimes made in designing and developing user interfaces because the designers and developers have limited knowledge about human performance (e.g., problem solving, decision making, planning, and reasoning). Even those trained in user interface design make mistakes because they are unable to address all of the known requirements and constraints on design. Evaluation of the user inter-face is therefore a critical phase of the user interface development process. Evaluation should not be considered the final phase of design; but it should be part of an iterative design cycle with the output of evaluation being feed back into design. The goal of this research was to develop a set of computer-based tools for objectively evaluating graphical user interfaces. The research was organized into three phases. The first phase resulted in the development of an embedded evaluation tool which evaluates the usability of a graphical user interface based on a user's performance. An expert system to assist in the design and evaluation of user interfaces based upon rules and guidelines was developed during the second phase. During the final phase of the research an automatic layout tool to be used in the initial design of graphical inter- faces was developed. The research was coordinated with NASA Marshall Space Flight Center's Mission Operations Laboratory's efforts in developing onboard payload display specifications for the Space Station.

IUS/TUG orbital operations and mission support study. Volume 4: Project planning data

NASA Technical Reports Server (NTRS)

1975-01-01

Planning data are presented for the development phases of interim upper stage (IUS) and tug systems. Major project planning requirements, major event schedules, milestones, system development and operations process networks, and relevant support research and technology requirements are included. Topics discussed include: IUS flight software; tug flight software; IUS/tug ground control center facilities, personnel, data systems, software, and equipment; IUS mission events; tug mission events; tug/spacecraft rendezvous and docking; tug/orbiter operations interface, and IUS/orbiter operations interface.

Towards the formal specification of the requirements and design of a processor interface unit: HOL listings

NASA Technical Reports Server (NTRS)

Fura, David A.; Windley, Phillip J.; Cohen, Gerald C.

1993-01-01

This technical report contains the HOL listings of the specification of the design and major portions of the requirements for a commercially developed processor interface unit (or PIU). The PIU is an interface chip performing memory interface, bus interface, and additional support services for a commercial microprocessor within a fault-tolerant computer system. This system, the Fault-Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance-free operation, or both. This report contains the actual HOL listings of the PIU specification as it currently exists. Section two of this report contains general-purpose HOL theories that support the PIU specification. These theories include definitions for the hardware components used in the PIU, our implementation of bit words, and our implementation of temporal logic. Section three contains the HOL listings for the PIU design specification. Aside from the PIU internal bus (I-Bus), this specification is complete. Section four contains the HOL listings for a major portion of the PIU requirements specification. Specifically, it contains most of the definition for the PIU behavior associated with memory accesses initiated by the local processor.

MarFS-Requirements-Design-Configuration-Admin

DOE Office of Scientific and Technical Information (OSTI.GOV)

Kettering, Brett Michael; Grider, Gary Alan

This document will be organized into sections that are defined by the requirements for a file system that presents a near-POSIX (Portable Operating System Interface) interface to the user, but whose data is stored in whatever form is most efficient for the type of data being stored. After defining the requirement the design for meeting the requirement will be explained. Finally there will be sections on configuring and administering this file system. More and more, data dominates the computing world. There is a “sea” of data out there in many different formats that needs to be managed and used. “Mar”more » means “sea” in Spanish. Thus, this product is dubbed MarFS, a file system for a sea of data.« less

19 CFR 128.23 - Entry requirements.

Code of Federal Regulations, 2010 CFR

2010-04-01

... utilizing the procedures in this part shall comply with the requirements of the Customs Automated Commercial System (ACS). These requirements include those under the Automated Manifest System (AMS), Cargo Selectivity, Statement Processing, the Automated Broker Interface System (ABI), and enhancements of ACS. (2...

3D hybrid electrode structure as implantable interface for a vestibular neural prosthesis in humans.

PubMed

Hoffmann, Klaus-P; Poppendieck, Wigand; Tätzner, Simon; DiGiovanna, Jack; Kos, Maria Izabel; Guinand, Nils; Guyot, Jean-P; Micera, Silvestro

2011-01-01

Implantable interfaces are essential components of vestibular neural prostheses. They interface the biological system with electrical stimulation that is used to restore transfer of vestibular information. Regarding the anatomical situation special 3D structures are required. In this paper, the design and the manufacturing process of a novel 3D hybrid microelectrode structure as interface to the human vestibular system are described. Photolithography techniques, assembling technology and rapid prototyping are used for manufacturing.

Neural Interfaces for Intracortical Recording: Requirements, Fabrication Methods, and Characteristics

PubMed Central

Szostak, Katarzyna M.; Grand, Laszlo; Constandinou, Timothy G.

2017-01-01

Implantable neural interfaces for central nervous system research have been designed with wire, polymer, or micromachining technologies over the past 70 years. Research on biocompatible materials, ideal probe shapes, and insertion methods has resulted in building more and more capable neural interfaces. Although the trend is promising, the long-term reliability of such devices has not yet met the required criteria for chronic human application. The performance of neural interfaces in chronic settings often degrades due to foreign body response to the implant that is initiated by the surgical procedure, and related to the probe structure, and material properties used in fabricating the neural interface. In this review, we identify the key requirements for neural interfaces for intracortical recording, describe the three different types of probes—microwire, micromachined, and polymer-based probes; their materials, fabrication methods, and discuss their characteristics and related challenges. PMID:29270103

Neural Interfaces for Intracortical Recording: Requirements, Fabrication Methods, and Characteristics.

PubMed

Szostak, Katarzyna M; Grand, Laszlo; Constandinou, Timothy G

2017-01-01

Implantable neural interfaces for central nervous system research have been designed with wire, polymer, or micromachining technologies over the past 70 years. Research on biocompatible materials, ideal probe shapes, and insertion methods has resulted in building more and more capable neural interfaces. Although the trend is promising, the long-term reliability of such devices has not yet met the required criteria for chronic human application. The performance of neural interfaces in chronic settings often degrades due to foreign body response to the implant that is initiated by the surgical procedure, and related to the probe structure, and material properties used in fabricating the neural interface. In this review, we identify the key requirements for neural interfaces for intracortical recording, describe the three different types of probes-microwire, micromachined, and polymer-based probes; their materials, fabrication methods, and discuss their characteristics and related challenges.

The Last Millimeter: Interfacing the New Public Radio Satellite System. Info. Packets No. 14.

ERIC Educational Resources Information Center

Pizzi, Skip

Public radio is about to achieve a new technological level as the new Public Radio Satellite System (PRSS) is deployed. The network will dramatically improve the capacity and quality of its interconnection system, but proper interfacing at member stations will be required to realize the full benefits of the new system. The new system uses digital…

Transforming Collaborative Process Models into Interface Process Models by Applying an MDA Approach

NASA Astrophysics Data System (ADS)

Lazarte, Ivanna M.; Chiotti, Omar; Villarreal, Pablo D.

Collaborative business models among enterprises require defining collaborative business processes. Enterprises implement B2B collaborations to execute these processes. In B2B collaborations the integration and interoperability of processes and systems of the enterprises are required to support the execution of collaborative processes. From a collaborative process model, which describes the global view of the enterprise interactions, each enterprise must define the interface process that represents the role it performs in the collaborative process in order to implement the process in a Business Process Management System. Hence, in this work we propose a method for the automatic generation of the interface process model of each enterprise from a collaborative process model. This method is based on a Model-Driven Architecture to transform collaborative process models into interface process models. By applying this method, interface processes are guaranteed to be interoperable and defined according to a collaborative process.

A haptic interface for virtual simulation of endoscopic surgery.

PubMed

Rosenberg, L B; Stredney, D

1996-01-01

Virtual reality can be described as a convincingly realistic and naturally interactive simulation in which the user is given a first person illusion of being immersed within a computer generated environment While virtual reality systems offer great potential to reduce the cost and increase the quality of medical training, many technical challenges must be overcome before such simulation platforms offer effective alternatives to more traditional training means. A primary challenge in developing effective virtual reality systems is designing the human interface hardware which allows rich sensory information to be presented to users in natural ways. When simulating a given manual procedure, task specific human interface requirements dictate task specific human interface hardware. The following paper explores the design of human interface hardware that satisfies the task specific requirements of virtual reality simulation of Endoscopic surgical procedures. Design parameters were derived through direct cadaver studies and interviews with surgeons. Final hardware design is presented.

CATO--A General User Interface for CAS

ERIC Educational Resources Information Center

Janetzko, Hans-Dieter

2015-01-01

CATO is a new user interface, developed by the author as a response to the significant difficulties faced by scientists, engineers, and students in their usage of computer algebra (CA) systems. Their tendency to use CA systems only occasionally means that they are unfamiliar with requisite grammar and syntax these systems require. The author…

Aircraft Alerting Systems Standardization Study. Phase IV. Accident Implications on Systems Design.

DTIC Science & Technology

1982-06-01

computing and processing to assimilate and process status informa- 5 tion using...provided with capabilities in computing and processing , sensing, interfacing, and controlling and displaying. 17 o Computing and Processing - Algorithms...alerting system to perform a flight status monitor function would require additional sensinq, computing and processing , interfacing, and controlling

Improved Orbiter Waste Collection System Study, Appendix D

NASA Technical Reports Server (NTRS)

1984-01-01

Basic requirements for a space shuttle orbiter waste collection system are established. They are intended to be an aid in the development and procurement of a representative flight test article. Orbiter interface requirements, performance requirements, flight crew operational requirements, flight environmental requirements, and ground operational and environmental requirements are considered.

ATM Technology Demonstration-1 Phase II Boeing Configurable Graphical Display (CGD) Software Design Description

NASA Technical Reports Server (NTRS)

Wilber, George F.

2017-01-01

This Software Description Document (SDD) captures the design for developing the Flight Interval Management (FIM) system Configurable Graphics Display (CGD) software. Specifically this SDD describes aspects of the Boeing CGD software and the surrounding context and interfaces. It does not describe the Honeywell components of the CGD system. The SDD provides the system overview, architectural design, and detailed design with all the necessary information to implement the Boeing components of the CGD software and integrate them into the CGD subsystem within the larger FIM system. Overall system and CGD system-level requirements are derived from the CGD SRS (in turn derived from the Boeing System Requirements Design Document (SRDD)). Display and look-and-feel requirements are derived from Human Machine Interface (HMI) design documents and working group recommendations. This Boeing CGD SDD is required to support the upcoming Critical Design Review (CDR).

The Large Synoptic Survey Telescope OCS and TCS models

NASA Astrophysics Data System (ADS)

Schumacher, German; Delgado, Francisco

2010-07-01

The Large Synoptic Survey Telescope (LSST) is a project envisioned as a system of systems with demanding science, technical, and operational requirements, that must perform as a fully integrated unit. The design and implementation of such a system poses big engineering challenges when performing requirements analysis, detailed interface definitions, operational modes and control strategy studies. The OMG System Modeling Language (SysML) has been selected as the framework for the systems engineering analysis and documentation for the LSST. Models for the overall system architecture and different observatory subsystems have been built describing requirements, structure, interfaces and behavior. In this paper we show the models for the Observatory Control System (OCS) and the Telescope Control System (TCS), and how this methodology has helped in the clarification of the design and requirements. In one common language, the relationships of the OCS, TCS, Camera and Data management subsystems are captured with models of the structure, behavior, requirements and the traceability between them.

Viscosity and viscoelasticity of two-phase systems having diffuse interfaces

NASA Technical Reports Server (NTRS)

Hopper, R. W.

1976-01-01

The equilibrium stability criterion for diffuse interfaces in a two-component solution with a miscibility gap requires that the interdiffusion flux vanish. If the system is continuously deformed, convective fluxes disrupt the equilibrium in the interface regions and induce a counter diffusive flux, which is dissipative and contributes to the apparent viscosity of the mixture. Chemical free energy is recoverably stored, causing viscoelastic phenomena. Both effects are significant.

Interfacing the PACS and the HIS: results of a 5-year implementation.

PubMed

Kinsey, T V; Horton, M C; Lewis, T E

2000-01-01

An interface was created between the Department of Defense's hospital information system (HIS) and its two picture archiving and communication system (PACS)-based radiology information systems (RISs). The HIS is called the Composite Healthcare Computer System (CHCS), and the RISs are called the Medical Diagnostic Imaging System (MDIS) and the Digital Imaging Network (DIN)-PACS. Extensive mapping between dissimilar data protocols was required to translate data from the HIS into both RISs. The CHCS uses a Health Level 7 (HL7) protocol, whereas the MDIS uses the American College of Radiology-National Electrical Manufacturers Association 2.0 protocol and the DIN-PACS uses the Digital Imaging and Communications in Medicine (DICOM) 3.0 protocol. An interface engine was required to change some data formats, as well as to address some nonstandard HL7 data being output from the CHCS. In addition, there are differences in terminology between fields and segments in all three protocols. This interface is in use at 20 military facilities throughout the world. The interface reduces the amount of manual entry into more than one automated system to the smallest level possible. Data mapping during installation saved time, improved productivity, and increased user acceptance during PACS implementation. It also resulted in more standardized database entries in both the HIS (CHCS) and the RIS (PACS).

Design for interaction between humans and intelligent systems during real-time fault management

NASA Technical Reports Server (NTRS)

Malin, Jane T.; Schreckenghost, Debra L.; Thronesbery, Carroll G.

1992-01-01

Initial results are reported to provide guidance and assistance for designers of intelligent systems and their human interfaces. The objective is to achieve more effective human-computer interaction (HCI) for real time fault management support systems. Studies of the development of intelligent fault management systems within NASA have resulted in a new perspective of the user. If the user is viewed as one of the subsystems in a heterogeneous, distributed system, system design becomes the design of a flexible architecture for accomplishing system tasks with both human and computer agents. HCI requirements and design should be distinguished from user interface (displays and controls) requirements and design. Effective HCI design for multi-agent systems requires explicit identification of activities and information that support coordination and communication between agents. The effects are characterized of HCI design on overall system design and approaches are identified to addressing HCI requirements in system design. The results include definition of (1) guidance based on information level requirements analysis of HCI, (2) high level requirements for a design methodology that integrates the HCI perspective into system design, and (3) requirements for embedding HCI design tools into intelligent system development environments.

Guidelines for mission integration, a summary report

NASA Technical Reports Server (NTRS)

1979-01-01

Guidelines are presented for instrument/experiment developers concerning hardware design, flight verification, and operations and mission implementation requirements. Interface requirements between the STS and instruments/experiments are defined. Interface constraints and design guidelines are presented along with integrated payload requirements for Spacelab Missions 1, 2, and 3. Interim data are suggested for use during hardware development until more detailed information is developed when a complete mission and an integrated payload system are defined. Safety requirements, flight verification requirements, and operations procedures are defined.

A database for TMT interface control documents

NASA Astrophysics Data System (ADS)

Gillies, Kim; Roberts, Scott; Brighton, Allan; Rogers, John

2016-08-01

The TMT Software System consists of software components that interact with one another through a software infrastructure called TMT Common Software (CSW). CSW consists of software services and library code that is used by developers to create the subsystems and components that participate in the software system. CSW also defines the types of components that can be constructed and their roles. The use of common component types and shared middleware services allows standardized software interfaces for the components. A software system called the TMT Interface Database System was constructed to support the documentation of the interfaces for components based on CSW. The programmer describes a subsystem and each of its components using JSON-style text files. A command interface file describes each command a component can receive and any commands a component sends. The event interface files describe status, alarms, and events a component publishes and status and events subscribed to by a component. A web application was created to provide a user interface for the required features. Files are ingested into the software system's database. The user interface allows browsing subsystem interfaces, publishing versions of subsystem interfaces, and constructing and publishing interface control documents that consist of the intersection of two subsystem interfaces. All published subsystem interfaces and interface control documents are versioned for configuration control and follow the standard TMT change control processes. Subsystem interfaces and interface control documents can be visualized in the browser or exported as PDF files.

Preliminary Candidate Advanced Avionics System (PCAAS). [reduction in single pilot workload during instrument flight rules flight

NASA Technical Reports Server (NTRS)

Teper, G. L.; Hon, R. H.; Smyth, R. K.

1977-01-01

Specifications which define the system functional requirements, the subsystem and interface needs, and other requirements such as maintainability, modularity, and reliability are summarized. A design definition of all required avionics functions and a system risk analysis are presented.

The Galley Parallel File System

NASA Technical Reports Server (NTRS)

Nieuwejaar, Nils; Kotz, David

1996-01-01

Most current multiprocessor file systems are designed to use multiple disks in parallel, using the high aggregate bandwidth to meet the growing I/0 requirements of parallel scientific applications. Many multiprocessor file systems provide applications with a conventional Unix-like interface, allowing the application to access multiple disks transparently. This interface conceals the parallelism within the file system, increasing the ease of programmability, but making it difficult or impossible for sophisticated programmers and libraries to use knowledge about their I/O needs to exploit that parallelism. In addition to providing an insufficient interface, most current multiprocessor file systems are optimized for a different workload than they are being asked to support. We introduce Galley, a new parallel file system that is intended to efficiently support realistic scientific multiprocessor workloads. We discuss Galley's file structure and application interface, as well as the performance advantages offered by that interface.

Quantitative method of medication system interface evaluation.

PubMed

Pingenot, Alleene Anne; Shanteau, James; Pingenot, James D F

2007-01-01

The objective of this study was to develop a quantitative method of evaluating the user interface for medication system software. A detailed task analysis provided a description of user goals and essential activity. A structural fault analysis was used to develop a detailed description of the system interface. Nurses experienced with use of the system under evaluation provided estimates of failure rates for each point in this simplified fault tree. Means of estimated failure rates provided quantitative data for fault analysis. Authors note that, although failures of steps in the program were frequent, participants reported numerous methods of working around these failures so that overall system failure was rare. However, frequent process failure can affect the time required for processing medications, making a system inefficient. This method of interface analysis, called Software Efficiency Evaluation and Fault Identification Method, provides quantitative information with which prototypes can be compared and problems within an interface identified.

Computer interfaces for the visually impaired

NASA Technical Reports Server (NTRS)

Higgins, Gerry

1991-01-01

Information access via computer terminals extends to blind and low vision persons employed in many technical and nontechnical disciplines. Two aspects are detailed of providing computer technology for persons with a vision related handicap. First, research into the most effective means of integrating existing adaptive technologies into information systems was made. This was conducted to integrate off the shelf products with adaptive equipment for cohesive integrated information processing systems. Details are included that describe the type of functionality required in software to facilitate its incorporation into a speech and/or braille system. The second aspect is research into providing audible and tactile interfaces to graphics based interfaces. Parameters are included for the design and development of the Mercator Project. The project will develop a prototype system for audible access to graphics based interfaces. The system is being built within the public domain architecture of X windows to show that it is possible to provide access to text based applications within a graphical environment. This information will be valuable to suppliers to ADP equipment since new legislation requires manufacturers to provide electronic access to the visually impaired.

NASA Docking System (NDS) Users Guide: International Space Station Program. Type 4

NASA Technical Reports Server (NTRS)

Tabakman, Alexander

2010-01-01

The NASA Docking System (NDS) Users Guide provides an overview of the basic information needed to integrate the NDS onto a Host Vehicle (HV). This Users Guide is intended to provide a vehicle developer with a fundamental understanding of the NDS technical and operations information to support their program and engineering integration planning. The Users Guide identifies the NDS Specification, Interface Definition or Requirement Documents that contain the complete technical details and requirements that a vehicle developer must use to design, develop and verify their systems will interface with NDS. This Guide is an initial reference and must not be used as a design document. In the event of conflict between this Users Guide and other applicable interface definition or requirements documents; the applicable document will take precedence. This Users Guide is organized in three main sections. Chapter 1 provides an overview of the NDS and CDA hardware and the operations concepts for the NDS. Chapter 2 provides information for Host Vehicle Program integration with the NDS Project Office. Chapter 2 describes the NDS Project organization, integration and verification processes, user responsibilities, and specification and interface requirement documents. Chapter 3 provides a summary of basic technical information for the NDS design. Chapter 3 includes NDS hardware component descriptions, physical size and weight characteristics, and summary of the capabilities and constraints for the various NDS sub-systems.

Common Database Interface for Heterogeneous Software Engineering Tools.

DTIC Science & Technology

1987-12-01

SUB-GROUP Database Management Systems ;Programming(Comuters); 1e 05 Computer Files;Information Transfer;Interfaces; 19. ABSTRACT (Continue on reverse...Air Force Institute of Technology Air University In Partial Fulfillment of the Requirements for the Degree of Master of Science in Information Systems ...Literature ..... 8 System 690 Configuration ......... 8 Database Functionis ............ 14 Software Engineering Environments ... 14 Data Manager

Technical Requirements Analysis and Control Systems (TRACS) Initial Operating Capability (IOC) documentation

NASA Technical Reports Server (NTRS)

Hammond, Dana P.

1991-01-01

The Technical Requirements Analysis and Control Systems (TRACS) software package is described. TRACS offers supplemental tools for the analysis, control, and interchange of project requirements. This package provides the fundamental capability to analyze and control requirements, serves a focal point for project requirements, and integrates a system that supports efficient and consistent operations. TRACS uses relational data base technology (ORACLE) in a stand alone or in a distributed environment that can be used to coordinate the activities required to support a project through its entire life cycle. TRACS uses a set of keyword and mouse driven screens (HyperCard) which imposes adherence through a controlled user interface. The user interface provides an interactive capability to interrogate the data base and to display or print project requirement information. TRACS has a limited report capability, but can be extended with PostScript conventions.

Task-Oriented, Naturally Elicited Speech (TONE) Database for the Force Requirements Expert System, Hawaii (FRESH)

DTIC Science & Technology

1988-09-01

Group Subgroup Command and control; Computational linguistics; expert system voice recognition; man- machine interface; U.S. Government 19 Abstract...simulates the characteristics of FRESH on a smaller scale. This study assisted NOSC in developing a voice-recognition, man- machine interface that could...scale. This study assisted NOSC in developing a voice-recogni- tion, man- machine interface that could be used with TONE and upgraded at a later date

Natural gesture interfaces

NASA Astrophysics Data System (ADS)

Starodubtsev, Illya

2017-09-01

The paper describes the implementation of the system of interaction with virtual objects based on gestures. The paper describes the common problems of interaction with virtual objects, specific requirements for the interfaces for virtual and augmented reality.

Crew interface specifications preparation for in-flight maintenance and stowage functions

NASA Technical Reports Server (NTRS)

Parker, F. W.; Carlton, B. E.

1972-01-01

The findings and data products developed during the Phase 2 crew interface specification study are presented. Five new NASA general specifications were prepared: operations location coding system for crew interfaces; loose equipment and stowage management requirements; loose equipment and stowage data base information requirements; spacecraft loose equipment stowage drawing requirements; and inflight stowage management data requirements. Additional data was developed defining inflight maintenance processes and related data concepts for inflight troubleshooting, remove/repair/replace and scheduled maintenance activities. The process of maintenance task and equipment definition during spacecraft design and development was also defined and related data concepts were identified for futher development into formal NASA specifications during future follow-on study phases of the contract.

Enabling Exploration Through Docking Standards

NASA Technical Reports Server (NTRS)

Hatfield, Caris A.

2012-01-01

Human exploration missions beyond low earth orbit will likely require international cooperation in order to leverage limited resources. International standards can help enable cooperative missions by providing well understood, predefined interfaces allowing compatibility between unique spacecraft and systems. The International Space Station (ISS) partnership has developed a publicly available International Docking System Standard (IDSS) that provides a solution to one of these key interfaces by defining a common docking interface. The docking interface provides a way for even dissimilar spacecraft to dock for exchange of crew and cargo, as well as enabling the assembly of large space systems. This paper provides an overview of the key attributes of the IDSS, an overview of the NASA Docking System (NDS), and the plans for updating the ISS with IDSS compatible interfaces. The NDS provides a state of the art, low impact docking system that will initially be made available to commercial crew and cargo providers. The ISS will be used to demonstrate the operational utility of the IDSS interface as a foundational technology for cooperative exploration.

An expert system shell for inferring vegetation characteristics: Interface for the addition of techniques (Task H)

NASA Technical Reports Server (NTRS)

Harrison, P. Ann

1993-01-01

All the NASA VEGetation Workbench (VEG) goals except the Learning System provide the scientist with several different techniques. When VEG is run, rules assist the scientist in selecting the best of the available techniques to apply to the sample of cover type data being studied. The techniques are stored in the VEG knowledge base. The design and implementation of an interface that allows the scientist to add new techniques to VEG without assistance from the developer were completed. A new interface that enables the scientist to add techniques to VEG without assistance from the developer was designed and implemented. This interface does not require the scientist to have a thorough knowledge of Knowledge Engineering Environment (KEE) by Intellicorp or a detailed knowledge of the structure of VEG. The interface prompts the scientist to enter the required information about the new technique. It prompts the scientist to enter the required Common Lisp functions for executing the technique and the left hand side of the rule that causes the technique to be selected. A template for each function and rule and detailed instructions about the arguments of the functions, the values they should return, and the format of the rule are displayed. Checks are made to ensure that the required data were entered, the functions compiled correctly, and the rule parsed correctly before the new technique is stored. The additional techniques are stored separately from the VEG knowledge base. When the VEG knowledge base is loaded, the additional techniques are not normally loaded. The interface allows the scientist the option of adding all the previously defined new techniques before running VEG. When the techniques are added, the required units to store the additional techniques are created automatically in the correct places in the VEG knowledge base. The methods file containing the functions required by the additional techniques is loaded. New rule units are created to store the new rules. The interface that allow the scientist to select which techniques to use is updated automatically to include the new techniques. Task H was completed. The interface that allows the scientist to add techniques to VEG was implemented and comprehensively tested. The Common Lisp code for the Add Techniques system is listed in Appendix A.

Estimation of payload loads using rigid body interface accelerations. [in structural design of launch vehicle systems

NASA Technical Reports Server (NTRS)

Chen, J. C.; Garba, J. A.; Wada, B. K.

1978-01-01

In the design/analysis process of a payload structural system, the accelerations at the payload/launch vehicle interface obtained from a system analysis using a rigid payload are often used as the input forcing function to the elastic payload to obtain structural design loads. Such an analysis is at best an approximation since the elastic coupling effects are neglected. This paper develops a method wherein the launch vehicle/rigid payload interface accelerations are modified to account for the payload elasticity. The advantage of the proposed method, which is exact to the extent that the physical system can be described by a truncated set of generalized coordinates, is that the complete design/analysis process can be performed within the organization responsible for the payload design. The method requires the updating of the system normal modes to account for payload changes, but does not require a complete transient solution using the composite system model. An application to a real complex structure, the Viking Spacecraft System, is given.

Space Shuttle Solid Rocket Booster decelerator subsystem - Air drop test vehicle/B-52 design

NASA Technical Reports Server (NTRS)

Runkle, R. E.; Drobnik, R. F.

1979-01-01

The air drop development test program for the Space Shuttle Solid Rocket Booster Recovery System required the design of a large drop test vehicle that would meet all the stringent requirements placed on it by structural loads, safety considerations, flight recovery system interfaces, and sequence. The drop test vehicle had to have the capability to test the drogue and the three main parachutes both separately and in the total flight deployment sequence and still be low-cost to fit in a low-budget development program. The design to test large ribbon parachutes to loads of 300,000 pounds required the detailed investigation and integration of several parameters such as carrier aircraft mechanical interface, drop test vehicle ground transportability, impact point ground penetration, salvageability, drop test vehicle intelligence, flight design hardware interfaces, and packaging fidelity.

US Search and Rescue Mission Control Center functions

NASA Technical Reports Server (NTRS)

1977-01-01

A satellite aided Search and Rescue (SAR) Mission concept consisting of a local coverage bent pipe system, and a global coverage system is described. The SAR instrument is to consist of a Canadian repeater and a French processor for which Canada and France, respectively are to evaluate health and trends. Performance evaluations of each system were provided. The United States and Canada will each have a Search and Rescue Mission Control Center (MCC) and their functions were also examined. A summary of the interface requirements necessary to perform each function was included as well as the information requirements between the USMCC and each of its interfaces. Physical requirements such as location, manning etc. of the USMCC were discussed.

Distributed user interfaces for clinical ubiquitous computing applications.

PubMed

Bång, Magnus; Larsson, Anders; Berglund, Erik; Eriksson, Henrik

2005-08-01

Ubiquitous computing with multiple interaction devices requires new interface models that support user-specific modifications to applications and facilitate the fast development of active workspaces. We have developed NOSTOS, a computer-augmented work environment for clinical personnel to explore new user interface paradigms for ubiquitous computing. NOSTOS uses several devices such as digital pens, an active desk, and walk-up displays that allow the system to track documents and activities in the workplace. We present the distributed user interface (DUI) model that allows standalone applications to distribute their user interface components to several devices dynamically at run-time. This mechanism permit clinicians to develop their own user interfaces and forms to clinical information systems to match their specific needs. We discuss the underlying technical concepts of DUIs and show how service discovery, component distribution, events and layout management are dealt with in the NOSTOS system. Our results suggest that DUIs--and similar network-based user interfaces--will be a prerequisite of future mobile user interfaces and essential to develop clinical multi-device environments.

Sharing data between mobile devices, connected vehicles, and infrastructure task 3: system requirements specifications (SyRS) final.

DOT National Transportation Integrated Search

2016-07-14

This report describes the system requirements specifications (SyRS) for the use of mobile devices in a connected vehicle environment. Specifically, it defines the different types of requirements (functional, interface, performance, security, data, an...

Earth Observatory Satellite system definition study. Report 6: Space shuttle interfaces/utilization

NASA Technical Reports Server (NTRS)

1974-01-01

An analysis was conducted to determine the compatibility of the Earth Observatory Satellite (EOS) with the space shuttle. The mechanical interfaces and provisions required for a launch or retrieval of the EOS by the space shuttle are summarized. The space shuttle flight support equipment required for the operation is defined. Diagrams of the space shuttle in various configurations are provised to show the mission capability with the EOS. The subjects considered are as follows: (1) structural and mechanical interfaces, (2) spacecraft retention and deployment, (3) spacecraft retrieval, (4) electrical interfaces, (5) payload shuttle operations, (6) shuttle mode cost analysis, (7) shuttle orbit trades, and (8) safety considerations.

mREST Interface Specification

NASA Technical Reports Server (NTRS)

McCartney, Patrick; MacLean, John

2012-01-01

mREST is an implementation of the REST architecture specific to the management and sharing of data in a system of logical elements. The purpose of this document is to clearly define the mREST interface protocol. The interface protocol covers all of the interaction between mREST clients and mREST servers. System-level requirements are not specifically addressed. In an mREST system, there are typically some backend interfaces between a Logical System Element (LSE) and the associated hardware/software system. For example, a network camera LSE would have a backend interface to the camera itself. These interfaces are specific to each type of LSE and are not covered in this document. There are also frontend interfaces that may exist in certain mREST manager applications. For example, an electronic procedure execution application may have a specialized interface for configuring the procedures. This interface would be application specific and outside of this document scope. mREST is intended to be a generic protocol which can be used in a wide variety of applications. A few scenarios are discussed to provide additional clarity but, in general, application-specific implementations of mREST are not specifically addressed. In short, this document is intended to provide all of the information necessary for an application developer to create mREST interface agents. This includes both mREST clients (mREST manager applications) and mREST servers (logical system elements, or LSEs).

System Architectural Concepts: Army Battlefield Command and Control Information Utility (CCIU).

DTIC Science & Technology

1982-07-25

produce (device-type), the computers they may interface with (required- host), and the identification number of the devices (device- number). Line- printers ...interface in a network PE ( ZINK Sol. A-5 GLOSSARY Kernel A layer of the PEOS; implements the basic system primitives. LUS Local Name Space Locking A

New tracking implementation in the Deep Space Network

NASA Technical Reports Server (NTRS)

Berner, Jeff B.; Bryant, Scott H.

2001-01-01

As part of the Network Simplification Project, the tracking system of the Deep Space Network is being upgraded. This upgrade replaces the discrete logic sequential ranging system with a system that is based on commercial Digital Signal Processor boards. The new implementation allows both sequential and pseudo-noise types of ranging. The other major change is a modernization of the data formatting. Previously, there were several types of interfaces, delivering both intermediate data and processed data (called 'observables'). All of these interfaces were bit-packed blocks, which do not allow for easy expansion, and many of these interfaces required knowledge of the specific hardware implementations. The new interface supports four classes of data: raw (direct from the measuring equipment), derived (the observable data), interferometric (multiple antenna measurements), and filtered (data whose values depend on multiple measurements). All of the measurements are reported at the sky frequency or phase level, so that no knowledge of the actual hardware is required. The data is formatted into Standard Formatted Data Units, as defined by the Consultative Committee for Space Data Systems, so that expansion and cross-center usage is greatly enhanced.

Deep Space Network (DSN), Network Operations Control Center (NOCC) computer-human interfaces

NASA Technical Reports Server (NTRS)

Ellman, Alvin; Carlton, Magdi

1993-01-01

The Network Operations Control Center (NOCC) of the DSN is responsible for scheduling the resources of DSN, and monitoring all multi-mission spacecraft tracking activities in real-time. Operations performs this job with computer systems at JPL connected to over 100 computers at Goldstone, Australia and Spain. The old computer system became obsolete, and the first version of the new system was installed in 1991. Significant improvements for the computer-human interfaces became the dominant theme for the replacement project. Major issues required innovating problem solving. Among these issues were: How to present several thousand data elements on displays without overloading the operator? What is the best graphical representation of DSN end-to-end data flow? How to operate the system without memorizing mnemonics of hundreds of operator directives? Which computing environment will meet the competing performance requirements? This paper presents the technical challenges, engineering solutions, and results of the NOCC computer-human interface design.

Fighter Aircraft OBIGGS (On-Board Inert Gas Generator System) Study. Volume 2

DTIC Science & Technology

1987-06-01

UNCLASSIFIED.UNLIMITED L SAME AS RPT. 0 OTIC USERS 0 UNCLASSIFIED 22m. NAME Or RESPONSIBLE INOIVIOUAL 22b TELEPHONE NUJN lER 22c OFFICE SYMBOL IflncI.de A C...Pressure Air System 53 3.2.1.6.11.3 Fuel Tank Vent System 54 3.2.1.6.11.4 Fuel Scrubbing System 54 3.2.1.6.12 Control/ Interface Processor 55 3.2.1.6.12.1...Flowmeters 60, 3.2.1.6.13.6 Motion Transducer 61 3.2.1.7 Interface Requirements 61 3.2.1.7.1 External Interfaces 61 3.2.1.7.1.1 External Systems

Design criteria for a PC-based common user interface to remote information systems

NASA Technical Reports Server (NTRS)

Dominick, Wayne D. (Editor); Hall, Philip P.

1984-01-01

A set of design criteria are presented which will allow the implementation of an interface to multiple remote information systems on a microcomputer. The focus of the design description is on providing the user with the functionality required to retrieve, store and manipulate data residing in remote information systems through the utilization of a standardized interface system. The intent is to spare the user from learning the details of retrieval from specific systems while retaining the full capabilities of each system. The system design includes multi-level capabilities to enhance usability by a wide range of users and utilizes microcomputer graphics capabilities where applicable. A data collection subsystem for evaluation purposes is also described.

An intelligent interface for satellite operations: Your Orbit Determination Assistant (YODA)

NASA Technical Reports Server (NTRS)

Schur, Anne

1988-01-01

An intelligent interface is often characterized by the ability to adapt evaluation criteria as the environment and user goals change. Some factors that impact these adaptations are redefinition of task goals and, hence, user requirements; time criticality; and system status. To implement adaptations affected by these factors, a new set of capabilities must be incorporated into the human-computer interface design. These capabilities include: (1) dynamic update and removal of control states based on user inputs, (2) generation and removal of logical dependencies as change occurs, (3) uniform and smooth interfacing to numerous processes, databases, and expert systems, and (4) unobtrusive on-line assistance to users of concepts were applied and incorporated into a human-computer interface using artificial intelligence techniques to create a prototype expert system, Your Orbit Determination Assistant (YODA). YODA is a smart interface that supports, in real teime, orbit analysts who must determine the location of a satellite during the station acquisition phase of a mission. Also described is the integration of four knowledge sources required to support the orbit determination assistant: orbital mechanics, spacecraft specifications, characteristics of the mission support software, and orbit analyst experience. This initial effort is continuing with expansion of YODA's capabilities, including evaluation of results of the orbit determination task.

Advanced EVA system design requirements study

NASA Technical Reports Server (NTRS)

Woods, T. G.

1988-01-01

The results are presented of a study to identify specific criteria regarding space station extravehicular activity system (EVAS) hardware requirements. Key EVA design issues include maintainability, technology readiness, LSS volume vs. EVA time available, suit pressure/cabin pressure relationship and productivity effects, crew autonomy, integration of EVA as a program resource, and standardization of task interfaces. A variety of DOD EVA systems issues were taken into consideration. Recommendations include: (1) crew limitations, not hardware limitations; (2) capability to perform all of 15 generic missions; (3) 90 days on-orbit maintainability with 50 percent duty cycle as minimum; and (4) use by payload sponsors of JSC document 10615A plus a Generic Tool Kit and Specialized Tool Kit description. EVA baseline design requirements and criteria, including requirements of various subsystems, are outlined. Space station/EVA system interface requirements and EVA accommodations are discussed in the areas of atmosphere composition and pressure, communications, data management, logistics, safe haven, SS exterior and interior requirements, and SS airlock.

IUS/TUG orbital operations and mission support study. Volume 3: Space tug operations

NASA Technical Reports Server (NTRS)

1975-01-01

A study was conducted to develop space tug operational concepts and baseline operations plan, and to provide cost estimates for space tug operations. Background data and study results are presented along with a transition phase analysis (the transition from interim upper state to tug operations). A summary is given of the tug operational and interface requirements with emphasis on the on-orbit checkout requirements, external interface operational requirements, safety requirements, and system operational interface requirements. Other topics discussed include reference missions baselined for the tug and details for the mission functional flows and timelines derived for the tug mission, tug subsystems, tug on-orbit operations prior to the tug first burn, spacecraft deployment and retrieval by the tug, operations centers, mission planning, potential problem areas, and cost data.

Development of a task analysis tool to facilitate user interface design

NASA Technical Reports Server (NTRS)

Scholtz, Jean C.

1992-01-01

A good user interface is one that facilitates the user in carrying out his task. Such interfaces are difficult and costly to produce. The most important aspect in producing a good interface is the ability to communicate to the software designers what the user's task is. The Task Analysis Tool is a system for cooperative task analysis and specification of the user interface requirements. This tool is intended to serve as a guide to development of initial prototypes for user feedback.

Generic worklist handler for workflow-enabled products

NASA Astrophysics Data System (ADS)

Schmidt, Joachim; Meetz, Kirsten; Wendler, Thomas

1999-07-01

Workflow management (WfM) is an emerging field of medical information technology. It appears as a promising key technology to model, optimize and automate processes, for the sake of improved efficiency, reduced costs and improved patient care. The Application of WfM concepts requires the standardization of architectures and interfaces. A component of central interest proposed in this report is a generic work list handler: A standardized interface between a workflow enactment service and application system. Application systems with embedded work list handlers will be called 'Workflow Enabled Application Systems'. In this paper we discus functional requirements of work list handlers, as well as their integration into workflow architectures and interfaces. To lay the foundation for this specification, basic workflow terminology, the fundamentals of workflow management and - later in the paper - the available standards as defined by the Workflow Management Coalition are briefly reviewed.

CLIPS application user interface for the PC

NASA Technical Reports Server (NTRS)

Jenkins, Jim; Holbrook, Rebecca; Shewhart, Mark; Crouse, Joey; Yarost, Stuart

1991-01-01

The majority of applications that utilize expert system development programs for their knowledge representation and inferencing capability require some form of interface with the end user. This interface is more than likely an interaction through the computer screen. When building an application the user interface can prove to be the most difficult and time consuming aspect to program. Commercial products currently exist which address this issue. To keep pace C Language Integrated Production System (CLIPS) will need to find a solution for their lack of an easy to use Application User Interface (AUI). This paper represents a survey of the DoD CLIPS' user community and provides the backbone of a possible solution.

Human computer interface guide, revision A

NASA Technical Reports Server (NTRS)

1993-01-01

The Human Computer Interface Guide, SSP 30540, is a reference document for the information systems within the Space Station Freedom Program (SSFP). The Human Computer Interface Guide (HCIG) provides guidelines for the design of computer software that affects human performance, specifically, the human-computer interface. This document contains an introduction and subparagraphs on SSFP computer systems, users, and tasks; guidelines for interactions between users and the SSFP computer systems; human factors evaluation and testing of the user interface system; and example specifications. The contents of this document are intended to be consistent with the tasks and products to be prepared by NASA Work Package Centers and SSFP participants as defined in SSP 30000, Space Station Program Definition and Requirements Document. The Human Computer Interface Guide shall be implemented on all new SSFP contractual and internal activities and shall be included in any existing contracts through contract changes. This document is under the control of the Space Station Control Board, and any changes or revisions will be approved by the deputy director.

International Docking Standard (IDSS) Interface Definition Document (IDD) . E; Revision

NASA Technical Reports Server (NTRS)

Kelly, Sean M.; Cryan, Scott P.

2016-01-01

This International Docking System Standard (IDSS) Interface Definition Document (IDD) is the result of a collaboration by the International Space Station membership to establish a standard docking interface to enable on-orbit crew rescue operations and joint collaborative endeavors utilizing different spacecraft. This IDSS IDD details the physical geometric mating interface and design loads requirements. The physical geometric interface requirements must be strictly followed to ensure physical spacecraft mating compatibility. This includes both defined components and areas that are void of components. The IDD also identifies common design parameters as identified in section 3.0, e.g., docking initial conditions and vehicle mass properties. This information represents a recommended set of design values enveloping a broad set of design reference missions and conditions, which if accommodated in the docking system design, increases the probability of successful docking between different spacecraft. This IDD does not address operational procedures or off-nominal situations, nor does it dictate implementation or design features behind the mating interface. It is the responsibility of the spacecraft developer to perform all hardware verification and validation, and to perform final docking analyses to ensure the needed docking performance and to develop the final certification loads for their application. While there are many other critical requirements needed in the development of a docking system such as fault tolerance, reliability, and environments (e.g. vibration, etc.), it is not the intent of the IDSS IDD to mandate all of these requirements; these requirements must be addressed as part of the specific developer's unique program, spacecraft and mission needs. This approach allows designers the flexibility to design and build docking mechanisms to their unique program needs and requirements. The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions.The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions. The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions.

The successful implementation of a licensed data management interface between a Sunquest(®) laboratory information system and an AB SCIEX™ mass spectrometer.

PubMed

French, Deborah; Terrazas, Enrique

2013-01-01

Interfacing complex laboratory equipment to laboratory information systems (LIS) has become a more commonly encountered problem in clinical laboratories, especially for instruments that do not have an interface provided by the vendor. Liquid chromatography-tandem mass spectrometry is a great example of such complex equipment, and has become a frequent addition to clinical laboratories. As the testing volume on such instruments can be significant, manual data entry will also be considerable and the potential for concomitant transcription errors arises. Due to this potential issue, our aim was to interface an AB SCIEX™ mass spectrometer to our Sunquest(®) LIS. WE LICENSED SOFTWARE FOR THE DATA MANAGEMENT INTERFACE FROM THE UNIVERSITY OF PITTSBURGH, BUT EXTENDED THIS WORK AS FOLLOWS: The interface was designed so that it would accept a text file exported from the AB SCIEX™ × 5500 QTrap(®) mass spectrometer, pre-process the file (using newly written code) into the correct format and upload it into Sunquest(®) via file transfer protocol. The licensed software handled the majority of the interface tasks with the exception of converting the output from the Analyst(®) software to the required Sunquest(®) import format. This required writing of a "pre-processor" by one of the authors which was easily integrated with the supplied software. We successfully implemented the data management interface licensed from the University of Pittsburgh. Given the coding that was required to write the pre-processor, and alterations to the source code that were performed when debugging the software, we would suggest that before a laboratory decides to implement such an interface, it would be necessary to have a competent computer programmer available.

The development of an airborne instrumentation computer system for flight test

NASA Technical Reports Server (NTRS)

Bever, G. A.

1984-01-01

Instrumentation interfacing frequently requires the linking of intelligent systems together, as well as requiring the link itself to be intelligent. The airborne instrumentation computer system (AICS) was developed to address this requirement. Its small size, approximately 254 by 133 by 140 mm (10 by 51/4 by 51/2 in), standard bus, and modular board configuration give it the ability to solve instrumentation interfacing and computation problems without forcing a redesign of the entire unit. This system has been used on the F-15 aircraft digital electronic engine control (DEEC) and its follow on engine model derivative (EMD) project and in an OV-1C Mohawk aircraft stall speed warning system. The AICS is presently undergoing configuration for use on an F-104 pace aircraft and on the advanced fighter technology integration (AFTI) F-111 aircraft.

A Proposed Intelligent Policy-Based Interface for a Mobile eHealth Environment

NASA Astrophysics Data System (ADS)

Tavasoli, Amir; Archer, Norm

Users of mobile eHealth systems are often novices, and the learning process for them may be very time consuming. In order for systems to be attractive to potential adopters, it is important that the interface should be very convenient and easy to learn. However, the community of potential users of a mobile eHealth system may be quite varied in their requirements, so the system must be able to adapt easily to suit user preferences. One way to accomplish this is to have the interface driven by intelligent policies. These policies can be refined gradually, using inputs from potential users, through intelligent agents. This paper develops a framework for policy refinement for eHealth mobile interfaces, based on dynamic learning from user interactions.

Digital interface of electronic transformers based on embedded system

NASA Astrophysics Data System (ADS)

Shang, Qiufeng; Qi, Yincheng

2008-10-01

Benefited from digital interface of electronic transformers, information sharing and system integration in substation can be realized. An embedded system-based digital output scheme of electronic transformers is proposed. The digital interface is designed with S3C44B0X 32bit RISC microprocessor as the hardware platform. The μCLinux operation system (OS) is transplanted on ARM7 (S3C44B0X). Applying Ethernet technology as the communication mode in the substation automation system is a new trend. The network interface chip RTL8019AS is adopted. Data transmission is realized through the in-line TCP/IP protocol of uClinux embedded OS. The application result and character analysis show that the design can meet the real-time and reliability requirements of IEC60044-7/8 electronic voltage/current instrument transformer standards.

Live Virtual Constructive (LVC): Interface Control Document (ICD) for the LVC Gateway. [Flight Test 3

NASA Technical Reports Server (NTRS)

Jovic, Srba

2015-01-01

This Interface Control Document (ICD) documents and tracks the necessary information required for the Live Virtual and Constructive (LVC) systems components as well as protocols for communicating with them in order to achieve all research objectives captured by the experiment requirements. The purpose of this ICD is to clearly communicate all inputs and outputs from the subsystem components.

Semantic integration of information about orthologs and diseases: the OGO system.

PubMed

Miñarro-Gimenez, Jose Antonio; Egaña Aranguren, Mikel; Martínez Béjar, Rodrigo; Fernández-Breis, Jesualdo Tomás; Madrid, Marisa

2011-12-01

Semantic Web technologies like RDF and OWL are currently applied in life sciences to improve knowledge management by integrating disparate information. Many of the systems that perform such task, however, only offer a SPARQL query interface, which is difficult to use for life scientists. We present the OGO system, which consists of a knowledge base that integrates information of orthologous sequences and genetic diseases, providing an easy to use ontology-constrain driven query interface. Such interface allows the users to define SPARQL queries through a graphical process, therefore not requiring SPARQL expertise. Copyright © 2011 Elsevier Inc. All rights reserved.

Human-Automation Interaction Design for Adaptive Cruise Control Systems of Ground Vehicles.

PubMed

Eom, Hwisoo; Lee, Sang Hun

2015-06-12

A majority of recently developed advanced vehicles have been equipped with various automated driver assistance systems, such as adaptive cruise control (ACC) and lane keeping assistance systems. ACC systems have several operational modes, and drivers can be unaware of the mode in which they are operating. Because mode confusion is a significant human error factor that contributes to traffic accidents, it is necessary to develop user interfaces for ACC systems that can reduce mode confusion. To meet this requirement, this paper presents a new human-automation interaction design methodology in which the compatibility of the machine and interface models is determined using the proposed criteria, and if the models are incompatible, one or both of the models is/are modified to make them compatible. To investigate the effectiveness of our methodology, we designed two new interfaces by separately modifying the machine model and the interface model and then performed driver-in-the-loop experiments. The results showed that modifying the machine model provides a more compact, acceptable, effective, and safe interface than modifying the interface model.

Human-Automation Interaction Design for Adaptive Cruise Control Systems of Ground Vehicles

PubMed Central

Eom, Hwisoo; Lee, Sang Hun

2015-01-01

A majority of recently developed advanced vehicles have been equipped with various automated driver assistance systems, such as adaptive cruise control (ACC) and lane keeping assistance systems. ACC systems have several operational modes, and drivers can be unaware of the mode in which they are operating. Because mode confusion is a significant human error factor that contributes to traffic accidents, it is necessary to develop user interfaces for ACC systems that can reduce mode confusion. To meet this requirement, this paper presents a new human-automation interaction design methodology in which the compatibility of the machine and interface models is determined using the proposed criteria, and if the models are incompatible, one or both of the models is/are modified to make them compatible. To investigate the effectiveness of our methodology, we designed two new interfaces by separately modifying the machine model and the interface model and then performed driver-in-the-loop experiments. The results showed that modifying the machine model provides a more compact, acceptable, effective, and safe interface than modifying the interface model. PMID:26076406

A user-system interface agent

NASA Technical Reports Server (NTRS)

Wakim, Nagi T.; Srivastava, Sadanand; Bousaidi, Mehdi; Goh, Gin-Hua

1995-01-01

Agent-based technologies answer to several challenges posed by additional information processing requirements in today's computing environments. In particular, (1) users desire interaction with computing devices in a mode which is similar to that used between people, (2) the efficiency and successful completion of information processing tasks often require a high-level of expertise in complex and multiple domains, (3) information processing tasks often require handling of large volumes of data and, therefore, continuous and endless processing activities. The concept of an agent is an attempt to address these new challenges by introducing information processing environments in which (1) users can communicate with a system in a natural way, (2) an agent is a specialist and a self-learner and, therefore, it qualifies to be trusted to perform tasks independent of the human user, and (3) an agent is an entity that is continuously active performing tasks that are either delegated to it or self-imposed. The work described in this paper focuses on the development of an interface agent for users of a complex information processing environment (IPE). This activity is part of an on-going effort to build a model for developing agent-based information systems. Such systems will be highly applicable to environments which require a high degree of automation, such as, flight control operations and/or processing of large volumes of data in complex domains, such as the EOSDIS environment and other multidisciplinary, scientific data systems. The concept of an agent as an information processing entity is fully described with emphasis on characteristics of special interest to the User-System Interface Agent (USIA). Issues such as agent 'existence' and 'qualification' are discussed in this paper. Based on a definition of an agent and its main characteristics, we propose an architecture for the development of interface agents for users of an IPE that is agent-oriented and whose resources are likely to be distributed and heterogeneous in nature. The architecture of USIA is outlined in two main components: (1) the user interface which is concerned with issues as user dialog and interaction, user modeling, and adaptation to user profile, and (2) the system interface part which deals with identification of IPE capabilities, task understanding and feasibility assessment, and task delegation and coordination of assistant agents.

Integrating interface slicing into software engineering processes

NASA Technical Reports Server (NTRS)

Beck, Jon

1993-01-01

Interface slicing is a tool which was developed to facilitate software engineering. As previously presented, it was described in terms of its techniques and mechanisms. The integration of interface slicing into specific software engineering activities is considered by discussing a number of potential applications of interface slicing. The applications discussed specifically address the problems, issues, or concerns raised in a previous project. Because a complete interface slicer is still under development, these applications must be phrased in future tenses. Nonetheless, the interface slicing techniques which were presented can be implemented using current compiler and static analysis technology. Whether implemented as a standalone tool or as a module in an integrated development or reverse engineering environment, they require analysis no more complex than that required for current system development environments. By contrast, conventional slicing is a methodology which, while showing much promise and intuitive appeal, has yet to be fully implemented in a production language environment despite 12 years of development.

Requirements Document for Development of a Livermore Tomography Tools Interface

DOE Office of Scientific and Technical Information (OSTI.GOV)

Seetho, I. M.

In this document, we outline an exercise performed at LLNL to evaluate the user interface deficits of a LLNL-developed CT reconstruction software package, Livermore Tomography Tools (LTT). We observe that a difficult-to-use command line interface and the lack of support functions compound to generate a bottleneck in the CT reconstruction process when input parameters to key functions are not well known. Through the exercise of systems engineering best practices, we generate key performance parameters for a LTT interface refresh, and specify a combination of back-end (“test-mode” functions) and front-end (graphical user interface visualization and command scripting tools) solutions to LTT’smore » poor user interface that aim to mitigate issues and lower costs associated with CT reconstruction using LTT. Key functional and non-functional requirements and risk mitigation strategies for the solution are outlined and discussed.« less

BrainIACS: a system for web-based medical image processing

NASA Astrophysics Data System (ADS)

Kishore, Bhaskar; Bazin, Pierre-Louis; Pham, Dzung L.

2009-02-01

We describe BrainIACS, a web-based medical image processing system that permits and facilitates algorithm developers to quickly create extensible user interfaces for their algorithms. Designed to address the challenges faced by algorithm developers in providing user-friendly graphical interfaces, BrainIACS is completely implemented using freely available, open-source software. The system, which is based on a client-server architecture, utilizes an AJAX front-end written using the Google Web Toolkit (GWT) and Java Servlets running on Apache Tomcat as its back-end. To enable developers to quickly and simply create user interfaces for configuring their algorithms, the interfaces are described using XML and are parsed by our system to create the corresponding user interface elements. Most of the commonly found elements such as check boxes, drop down lists, input boxes, radio buttons, tab panels and group boxes are supported. Some elements such as the input box support input validation. Changes to the user interface such as addition and deletion of elements are performed by editing the XML file or by using the system's user interface creator. In addition to user interface generation, the system also provides its own interfaces for data transfer, previewing of input and output files, and algorithm queuing. As the system is programmed using Java (and finally Java-script after compilation of the front-end code), it is platform independent with the only requirements being that a Servlet implementation be available and that the processing algorithms can execute on the server platform.

19 CFR 143.5 - System performance requirements.

Code of Federal Regulations, 2012 CFR

2012-04-01

... 19 Customs Duties 2 2012-04-01 2012-04-01 false System performance requirements. 143.5 Section 143.5 Customs Duties U.S. CUSTOMS AND BORDER PROTECTION, DEPARTMENT OF HOMELAND SECURITY; DEPARTMENT OF... must demonstrate that his system can interface directly with the Customs computer and ensure accurate...

19 CFR 143.5 - System performance requirements.

Code of Federal Regulations, 2011 CFR

2011-04-01

... 19 Customs Duties 2 2011-04-01 2011-04-01 false System performance requirements. 143.5 Section 143.5 Customs Duties U.S. CUSTOMS AND BORDER PROTECTION, DEPARTMENT OF HOMELAND SECURITY; DEPARTMENT OF... must demonstrate that his system can interface directly with the Customs computer and ensure accurate...

19 CFR 143.5 - System performance requirements.

Code of Federal Regulations, 2014 CFR

2014-04-01

... 19 Customs Duties 2 2014-04-01 2014-04-01 false System performance requirements. 143.5 Section 143.5 Customs Duties U.S. CUSTOMS AND BORDER PROTECTION, DEPARTMENT OF HOMELAND SECURITY; DEPARTMENT OF... must demonstrate that his system can interface directly with the Customs computer and ensure accurate...

19 CFR 143.5 - System performance requirements.

Code of Federal Regulations, 2010 CFR

2010-04-01

... 19 Customs Duties 2 2010-04-01 2010-04-01 false System performance requirements. 143.5 Section 143.5 Customs Duties U.S. CUSTOMS AND BORDER PROTECTION, DEPARTMENT OF HOMELAND SECURITY; DEPARTMENT OF... must demonstrate that his system can interface directly with the Customs computer and ensure accurate...

19 CFR 143.5 - System performance requirements.

Code of Federal Regulations, 2013 CFR

2013-04-01

... 19 Customs Duties 2 2013-04-01 2013-04-01 false System performance requirements. 143.5 Section 143.5 Customs Duties U.S. CUSTOMS AND BORDER PROTECTION, DEPARTMENT OF HOMELAND SECURITY; DEPARTMENT OF... must demonstrate that his system can interface directly with the Customs computer and ensure accurate...

A Multi-Purpose Modular Electronics Integration Node for Exploration Extravehicular Activity

NASA Technical Reports Server (NTRS)

Hodgson, Edward; Papale, William; Wichowski, Robert; Rosenbush, David; Hawes, Kevin; Stankiewicz, Tom

2013-01-01

As NASA works to develop an effective integrated portable life support system design for exploration Extravehicular activity (EVA), alternatives to the current system s electrical power and control architecture are needed to support new requirements for flexibility, maintainability, reliability, and reduced mass and volume. Experience with the current Extravehicular Mobility Unit (EMU) has demonstrated that the current architecture, based in a central power supply, monitoring and control unit, with dedicated analog wiring harness connections to active components in the system has a significant impact on system packaging and seriously constrains design flexibility in adapting to component obsolescence and changing system needs over time. An alternative architecture based in the use of a digital data bus offers possible wiring harness and system power savings, but risks significant penalties in component complexity and cost. A hybrid architecture that relies on a set of electronic and power interface nodes serving functional models within the Portable Life Support System (PLSS) is proposed to minimize both packaging and component level penalties. A common interface node hardware design can further reduce penalties by reducing the nonrecurring development costs, making miniaturization more practical, maximizing opportunities for maturation and reliability growth, providing enhanced fault tolerance, and providing stable design interfaces for system components and a central control. Adaptation to varying specific module requirements can be achieved with modest changes in firmware code within the module. A preliminary design effort has developed a common set of hardware interface requirements and functional capabilities for such a node based on anticipated modules comprising an exploration PLSS, and a prototype node has been designed assembled, programmed, and tested. One instance of such a node has been adapted to support testing the swingbed carbon dioxide and humidity control element in NASA s advanced PLSS 2.0 test article. This paper will describe the common interface node design concept, results of the prototype development and test effort, and plans for use in NASA PLSS 2.0 integrated tests.

Earth Observing System/Advanced Microwave Sounding Unit-A (EOS/AMSU-A): Firmware Requirements

NASA Technical Reports Server (NTRS)

Schwantje, Robert

1995-01-01

This Firmware Requirements Document specifies the functional, performance, and interface requirements of the firmware. It also specifies the major characteristics, implementation constraints, and design goals of the firmware.

Simulation of the human-telerobot interface

NASA Technical Reports Server (NTRS)

Stuart, Mark A.; Smith, Randy L.

1988-01-01

A part of NASA's Space Station will be a Flight Telerobotic Servicer (FTS) used to help assemble, service, and maintain the Space Station. Since the human operator will be required to control the FTS, the design of the human-telerobot interface must be optimized from a human factors perspective. Simulation has been used as an aid in the development of complex systems. Simulation has been especially useful when it has been applied to the development of complex systems. Simulation should ensure that the hardware and software components of the human-telerobot interface have been designed and selected so that the operator's capabilities and limitations have been accommodated for since this is a complex system where few direct comparisons to existent systems can be made. Three broad areas of the human-telerobot interface where simulation can be of assistance are described. The use of simulation not only can result in a well-designed human-telerobot interface, but also can be used to ensure that components have been selected to best meet system's goals, and for operator training.

The Diamond Beamline Controls and Data Acquisition Software Architecture

NASA Astrophysics Data System (ADS)

Rees, N.

2010-06-01

The software for the Diamond Light Source beamlines[1] is based on two complementary software frameworks: low level control is provided by the Experimental Physics and Industrial Control System (EPICS) framework[2][3] and the high level user interface is provided by the Java based Generic Data Acquisition or GDA[4][5]. EPICS provides a widely used, robust, generic interface across a wide range of hardware where the user interfaces are focused on serving the needs of engineers and beamline scientists to obtain detailed low level views of all aspects of the beamline control systems. The GDA system provides a high-level system that combines an understanding of scientific concepts, such as reciprocal lattice coordinates, a flexible python syntax scripting interface for the scientific user to control their data acquisition, and graphical user interfaces where necessary. This paper describes the beamline software architecture in more detail, highlighting how these complementary frameworks provide a flexible system that can accommodate a wide range of requirements.

The development of a highly constrained health level 7 implementation guide to facilitate electronic laboratory reporting to ambulatory electronic health record systems.

PubMed

Sujansky, Walter V; Overhage, J Marc; Chang, Sophia; Frohlich, Jonah; Faus, Samuel A

2009-01-01

Electronic laboratory interfaces can significantly increase the value of ambulatory electronic health record (EHR) systems by providing laboratory result data automatically and in a computable form. However, many ambulatory EHRs cannot implement electronic laboratory interfaces despite the existence of messaging standards, such as Health Level 7, version 2 (HL7). Among several barriers to implementing laboratory interfaces is the extensive optionality within the HL7 message standard. This paper describes the rationale for and development of an HL7 implementation guide that seeks to eliminate most of the optionality inherent in HL7, but retain the information content required for reporting outpatient laboratory results. A work group of heterogeneous stakeholders developed the implementation guide based on a set of design principles that emphasized parsimony, practical requirements, and near-term adoption. The resulting implementation guide contains 93% fewer optional data elements than HL7. This guide was successfully implemented by 15 organizations during an initial testing phase and has been approved by the HL7 standards body as an implementation guide for outpatient laboratory reporting. Further testing is required to determine whether widespread adoption of the implementation guide by laboratories and EHR systems can facilitate the implementation of electronic laboratory interfaces.

ESTL tracking and data relay satellite /TDRSS/ simulation system

NASA Technical Reports Server (NTRS)

Kapell, M. H.

1980-01-01

The Tracking Data Relay Satellite System (TDRSS) provides single access forward and return communication links with the Shuttle/Orbiter via S-band and Ku-band frequency bands. The ESTL (Electronic Systems Test Laboratory) at Lyndon B. Johnson Space Center (JSC) utilizes a TDRS satellite simulator and critical TDRS ground hardware for test operations. To accomplish Orbiter/TDRSS relay communications performance testing in the ESTL, a satellite simulator was developed which met the specification requirements of the TDRSS channels utilized by the Orbiter. Actual TDRSS ground hardware unique to the Orbiter communication interfaces was procured from individual vendors, integrated in the ESTL, and interfaced via a data bus for control and status monitoring. This paper discusses the satellite simulation hardware in terms of early development and subsequent modifications. The TDRS ground hardware configuration and the complex computer interface requirements are reviewed. Also, special test hardware such as a radio frequency interference test generator is discussed.

Access 5 - Step 1: Human Systems Integration Program Plan (HSIPP)

NASA Technical Reports Server (NTRS)

2005-01-01

This report describes the Human System Interface (HSI) analysis, design and test activities that will be performed to support the development of requirements and design guidelines to facilitate the incorporation of High Altitude Long Endurance (HALE) Remotely Operated Aircraft (ROA) at or above FL400 in the National Airspace System (NAS). These activities are required to support the design and development of safe, effective and reliable ROA operator and ATC interfaces. This plan focuses on the activities to be completed for Step 1 of the ACCESS 5 program. Updates to this document will be made for each of the four ACCESS 5 program steps.

Integrating UniTree with the data migration API

NASA Technical Reports Server (NTRS)

Schrodel, David G.

1994-01-01

The Data Migration Application Programming Interface (DMAPI) has the potential to allow developers of open systems Hierarchical Storage Management (HSM) products to virtualize native file systems without the requirement to make changes to the underlying operating system. This paper describes advantages of virtualizing native file systems in hierarchical storage management systems, the DMAPI at a high level, what the goals are for the interface, and the integration of the Convex UniTree+HSM with DMAPI along with some of the benefits derived in the resulting product.

Engineering Design of ITER Prototype Fast Plant System Controller

NASA Astrophysics Data System (ADS)

Goncalves, B.; Sousa, J.; Carvalho, B.; Rodrigues, A. P.; Correia, M.; Batista, A.; Vega, J.; Ruiz, M.; Lopez, J. M.; Rojo, R. Castro; Wallander, A.; Utzel, N.; Neto, A.; Alves, D.; Valcarcel, D.

2011-08-01

The ITER control, data access and communication (CODAC) design team identified the need for two types of plant systems. A slow control plant system is based on industrial automation technology with maximum sampling rates below 100 Hz, and a fast control plant system is based on embedded technology with higher sampling rates and more stringent real-time requirements than that required for slow controllers. The latter is applicable to diagnostics and plant systems in closed-control loops whose cycle times are below 1 ms. Fast controllers will be dedicated industrial controllers with the ability to supervise other fast and/or slow controllers, interface to actuators and sensors and, if necessary, high performance networks. Two prototypes of a fast plant system controller specialized for data acquisition and constrained by ITER technological choices are being built using two different form factors. This prototyping activity contributes to the Plant Control Design Handbook effort of standardization, specifically regarding fast controller characteristics. Envisaging a general purpose fast controller design, diagnostic use cases with specific requirements were analyzed and will be presented along with the interface with CODAC and sensors. The requirements and constraints that real-time plasma control imposes on the design were also taken into consideration. Functional specifications and technology neutral architecture, together with its implications on the engineering design, were considered. The detailed engineering design compliant with ITER standards was performed and will be discussed in detail. Emphasis will be given to the integration of the controller in the standard CODAC environment. Requirements for the EPICS IOC providing the interface to the outside world, the prototype decisions on form factor, real-time operating system, and high-performance networks will also be discussed, as well as the requirements for data streaming to CODAC for visualization and archiving.

How NASA KSC Controls Interfaces with the use of Motion Skeletons and Product Structure

NASA Technical Reports Server (NTRS)

Jones, Corey

2013-01-01

This presentation will show how NASA KSC controls interfaces for Modular Product Architecture (MPA) using Locator Skeletons, Interface Skeletons, and Product Structure, to be combined together within a Motion Skeleton. The user will learn how to utilize skeleton models to communicate interface data, as successfully done at NASA KSC in their use of Motion Skeletons to control interfaces for multi-launch systems. There will be discussion of the methodology used to control design requirements through WTParts, and how to utilize product structure for non-CAD documents.

NFIRAOS in 2015: engineering for future integration of complex subsystems

NASA Astrophysics Data System (ADS)

Atwood, Jenny; Andersen, David; Byrnes, Peter; Densmore, Adam; Fitzsimmons, Joeleff; Herriot, Glen; Hill, Alexis

2016-07-01

The Narrow Field InfraRed Adaptive Optics System (NFIRAOS) will be the first-light facility Adaptive Optics (AO) system for the Thirty Meter Telescope (TMT). NFIRAOS will be able to host three science instruments that can take advantage of this high performance system. NRC Herzberg is leading the design effort for this critical TMT subsystem. As part of the final design phase of NFIRAOS, we have identified multiple subsystems to be sub-contracted to Canadian industry. The scope of work for each subcontract is guided by the NFIRAOS Work Breakdown Structure (WBS) and is divided into two phases: the completion of the final design and the fabrication, assembly and delivery of the final product. Integration of the subsystems at NRC will require a detailed understanding of the interfaces between the subsystems, and this work has begun by defining the interface physical characteristics, stability, local coordinate systems, and alignment features. In order to maintain our stringent performance requirements, the interface parameters for each subsystem are captured in multiple performance budgets, which allow a bottom-up error estimate. In this paper we discuss our approach for defining the interfaces in a consistent manner and present an example error budget that is influenced by multiple subsystems.

AQBE — QBE Style Queries for Archetyped Data

NASA Astrophysics Data System (ADS)

Sachdeva, Shelly; Yaginuma, Daigo; Chu, Wanming; Bhalla, Subhash

Large-scale adoption of electronic healthcare applications requires semantic interoperability. The new proposals propose an advanced (multi-level) DBMS architecture for repository services for health records of patients. These also require query interfaces at multiple levels and at the level of semi-skilled users. In this regard, a high-level user interface for querying the new form of standardized Electronic Health Records system has been examined in this study. It proposes a step-by-step graphical query interface to allow semi-skilled users to write queries. Its aim is to decrease user effort and communication ambiguities, and increase user friendliness.

Human Computer Interface Design Criteria. Volume 1. User Interface Requirements

DTIC Science & Technology

2010-03-19

Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry. (c) All training...Shelf CSS Cascading Style Sheets DII Defense Information Infrastructure DISA Defense Information Systems Agency DoD Department of Defense

STS users study (study 2.2). Volume 2: STS users plan (user data requirements) study

NASA Technical Reports Server (NTRS)

Pritchard, E. I.

1975-01-01

Pre-flight scheduling and pre-flight requirements of the space transportation system are discussed. Payload safety requirements, shuttle flight manifests, and interface specifications are studied in detail.

Man-machine interface requirements - advanced technology

NASA Technical Reports Server (NTRS)

Remington, R. W.; Wiener, E. L.

1984-01-01

Research issues and areas are identified where increased understanding of the human operator and the interaction between the operator and the avionics could lead to improvements in the performance of current and proposed helicopters. Both current and advanced helicopter systems and avionics are considered. Areas critical to man-machine interface requirements include: (1) artificial intelligence; (2) visual displays; (3) voice technology; (4) cockpit integration; and (5) pilot work loads and performance.

Development of a Locomotion Interface for Portable Virtual Environment Systems Using an Inertial/Magnetic Sensor-Based System and a Ranging Measurement System

DTIC Science & Technology

2014-03-01

56 1. Motivation ...83 1. Motivation ...........................................................................................83 2. Environment Requirements...ENVIRONMENT SYSTEMS ......................................................97 A. BACKGROUND AND MOTIVATION

The control of float zone interfaces by the use of selected boundary conditions

NASA Technical Reports Server (NTRS)

Foster, L. M.; Mcintosh, J.

1983-01-01

The main goal of the float zone crystal growth project of NASA's Materials Processing in Space Program is to thoroughly understand the molten zone/freezing crystal system and all the mechanisms that govern this system. The surface boundary conditions required to give flat float zone solid melt interfaces were studied and computed. The results provide float zone furnace designers with better methods for controlling solid melt interface shapes and for computing thermal profiles and gradients. Documentation and a user's guide were provided for the computer software.

Optical-nanofiber-based interface for single molecules

NASA Astrophysics Data System (ADS)

Skoff, Sarah M.; Papencordt, David; Schauffert, Hardy; Bayer, Bernhard C.; Rauschenbeutel, Arno

2018-04-01

Optical interfaces for quantum emitters are a prerequisite for implementing quantum networks. Here, we couple single molecules to the guided modes of an optical nanofiber. The molecules are embedded within a crystal that provides photostability and, due to the inhomogeneous broadening, a means to spectrally address single molecules. Single molecules are excited and detected solely via the nanofiber interface without the requirement of additional optical access. In this way, we realize a fully fiber-integrated system that is scalable and may become a versatile constituent for quantum hybrid systems.

EOS image data processing system definition study

NASA Technical Reports Server (NTRS)

Gilbert, J.; Honikman, T.; Mcmahon, E.; Miller, E.; Pietrzak, L.; Yorsz, W.

1973-01-01

The Image Processing System (IPS) requirements and configuration are defined for NASA-sponsored advanced technology Earth Observatory System (EOS). The scope included investigation and definition of IPS operational, functional, and product requirements considering overall system constraints and interfaces (sensor, etc.) The scope also included investigation of the technical feasibility and definition of a point design reflecting system requirements. The design phase required a survey of present and projected technology related to general and special-purpose processors, high-density digital tape recorders, and image recorders.

Electrowetting-actuated zoom lens with spherical-interface liquid lenses.

PubMed

Peng, Runling; Chen, Jiabi; Zhuang, Songlin

2008-11-01

The interface shape of two immiscible liquids in a conical chamber is discussed. The analytical solution of the differential equation describing the interface shape shows that the interface shape is completely spherical when the density difference of two liquids is zero. On the basis of the spherical-interface shape and an energy-minimization method, explicit calculations and detailed analyses of an extended Young-type equation for the conical double-liquid lens are given. Finally, a novel design of a zoom lens system without motorized movements is proposed. The lens system consists of a fixed lens and two conical double-liquid variable-focus lenses. The structure and principle of the lens system are introduced in this paper. Taking finite objects as example, detailed calculations and simulation examples are presented to predict how two liquid lenses are related to meet the basic requirements of zoom lenses.

Design requirements for ubiquitous computing environments for healthcare professionals.

PubMed

Bång, Magnus; Larsson, Anders; Eriksson, Henrik

2004-01-01

Ubiquitous computing environments can support clinical administrative routines in new ways. The aim of such computing approaches is to enhance routine physical work, thus it is important to identify specific design requirements. We studied healthcare professionals in an emergency room and developed the computer-augmented environment NOSTOS to support teamwork in that setting. NOSTOS uses digital pens and paper-based media as the primary input interface for data capture and as a means of controlling the system. NOSTOS also includes a digital desk, walk-up displays, and sensor technology that allow the system to track documents and activities in the workplace. We propose a set of requirements and discuss the value of tangible user interfaces for healthcare personnel. Our results suggest that the key requirements are flexibility in terms of system usage and seamless integration between digital and physical components. We also discuss how ubiquitous computing approaches like NOSTOS can be beneficial in the medical workplace.

An intelligent multi-media human-computer dialogue system

NASA Technical Reports Server (NTRS)

Neal, J. G.; Bettinger, K. E.; Byoun, J. S.; Dobes, Z.; Thielman, C. Y.

1988-01-01

Sophisticated computer systems are being developed to assist in the human decision-making process for very complex tasks performed under stressful conditions. The human-computer interface is a critical factor in these systems. The human-computer interface should be simple and natural to use, require a minimal learning period, assist the user in accomplishing his task(s) with a minimum of distraction, present output in a form that best conveys information to the user, and reduce cognitive load for the user. In pursuit of this ideal, the Intelligent Multi-Media Interfaces project is devoted to the development of interface technology that integrates speech, natural language text, graphics, and pointing gestures for human-computer dialogues. The objective of the project is to develop interface technology that uses the media/modalities intelligently in a flexible, context-sensitive, and highly integrated manner modelled after the manner in which humans converse in simultaneous coordinated multiple modalities. As part of the project, a knowledge-based interface system, called CUBRICON (CUBRC Intelligent CONversationalist) is being developed as a research prototype. The application domain being used to drive the research is that of military tactical air control.

A validated methodology for determination of laboratory instrument computer interface efficacy

NASA Astrophysics Data System (ADS)

1984-12-01

This report is intended to provide a methodology for determining when, and for which instruments, direct interfacing of laboratory instrument and laboratory computers is beneficial. This methodology has been developed to assist the Tri-Service Medical Information Systems Program Office in making future decisions regarding laboratory instrument interfaces. We have calculated the time savings required to reach a break-even point for a range of instrument interface prices and corresponding average annual costs. The break-even analyses used empirical data to estimate the number of data points run per day that are required to meet the break-even point. The results indicate, for example, that at a purchase price of $3,000, an instrument interface will be cost-effective if the instrument is utilized for at least 154 data points per day if operated in the continuous mode, or 216 points per day if operated in the discrete mode. Although this model can help to ensure that instrument interfaces are cost effective, additional information should be considered in making the interface decisions. A reduction in results transcription errors may be a major benefit of instrument interfacing.

A universal data access and protocol integration mechanism for smart home

NASA Astrophysics Data System (ADS)

Shao, Pengfei; Yang, Qi; Zhang, Xuan

2013-03-01

With the lack of standardized or completely missing communication interfaces in home electronics, there is no perfect solution to address every aspect in smart homes based on existing protocols and technologies. In addition, the central control unit (CCU) of smart home system working point-to-point between the multiple application interfaces and the underlying hardware interfaces leads to its complicated architecture and unpleasant performance. A flexible data access and protocol integration mechanism is required. The current paper offers a universal, comprehensive data access and protocol integration mechanism for a smart home. The universal mechanism works as a middleware adapter with unified agreements of the communication interfaces and protocols, offers an abstraction of the application level from the hardware specific and decoupling the hardware interface modules from the application level. Further abstraction for the application interfaces and the underlying hardware interfaces are executed based on adaption layer to provide unified interfaces for more flexible user applications and hardware protocol integration. This new universal mechanism fundamentally changes the architecture of the smart home and in some way meets the practical requirement of smart homes more flexible and desirable.

The development of an intelligent interface to a computational fluid dynamics flow-solver code

NASA Technical Reports Server (NTRS)

Williams, Anthony D.

1988-01-01

Researchers at NASA Lewis are currently developing an 'intelligent' interface to aid in the development and use of large, computational fluid dynamics flow-solver codes for studying the internal fluid behavior of aerospace propulsion systems. This paper discusses the requirements, design, and implementation of an intelligent interface to Proteus, a general purpose, 3-D, Navier-Stokes flow solver. The interface is called PROTAIS to denote its introduction of artificial intelligence (AI) concepts to the Proteus code.

The development of an intelligent interface to a computational fluid dynamics flow-solver code

NASA Technical Reports Server (NTRS)

Williams, Anthony D.

1988-01-01

Researchers at NASA Lewis are currently developing an 'intelligent' interface to aid in the development and use of large, computational fluid dynamics flow-solver codes for studying the internal fluid behavior of aerospace propulsion systems. This paper discusses the requirements, design, and implementation of an intelligent interface to Proteus, a general purpose, three-dimensional, Navier-Stokes flow solver. The interface is called PROTAIS to denote its introduction of artificial intelligence (AI) concepts to the Proteus code.

Traffic off-balancing algorithm for energy efficient networks

NASA Astrophysics Data System (ADS)

Kim, Junhyuk; Lee, Chankyun; Rhee, June-Koo Kevin

2011-12-01

Physical layer of high-end network system uses multiple interface arrays. Under the load-balancing perspective, light load can be distributed to multiple interfaces. However, it can cause energy inefficiency in terms of the number of poor utilization interfaces. To tackle this energy inefficiency, traffic off-balancing algorithm for traffic adaptive interface sleep/awake is investigated. As a reference model, 40G/100G Ethernet is investigated. We report that suggested algorithm can achieve energy efficiency while satisfying traffic transmission requirement.

Human-telerobot interactions - Information, control, and mental models

NASA Technical Reports Server (NTRS)

Smith, Randy L.; Gillan, Douglas J.

1987-01-01

A part of the NASA's Space Station will be a teleoperated robot (telerobot) with arms for grasping and manipulation, feet for holding onto objects, and television cameras for visual feedback. The objective of the work described in this paper is to develop the requirements and specifications for the user-telerobot interface and to determine through research and testing that the interface results in efficient system operation. The focus of the development of the user-telerobot interface is on the information required by the user, the user inputs, and the design of the control workstation. Closely related to both the information required by the user and the user's control of the telerobot is the user's mental model of the relationship between the control inputs and the telerobot's actions.

Development of mining guidance and control systems

NASA Technical Reports Server (NTRS)

1979-01-01

New fundamental interface sensor concepts were identified and investigated including tabulation of the physical and performance characteristics of two new interface detector concepts: - natural background radiation and magnetic spin resonance. Studies of guidance and control techniques for the longwall miner identified three basic systems for use in automated/remote controlled longwall mining. The following projects were initiated: system study which will more completely define the longwall guidance and control system design concepts; integration of the various control functions (vertical, yaw, and roll); and hardware technical requirements.

Geographic information system/watershed model interface

USGS Publications Warehouse

Fisher, Gary T.

1989-01-01

Geographic information systems allow for the interactive analysis of spatial data related to water-resources investigations. A conceptual design for an interface between a geographic information system and a watershed model includes functions for the estimation of model parameter values. Design criteria include ease of use, minimal equipment requirements, a generic data-base management system, and use of a macro language. An application is demonstrated for a 90.1-square-kilometer subbasin of the Patuxent River near Unity, Maryland, that performs automated derivation of watershed parameters for hydrologic modeling.

Air Force Global Weather Central System Architecture Study. Final System/Subsystem Summary Report. Volume 4. Systems Analysis and Trade Studies

DTIC Science & Technology

1976-03-01

atmosphere,as well as very fine grid cloud models and cloud probability models. Some of the new requirements that will be supported with this system are a...including the Advanced Prediction Model for the global atmosphere, as well as very fine grid cloud models and cloud proba- bility models. Some of the new...with the mapping and gridding function (imput and output)? Should the capability exist to interface raw ungridded data with the SID interface

Development of a waste collection system for the space shuttle.

NASA Technical Reports Server (NTRS)

Behrend, A. F., Jr.; Swider, J. E., Jr.

1972-01-01

The development of a waste collection system to accommodate both male and female crew members for the space shuttle is discussed. The waste collection system, with emphasis on the collection and transfer of urine, is described. Human-interface requirements, zero-gravity influences and effects, and operational considerations required for total system design are discussed.

A software architecture for automating operations processes

NASA Technical Reports Server (NTRS)

Miller, Kevin J.

1994-01-01

The Operations Engineering Lab (OEL) at JPL has developed a software architecture based on an integrated toolkit approach for simplifying and automating mission operations tasks. The toolkit approach is based on building adaptable, reusable graphical tools that are integrated through a combination of libraries, scripts, and system-level user interface shells. The graphical interface shells are designed to integrate and visually guide a user through the complex steps in an operations process. They provide a user with an integrated system-level picture of an overall process, defining the required inputs and possible output through interactive on-screen graphics. The OEL has developed the software for building these process-oriented graphical user interface (GUI) shells. The OEL Shell development system (OEL Shell) is an extension of JPL's Widget Creation Library (WCL). The OEL Shell system can be used to easily build user interfaces for running complex processes, applications with extensive command-line interfaces, and tool-integration tasks. The interface shells display a logical process flow using arrows and box graphics. They also allow a user to select which output products are desired and which input sources are needed, eliminating the need to know which program and its associated command-line parameters must be executed in each case. The shells have also proved valuable for use as operations training tools because of the OEL Shell hypertext help environment. The OEL toolkit approach is guided by several principles, including the use of ASCII text file interfaces with a multimission format, Perl scripts for mission-specific adaptation code, and programs that include a simple command-line interface for batch mode processing. Projects can adapt the interface shells by simple changes to the resources configuration file. This approach has allowed the development of sophisticated, automated software systems that are easy, cheap, and fast to build. This paper will discuss our toolkit approach and the OEL Shell interface builder in the context of a real operations process example. The paper will discuss the design and implementation of a Ulysses toolkit for generating the mission sequence of events. The Sequence of Events Generation (SEG) system provides an adaptable multimission toolkit for producing a time-ordered listing and timeline display of spacecraft commands, state changes, and required ground activities.

Macintosh II based space Telemetry and Command (MacTac) system

NASA Technical Reports Server (NTRS)

Dominy, Carol T.; Chesney, James R.; Collins, Aaron S.; Kay, W. K.

1991-01-01

The general architecture and the principal functions of the Macintosh II based Telemetry and Command system, presently under development, are described, with attention given to custom telemetry cards, input/output interfaces, and the icon driven user interface. The MacTac is a low-cost, transportable, easy to use, compact system designed to meet the requirements specified by the Consultative Committeee for Space Data Systems while remaining flexible enough to support a wide variety of other user specific telemetry processing requirements, such as TDM data. In addition, the MacTac can accept or generate forward data (such as spacecraft commands), calculate and append a Polynomial Check Code, and output these data to NASCOM to provide full Telemetry and Command capability.

We can't explore space without it - Common human space needs for exploration spaceflight

NASA Technical Reports Server (NTRS)

Daues, K. R.; Erwin, H. O.

1992-01-01

An overview is conducted of physiological, psychological, and human-interface requirements for manned spaceflight programs to establish common criteria. Attention is given to the comfort levels relevant to human support in exploration mission spacecraft and planetary habitats, and three comfort levels (CLs) are established. The levels include: (1) CL-1 for basic crew life support; (2) CL-2 for enabling the nominal completion of mission science; and (3) CL-3 which provides for enhanced life support and user-friendly interface systems. CL-2 support systems can include systems for EVA, workstations, and activity centers for repairs and enhanced utilization of payload and human/machine integration. CL-3 supports can be useful for maintaining crew psychological and physiological health as well as the design of comfortable and earthlike surroundings. While all missions require CL-1 commonality, CL-2 commonality is required only for EVA systems, display nomenclature, and restraint designs.

A direct-interface fusible heat sink for astronaut cooling

NASA Technical Reports Server (NTRS)

Lomax, Curtis; Webbon, B. W.

1990-01-01

Astronaut cooling during extravehicular activity is a critical design issue in developing a portable life support system that meets the requirements of a space station mission. Some the requirements are that the cooling device can be easily regenerable and nonventing during operation. In response to this, a direct-interface, fusible heat sink prototpye with freezable quick-disconnects was developed. A proof-of-concept prototype was constructed and tested that consists of an elastic container filled with normal tap water and having two quick-disconnects embedded in a wall. These quick-disconnects are designed so that they may be frozen with the ice and yet still be joined to the cooling system, allowing an immediate flow path. The inherent difficulties in a direct-interface heat sink have been overcome, i.e., (1) establishing an initial flow path; (2) avoiding low-flow freeze-up; and (3) achieving adequate heat-transfer rates at the end of the melting process. The requirements, design, fabrication, and testing are discussed.

A direct-interface, fusible heat sink for astronaut cooling

NASA Technical Reports Server (NTRS)

Lomax, Curtis; Webbon, B. W.

1990-01-01

Astronaut cooling during extravehicular activity is a critical design issue in developing a portable life support system that meets the requirements of a space station mission. Some of the requirements are that the cooling device can be easily regenerable and nonventing during operation. In response to this, a direct-interface, fusible heat sink prototype with freezable quick-disconnects was developed. A proof-of-concept prototype was constructed and tested that consists of an elastic container filled with normal tap water and having two quick-disconnects embedded in a wall. These quick-disconnects are designed so that they may be frozen with the ice and yet still be joined to the cooling system, allowing an immediate flow path. The inherent difficulties in a direct-interface heat sink have been overcome, i.e., (1) establishing an initial flow path; (2) avoiding low-flow freeze-up; and (3) achieving adequate heat-transfer rates at the end of the melting process. The requirements, design, fabrication, and testing are discussed.

Interface Control Specification

DOT National Transportation Integrated Search

1996-06-12

The Requirements Specification Document (#9933.04) identifies the overall system level requirements of the Gary-Chicago-Milwaukee (GCM) Corridor Transportation Information Center (C-TIC). This document provides details about the data and control flow...

An approach to a real-time distribution system

NASA Technical Reports Server (NTRS)

Kittle, Frank P., Jr.; Paddock, Eddie J.; Pocklington, Tony; Wang, Lui

1990-01-01

The requirements of a real-time data distribution system are to provide fast, reliable delivery of data from source to destination with little or no impact to the data source. In this particular case, the data sources are inside an operational environment, the Mission Control Center (MCC), and any workstation receiving data directly from the operational computer must conform to the software standards of the MCC. In order to supply data to development workstations outside of the MCC, it is necessary to use gateway computers that prevent unauthorized data transfer back to the operational computers. Many software programs produced on the development workstations are targeted for real-time operation. Therefore, these programs must migrate from the development workstation to the operational workstation. It is yet another requirement for the Data Distribution System to ensure smooth transition of the data interfaces for the application developers. A standard data interface model has already been set up for the operational environment, so the interface between the distribution system and the application software was developed to match that model as closely as possible. The system as a whole therefore allows the rapid development of real-time applications without impacting the data sources. In summary, this approach to a real-time data distribution system provides development users outside of the MCC with an interface to MCC real-time data sources. In addition, the data interface was developed with a flexible and portable software design. This design allows for the smooth transition of new real-time applications to the MCC operational environment.

Transient Turbine Engine Modeling with Hardware-in-the-Loop Power Extraction (PREPRINT)

DTIC Science & Technology

2008-07-01

Furthermore, it must be compatible with a real - time operating system that is capable of running the simulation. For some models, especially those that use...problem of interfacing the engine/control model to a real - time operating system and associated lab hardware becomes a problem of interfacing these...model in real-time. This requires the use of a real - time operating system and a compatible I/O (input/output) board. Figure 1 illustrates the HIL

An improved maximum permissible exposure meter for safety assessments of laser radiation

NASA Astrophysics Data System (ADS)

Corder, D. A.; Evans, D. R.; Tyrer, J. R.

1997-12-01

Current interest in laser radiation safety requires demonstration that a laser system has been designed to prevent exposure to levels of laser radiation exceeding the Maximum Permissible Exposure. In some simple systems it is possible to prove this by calculation, but in most cases it is preferable to confirm calculated results with a measurement. This measurement may be made with commercially available equipment, but there are limitations with this approach. A custom designed instrument is presented in which the full range of measurement issues have been addressed. Important features of the instrument are the design and optimisation of detector heads for the measurement task, and consideration of user interface requirements. Three designs for detector head are presented, these cover the majority of common laser types. Detector heads are designed to optimise the performance of relatively low cost detector elements for this measurement task. The three detector head designs are suitable for interfacing to photodiodes, low power thermopiles and pyroelectric detectors. Design of the user interface was an important aspect of the work. A user interface which is designed for the specific application minimises the risk of user error or misinterpretation of the measurement results. A palmtop computer was used to provide an advanced user interface. User requirements were considered in order that the final implement was well matched to the task of laser radiation hazard audits.

The theory of interface slicing

NASA Technical Reports Server (NTRS)

Beck, Jon

1993-01-01

Interface slicing is a new tool which was developed to facilitate reuse-based software engineering, by addressing the following problems, needs, and issues: (1) size of systems incorporating reused modules; (2) knowledge requirements for program modification; (3) program understanding for reverse engineering; (4) module granularity and domain management; and (5) time and space complexity of conventional slicing. The definition of a form of static program analysis called interface slicing is addressed.

An assessment of the real-time application capabilities of the SIFT computer system

NASA Technical Reports Server (NTRS)

Butler, R. W.

1982-01-01

The real-time capabilities of the SIFT computer system, a highly reliable multicomputer architecture developed to support the flight controls of a relaxed static stability aircraft, are discussed. The SIFT computer system was designed to meet extremely high reliability requirements and to facilitate a formal proof of its correctness. Although SIFT represents a significant achievement in fault-tolerant system research it presents an unusual and restrictive interface to its users. The characteristics of the user interface and its impact on application system design are assessed.

A user interface for a knowledge-based planning and scheduling system

NASA Technical Reports Server (NTRS)

Mulvehill, Alice M.

1988-01-01

The objective of EMPRESS (Expert Mission Planning and Replanning Scheduling System) is to support the planning and scheduling required to prepare science and application payloads for flight aboard the US Space Shuttle. EMPRESS was designed and implemented in Zetalisp on a 3600 series Symbolics Lisp machine. Initially, EMPRESS was built as a concept demonstration system. The system has since been modified and expanded to ensure that the data have integrity. Issues underlying the design and development of the EMPRESS-I interface, results from a system usability assessment, and consequent modifications are described.

Service offerings and interfaces for the ACTS network of Earth stations

NASA Technical Reports Server (NTRS)

Coney, Thom A.

1988-01-01

The Advanced Communications Satellite (ACTS) is capable of two modes of communication. Mode 1 is a mesh network of Earth stations using baseband-switched, time-division multiple-access (BBS-TDMA) and hopping beams. Mode 2 is a mesh network using satellite-switched, time-division multiple-access (SS-TDMA) and fixed (or hopping) beams. The purpose of this paper is to present the functional requirements and the design of the ACTS Mode 1 Earth station terrestrial interface. Included among the requirements are that: (1) the interface support standard telecommunications service offerings (i.e., voice, video and data at rates ranging from 9.6 kbps to 44 Mbps); (2) the interface support the unique design characteristics of the ACTS communications systems (e.g., the real time demand assignment of satellite capacity); and (3) the interface support test hardware capable of validating ACTS communications processes. The resulting interface design makes use of an appropriate combination of T1 or T3 multiplexers and a small central office (maximum capacity 56 subscriber lines per unit).

IAC-1.5 - INTEGRATED ANALYSIS CAPABILITY

NASA Technical Reports Server (NTRS)

Vos, R. G.

1994-01-01

The objective of the Integrated Analysis Capability (IAC) system is to provide a highly effective, interactive analysis tool for the integrated design of large structures. IAC was developed to interface programs from the fields of structures, thermodynamics, controls, and system dynamics with an executive system and a database to yield a highly efficient multi-disciplinary system. Special attention is given to user requirements such as data handling and on-line assistance with operational features, and the ability to add new modules of the user's choice at a future date. IAC contains an executive system, a database, general utilities, interfaces to various engineering programs, and a framework for building interfaces to other programs. IAC has shown itself to be effective in automating data transfer among analysis programs. The IAC system architecture is modular in design. 1) The executive module contains an input command processor, an extensive data management system, and driver code to execute the application modules. 2) Technical modules provide standalone computational capability as well as support for various solution paths or coupled analyses. 3) Graphics and model generation modules are supplied for building and viewing models. 4) Interface modules provide for the required data flow between IAC and other modules. 5) User modules can be arbitrary executable programs or JCL procedures with no pre-defined relationship to IAC. 6) Special purpose modules are included, such as MIMIC (Model Integration via Mesh Interpolation Coefficients), which transforms field values from one model to another; LINK, which simplifies incorporation of user specific modules into IAC modules; and DATAPAC, the National Bureau of Standards statistical analysis package. The IAC database contains structured files which provide a common basis for communication between modules and the executive system, and can contain unstructured files such as NASTRAN checkpoint files, DISCOS plot files, object code, etc. The user can define groups of data and relations between them. A full data manipulation and query system operates with the database. The current interface modules comprise five groups: 1) Structural analysis - IAC contains a NASTRAN interface for standalone analysis or certain structural/control/thermal combinations. IAC provides enhanced structural capabilities for normal modes and static deformation analysis via special DMAP sequences. 2) Thermal analysis - IAC supports finite element and finite difference techniques for steady state or transient analysis. There are interfaces for the NASTRAN thermal analyzer, SINDA/SINFLO, and TRASYS II. 3) System dynamics - A DISCOS interface allows full use of this simulation program for either nonlinear time domain analysis or linear frequency domain analysis. 4) Control analysis - Interfaces for the ORACLS, SAMSAN, NBOD2, and INCA programs allow a wide range of control system analyses and synthesis techniques. 5) Graphics - The graphics packages PLOT and MOSAIC are included in IAC. PLOT generates vector displays of tabular data in the form of curves, charts, correlation tables, etc., while MOSAIC generates color raster displays of either tabular of array type data. Either DI3000 or PLOT-10 graphics software is required for full graphics capability. IAC is available by license for a period of 10 years to approved licensees. The licensed program product includes one complete set of supporting documentation. Additional copies of the documentation may be purchased separately. IAC is written in FORTRAN 77 and has been implemented on a DEC VAX series computer operating under VMS. IAC can be executed by multiple concurrent users in batch or interactive mode. The basic central memory requirement is approximately 750KB. IAC includes the executive system, graphics modules, a database, general utilities, and the interfaces to all analysis and controls programs described above. Source code is provided for the control programs ORACLS, SAMSAN, NBOD2, and DISCOS. The following programs are also available from COSMIC a

IAC-1.5 - INTEGRATED ANALYSIS CAPABILITY

NASA Technical Reports Server (NTRS)

Vos, R. G.

1994-01-01

The objective of the Integrated Analysis Capability (IAC) system is to provide a highly effective, interactive analysis tool for the integrated design of large structures. IAC was developed to interface programs from the fields of structures, thermodynamics, controls, and system dynamics with an executive system and a database to yield a highly efficient multi-disciplinary system. Special attention is given to user requirements such as data handling and on-line assistance with operational features, and the ability to add new modules of the user's choice at a future date. IAC contains an executive system, a database, general utilities, interfaces to various engineering programs, and a framework for building interfaces to other programs. IAC has shown itself to be effective in automating data transfer among analysis programs. The IAC system architecture is modular in design. 1) The executive module contains an input command processor, an extensive data management system, and driver code to execute the application modules. 2) Technical modules provide standalone computational capability as well as support for various solution paths or coupled analyses. 3) Graphics and model generation modules are supplied for building and viewing models. 4) Interface modules provide for the required data flow between IAC and other modules. 5) User modules can be arbitrary executable programs or JCL procedures with no pre-defined relationship to IAC. 6) Special purpose modules are included, such as MIMIC (Model Integration via Mesh Interpolation Coefficients), which transforms field values from one model to another; LINK, which simplifies incorporation of user specific modules into IAC modules; and DATAPAC, the National Bureau of Standards statistical analysis package. The IAC database contains structured files which provide a common basis for communication between modules and the executive system, and can contain unstructured files such as NASTRAN checkpoint files, DISCOS plot files, object code, etc. The user can define groups of data and relations between them. A full data manipulation and query system operates with the database. The current interface modules comprise five groups: 1) Structural analysis - IAC contains a NASTRAN interface for standalone analysis or certain structural/control/thermal combinations. IAC provides enhanced structural capabilities for normal modes and static deformation analysis via special DMAP sequences. 2) Thermal analysis - IAC supports finite element and finite difference techniques for steady state or transient analysis. There are interfaces for the NASTRAN thermal analyzer, SINDA/SINFLO, and TRASYS II. 3) System dynamics - A DISCOS interface allows full use of this simulation program for either nonlinear time domain analysis or linear frequency domain analysis. 4) Control analysis - Interfaces for the ORACLS, SAMSAN, NBOD2, and INCA programs allow a wide range of control system analyses and synthesis techniques. 5) Graphics - The graphics packages PLOT and MOSAIC are included in IAC. PLOT generates vector displays of tabular data in the form of curves, charts, correlation tables, etc., while MOSAIC generates color raster displays of either tabular of array type data. Either DI3000 or PLOT-10 graphics software is required for full graphics capability. IAC is available by license for a period of 10 years to approved licensees. The licensed program product includes one complete set of supporting documentation. Additional copies of the documentation may be purchased separately. IAC is written in FORTRAN 77 and has been implemented on a DEC VAX series computer operating under VMS. IAC can be executed by multiple concurrent users in batch or interactive mode. The basic central memory requirement is approximately 750KB. IAC includes the executive system, graphics modules, a database, general utilities, and the interfaces to all analysis and controls programs described above. Source code is provided for the control programs ORACLS, SAMSAN, NBOD2, and DISCOS. The following programs are also available from COSMIC as separate packages: NASTRAN, SINDA/SINFLO, TRASYS II, DISCOS, ORACLS, SAMSAN, NBOD2, and INCA. IAC was developed in 1985.

Optical data transmission technology for fixed and drag-on STS payloads umbilicals. Volume 1: Executive summary

NASA Technical Reports Server (NTRS)

St.denis, R. W.

1981-01-01

The feasibility of using optical data handling methods to transmit payload checkout and telemetry is discussed. Optical communications are superior to conventional communication systems for the following reasons: high data capacity optical channels; small and light weight optical cables; and optical signal immunity to electromagnetic interference. Task number one analyzed the ground checkout data requirements that may be expected from the payload community. Task number two selected the optical approach based on the interface requirements, the location of the interface, the amount of time required to reconfigure hardware, and the method of transporting the optical signal. Task number three surveyed and selected optical components for the two payload data link. Task number four makes a qualitative comparison of the conventional electrical communication system and the proposed optical communication system.

A Wireless Biomedical Signal Interface System-on-Chip for Body Sensor Networks.

PubMed

Lei Wang; Guang-Zhong Yang; Jin Huang; Jinyong Zhang; Li Yu; Zedong Nie; Cumming, D R S

2010-04-01

Recent years have seen the rapid development of biosensor technology, system-on-chip design, wireless technology. and ubiquitous computing. When assembled into an autonomous body sensor network (BSN), the technologies become powerful tools in well-being monitoring, medical diagnostics, and personal connectivity. In this paper, we describe the first demonstration of a fully customized mixed-signal silicon chip that has most of the attributes required for use in a wearable or implantable BSN. Our intellectual-property blocks include low-power analog sensor interface for temperature and pH, a data multiplexing and conversion module, a digital platform based around an 8-b microcontroller, data encoding for spread-spectrum wireless transmission, and a RF section requiring very few off-chip components. The chip has been fully evaluated and tested by connection to external sensors, and it satisfied typical system requirements.

Designing berthing mechanisms for international compatibility

NASA Technical Reports Server (NTRS)

Winch, John; Gonzalez-Vallejo, Juan J.

1991-01-01

The paper examines the technological issues regarding common berthing interfaces for the Space Station Freedom and pressurized modules from U.S., European, and Japanese space programs. The development of the common berthing mechanism (CBM) is based on common requirements concerning specifications, launch environments, and the unique requirements of ESA's Man-Tended Free Flyer. The berthing mechanism is composed of an active and a passive half, a remote manipulator system, 4 capture-latch assemblies, 16 structural bolts, and a pressure gage to verify equalization. Extensive graphic and verbal descriptions of each element are presented emphasizing the capture-latch motion and powered-bolt operation. The support systems to complete the interface are listed, and the manufacturing requirements for consistent fabrication are discussed to ensure effective international development.

The Johnson Space Center Management Information Systems (JSCMIS): An interface for organizational databases

NASA Technical Reports Server (NTRS)

Bishop, Peter C.; Erickson, Lloyd

1990-01-01

The Management Information and Decision Support Environment (MIDSE) is a research activity to build and test a prototype of a generic human interface on the Johnson Space Center (JSC) Information Network (CIN). The existing interfaces were developed specifically to support operations rather than the type of data which management could use. The diversity of the many interfaces and their relative difficulty discouraged occasional users from attempting to use them for their purposes. The MIDSE activity approached this problem by designing and building an interface to one JSC data base - the personnel statistics tables of the NASA Personnel and Payroll System (NPPS). The interface was designed against the following requirements: generic (use with any relational NOMAD data base); easy to learn (intuitive operations for new users); easy to use (efficient operations for experienced users); self-documenting (help facility which informs users about the data base structure as well as the operation of the interface); and low maintenance (easy configuration to new applications). A prototype interface entitled the JSC Management Information Systems (JSCMIS) was produced. It resides on CIN/PROFS and is available to JSC management who request it. The interface has passed management review and is ready for early use. Three kinds of data are now available: personnel statistics, personnel register, and plan/actual cost.

Functional Interface Considerations within an Exploration Life Support System Architecture

NASA Technical Reports Server (NTRS)

Perry, Jay L.; Sargusingh, Miriam J.; Toomarian, Nikzad

2016-01-01

As notional life support system (LSS) architectures are developed and evaluated, myriad options must be considered pertaining to process technologies, components, and equipment assemblies. Each option must be evaluated relative to its impact on key functional interfaces within the LSS architecture. A leading notional architecture has been developed to guide the path toward realizing future crewed space exploration goals. This architecture includes atmosphere revitalization, water recovery and management, and environmental monitoring subsystems. Guiding requirements for developing this architecture are summarized and important interfaces within the architecture are discussed. The role of environmental monitoring within the architecture is described.

Exploring the simulation requirements for virtual regional anesthesia training

NASA Astrophysics Data System (ADS)

Charissis, V.; Zimmer, C. R.; Sakellariou, S.; Chan, W.

2010-01-01

This paper presents an investigation towards the simulation requirements for virtual regional anaesthesia training. To this end we have developed a prototype human-computer interface designed to facilitate Virtual Reality (VR) augmenting educational tactics for regional anaesthesia training. The proposed interface system, aims to compliment nerve blocking techniques methods. The system is designed to operate in real-time 3D environment presenting anatomical information and enabling the user to explore the spatial relation of different human parts without any physical constrains. Furthermore the proposed system aims to assist the trainee anaesthetists so as to build a mental, three-dimensional map of the anatomical elements and their depictive relationship to the Ultra-Sound imaging which is used for navigation of the anaesthetic needle. Opting for a sophisticated approach of interaction, the interface elements are based on simplified visual representation of real objects, and can be operated through haptic devices and surround auditory cues. This paper discusses the challenges involved in the HCI design, introduces the visual components of the interface and presents a tentative plan of future work which involves the development of realistic haptic feedback and various regional anaesthesia training scenarios.

Steered Molecular Dynamics Simulations Predict Conformational Stability of Glutamate Receptors.

PubMed

Musgaard, Maria; Biggin, Philip C

2016-09-26

The stability of protein-protein interfaces can be essential for protein function. For ionotropic glutamate receptors, a family of ligand-gated ion channels vital for normal function of the central nervous system, such an interface exists between the extracellular ligand binding domains (LBDs). In the full-length protein, the LBDs are arranged as a dimer of dimers. Agonist binding to the LBDs opens the ion channel, and briefly after activation the receptor desensitizes. Several residues at the LBD dimer interface are known to modulate desensitization, and conformational changes around these residues are believed to be involved in the state transition. The general hypothesis is that the interface is disrupted upon desensitization, and structural evidence suggests that the disruption might be substantial. However, when cross-linking the central part of this interface, functional data suggest that the receptor can still undergo desensitization, contradicting the hypothesis of major interface disruption. Here, we illustrate how opening the dimer interface using steered molecular dynamics (SMD) simulations, and analyzing the work values required, provides a quantitative measure for interface stability. For one subtype of glutamate receptors, which is regulated by ion binding to the dimer interface, we show that opening the interface without ions bound requires less work than with ions present, suggesting that ion binding indeed stabilizes the interface. Likewise, for interface mutants with longer-lived active states, the interface is more stable, while the work required to open the interface is reduced for less active mutants. Moreover, a cross-linked mutant can still undergo initial interface opening motions similar to the native receptor and at similar energetic cost. Thus, our results support that interface opening is involved in desensitization. Furthermore, they provide reconciliation of apparently opposing data and demonstrate that SMD simulations can give relevant biological insight into longer time scale processes without the need for expensive calculations.

78 FR 58449 - Generator Requirements at the Transmission Interface

Federal Register 2010, 2011, 2012, 2013, 2014

2013-09-24

... Connection Requirements), FAC-003-3 (Transmission Vegetation Management), PRC-004- 2.1a (Analysis and... and Generation Protection System Maintenance and Testing). The modifications improve reliability... Standards FAC-001-1 (Facility Connection Requirements), FAC-003-3 (Transmission Vegetation Management), PRC...

A personal digital assistant application (MobilDent) for dental fieldwork data collection, information management and database handling.

PubMed

Forsell, M; Häggström, M; Johansson, O; Sjögren, P

2008-11-08

To develop a personal digital assistant (PDA) application for oral health assessment fieldwork, including back-office and database systems (MobilDent). System design, construction and implementation of PDA, back-office and database systems. System requirements for MobilDent were collected, analysed and translated into system functions. User interfaces were implemented and system architecture was outlined. MobilDent was based on a platform with. NET (Microsoft) components, using an SQL Server 2005 (Microsoft) for data storage with Windows Mobile (Microsoft) operating system. The PDA devices were Dell Axim. System functions and user interfaces were specified for MobilDent. User interfaces for PDA, back-office and database systems were based on. NET programming. The PDA user interface was based on Windows suitable to a PDA display, whereas the back-office interface was designed for a normal-sized computer screen. A synchronisation module (MS Active Sync, Microsoft) was used to enable download of field data from PDA to the database. MobilDent is a feasible application for oral health assessment fieldwork, and the oral health assessment database may prove a valuable source for care planning, educational and research purposes. Further development of the MobilDent system will include wireless connectivity with download-on-demand technology.

Software and Human-Machine Interface Development for Environmental Controls Subsystem Support

NASA Technical Reports Server (NTRS)

Dobson, Matthew

2018-01-01

The Space Launch System (SLS) is the next premier launch vehicle for NASA. It is the next stage of manned space exploration from American soil, and will be the platform in which we push further beyond Earth orbit. In preparation of the SLS maiden voyage on Exploration Mission 1 (EM-1), the existing ground support architecture at Kennedy Space Center required significant overhaul and updating. A comprehensive upgrade of controls systems was necessary, including programmable logic controller software, as well as Launch Control Center (LCC) firing room and local launch pad displays for technician use. Environmental control acts as an integral component in these systems, being the foremost system for conditioning the pad and extremely sensitive launch vehicle until T-0. The Environmental Controls Subsystem (ECS) required testing and modification to meet the requirements of the designed system, as well as the human factors requirements of NASA software for Validation and Verification (V&V). This term saw significant strides in the progress and functionality of the human-machine interfaces used at the launch pad, and improved integration with the controller code.

Analysis and preliminary design of Kunming land use and planning management information system

NASA Astrophysics Data System (ADS)

Li, Li; Chen, Zhenjie

2007-06-01

This article analyzes Kunming land use planning and management information system from the system building objectives and system building requirements aspects, nails down the system's users, functional requirements and construction requirements. On these bases, the three-tier system architecture based on C/S and B/S is defined: the user interface layer, the business logic layer and the data services layer. According to requirements for the construction of land use planning and management information database derived from standards of the Ministry of Land and Resources and the construction program of the Golden Land Project, this paper divides system databases into planning document database, planning implementation database, working map database and system maintenance database. In the design of the system interface, this paper uses various methods and data formats for data transmission and sharing between upper and lower levels. According to the system analysis results, main modules of the system are designed as follows: planning data management, the planning and annual plan preparation and control function, day-to-day planning management, planning revision management, decision-making support, thematic inquiry statistics, planning public participation and so on; besides that, the system realization technologies are discussed from the system operation mode, development platform and other aspects.

Modular space station Phase B extension preliminary performance specification. Volume 2: Project

NASA Technical Reports Server (NTRS)

1971-01-01

The four systems of the modular space station project are described, and the interfaces between this project and the shuttle project, the tracking and data relay satellite project, and an arbitrarily defined experiment project are defined. The experiment project was synthesized from internal experiments, detached research and application modules, and attached research and application modules to derive a set of interface requirements which will support multiple combinations of these elements expected during the modular space station mission. The modular space station project element defines a 6-man orbital program capable of growth to a 12-man orbital program capability. The modular space station project element specification defines the modular space station system, the premission operations support system, the mission operations support system, and the cargo module system and their interfaces.

User participation in the development of the human/computer interface for control centers

NASA Technical Reports Server (NTRS)

Broome, Richard; Quick-Campbell, Marlene; Creegan, James; Dutilly, Robert

1996-01-01

Technological advances coupled with the requirements to reduce operations staffing costs led to the demand for efficient, technologically-sophisticated mission operations control centers. The control center under development for the earth observing system (EOS) is considered. The users are involved in the development of a control center in order to ensure that it is cost-efficient and flexible. A number of measures were implemented in the EOS program in order to encourage user involvement in the area of human-computer interface development. The following user participation exercises carried out in relation to the system analysis and design are described: the shadow participation of the programmers during a day of operations; the flight operations personnel interviews; and the analysis of the flight operations team tasks. The user participation in the interface prototype development, the prototype evaluation, and the system implementation are reported on. The involvement of the users early in the development process enables the requirements to be better understood and the cost to be reduced.

Large Advanced Space Systems (LASS) computer-aided design program additions

NASA Technical Reports Server (NTRS)

Farrell, C. E.

1982-01-01

The LSS preliminary and conceptual design requires extensive iteractive analysis because of the effects of structural, thermal, and control intercoupling. A computer aided design program that will permit integrating and interfacing of required large space system (LSS) analyses is discussed. The primary objective of this program is the implementation of modeling techniques and analysis algorithms that permit interactive design and tradeoff studies of LSS concepts. Eight software modules were added to the program. The existing rigid body controls module was modified to include solar pressure effects. The new model generator modules and appendage synthesizer module are integrated (interfaced) to permit interactive definition and generation of LSS concepts. The mass properties module permits interactive specification of discrete masses and their locations. The other modules permit interactive analysis of orbital transfer requirements, antenna primary beam n, and attitude control requirements.

Common command-and-control user interface for current force UGS

NASA Astrophysics Data System (ADS)

Stolovy, Gary H.

2009-05-01

The Current Force Unattended Ground Sensors (UGS) comprise the OmniSense, Scorpion, and Silent Watch systems. As deployed by U.S. Army Central Command in 2006, sensor reports from the three systems were integrated into a common Graphical User Interface (GUI), with three separate vendor-specific applications for Command-and-Control (C2) functions. This paper describes the requirements, system architecture, implementation, and testing of an upgrade to the Processing, Exploitation, and Dissemination back-end server to incorporate common remote Command-and-Control capabilities.

CLIPS interface development tools and their application

NASA Technical Reports Server (NTRS)

Engel, Bernard A.; Rewerts, Chris C.; Srinivasan, Raghavan; Rogers, Joseph B.; Jones, Don D.

1990-01-01

A package of C-based PC user interface development functions has been developed and integrated into CLIPS. The primary function is ASK which provides a means to ask the user questions via multiple choice menus or the keyboard and then returns the user response to CLIPS. A parameter-like structure supplies information for the interface. Another function, SHOW, provides a means to paginate and display text. A third function, TITLE, formats and displays title screens. A similar set of C-based functions that are more general and thus will run on UNIX and machines have also been developed. Seven expert system applications were transformed from commercial development environments into CLIPS and utilize ASK, SHOW, and TITLE. Development of numerous new expert system applications using CLIPS and these interface functions has started. These functions greatly reduce the time required to build interfaces for CLIPS applications.

Systems engineering implementation in the preliminary design phase of the Giant Magellan Telescope

NASA Astrophysics Data System (ADS)

Maiten, J.; Johns, M.; Trancho, G.; Sawyer, D.; Mady, P.

2012-09-01

Like many telescope projects today, the 24.5-meter Giant Magellan Telescope (GMT) is truly a complex system. The primary and secondary mirrors of the GMT are segmented and actuated to support two operating modes: natural seeing and adaptive optics. GMT is a general-purpose telescope supporting multiple science instruments operated in those modes. GMT is a large, diverse collaboration and development includes geographically distributed teams. The need to implement good systems engineering processes for managing the development of systems like GMT becomes imperative. The management of the requirements flow down from the science requirements to the component level requirements is an inherently difficult task in itself. The interfaces must also be negotiated so that the interactions between subsystems and assemblies are well defined and controlled. This paper will provide an overview of the systems engineering processes and tools implemented for the GMT project during the preliminary design phase. This will include requirements management, documentation and configuration control, interface development and technical risk management. Because of the complexity of the GMT system and the distributed team, using web-accessible tools for collaboration is vital. To accomplish this GMTO has selected three tools: Cognition Cockpit, Xerox Docushare, and Solidworks Enterprise Product Data Management (EPDM). Key to this is the use of Cockpit for managing and documenting the product tree, architecture, error budget, requirements, interfaces, and risks. Additionally, drawing management is accomplished using an EPDM vault. Docushare, a documentation and configuration management tool is used to manage workflow of documents and drawings for the GMT project. These tools electronically facilitate collaboration in real time, enabling the GMT team to track, trace and report on key project metrics and design parameters.

User Working Group Charter

Atmospheric Science Data Center

2014-04-29

... Earth Observing System (EOS) Program through the EOS Data Information System (EOSDIS) Project and the Langley ASDC, located at NASA ... of the ASDC user interface, development of the Information Management System (IMS), and ASDC user conferences requirements for and ...

Performance interface document for users of Tracking and Data Relay Satellite System (TDRSS) electromechanically steered antenna systems (EMSAS)

NASA Technical Reports Server (NTRS)

Hockensmith, R.; Devine, E.; Digiacomo, M.; Hager, F.; Moss, R.

1983-01-01

Satellites that use the NASA Tracking and Data Relay Satellite System (TDRSS) require antennas that are crucial for performing and achieving reliable TDRSS link performance at the desired data rate. Technical guidelines are presented to assist the prospective TDRSS medium-and high-data rate user in selecting and procuring a viable, steerable high-gain antenna system. Topics addressed include the antenna gain/transmitter power/data rate relationship; Earth power flux-density limitations; electromechanical requirements dictated by the small beam widths, desired angular coverage, and minimal torque disturbance to the spacecraft; weight and moment considerations; mechanical, electrical and thermal interfaces; design lifetime failure modes; and handling and storage. Proven designs are cited and space-qualified assemblies and components are identified.

Data management system CIU and DIU. Appendix A: CIU and DIU schematics

NASA Technical Reports Server (NTRS)

1975-01-01

The Computer Interface Unit (CIU) and the Data Interface Unit (DIU) of the Data Management System (DMS) were described as to their functional location, purpose and function. This describes the CIU and DIU at the unit level illustrating their interface thru the Data Bus (DBUS) and to other DMS units. All unit level interfaces are defined as to function and characteristics. The controls, indicators, test points and connectors are listed and function, location and application are described for each. The mechanical configuration is defined and illustrated to provide card and component location for modification or repair purposes. Unique disassembly and assembly requirements are outlined where applicable. A unit internal functional block diagram level description is provided.

Automatic programming of simulation models

NASA Technical Reports Server (NTRS)

Schroer, Bernard J.; Tseng, Fan T.; Zhang, Shou X.; Dwan, Wen S.

1990-01-01

The concepts of software engineering were used to improve the simulation modeling environment. Emphasis was placed on the application of an element of rapid prototyping, or automatic programming, to assist the modeler define the problem specification. Then, once the problem specification has been defined, an automatic code generator is used to write the simulation code. The following two domains were selected for evaluating the concepts of software engineering for discrete event simulation: manufacturing domain and a spacecraft countdown network sequence. The specific tasks were to: (1) define the software requirements for a graphical user interface to the Automatic Manufacturing Programming System (AMPS) system; (2) develop a graphical user interface for AMPS; and (3) compare the AMPS graphical interface with the AMPS interactive user interface.

Earth Observatory Satellite system definition study. Report no. 2: Instrument constraints and interface specifications

NASA Technical Reports Server (NTRS)

1974-01-01

The instruments to be flown on the Earth Observatory Satellite (EOS) system are defined. The instruments will be used to support the Land Resources Management (LRM) mission of the EOS. Program planning information and suggested acquisition activities for obtaining the instruments are presented. The subjects considered are as follows: (1) the performance and interface of the Thematic Mapper (TM) and the High Resolution Pointing Imager (HRPI), (2) procedure for interfacing the TM and HRPI with the EOS satellite, (3) a space vehicle integration plan suggesting the steps and sequence of events required to carry out the interface activities, and (4) suggested agreements between the contractors for providing timely and equitable solution of problems at minimum cost.

Modular Integrated Stackable Layers (MISL) 1.1 Design Specification. Design Guideline Document

NASA Technical Reports Server (NTRS)

Yim, Hester J.

2012-01-01

This document establishes the design guideline of the Modular Instrumentation Data Acquisition (MI-DAQ) system in utilization of several designs available in EV. The MI- DAQ provides the options to the customers depending on their system requirements i.e. a 28V interface power supply, a low power battery operated system, a low power microcontroller, a higher performance microcontroller, a USB interface, a Ethernet interface, a wireless communication, various sensor interfaces, etc. Depending on customer's requirements, the each functional board can be stacked up from a bottom level of power supply to a higher level of stack to provide user interfaces. The stack up of boards are accomplished by a predefined and standardized power bus and data bus connections which are included in this document along with other physical and electrical guidelines. This guideline also provides information for a new design options. This specification is the product of a collaboration between NASA/JSC/EV and Texas A&M University. The goal of the collaboration is to open source the specification and allow outside entities to design, build, and market modules that are compatible with the specification. NASA has designed and is using numerous modules that are compatible to this specification. A limited number of these modules will also be released as open source designs to support the collaboration. The released designs are listed in the Applicable Documents.

Introduction of knowledge bases in patient's data management system: role of the user interface.

PubMed

Chambrin, M C; Ravaux, P; Jaborska, A; Beugnet, C; Lestavel, P; Chopin, C; Boniface, M

1995-02-01

As the number of signals and data to be handled grows in intensive care unit, it is necessary to design more powerful computing systems that integrate and summarize all this information. The manual input of data as e.g. clinical signs and drug prescription and the synthetic representation of these data requires an ever more sophisticated user interface. The introduction of knowledge bases in the data management allows to conceive contextual interfaces. The objective of this paper is to show the importance of the design of the user interface, in the daily use of clinical information system. Then we describe a methodology that uses the man-machine interaction to capture the clinician knowledge during the clinical practice. The different steps are the audit of the user's actions, the elaboration of statistic models allowing the definition of new knowledge, and the validation that is performed before complete integration. A part of this knowledge can be used to improve the user interface. Finally, we describe the implementation of these concepts on a UNIX platform using OSF/MOTIF graphical interface.

A Hybrid 2D/3D User Interface for Radiological Diagnosis.

PubMed

Mandalika, Veera Bhadra Harish; Chernoglazov, Alexander I; Billinghurst, Mark; Bartneck, Christoph; Hurrell, Michael A; Ruiter, Niels de; Butler, Anthony P H; Butler, Philip H

2018-02-01

This paper presents a novel 2D/3D desktop virtual reality hybrid user interface for radiology that focuses on improving 3D manipulation required in some diagnostic tasks. An evaluation of our system revealed that our hybrid interface is more efficient for novice users and more accurate for both novice and experienced users when compared to traditional 2D only interfaces. This is a significant finding because it indicates, as the techniques mature, that hybrid interfaces can provide significant benefit to image evaluation. Our hybrid system combines a zSpace stereoscopic display with 2D displays, and mouse and keyboard input. It allows the use of 2D and 3D components interchangeably, or simultaneously. The system was evaluated against a 2D only interface with a user study that involved performing a scoliosis diagnosis task. There were two user groups: medical students and radiology residents. We found improvements in completion time for medical students, and in accuracy for both groups. In particular, the accuracy of medical students improved to match that of the residents.

Enhancing the Human Factors Engineering Role in an Austere Fiscal Environment

NASA Technical Reports Server (NTRS)

Stokes, Jack W.

2003-01-01

An austere fiscal environment in the aerospace community creates pressures to reduce program costs, often minimizing or sometimes even deleting the human interface requirements from the design process. With an assumption that the flight crew can recover real time from a poorly human factored space vehicle design, the classical crew interface requirements have been either not included in the design or not properly funded, though carried as requirements. Cost cuts have also affected quality of retained human factors engineering personnel. In response to this concern, planning is ongoing to correct the acting issues. Herein are techniques for ensuring that human interface requirements are integrated into a flight design, from proposal through verification and launch activation. This includes human factors requirements refinement and consolidation across flight programs; keyword phrases in the proposals; closer ties with systems engineering and other classical disciplines; early planning for crew-interface verification; and an Agency integrated human factors verification program, under the One NASA theme. Importance is given to communication within the aerospace human factors discipline, and utilizing the strengths of all government, industry, and academic human factors organizations in an unified research and engineering approach. A list of recommendations and concerns are provided in closing.

Research and implementation on improving I/O performance of streaming media storage system

NASA Astrophysics Data System (ADS)

Lu, Zheng-wu; Wang, Yu-de; Jiang, Guo-song

2008-12-01

In this paper, we study the special requirements of a special storage system: streaming media server, and propose a solution to improve I/O performance of RAID storage system. The solution is suitable for streaming media applications. A streaming media storage subsystem includes the I/O interfaces, RAID arrays, I/O scheduling and device drivers. The solution is implemented on the top of the storage subsystem I/O Interface. Storage subsystem is the performance bottlenecks of a streaming media system, and I/O interface directly affect the performance of the storage subsystem. According to theoretical analysis, 64 KB block-size is most appropriate for streaming media applications. We carry out experiment in detail, and verified that the proper block-size really is 64KB. It is in accordance with our analysis. The experiment results also show that by using DMA controller, efficient memory management technology and mailbox interface design mechanism, streaming media storage system achieves a high-speed data throughput.

A Robotics Systems Design Need: A Design Standard to Provide the Systems Focus that is Required for Longterm Exploration Efforts

NASA Technical Reports Server (NTRS)

Dischinger, H. Charles., Jr.; Mullins, Jeffrey B.

2005-01-01

The United States is entering a new period of human exploration of the inner Solar System, and robotic human helpers will be partners in that effort. In order to support integration of these new worker robots into existing and new human systems, a new design standard should be developed, to be called the Robot-Systems Integration Standard (RSIS). It will address the requirements for and constraints upon robotic collaborators with humans. These workers are subject to the same functional constraints as humans of work, reach, and visibility/situational awareness envelopes, and they will deal with the same maintenance and communication interfaces. Thus, the RSIS will be created by discipline experts with the same sort of perspective on these and other interface concerns as human engineers.

Man-systems distributed system for Space Station Freedom

NASA Technical Reports Server (NTRS)

Lewis, J. L.

1990-01-01

Viewgraphs on man-systems distributed system for Space Station Freedom are presented. Topics addressed include: description of man-systems (definition, requirements, scope, subsystems, and topologies); implementation (approach, tools); man-systems interfaces (system to element and system to system); prime/supporting development relationship; selected accomplishments; and technical challenges.

Knowledge-based control of an adaptive interface

NASA Technical Reports Server (NTRS)

Lachman, Roy

1989-01-01

The analysis, development strategy, and preliminary design for an intelligent, adaptive interface is reported. The design philosophy couples knowledge-based system technology with standard human factors approaches to interface development for computer workstations. An expert system has been designed to drive the interface for application software. The intelligent interface will be linked to application packages, one at a time, that are planned for multiple-application workstations aboard Space Station Freedom. Current requirements call for most Space Station activities to be conducted at the workstation consoles. One set of activities will consist of standard data management services (DMS). DMS software includes text processing, spreadsheets, data base management, etc. Text processing was selected for the first intelligent interface prototype because text-processing software can be developed initially as fully functional but limited with a small set of commands. The program's complexity then can be increased incrementally. The intelligent interface includes the operator's behavior and three types of instructions to the underlying application software are included in the rule base. A conventional expert-system inference engine searches the data base for antecedents to rules and sends the consequents of fired rules as commands to the underlying software. Plans for putting the expert system on top of a second application, a database management system, will be carried out following behavioral research on the first application. The intelligent interface design is suitable for use with ground-based workstations now common in government, industrial, and educational organizations.

MaROS Strategic Relay Planning and Coordination Interfaces

NASA Technical Reports Server (NTRS)

Allard, Daniel A.

2010-01-01

The Mars Relay Operations Service (MaROS) is designed to provide planning and analysis tools in support of ongoing Mars Network relay operations. Strategic relay planning requires coordination between lander and orbiter mission ground data system (GDS) teams to schedule and execute relay communications passes. MaROS centralizes this process, correlating all data relevant to relay coordination to provide a cohesive picture of the relay state. Service users interact with the system through thin-layer command line and web user interface client applications. Users provide and utilize data such as lander view periods of orbiters, Deep Space Network (DSN) antenna tracks, and reports of relay pass performance. Users upload and download relevant relay data via formally defined and documented file structures including some described in Extensible Markup Language (XML). Clients interface with the system via an http-based Representational State Transfer (ReST) pattern using Javascript Object Notation (JSON) formats. This paper will provide a general overview of the service architecture and detail the software interfaces and considerations for interface design.

36 CFR 1234.34 - When may NARA conduct an inspection of a records storage facility?

Code of Federal Regulations, 2010 CFR

2010-07-01

....) Required. Entrances/Exits: X-ray & magnetometer at public entrances Recommended. Require x-ray screening of... design requirements, (e.g. fire detection, fire suppression systems, etc.) Entrances/Exits X-Ray and... would focus on tenant agencies, public interface, and feasibility. Required for Level V. Require X-Ray...

36 CFR 1234.34 - When may NARA conduct an inspection of a records storage facility?

Code of Federal Regulations, 2011 CFR

2011-07-01

....) Required. Entrances/Exits: X-ray & magnetometer at public entrances Recommended. Require x-ray screening of... design requirements, (e.g. fire detection, fire suppression systems, etc.) Entrances/Exits X-Ray and... would focus on tenant agencies, public interface, and feasibility. Required for Level V. Require X-Ray...

A Primer for Telemetry Interfacing in Accordance with NASA Standards Using Low Cost FPGAs

NASA Astrophysics Data System (ADS)

McCoy, Jake; Schultz, Ted; Tutt, James; Rogers, Thomas; Miles, Drew; McEntaffer, Randall

2016-03-01

Photon counting detector systems on sounding rocket payloads often require interfacing asynchronous outputs with a synchronously clocked telemetry (TM) stream. Though this can be handled with an on-board computer, there are several low cost alternatives including custom hardware, microcontrollers and field-programmable gate arrays (FPGAs). This paper outlines how a TM interface (TMIF) for detectors on a sounding rocket with asynchronous parallel digital output can be implemented using low cost FPGAs and minimal custom hardware. Low power consumption and high speed FPGAs are available as commercial off-the-shelf (COTS) products and can be used to develop the main component of the TMIF. Then, only a small amount of additional hardware is required for signal buffering and level translating. This paper also discusses how this system can be tested with a simulated TM chain in the small laboratory setting using FPGAs and COTS specialized data acquisition products.

A Multi-purpose Brain-Computer Interface Output Device

PubMed Central

Thompson, David E; Huggins, Jane E

2012-01-01

While brain-computer interfaces (BCIs) are a promising alternative access pathway for individuals with severe motor impairments, many BCI systems are designed as standalone communication and control systems, rather than as interfaces to existing systems built for these purposes. While an individual communication and control system may be powerful or flexible, no single system can compete with the variety of options available in the commercial assistive technology (AT) market. BCIs could instead be used as an interface to these existing AT devices and products, which are designed for improving access and agency of people with disabilities and are highly configurable to individual user needs. However, interfacing with each AT device and program requires significant time and effort on the part of researchers and clinicians. This work presents the Multi-Purpose BCI Output Device (MBOD), a tool to help researchers and clinicians provide BCI control of many forms of AT in a plug-and-play fashion, i.e. without the installation of drivers or software on the AT device, and a proof-of-concept of the practicality of such an approach. The MBOD was designed to meet the goals of target device compatibility, BCI input device compatibility, convenience, and intuitive command structure. The MBOD was successfully used to interface a BCI with multiple AT devices (including two wheelchair seating systems), as well as computers running Windows (XP and 7), Mac and Ubuntu Linux operating systems. PMID:22208120

A multi-purpose brain-computer interface output device.

PubMed

Thompson, David E; Huggins, Jane E

2011-10-01

While brain-computer interfaces (BCIs) are a promising alternative access pathway for individuals with severe motor impairments, many BCI systems are designed as stand-alone communication and control systems, rather than as interfaces to existing systems built for these purposes. An individual communication and control system may be powerful or flexible, but no single system can compete with the variety of options available in the commercial assistive technology (AT) market. BCls could instead be used as an interface to these existing AT devices and products, which are designed for improving access and agency of people with disabilities and are highly configurable to individual user needs. However, interfacing with each AT device and program requires significant time and effort on the part of researchers and clinicians. This work presents the Multi-Purpose BCI Output Device (MBOD), a tool to help researchers and clinicians provide BCI control of many forms of AT in a plug-and-play fashion, i.e., without the installation of drivers or software on the AT device, and a proof-of-concept of the practicality of such an approach. The MBOD was designed to meet the goals of target device compatibility, BCI input device compatibility, convenience, and intuitive command structure. The MBOD was successfully used to interface a BCI with multiple AT devices (including two wheelchair seating systems), as well as computers running Windows (XP and 7), Mac and Ubuntu Linux operating systems.

Next Gen One Portal Usability Evaluation

NASA Technical Reports Server (NTRS)

Cross, E. V., III; Perera, J. S.; Hanson, A. M.; English, K.; Vu, L.; Amonette, W.

2018-01-01

Each exercise device on the International Space Station (ISS) has a unique, customized software system interface with unique layouts / hierarchy, and operational principles that require significant crew training. Furthermore, the software programs are not adaptable and provide no real-time feedback or motivation to enhance the exercise experience and/or prevent injuries. Additionally, the graphical user interfaces (GUI) of these systems present information through multiple layers resulting in difficulty navigating to the desired screens and functions. These limitations of current exercise device GUI's lead to increased crew time spent on initiating, loading, performing exercises, logging data and exiting the system. To address these limitations a Next Generation One Portal (NextGen One Portal) Crew Countermeasure System (CMS) was developed, which utilizes the latest industry guidelines in GUI designs to provide an intuitive ease of use approach (i.e., 80% of the functionality gained within 5-10 minutes of initial use without/limited formal training required). This is accomplished by providing a consistent interface using common software to reduce crew training, increase efficiency & user satisfaction while also reducing development & maintenance costs. Results from the usability evaluations showed the NextGen One Portal UI having greater efficiency, learnability, memorability, usability and overall user experience than the current Advanced Resistive Exercise Device (ARED) UI used by astronauts on ISS. Specifically, the design of the One-Portal UI as an app interface similar to those found on the Apple and Google's App Store, assisted many of the participants in grasping the concepts of the interface with minimum training. Although the NextGen One-Portal UI was shown to be an overall better interface, observations by the test facilitators noted specific exercise tasks appeared to have a significant impact on the NextGen One-Portal UI efficiency. Future updates to the NextGen One Portal UI will address these inefficiencies.

On the utility of 3D hand cursors to explore medical volume datasets with a touchless interface.

PubMed

Lopes, Daniel Simões; Parreira, Pedro Duarte de Figueiredo; Paulo, Soraia Figueiredo; Nunes, Vitor; Rego, Paulo Amaral; Neves, Manuel Cassiano; Rodrigues, Pedro Silva; Jorge, Joaquim Armando

2017-08-01

Analyzing medical volume datasets requires interactive visualization so that users can extract anatomo-physiological information in real-time. Conventional volume rendering systems rely on 2D input devices, such as mice and keyboards, which are known to hamper 3D analysis as users often struggle to obtain the desired orientation that is only achieved after several attempts. In this paper, we address which 3D analysis tools are better performed with 3D hand cursors operating on a touchless interface comparatively to a 2D input devices running on a conventional WIMP interface. The main goals of this paper are to explore the capabilities of (simple) hand gestures to facilitate sterile manipulation of 3D medical data on a touchless interface, without resorting on wearables, and to evaluate the surgical feasibility of the proposed interface next to senior surgeons (N=5) and interns (N=2). To this end, we developed a touchless interface controlled via hand gestures and body postures to rapidly rotate and position medical volume images in three-dimensions, where each hand acts as an interactive 3D cursor. User studies were conducted with laypeople, while informal evaluation sessions were carried with senior surgeons, radiologists and professional biomedical engineers. Results demonstrate its usability as the proposed touchless interface improves spatial awareness and a more fluent interaction with the 3D volume than with traditional 2D input devices, as it requires lesser number of attempts to achieve the desired orientation by avoiding the composition of several cumulative rotations, which is typically necessary in WIMP interfaces. However, tasks requiring precision such as clipping plane visualization and tagging are best performed with mouse-based systems due to noise, incorrect gestures detection and problems in skeleton tracking that need to be addressed before tests in real medical environments might be performed. Copyright © 2017 Elsevier Inc. All rights reserved.

System analysis study of space platform and station accommodations for life sciences research facilities. Volume 2: Study results. Appendix D: Life sciences research facility requirements

NASA Technical Reports Server (NTRS)

Wiley, Lowell F.

1985-01-01

The purpose of this requirements document is to develop the foundation for concept development for the Life Sciences Research Facility (LSRF) on the Space Station. These requirements are developed from the perspective of a Space Station laboratory module outfitter. Science and mission requirements including those related to specimens are set forth. System requirements, including those for support, are detailed. Functional and design requirements are covered in the areas of structures, mechanisms, electrical power, thermal systems, data management system, life support, and habitability. Finally, interface requirements for the Command Module and Logistics Module are described.

Human respiratory considerations for civil transport aircraft oxygen system.

DOT National Transportation Integrated Search

1978-01-01

This report is intended to acquaint personnel involved in the design, inspection, and maintenance of civil transport oxygen systems with the human respiratory requirements and oxygen system design considerations necessary to effect an interface and p...

Multi-Modal Traveler Information System - Gateway Interface Control Requirements

DOT National Transportation Integrated Search

1997-10-30

The Multi-Modal Traveler Information System (MMTIS) project involves a large number of Intelligent Transportation System (ITS) related tasks. It involves research of all ITS initiatives in the Gary-Chicago-Milwaukee (GCM) Corridor which are currently...

Handling of the demilitarized zone using service providers in SAP

NASA Astrophysics Data System (ADS)

Iovan, A.; Robu, R.

2016-02-01

External collaboration needs to allow data access from the Internet. In a trusted Internet collaboration scenario where the external user works on the same data like the internal user direct access to the data in the Intranet is required. The paper presents a solution to get access to certain data in the Enterprise Resource Planning system, having the User Interface on a system in the Demilitarized Zone and the database on a system which is located in the trusted area. Using the Service Provider Interface framework, connections between separate systems can be created in different areas of the network. The paper demonstrates how to connect the two systems, one in the Demilitarized Zone and one in the trusted area, using SAP ERP 6.0 with Enhancement Package 7. In order to use the Service Provider Interface SAP Business Suite Foundation component must be installed in both systems. The advantage of using the Service Provider Interface framework is that the external user works on the same data like the internal user (and not on copies). This assures data consistency and less overhead for backup and security systems.

DRS: Derivational Reasoning System

NASA Technical Reports Server (NTRS)

Bose, Bhaskar

1995-01-01

The high reliability requirements for airborne systems requires fault-tolerant architectures to address failures in the presence of physical faults, and the elimination of design flaws during the specification and validation phase of the design cycle. Although much progress has been made in developing methods to address physical faults, design flaws remain a serious problem. Formal methods provides a mathematical basis for removing design flaws from digital systems. DRS (Derivational Reasoning System) is a formal design tool based on advanced research in mathematical modeling and formal synthesis. The system implements a basic design algebra for synthesizing digital circuit descriptions from high level functional specifications. DRS incorporates an executable specification language, a set of correctness preserving transformations, verification interface, and a logic synthesis interface, making it a powerful tool for realizing hardware from abstract specifications. DRS integrates recent advances in transformational reasoning, automated theorem proving and high-level CAD synthesis systems in order to provide enhanced reliability in designs with reduced time and cost.

14 CFR 417.409 - System hazard controls.

Code of Federal Regulations, 2012 CFR

2012-01-01

... hazard as identified by the ground safety analysis and satisfy the requirements of this section. A launch... electrical power and signal circuits that interface with hazardous subsystems. (e) Propulsion systems. A...

14 CFR 417.409 - System hazard controls.

Code of Federal Regulations, 2013 CFR

2013-01-01

... hazard as identified by the ground safety analysis and satisfy the requirements of this section. A launch... electrical power and signal circuits that interface with hazardous subsystems. (e) Propulsion systems. A...

14 CFR 417.409 - System hazard controls.

Code of Federal Regulations, 2014 CFR

2014-01-01

... hazard as identified by the ground safety analysis and satisfy the requirements of this section. A launch... electrical power and signal circuits that interface with hazardous subsystems. (e) Propulsion systems. A...

14 CFR 417.409 - System hazard controls.

Code of Federal Regulations, 2011 CFR

2011-01-01

... hazard as identified by the ground safety analysis and satisfy the requirements of this section. A launch... electrical power and signal circuits that interface with hazardous subsystems. (e) Propulsion systems. A...

Intelligent user interface concept for space station

NASA Technical Reports Server (NTRS)

Comer, Edward; Donaldson, Cameron; Bailey, Elizabeth; Gilroy, Kathleen

1986-01-01

The space station computing system must interface with a wide variety of users, from highly skilled operations personnel to payload specialists from all over the world. The interface must accommodate a wide variety of operations from the space platform, ground control centers and from remote sites. As a result, there is a need for a robust, highly configurable and portable user interface that can accommodate the various space station missions. The concept of an intelligent user interface executive, written in Ada, that would support a number of advanced human interaction techniques, such as windowing, icons, color graphics, animation, and natural language processing is presented. The user interface would provide intelligent interaction by understanding the various user roles, the operations and mission, the current state of the environment and the current working context of the users. In addition, the intelligent user interface executive must be supported by a set of tools that would allow the executive to be easily configured and to allow rapid prototyping of proposed user dialogs. This capability would allow human engineering specialists acting in the role of dialog authors to define and validate various user scenarios. The set of tools required to support development of this intelligent human interface capability is discussed and the prototyping and validation efforts required for development of the Space Station's user interface are outlined.

Systems Engineering Model and Training Application for Desktop Environment

NASA Technical Reports Server (NTRS)

May, Jeffrey T.

2010-01-01

Provide a graphical user interface based simulator for desktop training, operations and procedure development and system reference. This simulator allows for engineers to train and further understand the dynamics of their system from their local desktops. It allows the users to train and evaluate their system at a pace and skill level based on the user's competency and from a perspective based on the user's need. The simulator will not require any special resources to execute and should generally be available for use. The interface is based on a concept of presenting the model of the system in ways that best suits the user's application or training needs. The three levels of views are Component View, the System View (overall system), and the Console View (monitor). These views are portals into a single model, so changing the model from one view or from a model manager Graphical User Interface will be reflected on all other views.

Processing eutectics in space

NASA Technical Reports Server (NTRS)

Douglas, F. C.; Galasso, F. S.

1974-01-01

Experimental work is reported which was directed toward obtaining interface shape control while a numerical thermal analysis program was being made operational. An experimental system was developed in which the solid-liquid interface in a directionally solidified aluminum-nickel eutectic could be made either concave to the melt or convex to the melt. This experimental system provides control over the solid-liquid interface shape and can be used to study the effect of such control on the microstructure. The SINDA thermal analysis program, obtained from Marshall Space Flight Center, was used to evaluate experimental directional solidification systems for the aluminum-nickel and the aluminum-copper eutectics. This program was applied to a three-dimensional ingot, and was used to calculate the thermal profiles in axisymmetric heat flow. The results show that solid-liquid interface shape control can be attained with physically realizable thermal configurations and the magnitudes of the required thermal inputs were indicated.

Rodent wearable ultrasound system for wireless neural recording.

PubMed

Piech, David K; Kay, Joshua E; Boser, Bernhard E; Maharbiz, Michel M

2017-07-01

Advances in minimally-invasive, distributed biological interface nodes enable possibilities for networks of sensors and actuators to connect the brain with external devices. The recent development of the neural dust sensor mote has shown that utilizing ultrasound backscatter communication enables untethered sub-mm neural recording devices. These implanted sensor motes require a wearable external ultrasound interrogation device to enable in-vivo, freely-behaving neural interface experiments. However, minimizing the complexity and size of the implanted sensors shifts the power and processing burden to the external interrogator. In this paper, we present an ultrasound backscatter interrogator that supports real-time backscatter processing in a rodent-wearable, completely wireless device. We demonstrate a generic digital encoding scheme which is intended for transmitting neural information. The system integrates a front-end ultrasonic interface ASIC with off-the-shelf components to enable a highly compact ultrasound interrogation device intended for rodent neural interface experiments but applicable to other model systems.

Electro-mechanical probe positioning system for large volume plasma device

NASA Astrophysics Data System (ADS)

Sanyasi, A. K.; Sugandhi, R.; Srivastava, P. K.; Srivastav, Prabhakar; Awasthi, L. M.

2018-05-01

An automated electro-mechanical system for the positioning of plasma diagnostics has been designed and implemented in a Large Volume Plasma Device (LVPD). The system consists of 12 electro-mechanical assemblies, which are orchestrated using the Modbus communication protocol on 4-wire RS485 communications to meet the experimental requirements. Each assembly has a lead screw-based mechanical structure, Wilson feed-through-based vacuum interface, bipolar stepper motor, micro-controller-based stepper drive, and optical encoder for online positioning correction of probes. The novelty of the system lies in the orchestration of multiple drives on a single interface, fabrication and installation of the system for a large experimental device like the LVPD, in-house developed software, and adopted architectural practices. The paper discusses the design, description of hardware and software interfaces, and performance results in LVPD.

A Novel Passive Robotic Tool Interface

NASA Astrophysics Data System (ADS)

Roberts, Paul

2013-09-01

The increased capability of space robotics has seen their uses increase from simple sample gathering and mechanical adjuncts to humans, to sophisticated multi- purpose investigative and maintenance tools that substitute for humans for many external space tasks. As with all space missions, reducing mass and system complexity is critical. A key component of robotic systems mass and complexity is the number of motors and actuators needed. MDA has developed a passive tool interface that, like a household power drill, permits a single tool actuator to be interfaced with many Tool Tips without requiring additional actuators to manage the changing and storage of these tools. MDA's Multifunction Tool interface permits a wide range of Tool Tips to be designed to a single interface that can be pre-qualified to torque and strength limits such that additional Tool Tips can be added to a mission's "tool kit" simply and quickly.

Development and evaluation of nursing user interface screens using multiple methods.

PubMed

Hyun, Sookyung; Johnson, Stephen B; Stetson, Peter D; Bakken, Suzanne

2009-12-01

Building upon the foundation of the Structured Narrative Electronic Health Record (EHR) model, we applied theory-based (combined Technology Acceptance Model and Task-Technology Fit Model) and user-centered methods to explore nurses' perceptions of functional requirements for an electronic nursing documentation system, design user interface screens reflective of the nurses' perspectives, and assess nurses' perceptions of the usability of the prototype user interface screens. The methods resulted in user interface screens that were perceived to be easy to use, potentially useful, and well-matched to nursing documentation tasks associated with Nursing Admission Assessment, Blood Administration, and Nursing Discharge Summary. The methods applied in this research may serve as a guide for others wishing to implement user-centered processes to develop or extend EHR systems. In addition, some of the insights obtained in this study may be informative to the development of safe and efficient user interface screens for nursing document templates in EHRs.

A bidirectional ACR-NEMA interface between the VA's DHCP Integrated Imaging System and the Siemens-Loral PACS.

PubMed Central

Kuzmak, P. M.; Dayhoff, R. E.

1992-01-01

There is a wide range of requirements for digital hospital imaging systems. Radiology needs very high resolution black and white images. Other diagnostic disciplines need high resolution color imaging capabilities. Images need to be displayed in many locations throughout the hospital. Different imaging systems within a hospital need to cooperate in order to show the whole picture. At the Baltimore VA Medical Center, the DHCP Integrated Imaging System and a commercial Picture Archiving and Communication System (PACS) work in concert to provide a wide-range of departmental and hospital-wide imaging capabilities. An interface between the DHCP and the Siemens-Loral PACS systems enables patient text and image data to be passed between the two systems. The interface uses ACR-NEMA 2.0 Standard messages extended with shadow groups based on draft ACR-NEMA 3.0 prototypes. A Novell file server, accessible to both systems via Ethernet, is used to communicate all the messages. Patient identification information, orders, ADT, procedure status, changes, patient reports, and images are sent between the two systems across the interface. The systems together provide an extensive set of imaging capabilities for both the specialist and the general practitioner. PMID:1482906

A bidirectional ACR-NEMA interface between the VA's DHCP Integrated Imaging System and the Siemens-Loral PACS.

PubMed

Kuzmak, P M; Dayhoff, R E

1992-01-01

There is a wide range of requirements for digital hospital imaging systems. Radiology needs very high resolution black and white images. Other diagnostic disciplines need high resolution color imaging capabilities. Images need to be displayed in many locations throughout the hospital. Different imaging systems within a hospital need to cooperate in order to show the whole picture. At the Baltimore VA Medical Center, the DHCP Integrated Imaging System and a commercial Picture Archiving and Communication System (PACS) work in concert to provide a wide-range of departmental and hospital-wide imaging capabilities. An interface between the DHCP and the Siemens-Loral PACS systems enables patient text and image data to be passed between the two systems. The interface uses ACR-NEMA 2.0 Standard messages extended with shadow groups based on draft ACR-NEMA 3.0 prototypes. A Novell file server, accessible to both systems via Ethernet, is used to communicate all the messages. Patient identification information, orders, ADT, procedure status, changes, patient reports, and images are sent between the two systems across the interface. The systems together provide an extensive set of imaging capabilities for both the specialist and the general practitioner.

Multiple IMU system hardware interface design, volume 2

NASA Technical Reports Server (NTRS)

Landey, M.; Brown, D.

1975-01-01

The design of each system component is described. Emphasis is placed on functional requirements unique in this system, including data bus communication, data bus transmitters and receivers, and ternary-to-binary torquing decision logic. Mechanization drawings are presented.

Multi-Modal Traveler Information System - GCM Corridor Architecture Interface Control Requirements

DOT National Transportation Integrated Search

1997-10-31

The Multi-Modal Traveler Information System (MMTIS) project involves a large number of Intelligent Transportation System (ITS) related tasks. It involves research of all ITS initiatives in the Gary-Chicago-Milwaukee (GCM) Corridor which are currently...

Human Factors Design Of Automated Highway Systems: Scenario Definition

DOT National Transportation Integrated Search

1995-09-01

Attention to driver acceptance and performance issues during system design will be key to the success of the Automated Highway System (AHS). A first step in the process of defining driver roles and driver-system interface requirements of AHS is the d...

Collaborative engineering and design management for the Hobby-Eberly Telescope tracker upgrade

NASA Astrophysics Data System (ADS)

Mollison, Nicholas T.; Hayes, Richard J.; Good, John M.; Booth, John A.; Savage, Richard D.; Jackson, John R.; Rafal, Marc D.; Beno, Joseph H.

2010-07-01

The engineering and design of systems as complex as the Hobby-Eberly Telescope's* new tracker require that multiple tasks be executed in parallel and overlapping efforts. When the design of individual subsystems is distributed among multiple organizations, teams, and individuals, challenges can arise with respect to managing design productivity and coordinating successful collaborative exchanges. This paper focuses on design management issues and current practices for the tracker design portion of the Hobby-Eberly Telescope Wide Field Upgrade project. The scope of the tracker upgrade requires engineering contributions and input from numerous fields including optics, instrumentation, electromechanics, software controls engineering, and site-operations. Successful system-level integration of tracker subsystems and interfaces is critical to the telescope's ultimate performance in astronomical observation. Software and process controls for design information and workflow management have been implemented to assist the collaborative transfer of tracker design data. The tracker system architecture and selection of subsystem interfaces has also proven to be a determining factor in design task formulation and team communication needs. Interface controls and requirements change controls will be discussed, and critical team interactions are recounted (a group-participation Failure Modes and Effects Analysis [FMEA] is one of special interest). This paper will be of interest to engineers, designers, and managers engaging in multi-disciplinary and parallel engineering projects that require coordination among multiple individuals, teams, and organizations.

Gary-Chicago-Milwaukee corridor : corridor transportation information center : system glossary

DOT National Transportation Integrated Search

1995-10-30

The following definitions, abbreviations and acronyms are generated from the : System Definition Document (Document #9931.GCM), the Interface Control : Specification (Document #9932.GCM), and the Requirements Specification (Document : #9933.GCM). The...

The role of man in flight experiment payload missions. Volume 2: Appendices

NASA Technical Reports Server (NTRS)

Malone, T. B.

1973-01-01

In the study to determine the role of man in Sortie Lab operations, a functional model of a generalized experiment system was developed. The results are presented of a requirements analysis which was conducted to identify performance requirements, information requirements, and interface requirements associated with each function in the model.

Payload transportation system study

NASA Technical Reports Server (NTRS)

1976-01-01

A standard size set of shuttle payload transportation equipment was defined that will substantially reduce the cost of payload transportation and accommodate a wide range of payloads with minimum impact on payload design. The system was designed to accommodate payload shipments between the level 4 payload integration sites and the launch site during the calendar years 1979-1982. In addition to defining transportation multi-use mission support equipment (T-MMSE) the mode of travel, prime movers, and ancillary equipment required in the transportation process were also considered. Consistent with the STS goals of low cost and the use of standardized interfaces, the transportation system was designed to commercial grade standards and uses the payload flight mounting interfaces for transportation. The technical, cost, and programmatic data required to permit selection of a baseline system of MMSE for intersite movement of shuttle payloads were developed.

Ver-i-Fus: an integrated access control and information monitoring and management system

NASA Astrophysics Data System (ADS)

Thomopoulos, Stelios C.; Reisman, James G.; Papelis, Yiannis E.

1997-01-01

This paper describes the Ver-i-Fus Integrated Access Control and Information Monitoring and Management (IAC-I2M) system that INTELNET Inc. has developed. The Ver-i-Fus IAC-I2M system has been designed to meet the most stringent security and information monitoring requirements while allowing two- way communication between the user and the system. The systems offers a flexible interface that permits to integrate practically any sensing device, or combination of sensing devices, including a live-scan fingerprint reader, thus providing biometrics verification for enhanced security. Different configurations of the system provide solutions to different sets of access control problems. The re-configurable hardware interface, tied together with biometrics verification and a flexible interface that allows to integrate Ver-i-Fus with an MIS, provide an integrated solution to security, time and attendance, labor monitoring, production monitoring, and payroll applications.

MiRTE: Mixed Reality Triage and Evacuation game for Mass Casualty information systems design, testing and training.

PubMed

Yu, Xunyi; Ganz, Aura

2011-01-01

In this paper we introduce a Mixed Reality Triage and Evacuation game, MiRTE, that is used in the development, testing and training of Mass Casualty Incident (MCI) information systems for first responders. Using the Source game engine from Valve software, MiRTE creates immersive virtual environments to simulate various incident scenarios, and enables interactions between multiple players/first responders. What distinguishes it from a pure computer simulation game is that it can interface with external mass casualty incident management systems, such as DIORAMA. The game will enable system developers to specify technical requirements of underlying technology, and test different alternatives of design. After the information system hardware and software are completed, the game can simulate various algorithms such as localization technologies, and interface with an actual user interface on PCs and Smartphones. We implemented and tested the game with the DIORAMA system.

Interfacing An Intelligent Decision-Maker To A Real-Time Control System

NASA Astrophysics Data System (ADS)

Evers, D. C.; Smith, D. M.; Staros, C. J.

1984-06-01

This paper discusses some of the practical aspects of implementing expert systems in a real-time environment. There is a conflict between the needs of a process control system and the computational load imposed by intelligent decision-making software. The computation required to manage a real-time control problem is primarily concerned with routine calculations which must be executed in real time. On most current hardware, non-trivial AI software should not be forced to operate under real-time constraints. In order for the system to work efficiently, the two processes must be separated by a well-defined interface. Although the precise nature of the task separation will vary with the application, the definition of the interface will need to follow certain fundamental principles in order to provide functional separation. This interface was successfully implemented in the expert scheduling software currently running the automated chemical processing facility at Lockheed-Georgia. Potential applications of this concept in the areas of airborne avionics and robotics will be discussed.

Systems and technologies for high-speed inter-office/datacenter interface

NASA Astrophysics Data System (ADS)

Sone, Y.; Nishizawa, H.; Yamamoto, S.; Fukutoku, M.; Yoshimatsu, T.

2017-01-01

Emerging requirements for inter-office/inter-datacenter short reach links for data center interconnects (DCI) and metro transport networks have led to various inter-office and inter-datacenter optical interface technologies. These technologies are bringing significant changes to systems and network architectures. In this paper, we present a system and ZR optical interface technologies for DCI and metro transport networks, then introduce the latest challenges facing the system framework. There are two trends in reach extension; one is to use Ethernet and the other is to use digital coherent technologies. The first approach achieves reach extension while using as many existing Ethernet components as possible. It offers low costs as reuses the cost-effective components created for the large Ethernet market. The second approach adopts low-cost and low power coherent DSPs that implement the minimal set long haul transmission functions. This paper introduces an architecture that integrates both trends. The architecture satisfies both datacom and telecom needs with a common control and management interface and automated configuration.

Probing low noise at the MOS interface with a spin-orbit qubit.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Jock, Ryan Michael; Jacobson, Noah Tobias; Harvey-Collard, Patrick

The silicon metal-oxide-semiconductor (MOS) material system is technologically important for the implementation of electron spin-based quantum information technologies. Researchers predict the need for an integrated platform in order to implement useful computation, and decades of advancements in silicon microelectronics fabrication lends itself to this challenge. However, fundamental concerns have been raised about the MOS interface (e.g. trap noise, variations in electron g-factor and practical implementation of multi-QDs). Furthermore, two-axis control of silicon qubits has, to date, required the integration of non-ideal components (e.g. microwave strip-lines, micro-magnets, triple quantum dots, or introduction of donor atoms). In this paper, we introduce amore » spin-orbit (SO) driven singlet- triplet (ST) qubit in silicon, demonstrating all-electrical two-axis control that requires no additional integrated elements and exhibits charge noise properties equivalent to other more model, but less commercially mature, semiconductor systems. We demonstrate the ability to tune an intrinsic spin-orbit interface effect, which is consistent with Rashba and Dresselhaus contributions that are remarkably strong for a low spin-orbit material such as silicon. The qubit maintains the advantages of using isotopically enriched silicon for producing a quiet magnetic environment, measuring spin dephasing times of 1.6 μs using 99.95% 28Si epitaxy for the qubit, comparable to results from other isotopically enhanced silicon ST qubit systems. This work, therefore, demonstrates that the interface inherently provides properties for two-axis control, and the technologically important MOS interface does not add additional detrimental qubit noise. isotopically enhanced silicon ST qubit systems« less

Smart nanogels at the air/water interface: structural studies by neutron reflectivity

NASA Astrophysics Data System (ADS)

Zielińska, Katarzyna; Sun, Huihui; Campbell, Richard A.; Zarbakhsh, Ali; Resmini, Marina

2016-02-01

The development of effective transdermal drug delivery systems based on nanosized polymers requires a better understanding of the behaviour of such nanomaterials at interfaces. N-Isopropylacrylamide-based nanogels synthesized with different percentages of N,N'-methylenebisacrylamide as cross-linker, ranging from 10 to 30%, were characterized at physiological temperature at the air/water interface, using neutron reflectivity (NR), with isotopic contrast variation, and surface tension measurements; this allowed us to resolve the adsorbed amount and the volume fraction of nanogels at the interface. A large conformational change for the nanogels results in strong deformations at the interface. As the percentage of cross-linker incorporated in the nanogels becomes higher, more rigid matrices are obtained, although less deformed, and the amount of adsorbed nanogels is increased. The data provide the first experimental evidence of structural changes of nanogels as a function of the degree of cross-linking at the air/water interface.The development of effective transdermal drug delivery systems based on nanosized polymers requires a better understanding of the behaviour of such nanomaterials at interfaces. N-Isopropylacrylamide-based nanogels synthesized with different percentages of N,N'-methylenebisacrylamide as cross-linker, ranging from 10 to 30%, were characterized at physiological temperature at the air/water interface, using neutron reflectivity (NR), with isotopic contrast variation, and surface tension measurements; this allowed us to resolve the adsorbed amount and the volume fraction of nanogels at the interface. A large conformational change for the nanogels results in strong deformations at the interface. As the percentage of cross-linker incorporated in the nanogels becomes higher, more rigid matrices are obtained, although less deformed, and the amount of adsorbed nanogels is increased. The data provide the first experimental evidence of structural changes of nanogels as a function of the degree of cross-linking at the air/water interface. Electronic supplementary information (ESI) available. See DOI: 10.1039/c5nr07538f

Research of aerial imaging spectrometer data acquisition technology based on USB 3.0

NASA Astrophysics Data System (ADS)

Huang, Junze; Wang, Yueming; He, Daogang; Yu, Yanan

2016-11-01

With the emergence of UAV (unmanned aerial vehicle) platform for aerial imaging spectrometer, research of aerial imaging spectrometer DAS(data acquisition system) faces new challenges. Due to the limitation of platform and other factors, the aerial imaging spectrometer DAS requires small-light, low-cost and universal. Traditional aerial imaging spectrometer DAS system is expensive, bulky, non-universal and unsupported plug-and-play based on PCIe. So that has been unable to meet promotion and application of the aerial imaging spectrometer. In order to solve these problems, the new data acquisition scheme bases on USB3.0 interface.USB3.0 can provide guarantee of small-light, low-cost and universal relying on the forward-looking technology advantage. USB3.0 transmission theory is up to 5Gbps.And the GPIF programming interface achieves 3.2Gbps of the effective theoretical data bandwidth.USB3.0 can fully meet the needs of the aerial imaging spectrometer data transmission rate. The scheme uses the slave FIFO asynchronous data transmission mode between FPGA and USB3014 interface chip. Firstly system collects spectral data from TLK2711 of high-speed serial interface chip. Then FPGA receives data in DDR2 cache after ping-pong data processing. Finally USB3014 interface chip transmits data via automatic-dma approach and uploads to PC by USB3.0 cable. During the manufacture of aerial imaging spectrometer, the DAS can achieve image acquisition, transmission, storage and display. All functions can provide the necessary test detection for aerial imaging spectrometer. The test shows that system performs stable and no data lose. Average transmission speed and storage speed of writing SSD can stabilize at 1.28Gbps. Consequently ,this data acquisition system can meet application requirements for aerial imaging spectrometer.

Single-channel ground airborne radio system (SINCGARS) based remote control for the M1 Abrahms

NASA Astrophysics Data System (ADS)

Urda, Joseph R.

1995-04-01

Remote control of the Ml Abrahms Main Battle Tank through a minefield breach operation will remove the vehicle crew from the inherent hazard. A successful remote control system will provide automotive control yet not impair normal operation. This requires a minimum of physical parts, and an unobtrusive installation. Most importantly, a system failure must not impair the regular operation as a manned system. The system itself need not be complex. A minefield breach only requires simple control of automotive function and a mine plow interface. Control hardware for the Ml-Al can be reduced to two linear actuators, an electrical interface for the engine control unit, an interface for the mine plow, and the associated cables. Communication between vehicle control and operator control takes place over the vehicles organic radio (typically SINCGARS). This helps reduce the number of special purpose components for the remote control device. The device is currently awaiting an automotive safety test to prepare for its safety release. Because of the specific nature of the MDL-STD 1553-B data bus the device will not control an M1-A2 Main Battle Tank. The architecture will allow control of the M1-A2 through the 1553-B data bus however the physical hardware has not been constructed. The control scheme will not change. The communication interface will provide greater flexibility when interfacing to the vehicle tactical radio. Operational utility will be determined by U.S. Army Training and Doctrine Command personnel. The obvious benefit is that if a remote tank is lost during a minefield breach the crew is saved.

Development and Design of a User Interface for a Computer Automated Heating, Ventilation, and Air Conditioning System

DOE Office of Scientific and Technical Information (OSTI.GOV)

Anderson, B.; /Fermilab

1999-10-08

A user interface is created to monitor and operate the heating, ventilation, and air conditioning system. The interface is networked to the system's programmable logic controller. The controller maintains automated control of the system. The user through the interface is able to see the status of the system and override or adjust the automatic control features. The interface is programmed to show digital readouts of system equipment as well as visual queues of system operational statuses. It also provides information for system design and component interaction. The interface is made easier to read by simple designs, color coordination, and graphics.more » Fermi National Accelerator Laboratory (Fermi lab) conducts high energy particle physics research. Part of this research involves collision experiments with protons, and anti-protons. These interactions are contained within one of two massive detectors along Fermilab's largest particle accelerator the Tevatron. The D-Zero Assembly Building houses one of these detectors. At this time detector systems are being upgraded for a second experiment run, titled Run II. Unlike the previous run, systems at D-Zero must be computer automated so operators do not have to continually monitor and adjust these systems during the run. Human intervention should only be necessary for system start up and shut down, and equipment failure. Part of this upgrade includes the heating, ventilation, and air conditioning system (HVAC system). The HVAC system is responsible for controlling two subsystems, the air temperatures of the D-Zero Assembly Building and associated collision hall, as well as six separate water systems used in the heating and cooling of the air and detector components. The BYAC system is automated by a programmable logic controller. In order to provide system monitoring and operator control a user interface is required. This paper will address methods and strategies used to design and implement an effective user interface. Background material pertinent to the BYAC system will cover the separate water and air subsystems and their purposes. In addition programming and system automation will also be covered.« less

Low Cost Graphics. Second Edition.

ERIC Educational Resources Information Center

Tinker, Robert F.

This manual describes the CALM TV graphics interface, a low-cost means of producing quality graphics on an ordinary TV. The system permits the output of data in graphic as well as alphanumeric form and the input of data from the face of the TV using a light pen. The integrated circuits required in the interface can be obtained from standard…

Software Independent Verification and Validation (SIV&V) Simplified

DTIC Science & Technology

2006-12-01

Configuration Item I/O Input/Output I2V2 Independent Integrated Verification and Validation IBM International Business Machines ICD Interface...IPT Integrated Product Team IRS Interface Requirements Specification ISD Integrated System Diagram ITD Integrated Test Description ITP ...programming languages such as COBOL (Common Business Oriented Language) (Codasyl committee 1960), and FORTRAN (FORmula TRANslator) ( IBM 1952) (Robat 11

Integrated guidance, navigation and control verification plan primary flight system. [space shuttle avionics integration

NASA Technical Reports Server (NTRS)

1978-01-01

The verification process and requirements for the ascent guidance interfaces and the ascent integrated guidance, navigation and control system for the space shuttle orbiter are defined as well as portions of supporting systems which directly interface with the system. The ascent phase of verification covers the normal and ATO ascent through the final OMS-2 circularization burn (all of OPS-1), the AOA ascent through the OMS-1 burn, and the RTLS ascent through ET separation (all of MM 601). In addition, OPS translation verification is defined. Verification trees and roadmaps are given.

Automated crystallographic system for high-throughput protein structure determination.

PubMed

Brunzelle, Joseph S; Shafaee, Padram; Yang, Xiaojing; Weigand, Steve; Ren, Zhong; Anderson, Wayne F

2003-07-01

High-throughput structural genomic efforts require software that is highly automated, distributive and requires minimal user intervention to determine protein structures. Preliminary experiments were set up to test whether automated scripts could utilize a minimum set of input parameters and produce a set of initial protein coordinates. From this starting point, a highly distributive system was developed that could determine macromolecular structures at a high throughput rate, warehouse and harvest the associated data. The system uses a web interface to obtain input data and display results. It utilizes a relational database to store the initial data needed to start the structure-determination process as well as generated data. A distributive program interface administers the crystallographic programs which determine protein structures. Using a test set of 19 protein targets, 79% were determined automatically.

Development and Implementation of the X.25 Protocol for the Universal Network Interface Device (UNID) II. Volume 1.

DTIC Science & Technology

1985-12-01

development of an improved Universal Network Interface Device (UNID II). The UNID II’s architecture was based on a preliminary design project at...interface device, performing all functions required ,: the multi-ring LAN. The device depicted by RADC’s studies would connect a highly variable group of host...used the ISO Open Systems Ilterconnection (OSI) seven layer model as the basic structure for data flow and program development . In 1982 Cuomo

Multi-modal assessment of on-road demand of voice and manual phone calling and voice navigation entry across two embedded vehicle systems.

PubMed

Mehler, Bruce; Kidd, David; Reimer, Bryan; Reagan, Ian; Dobres, Jonathan; McCartt, Anne

2016-03-01

One purpose of integrating voice interfaces into embedded vehicle systems is to reduce drivers' visual and manual distractions with 'infotainment' technologies. However, there is scant research on actual benefits in production vehicles or how different interface designs affect attentional demands. Driving performance, visual engagement, and indices of workload (heart rate, skin conductance, subjective ratings) were assessed in 80 drivers randomly assigned to drive a 2013 Chevrolet Equinox or Volvo XC60. The Chevrolet MyLink system allowed completing tasks with one voice command, while the Volvo Sensus required multiple commands to navigate the menu structure. When calling a phone contact, both voice systems reduced visual demand relative to the visual-manual interfaces, with reductions for drivers in the Equinox being greater. The Equinox 'one-shot' voice command showed advantages during contact calling but had significantly higher error rates than Sensus during destination address entry. For both secondary tasks, neither voice interface entirely eliminated visual demand. Practitioner Summary: The findings reinforce the observation that most, if not all, automotive auditory-vocal interfaces are multi-modal interfaces in which the full range of potential demands (auditory, vocal, visual, manipulative, cognitive, tactile, etc.) need to be considered in developing optimal implementations and evaluating drivers' interaction with the systems. Social Media: In-vehicle voice-interfaces can reduce visual demand but do not eliminate it and all types of demand need to be taken into account in a comprehensive evaluation.

Multi-modal assessment of on-road demand of voice and manual phone calling and voice navigation entry across two embedded vehicle systems

PubMed Central

Mehler, Bruce; Kidd, David; Reimer, Bryan; Reagan, Ian; Dobres, Jonathan; McCartt, Anne

2016-01-01

Abstract One purpose of integrating voice interfaces into embedded vehicle systems is to reduce drivers’ visual and manual distractions with ‘infotainment’ technologies. However, there is scant research on actual benefits in production vehicles or how different interface designs affect attentional demands. Driving performance, visual engagement, and indices of workload (heart rate, skin conductance, subjective ratings) were assessed in 80 drivers randomly assigned to drive a 2013 Chevrolet Equinox or Volvo XC60. The Chevrolet MyLink system allowed completing tasks with one voice command, while the Volvo Sensus required multiple commands to navigate the menu structure. When calling a phone contact, both voice systems reduced visual demand relative to the visual–manual interfaces, with reductions for drivers in the Equinox being greater. The Equinox ‘one-shot’ voice command showed advantages during contact calling but had significantly higher error rates than Sensus during destination address entry. For both secondary tasks, neither voice interface entirely eliminated visual demand. Practitioner Summary: The findings reinforce the observation that most, if not all, automotive auditory–vocal interfaces are multi-modal interfaces in which the full range of potential demands (auditory, vocal, visual, manipulative, cognitive, tactile, etc.) need to be considered in developing optimal implementations and evaluating drivers’ interaction with the systems. Social Media: In-vehicle voice-interfaces can reduce visual demand but do not eliminate it and all types of demand need to be taken into account in a comprehensive evaluation. PMID:26269281

Software Acquisition Manager’s Workstation (SAM/WS) System Design.

DTIC Science & Technology

1984-04-30

3. Tactical Digital System Requirements ..................... 31General...pspc t14 3. Tactical Digital System Requirements pspc-tiS 3.1 General pspc-t16 3.2 Program Description pspc-t17 3.2.1 General...pspc-t22 3.3.2 Digital Processor Input/Output Utilization Table pspc t23 3.3.3 Digital Processor Interface Block Diagram pspc-t24 3.3.4 Program

Servicing capability for the evolutionary Space Station

NASA Technical Reports Server (NTRS)

Thomas, Edward F.; Grems, Edward G., III; Corbo, James E.

1990-01-01

Since the beginning of the Space Station Freedom (SSF) program the concept of on-orbit servicing of user hardware has been an integral part of the program implementation. The user servicing system architecture has been divided into a baseline and a growth phase. The baseline system consists of the following hardware elements that will support user servicing - flight telerobotic servicer, crew and equipment translation aid, crew intravehicular and extravehicular servicing support, logistics supply system, mobile servicing center, and the special purpose dextrous manipulator. The growth phase incorporates a customer servicing facility (CSF), a station-based orbital maneuvering vehicle and an orbital spacecraft consumables resupply system. The requirements for user servicing were derived from the necessity to service attached payloads, free flyers and coorbiting platforms. These requirements include: orbital replacement units (ORU) and instrument changeout, National Space Transportation System cargo bay loading and unloading, contamination control and monitoring, thermal protection, payload berthing, storage, access to SSF distributed systems, functional checkout, and fluid replenishment. The baseline user servicing capabilities accommodate ORU and instrument changeout. However, this service is limited to attached payloads, either in situ or at a locally adjacent site. The growth phase satisfies all identified user servicing requirements by expanding servicing capabilities to include complex servicing tasks for attached payloads, free-flyers and coorbiting platforms at a dedicated, protected Servicing site. To provide a smooth evolution of user servicing the SSF interfaces that are necessary to accommodate the growth phase have been identified. The interface requirements on SSF have been greatly simplified by accommodating the growth servicing support elements within the CSF. This results in a single SSF interface: SSF to the CSF.

7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.

Code of Federal Regulations, 2012 CFR

2012-01-01

... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...

7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.

Code of Federal Regulations, 2013 CFR

2013-01-01

... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...

7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.

Code of Federal Regulations, 2014 CFR

2014-01-01

... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...

7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.

Code of Federal Regulations, 2011 CFR

2011-01-01

... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...

Advanced extravehicular activity systems requirements definition study. Phase 2: Extravehicular activity at a lunar base

NASA Technical Reports Server (NTRS)

Neal, Valerie; Shields, Nicholas, Jr.; Carr, Gerald P.; Pogue, William; Schmitt, Harrison H.; Schulze, Arthur E.

1988-01-01

The focus is on Extravehicular Activity (EVA) systems requirements definition for an advanced space mission: remote-from-main base EVA on the Moon. The lunar environment, biomedical considerations, appropriate hardware design criteria, hardware and interface requirements, and key technical issues for advanced lunar EVA were examined. Six remote EVA scenarios (three nominal operations and three contingency situations) were developed in considerable detail.

IAC - INTEGRATED ANALYSIS CAPABILITY

NASA Technical Reports Server (NTRS)

Frisch, H. P.

1994-01-01

The objective of the Integrated Analysis Capability (IAC) system is to provide a highly effective, interactive analysis tool for the integrated design of large structures. With the goal of supporting the unique needs of engineering analysis groups concerned with interdisciplinary problems, IAC was developed to interface programs from the fields of structures, thermodynamics, controls, and system dynamics with an executive system and database to yield a highly efficient multi-disciplinary system. Special attention is given to user requirements such as data handling and on-line assistance with operational features, and the ability to add new modules of the user's choice at a future date. IAC contains an executive system, a data base, general utilities, interfaces to various engineering programs, and a framework for building interfaces to other programs. IAC has shown itself to be effective in automatic data transfer among analysis programs. IAC 2.5, designed to be compatible as far as possible with Level 1.5, contains a major upgrade in executive and database management system capabilities, and includes interfaces to enable thermal, structures, optics, and control interaction dynamics analysis. The IAC system architecture is modular in design. 1) The executive module contains an input command processor, an extensive data management system, and driver code to execute the application modules. 2) Technical modules provide standalone computational capability as well as support for various solution paths or coupled analyses. 3) Graphics and model generation interfaces are supplied for building and viewing models. Advanced graphics capabilities are provided within particular analysis modules such as INCA and NASTRAN. 4) Interface modules provide for the required data flow between IAC and other modules. 5) User modules can be arbitrary executable programs or JCL procedures with no pre-defined relationship to IAC. 6) Special purpose modules are included, such as MIMIC (Model Integration via Mesh Interpolation Coefficients), which transforms field values from one model to another; LINK, which simplifies incorporation of user specific modules into IAC modules; and DATAPAC, the National Bureau of Standards statistical analysis package. The IAC database contains structured files which provide a common basis for communication between modules and the executive system, and can contain unstructured files such as NASTRAN checkpoint files, DISCOS plot files, object code, etc. The user can define groups of data and relations between them. A full data manipulation and query system operates with the database. The current interface modules comprise five groups: 1) Structural analysis - IAC contains a NASTRAN interface for standalone analysis or certain structural/control/thermal combinations. IAC provides enhanced structural capabilities for normal modes and static deformation analysis via special DMAP sequences. IAC 2.5 contains several specialized interfaces from NASTRAN in support of multidisciplinary analysis. 2) Thermal analysis - IAC supports finite element and finite difference techniques for steady state or transient analysis. There are interfaces for the NASTRAN thermal analyzer, SINDA/SINFLO, and TRASYS II. FEMNET, which converts finite element structural analysis models to finite difference thermal analysis models, is also interfaced with the IAC database. 3) System dynamics - The DISCOS simulation program which allows for either nonlinear time domain analysis or linear frequency domain analysis, is fully interfaced to the IAC database management capability. 4) Control analysis - Interfaces for the ORACLS, SAMSAN, NBOD2, and INCA programs allow a wide range of control system analyses and synthesis techniques. Level 2.5 includes EIGEN, which provides tools for large order system eigenanalysis, and BOPACE, which allows for geometric capabilities and finite element analysis with nonlinear material. Also included in IAC level 2.5 is SAMSAN 3.1, an engineering analysis program which contains a general purpose library of over 600 subroutines for numerical analysis. 5) Graphics - The graphics package IPLOT is included in IAC. IPLOT generates vector displays of tabular data in the form of curves, charts, correlation tables, etc. Either DI3000 or PLOT-10 graphics software is required for full graphic capability. In addition to these analysis tools, IAC 2.5 contains an IGES interface which allows the user to read arbitrary IGES files into an IAC database and to edit and output new IGES files. IAC is available by license for a period of 10 years to approved U.S. licensees. The licensed program product includes one set of supporting documentation. Additional copies may be purchased separately. IAC is written in FORTRAN 77 and has been implemented on a DEC VAX series computer operating under VMS. IAC can be executed by multiple concurrent users in batch or interactive mode. The program is structured to allow users to easily delete those program capabilities and "how to" examples they do not want in order to reduce the size of the package. The basic central memory requirement for IAC is approximately 750KB. The following programs are also available from COSMIC as separate packages: NASTRAN, SINDA/SINFLO, TRASYS II, DISCOS, ORACLS, SAMSAN, NBOD2, and INCA. The development of level 2.5 of IAC was completed in 1989.

Shuttle/Agena study. Volume 2, part 1: Program requirements, conclusions, recommendations

NASA Technical Reports Server (NTRS)

1972-01-01

An evaluation to determine the compatibility of the Agena with the space transportation system for use as an expendable third stage to the space shuttle was conducted. The Agena was considered for those missions requiring additional propulsion capability beyond that used for low earth orbit. The study defines the interface requirements imposed on both the Agena and the shuttle system and identifies those areas where the Agena must be improved or modified to satisfy mission requirements.

Degree Audit Systems: Are They Worth It?

ERIC Educational Resources Information Center

Johns, Virginia

2006-01-01

A lot of various degree audit systems are available on the market and most often they have similar features such as the functionality they each provide, the technical platforms upon which they operate, their requirements for interfacing with the local SIS, the ease of use, and the level of effort required to implement and operate. However, the…

Requirements and specifications of the space telescope for scientific operations

NASA Technical Reports Server (NTRS)

West, D. K.

1976-01-01

Requirements for the scientific operations of the Space Telescope and the Science Institute are used to develop operational interfaces between user scientists and the NASA ground system. General data systems are defined for observatory scheduling, daily science planning, and science data management. Hardware, software, manpower, and space are specified for several science institute locations and support options.

Usability assessment of an electronic health record in a comprehensive dental clinic.

PubMed

Suebnukarn, Siriwan; Rittipakorn, Pawornwan; Thongyoi, Budsara; Boonpitak, Kwanwong; Wongsapai, Mansuang; Pakdeesan, Panu

2013-12-01

In this paper we present the development and usability of an electronic health record (EHR) system in a comprehensive dental clinic.The graphic user interface of the system was designed to consider the concept of cognitive ergonomics.The cognitive task analysis was used to evaluate the user interface of the EHR by identifying all sub-tasks and classifying them into mental or physical operators, and to predict task execution time required to perform the given task. We randomly selected 30 cases that had oral examinations for routine clinical care in a comprehensive dental clinic. The results were based on the analysis of 4 prototypical tasks performed by ten EHR users. The results showed that on average a user needed to go through 27 steps to complete all tasks for one case. To perform all 4 tasks of 30 cases, they spent about 91 min (independent of system response time) for data entry, of which 51.8 min were spent on more effortful mental operators. In conclusion, the user interface can be improved by reducing the percentage of mental effort required for the tasks.

Quality assurance in the production of pipe fittings by automatic laser-based material identification

NASA Astrophysics Data System (ADS)

Moench, Ingo; Peter, Laszlo; Priem, Roland; Sturm, Volker; Noll, Reinhard

1999-09-01

In plants of the chemical, nuclear and off-shore industry, application specific high-alloyed steels are used for pipe fittings. Mixing of different steel grades can lead to corrosion with severe consequential damages. Growing quality requirements and environmental responsibilities demand a 100% material control in the production of the pipe fittings. Therefore, LIFT, an automatic inspection machine, was developed to insure against any mix of material grades. LIFT is able to identify more than 30 different steel grades. The inspection method is based on Laser-Induced Breakdown Spectrometry (LIBS). An expert system, which can be easily trained and recalibrated, was developed for the data evaluation. The result of the material inspection is transferred to an external handling system via a PLC interface. The duration of the inspection process is 2 seconds. The graphical user interface was developed with respect to the requirements of an unskilled operator. The software is based on a realtime operating system and provides a safe and reliable operation. An interface for the remote maintenance by modem enables a fast operational support. Logged data are retrieved and evaluated. This is the basis for an adaptive improvement of the configuration of LIFT with respect to changing requirements in the production line. Within the first six months of routine operation, about 50000 pipe fittings were inspected.

Soft Material-Enabled, Flexible Hybrid Electronics for Medicine, Healthcare, and Human-Machine Interfaces

PubMed Central

Herbert, Robert; Kim, Jong-Hoon; Kim, Yun Soung; Lee, Hye Moon

2018-01-01

Flexible hybrid electronics (FHE), designed in wearable and implantable configurations, have enormous applications in advanced healthcare, rapid disease diagnostics, and persistent human-machine interfaces. Soft, contoured geometries and time-dynamic deformation of the targeted tissues require high flexibility and stretchability of the integrated bioelectronics. Recent progress in developing and engineering soft materials has provided a unique opportunity to design various types of mechanically compliant and deformable systems. Here, we summarize the required properties of soft materials and their characteristics for configuring sensing and substrate components in wearable and implantable devices and systems. Details of functionality and sensitivity of the recently developed FHE are discussed with the application areas in medicine, healthcare, and machine interactions. This review concludes with a discussion on limitations of current materials, key requirements for next generation materials, and new application areas. PMID:29364861

Space transfer vehicle concepts and requirements study. Volume 2, book 3: STV system interfaces

NASA Technical Reports Server (NTRS)

Weber, Gary A.

1991-01-01

This report presents the results of systems analyses and conceptual design of space transfer vehicles (STV). The missions examined included piloted and unpiloted lunar outpost support and spacecraft servicing, and unpiloted payload delivery to various earth and solar orbits. The study goal was to examine the mission requirements and provide a decision data base for future programmatic development plans. The final lunar transfer vehicles provided a wide range of capabilities and interface requirements while maintaining a constant payload mission model. Launch vehicle and space station sensitivity was examined, with the final vehicles as point design covering the range of possible options. Development programs were defined and technology readiness levels for different options were determined. Volume 1 presents the executive summary, volume 2 provides the study results, and volume 3 the cost and WBS data.

Soft Material-Enabled, Flexible Hybrid Electronics for Medicine, Healthcare, and Human-Machine Interfaces.

PubMed

Herbert, Robert; Kim, Jong-Hoon; Kim, Yun Soung; Lee, Hye Moon; Yeo, Woon-Hong

2018-01-24

Flexible hybrid electronics (FHE), designed in wearable and implantable configurations, have enormous applications in advanced healthcare, rapid disease diagnostics, and persistent human-machine interfaces. Soft, contoured geometries and time-dynamic deformation of the targeted tissues require high flexibility and stretchability of the integrated bioelectronics. Recent progress in developing and engineering soft materials has provided a unique opportunity to design various types of mechanically compliant and deformable systems. Here, we summarize the required properties of soft materials and their characteristics for configuring sensing and substrate components in wearable and implantable devices and systems. Details of functionality and sensitivity of the recently developed FHE are discussed with the application areas in medicine, healthcare, and machine interactions. This review concludes with a discussion on limitations of current materials, key requirements for next generation materials, and new application areas.

Comparing Text-based and Graphic User Interfaces for Novice and Expert Users

PubMed Central

Chen, Jung-Wei; Zhang, Jiajie

2007-01-01

Graphic User Interface (GUI) is commonly considered to be superior to Text-based User Interface (TUI). This study compares GUI and TUI in an electronic dental record system. Several usability analysis techniques compared the relative effectiveness of a GUI and a TUI. Expert users and novice users were evaluated in time required and steps needed to complete the task. A within-subject design was used to evaluate if the experience with either interface will affect task performance. The results show that the GUI interface was not better than the TUI for expert users. GUI interface was better for novice users. For novice users there was a learning transfer effect from TUI to GUI. This means a user interface is user-friendly or not depending on the mapping between the user interface and tasks. GUI by itself may or may not be better than TUI. PMID:18693811

Comparing Text-based and Graphic User Interfaces for novice and expert users.

PubMed

Chen, Jung-Wei; Zhang, Jiajie

2007-10-11

Graphic User Interface (GUI) is commonly considered to be superior to Text-based User Interface (TUI). This study compares GUI and TUI in an electronic dental record system. Several usability analysis techniques compared the relative effectiveness of a GUI and a TUI. Expert users and novice users were evaluated in time required and steps needed to complete the task. A within-subject design was used to evaluate if the experience with either interface will affect task performance. The results show that the GUI interface was not better than the TUI for expert users. GUI interface was better for novice users. For novice users there was a learning transfer effect from TUI to GUI. This means a user interface is user-friendly or not depending on the mapping between the user interface and tasks. GUI by itself may or may not be better than TUI.

Evaluation of a commercial electro-kinetically pumped sheath-flow nanospray interface coupled to an automated capillary zone electrophoresis system.

PubMed

Peuchen, Elizabeth H; Zhu, Guije; Sun, Liangliang; Dovichi, Norman J

2017-03-01

Capillary zone electrophoresis-electrospray ionization-mass spectrometry (CZE-ESI-MS) is attracting renewed attention for proteomic and metabolomic analysis. An important reason for this interest is the maturation and commercialization of interfaces for coupling CZE with ESI-MS. One of these interfaces is an electro-kinetically pumped sheath flow nanospray interface developed by the Dovichi group, in which a very low sheath flow is generated based on electroosmosis within a glass emitter. CMP Scientific has commercialized this interface as the EMASS-II ion source. In this work, we compared the performance of the EMASS-II ion source with our in-house system. The performance of the systems is equivalent. We also coupled the EMASS-II ion source with a PrinCE Next|480 capillary electrophoresis autosampler and an Orbitrap mass spectrometer, and analyzed this system's performance in terms of sensitivity, reproducibility, and separation performance for separation of tryptic digests, intact proteins, and amino acids. The system produced reproducible analysis of BSA digest; the RSDs of peptide intensity and migration time across 24 runs were less than 20 and 6%, respectively. The system produced a linear calibration curve of intensity across a 30-fold range of tryptic digest concentration. The combination of a commercial autosampler and electrospray interface efficiently separated amino acids, peptides, and intact proteins, and only required 5 μL of sample for analysis. Graphical Abstract The commercial and locally constructed versions of the interface provide similar numbers of protein identifications from a Xenopus laevis fertilized egg digest.

Smashing the Stovepipe: Leveraging the GMSEC Open Architecture and Advanced IT Automation to Rapidly Prototype, Develop and Deploy Next-Generation Multi-Mission Ground Systems

NASA Technical Reports Server (NTRS)

Swenson, Paul

2017-01-01

Satellite/Payload Ground Systems - Typically highly-customized to a specific mission's use cases - Utilize hundreds (or thousands!) of specialized point-to-point interfaces for data flows / file transfers Documentation and tracking of these complex interfaces requires extensive time to develop and extremely high staffing costs Implementation and testing of these interfaces are even more cost-prohibitive, and documentation often lags behind implementation resulting in inconsistencies down the road With expanding threat vectors, IT Security, Information Assurance and Operational Security have become key Ground System architecture drivers New Federal security-related directives are generated on a daily basis, imposing new requirements on current / existing ground systems - These mandated activities and data calls typically carry little or no additional funding for implementation As a result, Ground System Sustaining Engineering groups and Information Technology staff continually struggle to keep up with the rolling tide of security Advancing security concerns and shrinking budgets are pushing these large stove-piped ground systems to begin sharing resources - I.e. Operational / SysAdmin staff, IT security baselines, architecture decisions or even networks / hosting infrastructure Refactoring these existing ground systems into multi-mission assets proves extremely challenging due to what is typically very tight coupling between legacy components As a result, many "Multi-Mission" ops. environments end up simply sharing compute resources and networks due to the difficulty of refactoring into true multi-mission systems Utilizing continuous integration / rapid system deployment technologies in conjunction with an open architecture messaging approach allows System Engineers and Architects to worry less about the low-level details of interfaces between components and configuration of systems GMSEC messaging is inherently designed to support multi-mission requirements, and allows components to aggregate data across multiple homogeneous or heterogeneous satellites or payloads - The highly-successful Goddard Science and Planetary Operations Control Center (SPOCC) utilizes GMSEC as the hub for it's automation and situational awareness capability Shifts focus towards getting GS to a final configuration-managed baseline, as well as multi-mission / big-picture capabilities that help increase situational awareness, promote cross-mission sharing and establish enhanced fleet management capabilities across all levels of the enterprise.

Inter-Module Ventilation Changes to the International Space Station Vehicle to Support Integration of the International Docking Adapter and Commercial Crew Vehicles

NASA Technical Reports Server (NTRS)

Link, Dwight E., Jr.; Balistreri, Steven F., Jr.

2015-01-01

The International Space Station (ISS) Environmental Control and Life Support System (ECLSS) is continuing to evolve in the post-Space Shuttle era. The ISS vehicle configuration that is in operation was designed for docking of a Space Shuttle vehicle, and designs currently under development for commercial crew vehicles require different interfaces. The ECLSS Temperature and Humidity Control Subsystem (THC) Inter-Module Ventilation (IMV) must be modified in order to support two docking interfaces at the forward end of ISS, to provide the required air exchange. Development of a new higher-speed IMV fan and extensive ducting modifications are underway to support the new Commercial Crew Vehicle interfaces. This paper will review the new ECLSS IMV development requirements, component design and hardware status, subsystem analysis and testing performed to date, and implementation plan to support Commercial Crew Vehicle docking.

Integration of an expert system into a user interface language demonstration

NASA Technical Reports Server (NTRS)

Stclair, D. C.

1986-01-01

The need for a User Interface Language (UIL) has been recognized by the Space Station Program Office as a necessary tool to aid in minimizing the cost of software generation by multiple users. Previous history in the Space Shuttle Program has shown that many different areas of software generation, such as operations, integration, testing, etc., have each used a different user command language although the types of operations being performed were similar in many respects. Since the Space Station represents a much more complex software task, a common user command language--a user interface language--is required to support the large spectrum of space station software developers and users. To assist in the selection of an appropriate set of definitions for a UIL, a series of demonstration programs was generated with which to test UIL concepts against specific Space Station scenarios using operators for the astronaut and scientific community. Because of the importance of expert system in the space station, it was decided that an expert system should be embedded in the UIL. This would not only provide insight into the UIL components required but would indicate the effectiveness with which an expert system could function in such an environment.

Structural and thermal interface characteristics of Stirling cycle cryocoolers for space applications

NASA Technical Reports Server (NTRS)

Boyle, R.; James, E.; Miller, P.; Arillo, V.; Sparr, L.; Castles, S.

1991-01-01

Integration of a Stirling cycle cryocooler into a flight system will require careful attention to the thermal, structural, and electrical interfaces between the cryocooler, the instrument and the spacecraft. These issues are currently under investigation by National Aeronautics and Space Administration/Goddard Space Flight Center personnel in laboratory tests of representative longlife cryocoolers. An 80 K cryocooler has been instrumented as a testbed for vibration control systems characterization. Initial vibration data using a new six-DOF force dynamometer is presented in this report.

The development of a complementary expendable launch vehicle interface for an STS deployable payload

NASA Astrophysics Data System (ADS)

Eubanks, Ed; Gibb, John

1990-04-01

The development is described of an interface, the Titan Payload Adapter (TPA), between a Space Transportation System (STS) deployable payload and an expendable launch vehicle (ELV). Separate ascent and separation constraint systems allow a payload with integral trunnions to retain its originally designed, boost-phase load structure, yet also allow the expendable booster vehicle to separate from the payload via retro-rockets. Design requirements as well as development problems and their solutions are discussed.

Software handlers for process interfaces

NASA Technical Reports Server (NTRS)

Bercaw, R. W.

1976-01-01

Process interfaces are developed in an effort to reduce the time, effort, and money required to install computer systems. Probably the chief obstacle to the achievement of these goals lies in the problem of developing software handlers having the same degree of generality and modularity as the hardware. The problem of combining the advantages of modular instrumentation with those of modern multitask operating systems has not been completely solved, but there are a number of promising developments. The essential principles involved are considered.

The development of a complementary expendable launch vehicle interface for an STS deployable payload

NASA Technical Reports Server (NTRS)

Eubanks, ED; Gibb, John

1990-01-01

The development is described of an interface, the Titan Payload Adapter (TPA), between a Space Transportation System (STS) deployable payload and an expendable launch vehicle (ELV). Separate ascent and separation constraint systems allow a payload with integral trunnions to retain its originally designed, boost-phase load structure, yet also allow the expendable booster vehicle to separate from the payload via retro-rockets. Design requirements as well as development problems and their solutions are discussed.

PDSS configuration control plan and procedures

NASA Technical Reports Server (NTRS)

1983-01-01

The payload development support system (PDSS) configuration control plan and procedures are presented. These plans and procedures establish the process for maintaining configuration control of the PDSS system, especially the Spacelab experiment interface device's (SEID) RAU, HRM, and PDI interface simulations and the PDSS ECOS DEP Services simulation. The plans and procedures as specified are designed to provide a simplified but complete configuration control process. The intent is to require a minimum amount of paperwork but provide total traceability of PDSS during experiment test activities.

Computerized Adaptive Testing System Design: Preliminary Design Considerations.

DTIC Science & Technology

1982-07-01

the administrative or operational requirements of CAT and presented - # k*----.,ku nh-n.-utu (IPOI efi~g.2me (PMU tQ7q. vim NPRDC TR 82-52 July 1982...design model for a computerized adaptive testing ( CAT ) system was developed and presented through a series of hierarchy plus input-process-output (HIPO...physical system was addressed through brief discussions of hardware, software, interfaces, and personnel requirements. Further steps in CAT system

Domain Engineering

NASA Astrophysics Data System (ADS)

Bjørner, Dines

Before software can be designed we must know its requirements. Before requirements can be expressed we must understand the domain. So it follows, from our dogma, that we must first establish precise descriptions of domains; then, from such descriptions, “derive” at least domain and interface requirements; and from those and machine requirements design the software, or, more generally, the computing systems.

Viper cabin-fuselage structural design concept with engine installation and wing structural design

NASA Technical Reports Server (NTRS)

Marchesseault, B.; Carr, D.; Mccorkle, T.; Stevens, C.; Turner, D.

1993-01-01

This report describes the process and considerations in designing the cabin, nose, drive shaft, and wing assemblies for the 'Viper' concept aircraft. Interfaces of these assemblies, as well as interfaces with the sections of the aircraft aft of the cabin, are also discussed. The results of the design process are included. The goal of this project is to provide a structural design which complies with FAR 23 requirements regarding occupant safety, emergency landing loads, and maneuvering loads. The design must also address the interfaces of the various systems in the cabin, nose, and wing, including the drive shaft, venting, vacuum, electrical, fuel, and control systems. Interfaces between the cabin assembly and the wing carrythrough and empennage assemblies were required, as well. In the design of the wing assemblies, consistency with the existing cabin design was required. The major areas considered in this report are materials and construction, loading, maintenance, environmental considerations, wing assembly fatigue, and weight. The first three areas are developed separately for the nose, cabin, drive shaft, and wing assemblies, while the last three are discussed for the entire design. For each assembly, loading calculations were performed to determine the proper sizing of major load carrying components. Table 1.0 lists the resulting margins of safety for these key components, along with the types of the loads involved, and the page number upon which they are discussed.

Making intelligent systems team players: Case studies and design issues. Volume 1: Human-computer interaction design

NASA Technical Reports Server (NTRS)

Malin, Jane T.; Schreckenghost, Debra L.; Woods, David D.; Potter, Scott S.; Johannesen, Leila; Holloway, Matthew; Forbus, Kenneth D.

1991-01-01

Initial results are reported from a multi-year, interdisciplinary effort to provide guidance and assistance for designers of intelligent systems and their user interfaces. The objective is to achieve more effective human-computer interaction (HCI) for systems with real time fault management capabilities. Intelligent fault management systems within the NASA were evaluated for insight into the design of systems with complex HCI. Preliminary results include: (1) a description of real time fault management in aerospace domains; (2) recommendations and examples for improving intelligent systems design and user interface design; (3) identification of issues requiring further research; and (4) recommendations for a development methodology integrating HCI design into intelligent system design.

HAL/S-FC compiler system functional specification

NASA Technical Reports Server (NTRS)

1974-01-01

Compiler organization is discussed, including overall compiler structure, internal data transfer, compiler development, and code optimization. The user, system, and SDL interfaces are described, along with compiler system requirements. Run-time software support package and restrictions and dependencies are also considered of the HAL/S-FC system.

Voltage assisted asymmetric nanoscale wear on ultra-smooth diamond like carbon thin films at high sliding speeds

PubMed Central

Rajauria, Sukumar; Schreck, Erhard; Marchon, Bruno

2016-01-01

The understanding of tribo- and electro-chemical phenomenons on the molecular level at a sliding interface is a field of growing interest. Fundamental chemical and physical insights of sliding surfaces are crucial for understanding wear at an interface, particularly for nano or micro scale devices operating at high sliding speeds. A complete investigation of the electrochemical effects on high sliding speed interfaces requires a precise monitoring of both the associated wear and surface chemical reactions at the interface. Here, we demonstrate that head-disk interface inside a commercial magnetic storage hard disk drive provides a unique system for such studies. The results obtained shows that the voltage assisted electrochemical wear lead to asymmetric wear on either side of sliding interface. PMID:27150446

Voltage assisted asymmetric nanoscale wear on ultra-smooth diamond like carbon thin films at high sliding speeds

NASA Astrophysics Data System (ADS)

Rajauria, Sukumar; Schreck, Erhard; Marchon, Bruno

2016-05-01

The understanding of tribo- and electro-chemical phenomenons on the molecular level at a sliding interface is a field of growing interest. Fundamental chemical and physical insights of sliding surfaces are crucial for understanding wear at an interface, particularly for nano or micro scale devices operating at high sliding speeds. A complete investigation of the electrochemical effects on high sliding speed interfaces requires a precise monitoring of both the associated wear and surface chemical reactions at the interface. Here, we demonstrate that head-disk interface inside a commercial magnetic storage hard disk drive provides a unique system for such studies. The results obtained shows that the voltage assisted electrochemical wear lead to asymmetric wear on either side of sliding interface.

PointCom: semi-autonomous UGV control with intuitive interface

NASA Astrophysics Data System (ADS)

Rohde, Mitchell M.; Perlin, Victor E.; Iagnemma, Karl D.; Lupa, Robert M.; Rohde, Steven M.; Overholt, James; Fiorani, Graham

2008-04-01

Unmanned ground vehicles (UGVs) will play an important role in the nation's next-generation ground force. Advances in sensing, control, and computing have enabled a new generation of technologies that bridge the gap between manual UGV teleoperation and full autonomy. In this paper, we present current research on a unique command and control system for UGVs named PointCom (Point-and-Go Command). PointCom is a semi-autonomous command system for one or multiple UGVs. The system, when complete, will be easy to operate and will enable significant reduction in operator workload by utilizing an intuitive image-based control framework for UGV navigation and allowing a single operator to command multiple UGVs. The project leverages new image processing algorithms for monocular visual servoing and odometry to yield a unique, high-performance fused navigation system. Human Computer Interface (HCI) techniques from the entertainment software industry are being used to develop video-game style interfaces that require little training and build upon the navigation capabilities. By combining an advanced navigation system with an intuitive interface, a semi-autonomous control and navigation system is being created that is robust, user friendly, and less burdensome than many current generation systems. mand).

Energetics of the Semiconductor-Electrolyte Interface.

ERIC Educational Resources Information Center

Turner, John A.

1983-01-01

The use of semiconductors as electrodes for electrochemistry requires an understanding of both solid-state physics and electrochemistry, since phenomena associated with both disciplines are seen in semiconductor/electrolyte systems. The interfacial energetics of these systems are discussed. (JN)

Integrated geometry and grid generation system for complex configurations

NASA Technical Reports Server (NTRS)

Akdag, Vedat; Wulf, Armin

1992-01-01

A grid generation system was developed that enables grid generation for complex configurations. The system called ICEM/CFD is described and its role in computational fluid dynamics (CFD) applications is presented. The capabilities of the system include full computer aided design (CAD), grid generation on the actual CAD geometry definition using robust surface projection algorithms, interfacing easily with known CAD packages through common file formats for geometry transfer, grid quality evaluation of the volume grid, coupling boundary condition set-up for block faces with grid topology generation, multi-block grid generation with or without point continuity and block to block interface requirement, and generating grid files directly compatible with known flow solvers. The interactive and integrated approach to the problem of computational grid generation not only substantially reduces manpower time but also increases the flexibility of later grid modifications and enhancements which is required in an environment where CFD is integrated into a product design cycle.

A finite element model of conduction, convection, and phase change near a solid/melt interface. Ph.D. Thesis - Michigan Univ.

NASA Technical Reports Server (NTRS)

Viterna, Larry A.

1991-01-01

Detailed understanding of heat transfer and fluid flow is required for many aerospace thermal systems. These systems often include phase change and operate over a range of accelerations or effective gravitational fields. An approach to analyzing such systems is presented which requires the simultaneous solution of the conservation laws of energy, momentum, and mass, as well as an equation of state. The variable property form of the governing equations are developed in two-dimensional Cartesian coordinates for a Newtonian fluid. A numerical procedure for solving the governing equations is presented and implemented in a computer program. The Galerkin form of the finite element method is used to solve the spatial variation of the field variables, along with the implicit Crank-Nicolson time marching algorithm. Quadratic Langrangian elements are used for the internal energy and the two components of velocity. Linear Lagrangian elements are used for the pressure. The location of the solid/liquid interface as well as the temperatures are determined form the calculated internal energy and pressure. This approach is quite general in that it can describe heat transfer without phase change, phase change with a sharp interface, and phase change without an interface. Analytical results from this model are compared to those of other researchers studying transient conduction, convection, and phase change and are found to be in good agreement. The numerical procedure presented requires significant computer resources, but this is not unusual when compared to similar studies by other researchers. Several methods are suggested to reduce the computational times.

Emissivity of Rocket Plume Particulates

DTIC Science & Technology

1992-09-01

V. EXPERIMENTAL RESULTS ........ ............... 29 VI. CONCLUSIONS AND RECOMMENDATIONS .... ........ 32 APPENDIX A. CATS -E SOFTWARE...interfaced through the CATS E Thermal Analysis software, which is MS-DOS based, and can be run on any 28b or higher CPU. This system allows real-time...body source to establish the parameters required by the CATS program for proper microscope/scanner interface. A complete description of microscope

Command module/service module reaction control subsystem assessment

NASA Technical Reports Server (NTRS)

Weary, D. P.

1971-01-01

Detailed review of component failure histories, qualification adequacy, manufacturing flow, checkout requirements and flow, ground support equipment interfaces, subsystem interface verification, protective devices, and component design did not reveal major weaknesses in the command service module (CSM) reaction control system (RCS). No changes to the CSM RCS were recommended. The assessment reaffirmed the adequacy of the CSM RCS for future Apollo missions.

12-bit 32 channel 500 MS/s low-latency ADC for particle accelerators real-time control

NASA Astrophysics Data System (ADS)

Karnitski, Anton; Baranauskas, Dalius; Zelenin, Denis; Baranauskas, Gytis; Zhankevich, Alexander; Gill, Chris

2017-09-01

Particle beam control systems require real-time low latency digital feedback with high linearity and dynamic range. Densely packed electronic systems employ high performance multichannel digitizers causing excessive heat dissipation. Therefore, low power dissipation is another critical requirement for these digitizers. A described 12-bit 500 MS/s ADC employs a sub-ranging architecture based on a merged sample & hold circuit, a residue C-DAC and a shared 6-bit flash core ADC. The core ADC provides a sequential coarse and fine digitization featuring a latency of two clock cycles. The ADC is implemented in a 28 nm CMOS process and consumes 4 mW of power per channel from a 0.9 V supply (interfacing and peripheral circuits are excluded). Reduced power consumption and small on-chip area permits the implementation of 32 ADC channels on a 10.7 mm2 chip. The ADC includes a JESD204B standard compliant output data interface operated at the 7.5 Gbps/ch rate. To minimize the data interface related time latency, a special feature permitting to bypass the JESD204B interface is built in. DoE Phase I Award Number: DE-SC0017213.

Selectivity and Longevity of Peripheral-Nerve and Machine Interfaces: A Review

PubMed Central

Ghafoor, Usman; Kim, Sohee; Hong, Keum-Shik

2017-01-01

For those individuals with upper-extremity amputation, a daily normal living activity is no longer possible or it requires additional effort and time. With the aim of restoring their sensory and motor functions, theoretical and technological investigations have been carried out in the field of neuroprosthetic systems. For transmission of sensory feedback, several interfacing modalities including indirect (non-invasive), direct-to-peripheral-nerve (invasive), and cortical stimulation have been applied. Peripheral nerve interfaces demonstrate an edge over the cortical interfaces due to the sensitivity in attaining cortical brain signals. The peripheral nerve interfaces are highly dependent on interface designs and are required to be biocompatible with the nerves to achieve prolonged stability and longevity. Another criterion is the selection of nerves that allows minimal invasiveness and damages as well as high selectivity for a large number of nerve fascicles. In this paper, we review the nerve-machine interface modalities noted above with more focus on peripheral nerve interfaces, which are responsible for provision of sensory feedback. The invasive interfaces for recording and stimulation of electro-neurographic signals include intra-fascicular, regenerative-type interfaces that provide multiple contact channels to a group of axons inside the nerve and the extra-neural-cuff-type interfaces that enable interaction with many axons around the periphery of the nerve. Section Current Prosthetic Technology summarizes the advancements made to date in the field of neuroprosthetics toward the achievement of a bidirectional nerve-machine interface with more focus on sensory feedback. In the Discussion section, the authors propose a hybrid interface technique for achieving better selectivity and long-term stability using the available nerve interfacing techniques. PMID:29163122

Systematic Refinement of a Health Information Technology Time and Motion Workflow Instrument for Inpatient Nursing Care using a Standardized Interface Terminology

PubMed Central

Zhang, Yi; Monsen, Karen A; Adam, Terrence J; Pieczkiewicz, David S; Daman, Megan; Melton, Genevieve B

2011-01-01

Time and motion (T&M) studies provide an objective method to measure the expenditure of time by clinicians. While some instruments for T&M studies have been designed to evaluate health information technology (HIT), these instruments have not been designed for nursing workflow. We took an existing open source HIT T&M study application designed to evaluate physicians in the ambulatory setting and rationally adapted it through empiric observations to record nursing activities in the inpatient setting and linked this instrument to an existing interface terminology, the Omaha System. Nursing activities involved several dimensions and could include multiple activities occurring simultaneously, requiring significant instrument redesign. 94% of the activities from the study instrument mapped adequately to the Omaha System. T&M study instruments require customization in design optimize them for different environments, such as inpatient nursing, to enable optimal data collection. Interface terminologies show promise as a framework for recording and analyzing T&M study data. PMID:22195228

Display integration for ground combat vehicles

NASA Astrophysics Data System (ADS)

Busse, David J.

1998-09-01

The United States Army's requirement to employ high resolution target acquisition sensors and information warfare to increase its dominance over enemy forces has led to the need to integrate advanced display devices into ground combat vehicle crew stations. The Army's force structure require the integration of advanced displays on both existing and emerging ground combat vehicle systems. The fielding of second generation target acquisition sensors, color digital terrain maps and high volume digital command and control information networks on these platforms define display performance requirements. The greatest challenge facing the system integrator is the development and integration of advanced displays that meet operational, vehicle and human computer interface performance requirements for the ground combat vehicle fleet. The subject of this paper is to address those challenges: operational and vehicle performance, non-soldier centric crew station configurations, display performance limitations related to human computer interfaces and vehicle physical environments, display technology limitations and the Department of Defense (DOD) acquisition reform initiatives. How the ground combat vehicle Program Manager and system integrator are addressing these challenges are discussed through the integration of displays on fielded, current and future close combat vehicle applications.

Monitoring and controlling ATLAS data management: The Rucio web user interface

NASA Astrophysics Data System (ADS)

Lassnig, M.; Beermann, T.; Vigne, R.; Barisits, M.; Garonne, V.; Serfon, C.

2015-12-01

The monitoring and controlling interfaces of the previous data management system DQ2 followed the evolutionary requirements and needs of the ATLAS collaboration. The new data management system, Rucio, has put in place a redesigned web-based interface based upon the lessons learnt from DQ2, and the increased volume of managed information. This interface encompasses both a monitoring and controlling component, and allows easy integration for usergenerated views. The interface follows three design principles. First, the collection and storage of data from internal and external systems is asynchronous to reduce latency. This includes the use of technologies like ActiveMQ or Nagios. Second, analysis of the data into information is done massively parallel due to its volume, using a combined approach with an Oracle database and Hadoop MapReduce. Third, sharing of the information does not distinguish between human or programmatic access, making it easy to access selective parts of the information both in constrained frontends like web-browsers as well as remote services. This contribution will detail the reasons for these principles and the design choices taken. Additionally, the implementation, the interactions with external systems, and an evaluation of the system in production, both from a technological and user perspective, conclude this contribution.

Detailed requirements document for the Interactive Financial Management System (IFMS), volume 1

NASA Technical Reports Server (NTRS)

Dodson, D. B.

1975-01-01

The detailed requirements for phase 1 (online fund control, subauthorization accounting, and accounts receivable functional capabilities) of the Interactive Financial Management System (IFMS) are described. This includes information on the following: systems requirements, performance requirements, test requirements, and production implementation. Most of the work is centered on systems requirements, and includes discussions on the following processes: resources authority, allotment, primary work authorization, reimbursable order acceptance, purchase request, obligation, cost accrual, cost distribution, disbursement, subauthorization performance, travel, accounts receivable, payroll, property, edit table maintenance, end-of-year, backup input. Other subjects covered include: external systems interfaces, general inquiries, general report requirements, communication requirements, and miscellaneous. Subjects covered under performance requirements include: response time, processing volumes, system reliability, and accuracy. Under test requirements come test data sources, general test approach, and acceptance criteria. Under production implementation come data base establishment, operational stages, and operational requirements.

49 CFR 236.1013 - PTC Development Plan and Notice of Product Intent content requirements and Type Approval.

Code of Federal Regulations, 2012 CFR

2012-10-01

... physical relationships in the subsystem or system; (2) A description of the railroad operation or... requirements; (5) A preliminary human factors analysis, including a complete description of all human-machine interfaces and the impact of interoperability requirements on the same; (6) An analysis of the applicability...

49 CFR 236.1013 - PTC Development Plan and Notice of Product Intent content requirements and Type Approval.

Code of Federal Regulations, 2011 CFR

2011-10-01

... physical relationships in the subsystem or system; (2) A description of the railroad operation or... requirements; (5) A preliminary human factors analysis, including a complete description of all human-machine interfaces and the impact of interoperability requirements on the same; (6) An analysis of the applicability...

49 CFR 236.1013 - PTC Development Plan and Notice of Product Intent content requirements and Type Approval.

Code of Federal Regulations, 2013 CFR

2013-10-01

... physical relationships in the subsystem or system; (2) A description of the railroad operation or... requirements; (5) A preliminary human factors analysis, including a complete description of all human-machine interfaces and the impact of interoperability requirements on the same; (6) An analysis of the applicability...

49 CFR 236.1013 - PTC Development Plan and Notice of Product Intent content requirements and Type Approval.

Code of Federal Regulations, 2014 CFR

2014-10-01

... physical relationships in the subsystem or system; (2) A description of the railroad operation or... requirements; (5) A preliminary human factors analysis, including a complete description of all human-machine interfaces and the impact of interoperability requirements on the same; (6) An analysis of the applicability...

Using RDF and Git to Realize a Collaborative Metadata Repository.

PubMed

Stöhr, Mark R; Majeed, Raphael W; Günther, Andreas

2018-01-01

The German Center for Lung Research (DZL) is a research network with the aim of researching respiratory diseases. The participating study sites' register data differs in terms of software and coding system as well as data field coverage. To perform meaningful consortium-wide queries through one single interface, a uniform conceptual structure is required covering the DZL common data elements. No single existing terminology includes all our concepts. Potential candidates such as LOINC and SNOMED only cover specific subject areas or are not granular enough for our needs. To achieve a broadly accepted and complete ontology, we developed a platform for collaborative metadata management. The DZL data management group formulated detailed requirements regarding the metadata repository and the user interfaces for metadata editing. Our solution builds upon existing standard technologies allowing us to meet those requirements. Its key parts are RDF and the distributed version control system Git. We developed a software system to publish updated metadata automatically and immediately after performing validation tests for completeness and consistency.

Systems Engineering

NASA Technical Reports Server (NTRS)

Pellerano, Fernando

2015-01-01

This short course provides information on what systems engineering is and how the systems engineer guides requirements, interfaces with the discipline leads, and resolves technical issues. There are many system-wide issues that either impact or are impacted by the thermal subsystem. This course will introduce these issues and illustrate them with real life examples.

IAC - INTEGRATED ANALYSIS CAPABILITY

NASA Technical Reports Server (NTRS)

Frisch, H. P.

1994-01-01

The objective of the Integrated Analysis Capability (IAC) system is to provide a highly effective, interactive analysis tool for the integrated design of large structures. With the goal of supporting the unique needs of engineering analysis groups concerned with interdisciplinary problems, IAC was developed to interface programs from the fields of structures, thermodynamics, controls, and system dynamics with an executive system and database to yield a highly efficient multi-disciplinary system. Special attention is given to user requirements such as data handling and on-line assistance with operational features, and the ability to add new modules of the user's choice at a future date. IAC contains an executive system, a data base, general utilities, interfaces to various engineering programs, and a framework for building interfaces to other programs. IAC has shown itself to be effective in automatic data transfer among analysis programs. IAC 2.5, designed to be compatible as far as possible with Level 1.5, contains a major upgrade in executive and database management system capabilities, and includes interfaces to enable thermal, structures, optics, and control interaction dynamics analysis. The IAC system architecture is modular in design. 1) The executive module contains an input command processor, an extensive data management system, and driver code to execute the application modules. 2) Technical modules provide standalone computational capability as well as support for various solution paths or coupled analyses. 3) Graphics and model generation interfaces are supplied for building and viewing models. Advanced graphics capabilities are provided within particular analysis modules such as INCA and NASTRAN. 4) Interface modules provide for the required data flow between IAC and other modules. 5) User modules can be arbitrary executable programs or JCL procedures with no pre-defined relationship to IAC. 6) Special purpose modules are included, such as MIMIC (Model Integration via Mesh Interpolation Coefficients), which transforms field values from one model to another; LINK, which simplifies incorporation of user specific modules into IAC modules; and DATAPAC, the National Bureau of Standards statistical analysis package. The IAC database contains structured files which provide a common basis for communication between modules and the executive system, and can contain unstructured files such as NASTRAN checkpoint files, DISCOS plot files, object code, etc. The user can define groups of data and relations between them. A full data manipulation and query system operates with the database. The current interface modules comprise five groups: 1) Structural analysis - IAC contains a NASTRAN interface for standalone analysis or certain structural/control/thermal combinations. IAC provides enhanced structural capabilities for normal modes and static deformation analysis via special DMAP sequences. IAC 2.5 contains several specialized interfaces from NASTRAN in support of multidisciplinary analysis. 2) Thermal analysis - IAC supports finite element and finite difference techniques for steady state or transient analysis. There are interfaces for the NASTRAN thermal analyzer, SINDA/SINFLO, and TRASYS II. FEMNET, which converts finite element structural analysis models to finite difference thermal analysis models, is also interfaced with the IAC database. 3) System dynamics - The DISCOS simulation program which allows for either nonlinear time domain analysis or linear frequency domain analysis, is fully interfaced to the IAC database management capability. 4) Control analysis - Interfaces for the ORACLS, SAMSAN, NBOD2, and INCA programs allow a wide range of control system analyses and synthesis techniques. Level 2.5 includes EIGEN, which provides tools for large order system eigenanalysis, and BOPACE, which allows for geometric capabilities and finite element analysis with nonlinear material. Also included in IAC level 2.5 is SAMSAN 3.1, an engineering analysis program which contains a general purpose library of over 600 subroutin

Implementation of EPICS based vacuum control system for variable energy cyclotron centre, Kolkata

NASA Astrophysics Data System (ADS)

Roy, Anindya; Bhole, R. B.; Nandy, Partha P.; Yadav, R. C.; Pal, Sarbajit; Roy, Amitava

2015-03-01

The vacuum system of the Room Temperature (K = 130) Cyclotron of Variable Energy Cyclotron Centre is comprised of vacuum systems of main machine and Beam Transport System. The vacuum control system is upgraded to a PLC based Automated system from the initial relay based Manual system. The supervisory control of the vacuum system is implemented in Experimental Physics and Industrial Control System (EPICS). An EPICS embedded ARM based vacuum gauge controller is developed to mitigate the requirement of vendor specific gauge controller for gauges and also for seamless integration of the gauge controllers with the control system. A set of MS-Windows ActiveX components with embedded EPICS Channel Access interface are developed to build operator interfaces with less complex programming and to incorporate typical Windows feature, e.g., user authentication, file handling, better fonts, colors, mouse actions etc. into the operator interfaces. The control parameters, monitoring parameters, and system interlocks of the system are archived in MySQL based EPICS MySQL Archiver developed indigenously. In this paper, we describe the architecture, the implementation details, and the performance of the system.

Implementation of EPICS based vacuum control system for variable energy cyclotron centre, Kolkata.

PubMed

Roy, Anindya; Bhole, R B; Nandy, Partha P; Yadav, R C; Pal, Sarbajit; Roy, Amitava

2015-03-01

The vacuum system of the Room Temperature (K = 130) Cyclotron of Variable Energy Cyclotron Centre is comprised of vacuum systems of main machine and Beam Transport System. The vacuum control system is upgraded to a PLC based Automated system from the initial relay based Manual system. The supervisory control of the vacuum system is implemented in Experimental Physics and Industrial Control System (EPICS). An EPICS embedded ARM based vacuum gauge controller is developed to mitigate the requirement of vendor specific gauge controller for gauges and also for seamless integration of the gauge controllers with the control system. A set of MS-Windows ActiveX components with embedded EPICS Channel Access interface are developed to build operator interfaces with less complex programming and to incorporate typical Windows feature, e.g., user authentication, file handling, better fonts, colors, mouse actions etc. into the operator interfaces. The control parameters, monitoring parameters, and system interlocks of the system are archived in MySQL based EPICS MySQL Archiver developed indigenously. In this paper, we describe the architecture, the implementation details, and the performance of the system.

Research in image management and access

NASA Technical Reports Server (NTRS)

Vondran, Raymond F.; Barron, Billy J.

1993-01-01

Presently, the problem of over-all library system design has been compounded by the accretion of both function and structure to a basic framework of requirements. While more device power has led to increased functionality, opportunities for reducing system complexity at the user interface level have not always been pursued with equal zeal. The purpose of this book is therefore to set forth and examine these opportunities, within the general framework of human factors research in man-machine interfaces. Human factors may be viewed as a series of trade-off decisions among four polarized objectives: machine resources and user specifications; functionality and user requirements. In the past, a limiting factor was the availability of systems. However, in the last two years, over one hundred libraries supported by many different software configurations have been added to the Internet. This document includes a statistical analysis of human responses to five Internet library systems by key features, development of the ideal online catalog system, and ideal online catalog systems for libraries and information centers.

Kennedy Space Center's Command and Control System - "Toasters to Rocket Ships"

NASA Technical Reports Server (NTRS)

Lougheed, Kirk; Mako, Cheryle

2011-01-01

This slide presentation reviews the history of the development of the command and control system at Kennedy Space Center. From a system that could be brought to Florida in the trunk of a car in the 1950's. Including the development of larger and more complex launch vehicles with the Apollo program where human launch controllers managed the launch process with a hardware only system that required a dedicated human interface to perform every function until the Apollo vehicle lifted off from the pad. Through the development of the digital computer that interfaced with ground launch processing systems with the Space Shuttle program. Finally, showing the future control room being developed to control the missions to return to the moon and Mars, which will maximize the use of Commercial-Off-The Shelf (COTS) hardware and software which was standards based and not tied to a single vendor. The system is designed to be flexible and adaptable to support the requirements of future spacecraft and launch vehicles.

Space shuttle EVA/IVA support equipment requirements study. Volume 1: Final summary report

NASA Technical Reports Server (NTRS)

1973-01-01

A study was conducted to determine the support equipment requirements for space shuttle intravehicular and extravehicular activities. The subjects investigated are; (1) EVA/IVA task identification and analysis,. (2) primary life support system, (3) emergency life support system, (4) pressure suit assembly, (5) restraints, (6) work site provision, (7) emergency internal vehicular emergencies, and (8) vehicular interfaces.

Space station needs, attributes and architectural options study. Volume 3: Requirements

NASA Technical Reports Server (NTRS)

1983-01-01

A typical system specification format is presented and requirements are compiled. A Program Specification Tree is shown showing a high inclination space station and a low inclination space station with their typical element breakdown, also represented along the top blocks are the interfaces with other systems. The specification format is directed at the Low Inclination space station.

Mark IVA microprocessor support

NASA Technical Reports Server (NTRS)

Burford, A. L.

1982-01-01

The requirements and plans for the maintenance support of microprocessor-based controllers in the Deep Space Network Mark IVA System are discussed. Additional new interfaces and 16-bit processors have introduced problems not present in the Mark III System. The need for continuous training of maintenance personnel to maintain a level of expertise consistent with the sophistication of the required tools is also emphasized.

Experiment module concepts study. Volume 2: Experiments and mission operations

NASA Technical Reports Server (NTRS)

Macdonald, J. M.

1970-01-01

The baseline experiment program is concerned with future space experiments and cover the scientific disciplines of astronomy, space physics, space biology, biomedicine and biotechnology, earth applications, materials science, and advanced technology. The experiments within each discipline are grouped into functional program elements according to experiments that support a particular area of research or investigation and experiments that impose similar or related demand on space station support systems. The experiment requirements on module subsystems, experiment operating modes and time profiles, and the role of the astronaut are discussed. Launch and rendezvous with the space station, disposal, and on-orbit operations are delineated. The operational interfaces between module and other system elements are presented and include space station and logistic system interfaces. Preliminary launch and on-orbit environmental criteria and requirements are discussed, and experiment equipment weights by functional program elements are tabulated.

Systems Maintenance Automated Repair Tasks (SMART)

NASA Technical Reports Server (NTRS)

2008-01-01

SMART is an interactive decision analysis and refinement software system that uses evaluation criteria for discrepant conditions to automatically provide and populate a document/procedure with predefined steps necessary to repair a discrepancy safely, effectively, and efficiently. SMART can store the tacit (corporate) knowledge merging the hardware specification requirements with the actual "how to" repair methods, sequences, and required equipment, all within a user-friendly interface. Besides helping organizations retain repair knowledge in streamlined procedures and sequences, SMART can also help them in saving processing time and expense, increasing productivity, improving quality, and adhering more closely to safety and other guidelines. Though SMART was developed for Space Shuttle applications, its interface is easily adaptable to any hardware that can be broken down by component, subcomponent, discrepancy, and repair.

Space shuttle main engine controller

NASA Technical Reports Server (NTRS)

Mattox, R. M.; White, J. B.

1981-01-01

A technical description of the space shuttle main engine controller, which provides engine checkout prior to launch, engine control and monitoring during launch, and engine safety and monitoring in orbit, is presented. Each of the major controller subassemblies, the central processing unit, the computer interface electronics, the input electronics, the output electronics, and the power supplies are described and discussed in detail along with engine and orbiter interfaces and operational requirements. The controller represents a unique application of digital concepts, techniques, and technology in monitoring, managing, and controlling a high performance rocket engine propulsion system. The operational requirements placed on the controller, the extremely harsh operating environment to which it is exposed, and the reliability demanded, result in the most complex and rugged digital system ever designed, fabricated, and flown.

Admission and Preventive Load Control for Delivery of Multicast and Broadcast Services via S-UMTS

NASA Astrophysics Data System (ADS)

Angelou, E.; Koutsokeras, N.; Andrikopoulos, I.; Mertzanis, I.; Karaliopoulos, M.; Henrio, P.

2003-07-01

An Admission Control strategy is proposed for unidirectional satellite systems delivering multicast and broadcast services to mobile users. In such systems, both the radio interface and the targeted services impose particular requirements on the RRM task. We briefly discuss the RRM requirements that stem from the services point of view and from the features of the SATIN access scheme that differentiate it from the conventional T-UMTS radio interface. The main functional entities of RRM and the alternative modes of operation are outlined and the proposed Admission Control algorithm is described in detail. The results from the simulation study that demonstrate its performance for a number of different scenarios are finally presented and conclusions derived.

Human-machine interface (HMI) report for 241-SY-101 data acquisition [and control] system (DACS) upgrade study

DOE Office of Scientific and Technical Information (OSTI.GOV)

Truitt, R.W.

1997-10-22

This report provides an independent evaluation of information for a Windows based Human Machine Interface (HMI) to replace the existing DOS based Iconics HMI currently used in the Data Acquisition and Control System (DACS) used at Tank 241-SY-101. A fundamental reason for this evaluation is because of the difficulty of maintaining the system with obsolete, unsupported software. The DACS uses a software operator interface (Genesis for DOS HMI) that is no longer supported by its manufacturer, Iconics. In addition to its obsolescence, it is complex and difficult to train additional personnel on. The FY 1997 budget allocated $40K for phasemore » 1 of a software/hardware upgrade that would have allowed the old DOS based system to be replaced by a current Windows based system. Unfortunately, budget constraints during FY 1997 has prompted deferral of the upgrade. The upgrade needs to be performed at the earliest possible time, before other failures render the system useless. Once completed, the upgrade could alleviate other concerns: spare pump software may be able to be incorporated into the same software as the existing pump, thereby eliminating the parallel path dilemma; and the newer, less complex software should expedite training of future personnel, and in the process, require that less technical time be required to maintain the system.« less

Functional Mobility Testing: A Novel Method to Establish Human System Interface Design Requirements

NASA Technical Reports Server (NTRS)

England, Scott A.; Benson, Elizabeth A.; Rajulu, Sudhakar

2008-01-01

Across all fields of human-system interface design it is vital to posses a sound methodology dictating the constraints on the system based on the capabilities of the human user. These limitations may be based on strength, mobility, dexterity, cognitive ability, etc. and combinations thereof. Data collected in an isolated environment to determine, for example, maximal strength or maximal range of motion would indeed be adequate for establishing not-to-exceed type design limitations, however these restraints on the system may be excessive over what is basally needed. Resources may potentially be saved by having a technique to determine the minimum measurements a system must accommodate. This paper specifically deals with the creation of a novel methodology for establishing mobility requirements for a new generation of space suit design concepts. Historically, the Space Shuttle and the International Space Station vehicle and space hardware design requirements documents such as the Man-Systems Integration Standards and International Space Station Flight Crew Integration Standard explicitly stated that the designers should strive to provide the maximum joint range of motion capabilities exhibited by a minimally clothed human subject. In the course of developing the Human-Systems Integration Requirements (HSIR) for the new space exploration initiative (Constellation), an effort was made to redefine the mobility requirements in the interest of safety and cost. Systems designed for manned space exploration can receive compounded gains from simplified designs that are both initially less expensive to produce and lighter, thereby, cheaper to launch.

A Browser-Based Multi-User Working Environment for Physicists

NASA Astrophysics Data System (ADS)

Erdmann, M.; Fischer, R.; Glaser, C.; Klingebiel, D.; Komm, M.; Müller, G.; Rieger, M.; Steggemann, J.; Urban, M.; Winchen, T.

2014-06-01

Many programs in experimental particle physics do not yet have a graphical interface, or demand strong platform and software requirements. With the most recent development of the VISPA project, we provide graphical interfaces to existing software programs and access to multiple computing clusters through standard web browsers. The scalable clientserver system allows analyses to be performed in sizable teams, and disburdens the individual physicist from installing and maintaining a software environment. The VISPA graphical interfaces are implemented in HTML, JavaScript and extensions to the Python webserver. The webserver uses SSH and RPC to access user data, code and processes on remote sites. As example applications we present graphical interfaces for steering the reconstruction framework OFFLINE of the Pierre-Auger experiment, and the analysis development toolkit PXL. The browser based VISPA system was field-tested in biweekly homework of a third year physics course by more than 100 students. We discuss the system deployment and the evaluation by the students.

Soft, Conformal Bioelectronics for a Wireless Human-Wheelchair Interface

PubMed Central

Mishra, Saswat; Norton, James J. S.; Lee, Yongkuk; Lee, Dong Sup; Agee, Nicolas; Chen, Yanfei; Chun, Youngjae; Yeo, Woon-Hong

2017-01-01

There are more than 3 million people in the world whose mobility relies on wheelchairs. Recent advancement on engineering technology enables more intuitive, easy-to-use rehabilitation systems. A human-machine interface that uses non-invasive, electrophysiological signals can allow a systematic interaction between human and devices; for example, eye movement-based wheelchair control. However, the existing machine-interface platforms are obtrusive, uncomfortable, and often cause skin irritations as they require a metal electrode affixed to the skin with a gel and acrylic pad. Here, we introduce a bioelectronic system that makes dry, conformal contact to the skin. The mechanically comfortable sensor records high-fidelity electrooculograms, comparable to the conventional gel electrode. Quantitative signal analysis and infrared thermographs show the advantages of the soft biosensor for an ergonomic human-machine interface. A classification algorithm with an optimized set of features shows the accuracy of 94% with five eye movements. A Bluetooth-enabled system incorporating the soft bioelectronics demonstrates a precise, hands-free control of a robotic wheelchair via electrooculograms. PMID:28152485

Experimental research control software system

NASA Astrophysics Data System (ADS)

Cohn, I. A.; Kovalenko, A. G.; Vystavkin, A. N.

2014-05-01

A software system, intended for automation of a small scale research, has been developed. The software allows one to control equipment, acquire and process data by means of simple scripts. The main purpose of that development is to increase experiment automation easiness, thus significantly reducing experimental setup automation efforts. In particular, minimal programming skills are required and supervisors have no reviewing troubles. Interactions between scripts and equipment are managed automatically, thus allowing to run multiple scripts simultaneously. Unlike well-known data acquisition commercial software systems, the control is performed by an imperative scripting language. This approach eases complex control and data acquisition algorithms implementation. A modular interface library performs interaction with external interfaces. While most widely used interfaces are already implemented, a simple framework is developed for fast implementations of new software and hardware interfaces. While the software is in continuous development with new features being implemented, it is already used in our laboratory for automation of a helium-3 cryostat control and data acquisition. The software is open source and distributed under Gnu Public License.

Open-systems architecture of a standardized command interface chip-set for switching and control of a spacecraft power bus

NASA Technical Reports Server (NTRS)

Ruiz, Ian B.; Burke, Gary R.; Lung, Gerald; Whitaker, William D.; Nowicki, Robert M.

2004-01-01

The Jet Propulsion Laboratory (JPL) has developed a command interface chip-set that primarily consists of two mixed-signal ASICs'; the Command Interface ASIC (CIA) and Analog Interface ASIC (AIA). The Open-systems architecture employed during the design of this chip-set enables its use as both an intelligent gateway between the system's flight computer and the control, actuation, and activation of the spacecraft's loads, valves, and pyrotechnics respectfully as well as the regulator of the spacecraft power bus. Furthermore, the architecture is highly adaptable and employed fault-tolerant design methods enabling a host of other mission uses including reliable remote data collection. The objective of this design is to both provide a needed flight component that meets the stringent environmental requirements of current deep space missions and to add a new element to a growing library that can be used as a standard building block for future missions to the outer planets.

Optical nano-biosensing interface via nucleic acid amplification strategy: construction and application.

PubMed

Zhou, Hong; Liu, Jing; Xu, Jing-Juan; Zhang, Shu-Sheng; Chen, Hong-Yuan

2018-03-21

Modern optical detection technology plays a critical role in current clinical detection due to its high sensitivity and accuracy. However, higher requirements such as extremely high detection sensitivity have been put forward due to the clinical needs for the early finding and diagnosing of malignant tumors which are significant for tumor therapy. The technology of isothermal amplification with nucleic acids opens up avenues for meeting this requirement. Recent reports have shown that a nucleic acid amplification-assisted modern optical sensing interface has achieved satisfactory sensitivity and accuracy, high speed and specificity. Compared with isothermal amplification technology designed to work completely in a solution system, solid biosensing interfaces demonstrated better performances in stability and sensitivity due to their ease of separation from the reaction mixture and the better signal transduction on these optical nano-biosensing interfaces. Also the flexibility and designability during the construction of these nano-biosensing interfaces provided a promising research topic for the ultrasensitive detection of cancer diseases. In this review, we describe the construction of the burgeoning number of optical nano-biosensing interfaces assisted by a nucleic acid amplification strategy, and provide insightful views on: (1) approaches to the smart fabrication of an optical nano-biosensing interface, (2) biosensing mechanisms via the nucleic acid amplification method, (3) the newest strategies and future perspectives.

ANALOG I/O MODULE TEST SYSTEM BASED ON EPICS CA PROTOCOL AND ACTIVEX CA INTERFACE

DOE Office of Scientific and Technical Information (OSTI.GOV)

YENG,YHOFF,L.

2003-10-13

Analog input (ADC) and output (DAC) modules play a substantial role in device level control of accelerator and large experiment physics control system. In order to get the best performance some features of analog modules including linearity, accuracy, crosstalk, thermal drift and so on have to be evaluated during the preliminary design phase. Gain and offset error calibration and thermal drift compensation (if needed) may have to be done in the implementation phase as well. A natural technique for performing these tasks is to interface the analog VO modules and GPIB interface programmable test instruments with a computer, which canmore » complete measurements or calibration automatically. A difficulty is that drivers of analog modules and test instruments usually work on totally different platforms (vxworks VS Windows). Developing new test routines and drivers for testing instruments under VxWorks (or any other RTOS) platform is not a good solution because such systems have relatively poor user interface and developing such software requires substantial effort. EPICS CA protocol and ActiveX CA interface provide another choice, a PC and LabVIEW based test system. Analog 110 module can be interfaced from LabVIEW test routines via ActiveX CA interface. Test instruments can be controlled via LabVIEW drivers, most of which are provided by instrument vendors or by National Instruments. Labview also provides extensive data analysis and process functions. Using these functions, users can generate powerful test routines very easily. Several applications built for Spallation Neutron Source (SNS) Beam Loss Monitor (BLM) system are described in this paper.« less

Analyzing Software Requirements Errors in Safety-Critical, Embedded Systems

NASA Technical Reports Server (NTRS)

Lutz, Robyn R.

1993-01-01

This paper analyzes the root causes of safety-related software errors in safety-critical, embedded systems. The results show that software errors identified as potentially hazardous to the system tend to be produced by different error mechanisms than non- safety-related software errors. Safety-related software errors are shown to arise most commonly from (1) discrepancies between the documented requirements specifications and the requirements needed for correct functioning of the system and (2) misunderstandings of the software's interface with the rest of the system. The paper uses these results to identify methods by which requirements errors can be prevented. The goal is to reduce safety-related software errors and to enhance the safety of complex, embedded systems.

Conceptual Design of a Space-Based Multimegawatt MHD Power System, Task 1 Topical Report; Volume 1: Technical Discussion

DTIC Science & Technology

1988-01-01

system requirements, design guidelines, and interface requirements has been prepared and included as Volume II of this Task 1 topical report. The Volume ...WAESD-TR-88-0002 Conceptual Design Of A Space-Based Multimegawatt MHD Power System ffA«kjjjjjTfc Task 1 Topical Report Volume I: Technical...Space-Based Multimegawatt MHD Power System: Task 1 Topical Report, Volume I: Technical Discussion Personal Author: Dana, RA. Corporate Author Or

Automated placement of interfaces in conformational kinetics calculations using machine learning

NASA Astrophysics Data System (ADS)

Grazioli, Gianmarc; Butts, Carter T.; Andricioaei, Ioan

2017-10-01

Several recent implementations of algorithms for sampling reaction pathways employ a strategy for placing interfaces or milestones across the reaction coordinate manifold. Interfaces can be introduced such that the full feature space describing the dynamics of a macromolecule is divided into Voronoi (or other) cells, and the global kinetics of the molecular motions can be calculated from the set of fluxes through the interfaces between the cells. Although some methods of this type are exact for an arbitrary set of cells, in practice, the calculations will converge fastest when the interfaces are placed in regions where they can best capture transitions between configurations corresponding to local minima. The aim of this paper is to introduce a fully automated machine-learning algorithm for defining a set of cells for use in kinetic sampling methodologies based on subdividing the dynamical feature space; the algorithm requires no intuition about the system or input from the user and scales to high-dimensional systems.

Automated placement of interfaces in conformational kinetics calculations using machine learning.

PubMed

Grazioli, Gianmarc; Butts, Carter T; Andricioaei, Ioan

2017-10-21

Several recent implementations of algorithms for sampling reaction pathways employ a strategy for placing interfaces or milestones across the reaction coordinate manifold. Interfaces can be introduced such that the full feature space describing the dynamics of a macromolecule is divided into Voronoi (or other) cells, and the global kinetics of the molecular motions can be calculated from the set of fluxes through the interfaces between the cells. Although some methods of this type are exact for an arbitrary set of cells, in practice, the calculations will converge fastest when the interfaces are placed in regions where they can best capture transitions between configurations corresponding to local minima. The aim of this paper is to introduce a fully automated machine-learning algorithm for defining a set of cells for use in kinetic sampling methodologies based on subdividing the dynamical feature space; the algorithm requires no intuition about the system or input from the user and scales to high-dimensional systems.

A Method for Automated Detection of Usability Problems from Client User Interface Events

PubMed Central

Saadawi, Gilan M.; Legowski, Elizabeth; Medvedeva, Olga; Chavan, Girish; Crowley, Rebecca S.

2005-01-01

Think-aloud usability analysis provides extremely useful data but is very time-consuming and expensive to perform because of the extensive manual video analysis that is required. We describe a simple method for automated detection of usability problems from client user interface events for a developing medical intelligent tutoring system. The method incorporates (1) an agent-based method for communication that funnels all interface events and system responses to a centralized database, (2) a simple schema for representing interface events and higher order subgoals, and (3) an algorithm that reproduces the criteria used for manual coding of usability problems. A correction factor was empirically determining to account for the slower task performance of users when thinking aloud. We tested the validity of the method by simultaneously identifying usability problems using TAU and manually computing them from stored interface event data using the proposed algorithm. All usability problems that did not rely on verbal utterances were detectable with the proposed method. PMID:16779121

Molecular conformation of linear alkane molecules: From gas phase to bulk water through the interface

NASA Astrophysics Data System (ADS)

Murina, Ezequiel L.; Fernández-Prini, Roberto; Pastorino, Claudio

2017-08-01

We studied the behavior of long chain alkanes (LCAs) as they were transferred from gas to bulk water, through the liquid-vapor interface. These systems were studied using umbrella sampling molecular dynamics simulation and we have calculated properties like free energy profiles, molecular orientation, and radius of gyration of the LCA molecules. The results show changes in conformation of the solutes along the path. LCAs adopt pronounced molecular orientations and the larger ones extend appreciably when partially immersed in the interface. In bulk water, their conformations up to dodecane are mainly extended. However, larger alkanes like eicosane present a more stable collapsed conformation as they approach bulk water. We have characterized the more probable configurations in all interface and bulk regions. The results obtained are of interest for the study of biomatter processes requiring the transfer of hydrophobic matter, especially chain-like molecules like LCAs, from gas to bulk aqueous systems through the interface.

Real-Time Operating System/360

NASA Technical Reports Server (NTRS)

Hoffman, R. L.; Kopp, R. S.; Mueller, H. H.; Pollan, W. D.; Van Sant, B. W.; Weiler, P. W.

1969-01-01

RTOS has a cost savings advantage for real-time applications, such as those with random inputs requiring a flexible data routing facility, display systems simplified by a device independent interface language, and complex applications needing added storage protection and data queuing.

Assessing performance of an Electronic Health Record (EHR) using Cognitive Task Analysis.

PubMed

Saitwal, Himali; Feng, Xuan; Walji, Muhammad; Patel, Vimla; Zhang, Jiajie

2010-07-01

Many Electronic Health Record (EHR) systems fail to provide user-friendly interfaces due to the lack of systematic consideration of human-centered computing issues. Such interfaces can be improved to provide easy to use, easy to learn, and error-resistant EHR systems to the users. To evaluate the usability of an EHR system and suggest areas of improvement in the user interface. The user interface of the AHLTA (Armed Forces Health Longitudinal Technology Application) was analyzed using the Cognitive Task Analysis (CTA) method called GOMS (Goals, Operators, Methods, and Selection rules) and an associated technique called KLM (Keystroke Level Model). The GOMS method was used to evaluate the AHLTA user interface by classifying each step of a given task into Mental (Internal) or Physical (External) operators. This analysis was performed by two analysts independently and the inter-rater reliability was computed to verify the reliability of the GOMS method. Further evaluation was performed using KLM to estimate the execution time required to perform the given task through application of its standard set of operators. The results are based on the analysis of 14 prototypical tasks performed by AHLTA users. The results show that on average a user needs to go through 106 steps to complete a task. To perform all 14 tasks, they would spend about 22 min (independent of system response time) for data entry, of which 11 min are spent on more effortful mental operators. The inter-rater reliability analysis performed for all 14 tasks was 0.8 (kappa), indicating good reliability of the method. This paper empirically reveals and identifies the following finding related to the performance of AHLTA: (1) large number of average total steps to complete common tasks, (2) high average execution time and (3) large percentage of mental operators. The user interface can be improved by reducing (a) the total number of steps and (b) the percentage of mental effort, required for the tasks. 2010 Elsevier Ireland Ltd. All rights reserved.

Local intelligent electronic device (IED) rendering templates over limited bandwidth communication link to manage remote IED

DOEpatents

Bradetich, Ryan; Dearien, Jason A; Grussling, Barry Jakob; Remaley, Gavin

2013-11-05

The present disclosure provides systems and methods for remote device management. According to various embodiments, a local intelligent electronic device (IED) may be in communication with a remote IED via a limited bandwidth communication link, such as a serial link. The limited bandwidth communication link may not support traditional remote management interfaces. According to one embodiment, a local IED may present an operator with a management interface for a remote IED by rendering locally stored templates. The local IED may render the locally stored templates using sparse data obtained from the remote IED. According to various embodiments, the management interface may be a web client interface and/or an HTML interface. The bandwidth required to present a remote management interface may be significantly reduced by rendering locally stored templates rather than requesting an entire management interface from the remote IED. According to various embodiments, an IED may comprise an encryption transceiver.

User interface for a tele-operated robotic hand system

DOEpatents

Crawford, Anthony L

2015-03-24

Disclosed here is a user interface for a robotic hand. The user interface anchors a user's palm in a relatively stationary position and determines various angles of interest necessary for a user's finger to achieve a specific fingertip location. The user interface additionally conducts a calibration procedure to determine the user's applicable physiological dimensions. The user interface uses the applicable physiological dimensions and the specific fingertip location, and treats the user's finger as a two link three degree-of-freedom serial linkage in order to determine the angles of interest. The user interface communicates the angles of interest to a gripping-type end effector which closely mimics the range of motion and proportions of a human hand. The user interface requires minimal contact with the operator and provides distinct advantages in terms of available dexterity, work space flexibility, and adaptability to different users.

48 CFR 2942.1502 - Policy.

Code of Federal Regulations, 2014 CFR

2014-10-01

... ADMINISTRATION AND AUDIT SERVICES Contractor Performance Information 2942.1502 Policy. DOL contracting officers are required to use or interface with the Past Performance Information Retrieval System (PPIRS), and...

48 CFR 2942.1502 - Policy.

Code of Federal Regulations, 2011 CFR

2011-10-01

... ADMINISTRATION AND AUDIT SERVICES Contractor Performance Information 2942.1502 Policy. DOL contracting officers are required to use or interface with the Past Performance Information Retrieval System (PPIRS), and...

48 CFR 2942.1502 - Policy.

Code of Federal Regulations, 2010 CFR

2010-10-01

... ADMINISTRATION AND AUDIT SERVICES Contractor Performance Information 2942.1502 Policy. DOL contracting officers are required to use or interface with the Past Performance Information Retrieval System (PPIRS), and...

48 CFR 2942.1502 - Policy.

Code of Federal Regulations, 2012 CFR

2012-10-01

... ADMINISTRATION AND AUDIT SERVICES Contractor Performance Information 2942.1502 Policy. DOL contracting officers are required to use or interface with the Past Performance Information Retrieval System (PPIRS), and...

48 CFR 2942.1502 - Policy.

Code of Federal Regulations, 2013 CFR

2013-10-01

... ADMINISTRATION AND AUDIT SERVICES Contractor Performance Information 2942.1502 Policy. DOL contracting officers are required to use or interface with the Past Performance Information Retrieval System (PPIRS), and...

Space Station module Power Management And Distribution (PMAD) system

NASA Technical Reports Server (NTRS)

Walls, Bryan

1990-01-01

This project consists of several tasks which are unified toward experimentally demonstrating the operation of a highly autonomous, user-supportive power management and distribution system for Space Station Freedom (SSF) habitation/laboratory modules. This goal will be extended to a demonstration of autonomous, cooperative power system operation for the whole SSF power system through a joint effort with NASA's Lewis Research Center, using their Autonomous Power System. Short term goals for the space station module power management and distribution include having an operational breadboard reflecting current plans for SSF, improving performance of the system communications, and improving the organization and mutability of the artificial intelligence (AI) systems. In the middle term, intermediate levels of autonomy will be added, user interfaces will be modified, and enhanced modeling capabilities will be integrated in the system. Long term goals involve conversion of all software into Ada, vigorous verification and validation efforts and, finally, seeing an impact of this research on the operation of SSF. Conversion of the system to a DC Star configuration is now in progress, and should be completed by the end of October, 1989. This configuration reflects the latest SSF module architecture. Hardware is now being procured which will improve system communications significantly. The Knowledge-Based Management System (KBMS) is initially developed and the rules from FRAMES have been implemented in the KBMS. Rules in the other two AI systems are also being grouped modularly, making them more tractable, and easier to eventually move into the KBMS. Adding an intermediate level of autonomy will require development of a planning utility, which will also be built using the KBMS. These changes will require having the user interface for the whole system available from one interface. An Enhanced Model will be developed, which will allow exercise of the system through the interface without requiring all of the power hardware to be operational. The functionality of the AI systems will continue to be advanced, including incipient failure detection. Ada conversion will begin with the lowest level processor (LLP) code. Then selected pieces of the higher level functionality will be recorded in Ada and, where possible, moved to the LLP level. Validation and verification will be done on the Ada code, and will complete sometimes after completion of the Ada conversion.

Adaptive interface for personalizing information seeking.

PubMed

Narayanan, S; Koppaka, Lavanya; Edala, Narasimha; Loritz, Don; Daley, Raymond

2004-12-01

An adaptive interface autonomously adjusts its display and available actions to current goals and abilities of the user by assessing user status, system task, and the context. Knowledge content adaptability is needed for knowledge acquisition and refinement tasks. In the case of knowledge content adaptability, the requirements of interface design focus on the elicitation of information from the user and the refinement of information based on patterns of interaction. In such cases, the emphasis on adaptability is on facilitating information search and knowledge discovery. In this article, we present research on adaptive interfaces that facilitates personalized information seeking from a large data warehouse. The resulting proof-of-concept system, called source recommendation system (SRS), assists users in locating and navigating data sources in the repository. Based on the initial user query and an analysis of the content of the search results, the SRS system generates a profile of the user tailored to the individual's context during information seeking. The user profiles are refined successively and are used in progressively guiding the user to the appropriate set of sources within the knowledge base. The SRS system is implemented as an Internet browser plug-in to provide a seamless and unobtrusive, personalized experience to the users during the information search process. The rationale behind our approach, system design, empirical evaluation, and implications for research on adaptive interfaces are described in this paper.

Civilian Radioactive Waste Management System Requirements Document

DOE Office of Scientific and Technical Information (OSTI.GOV)

C.A. Kouts

2006-05-10

The CRD addresses the requirements of Department of Energy (DOE) Order 413.3-Change 1, ''Program and Project Management for the Acquisition of Capital Assets'', by providing the Secretarial Acquisition Executive (Level 0) scope baseline and the Program-level (Level 1) technical baseline. The Secretarial Acquisition Executive approves the Office of Civilian Radioactive Waste Management's (OCRWM) critical decisions and changes against the Level 0 baseline; and in turn, the OCRWM Director approves all changes against the Level 1 baseline. This baseline establishes the top-level technical scope of the CRMWS and its three system elements, as described in section 1.3.2. The organizations responsible formore » design, development, and operation of system elements described in this document must therefore prepare subordinate project-level documents that are consistent with the CRD. Changes to requirements will be managed in accordance with established change and configuration control procedures. The CRD establishes requirements for the design, development, and operation of the CRWMS. It specifically addresses the top-level governing laws and regulations (e.g., ''Nuclear Waste Policy Act'' (NWPA), 10 Code of Federal Regulations (CFR) Part 63, 10 CFR Part 71, etc.) along with specific policy, performance requirements, interface requirements, and system architecture. The CRD shall be used as a vehicle to incorporate specific changes in technical scope or performance requirements that may have significant program implications. Such may include changes to the program mission, changes to operational capability, and high visibility stakeholder issues. The CRD uses a systems approach to: (1) identify key functions that the CRWMS must perform, (2) allocate top-level requirements derived from statutory, regulatory, and programmatic sources, and (3) define the basic elements of the system architecture and operational concept. Project-level documents address CRD requirements by further defining system element functions, decomposing requirements into significantly greater detail, and developing designs of system components, facilities, and equipment. The CRD addresses the identification and control of functional, physical, and operational boundaries between and within CRWMS elements. The CRD establishes requirements regarding key interfaces between the CRWMS and elements external to the CRWMS. Project elements define interfaces between CRWMS program elements. The Program has developed a change management process consistent with DOE Order 413.3-Change 1. Changes to the Secretarial Acquisition Executive and Program-level baselines must be approved by a Program Baseline Change Control Board. Specific thresholds have been established for identifying technical, cost, and schedule changes that require approval. The CRWMS continually evaluates system design and operational concepts to optimize performance and/or cost. The Program has developed systems analysis tools to assess potential enhancements to the physical system and to determine the impacts from cost saving initiatives, scientific and technological improvements, and engineering developments. The results of systems analyses, if appropriate, are factored into revisions to the CRD as revised Programmatic Requirements.« less

Visual communication interface for severe physically disabled patients

NASA Astrophysics Data System (ADS)

Savino, M. J.; Fernández, E. A.

2007-11-01

During the last years several interfaces have been developed to allow communication to those patients suffering serious physical disabilities. In this work, a computer based communication interface is presented. It was designed to allow communication to those patients that cannot use neither their hands nor their voice but they can do it through their eyes. The system monitors the eyes movements by means of a webcam. Then, by means of an Artificial Neural Network, the system allows the identification of specified position on the screen through the identification of the eyes positions. This way the user can control a virtual keyboard on a screen that allows him to write and browse the system and enables him to send e-mails, SMS, activate video/music programs and control environmental devices. A patient was simulated to evaluate the versatility of the system. Its operation was satisfactory and it allowed the evaluation of the system potential. The development of this system requires low cost elements that are easily found in the market.

Process for Selecting System Level Assessments for Human System Technologies

NASA Technical Reports Server (NTRS)

Watts, James; Park, John

2006-01-01

The integration of many life support systems necessary to construct a stable habitat is difficult. The correct identification of the appropriate technologies and corresponding interfaces is an exhaustive process. Once technologies are selected secondary issues such as mechanical and electrical interfaces must be addressed. The required analytical and testing work must be approached in a piecewise fashion to achieve timely results. A repeatable process has been developed to identify and prioritize system level assessments and testing needs. This Assessment Selection Process has been defined to assess cross cutting integration issues on topics at the system or component levels. Assessments are used to identify risks, encourage future actions to mitigate risks, or spur further studies.

Network Control Center User Planning System (NCC UPS)

NASA Astrophysics Data System (ADS)

Dealy, Brian

1991-09-01

NCC UPS is presented in the form of the viewgraphs. The following subject areas are covered: UPS overview; NCC UPS role; major NCC UPS functional requirements; interactive user access levels; UPS interfaces; interactive user subsystem; interface navigation; scheduling screen hierarchy; interactive scheduling input panels; autogenerated schedule request panel; schedule data tabular display panel; schedule data graphic display panel; graphic scheduling aid design; and schedule data graphic display.

Network Control Center User Planning System (NCC UPS)

NASA Technical Reports Server (NTRS)

Dealy, Brian

1991-01-01

NCC UPS is presented in the form of the viewgraphs. The following subject areas are covered: UPS overview; NCC UPS role; major NCC UPS functional requirements; interactive user access levels; UPS interfaces; interactive user subsystem; interface navigation; scheduling screen hierarchy; interactive scheduling input panels; autogenerated schedule request panel; schedule data tabular display panel; schedule data graphic display panel; graphic scheduling aid design; and schedule data graphic display.

Software components for medical image visualization and surgical planning

NASA Astrophysics Data System (ADS)

Starreveld, Yves P.; Gobbi, David G.; Finnis, Kirk; Peters, Terence M.

2001-05-01

Purpose: The development of new applications in medical image visualization and surgical planning requires the completion of many common tasks such as image reading and re-sampling, segmentation, volume rendering, and surface display. Intra-operative use requires an interface to a tracking system and image registration, and the application requires basic, easy to understand user interface components. Rapid changes in computer and end-application hardware, as well as in operating systems and network environments make it desirable to have a hardware and operating system as an independent collection of reusable software components that can be assembled rapidly to prototype new applications. Methods: Using the OpenGL based Visualization Toolkit as a base, we have developed a set of components that implement the above mentioned tasks. The components are written in both C++ and Python, but all are accessible from Python, a byte compiled scripting language. The components have been used on the Red Hat Linux, Silicon Graphics Iris, Microsoft Windows, and Apple OS X platforms. Rigorous object-oriented software design methods have been applied to ensure hardware independence and a standard application programming interface (API). There are components to acquire, display, and register images from MRI, MRA, CT, Computed Rotational Angiography (CRA), Digital Subtraction Angiography (DSA), 2D and 3D ultrasound, video and physiological recordings. Interfaces to various tracking systems for intra-operative use have also been implemented. Results: The described components have been implemented and tested. To date they have been used to create image manipulation and viewing tools, a deep brain functional atlas, a 3D ultrasound acquisition and display platform, a prototype minimally invasive robotic coronary artery bypass graft planning system, a tracked neuro-endoscope guidance system and a frame-based stereotaxy neurosurgery planning tool. The frame-based stereotaxy module has been licensed and certified for use in a commercial image guidance system. Conclusions: It is feasible to encapsulate image manipulation and surgical guidance tasks in individual, reusable software modules. These modules allow for faster development of new applications. The strict application of object oriented software design methods allows individual components of such a system to make the transition from the research environment to a commercial one.

Basic concepts and development of an all-purpose computer interface for ROC/FROC observer study.

PubMed

Shiraishi, Junji; Fukuoka, Daisuke; Hara, Takeshi; Abe, Hiroyuki

2013-01-01

In this study, we initially investigated various aspects of requirements for a computer interface employed in receiver operating characteristic (ROC) and free-response ROC (FROC) observer studies which involve digital images and ratings obtained by observers (radiologists). Secondly, by taking into account these aspects, an all-purpose computer interface utilized for these observer performance studies was developed. Basically, the observer studies can be classified into three paradigms, such as one rating for one case without an identification of a signal location, one rating for one case with an identification of a signal location, and multiple ratings for one case with identification of signal locations. For these paradigms, display modes on the computer interface can be used for single/multiple views of a static image, continuous viewing with cascade images (i.e., CT, MRI), and dynamic viewing of movies (i.e., DSA, ultrasound). Various functions on these display modes, which include windowing (contrast/level), magnifications, and annotations, are needed to be selected by an experimenter corresponding to the purpose of the research. In addition, the rules of judgment for distinguishing between true positives and false positives are an important factor for estimating diagnostic accuracy in an observer study. We developed a computer interface which runs on a Windows operating system by taking into account all aspects required for various observer studies. This computer interface requires experimenters to have sufficient knowledge about ROC/FROC observer studies, but allows its use for any purpose of the observer studies. This computer interface will be distributed publicly in the near future.

A mobile field-work data collection system for the wireless era of health surveillance.

PubMed

Forsell, Marianne; Sjögren, Petteri; Renard, Matthew; Johansson, Olle

2011-03-01

In many countries or regions the capacity of health care resources is below the needs of the population and new approaches for health surveillance are needed. Innovative projects, utilizing wireless communication technology, contribute to reliable methods for field-work data collection and reporting to databases. The objective was to describe a new version of a wireless IT-support system for field-work data collection and administration. The system requirements were drawn from the design objective and translated to system functions. The system architecture was based on fieldwork experiences and administrative requirements. The Smartphone devices were HTC Touch Diamond2s, while the system was based on a platform with Microsoft .NET components, and a SQL Server 2005 with Microsoft Windows Server 2003 operating system. The user interfaces were based on .NET programming, and Microsoft Windows Mobile operating system. A synchronization module enabled download of field data to the database, via a General Packet Radio Services (GPRS) to a Local Area Network (LAN) interface. The field-workers considered the here-described applications user-friendly and almost self-instructing. The office administrators considered that the back-office interface facilitated retrieval of health reports and invoice distribution. The current IT-support system facilitates short lead times from fieldwork data registration to analysis, and is suitable for various applications. The advantages of wireless technology, and paper-free data administration need to be increasingly emphasized in development programs, in order to facilitate reliable and transparent use of limited resources.

Software systems for modeling articulated figures

NASA Technical Reports Server (NTRS)

Phillips, Cary B.

1989-01-01

Research in computer animation and simulation of human task performance requires sophisticated geometric modeling and user interface tools. The software for a research environment should present the programmer with a powerful but flexible substrate of facilities for displaying and manipulating geometric objects, yet insure that future tools have a consistent and friendly user interface. Jack is a system which provides a flexible and extensible programmer and user interface for displaying and manipulating complex geometric figures, particularly human figures in a 3D working environment. It is a basic software framework for high-performance Silicon Graphics IRIS workstations for modeling and manipulating geometric objects in a general but powerful way. It provides a consistent and user-friendly interface across various applications in computer animation and simulation of human task performance. Currently, Jack provides input and control for applications including lighting specification and image rendering, anthropometric modeling, figure positioning, inverse kinematics, dynamic simulation, and keyframe animation.

Evaluation of the Next-Gen Exercise Software Interface in the NEEMO Analog

NASA Technical Reports Server (NTRS)

Hanson, Andrea; Kalogera, Kent; Sandor, Aniko; Hardy, Marc; Frank, Andrew; English, Kirk; Williams, Thomas; Perera, Jeevan; Amonette, William

2017-01-01

NSBRI (National Space Biomedical Research Institute) funded research grant to develop the 'NextGen' exercise software for the NEEMO (NASA Extreme Environment Mission Operations) analog. Develop a software architecture to integrate instructional, motivational and socialization techniques into a common portal to enhance exercise countermeasures in remote environments. Increase user efficiency and satisfaction, and institute commonality across multiple exercise systems. Utilized GUI (Graphical User Interface) design principals focused on intuitive ease of use to minimize training time and realize early user efficiency. Project requirement to test the software in an analog environment. Top Level Project Aims: 1) Improve the usability of crew interface software to exercise CMS (Crew Management System) through common app-like interfaces. 2) Introduce virtual instructional motion training. 3) Use virtual environment to provide remote socialization with family and friends, improve exercise technique, adherence, motivation and ultimately performance outcomes.

Geostationary platform systems concepts definition study. Volume 2: Technical, book 3

NASA Technical Reports Server (NTRS)

1980-01-01

The supporting research and technology, and space demonstrations required to support the 1990s operational geostationary platforms are identified. Also the requirements on and interfaces with the Space Transportation System hardware elements supporting the geostationary platform program, including the shuttle, orbital transfer vehicles, teleoperator, etc., are investigated to provide integrated support requirements. Finally, a preliminary evaluation of the practicability and capabilities of an experimental platform from the standpoint of technology, schedule, and cost is given.

User interface support

NASA Technical Reports Server (NTRS)

Lewis, Clayton; Wilde, Nick

1989-01-01

Space construction will require heavy investment in the development of a wide variety of user interfaces for the computer-based tools that will be involved at every stage of construction operations. Using today's technology, user interface development is very expensive for two reasons: (1) specialized and scarce programming skills are required to implement the necessary graphical representations and complex control regimes for high-quality interfaces; (2) iteration on prototypes is required to meet user and task requirements, since these are difficult to anticipate with current (and foreseeable) design knowledge. We are attacking this problem by building a user interface development tool based on extensions to the spreadsheet model of computation. The tool provides high-level support for graphical user interfaces and permits dynamic modification of interfaces, without requiring conventional programming concepts and skills.

The Human Resources Management System: Part 1.

ERIC Educational Resources Information Center

Ceriello, Vincent R.

1982-01-01

Presents a systematic and disciplined approach to planning for the development and implementation of an information system which will collect, store, maintain, and report human resources data. Discusses guidelines, priorities, training requirements, security, auditing, interface with payroll, and personnel reporting. (CT)

A revisit to the requirements methodologies for services provided by the Office of Space Communications

NASA Technical Reports Server (NTRS)

Fishkind, Stanley; Harris, Richard N.; Pfeiffer, William A.

1996-01-01

The methodologies of the NASA requirements processing system, originally designed to enhance NASA's customer interface and response time, are reviewed. The response of NASA to the problems associated with the system is presented, and it is shown what was done to facilitate the process and to improve customer relations. The requirements generation system (RGS), a computer-supported client-server system, adopted by NASA is presented. The RGS system is configurable on a per-mission basis and can be structured to allow levels of requirements. The details provided concerning the RGS include the recommended configuration, information on becoming an RGS user and network connectivity worksheets for computer users.

Space tug point design study. Volume 2: Operations, performance and requirements

NASA Technical Reports Server (NTRS)

1973-01-01

A design study to determine the configuration and characteristics of a space tug was conducted. Among the subjects analyzed in the study are: (1) flight and ground operations, (2) vehicle flight performance and performance enhancement techniques, (3) flight requirements, (4) basic design criteria, and (5) functional and procedural interface requirements between the tug and other systems.

STS-2: SAIL non-avionics subsystems math model requirements

NASA Technical Reports Server (NTRS)

Bennett, W. P.; Herold, R. W.

1980-01-01

Simulation of the STS-2 Shuttle nonavionics subsystems in the shuttle avionics integration laboratory (SAIL) is necessary for verification of the integrated shuttle avionics system. The math model (simulation) requirements for each of the nonavionics subsystems that interfaces with the Shuttle avionics system is documented and a single source document for controlling approved changes (by the SAIL change control panel) to the math models is provided.

Earth orbital teleoperator visual system evaluation program

NASA Technical Reports Server (NTRS)

Shields, N. L., Jr.; Kirkpatrick, M., III; Frederick, P. N.; Malone, T. B.

1975-01-01

Empirical tests of range estimation accuracy and resolution, via television, under monoptic and steroptic viewing conditions are discussed. Test data are used to derive man machine interface requirements and make design decisions for an orbital remote manipulator system. Remote manipulator system visual tasks are given and the effects of system parameters of these tasks are evaluated.

Space shuttle engineering and operations support. Avionics system engineering

NASA Technical Reports Server (NTRS)

Broome, P. A.; Neubaur, R. J.; Welsh, R. T.

1976-01-01

The shuttle avionics integration laboratory (SAIL) requirements for supporting the Spacelab/orbiter avionics verification process are defined. The principal topics are a Spacelab avionics hardware assessment, test operations center/electronic systems test laboratory (TOC/ESL) data processing requirements definition, SAIL (Building 16) payload accommodations study, and projected funding and test scheduling. Because of the complex nature of the Spacelab/orbiter computer systems, the PCM data link, and the high rate digital data system hardware/software relationships, early avionics interface verification is required. The SAIL is a prime candidate test location to accomplish this early avionics verification.

Science and Technology Education in the STES Context in Primary Schools: What Should It Take?

ERIC Educational Resources Information Center

Zoller, Uri

2011-01-01

Striving for sustainability requires a paradigm shift in conceptualization, thinking, research and education, particularly concerning the science-technology-environment-society (STES) interfaces. Consequently, "STES literacy" requires the development of students' question asking, critical, evaluative system thinking, decision making and problem…

Air Force System Safety Handbook, Designing the Safest Possible Systems Consistent with Mission Requirements and Cost Effectiveness

DTIC Science & Technology

2000-07-01

acceptance is not as simple a matter as it may first appear. Several points must be kept in mind. (1) Risk is a fundamental reality . (2) Risk...1) Proper preparation of an SSPP requires coming to grips with the hard realities of program execution. It involves the exami- nation and...Interfaces. (32:48) Since the conduct of a system safety program will eventually touch on virtually every other element of a system devel- opment program, a

Managing computer-controlled operations

NASA Technical Reports Server (NTRS)

Plowden, J. B.

1985-01-01

A detailed discussion of Launch Processing System Ground Software Production is presented to establish the interrelationships of firing room resource utilization, configuration control, system build operations, and Shuttle data bank management. The production of a test configuration identifier is traced from requirement generation to program development. The challenge of the operational era is to implement fully automated utilities to interface with a resident system build requirements document to eliminate all manual intervention in the system build operations. Automatic update/processing of Shuttle data tapes will enhance operations during multi-flow processing.

Matching brain-machine interface performance to space applications.

PubMed

Citi, Luca; Tonet, Oliver; Marinelli, Martina

2009-01-01

A brain-machine interface (BMI) is a particular class of human-machine interface (HMI). BMIs have so far been studied mostly as a communication means for people who have little or no voluntary control of muscle activity. For able-bodied users, such as astronauts, a BMI would only be practical if conceived as an augmenting interface. A method is presented for pointing out effective combinations of HMIs and applications of robotics and automation to space. Latency and throughput are selected as performance measures for a hybrid bionic system (HBS), that is, the combination of a user, a device, and a HMI. We classify and briefly describe HMIs and space applications and then compare the performance of classes of interfaces with the requirements of classes of applications, both in terms of latency and throughput. Regions of overlap correspond to effective combinations. Devices requiring simpler control, such as a rover, a robotic camera, or environmental controls are suitable to be driven by means of BMI technology. Free flyers and other devices with six degrees of freedom can be controlled, but only at low-interactivity levels. More demanding applications require conventional interfaces, although they could be controlled by BMIs once the same levels of performance as currently recorded in animal experiments are attained. Robotic arms and manipulators could be the next frontier for noninvasive BMIs. Integrating smart controllers in HBSs could improve interactivity and boost the use of BMI technology in space applications.

The System Dynamics Model User Sustainability Explorer (SD-MUSE) user interface: a user-friendly tool for interpreting system dynamic models

EPA Science Inventory

Sustainability-based decision making is a challenging process that requires balancing trade-offs among social, economic, and environmental components. System Dynamic (SD) models can be useful tools to inform sustainability-based decision making because they provide a holistic co...

Intelligent CAI: An Author Aid for a Natural Language Interface.

ERIC Educational Resources Information Center

Burton, Richard R.; Brown, John Seely

This report addresses the problems of using natural language (English) as the communication language for advanced computer-based instructional systems. The instructional environment places requirements on a natural language understanding system that exceed the capabilities of all existing systems, including: (1) efficiency, (2) habitability, (3)…

Manipulator system man-machine interface evaluation program. [technology assessment

NASA Technical Reports Server (NTRS)

Malone, T. B.; Kirkpatrick, M.; Shields, N. L.

1974-01-01

Application and requirements for remote manipulator systems for future space missions were investigated. A manipulator evaluation program was established to study the effects of various systems parameters on operator performance of tasks necessary for remotely manned missions. The program and laboratory facilities are described. Evaluation criteria and philosophy are discussed.

Towards Intelligent Environments: An Augmented Reality–Brain–Machine Interface Operated with a See-Through Head-Mount Display

PubMed Central

Takano, Kouji; Hata, Naoki; Kansaku, Kenji

2011-01-01

The brain–machine interface (BMI) or brain–computer interface is a new interface technology that uses neurophysiological signals from the brain to control external machines or computers. This technology is expected to support daily activities, especially for persons with disabilities. To expand the range of activities enabled by this type of interface, here, we added augmented reality (AR) to a P300-based BMI. In this new system, we used a see-through head-mount display (HMD) to create control panels with flicker visual stimuli to support the user in areas close to controllable devices. When the attached camera detects an AR marker, the position and orientation of the marker are calculated, and the control panel for the pre-assigned appliance is created by the AR system and superimposed on the HMD. The participants were required to control system-compatible devices, and they successfully operated them without significant training. Online performance with the HMD was not different from that using an LCD monitor. Posterior and lateral (right or left) channel selections contributed to operation of the AR–BMI with both the HMD and LCD monitor. Our results indicate that AR–BMI systems operated with a see-through HMD may be useful in building advanced intelligent environments. PMID:21541307

Space station Simulation Computer System (SCS) study for NASA/MSFC. Volume 2: Concept document

NASA Technical Reports Server (NTRS)

1989-01-01

The Simulation Computer System (SCS) concept document describes and establishes requirements for the functional performance of the SCS system, including interface, logistic, and qualification requirements. The SCS is the computational communications and display segment of the Marshall Space Flight Center (MSFC) Payload Training Complex (PTC). The PTC is the MSFC facility that will train onboard and ground operations personnel to operate the payloads and experiments on board the international Space Station Freedom. The requirements to be satisfied by the system implementation are identified here. The SCS concept document defines the requirements to be satisfied through the implementation of the system capability. The information provides the operational basis for defining the requirements to be allocated to the system components and enables the system organization to assess whether or not the completed system complies with the requirements of the system.

Detailed requirements document for the integrated structural analysis system, phase B

NASA Technical Reports Server (NTRS)

Rainey, J. A.

1976-01-01

The requirements are defined for a software system entitled integrated Structural Analysis System (ISAS) Phase B which is being developed to provide the user with a tool by which a complete and detailed analysis of a complex structural system can be performed. This software system will allow for automated interface with numerous structural analysis batch programs and for user interaction in the creation, selection, and validation of data. This system will include modifications to the 4 functions developed for ISAS, and the development of 25 new functions. The new functions are described.

Service offerings and interfaces for the ACTS network of earth stations

NASA Technical Reports Server (NTRS)

Coney, T. A.; Dobyns, T. R.; Chitre, D. M.; Lindstrom, R.

1988-01-01

The NASA Advanced Communications Technology Satellite (ACTS) will use a network of about 20 earth stations to operate as a Mode 1 network. This network will support two ACTS program objectives: to verify the technical performance of ACTS Mode 1 operation in GEO and to demonstrate the types and quality of services that can be provided by an ACTS Mode 1 communications system. The terrestrial interface design is a critical element in assuring that these network earth stations will meet the objectives. In this paper, the applicable terrestrial interface design requirements, the resulting interface specifications, and the associated terrestrial input/output hardware are discussed. A functional block diagram of a network earth station is shown.

TELICS—A Telescope Instrument Control System for Small/Medium Sized Astronomical Observatories

NASA Astrophysics Data System (ADS)

Srivastava, Mudit K.; Ramaprakash, A. N.; Burse, Mahesh P.; Chordia, Pravin A.; Chillal, Kalpesh S.; Mestry, Vilas B.; Das, Hillol K.; Kohok, Abhay A.

2009-10-01

For any modern astronomical observatory, it is essential to have an efficient interface between the telescope and its back-end instruments. However, for small and medium-sized observatories, this requirement is often limited by tight financial constraints. Therefore a simple yet versatile and low-cost control system is required for such observatories to minimize cost and effort. Here we report the development of a modern, multipurpose instrument control system TELICS (Telescope Instrument Control System) to integrate the controls of various instruments and devices mounted on the telescope. TELICS consists of an embedded hardware unit known as a common control unit (CCU) in combination with Linux-based data acquisition and user interface. The hardware of the CCU is built around the ATmega 128 microcontroller (Atmel Corp.) and is designed with a backplane, master-slave architecture. A Qt-based graphical user interface (GUI) has been developed and the back-end application software is based on C/C++. TELICS provides feedback mechanisms that give the operator good visibility and a quick-look display of the status and modes of instruments as well as data. TELICS has been used for regular science observations since 2008 March on the 2 m, f/10 IUCAA Telescope located at Girawali in Pune, India.

Infrared Imagery of Shuttle (IRIS). Task 1

NASA Technical Reports Server (NTRS)

Chocol, C. J.

1977-01-01

Assessment of available IR sensor technology showed that the four aerothermodynamic conditions of interest during the entry trajectory of space shuttle can be accommodated by an aircraft flying parallel to the orbiter reentry ground track. Thermal information from the sides of the vehicle can be obtained with degraded performance (temperatures below 800 K) by flying the C-141 aircraft on the opposite side of the shuttle ground track and in the direction opposite that which is optimum for lower surface viewing. An acquisition system using a 6.25-cm aperture telescope and a single indium antimonide detector were designed to meet the acquisition requirements and interface with the 91.5-cm telescope with minimum modification. An image plane system using 600 indium antimonide detectors in two arrays which requires no modification to the existing telescope was also designed. Currently available components were used in a data handling system with interfaces with the experimentors station and the HP2100 computer.

Versioned distributed arrays for resilience in scientific applications: Global view resilience

DOE PAGES

Chien, A.; Balaji, P.; Beckman, P.; ...

2015-06-01

Exascale studies project reliability challenges for future high-performance computing (HPC) systems. We propose the Global View Resilience (GVR) system, a library that enables applications to add resilience in a portable, application-controlled fashion using versioned distributed arrays. We describe GVR’s interfaces to distributed arrays, versioning, and cross-layer error recovery. Using several large applications (OpenMC, the preconditioned conjugate gradient solver PCG, ddcMD, and Chombo), we evaluate the programmer effort to add resilience. The required changes are small (<2% LOC), localized, and machine-independent, requiring no software architecture changes. We also measure the overhead of adding GVR versioning and show that generally overheads <2%more » are achieved. We conclude that GVR’s interfaces and implementation are flexible and portable and create a gentle-slope path to tolerate growing error rates in future systems.« less

High density, multi-range analog output Versa Module Europa board for control system applications

DOE Office of Scientific and Technical Information (OSTI.GOV)

Singh, Kundan, E-mail: kundan@iuac.res.in; Das, Ajit Lal

2014-01-15

A new VMEDAC64, 12-bit 64 channel digital-to-analog converter, a Versa Module Europa (VME) module, features 64 analog voltage outputs with user selectable multiple ranges, has been developed for control system applications at Inter University Accelerator Centre. The FPGA (Field Programmable Gate Array) is the module's core, i.e., it implements the DAC control logic and complexity of VMEbus slave interface logic. The VMEbus slave interface and DAC control logic are completely designed and implemented on a single FPGA chip to achieve high density of 64 channels in a single width VME module and will reduce the module count in the controlmore » system applications, and hence will reduce the power consumption and cost of overall system. One of our early design goals was to develop the VME interface such that it can be easily integrated with the peripheral devices and satisfy the timing specifications of VME standard. The modular design of this module reduces the amount of time required to develop other custom modules for control system. The VME slave interface is written as a single component inside FPGA which will be used as a basic building block for any VMEbus interface project. The module offers multiple output voltage ranges depending upon the requirement. The output voltage range can be reduced or expanded by writing range selection bits in the control register. The module has programmable refresh rate and by default hold capacitors in the sample and hold circuit for each channel are charged periodically every 7.040 ms (i.e., update frequency 284 Hz). Each channel has software controlled output switch which disconnects analog output from the field. The modularity in the firmware design on FPGA makes the debugging very easy. On-board DC/DC converters are incorporated for isolated power supply for the analog section of the board.« less

Simplifying the interaction between cognitive models and task environments with the JSON Network Interface.

PubMed

Hope, Ryan M; Schoelles, Michael J; Gray, Wayne D

2014-12-01

Process models of cognition, written in architectures such as ACT-R and EPIC, should be able to interact with the same software with which human subjects interact. By eliminating the need to simulate the experiment, this approach would simplify the modeler's effort, while ensuring that all steps required of the human are also required by the model. In practice, the difficulties of allowing one software system to interact with another present a significant barrier to any modeler who is not also skilled at this type of programming. The barrier increases if the programming language used by the modeling software differs from that used by the experimental software. The JSON Network Interface simplifies this problem for ACT-R modelers, and potentially, modelers using other systems.

Transparent Information Systems through Gateways, Front Ends, Intermediaries, and Interfaces.

ERIC Educational Resources Information Center

Williams, Martha E.

1986-01-01

Provides overview of design requirements for transparent information retrieval (implies that user sees through complexity of retrieval activities sequence). Highlights include need for transparent systems; history of transparent retrieval research; information retrieval functions (automated converters, routers, selectors, evaluators/analyzers);…

Front-End/Gateway Software: Availability and Usefulness.

ERIC Educational Resources Information Center

Kesselman, Martin

1985-01-01

Reviews features of front-end software packages (interface between user and online system)--database selection, search strategy development, saving and downloading, hardware and software requirements, training and documentation, online systems and database accession, and costs--and discusses gateway services (user searches through intermediary…

Synthesis and analysis of precise spaceborne laser ranging systems, volume 2. [Spacelab payload

NASA Technical Reports Server (NTRS)

Paddon, E. A.

1978-01-01

The performance capabilities of specific shuttle-based laser ranging systems were evaluated, and interface and support requirements were determined. The preliminary design of a shuttle-borne laser ranging experiment developed as part of the Spacelab program is discussed.

Laboratory process control using natural language commands from a personal computer

NASA Technical Reports Server (NTRS)

Will, Herbert A.; Mackin, Michael A.

1989-01-01

PC software is described which provides flexible natural language process control capability with an IBM PC or compatible machine. Hardware requirements include the PC, and suitable hardware interfaces to all controlled devices. Software required includes the Microsoft Disk Operating System (MS-DOS) operating system, a PC-based FORTRAN-77 compiler, and user-written device drivers. Instructions for use of the software are given as well as a description of an application of the system.

Online Access to Weather Satellite Imagery Through the World Wide Web

NASA Technical Reports Server (NTRS)

Emery, W.; Baldwin, D.

1998-01-01

Both global area coverage (GAC) and high-resolution picture transmission (HRTP) data from the Advanced Very High Resolution Radiometer (AVHRR) are made available to laternet users through an online data access system. Older GOES-7 data am also available. Created as a "testbed" data system for NASA's future Earth Observing System Data and Information System (EOSDIS), this testbed provides an opportunity to test both the technical requirements of an onune'd;ta system and the different ways in which the -general user, community would employ such a system. Initiated in December 1991, the basic data system experienced five major evolutionary changes In response to user requests and requirements. Features added with these changes were the addition of online browse, user subsetting, dynamic image Processing/navigation, a stand-alone data storage system, and movement,from an X-windows graphical user Interface (GUI) to a World Wide Web (WWW) interface. Over Its lifetime, the system has had as many as 2500 registered users. The system on the WWW has had over 2500 hits since October 1995. Many of these hits are by casual users that only take the GIF images directly from the interface screens and do not specifically order digital data. Still, there b a consistent stream of users ordering the navigated image data and related products (maps and so forth). We have recently added a real-time, seven- day, northwestern United States normalized difference vegetation index (NDVI) composite that has generated considerable Interest. Index Terms-Data system, earth science, online access, satellite data.

Modular Software Interfaces for Revolutionary Flexibility in Space Operations

NASA Technical Reports Server (NTRS)

Glass, Brian; Braham, Stephen; Pollack, Jay

2005-01-01

To make revolutionary improvements in exploration, space systems need to be flexible, realtime reconfigurable, and able to trade data transparently among themselves and mission operations. Onboard operations systems, space assembly coordination and EVA systems in exploration and construction all require real-time modular reconfigurability and data sharing. But NASA's current exploration systems are still largely legacies from hastily-developed, one-off Apollo-era practices. Today's rovers, vehicles, spacesuits, space stations, and instruments are not able to plug-and-play, Lego-like: into different combinations. Point-to-point dominates - individual suit to individual vehicle, individual instrument to rover. All are locally optimized, all unique, each of the data interfaces has been recoded for each possible combination. This will be an operations and maintenance nightmare in the much larger Project Constellation system of systems. This legacy approach does not scale to the hundreds of networked space components needed for space construction and for new, space-based approaches to Earth-Moon operations. By comparison, battlefield information management systems, which are considered critical to military force projection, have long since abandoned a point-to-point approach to systems integration. From a system-of-systems viewpoint, a clean-sheet redesign of the interfaces of all exploration systems is a necessary prerequisite before designing the interfaces of the individual exploration systems. Existing communications and Global Information Grid and middleware technologies are probably sufficient for command and control and information interfaces, with some hardware and time-delay modifications for space environments. NASA's future advanced space operations must also be information and data compatible with aerospace operations and surveillance systems being developed by other US Government agencies such as the Department of Homeland Security, Federal Aviation Administration and Department of Defense. This paper discusses fundamental system-of-systems infrastructure: approaches and architectures for modular plug-and-play software interfaces for revolutionary improvements in flexibility, modularity, robustness, ease of maintenance, reconfigurability, safety and productivity. Starting with middleware, databases, and mobile communications technologies, our technical challenges will be to apply these ideas to the requirements of constellations of space systems and to implement them initially on prototype space hardware. This is necessary to demonstrate an integrated information sharing architecture and services. It is a bottom-up approach, one that solves the problem of space operations data integration. Exploration demands uniform software mechanisms for application information interchange, and the corresponding uniformly available software services to enhance these mechanisms. We will examine the issues in plug-and-play, real-time-configurable systems, including common definition and management and tracking of data and information among many different space systems. Different field test approaches are discussed, including the use of the International Space Station and terrestrial analog mission operations at field sites.

A Study on User Interface Design of Knowledge Management Groupware in Selected Leading Organizations of Pakistan

DTIC Science & Technology

2004-06-01

Information Systems, Faculty of ICT, International Islamic University, Malaysia . Abstract. Several techniques for evaluating a groupware...inspection based techniques couldn’t be carried out in other parts of Pakistan where the IT industry has mushroomed in the past few years. Nevertheless...there are no set standards for using any particular technique. Evaluating a groupware interface is an evolving process and requires more investigation

Multiple man-machine interfaces

NASA Technical Reports Server (NTRS)

Stanton, L.; Cook, C. W.

1981-01-01

The multiple man machine interfaces inherent in military pilot training, their social implications, and the issue of possible negative feedback were explored. Modern technology has produced machines which can see, hear, and touch with greater accuracy and precision than human beings. Consequently, the military pilot is more a systems manager, often doing battle against a target he never sees. It is concluded that unquantifiable human activity requires motivation that is not intrinsic in a machine.

Design of an efficient framework for fast prototyping of customized human-computer interfaces and virtual environments for rehabilitation.

PubMed

Avola, Danilo; Spezialetti, Matteo; Placidi, Giuseppe

2013-06-01

Rehabilitation is often required after stroke, surgery, or degenerative diseases. It has to be specific for each patient and can be easily calibrated if assisted by human-computer interfaces and virtual reality. Recognition and tracking of different human body landmarks represent the basic features for the design of the next generation of human-computer interfaces. The most advanced systems for capturing human gestures are focused on vision-based techniques which, on the one hand, may require compromises from real-time and spatial precision and, on the other hand, ensure natural interaction experience. The integration of vision-based interfaces with thematic virtual environments encourages the development of novel applications and services regarding rehabilitation activities. The algorithmic processes involved during gesture recognition activity, as well as the characteristics of the virtual environments, can be developed with different levels of accuracy. This paper describes the architectural aspects of a framework supporting real-time vision-based gesture recognition and virtual environments for fast prototyping of customized exercises for rehabilitation purposes. The goal is to provide the therapist with a tool for fast implementation and modification of specific rehabilitation exercises for specific patients, during functional recovery. Pilot examples of designed applications and preliminary system evaluation are reported and discussed. Copyright © 2013 Elsevier Ireland Ltd. All rights reserved.

Tele-counseling and social-skill trainings using JGNII optical network and a mirror-interface system

NASA Astrophysics Data System (ADS)

Hashimoto, Sayuri; Hashimoto, Nobuyuki; Onozawa, Akira; Hosoya, Eiichi; Harada, Ikuo; Okunaka, Junzo

2007-09-01

"Tele-presence" communication using JGNII - an exclusive optical-fiber network system - was applied to social-skills training in the form of child-rearing support. This application focuses on internet counseling and social training skills that require interactive verbal and none-verbal communications. The motivation for this application is supporting local communities by constructing tele-presence education and entertainment systems using recently available, inexpensive IP networks. This latest application of tele-presence communication uses mirror-interface system which provides to users in remote locations a shared quasi-space where they can see themselves as if they were in the same room by overlapping video images from remote locations.

An Expert Assistant for Computer Aided Parallelization

NASA Technical Reports Server (NTRS)

Jost, Gabriele; Chun, Robert; Jin, Haoqiang; Labarta, Jesus; Gimenez, Judit

2004-01-01

The prototype implementation of an expert system was developed to assist the user in the computer aided parallelization process. The system interfaces to tools for automatic parallelization and performance analysis. By fusing static program structure information and dynamic performance analysis data the expert system can help the user to filter, correlate, and interpret the data gathered by the existing tools. Sections of the code that show poor performance and require further attention are rapidly identified and suggestions for improvements are presented to the user. In this paper we describe the components of the expert system and discuss its interface to the existing tools. We present a case study to demonstrate the successful use in full scale scientific applications.

Development and evaluation of a self-regulating alternating pressure air cushion.

PubMed

Nakagami, Gojiro; Sanada, Hiromi; Sugama, Junko

2015-03-01

To investigate the effect of alternating air cells of a newly developed dynamic cushion on interface pressure and tissue oxygenation levels. This cross-over experimental study included 19 healthy volunteers. The dynamic cushion used has an automatic self-regulating alternating pressure air-cell system with 35 small and four large air cells for maintaining posture while seated. This cushion also has 17 bottoming-out detectors that automatically inflate the air cells to release a high interface pressure. To assess the effect of this alternating system, participants sat on the new cushion with an alternating system or static system for 30 min and then performed push-ups. The interface pressure was monitored by pressure-sensitive and conductive ink film sensors and tissue oxygenation levels were monitored by near-infrared spectroscopy. A reactive hyperaemia indicator was calculated using tissue oxygenation levels as an outcome measure. The peak interface pressure was not significantly different between the groups. The reactive hyperaemia indicator was significantly higher in the static group than in the alternating group. An alternating system has beneficial effects on blood oxygenation levels without increasing interface pressure. Therefore, our new cushion is promising for preventing pressure ulcers with patients with limited ability to perform push-ups. Implications for Rehabilitation A dynamic cushion was developed, which consists of a uniquely-designed air-cell layout, detectors for bottoming out, and an alternating system with multiple air-cell lines. The alternating system did not increase interface pressure and it significantly reduced reactive hyperaemia after 30 min of sitting in healthy volunteers. This cushion is a new option for individuals who require stable posture but have limitations in performing scheduled push-ups for prevention of pressure ulcers.

SODR Memory Control Buffer Control ASIC

NASA Technical Reports Server (NTRS)

Hodson, Robert F.

1994-01-01

The Spacecraft Optical Disk Recorder (SODR) is a state of the art mass storage system for future NASA missions requiring high transmission rates and a large capacity storage system. This report covers the design and development of an SODR memory buffer control applications specific integrated circuit (ASIC). The memory buffer control ASIC has two primary functions: (1) buffering data to prevent loss of data during disk access times, (2) converting data formats from a high performance parallel interface format to a small computer systems interface format. Ten 144 p in, 50 MHz CMOS ASIC's were designed, fabricated and tested to implement the memory buffer control function.

Methodology for automating software systems

NASA Technical Reports Server (NTRS)

Moseley, Warren

1990-01-01

Applying ITS technology to the shuttle diagnostics would not require the rigor of the Petri Net representation, however it is important in providing the animated simulated portion of the interface and the demands placed on the system to support the training aspects to have a homogeneous and consistent underlying knowledge representation. By keeping the diagnostic rule base, the hardware description, the software description, user profiles, desired behavioral knowledge, and the user interface in the same notation, it is possible to reason about the all of the properties of petri nets, on any selected portion of the simulation. This reasoning provides foundation for utilization of intelligent tutoring systems technology.

Material platforms for spin-based photonic quantum technologies

NASA Astrophysics Data System (ADS)

Atatüre, Mete; Englund, Dirk; Vamivakas, Nick; Lee, Sang-Yun; Wrachtrup, Joerg

2018-05-01

A central goal in quantum optics and quantum information science is the development of quantum networks to generate entanglement between distributed quantum memories. Experimental progress relies on the quality and efficiency of the light-matter quantum interface connecting the quantum states of photons to internal states of quantum emitters. Quantum emitters in solids, which have properties resembling those of atoms and ions, offer an opportunity for realizing light-matter quantum interfaces in scalable and compact hardware. These quantum emitters require a material platform that enables stable spin and optical properties, as well as a robust manufacturing of quantum photonic circuits. Because no emitter system is yet perfect and different applications may require different properties, several light-matter quantum interfaces are being developed in various platforms. This Review highlights the progress in three leading material platforms: diamond, silicon carbide and atomically thin semiconductors.

Space Station Furnace Facility Management Information System (SSFF-MIS) Development

NASA Technical Reports Server (NTRS)

Meade, Robert M.

1996-01-01

This report summarizes the chronology, results, and lessons learned from the development of the SSFF-MIS. This system has been nearly two years in development and has yielded some valuable insights into specialized MIS development. General: In December of 1994, the Camber Corporation and Science Applications International Corporation (SAIC) were contracted to design, develop, and implement a MIS for Marshall Space Flight Center's Space Station Furnace Facility Project. The system was to be accessible from both EBM-Compatible PC and Macintosh platforms. The system was required to contain data manually entered into the MIS as well as data imported from other MSFC sources. Electronic interfaces were established for each data source and retrieval was to be performed at prescribed time intervals. The SOW requirement that predominantly drove the development software selection was the dual-platform (IBM-PC and Macintosh) requirement. The requirement that the system would be maintained by Government personnel influenced the selection of Commercial Off-the-shelf software because of its inherent stability and readily available documentation and support. Microsoft FoxPro Professional 2.6 for Windows and Macintosh was selected as the development tool. This is a software development tool that has been in use for many years. It is stable and powerful. Microsoft has since released the replacement for this product, Microsoft Visual FoxPro, but at the time of this development, it was only available on the Windows platform. The initial contract included included the requirement for capabilities relating to the Work- and Organizational Breakdown Structures, cost (plan and actuals), workforce (plan and actuals), critical path scheduling, trend analysis, procurements and contracts, interface to manufacturing, Safety and Mission Assurance, risk analysis, and technical performance indicators. It also required full documentation of the system and training of users. During the course of the contract, the requirements for Safety and Mission Assurance interface, risk analysis, and technical performance indicators were deleted. Additional capabilities were added as reflected in the Contract Chronology below. Modification 4 added the requirement for Support Contractor manpower data, the ability to manually input data not imported from non-nal sources, a general 'health' indicator screen, and remote usage. Mod 6 included the ability to change the level of planning of Civil Service Manpower at any time and the ability to manually enter Op Codes in the manufacturing data where such codes were not provided by the EMPACS database. Modification 9 included a number of changes to report contents and formats. Modification 11 required the preparation of a detailed System Design Document.

Subsea approach to work systems development

NASA Technical Reports Server (NTRS)

Gernhardt, M. L.; Frisbie, F. R.; Brown, C. E.

1988-01-01

Self-contained undersea working environments with applications to space station EVA environments are discussed. Physiological limitations include decompression, inert gas narcosis, high-pressure nervous system, gas toxicity, and thermal limitations. Work task requirements include drilling support, construction, inspection, and repair. Work systems include hyperbaric diving, atmospheric work systems, tele-operated work systems, and hybrid systems. Each type of work system is outlined in terms of work capabilities, special interface requirements, and limitations. Various operational philosophies are discussed. The evolution of work systems in the subsea industry has been the result of direct operational experience in a competitive market.

Implementation of EPICS based vacuum control system for variable energy cyclotron centre, Kolkata

DOE Office of Scientific and Technical Information (OSTI.GOV)

Roy, Anindya, E-mail: r-ani@vecc.gov.in; Bhole, R. B.; Nandy, Partha P.

2015-03-15

The vacuum system of the Room Temperature (K = 130) Cyclotron of Variable Energy Cyclotron Centre is comprised of vacuum systems of main machine and Beam Transport System. The vacuum control system is upgraded to a PLC based Automated system from the initial relay based Manual system. The supervisory control of the vacuum system is implemented in Experimental Physics and Industrial Control System (EPICS). An EPICS embedded ARM based vacuum gauge controller is developed to mitigate the requirement of vendor specific gauge controller for gauges and also for seamless integration of the gauge controllers with the control system. A setmore » of MS-Windows ActiveX components with embedded EPICS Channel Access interface are developed to build operator interfaces with less complex programming and to incorporate typical Windows feature, e.g., user authentication, file handling, better fonts, colors, mouse actions etc. into the operator interfaces. The control parameters, monitoring parameters, and system interlocks of the system are archived in MySQL based EPICS MySQL Archiver developed indigenously. In this paper, we describe the architecture, the implementation details, and the performance of the system.« less

Optimizing the user interface of a data entry module for an electronic patient record for cardiac rehabilitation: A mixed method usability approach.

PubMed

van Engen-Verheul, Mariëtte M; Peute, Linda W P; de Keizer, Nicolette F; Peek, Niels; Jaspers, Monique W M

2016-03-01

Cumbersome electronic patient record (EPR) interfaces may complicate data-entry in clinical practice. Completeness of data entered in the EPR determines, among other things, the value of computerized clinical decision support (CCDS). Quantitative usability evaluations can provide insight into mismatches between the system design model of data entry and users' data entry behavior, but not into the underlying causes for these mismatches. Mixed method usability evaluation studies may provide these insights, and thus support generating redesign recommendations for improving an EPR system's data entry interface. To improve the usability of the data entry interface of an EPR system with CCDS in the field of cardiac rehabilitation (CR), and additionally, to assess the value of a mixed method usability approach in this context. Seven CR professionals performed a think-aloud usability evaluation both before (beta-version) and after the redesign of the system. Observed usability problems from both evaluations were analyzed and categorized using Zhang et al.'s heuristic principles of good interface design. We combined the think-aloud usability evaluation of the system's beta-version with the measurement of a new usability construct: users' deviations in action sequence from the system's predefined data entry order sequence. Recommendations for redesign were implemented. We assessed whether the redesign improved CR professionals' (1) task efficacy (with respect to the completeness of data they collected), and (2) task efficiency (with respect to the average number of mouse clicks they needed to complete data entry subtasks). With the system's beta version, 40% of health care professionals' navigation actions through the system deviated from the predefined next system action. The causes for these deviations as revealed by the think-aloud method mostly concerned mismatches between the system design model for data entry action sequences and users expectations of these action sequences, based on their paper-based daily routines. This caused non completion of data entry tasks (31% of main tasks completed), and more navigation actions than minimally required (146% of the minimum required). In the redesigned system the data entry navigational structure was organized in a flexible way around an overview screen to better mimic users' paper-based daily routines of collecting patient data. This redesign resulted in an increased number of completed main tasks (70%) and a decrease in navigation actions (133% of the minimum required). The think-aloud usability evaluation of the redesigned system showed that remaining problems concerned flexibility (e.g., lack of customization options) and consistency (mainly with layout and position of items on the screen). The mixed method usability evaluation was supportive in revealing the magnitude and causes of mismatches between the system design model of data-entry with users' data entry behavior. However, as both task efficacy and efficiency were still not optimal with the redesigned EPR, we advise to perform a cognitive analysis on end users' mental processes and behavior patterns in daily work processes specifically during the requirements analysis phase of development of interactive healthcare information systems. Copyright © 2015 Elsevier Ireland Ltd. All rights reserved.

'Fly Like This': Natural Language Interface for UAV Mission Planning

NASA Technical Reports Server (NTRS)

Chandarana, Meghan; Meszaros, Erica L.; Trujillo, Anna; Allen, B. Danette

2017-01-01

With the increasing presence of unmanned aerial vehicles (UAVs) in everyday environments, the user base of these powerful and potentially intelligent machines is expanding beyond exclusively highly trained vehicle operators to include non-expert system users. Scientists seeking to augment costly and often inflexible methods of data collection historically used are turning towards lower cost and reconfigurable UAVs. These new users require more intuitive and natural methods for UAV mission planning. This paper explores two natural language interfaces - gesture and speech - for UAV flight path generation through individual user studies. Subjects who participated in the user studies also used a mouse-based interface for a baseline comparison. Each interface allowed the user to build flight paths from a library of twelve individual trajectory segments. Individual user studies evaluated performance, efficacy, and ease-of-use of each interface using background surveys, subjective questionnaires, and observations on time and correctness. Analysis indicates that natural language interfaces are promising alternatives to traditional interfaces. The user study data collected on the efficacy and potential of each interface will be used to inform future intuitive UAV interface design for non-expert users.

LINKING THE CMAQ AND HYSPLIT MODELING SYSTEM INTERFACE PROGRAM AND EXAMPLE APPLICATION

EPA Science Inventory

A new software tool has been developed to link the Eulerian-based Community Multiscale Air Quality (CMAQ) modeling system with the Lagrangian-based HYSPLIT (HYbrid Single-Particle Lagrangian Integrated Trajectory) model. Both models require many of the same hourly meteorological...

Solar-powered hot-air system

NASA Technical Reports Server (NTRS)

1979-01-01

Solar-powered air heater supplies part or all of space heating requirements of residential or commercial buildings and is interfaced with air to water heat exchanger to heat domestic hot water. System has potential application in drying agricultural products such as cotton, lumber, corn, grains, and peanuts.

A hybrid nonlinear programming method for design optimization

NASA Technical Reports Server (NTRS)

Rajan, S. D.

1986-01-01

Solutions to engineering design problems formulated as nonlinear programming (NLP) problems usually require the use of more than one optimization technique. Moreover, the interaction between the user (analysis/synthesis) program and the NLP system can lead to interface, scaling, or convergence problems. An NLP solution system is presented that seeks to solve these problems by providing a programming system to ease the user-system interface. A simple set of rules is used to select an optimization technique or to switch from one technique to another in an attempt to detect, diagnose, and solve some potential problems. Numerical examples involving finite element based optimal design of space trusses and rotor bearing systems are used to illustrate the applicability of the proposed methodology.

Integrated command, control, communications and computation system functional architecture

NASA Technical Reports Server (NTRS)

Cooley, C. G.; Gilbert, L. E.

1981-01-01

The functional architecture for an integrated command, control, communications, and computation system applicable to the command and control portion of the NASA End-to-End Data. System is described including the downlink data processing and analysis functions required to support the uplink processes. The functional architecture is composed of four elements: (1) the functional hierarchy which provides the decomposition and allocation of the command and control functions to the system elements; (2) the key system features which summarize the major system capabilities; (3) the operational activity threads which illustrate the interrelationahip between the system elements; and (4) the interfaces which illustrate those elements that originate or generate data and those elements that use the data. The interfaces also provide a description of the data and the data utilization and access techniques.

NASA/NBS (National Aeronautics and Space Administration/National Bureau of Standards) standard reference model for telerobot control system architecture (NASREM)

NASA Technical Reports Server (NTRS)

Albus, James S.; Mccain, Harry G.; Lumia, Ronald

1989-01-01

The document describes the NASA Standard Reference Model (NASREM) Architecture for the Space Station Telerobot Control System. It defines the functional requirements and high level specifications of the control system for the NASA space Station document for the functional specification, and a guideline for the development of the control system architecture, of the 10C Flight Telerobot Servicer. The NASREM telerobot control system architecture defines a set of standard modules and interfaces which facilitates software design, development, validation, and test, and make possible the integration of telerobotics software from a wide variety of sources. Standard interfaces also provide the software hooks necessary to incrementally upgrade future Flight Telerobot Systems as new capabilities develop in computer science, robotics, and autonomous system control.

Selective electrical interfaces with the nervous system.

PubMed

Rutten, Wim L C

2002-01-01

To achieve selective electrical interfacing to the neural system it is necessary to approach neuronal elements on a scale of micrometers. This necessitates microtechnology fabrication and introduces the interdisciplinary field of neurotechnology, lying at the juncture of neuroscience with microtechnology. The neuroelectronic interface occurs where the membrane of a cell soma or axon meets a metal microelectrode surface. The seal between these may be narrow or may be leaky. In the latter case the surrounding volume conductor becomes part of the interface. Electrode design for successful interfacing, either for stimulation or recording, requires good understanding of membrane phenomena, natural and evoked action potential generation, volume conduction, and electrode behavior. Penetrating multimicroelectrodes have been produced as one-, two-, and three-dimensional arrays, mainly in silicon, glass, and metal microtechnology. Cuff electrodes circumvent a nerve; their selectivity aims at fascicles more than at nerve fibers. Other types of electrodes are regenerating sieves and cone-ingrowth electrodes. The latter may play a role in brain-computer interfaces. Planar substrate-embedded electrode arrays with cultured neural cells on top are used to study the activity and plasticity of developing neural networks. They also serve as substrates for future so-called cultured probes.

Adhesion of Silicone Elastomer Seals for NASA's Crew Exploration Vehicle

NASA Technical Reports Server (NTRS)

deGroh, Henry C., III; Miller, Sharon K. R.; Smith, Ian M.; Daniels, Christopher C.; Steinetz, Bruce M

2008-01-01

Silicone rubber seals are being considered for a number of interfaces on NASA's Crew Exploration Vehicle (CEV). Some of these joints include the docking system, hatches, and heat shield-to-back shell interface. A large diameter molded silicone seal is being developed for the Low Impact Docking System (LIDS) that forms an effective seal between the CEV and International Space Station (ISS) and other future Constellation Program spacecraft. Seals between the heat shield and back shell prevent high temperature reentry gases from leaking into the interface. Silicone rubber seals being considered for these locations have inherent adhesive tendencies that would result in excessive forces required to separate the joints if left unchecked. This paper summarizes adhesion assessments for both as-received and adhesion-mitigated seals for the docking system and the heat shield interface location. Three silicone elastomers were examined: Parker Hannifin S0899-50 and S0383-70 compounds, and Esterline ELA-SA-401 compound. For the docking system application various levels of exposure to atomic oxygen (AO) were evaluated. Moderate AO treatments did not lower the adhesive properties of S0899-50 sufficiently. However, AO pretreatments of approximately 10(exp 20) atoms/sq cm did lower the adhesion of S0383-70 and ELA-SA-401 to acceptable levels. For the heat shield-to-back shell interface application, a fabric covering was also considered. Molding Nomex fabric into the heat shield pressure seal appreciably reduced seal adhesion for the heat shield-to-back shell interface application.

Atmospheric Modeling And Sensor Simulation (AMASS) study

NASA Technical Reports Server (NTRS)

Parker, K. G.

1985-01-01

A 4800 band synchronous communications link was established between the Perkin-Elmer (P-E) 3250 Atmospheric Modeling and Sensor Simulation (AMASS) system and the Cyber 205 located at the Goddard Space Flight Center. An extension study of off-the-shelf array processors offering standard interface to the Perkin-Elmer was conducted to determine which would meet computational requirements of the division. A Floating Point Systems AP-120B was borrowed from another Marshall Space Flight Center laboratory for evaluation. It was determined that available array processors did not offer significantly more capabilities than the borrowed unit, although at least three other vendors indicated that standard Perkin-Elmer interfaces would be marketed in the future. Therefore, the recommendation was made to continue to utilize the 120B ad to keep monitoring the AP market. Hardware necessary to support requirements of the ASD as well as to enhance system performance was specified and procured. Filters were implemented on the Harris/McIDAS system including two-dimensional lowpass, gradient, Laplacian, and bicubic interpolation routines.

Technology requirements and readiness for very large vehicles

NASA Technical Reports Server (NTRS)

Conner, D. W.

1979-01-01

Common concerns of very large vehicles in the areas of economics, transportation system interfaces and operational problems were reviewed regarding their influence on vehicle configurations and technology. Fifty-four technology requirements were identified which are judged to be unique, or particularly critical, to very large vehicles. The requirements were about equally divided among the four general areas of aero/hydrodynamics, propulsion and acoustics, structures, and vehicle systems and operations. The state of technology readiness was judged to be poor to fair for slightly more than one half of the requirements. In the classic disciplinary areas, the state of technology readiness appears to be more advanced than for vehicle systems and operations.

Reliability program requirements for aeronautical and space system contractors

NASA Technical Reports Server (NTRS)

1987-01-01

General reliability program requirements for NASA contracts involving the design, development, fabrication, test, and/or use of aeronautical and space systems including critical ground support equipment are prescribed. The reliability program requirements require (1) thorough planning and effective management of the reliability effort; (2) definition of the major reliability tasks and their place as an integral part of the design and development process; (3) planning and evaluating the reliability of the system and its elements (including effects of software interfaces) through a program of analysis, review, and test; and (4) timely status indication by formal documentation and other reporting to facilitate control of the reliability program.

Scientific Visualization of Radio Astronomy Data using Gesture Interaction

NASA Astrophysics Data System (ADS)

Mulumba, P.; Gain, J.; Marais, P.; Woudt, P.

2015-09-01

MeerKAT in South Africa (Meer = More Karoo Array Telescope) will require software to help visualize, interpret and interact with multidimensional data. While visualization of multi-dimensional data is a well explored topic, little work has been published on the design of intuitive interfaces to such systems. More specifically, the use of non-traditional interfaces (such as motion tracking and multi-touch) has not been widely investigated within the context of visualizing astronomy data. We hypothesize that a natural user interface would allow for easier data exploration which would in turn lead to certain kinds of visualizations (volumetric, multidimensional). To this end, we have developed a multi-platform scientific visualization system for FITS spectral data cubes using VTK (Visualization Toolkit) and a natural user interface to explore the interaction between a gesture input device and multidimensional data space. Our system supports visual transformations (translation, rotation and scaling) as well as sub-volume extraction and arbitrary slicing of 3D volumetric data. These tasks were implemented across three prototypes aimed at exploring different interaction strategies: standard (mouse/keyboard) interaction, volumetric gesture tracking (Leap Motion controller) and multi-touch interaction (multi-touch monitor). A Heuristic Evaluation revealed that the volumetric gesture tracking prototype shows great promise for interfacing with the depth component (z-axis) of 3D volumetric space across multiple transformations. However, this is limited by users needing to remember the required gestures. In comparison, the touch-based gesture navigation is typically more familiar to users as these gestures were engineered from standard multi-touch actions. Future work will address a complete usability test to evaluate and compare the different interaction modalities against the different visualization tasks.

Electronic processing and control system with programmable hardware

NASA Technical Reports Server (NTRS)

Alkalaj, Leon (Inventor); Fang, Wai-Chi (Inventor); Newell, Michael A. (Inventor)

1998-01-01

A computer system with reprogrammable hardware allowing dynamically allocating hardware resources for different functions and adaptability for different processors and different operating platforms. All hardware resources are physically partitioned into system-user hardware and application-user hardware depending on the specific operation requirements. A reprogrammable interface preferably interconnects the system-user hardware and application-user hardware.

A Generic Inner-Loop Control Law Structure for Six-Degree-of-Freedom Conceptual Aircraft Design

NASA Technical Reports Server (NTRS)

Cox, Timothy H.; Cotting, M. Christopher

2005-01-01

A generic control system framework for both real-time and batch six-degree-of-freedom simulations is presented. This framework uses a simplified dynamic inversion technique to allow for stabilization and control of any type of aircraft at the pilot interface level. The simulation, designed primarily for the real-time simulation environment, also can be run in a batch mode through a simple guidance interface. Direct vehicle-state acceleration feedback is required with the simplified dynamic inversion technique. The estimation of surface effectiveness within real-time simulation timing constraints also is required. The generic framework provides easily modifiable control variables, allowing flexibility in the variables that the pilot commands. A direct control allocation scheme is used to command aircraft effectors. Primary uses for this system include conceptual and preliminary design of aircraft, when vehicle models are rapidly changing and knowledge of vehicle six-degree-of-freedom performance is required. A simulated airbreathing hypersonic vehicle and simulated high-performance fighter aircraft are used to demonstrate the flexibility and utility of the control system.

A Generic Inner-Loop Control Law Structure for Six-Degree-of-Freedom Conceptual Aircraft Design

NASA Technical Reports Server (NTRS)

Cox, Timothy H.; Cotting, Christopher

2005-01-01

A generic control system framework for both real-time and batch six-degree-of-freedom (6-DOF) simulations is presented. This framework uses a simplified dynamic inversion technique to allow for stabilization and control of any type of aircraft at the pilot interface level. The simulation, designed primarily for the real-time simulation environment, also can be run in a batch mode through a simple guidance interface. Direct vehicle-state acceleration feedback is required with the simplified dynamic inversion technique. The estimation of surface effectiveness within real-time simulation timing constraints also is required. The generic framework provides easily modifiable control variables, allowing flexibility in the variables that the pilot commands. A direct control allocation scheme is used to command aircraft effectors. Primary uses for this system include conceptual and preliminary design of aircraft, when vehicle models are rapidly changing and knowledge of vehicle 6-DOF performance is required. A simulated airbreathing hypersonic vehicle and simulated high-performance fighter aircraft are used to demonstrate the flexibility and utility of the control system.

Scientific customer needs - NASA user

NASA Technical Reports Server (NTRS)

Black, David C.

1987-01-01

Some requirements for scientific users of the Space Station are considered. The use of testbeds to evaluate design concepts for information systems, and for interfacing between designers and builders of systems is examined. The need for an information system that provides an effective interaction between ground-based users and their space-based equipment is discussed.

SEASAT study documentation

NASA Technical Reports Server (NTRS)

1974-01-01

The proposed spacecraft consists of a bus module, containing all subsystems required for support of the sensors, and a payload module containing all of the sensor equipment. The two modules are bolted together to form the spacecraft, and electrical interfaces are accomplished via mated connectors at the interface plane. This approach permits independent parallel assembly and test operations on each module up until mating for final spacecraft integration and test operations. Proposed program schedules recognize the need to refine sensor/spacecraft interfaces prior to proceeding with procurement, reflect the lead times estimated by suppliers for delivery of equipment, reflect a comprehensive test program, and provide flexibility for unanticipated problems. The spacecraft systems are described in detail along with aerospace ground equipment, ground handling equipment, the launch vehicle, imaging radar incorporation, and systems tests.

IGDS/TRAP Interface Program (ITIP). Software User Manual (SUM). [network flow diagrams for coal gasification studies

NASA Technical Reports Server (NTRS)

Jefferys, S.; Johnson, W.; Lewis, R.; Rich, R.

1981-01-01

This specification establishes the requirements, concepts, and preliminary design for a set of software known as the IGDS/TRAP Interface Program (ITIP). This software provides the capability to develop at an Interactive Graphics Design System (IGDS) design station process flow diagrams for use by the NASA Coal Gasification Task Team. In addition, ITIP will use the Data Management and Retrieval System (DMRS) to maintain a data base from which a properly formatted input file to the Time-Line and Resources Analysis Program (TRAP) can be extracted. This set of software will reside on the PDP-11/70 and will become the primary interface between the Coal Gasification Task Team and IGDS, DMRS, and TRAP. The user manual for the computer program is presented.

High Speed A/D DSP Interface for Carrier Doppler Tracking

NASA Technical Reports Server (NTRS)

Baggett, Timothy

1998-01-01

As on-board satellite systems continue to increase in ability to perform self diagnostic checks, it will become more important for satellites to initiate ground communications contact. Currently, the NASA Space Network requires users to pre-arranged times for satellite communications links through the Tracking and Data Relay Satellite (TDRS). One of the challenges in implementing an on-demand access protocol into the Space Network, is the fact that a low Earth orbiting (LEO) satellite's communications will be subject to a doppler shift which is outside the capability of the NASA ground station to lock onto. In a prearranged system, the satellite's doppler is known a priori, and the ground station is able to lock onto the satellite's signal. This paper describes the development of a high speed analog to digital interface into a Digital Signal Processor (DSP). This system will be used for identifying the doppler shift of a LEO satellite through the Space Network, and aiding the ground station equipment in locking onto the signal. Although this interface is specific to one application, it can be used as a basis for interfacing other devices with a DSP.

SCAILET - An intelligent assistant for satellite ground terminal operations

NASA Technical Reports Server (NTRS)

Shahidi, A. K.; Crapo, J. A.; Schlegelmilch, R. F.; Reinhart, R. C.; Petrik, E. J.; Walters, J. L.; Jones, R. E.

1992-01-01

Space communication artificial intelligence for the link evaluation terminal (SCAILET) is an experimenter interface to the link evaluation terminal (LET) developed by NASA through the application of artificial intelligence to an advanced ground terminal. The high-burst-rate (HBR) LET provides the required capabilities for wideband communications experiments with the advanced communications technology satellite (ACTS). The HBR-LET terminal consists of seven major subsystems and is controlled and monitored by a minicomputer through an IEEE-488 or RS-232 interface. Programming scripts configure HBR-LET and allow data acquisition but are difficult to use and therefore the full capabilities of the system are not utilized. An intelligent assistant module was developed as part of the SCAILET module and solves problems encountered during configuration of the HBR-LET system. This assistant is a graphical interface with an expert system running in the background and allows users to configure instrumentation, program sequences and reference documentation. The simplicity of use makes SCAILET a superior interface to the ASCII terminal and continuous monitoring allows nearly flawless configuration and execution of HBR-LET experiments.

Exploring model based engineering for large telescopes: getting started with descriptive models

NASA Astrophysics Data System (ADS)

Karban, R.; Zamparelli, M.; Bauvir, B.; Koehler, B.; Noethe, L.; Balestra, A.

2008-07-01

Large telescopes pose a continuous challenge to systems engineering due to their complexity in terms of requirements, operational modes, long duty lifetime, interfaces and number of components. A multitude of decisions must be taken throughout the life cycle of a new system, and a prime means of coping with complexity and uncertainty is using models as one decision aid. The potential of descriptive models based on the OMG Systems Modeling Language (OMG SysMLTM) is examined in different areas: building a comprehensive model serves as the basis for subsequent activities of soliciting and review for requirements, analysis and design alike. Furthermore a model is an effective communication instrument against misinterpretation pitfalls which are typical of cross disciplinary activities when using natural language only or free-format diagrams. Modeling the essential characteristics of the system, like interfaces, system structure and its behavior, are important system level issues which are addressed. Also shown is how to use a model as an analysis tool to describe the relationships among disturbances, opto-mechanical effects and control decisions and to refine the control use cases. Considerations on the scalability of the model structure and organization, its impact on the development process, the relation to document-centric structures, style and usage guidelines and the required tool chain are presented.

Digital avionics systems - Principles and practices (2nd revised and enlarged edition)

NASA Technical Reports Server (NTRS)

Spitzer, Cary R.

1993-01-01

The state of the art in digital avionics systems is surveyed. The general topics addressed include: establishing avionics system requirements; avionics systems essentials in data bases, crew interfaces, and power; fault tolerance, maintainability, and reliability; architectures; packaging and fitting the system into the aircraft; hardware assessment and validation; software design, assessment, and validation; determining the costs of avionics.

Information management system study results. Volume 2: IMS study results appendixes

NASA Technical Reports Server (NTRS)

1971-01-01

Computer systems program specifications are presented for the modular space station information management system. These are the computer program contract end item, data bus system, data bus breadboard, and display interface adapter specifications. The performance, design, tests, and qualification requirements are established for the implementation of the information management system. For Vol. 1, see N72-19972.

The EOSDIS software challenge

NASA Astrophysics Data System (ADS)

Jaworski, Allan

1993-08-01

The Earth Observing System (EOS) Data and Information System (EOSDIS) will serve as a major resource for the earth science community, supporting both command and control of complex instruments onboard the EOS spacecraft and the archiving, distribution, and analysis of data. The scale of EOSDIS and the volume of multidisciplinary research to be conducted using EOSDIS resources will produce unparalleled needs for technology transparency, data integration, and system interoperability. The scale of this effort far outscopes any previous scientific data system in its breadth or operational and performance needs. Modern hardware technology can meet the EOSDIS technical challenge. Multiprocessing speeds of many giga-flops are being realized by modern computers. Online storage disk, optical disk, and videocassette libraries with storage capacities of many terabytes are now commercially available. Radio frequency and fiber optics communications networks with gigabit rates are demonstrable today. It remains, of course, to perform the system engineering to establish the requirements, architectures, and designs that will implement the EOSDIS systems. Software technology, however, has not enjoyed the price/performance advances of hardware. Although we have learned to engineer hardware systems which have several orders of magnitude greater complexity and performance than those built in the 1960's, we have not made comparable progress in dramatically reducing the cost of software development. This lack of progress may significantly reduce our capabilities to achieve economically the types of highly interoperable, responsive, integraded, and productive environments which are needed by the earth science community. This paper describes some of the EOSDIS software requirements and current activities in the software community which are applicable to meeting the EOSDIS challenge. Some of these areas include intelligent user interfaces, software reuse libraries, and domain engineering. Also included are discussions of applicable standards in the areas of operating systems interfaces, user interfaces, communications interfaces, data transport, and science algorithm support, and their role in supporting the software development process.

Physician acceptance of the IRIS user interface during a clinical trial at the Ottawa Civic Hospital

NASA Astrophysics Data System (ADS)

Coristine, Marjorie; Beeton, Carolyn; Tombaugh, Jo W.; Ahuja, J.; Belanger, Garry; Dillon, Richard F.; Currie, Shawn; Hind, E.

1990-07-01

During a clinical trial, emergency physicians and radiologists at the Ottawa Civic Hospital used IRIS (Integrated Radiological Information System) to process patients' x-rays, requisitions, and reports, and to have consultations, for 319 active cases. This paper discusses IRIS user interface issues raised during the clinical trial. The IRIS workstation consists of three major system components: 1) an image screen for viewing and enhancing images; 2) a control screen for presenting patient information, selecting images, and executing commands; and 3) a hands-free telephone for reporting activities and consultations. The control screen and hands-free telephone user interface allow physicians to navigate through patient files, select images and access reports, enter new reports, and perform remote consultations. Physicians were observed using the system during the trial and responded to questions about the user interface on an extensive debriefing interview after the trial. Overall, radiologists and emergency physicians were satisfied with IRIS control screen functionality and user interface. In a number of areas radiologists and emergency physicians differed in their user interface needs. Some features were found to be acceptable to one group of physicians but required modification to meet the needs of the other physician group. The data from the interviews, along with the comments from radiologists and emergency physicians provided important information for the revision of some features, and for the evolution of new features.

Update Of The ACR-NEMA Standard Committee

NASA Astrophysics Data System (ADS)

Wang, Yen; Best, D. E.; Morse, R. R.; Horii, S. C.; Lehr, J. L.; Lodwick, G. S.; Fuscoe, C.; Nelson, O. L.; Perry, J. R.; Thompson, B. G.; Wessell, W. R.

1988-06-01

In January, 1984, the American College of Radiology (ACR) representing the users of imaging equipment and the National Electrical Manufacturers Association (NEMA) representing the manufacturers of imaging equipment joined forces to create a committee that could solve the compatibility issues surrounding the exchange of digital medical images. This committee, the ACR-NEMA Digital Imaging and Communication Standards Committee was composed of radiologists and experts from industry who addressed the problems involved in interfacing different digital imaging modalities. In just two years, the committee and three of its working groups created an industry standard interface, ACR-NEMA Digital Imaging and Communications Standard, Publication No. 300-1985. The ACR-NEMA interface allows digital medical images and related information to be communicated between different imaging devices, regardless of manufacturer or use of differing image formats. The interface is modeled on the International Standards Organization's Open Systems Interconnection sever-layer reference model. It is believed that the development of the Interface was the first step in the development of standards for Medical Picture Archiving and Communications Systems (PACS). Developing the interface Standard has required intensive technical analysis and examination of the future trends for digital imaging in order to design a model which would not be quickly outmoded. To continue the enhancement and future development of image management systems, various working groups have been created under the direction of the ACR-NEMA Committee.

Representation and presentation of requirements knowledge

NASA Technical Reports Server (NTRS)

Johnson, W. L.; Feather, Martin S.; Harris, David R.

1992-01-01

An approach to representation and presentation of knowledge used in the ARIES, an experimental requirements/specification environment, is described. The approach applies the notion of a representation architecture to the domain of software engineering and incorporates a strong coupling to a transformation system. It is characterized by a single highly expressive underlying representation, interfaced simultaneously to multiple presentations, each with notations of differing degrees of expressivity. This enables analysts to use multiple languages for describing systems and have these descriptions yield a single consistent model of the system.

Validation Methods Research for Fault-Tolerant Avionics and Control Systems Sub-Working Group Meeting. CARE 3 peer review

NASA Technical Reports Server (NTRS)

Trivedi, K. S. (Editor); Clary, J. B. (Editor)

1980-01-01

A computer aided reliability estimation procedure (CARE 3), developed to model the behavior of ultrareliable systems required by flight-critical avionics and control systems, is evaluated. The mathematical models, numerical method, and fault-tolerant architecture modeling requirements are examined, and the testing and characterization procedures are discussed. Recommendations aimed at enhancing CARE 3 are presented; in particular, the need for a better exposition of the method and the user interface is emphasized.

Organization of the ER–Golgi interface for membrane traffic control

PubMed Central

Brandizzi, Federica; Barlowe, Charles

2014-01-01

Coat protein complex I (COPI) and COPII are required for bidirectional membrane trafficking between the endoplasmic reticulum (ER) and the Golgi. While these core coat machineries and other transport factors are highly conserved across species, high-resolution imaging studies indicate that the organization of the ER–Golgi interface is varied in eukaryotic cells. Regulation of COPII assembly, in some cases to manage distinct cellular cargo, is emerging as one important component in determining this structure. Comparison of the ER–Golgi interface across different systems, particularly mammalian and plant cells, reveals fundamental elements and distinct organization of this interface. A better understanding of how these interfaces are regulated to meet varying cellular secretory demands should provide key insights into the mechanisms that control efficient trafficking of proteins and lipids through the secretory pathway. PMID:23698585

Real-Time Extended Interface Automata for Software Testing Cases Generation

PubMed Central

Yang, Shunkun; Xu, Jiaqi; Man, Tianlong; Liu, Bin

2014-01-01

Testing and verification of the interface between software components are particularly important due to the large number of complex interactions, which requires the traditional modeling languages to overcome the existing shortcomings in the aspects of temporal information description and software testing input controlling. This paper presents the real-time extended interface automata (RTEIA) which adds clearer and more detailed temporal information description by the application of time words. We also establish the input interface automaton for every input in order to solve the problems of input controlling and interface covering nimbly when applied in the software testing field. Detailed definitions of the RTEIA and the testing cases generation algorithm are provided in this paper. The feasibility and efficiency of this method have been verified in the testing of one real aircraft braking system. PMID:24892080

Hitchhiker: Customer Accommodations and Requirements Specifications (CARS)

NASA Technical Reports Server (NTRS)

1992-01-01

In 1984, NASA Headquarters established projects at the Goddard Space Flight Center (GSFC) and the Marshall Space Flight Center (MSFC) to develop quick-reaction carrier systems for low-cost 'flight of opportunity' or secondary payloads on the Space Transportation System (STS). One of these projects is the Hitchhiker (HH) Program. GSFC has developed a family of carrier equipment known as the Shuttle Payload of Opportunity Carrier (SPOC) system for mounting small payloads such as HH to the side of the Orbiter payload bay. The side-mounted HHs are referred to as Hitchhiker-G (HH-G). MSFC developed a cross-bay 'bridge-type' carrier structure called the Hitchhiker-M (HH-M). In 1987, responsibility for the HH-M carrier was transferred to and is now managed by the HH Project Office at the GSFC. The HH-M carrier now uses the same interchangeable SPOC avionics unit and the same electrical interfaces and services developed for HH-G. National Aeronautics and Space Administration (NASA) has created this document to acquaint potential HH system customers with the facilities NASA provides and the requirements which customers must satisfy to use these facilities. This publication defines interface items required for integrating customer equipment with the HH carrier system. Those items such as mounting equipment and electrical inputs and outputs; configuration, environmental, command, telemetry, and operational constraints are described as well as weight, power, and communications. The purpose of this publication is to help the customer understand essential integration documentation requirements and to prepare a Customer Payload Requirements (CPR) document.

Space shuttle main engine definition (phase B). Volume 2: Avionics. [for space shuttle

NASA Technical Reports Server (NTRS)

1971-01-01

The advent of the space shuttle engine with its requirements for high specific impulse, long life, and low cost have dictated a combustion cycle and a closed loop control system to allow the engine components to run close to operating limits. These performance requirements, combined with the necessity for low operational costs, have placed new demands on rocket engine control, system checkout, and diagnosis technology. Based on considerations of precision environment, and compatibility with vehicle interface commands, an electronic control, makes available many functions that logically provide the information required for engine system checkout and diagnosis.

Standardized Modular Power Interfaces for Future Space Explorations Missions

NASA Technical Reports Server (NTRS)

Oeftering, Richard

2015-01-01

Earlier studies show that future human explorations missions are composed of multi-vehicle assemblies with interconnected electric power systems. Some vehicles are often intended to serve as flexible multi-purpose or multi-mission platforms. This drives the need for power architectures that can be reconfigured to support this level of flexibility. Power system developmental costs can be reduced, program wide, by utilizing a common set of modular building blocks. Further, there are mission operational and logistics cost benefits of using a common set of modular spares. These benefits are the goals of the Advanced Exploration Systems (AES) Modular Power System (AMPS) project. A common set of modular blocks requires a substantial level of standardization in terms of the Electrical, Data System, and Mechanical interfaces. The AMPS project is developing a set of proposed interface standards that will provide useful guidance for modular hardware developers but not needlessly constrain technology options, or limit future growth in capability. In 2015 the AMPS project focused on standardizing the interfaces between the elements of spacecraft power distribution and energy storage. The development of the modular power standard starts with establishing mission assumptions and ground rules to define design application space. The standards are defined in terms of AMPS objectives including Commonality, Reliability-Availability, Flexibility-Configurability and Supportability-Reusability. The proposed standards are aimed at assembly and sub-assembly level building blocks. AMPS plans to adopt existing standards for spacecraft command and data, software, network interfaces, and electrical power interfaces where applicable. Other standards including structural encapsulation, heat transfer, and fluid transfer, are governed by launch and spacecraft environments and bound by practical limitations of weight and volume. Developing these mechanical interface standards is more difficult but an essential part of defining physical building blocks of modular power. This presentation describes the AMPS projects progress towards standardized modular power interfaces.

Advanced flight deck/crew station simulator functional requirements

NASA Technical Reports Server (NTRS)

Wall, R. L.; Tate, J. L.; Moss, M. J.

1980-01-01

This report documents a study of flight deck/crew system research facility requirements for investigating issues involved with developing systems, and procedures for interfacing transport aircraft with air traffic control systems planned for 1985 to 2000. Crew system needs of NASA, the U.S. Air Force, and industry were investigated and reported. A matrix of these is included, as are recommended functional requirements and design criteria for simulation facilities in which to conduct this research. Methods of exploiting the commonality and similarity in facilities are identified, and plans for exploiting this in order to reduce implementation costs and allow efficient transfer of experiments from one facility to another are presented.

Space transportation system payload interface verification

NASA Technical Reports Server (NTRS)

Everline, R. T.

1977-01-01

The paper considers STS payload-interface verification requirements and the capability provided by STS to support verification. The intent is to standardize as many interfaces as possible, not only through the design, development, test and evaluation (DDT and E) phase of the major payload carriers but also into the operational phase. The verification process is discussed in terms of its various elements, such as the Space Shuttle DDT and E (including the orbital flight test program) and the major payload carriers DDT and E (including the first flights). Five tools derived from the Space Shuttle DDT and E are available to support the verification process: mathematical (structural and thermal) models, the Shuttle Avionics Integration Laboratory, the Shuttle Manipulator Development Facility, and interface-verification equipment (cargo-integration test equipment).

Amino Acid Hydrolysis and Analysis System for Investigation of Site Directed Nucleation and Growth of Ceramic Films on Metallic Surfaces

DTIC Science & Technology

2008-09-30

that composed the proteinaceous polymers found at the interface between calcite crystals deposited by oyster cells and the various n1etal substrates...proteinaceous polymers found at the interface between calcite crystals deposited by oyster cells and the various metal substrates. A recently...required for the mechanism of biomineralization and site-specific deposition of ceramic crystals on aluminum alloy substrates. These calcite crystals

A general graphical user interface for automatic reliability modeling

NASA Technical Reports Server (NTRS)

Liceaga, Carlos A.; Siewiorek, Daniel P.

1991-01-01

Reported here is a general Graphical User Interface (GUI) for automatic reliability modeling of Processor Memory Switch (PMS) structures using a Markov model. This GUI is based on a hierarchy of windows. One window has graphical editing capabilities for specifying the system's communication structure, hierarchy, reconfiguration capabilities, and requirements. Other windows have field texts, popup menus, and buttons for specifying parameters and selecting actions. An example application of the GUI is given.

Visualization of usability and functionality of a professional website through web-mining.

PubMed

Jones, Josette F; Mahoui, Malika; Gopa, Venkata Devi Pragna

2007-10-11

Functional interface design requires understanding of the information system structure and the user. Web logs record user interactions with the interface, and thus provide some insight into user search behavior and efficiency of the search process. The present study uses a data-mining approach with techniques such as association rules, clustering and classification, to visualize the usability and functionality of a digital library through in depth analyses of web logs.

Interface requirements to couple thermal-hydraulic codes to 3D neutronic codes

DOE Office of Scientific and Technical Information (OSTI.GOV)

Langenbuch, S.; Austregesilo, H.; Velkov, K.

1997-07-01

The present situation of thermalhydraulics codes and 3D neutronics codes is briefly described and general considerations for coupling of these codes are discussed. Two different basic approaches of coupling are identified and their relative advantages and disadvantages are discussed. The implementation of the coupling for 3D neutronics codes in the system ATHLET is presented. Meanwhile, this interface is used for coupling three different 3D neutronics codes.

High Available COTS Based Computer for Space

NASA Astrophysics Data System (ADS)

Hartmann, J.; Magistrati, Giorgio

2015-09-01

The availability and reliability factors of a system are central requirements of a target application. From a simple fuel injection system used in cars up to a flight control system of an autonomous navigating spacecraft, each application defines its specific availability factor under the target application boundary conditions. Increasing quality requirements on data processing systems used in space flight applications calling for new architectures to fulfill the availability, reliability as well as the increase of the required data processing power. Contrary to the increased quality request simplification and use of COTS components to decrease costs while keeping the interface compatibility to currently used system standards are clear customer needs. Data processing system design is mostly dominated by strict fulfillment of the customer requirements and reuse of available computer systems were not always possible caused by obsolescence of EEE-Parts, insufficient IO capabilities or the fact that available data processing systems did not provide the required scalability and performance.

FLUID MECHANICS AND TANKAGE DESIGN FOR LOW GRAVITY ENVIRONMENT

DTIC Science & Technology

tankage delivers only single-phase propellants. The requirements for feed systems of electric engines are described briefly. Also, the 1.85-second drop...direction of mass transfer in tapered tubes and liquid-vapor interface shapes in an annular space between concentric cylinders. Possible feed systems

78 FR 24101 - Generator Requirements at the Transmission Interface

Federal Register 2010, 2011, 2012, 2013, 2014

2013-04-24

... (Transmission Vegetation Management), PRC-004- 2.1a (Analysis and Mitigation of Transmission and Generation Protection System Misoperations), and PRC-005-1.1b (Transmission and Generation Protection System Maintenance... (Transmission Vegetation Management), PRC-004- 2.1a (Analysis and Mitigation of Transmission and Generation...

Operational experience with DICOM for the clinical specialties in the healthcare enterprise

NASA Astrophysics Data System (ADS)

Kuzmak, Peter M.; Dayhoff, Ruth E.

2004-04-01

A number of clinical specialties routinely use images in treating patients, for example ophthalmology, dentistry, cardiology, endoscopy, and surgery. These images are captured by a variety of commercial digital image acquisition systems. The US Department of Veterans Affairs has been working for several years on advancing the use of the Digital Imaging and Communications in Medicine (DICOM) Standard in these clinical specialties. This is an effort that has involved several facets: (1) working with the vendors to ensure that they satisfy existing DICOM requirements, (2) developing interface software to the VistA hospital information system (HIS), (3) field testing DICOM systems, (4) deploying these DICOM interfaces nation-wide to all VA medical centers, (5) working with the healthcare providers using the system, and (6) participating in the DICOM working groups to improve the standard. The VA is now beginning to develop clinical applications that make use of the DICOM interfaces in the clinical specialties. The first of these will be in ophthalmology to remotely screen patients for diabetic retinopathy.

JPL Space Telecommunications Radio System Operating Environment

NASA Technical Reports Server (NTRS)

Lux, James P.; Lang, Minh; Peters, Kenneth J.; Taylor, Gregory H.; Duncan, Courtney B.; Orozco, David S.; Stern, Ryan A.; Ahten, Earl R.; Girard, Mike

2013-01-01

A flight-qualified implementation of a Software Defined Radio (SDR) Operating Environment for the JPL-SDR built for the CoNNeCT Project has been developed. It is compliant with the NASA Space Telecommunications Radio System (STRS) Architecture Standard, and provides the software infrastructure for STRS compliant waveform applications. This software provides a standards-compliant abstracted view of the JPL-SDR hardware platform. It uses industry standard POSIX interfaces for most functions, as well as exposing the STRS API (Application Programming In terface) required by the standard. This software includes a standardized interface for IP components instantiated within a Xilinx FPGA (Field Programmable Gate Array). The software provides a standardized abstracted interface to platform resources such as data converters, file system, etc., which can be used by STRS standards conformant waveform applications. It provides a generic SDR operating environment with a much smaller resource footprint than similar products such as SCA (Software Communications Architecture) compliant implementations, or the DoD Joint Tactical Radio Systems (JTRS).

Clustered engine study

NASA Technical Reports Server (NTRS)

Shepard, Kyle; Sager, Paul; Kusunoki, Sid; Porter, John; Campion, AL; Mouritzan, Gunnar; Glunt, George; Vegter, George; Koontz, Rob

1993-01-01

Several topics are presented in viewgraph form which together encompass the preliminary assessment of nuclear thermal rocket engine clustering. The study objectives, schedule, flow, and groundrules are covered. This is followed by the NASA groundrules mission and our interpretation of the associated operational scenario. The NASA reference vehicle is illustrated, then the four propulsion system options are examined. Each propulsion system's preliminary design, fluid systems, operating characteristics, thrust structure, dimensions, and mass properties are detailed as well as the associated key propulsion system/vehicle interfaces. A brief series of systems analysis is also covered including: thrust vector control requirements, engine out possibilities, propulsion system failure modes, surviving system requirements, and technology requirements. An assessment of vehicle/propulsion system impacts due to the lessons learned are presented.

The impact of common APSE interface set specifications on space station information systems

NASA Technical Reports Server (NTRS)

Diaz-Herrera, Jorge L.; Sibley, Edgar H.

1986-01-01

Certain types of software facilities are needed in a Space Station Information Systems Environment; the Common APSE (Ada Program Support Environment) Interface Set (CAIS) was proposed as a means of satisfying them. The reasonableness of this is discussed by examining the current CAIS, considering the changes due to the latest Requirements and Criteria (RAC) document, and postulating the effects on the CAIS 2.0. Finally, a few additional comments are made on the problems inherent in the Ada language itself, especially on its deficiencies when used for implementing large distributed processing and data base applications.

Quartz Crystal Microbalance Electronic Interfacing Systems: A Review.

PubMed

Alassi, Abdulrahman; Benammar, Mohieddine; Brett, Dan

2017-12-05

Quartz Crystal Microbalance (QCM) sensors are actively being implemented in various fields due to their compatibility with different operating conditions in gaseous/liquid mediums for a wide range of measurements. This trend has been matched by the parallel advancement in tailored electronic interfacing systems for QCM sensors. That is, selecting the appropriate electronic circuit is vital for accurate sensor measurements. Many techniques were developed over time to cover the expanding measurement requirements (e.g., accommodating highly-damping environments). This paper presents a comprehensive review of the various existing QCM electronic interfacing systems. Namely, impedance-based analysis, oscillators (conventional and lock-in based techniques), exponential decay methods and the emerging phase-mass based characterization. The aforementioned methods are discussed in detail and qualitatively compared in terms of their performance for various applications. In addition, some theoretical improvements and recommendations are introduced for adequate systems implementation. Finally, specific design considerations of high-temperature microbalance systems (e.g., GaPO₄ crystals (GCM) and Langasite crystals (LCM)) are introduced, while assessing their overall system performance, stability and quality compared to conventional low-temperature applications.

Quartz Crystal Microbalance Electronic Interfacing Systems: A Review

PubMed Central

Benammar, Mohieddine; Brett, Dan

2017-01-01

Quartz Crystal Microbalance (QCM) sensors are actively being implemented in various fields due to their compatibility with different operating conditions in gaseous/liquid mediums for a wide range of measurements. This trend has been matched by the parallel advancement in tailored electronic interfacing systems for QCM sensors. That is, selecting the appropriate electronic circuit is vital for accurate sensor measurements. Many techniques were developed over time to cover the expanding measurement requirements (e.g., accommodating highly-damping environments). This paper presents a comprehensive review of the various existing QCM electronic interfacing systems. Namely, impedance-based analysis, oscillators (conventional and lock-in based techniques), exponential decay methods and the emerging phase-mass based characterization. The aforementioned methods are discussed in detail and qualitatively compared in terms of their performance for various applications. In addition, some theoretical improvements and recommendations are introduced for adequate systems implementation. Finally, specific design considerations of high-temperature microbalance systems (e.g., GaPO4 crystals (GCM) and Langasite crystals (LCM)) are introduced, while assessing their overall system performance, stability and quality compared to conventional low-temperature applications. PMID:29206212

The 30-centimeter ion thrust subsystem design manual

NASA Technical Reports Server (NTRS)

1979-01-01

The principal characteristics of the 30-centimeter ion propulsion thrust subsystem technology that was developed to satisfy the propulsion needs of future planetary and early orbital missions are described. Functional requirements and descriptions, interface and performance requirements, and physical characteristics of the hardware are described at the thrust subsystem, BIMOD engine system, and component level.

40 CFR 85.2231 - On-board diagnostic test equipment requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

... 40 Protection of Environment 19 2012-07-01 2012-07-01 false On-board diagnostic test equipment... Warranty Short Tests § 85.2231 On-board diagnostic test equipment requirements. (a) The test system interface to the vehicle shall include a plug that conforms to SAE J1962 “Diagnostic Connector.” The...

40 CFR 85.2231 - On-board diagnostic test equipment requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

... 40 Protection of Environment 18 2011-07-01 2011-07-01 false On-board diagnostic test equipment... Warranty Short Tests § 85.2231 On-board diagnostic test equipment requirements. (a) The test system interface to the vehicle shall include a plug that conforms to SAE J1962 “Diagnostic Connector.” The...

40 CFR 85.2231 - On-board diagnostic test equipment requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

... 40 Protection of Environment 19 2013-07-01 2013-07-01 false On-board diagnostic test equipment... Warranty Short Tests § 85.2231 On-board diagnostic test equipment requirements. (a) The test system interface to the vehicle shall include a plug that conforms to SAE J1962 “Diagnostic Connector.” The...

A land mobile satellite data system

NASA Technical Reports Server (NTRS)

Kent, John D. B.

1990-01-01

The Telesat Mobile Incorporated (TMI) Mobile Data System (MDS) was developed to apply satellite technology to the transportation industry's requirement for a fleet management system. It will provide two-way messaging and automatic position reporting capabilities between dispatch centers and customers' fleets of trucks. The design was based on the Inmarsat L-Band space segment with system link parameters and margins adjusted to meet the land mobile satellite channel characteristics. The system interfaces with the Teleglobe Des Laurentides earth station at Weir, Quebec. The signaling protocols were derived from the Inmarsat Standard C packet signalling system with unique trucking requirements incorporated where necessary.

Manned space flight nuclear system safety. Volume 5: Nuclear System safety guidelines. Part 1: Space base nuclear safety

NASA Technical Reports Server (NTRS)

1972-01-01

The design and operations guidelines and requirements developed in the study of space base nuclear system safety are presented. Guidelines and requirements are presented for the space base subsystems, nuclear hardware (reactor, isotope sources, dynamic generator equipment), experiments, interfacing vehicles, ground support systems, range safety and facilities. Cross indices and references are provided which relate guidelines to each other, and to substantiating data in other volumes. The guidelines are intended for the implementation of nuclear safety related design and operational considerations in future space programs.

47 CFR 11.52 - EAS code and Attention Signal Monitoring requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... technologies, such as instant messaging and email) the distribution of Common Alert Protocol (CAP)-formatted... Integrated Public Alert and Warning System (IPAWS) to enable (whether through “pull” interface technologies...

47 CFR 11.52 - EAS code and Attention Signal Monitoring requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... technologies, such as instant messaging and email) the distribution of Common Alert Protocol (CAP)-formatted... Integrated Public Alert and Warning System (IPAWS) to enable (whether through “pull” interface technologies...

47 CFR 11.52 - EAS code and Attention Signal Monitoring requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... technologies, such as instant messaging and email) the distribution of Common Alert Protocol (CAP)-formatted... Integrated Public Alert and Warning System (IPAWS) to enable (whether through “pull” interface technologies...

SUMC/MPOS/HAL interface study

NASA Technical Reports Server (NTRS)

Saponaro, J. A.; Kosmala, A. L.

1973-01-01

The implementation of the HAL/S language on the IBM-360, and in particular the mechanization of its real time, I/O, and error control statements within the OS-360 environment is described. The objectives are twofold: (1) An analysis and general description of HAL/S real time, I/O, and error control statements and the structure required to mechanize these statements. The emphasis is on describing the logical functions performed upon execution of each HAL statement rather than defining whether it is accomplished by the compiler or operating system. (2) An identification of the OS-360 facilities required during execution of HAL/S code as implemented for the current HAL/S-360 compiler; and an evaluation of the aspects involved with interfacing HAL/S with the SUMC operating system utilizing either the HAL/S-360 compiler or by designing a new HAL/S-SUMC compiler.

Space station automation and robotics study. Operator-systems interface

NASA Technical Reports Server (NTRS)

1984-01-01

This is the final report of a Space Station Automation and Robotics Planning Study, which was a joint project of the Boeing Aerospace Company, Boeing Commercial Airplane Company, and Boeing Computer Services Company. The study is in support of the Advanced Technology Advisory Committee established by NASA in accordance with a mandate by the U.S. Congress. Boeing support complements that provided to the NASA Contractor study team by four aerospace contractors, the Stanford Research Institute (SRI), and the California Space Institute. This study identifies automation and robotics (A&R) technologies that can be advanced by requirements levied by the Space Station Program. The methodology used in the study is to establish functional requirements for the operator system interface (OSI), establish the technologies needed to meet these requirements, and to forecast the availability of these technologies. The OSI would perform path planning, tracking and control, object recognition, fault detection and correction, and plan modifications in connection with extravehicular (EV) robot operations.

Lamprey: tracking users on the World Wide Web.

PubMed

Felciano, R M; Altman, R B

1996-01-01

Tracking individual web sessions provides valuable information about user behavior. This information can be used for general purpose evaluation of web-based user interfaces to biomedical information systems. To this end, we have developed Lamprey, a tool for doing quantitative and qualitative analysis of Web-based user interfaces. Lamprey can be used from any conforming browser, and does not require modification of server or client software. By rerouting WWW navigation through a centralized filter, Lamprey collects the sequence and timing of hyperlinks used by individual users to move through the web. Instead of providing marginal statistics, it retains the full information required to recreate a user session. We have built Lamprey as a standard Common Gateway Interface (CGI) that works with all standard WWW browsers and servers. In this paper, we describe Lamprey and provide a short demonstration of this approach for evaluating web usage patterns.

An Implantable Wireless Neural Interface System for Simultaneous Recording and Stimulation of Peripheral Nerve with a Single Cuff Electrode.

PubMed

Shon, Ahnsei; Chu, Jun-Uk; Jung, Jiuk; Kim, Hyungmin; Youn, Inchan

2017-12-21

Recently, implantable devices have become widely used in neural prostheses because they eliminate endemic drawbacks of conventional percutaneous neural interface systems. However, there are still several issues to be considered: low-efficiency wireless power transmission; wireless data communication over restricted operating distance with high power consumption; and limited functionality, working either as a neural signal recorder or as a stimulator. To overcome these issues, we suggest a novel implantable wireless neural interface system for simultaneous neural signal recording and stimulation using a single cuff electrode. By using widely available commercial off-the-shelf (COTS) components, an easily reconfigurable implantable wireless neural interface system was implemented into one compact module. The implantable device includes a wireless power consortium (WPC)-compliant power transmission circuit, a medical implant communication service (MICS)-band-based radio link and a cuff-electrode path controller for simultaneous neural signal recording and stimulation. During in vivo experiments with rabbit models, the implantable device successfully recorded and stimulated the tibial and peroneal nerves while communicating with the external device. The proposed system can be modified for various implantable medical devices, especially such as closed-loop control based implantable neural prostheses requiring neural signal recording and stimulation at the same time.

EMG and EPP-integrated human-machine interface between the paralyzed and rehabilitation exoskeleton.

PubMed

Yin, Yue H; Fan, Yuan J; Xu, Li D

2012-07-01

Although a lower extremity exoskeleton shows great prospect in the rehabilitation of the lower limb, it has not yet been widely applied to the clinical rehabilitation of the paralyzed. This is partly caused by insufficient information interactions between the paralyzed and existing exoskeleton that cannot meet the requirements of harmonious control. In this research, a bidirectional human-machine interface including a neurofuzzy controller and an extended physiological proprioception (EPP) feedback system is developed by imitating the biological closed-loop control system of human body. The neurofuzzy controller is built to decode human motion in advance by the fusion of the fuzzy electromyographic signals reflecting human motion intention and the precise proprioception providing joint angular feedback information. It transmits control information from human to exoskeleton, while the EPP feedback system based on haptic stimuli transmits motion information of the exoskeleton back to the human. Joint angle and torque information are transmitted in the form of air pressure to the human body. The real-time bidirectional human-machine interface can help a patient with lower limb paralysis to control the exoskeleton with his/her healthy side and simultaneously perceive motion on the paralyzed side by EPP. The interface rebuilds a closed-loop motion control system for paralyzed patients and realizes harmonious control of the human-machine system.

An Implantable Wireless Neural Interface System for Simultaneous Recording and Stimulation of Peripheral Nerve with a Single Cuff Electrode

PubMed Central

Shon, Ahnsei; Chu, Jun-Uk; Jung, Jiuk; Youn, Inchan

2017-01-01

Recently, implantable devices have become widely used in neural prostheses because they eliminate endemic drawbacks of conventional percutaneous neural interface systems. However, there are still several issues to be considered: low-efficiency wireless power transmission; wireless data communication over restricted operating distance with high power consumption; and limited functionality, working either as a neural signal recorder or as a stimulator. To overcome these issues, we suggest a novel implantable wireless neural interface system for simultaneous neural signal recording and stimulation using a single cuff electrode. By using widely available commercial off-the-shelf (COTS) components, an easily reconfigurable implantable wireless neural interface system was implemented into one compact module. The implantable device includes a wireless power consortium (WPC)-compliant power transmission circuit, a medical implant communication service (MICS)-band-based radio link and a cuff-electrode path controller for simultaneous neural signal recording and stimulation. During in vivo experiments with rabbit models, the implantable device successfully recorded and stimulated the tibial and peroneal nerves while communicating with the external device. The proposed system can be modified for various implantable medical devices, especially such as closed-loop control based implantable neural prostheses requiring neural signal recording and stimulation at the same time. PMID:29267230

User-centered development and testing of a monitoring system that provides feedback regarding physical functioning to elderly people

PubMed Central

Vermeulen, Joan; Neyens, Jacques CL; Spreeuwenberg, Marieke D; van Rossum, Erik; Sipers, Walther; Habets, Herbert; Hewson, David J; de Witte, Luc P

2013-01-01

Purpose To involve elderly people during the development of a mobile interface of a monitoring system that provides feedback to them regarding changes in physical functioning and to test the system in a pilot study. Methods and participants The iterative user-centered development process consisted of the following phases: (1) selection of user representatives; (2) analysis of users and their context; (3) identification of user requirements; (4) development of the interface; and (5) evaluation of the interface in the lab. Subsequently, the monitoring and feedback system was tested in a pilot study by five patients who were recruited via a geriatric outpatient clinic. Participants used a bathroom scale to monitor weight and balance, and a mobile phone to monitor physical activity on a daily basis for six weeks. Personalized feedback was provided via the interface of the mobile phone. Usability was evaluated on a scale from 1 to 7 using a modified version of the Post-Study System Usability Questionnaire (PSSUQ); higher scores indicated better usability. Interviews were conducted to gain insight into the experiences of the participants with the system. Results The developed interface uses colors, emoticons, and written and/or spoken text messages to provide daily feedback regarding (changes in) weight, balance, and physical activity. The participants rated the usability of the monitoring and feedback system with a mean score of 5.2 (standard deviation 0.90) on the modified PSSUQ. The interviews revealed that most participants liked using the system and appreciated that it signaled changes in their physical functioning. However, usability was negatively influenced by a few technical errors. Conclusion Involvement of elderly users during the development process resulted in an interface with good usability. However, the technical functioning of the monitoring system needs to be optimized before it can be used to support elderly people in their self-management. PMID:24039407

The hypothalamic neuropeptide oxytocin is required for formation of the neurovascular interface of the pituitary.

PubMed

Gutnick, Amos; Blechman, Janna; Kaslin, Jan; Herwig, Lukas; Belting, Heinz-Georg; Affolter, Markus; Bonkowsky, Joshua L; Levkowitz, Gil

2011-10-18

The hypothalamo-neurohypophyseal system (HNS) is the neurovascular structure through which the hypothalamic neuropeptides oxytocin and arginine-vasopressin exit the brain into the bloodstream, where they go on to affect peripheral physiology. Here, we investigate the molecular cues that regulate the neurovascular contact between hypothalamic axons and neurohypophyseal capillaries of the zebrafish. We developed a transgenic system in which both hypothalamic axons and neurohypophyseal vasculature can be analyzed in vivo. We identified the cellular organization of the zebrafish HNS as well as the dynamic processes that contribute to formation of the HNS neurovascular interface. We show that formation of this interface is regulated during development by local release of oxytocin, which affects endothelial morphogenesis. This cell communication process is essential for the establishment of a tight axovasal interface between the neurons and blood vessels of the HNS. We present a unique example of axons affecting endothelial morphogenesis through secretion of a neuropeptide. Copyright © 2011 Elsevier Inc. All rights reserved.

Towards SSVEP-based, portable, responsive Brain-Computer Interface.

PubMed

Kaczmarek, Piotr; Salomon, Pawel

2015-08-01

A Brain-Computer Interface in motion control application requires high system responsiveness and accuracy. SSVEP interface consisted of 2-8 stimuli and 2 channel EEG amplifier was presented in this paper. The observed stimulus is recognized based on a canonical correlation calculated in 1 second window, ensuring high interface responsiveness. A threshold classifier with hysteresis (T-H) was proposed for recognition purposes. Obtained results suggest that T-H classifier enables to significantly increase classifier performance (resulting in accuracy of 76%, while maintaining average false positive detection rate of stimulus different then observed one between 2-13%, depending on stimulus frequency). It was shown that the parameters of T-H classifier, maximizing true positive rate, can be estimated by gradient-based search since the single maximum was observed. Moreover the preliminary results, performed on a test group (N=4), suggest that for T-H classifier exists a certain set of parameters for which the system accuracy is similar to accuracy obtained for user-trained classifier.

Multimedia courseware in an open-systems environment: a DoD strategy

NASA Astrophysics Data System (ADS)

Welsch, Lawrence A.

1991-03-01

The federal government is about to invest billions of dollars to develop multimedia training materials for delivery on computer-based interactive training systems. Acquisition of a variety of computers and peripheral devices hosting various operating systems and suites of authoring system software will be necessary to facilitate the development of this courseware. There is no single source that will satisfy all needs. Although high-performance, low-cost interactive training hardware is available, the products have proprietary software interfaces. Because the interfaces are proprietary, expensive reprogramming is usually required to adapt such software products to other platforms. This costly reprogramming could be eliminated by adopting standard software interfaces. DoD's Portable Courseware Project (PORTCO) is typical of projects worldwide that require standard software interfaces. This paper articulates the strategy whereby PORTCO leverages the open systems movement and the new realities of information technology. These realities encompass changes in the pace at which new technology becomes available, changes in organizational goals and philosophy, new roles of vendors and users, changes in the procurement process, and acceleration toward open system environments. The PORTCO strategy is applicable to all projects and systems that require open systems to achieve mission objectives. The federal goal is to facilitate the creation of an environment in which high quality portable courseware is available as commercial off-the-shelf products and is competitively supplied by a variety of vendors. In order to achieve this goal a system architecture incorporating standards to meet the users' needs must be established. The Request for Architecture (RFA) developed cooperatively by DoD and the National Institute of Standards and Technology (NIST) will generate the PORTCO systems architecture. This architecture must freely integrate the courseware and authoring software from the lower levels of machine architecture and systems service implementation. In addition, the systems architecture will establish how the application-specific technologies relate to other technologies. Further, a computer-based interactive training applications profile must be developed. This profile, along with the systems architecture derived as a result of the RFA, provides the basis for identifying the needed standards. NIST will then accelerate the development of these standards using, but not restricted to, existing standards activities within established standards forums. The federal multimedia courseware effort has adopted the Interactive Multimedia Association (INA) Recommended Practices for Interactive Video Portability as the baseline for the migration of computer-based interactive training systems to an open systems environment based upon international standards. The PORTCO strategy includes an evolutionary migration to a standards-based, Open System Environments (OSE). An important aspect of this migration strategy is to move to open systems via stepwise evolution rather than via quantum leaps. Another area of concern is that of infrastructure issues, such as maintaining and supporting the technologies required for computer-based interactive training. The federal multimedia initiative will use the RFA-based architecture to differentiate between those technologies that can be maintained and supported by existing infrastructure mechanisms and those that require new mechanisms. Existing infrastructure mechanisms will be used and where infrastructure mechanisms do not exist, the approach will be to place high priority on establishing the appropriate mechanisms. Establishing an infrastructure mechanism is a nontrivial task requiring sustained investment of resources.

Transportability, distributability and rehosting experience with a kernel operating system interface set

NASA Technical Reports Server (NTRS)

Blumberg, F. C.; Reedy, A.; Yodis, E.

1986-01-01

For the past two years, PRC has been transporting and installing a software engineering environment framework, the Automated Product control Environment (APCE), at a number of PRC and government sites on a variety of different hardware. The APCE was designed using a layered architecture which is based on a standardized set of interfaces to host system services. This interface set called the APCE Interface Set (AIS), was designed to support many of the same goals as the Common Ada Programming Support Environment (APSE) Interface Set (CAIS). The APCE was developed to provide support for the full software lifecycle. Specific requirements of the APCE design included: automation of labor intensive administrative and logistical tasks: freedom for project team members to use existing tools: maximum transportability for APCE programs, interoperability of APCE database data, and distributability of both processes and data: and maximum performance on a wide variety of operating systems. A brief description is given of the APCE and AIS, a comparison of the AIS and CAIS both in terms of functionality and of philosophy and approach and a presentation of PRC's experience in rehosting AIS and transporting APCE programs and project data. Conclusions are drawn from this experience with respect to both the CAIS efforts and Space Station plans.

Remotely manned systems: Exploration and operation in space; Proceedings of the First National Conference, California Institute of Technology, Pasadena, Calif., September 13-15, 1972.

NASA Technical Reports Server (NTRS)

Heer, E.

1973-01-01

Free-flying teleoperator systems are discussed, giving attention to earth-orbit mission considerations and Space Tug requirements, free-flying teleoperator requirements and conceptual design, system requirements for a free-flying teleoperator to despin, and the experimental evaluation of remote manipulator systems. Shuttle-Attached Manipulator Systems are considered, together with remote surface vehicle systems, manipulator systems technology, remote sensor and display technology, the man-machine interface, and control and machine intelligence. Nonspace applications are also explored, taking into account implications of nonspace applications, naval applications of remote manipulators, and hand tools and mechanical accessories for a deep submersible. Individual items are announced in this issue.

Design of Epidemia - an Ecohealth Informatics System for Integrated Forecasting of Malaria Epidemics

NASA Astrophysics Data System (ADS)

Wimberly, M. C.; Bayabil, E.; Beyane, B.; Bishaw, M.; Henebry, G. M.; Lemma, A.; Liu, Y.; Merkord, C. L.; Mihretie, A.; Senay, G. B.; Yalew, W.

2014-12-01

Early warning of the timing and locations of malaria epidemics can facilitate the targeting of resources for prevention and emergency response. In response to this need, we are developing the Epidemic Prognosis Incorporating Disease and Environmental Monitoring for Integrated Assessment (EPIDEMIA) computer system. The system incorporates software for capturing, processing, and integrating environmental and epidemiological data from multiple sources; data assimilation techniques that continually update models and forecasts; and a web-based interface that makes the resulting information available to public health decision makers. This technology will enable forecasts based on lagged responses to environmental risk factors as well as information about recent trends in malaria cases. Environmental driving variables will include a variety of remote-sensed hydrological indicators. EPIDEMIA will be implemented and tested in the Amhara Region of Ethiopia in collaboration with local stakeholders. We conducted an initial co-design workshop in July 2014 that included environmental scientists, software engineers, and participants from the NGO, academic, and public health sectors in Ethiopia. A prototype of the EPIDEMIA web interface was presented and a requirements analysis was conducted to characterize the main use cases for the public health community, identify the critical data requirements for malaria risk modeling, and develop of a list of baseline features for the public health interface. Several critical system features were identified, including a secure web-based interface for uploading and validating surveillance data; a flexible query system to allow retrieval of environmental and epidemiological data summaries as tables, charts, and maps; and an alert system to provide automatic warnings in response to environmental and epidemiological risk factors for malaria. Future system development will involve a cycle of implementation, training, usability testing, and upgrading. This innovative translational bioinformatics approach will allow us to assess the practical effectiveness of these tools as we continually improve the technologies.

Intelligent systems technology infrastructure for integrated systems

NASA Technical Reports Server (NTRS)

Lum, Henry, Jr.

1991-01-01

Significant advances have occurred during the last decade in intelligent systems technologies (a.k.a. knowledge-based systems, KBS) including research, feasibility demonstrations, and technology implementations in operational environments. Evaluation and simulation data obtained to date in real-time operational environments suggest that cost-effective utilization of intelligent systems technologies can be realized for Automated Rendezvous and Capture applications. The successful implementation of these technologies involve a complex system infrastructure integrating the requirements of transportation, vehicle checkout and health management, and communication systems without compromise to systems reliability and performance. The resources that must be invoked to accomplish these tasks include remote ground operations and control, built-in system fault management and control, and intelligent robotics. To ensure long-term evolution and integration of new validated technologies over the lifetime of the vehicle, system interfaces must also be addressed and integrated into the overall system interface requirements. An approach for defining and evaluating the system infrastructures including the testbed currently being used to support the on-going evaluations for the evolutionary Space Station Freedom Data Management System is presented and discussed. Intelligent system technologies discussed include artificial intelligence (real-time replanning and scheduling), high performance computational elements (parallel processors, photonic processors, and neural networks), real-time fault management and control, and system software development tools for rapid prototyping capabilities.

Network and user interface for PAT DOME virtual motion environment system

NASA Technical Reports Server (NTRS)

Worthington, J. W.; Duncan, K. M.; Crosier, W. G.

1993-01-01

The Device for Orientation and Motion Environments Preflight Adaptation Trainer (DOME PAT) provides astronauts a virtual microgravity sensory environment designed to help alleviate tye symptoms of space motion sickness (SMS). The system consists of four microcomputers networked to provide real time control, and an image generator (IG) driving a wide angle video display inside a dome structure. The spherical display demands distortion correction. The system is currently being modified with a new graphical user interface (GUI) and a new Silicon Graphics IG. This paper will concentrate on the new GUI and the networking scheme. The new GUI eliminates proprietary graphics hardware and software, and instead makes use of standard and low cost PC video (CGA) and off the shelf software (Microsoft's Quick C). Mouse selection for user input is supported. The new Silicon Graphics IG requires an Ethernet interface. The microcomputer known as the Real Time Controller (RTC), which has overall control of the system and is written in Ada, was modified to use the free public domain NCSA Telnet software for Ethernet communications with the Silicon Graphics IG. The RTC also maintains the original ARCNET communications through Novell Netware IPX with the rest of the system. The Telnet TCP/IP protocol was first used for real-time communication, but because of buffering problems the Telnet datagram (UDP) protocol needed to be implemented. Since the Telnet modules are written in C, the Adap pragma 'Interface' was used to interface with the network calls.

Procurement specification color graphic camera system

NASA Technical Reports Server (NTRS)

Prow, G. E.

1980-01-01

The performance and design requirements for a Color Graphic Camera System are presented. The system is a functional part of the Earth Observation Department Laboratory System (EODLS) and will be interfaced with Image Analysis Stations. It will convert the output of a raster scan computer color terminal into permanent, high resolution photographic prints and transparencies. Images usually displayed will be remotely sensed LANDSAT imager scenes.

ORBIT: an integrated environment for user-customized bioinformatics tools.

PubMed

Bellgard, M I; Hiew, H L; Hunter, A; Wiebrands, M

1999-10-01

There are a large number of computational programs freely available to bioinformaticians via a client/server, web-based environment. However, the client interface to these tools (typically an html form page) cannot be customized from the client side as it is created by the service provider. The form page is usually generic enough to cater for a wide range of users. However, this implies that a user cannot set as 'default' advanced program parameters on the form or even customize the interface to his/her specific requirements or preferences. Currently, there is a lack of end-user interface environments that can be modified by the user when accessing computer programs available on a remote server running on an intranet or over the Internet. We have implemented a client/server system called ORBIT (Online Researcher's Bioinformatics Interface Tools) where individual clients can have interfaces created and customized to command-line-driven, server-side programs. Thus, Internet-based interfaces can be tailored to a user's specific bioinformatic needs. As interfaces are created on the client machine independent of the server, there can be different interfaces to the same server-side program to cater for different parameter settings. The interface customization is relatively quick (between 10 and 60 min) and all client interfaces are integrated into a single modular environment which will run on any computer platform supporting Java. The system has been developed to allow for a number of future enhancements and features. ORBIT represents an important advance in the way researchers gain access to bioinformatics tools on the Internet.

Advanced software integration: The case for ITV facilities

NASA Technical Reports Server (NTRS)

Garman, John R.

1990-01-01

The array of technologies and methodologies involved in the development and integration of avionics software has moved almost as rapidly as computer technology itself. Future avionics systems involve major advances and risks in the following areas: (1) Complexity; (2) Connectivity; (3) Security; (4) Duration; and (5) Software engineering. From an architectural standpoint, the systems will be much more distributed, involve session-based user interfaces, and have the layered architectures typified in the layers of abstraction concepts popular in networking. Typified in the NASA Space Station Freedom will be the highly distributed nature of software development itself. Systems composed of independent components developed in parallel must be bound by rigid standards and interfaces, the clean requirements and specifications. Avionics software provides a challenge in that it can not be flight tested until the first time it literally flies. It is the binding of requirements for such an integration environment into the advances and risks of future avionics systems that form the basis of the presented concept and the basic Integration, Test, and Verification concept within the development and integration life cycle of Space Station Mission and Avionics systems.

General Mission Analysis Tool (GMAT) Architectural Specification. Draft

NASA Technical Reports Server (NTRS)

Hughes, Steven P.; Conway, Darrel, J.

2007-01-01

Early in 2002, Goddard Space Flight Center (GSFC) began to identify requirements for the flight dynamics software needed to fly upcoming missions that use formations of spacecraft to collect data. These requirements ranged from low level modeling features to large scale interoperability requirements. In 2003 we began work on a system designed to meet these requirement; this system is GMAT. The General Mission Analysis Tool (GMAT) is a general purpose flight dynamics modeling tool built on open source principles. The GMAT code is written in C++, and uses modern C++ constructs extensively. GMAT can be run through either a fully functional Graphical User Interface (GUI) or as a command line program with minimal user feedback. The system is built and runs on Microsoft Windows, Linux, and Macintosh OS X platforms. The GMAT GUI is written using wxWidgets, a cross platform library of components that streamlines the development and extension of the user interface Flight dynamics modeling is performed in GMAT by building components that represent the players in the analysis problem that is being modeled. These components interact through the sequential execution of instructions, embodied in the GMAT Mission Sequence. A typical Mission Sequence will model the trajectories of a set of spacecraft evolving over time, calculating relevant parameters during this propagation, and maneuvering individual spacecraft to maintain a set of mission constraints as established by the mission analyst. All of the elements used in GMAT for mission analysis can be viewed in the GMAT GUI or through a custom scripting language. Analysis problems modeled in GMAT are saved as script files, and these files can be read into GMAT. When a script is read into the GMAT GUI, the corresponding user interface elements are constructed in the GMAT GUI. The GMAT system was developed from the ground up to run in a platform agnostic environment. The source code compiles on numerous different platforms, and is regularly exercised running on Windows, Linux and Macintosh computers by the development and analysis teams working on the project. The system can be run using either a graphical user interface, written using the open source wxWidgets framework, or from a text console. The GMAT source code was written using open source tools. GSFC has released the code using the NASA open source license.

Operator interface design considerations for a PACS information management system

NASA Astrophysics Data System (ADS)

Steinke, James E.; Nabijee, Kamal H.; Freeman, Rick H.; Prior, Fred W.

1990-08-01

As prototype PACS grow into fully digital departmental and hospital-wide systems, effective information storage and retrieval mechanisms become increasingly important. Thus far, designers of PACS workstations have concentrated on image communication and display functionality. The new challenge is to provide appropriate operator interface environments to facilitate information retrieval. The "Marburg Model" 1 provides a detailed analysis of the functions, control flows and data structures used in Radiology. It identifies a set of "actors" who perform information manipulation functions. Drawing on this model and its associated methodology it is possible to identify four modes of use of information systems in Radiology: Clinical Routine, Research, Consultation, and Administration. Each mode has its own specific access requirements and views of information. An operator interface strategy appropriate for each mode will be proposed. Clinical Routine mode is the principal concern of PACS primary diagnosis workstations. In a full PACS implementation, such workstations must provide a simple and consistent navigational aid for the on-line image database, a local work list of cases to be reviewed, and easy access to information from other hospital information systems. A hierarchical method of information access is preferred because it provides the ability to start at high-level entities and iteratively narrow the scope of information from which to select subsequent operations. An implementation using hierarchical, nested software windows which fulfills such requirements shall be examined.

Early-Stage Software Design for Usability

ERIC Educational Resources Information Center

Golden, Elspeth

2010-01-01

In spite of the goodwill and best efforts of software engineers and usability professionals, systems continue to be built and released with glaring usability flaws that are costly and difficult to fix after the system has been built. Although user interface (UI) designers, be they usability or design experts, communicate usability requirements to…

Multimedia Courseware in an Open Systems Environment: A Federal Strategy.

ERIC Educational Resources Information Center

Moline, Judi; And Others

The Portable Courseware Project (PORTCO) of the U.S. Department of Defense (DoD) is typical of projects worldwide that require standard software interfaces. This paper articulates the strategy whereby the federal multimedia courseware initiative leverages the open systems movement and the new realities of information technology. The federal…

CHIMERA II - A real-time multiprocessing environment for sensor-based robot control

NASA Technical Reports Server (NTRS)

Stewart, David B.; Schmitz, Donald E.; Khosla, Pradeep K.

1989-01-01

A multiprocessing environment for a wide variety of sensor-based robot system, providing the flexibility, performance, and UNIX-compatible interface needed for fast development of real-time code is addressed. The requirements imposed on the design of a programming environment for sensor-based robotic control is outlined. The details of the current hardware configuration are presented, along with the details of the CHIMERA II software. Emphasis is placed on the kernel, low-level interboard communication, user interface, extended file system, user-definable and dynamically selectable real-time schedulers, remote process synchronization, and generalized interprocess communication. A possible implementation of a hierarchical control model, the NASA/NBS standard reference model for telerobot control system is demonstrated.

Plutonium Immobilization Project System Design Description for Can Loading System

DOE Office of Scientific and Technical Information (OSTI.GOV)

Kriikku, E.

2001-02-15

The purpose of this System Design Description (SDD) is to specify the system and component functions and requirements for the Can Loading System and provide a complete description of the system (design features, boundaries, and interfaces), principles of operation (including upsets and recovery), and the system maintenance approach. The Plutonium Immobilization Project (PIP) will immobilize up to 13 metric tons (MT) of U.S. surplus weapons usable plutonium materials.

Department of Defense Air Traffic Control and Airspace Systems Interface with the National Airspace System

DTIC Science & Technology

1990-03-30

systems on the DoD in terms of safety and operational- effectiveness and probable impacts on specific Air Force mission requirements. The report does... Systems ................................. 2-21 2.1.3 Flight Service and Weather Systems .......................... 2-22 2.1.3.1 Flight Service Automation...2-41 2.2.2 Terminal Control and Landing Systems .. ....................... 2-44 2.2.3 Flight Information and Weather Systems

Advanced flight control system study

NASA Technical Reports Server (NTRS)

Mcgough, J.; Moses, K.; Klafin, J. F.

1982-01-01

The architecture, requirements, and system elements of an ultrareliable, advanced flight control system are described. The basic criteria are functional reliability of 10 to the minus 10 power/hour of flight and only 6 month scheduled maintenance. A distributed system architecture is described, including a multiplexed communication system, reliable bus controller, the use of skewed sensor arrays, and actuator interfaces. Test bed and flight evaluation program are proposed.

MSFC Propulsion Systems Department Knowledge Management Project

NASA Technical Reports Server (NTRS)

Caraccioli, Paul A.

2007-01-01

This slide presentation reviews the Knowledge Management (KM) project of the Propulsion Systems Department at Marshall Space Flight Center. KM is needed to support knowledge capture, preservation and to support an information sharing culture. The presentation includes the strategic plan for the KM initiative, the system requirements, the technology description, the User Interface and custom features, and a search demonstration.

Reducing Lifecycle Sustainment Costs

DTIC Science & Technology

2015-05-01

ahead of government systems – Specific O&S needs in government: depots, software centers, VAMOSC/ ERP interfaces Implications of ERP Systems...funding is not allocated for its implementation .  Technology Refresh often requires non-recurring engineering investment, but the Working Capital Funds...VAMOSC Systems – Cost and Software Data Reports (CSDRs) • Contractor Logistics Support Contracts • Includes subcontractor reporting – Effects of

Power Extension Package (PEP) system definition extension, orbital service module systems analysis study. Volume 2: PEP

NASA Technical Reports Server (NTRS)

1979-01-01

User power, duration, and orbit requirements, which were the prime factors influencing power extension package (PEP) design, are discussed. A representative configuration of the PEP concept is presented and the major elements of the system are described as well as the PEP-to-Orbiter and remote manipulator interface provisions.

Spool pieces at the SSCL

DOE Office of Scientific and Technical Information (OSTI.GOV)

Clayton, T.; Cai, Y.; Smellie, R.

1993-05-01

The basic features of the Superconducting Super Collider lattice are the two beamlines formed by superconducting dipoles (7736) and quadrupoles (1564). The dipoles constraint two 20 TeV proton beams into counterrotating closed orbits of 86.2 km. The quadrupoles (FODO) require cryogenic cooling the LHe temperatures. This requirement isolates the main magnets from the outside world. The interface required, the spool, is a crucial component of superconducting lattice design and machine operation. There are over 1588 spools in the Super Collider. We present hear SSCL spool designs which consist of (1) housing for superconducting closed orbit and multipole correction magnets, (2)more » cryogenic function, magnet quench protection, system power, and instrumentation interfaces, and (3) cold to warm transitions for ware magnet and warm instrumentation drift spaces.« less

Earth radiation budget measurement from a spinning satellite: Conceptual design of detectors

NASA Technical Reports Server (NTRS)

Sromovsky, L. A.; Revercomb, H. E.; Suomi, V. E.

1975-01-01

The conceptual design, sensor characteristics, sensor performance and accuracy, and spacecraft and orbital requirements for a spinning wide-field-of-view earth energy budget detector were investigated. The scientific requirements for measurement of the earth's radiative energy budget are presented. Other topics discussed include the observing system concept, solar constant radiometer design, plane flux wide FOV sensor design, fast active cavity theory, fast active cavity design and error analysis, thermopile detectors as an alternative, pre-flight and in-flight calibration plane, system error summary, and interface requirements.

Operability of Space Station Freedom's meteoroid/debris protection system

NASA Technical Reports Server (NTRS)

Kahl, Maggie S.; Stokes, Jack W.

1992-01-01

The design of Space Station Freedom's external structure must not only protect the spacecraft from the hazardous environment, but also must be compatible with the extra vehicular activity system for assembly and maintenance. The external procedures for module support are utility connections, external orbital replaceable unit changeout, and maintenance of the meteoroid/debris shields and multilayer insulation. All of these interfaces require proper man-machine engineering to be compatible with the extra vehicular activity and manipulator systems. This paper discusses design solutions, including those provided for human interface, to the Space Station Freedom meteoroid/debris protection system. The system advantages and current access capabilities are illustrated through analysis of its configuration over the Space Station Freedom resource nodes and common modules, with emphasis on the cylindrical sections and endcones.

Combining a hybrid robotic system with a bain-machine interface for the rehabilitation of reaching movements: A case study with a stroke patient.

PubMed

Resquin, F; Ibañez, J; Gonzalez-Vargas, J; Brunetti, F; Dimbwadyo, I; Alves, S; Carrasco, L; Torres, L; Pons, Jose Luis

2016-08-01

Reaching and grasping are two of the most affected functions after stroke. Hybrid rehabilitation systems combining Functional Electrical Stimulation with Robotic devices have been proposed in the literature to improve rehabilitation outcomes. In this work, we present the combined use of a hybrid robotic system with an EEG-based Brain-Machine Interface to detect the user's movement intentions to trigger the assistance. The platform has been tested in a single session with a stroke patient. The results show how the patient could successfully interact with the BMI and command the assistance of the hybrid system with low latencies. Also, the Feedback Error Learning controller implemented in this system could adjust the required FES intensity to perform the task.