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.

Earth Observing System (EOS) Advanced Microwave Sounding Unit-A (AMSU-A): Instrumentation interface control document

NASA Technical Reports Server (NTRS)

1994-01-01

This Interface Control Document (ICD) defines the specific details of the complete accomodation information between the Earth Observing System (EOS) PM Spacecraft and the Advanced Microwave Sounding Unit (AMSU-A)Instrument. This is the first submittal of the ICN: it will be updated periodically throughout the life of the program. The next update is planned prior to Critical Design Review (CDR).

Representation-based user interfaces for the audiovisual library of the year 2000

NASA Astrophysics Data System (ADS)

Aigrain, Philippe; Joly, Philippe; Lepain, Philippe; Longueville, Veronique

1995-03-01

The audiovisual library of the future will be based on computerized access to digitized documents. In this communication, we address the user interface issues which will arise from this new situation. One cannot simply transfer a user interface designed for the piece by piece production of some audiovisual presentation and make it a tool for accessing full-length movies in an electronic library. One cannot take a digital sound editing tool and propose it as a means to listen to a musical recording. In our opinion, when computers are used as mediations to existing contents, document representation-based user interfaces are needed. With such user interfaces, a structured visual representation of the document contents is presented to the user, who can then manipulate it to control perception and analysis of these contents. In order to build such manipulable visual representations of audiovisual documents, one needs to automatically extract structural information from the documents contents. In this communication, we describe possible visual interfaces for various temporal media, and we propose methods for the economically feasible large scale processing of documents. The work presented is sponsored by the Bibliotheque Nationale de France: it is part of the program aiming at developing for image and sound documents an experimental counterpart to the digitized text reading workstation of this library.

International interface design for Space Station Freedom - Challenges and solutions

NASA Technical Reports Server (NTRS)

Mayo, Richard E.; Bolton, Gordon R.; Laurini, Daniele

1988-01-01

The definition of interfaces for the International Space Station is discussed, with a focus on negotiations between NASA and ESA. The program organization and division of responsibilities for the Space Station are outlined; the basic features of physical and functional interfaces are described; and particular attention is given to the interface management and documentation procedures, architectural control elements, interface implementation and verification, and examples of Columbus interface solutions (including mechanical, ECLSS, thermal-control, electrical, data-management, standardized user, and software interfaces). Diagrams, drawings, graphs, and tables listing interface types are provided.

Save medical personnel's time by improved user interfaces.

PubMed

Kindler, H

1997-01-01

Common objectives in the industrial countries are the improvement of quality of care, clinical effectiveness, and cost control. Cost control, in particular, has been addressed through the introduction of case mix systems for reimbursement by social-security institutions. More data is required to enable quality improvement, increases in clinical effectiveness and for juridical reasons. At first glance, this documentation effort is contradictory to cost reduction. However, integrated services for resource management based on better documentation should help to reduce costs. The clerical effort for documentation should be decreased by providing a co-operative working environment for healthcare professionals applying sophisticated human-computer interface technology. Additional services, e.g., automatic report generation, increase the efficiency of healthcare personnel. Modelling the medical work flow forms an essential prerequisite for integrated resource management services and for co-operative user interfaces. A user interface aware of the work flow provides intelligent assistance by offering the appropriate tools at the right moment. Nowadays there is a trend to client/server systems with relational databases or object-oriented databases as repository. The work flows used for controlling purposes and to steer the user interfaces must be represented in the repository.

10 CFR Appendix B to Part 50 - Quality Assurance Criteria for Nuclear Power Plants and Fuel Reprocessing Plants

Code of Federal Regulations, 2012 CFR

2012-01-01

... executing. III. Design Control Measures shall be established to assure that applicable regulatory... control of design interfaces and for coordination among participating design organizations. These measures..., approval, release, distribution, and revision of documents involving design interfaces. The design control...

10 CFR Appendix B to Part 50 - Quality Assurance Criteria for Nuclear Power Plants and Fuel Reprocessing Plants

Code of Federal Regulations, 2013 CFR

2013-01-01

... executing. III. Design Control Measures shall be established to assure that applicable regulatory... control of design interfaces and for coordination among participating design organizations. These measures..., approval, release, distribution, and revision of documents involving design interfaces. The design control...

Orbiter middeck/payload standard interfaces control document

NASA Technical Reports Server (NTRS)

1984-01-01

The interfaces which shall be provided by the baseline shuttle mid-deck for payload use within the mid-deck area are defined, as well as all constraints which shall be observed by all the users of the defined interfaces. Commonality was established with respect to analytical approaches, analytical models, technical data and definitions for integrated analyses by all the interfacing parties. Any payload interfaces that are out of scope with the standard interfaces defined shall be defined in a Payload Unique Interface Control Document (ICD) for a given payload. Each Payload Unique ICD will have comparable paragraphs to this ICD and will have a corresponding notation of A, for applicable; N/A, for not applicable; N, for note added for explanation; and E, for exception. On any flight, the STS reserves the right to assign locations to both payloads mounted on an adapter plate(s) and payloads stored within standard lockers. Specific locations requests and/or requirements exceeding standard mid-deck payload requirements may result in a reduction in manifesting opportunities.

Cockpit Interfaces, Displays, and Alerting Messages for the Interval Management Alternative Clearances (IMAC) Experiment

NASA Technical Reports Server (NTRS)

Baxley, Brian T.; Palmer, Michael T.; Swieringa, Kurt A.

2015-01-01

This document describes the IM cockpit interfaces, displays, and alerting capabilities that were developed for and used in the IMAC experiment, which was conducted at NASA Langley in the summer of 2015. Specifically, this document includes: (1) screen layouts for each page of the interface; (2) step-by-step instructions for data entry, data verification and input error correction; (3) algorithm state messages and error condition alerting messages; (4) aircraft speed guidance and deviation indications; and (5) graphical display of the spatial relationships between the Ownship aircraft and the Target aircraft. The controller displays for IM will be described in a separate document.

NAS (Host/ARTS) IIIA to VME Modem Interface ATC Interface Hardware Manual

DOT National Transportation Integrated Search

1990-10-01

This document is reference material for personnel using the National Airspace : System (NAS) (HOST or ARTS IIIA) Air Traffic Control (ATC) Interface Subsystem. : It was originally developed to be part of the Data Link Test and Analysis System : (DATA...

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.

Unified Desktop for Monitoring & Control Applications - The Open Navigator Framework Applied for Control Centre and EGSE Applications

NASA Astrophysics Data System (ADS)

Brauer, U.

2007-08-01

The Open Navigator Framework (ONF) was developed to provide a unified and scalable platform for user interface integration. The main objective for the framework was to raise usability of monitoring and control consoles and to provide a reuse of software components in different application areas. ONF is currently applied for the Columbus onboard crew interface, the commanding application for the Columbus Control Centre, the Columbus user facilities specialized user interfaces, the Mission Execution Crew Assistant (MECA) study and EADS Astrium internal R&D projects. ONF provides a well documented and proven middleware for GUI components (Java plugin interface, simplified concept similar to Eclipse). The overall application configuration is performed within a graphical user interface for layout and component selection. The end-user does not have to work in the underlying XML configuration files. ONF was optimized to provide harmonized user interfaces for monitoring and command consoles. It provides many convenience functions designed together with flight controllers and onboard crew: user defined workspaces, incl. support for multi screens efficient communication mechanism between the components integrated web browsing and documentation search &viewing consistent and integrated menus and shortcuts common logging and application configuration (properties) supervision interface for remote plugin GUI access (web based) A large number of operationally proven ONF components have been developed: Command Stack & History: Release of commands and follow up the command acknowledges System Message Panel: Browse, filter and search system messages/events Unified Synoptic System: Generic synoptic display system Situational Awareness : Show overall subsystem status based on monitoring of key parameters System Model Browser: Browse mission database defintions (measurements, commands, events) Flight Procedure Executor: Execute checklist and logical flow interactive procedures Web Browser : Integrated browser reference documentation and operations data Timeline Viewer: View master timeline as Gantt chart Search: Local search of operations products (e.g. documentation, procedures, displays) All GUI components access the underlying spacecraft data (commanding, reporting data, events, command history) via a common library providing adaptors for the current deployments (Columbus MCS, Columbus onboard Data Management System, Columbus Trainer raw packet protocol). New Adaptors are easy to develop. Currently an adaptor to SCOS 2000 is developed as part of a study for the ESTEC standardization section ("USS for ESTEC Reference Facility").

Managing operational documentation in the ALICE Detector Control System

NASA Astrophysics Data System (ADS)

Lechman, M.; Augustinus, A.; Bond, P.; Chochula, P.; Kurepin, A.; Pinazza, O.; Rosinsky, P.

2012-12-01

ALICE (A Large Ion Collider Experiment) is one of the big LHC (Large Hadron Collider) experiments at CERN in Geneve, Switzerland. The experiment is composed of 18 sub-detectors controlled by an integrated Detector Control System (DCS) that is implemented using the commercial SCADA package PVSSII. The DCS includes over 1200 network devices, over 1,000,000 monitored parameters and numerous custom made software components that are prepared by over 100 developers from all around the world. This complex system is controlled by a single operator via a central user interface. One of his/her main tasks is the recovery of anomalies and errors that may occur during operation. Therefore, clear, complete and easily accessible documentation is essential to guide the shifter through the expert interfaces of different subsystems. This paper describes the idea of the management of the operational documentation in ALICE using a generic repository that is built on a relational database and is integrated with the control system. The experience gained and the conclusions drawn from the project are also presented.

B-Plant Canyon Ventilation Control System Description

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

MCDANIEL, K.S.

1999-08-31

Project W-059 installed a new B Plant Canyon Ventilation System. Monitoring and control of the system is implemented by the Canyon Ventilation Control System (CVCS). This document describes the CVCS system components which include a Programmable Logic Controller (PLC) coupled with an Operator Interface Unit (OIU) and application software. This document also includes an Alarm Index specifying the setpoints and technical basis for system analog and digital alarms.

Development of an interface for an ultrareliable fault-tolerant control system and an electronic servo-control unit

NASA Technical Reports Server (NTRS)

Shaver, Charles; Williamson, Michael

1986-01-01

The NASA Ames Research Center sponsors a research program for the investigation of Intelligent Flight Control Actuation systems. The use of artificial intelligence techniques in conjunction with algorithmic techniques for autonomous, decentralized fault management of flight-control actuation systems is explored under this program. The design, development, and operation of the interface for laboratory investigation of this program is documented. The interface, architecturally based on the Intel 8751 microcontroller, is an interrupt-driven system designed to receive a digital message from an ultrareliable fault-tolerant control system (UFTCS). The interface links the UFTCS to an electronic servo-control unit, which controls a set of hydraulic actuators. It was necessary to build a UFTCS emulator (also based on the Intel 8751) to provide signal sources for testing the equipment.

Space station automation of common module power management and distribution, volume 2

NASA Technical Reports Server (NTRS)

Ashworth, B.; Riedesel, J.; Myers, C.; Jakstas, L.; Smith, D.

1990-01-01

The new Space Station Module Power Management and Distribution System (SSM/PMAD) testbed automation system is described. The subjects discussed include testbed 120 volt dc star bus configuration and operation, SSM/PMAD automation system architecture, fault recovery and management expert system (FRAMES) rules english representation, the SSM/PMAD user interface, and the SSM/PMAD future direction. Several appendices are presented and include the following: SSM/PMAD interface user manual version 1.0, SSM/PMAD lowest level processor (LLP) reference, SSM/PMAD technical reference version 1.0, SSM/PMAD LLP visual control logic representation's (VCLR's), SSM/PMAD LLP/FRAMES interface control document (ICD) , and SSM/PMAD LLP switchgear interface controller (SIC) ICD.

Virtual workstations and telepresence interfaces: Design accommodations and prototypes for Space Station Freedom evolution

NASA Technical Reports Server (NTRS)

Mcgreevy, Michael W.

1990-01-01

An advanced human-system interface is being developed for evolutionary Space Station Freedom as part of the NASA Office of Space Station (OSS) Advanced Development Program. The human-system interface is based on body-pointed display and control devices. The project will identify and document the design accommodations ('hooks and scars') required to support virtual workstations and telepresence interfaces, and prototype interface systems will be built, evaluated, and refined. The project is a joint enterprise of Marquette University, Astronautics Corporation of America (ACA), and NASA's ARC. The project team is working with NASA's JSC and McDonnell Douglas Astronautics Company (the Work Package contractor) to ensure that the project is consistent with space station user requirements and program constraints. Documentation describing design accommodations and tradeoffs will be provided to OSS, JSC, and McDonnell Douglas, and prototype interface devices will be delivered to ARC and JSC. ACA intends to commercialize derivatives of the interface for use with computer systems developed for scientific visualization and system simulation.

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.

Atmospheric, Magnetospheric and Plasmas in Space (AMPS) spacelab payload definition study. Volume 3: Interface control documents. Part 1: AMPS payload to shuttle ICD

NASA Technical Reports Server (NTRS)

1976-01-01

Physical, functional, and operational interfaces between the space shuttle orbiter and the AMPS payload are described for the ground handling and test phases, prelaunch, launch and ascent, operational, stowage, and reentry and landing activities.

AgRISTARS: Yield model development/soil moisture. Interface control document

NASA Technical Reports Server (NTRS)

1980-01-01

The interactions and support functions required between the crop Yield Model Development (YMD) Project and Soil Moisture (SM) Project are defined. The requirements for YMD support of SM and vice-versa are outlined. Specific tasks in support of these interfaces are defined for development of support functions.

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.

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.

Meteorological Support Interface Control Working Group (MSICWG) Instrumentation, Data Format, and Networks Document

NASA Technical Reports Server (NTRS)

Brenton, James; Roberts, Barry C.

2017-01-01

The purpose of this document is to provide an overview of instrumentation discussed at the Meteorological Interface Control Working Group (MSICWG), a reference for data formats currently used by members of the group, a summary of proposed formats for future use by the group, an overview of the data networks of the group's members. This document will be updated as new systems are introduced, old systems are retired, and when the MSICWG community necessitates a change to the formats. The MSICWG consists of personnel from the National Aeronautics and Space Administration (NASA) Kennedy Space Center (KSC), NASA Marshall Space Flight Center (MSFC), NASA Johnson Space Center (JSC), National Oceanic and Atmospheric Administration National Weather Service Spaceflight Meteorology Group (SMG), and the United States Air Force (USAF) 45th Space Wing and Weather Squadron. The purpose of the group is to coordinate the distribution of weather related data to support NASA space launch related activities.

Interface definition for the Far Ultraviolet Spectrometer Experiment S169

NASA Technical Reports Server (NTRS)

Fastie, W. G.

1971-01-01

A final contract for development, fabrication, test and flight of the ultraviolet spectrometer experiment on an Apollo space mission is reported. Two interface control documents were completed and signed off and three more were essentially completed. Supporting preliminary concepts formulation, design study and component investigation, specification and subcontract negotiation were accomplished.

Study of orbiter/payload interface communications configuration control board directive from an operational perspective

NASA Technical Reports Server (NTRS)

Addis, A. W.; Tatosian, C. G.; Lidsey, J. F.

1974-01-01

Orbiter/payload data and communications interface was examined. It was found that the Configuration Control Board Directive (CCBD) greatly increases the capability of the orbiter to communicate with a wide variety of projected shuttle payloads. Rather than being derived from individual payload communication requirements, the CCBD appears to be based on an operational philosophy that requires the orbiter to duplicate or augment the ground network/payload communication links. It is suggested that the implementation of the CCBD be reviewed and compared with the Level 1 Program Requirements Document, differences reconciled, and interface characteristics defined.

Cardiopulmonary data acquisition system. Version 2.0, volume 2: Detailed software/hardware documentation

NASA Technical Reports Server (NTRS)

1980-01-01

Detailed software and hardware documentation for the Cardiopulmonary Data Acquisition System is presented. General wiring and timing diagrams are given including those for the LSI-11 computer control panel and interface cables. Flowcharts and complete listings of system programs are provided along with the format of the floppy disk file.

Basic Electronic Design for Proposed NMSU Hitchhiker Payload

NASA Technical Reports Server (NTRS)

Horan, Stephen

2000-01-01

This document presents the bas'c hardware design developed by the EE 499 class during the spring semester of the 1999-2000 academic year. This design covers the electrical components to supply power to the experiments, the computer software and interfaces to control the experiments, and the ground data processing to provide an operator interface. This document is a follow-on to the Payload Mission description document and the System Requirements document developed during the EE 498 class during the fall semester. The design activities are broken down by functional area within the structure. For each area, we give the requirements that need to be met and the design to meet the requirements. For each of these areas, a prototype selection of hardware and/or software was done by the class and the components assembled as part of the class to verify that they worked as intended.

Microcomputer Interfaces with U.S. Marine Corps Tactical Communications Systems,

DTIC Science & Technology

1991-04-01

Schneider and Mrs. Kirkpatrick at the Communications officer School Quantico, Virginia This document has been approvedf or p,bic Yleaze cncd sae; its...communications systems; however, there is not a comprehensive USMC Command, Control, Communications, and Computers (C4) operational policy that documents these...5-6 COMMUNICATIONS SYSTEMS .... ............. 5-6 ADP SYSTEMS ....... .................. 5-6 OPERATIONAL POLICIES

User-Friendly Interface Developed for a Web-Based Service for SpaceCAL Emulations

NASA Technical Reports Server (NTRS)

Liszka, Kathy J.; Holtz, Allen P.

2004-01-01

A team at the NASA Glenn Research Center is developing a Space Communications Architecture Laboratory (SpaceCAL) for protocol development activities for coordinated satellite missions. SpaceCAL will provide a multiuser, distributed system to emulate space-based Internet architectures, backbone networks, formation clusters, and constellations. As part of a new effort in 2003, building blocks are being defined for an open distributed system to make the satellite emulation test bed accessible through an Internet connection. The first step in creating a Web-based service to control the emulation remotely is providing a user-friendly interface for encoding the data into a well-formed and complete Extensible Markup Language (XML) document. XML provides coding that allows data to be transferred between dissimilar systems. Scenario specifications include control parameters, network routes, interface bandwidths, delay, and bit error rate. Specifications for all satellite, instruments, and ground stations in a given scenario are also included in the XML document. For the SpaceCAL emulation, the XML document can be created using XForms, a Webbased forms language for data collection. Contrary to older forms technology, the interactive user interface makes the science prevalent, not the data representation. Required versus optional input fields, default values, automatic calculations, data validation, and reuse will help researchers quickly and accurately define missions. XForms can apply any XML schema defined for the test mission to validate data before forwarding it to the emulation facility. New instrument definitions, facilities, and mission types can be added to the existing schema. The first prototype user interface incorporates components for interactive input and form processing. Internet address, data rate, and the location of the facility are implemented with basic form controls with default values provided for convenience and efficiency using basic XForms operations. Because different emulation scenarios will vary widely in their component structure, more complex operations are used to add and delete facilities.

Interface for the documentation and compilation of a library of computer models in physiology.

PubMed Central

Summers, R. L.; Montani, J. P.

1994-01-01

A software interface for the documentation and compilation of a library of computer models in physiology was developed. The interface is an interactive program built within a word processing template in order to provide ease and flexibility of documentation. A model editor within the interface directs the model builder as to standardized requirements for incorporating models into the library and provides the user with an index to the levels of documentation. The interface and accompanying library are intended to facilitate model development, preservation and distribution and will be available for public use. PMID:7950046

HSI Guidelines Outline for the Air Vehicle Control Station. Version 2

NASA Technical Reports Server (NTRS)

2006-01-01

This document provides guidance to the FAA and manufacturers on how to develop UAS Pilot Vehicle Interfaces to safely and effectively integrate UASs into the NAS. Preliminary guidelines are provided for Aviate, Communicate, Navigate and Avoid Hazard functions. The pilot shall have information and control capability so that pilot-UA interactions are not adverse, unfavorable, nor compromise safety. Unfavorable interactions include anomalous aircraft-pilot coupling (APC) interactions (closed loop), pilot-involved oscillations (categories I, II or III), and non-oscillatory APC events (e.g., divergence). - Human Systems Integration Pilot-Technology Interface Requirements for Command, Control, and Communications (C3)

Comparing two anesthesia information management system user interfaces: a usability evaluation.

PubMed

Wanderer, Jonathan P; Rao, Anoop V; Rothwell, Sarah H; Ehrenfeld, Jesse M

2012-11-01

Anesthesia information management systems (AIMS) have been developed by multiple vendors and are deployed in thousands of operating rooms around the world, yet not much is known about measuring and improving AIMS usability. We developed a methodology for evaluating AIMS usability in a low-fidelity simulated clinical environment and used it to compare an existing user interface with a revised version. We hypothesized that the revised user interface would be more useable. In a low-fidelity simulated clinical environment, twenty anesthesia providers documented essential anesthetic information for the start of the case using both an existing and a revised user interface. Participants had not used the revised user interface previously and completed a brief training exercise prior to the study task. All participants completed a workload assessment and a satisfaction survey. All sessions were recorded. Multiple usability metrics were measured. The primary outcome was documentation accuracy. Secondary outcomes were perceived workload, number of documentation steps, number of user interactions, and documentation time. The interfaces were compared and design problems were identified by analyzing recorded sessions and survey results. Use of the revised user interface was shown to improve documentation accuracy from 85.1% to 92.4%, a difference of 7.3% (95% confidence interval [CI] for the difference 1.8 to 12.7). The revised user interface decreased the number of user interactions by 6.5 for intravenous documentation (95% CI 2.9 to 10.1) and by 16.1 for airway documentation (95% CI 11.1 to 21.1). The revised user interface required 3.8 fewer documentation steps (95% CI 2.3 to 5.4). Airway documentation time was reduced by 30.5 seconds with the revised workflow (95% CI 8.5 to 52.4). There were no significant time differences noted in intravenous documentation or in total task time. No difference in perceived workload was found between the user interfaces. Two user interface design problems were identified in the revised user interface. The usability of anesthesia information management systems can be evaluated using a low-fidelity simulated clinical environment. User testing of the revised user interface showed improvement in some usability metrics and highlighted areas for further revision. Vendors of AIMS and those who use them should consider adopting methods to evaluate and improve AIMS usability.

Flight simulation for flight control computer S/N 0104-1 (ASTP)

NASA Technical Reports Server (NTRS)

1975-01-01

Flight control computer (FCC) 0104-I has been designated the prime unit for the SA-210 launch vehicle. The results of the final flight simulation for FCC S/N 0104-I are documented. These results verify satisfactory implementation of the design release and proper interfacing of the FCC with flight-type control sensor elements and simulated thrust vector control system.

Consolidated Cab Display (CCD) System, Project Planning Document (PPD),

DTIC Science & Technology

1981-02-01

1980 1981 I 2 3 4 5 6 7 8 9 10 1112 1 2 3 4 5 6 7 8 9 1011112 1 2 31 12. Software Documentation a. Overall Computer Program Description ( OCPD ) b...Approve OCPD c. Computer Program Functional Specifications (CPFS) d. Data Base Table Design Specification (DBTDS) e. Software Interface Control Document...Parts List Master Pattern and Plan View Reproducible Drawings Instruction Book Training Aids/Materials b. Software: OCPD CPFS SI CD PDS DBTDS SDD

A Graphical User-Interface for Propulsion System Analysis

NASA Technical Reports Server (NTRS)

Curlett, Brian P.; Ryall, Kathleen

1992-01-01

NASA LeRC uses a series of computer codes to calculate installed propulsion system performance and weight. The need to evaluate more advanced engine concepts with a greater degree of accuracy has resulted in an increase in complexity of this analysis system. Therefore, a graphical user interface was developed to allow the analyst to more quickly and easily apply these codes. The development of this interface and the rationale for the approach taken are described. The interface consists of a method of pictorially representing and editing the propulsion system configuration, forms for entering numerical data, on-line help and documentation, post processing of data, and a menu system to control execution.

A graphical user-interface for propulsion system analysis

NASA Technical Reports Server (NTRS)

Curlett, Brian P.; Ryall, Kathleen

1993-01-01

NASA LeRC uses a series of computer codes to calculate installed propulsion system performance and weight. The need to evaluate more advanced engine concepts with a greater degree of accuracy has resulted in an increase in complexity of this analysis system. Therefore, a graphical user interface was developed to allow the analyst to more quickly and easily apply these codes. The development of this interface and the rationale for the approach taken are described. The interface consists of a method of pictorially representing and editing the propulsion system configuration, forms for entering numerical data, on-line help and documentation, post processing of data, and a menu system to control execution.

XAL Application Framework and Bricks GUI Builder

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

Pelaia II, Tom

2007-01-01

The XAL [1] Application Framework is a framework for rapidly developing document based Java applications with a common look and feel along with many built-in user interface behaviors. The Bricks GUI builder consists of a modern application and framework for rapidly building user interfaces in support of true Model-View-Controller (MVC) compliant Java applications. Bricks and the XAL Application Framework allow developers to rapidly create quality applications.

Modeling Complex Cross-Systems Software Interfaces Using SysML

NASA Technical Reports Server (NTRS)

Mandutianu, Sanda; Morillo, Ron; Simpson, Kim; Liepack, Otfrid; Bonanne, Kevin

2013-01-01

The complex flight and ground systems for NASA human space exploration are designed, built, operated and managed as separate programs and projects. However, each system relies on one or more of the other systems in order to accomplish specific mission objectives, creating a complex, tightly coupled architecture. Thus, there is a fundamental need to understand how each system interacts with the other. To determine if a model-based system engineering approach could be utilized to assist with understanding the complex system interactions, the NASA Engineering and Safety Center (NESC) sponsored a task to develop an approach for performing cross-system behavior modeling. This paper presents the results of applying Model Based Systems Engineering (MBSE) principles using the System Modeling Language (SysML) to define cross-system behaviors and how they map to crosssystem software interfaces documented in system-level Interface Control Documents (ICDs).

Cargo Movement Operation Systems (CMOS) Interface Design Document (Preliminary)

DTIC Science & Technology

1990-04-29

between these versions, each must be individually numbered. CMOS PMO ACCEPTS COMMENT: YES [ ] NO [ ] ERCI ACCEPTS COMMENT: YES [ ] NO [ ] COMMENT DISPOSITION...ACCEPTS COMMENT: YES [ ] NO [ ] COMMENT DISPOSITION: COMMENT STATUS: OPEN [ ] CLOSED [ ] ORIGINATOR CONTROL NUMBER: IDDl-0004 PROGRAM OFFICE CONTROL NUMBER...COMMENT: YES [ ] NO [ ] ERCI ACCEPTS COMMENT: YES [ ] NO [ ] COMMENT DISPOSITION: COMMENT STATUS: OPEN [ ] CLOSED [ ] ORIGINATOR CONTROL NUMBER: IDDl-0006

Flight Experiment Demonstration System (FEDS) functional description and interface document

NASA Technical Reports Server (NTRS)

Belcher, R. C.; Shank, D. E.

1984-01-01

This document presents a functional description of the Flight Experiment Demonstration System (FEDS) and of interfaces between FEDS and external hardware and software. FEDS is a modification of the Automated Orbit Determination System (AODS). FEDS has been developed to support a ground demonstration of microprocessor-based onboard orbit determination. This document provides an overview of the structure and logic of FEDS and details the various operational procedures to build and execute FEDS. It also documents a microprocessor interface between FEDS and a TDRSS user transponder and describes a software simulator of the interface used in the development and system testing of FEDS.

Inexpensive DAQ based physics labs

NASA Astrophysics Data System (ADS)

Lewis, Benjamin; Clark, Shane

2015-11-01

Quality Data Acquisition (DAQ) based physics labs can be designed using microcontrollers and very low cost sensors with minimal lab equipment. A prototype device with several sensors and documentation for a number of DAQ-based labs is showcased. The device connects to a computer through Bluetooth and uses a simple interface to control the DAQ and display real time graphs, storing the data in .txt and .xls formats. A full device including a larger number of sensors combined with software interface and detailed documentation would provide a high quality physics lab education for minimal cost, for instance in high schools lacking lab equipment or students taking online classes. An entire semester’s lab course could be conducted using a single device with a manufacturing cost of under $20.

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.

Automated documentation generator for advanced protein crystal growth

NASA Technical Reports Server (NTRS)

Maddux, Gary A.; Provancha, Anna; Chattam, David; Ford, Ronald

1993-01-01

The System Management and Production Laboratory at the Research Institute, the University of Alabama in Huntsville (UAH), was tasked by the Microgravity Experiment Projects (MEP) Office of the Payload Projects Office (PPO) at Marshall Space Flight Center (MSFC) to conduct research in the current methods of written documentation control and retrieval. The goals of this research were to determine the logical interrelationships within selected NASA documentation, and to expand on a previously developed prototype system to deliver a distributable, electronic knowledge-based system. This computer application would then be used to provide a paperless interface between the appropriate parties for the required NASA document.

Automating testbed documentation and database access using World Wide Web (WWW) tools

NASA Technical Reports Server (NTRS)

Ames, Charles; Auernheimer, Brent; Lee, Young H.

1994-01-01

A method for providing uniform transparent access to disparate distributed information systems was demonstrated. A prototype testing interface was developed to access documentation and information using publicly available hypermedia tools. The prototype gives testers a uniform, platform-independent user interface to on-line documentation, user manuals, and mission-specific test and operations data. Mosaic was the common user interface, and HTML (Hypertext Markup Language) provided hypertext capability.

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).

Prototype Interoperability Document between NASA-JSC and DLR-GSOC Describing the CCSDS SM and C Mission Operations Prototype

NASA Technical Reports Server (NTRS)

Lucord, Steve A.; Gully, Sylvain

2009-01-01

The purpose of the PROTOTYPE INTEROPERABILITY DOCUMENT is to document the design and interfaces for the service providers and consumers of a Mission Operations prototype between JSC-OTF and DLR-GSOC. The primary goal is to test the interoperability sections of the CCSDS Spacecraft Monitor & Control (SM&C) Mission Operations (MO) specifications between both control centers. An additional goal is to provide feedback to the Spacecraft Monitor and Control (SM&C) working group through the Review Item Disposition (RID) process. This Prototype is considered a proof of concept and should increase the knowledge base of the CCSDS SM&C Mission Operations standards. No operational capabilities will be provided. The CCSDS Mission Operations (MO) initiative was previously called Spacecraft Monitor and Control (SM&C). The specifications have been renamed to better reflect the scope and overall objectives. The working group retains the name Spacecraft Monitor and Control working group and is under the Mission Operations and Information Services Area (MOIMS) of CCSDS. This document will refer to the specifications as SM&C Mission Operations, Mission Operations or just MO.

HALO--a Java framework for precise transcript half-life determination.

PubMed

Friedel, Caroline C; Kaufmann, Stefanie; Dölken, Lars; Zimmer, Ralf

2010-05-01

Recent improvements in experimental technologies now allow measurements of de novo transcription and/or RNA decay at whole transcriptome level and determination of precise transcript half-lives. Such transcript half-lives provide important insights into the regulation of biological processes and the relative contributions of RNA decay and de novo transcription to differential gene expression. In this article, we present HALO (Half-life Organizer), the first software for the precise determination of transcript half-lives from measurements of RNA de novo transcription or decay determined with microarrays or RNA-seq. In addition, methods for quality control, filtering and normalization are supplied. HALO provides a graphical user interface, command-line tools and a well-documented Java application programming interface (API). Thus, it can be used both by biologists to determine transcript half-lives fast and reliably with the provided user interfaces as well as software developers integrating transcript half-life analysis into other gene expression profiling pipelines. Source code, executables and documentation are available at http://www.bio.ifi.lmu.de/software/halo.

ARX - A Comprehensive Tool for Anonymizing Biomedical Data

PubMed Central

Prasser, Fabian; Kohlmayer, Florian; Lautenschläger, Ronald; Kuhn, Klaus A.

2014-01-01

Collaboration and data sharing have become core elements of biomedical research. Especially when sensitive data from distributed sources are linked, privacy threats have to be considered. Statistical disclosure control allows the protection of sensitive data by introducing fuzziness. Reduction of data quality, however, needs to be balanced against gains in protection. Therefore, tools are needed which provide a good overview of the anonymization process to those responsible for data sharing. These tools require graphical interfaces and the use of intuitive and replicable methods. In addition, extensive testing, documentation and openness to reviews by the community are important. Existing publicly available software is limited in functionality, and often active support is lacking. We present ARX, an anonymization tool that i) implements a wide variety of privacy methods in a highly efficient manner, ii) provides an intuitive cross-platform graphical interface, iii) offers a programming interface for integration into other software systems, and iv) is well documented and actively supported. PMID:25954407

A catalog of graphic symbols used at maintenance control centers : toward a symbol standardization process.

DOT National Transportation Integrated Search

2002-04-01

This document catalogs the symbols presented with the various interfaces used by Federal Aviation Administration Airway Facilities specialists. It includes a high-level overview of each system and the symbols and coding conventions used. These data w...

Land Use Control: Interface of Law and Geography. Resource Paper No. 75-1.

ERIC Educational Resources Information Center

Platt, Rutherford H.

The document suggests that problems of land use control can often be solved by applying geographic skills in analyzing the physical, economic, and cultural attributes of land. The paper is intended predominately for use by citizens' groups as they study the legal and judicial components of land management legislation. It can also be used as…

300 Area treated effluent disposal facility sampling schedule

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

Loll, C.M.

1994-10-11

This document is the interface between the 300 Area Liquid Effluent Process Engineering (LEPE) group and the Waste Sampling and Characterization Facility (WSCF), concerning process control samples. It contains a schedule for process control samples at the 300 Area TEDF which describes the parameters to be measured, the frequency of sampling and analysis, the sampling point, and the purpose for each parameter.

An adaptable product for material processing and life science missions

NASA Technical Reports Server (NTRS)

Wassick, Gregory; Dobbs, Michael

1995-01-01

The Experiment Control System II (ECS-II) is designed to make available to the microgravity research community the same tools and mode of automated experimentation that their ground-based counterparts have enjoyed for the last two decades. The design goal was accomplished by combining commercial automation tools familiar to the experimenter community with system control components that interface with the on-orbit platform in a distributed architecture. The architecture insulates the tools necessary for managing a payload. By using commercial software and hardware components whenever possible, development costs were greatly reduced when compared to traditional space development projects. Using commercial-off-the-shelf (COTS) components also improved the usability documentation, and reducing the need for training of the system by providing familiar user interfaces, providing a wealth of readily available documentation, and reducing the need for training on system-specific details. The modularity of the distributed architecture makes it very amenable for modification to different on-orbit experiments requiring robotics-based automation.

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).

[Development of an ophthalmological clinical information system for inpatient eye clinics].

PubMed

Kortüm, K U; Müller, M; Babenko, A; Kampik, A; Kreutzer, T C

2015-12-01

In times of increased digitalization in healthcare, departments of ophthalmology are faced with the challenge of introducing electronic clinical health records (EHR); however, specialized software for ophthalmology is not available with most major EHR sytems. The aim of this project was to create specific ophthalmological user interfaces for large inpatient eye care providers within a hospitalwide EHR. Additionally the integration of ophthalmic imaging systems, scheduling and surgical documentation should be achieved. The existing EHR i.s.h.med (Siemens, Germany) was modified using advanced business application programming (ABAP) language to create specific ophthalmological user interfaces for reproduction and moreover optimization of the clinical workflow. A user interface for documentation of ambulatory patients with eight tabs was designed. From June 2013 to October 2014 a total of 61,551 patient contact details were documented. For surgical documentation a separate user interface was set up. Digital clinical orders for documentation of registration and scheduling of operations user interfaces were also set up. A direct integration of ophthalmic imaging modalities could be established. An ophthalmologist-orientated EHR for outpatient and surgical documentation for inpatient clinics was created and successfully implemented. By incorporation of imaging procedures the foundation of future smart/big data analyses was created.

Kuipers during photo documentation of the fluid and electrical interfaces on the UIA

NASA Image and Video Library

2012-01-27

ISS030-E-156468 (27 Jan. 2012) --- European Space Agency astronaut Andre Kuipers, Expedition 30 flight engineer, is pictured in the Quest airlock of the International Space Station during photo documentation of the fluid and electrical interfaces on the Umbilical Interface Assembly (UIA) Connector Shelf.

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

NASA Technical Reports Server (NTRS)

2005-01-01

This document involves definition of technology interface requirements for Contingency Management. This was performed through a review of Contingency Management-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Contingency Management Work Package were considered. Beginning with HSI high-level functional requirements for Contingency Management, and Contingency Management 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 system failures and associated contingency procedures, and (2) the control capability needed by the pilot to obtain system status and procedure information. Fundamentally, these requirements provide the candidate Contingency Management technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Contingency Management operations and functions should interface with the pilot to provide the necessary Contingency Management functionality to the UA-pilot system. Requirements and guidelines for Contingency Management are partitioned into four categories: (1) Health and Status and (2) Contingency Management. Each requirement is stated and is supported with a rationale and associated reference(s).

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).

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

300 Area treated effluent disposal facility sampling schedule. Revision 1

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

Loll, C.M.

1995-03-28

This document is the interface between the 300 Area liquid effluent process engineering (LEPE) group and the waste sampling and characterization facility (WSCF), concerning process control samples. It contains a schedule for process control samples at the 300 Area TEDF which describes the parameters to be measured, the frequency of sampling and analysis, the sampling point, and the purpose for each parameter.

Proximity Displays for Access Control

ERIC Educational Resources Information Center

Vaniea, Kami

2012-01-01

Managing access to shared digital information, such as photographs and documents. is difficult for end users who are accumulating an increasingly large and diverse collection of data that they want to share with others. Current policy-management solutions require a user to proactively seek out and open a separate policy-management interface when…

Launch Control Network Engineer

NASA Technical Reports Server (NTRS)

Medeiros, Samantha

2017-01-01

The Spaceport Command and Control System (SCCS) is being built at the Kennedy Space Center in order to successfully launch NASA’s revolutionary vehicle that allows humans to explore further into space than ever before. During my internship, I worked with the Network, Firewall, and Hardware teams that are all contributing to the huge SCCS network project effort. I learned the SCCS network design and the several concepts that are running in the background. I also updated and designed documentation for physical networks that are part of SCCS. This includes being able to assist and build physical installations as well as configurations. I worked with the network design for vehicle telemetry interfaces to the Launch Control System (LCS); this allows the interface to interact with other systems at other NASA locations. This network design includes the Space Launch System (SLS), Interim Cryogenic Propulsion Stage (ICPS), and the Orion Multipurpose Crew Vehicle (MPCV). I worked on the network design and implementation in the Customer Avionics Interface Development and Analysis (CAIDA) lab.

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.

Final Report: MaRSPlus Sensor System Electrical Cable Management and Distributed Motor Control Computer Interface

NASA Technical Reports Server (NTRS)

Reil, Robin

2011-01-01

The success of JPL's Next Generation Imaging Spectrometer (NGIS) in Earth remote sensing has inspired a follow-on instrument project, the MaRSPlus Sensor System (MSS). One of JPL's responsibilities in the MSS project involves updating the documentation from the previous JPL airborne imagers to provide all the information necessary for an outside customer to operate the instrument independently. As part of this documentation update, I created detailed electrical cabling diagrams to provide JPL technicians with clear and concise build instructions and a database to track the status of cables from order to build to delivery. Simultaneously, a distributed motor control system is being developed for potential use on the proposed 2018 Mars rover mission. This system would significantly reduce the mass necessary for rover motor control, making more mass space available to other important spacecraft systems. The current stage of the project consists of a desktop computer talking to a single "cold box" unit containing the electronics to drive a motor. In order to test the electronics, I developed a graphical user interface (GUI) using MATLAB to allow a user to send simple commands to the cold box and display the responses received in a user-friendly format.

Role and interest of new technologies in data processing for space control centers

NASA Astrophysics Data System (ADS)

Denier, Jean-Paul; Caspar, Raoul; Borillo, Mario; Soubie, Jean-Luc

1990-10-01

The ways in which a multidisplinary approach will improve space control centers is discussed. Electronic documentation, ergonomics of human computer interfaces, natural language, intelligent tutoring systems and artificial intelligence systems are considered and applied in the study of the Hermes flight control center. It is concluded that such technologies are best integrated into a classical operational environment rather than taking a revolutionary approach which would involve a global modification of the system.

Content Documents Management

NASA Technical Reports Server (NTRS)

Muniz, R.; Hochstadt, J.; Boelke J.; Dalton, A.

2011-01-01

The Content Documents are created and managed under the System Software group with. Launch Control System (LCS) project. The System Software product group is lead by NASA Engineering Control and Data Systems branch (NEC3) at Kennedy Space Center. The team is working on creating Operating System Images (OSI) for different platforms (i.e. AIX, Linux, Solaris and Windows). Before the OSI can be created, the team must create a Content Document which provides the information of a workstation or server, with the list of all the software that is to be installed on it and also the set where the hardware belongs. This can be for example in the LDS, the ADS or the FR-l. The objective of this project is to create a User Interface Web application that can manage the information of the Content Documents, with all the correct validations and filters for administrator purposes. For this project we used one of the most excellent tools in agile development applications called Ruby on Rails. This tool helps pragmatic programmers develop Web applications with Rails framework and Ruby programming language. It is very amazing to see how a student can learn about OOP features with the Ruby language, manage the user interface with HTML and CSS, create associations and queries with gems, manage databases and run a server with MYSQL, run shell commands with command prompt and create Web frameworks with Rails. All of this in a real world project and in just fifteen weeks!

NASA Docking System (NDS) Interface Definitions Document (IDD). Revision C, Nov. 2010

NASA Technical Reports Server (NTRS)

2010-01-01

The NASA Docking System (NDS) mating system supports low approach velocity docking and provides a modular and reconfigurable standard interface, supporting crewed and autonomous vehicles during mating and assembly operations. The NDS is NASA's implementation for the emerging International Docking System Standard (IDSS) using low impact docking technology. All NDS configurations can mate with the configuration specified in the IDSS Interface Definition Document (IDD) released September 21, 2010. The NDS evolved from the Low Impact Docking System (LIDS). The acronym international Low Impact Docking System (iLIDS) is also used to describe this system. NDS and iLIDS may be used interchangeability. Some of the heritage documentation and implementations (e.g., software command names) used on NDS will continue to use the LIDS acronym. The NDS IDD defines the interface characteristics and performance capability of the NDS, including uses ranging from crewed to autonomous space vehicles and from low earth orbit to deep space exploration. The responsibility for developing space vehicles and for making them technically and operationally compatible with the NDS rests with the vehicle providers. Host vehicle examples include crewed/uncrewed spacecraft, space station modules, elements, etc. Within this document, any docking space vehicle will be referred to as the host vehicle. This document defines the NDS-to-NDS interfaces, as well as the NDS-to-host vehicle interfaces and performance capability.

National Airspace System interface management plan

DOT National Transportation Integrated Search

1986-01-01

This document is intended to implement Interface Management for interfacing subsystems of the National Airspace System (NAS) and for external NAS interfaces by establishing a process which assures that: Interface requirements are agreed to by interfa...

Visual design for the user interface, Part 1: Design fundamentals.

PubMed

Lynch, P J

1994-01-01

Digital audiovisual media and computer-based documents will be the dominant forms of professional communication in both clinical medicine and the biomedical sciences. The design of highly interactive multimedia systems will shortly become a major activity for biocommunications professionals. The problems of human-computer interface design are intimately linked with graphic design for multimedia presentations and on-line document systems. This article outlines the history of graphic interface design and the theories that have influenced the development of today's major graphic user interfaces.

Interface Control Document for the Traffic Lights and Emergency Communications System at Gretna and Governor Nicholls Traffic Light Facilities

DOT National Transportation Integrated Search

1997-11-06

Gretna and Governor Nicholls Light facilities are two manned shore side : facilities mounted in critical areas on the banks of the Mississippi River in : the port of New Orleans, Louisiana. Coast Guard plans call for the lights to : be remotely contr...

Preliminary design of a solar central receiver for a site-specific repowering application (Saguaro Power Plant). Volume III. Specifications. Final report, October 1982-September 1983

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

Weber, E.R.

1983-09-01

This volume on specifications for the Saguaro Power Plant includes the following: subsystem interface definition document; solar collector subsystem specification; receiver specification; thermal energy storage specification; solar steam generator specification; and master control system specification.

U.S. Army weapon systems human-computer interface style guide. Version 2

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

Avery, L.W.; O`Mara, P.A.; Shepard, A.P.

1997-12-31

A stated goal of the US Army has been the standardization of the human computer interfaces (HCIs) of its system. Some of the tools being used to accomplish this standardization are HCI design guidelines and style guides. Currently, the Army is employing a number of HCI design guidance documents. While these style guides provide good guidance for the command, control, communications, computers, and intelligence (C4I) domain, they do not necessarily represent the more unique requirements of the Army`s real time and near-real time (RT/NRT) weapon systems. The Office of the Director of Information for Command, Control, Communications, and Computers (DISC4),more » in conjunction with the Weapon Systems Technical Architecture Working Group (WSTAWG), recognized this need as part of their activities to revise the Army Technical Architecture (ATA), now termed the Joint Technical Architecture-Army (JTA-A). To address this need, DISC4 tasked the Pacific Northwest National Laboratory (PNNL) to develop an Army weapon systems unique HCI style guide, which resulted in the US Army Weapon Systems Human-Computer Interface (WSHCI) Style Guide Version 1. Based on feedback from the user community, DISC4 further tasked PNNL to revise Version 1 and publish Version 2. The intent was to update some of the research and incorporate some enhancements. This document provides that revision. The purpose of this document is to provide HCI design guidance for the RT/NRT Army system domain across the weapon systems subdomains of ground, aviation, missile, and soldier systems. Each subdomain should customize and extend this guidance by developing their domain-specific style guides, which will be used to guide the development of future systems within their subdomains.« less

ADST Software Design Document for the BDS-D VIDS-equipped M1

DTIC Science & Technology

1993-09-10

system responds to perceived threats in the following ways:I a. by displaying visual icons on the Commander’s Controls Display Panel (CCDP). b. by...also referred to as the Soldier Machine Interface (SMI) and the Commander’s Controls Display Panel (CCDP). 3.2.1. VIDS-GT CSC The VIDS-GT CSC handles...countermeasure will be activated first in Individual_CM_Simul. 4.1.3.4.3. IndividualCMSimul CSU IndividualCM-Simul controls the activation and deactivation of

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.

Curating NASA's Extraterrestrial Samples - Past, Present, and Future

NASA Technical Reports Server (NTRS)

Allen, Carlton; Allton, Judith; Lofgren, Gary; Righter, Kevin; Zolensky, Michael

2011-01-01

Curation of extraterrestrial samples is the critical interface between sample return missions and the international research community. The Astromaterials Acquisition and Curation Office at the NASA Johnson Space Center (JSC) is responsible for curating NASA s extraterrestrial samples. Under the governing document, NASA Policy Directive (NPD) 7100.10E "Curation of Extraterrestrial Materials", JSC is charged with ". . . curation of all extraterrestrial material under NASA control, including future NASA missions." The Directive goes on to define Curation as including "documentation, preservation, preparation, and distribution of samples for research, education, and public outreach."

Curating NASA's Extraterrestrial Samples - Past, Present, and Future

NASA Technical Reports Server (NTRS)

Allen, Carlton; Allton, Judith; Lofgren, Gary; Righter, Kevin; Zolensky, Michael

2010-01-01

Curation of extraterrestrial samples is the critical interface between sample return missions and the international research community. The Astromaterials Acquisition and Curation Office at the NASA Johnson Space Center (JSC) is responsible for curating NASA's extraterrestrial samples. Under the governing document, NASA Policy Directive (NPD) 7100.10E "Curation of Extraterrestrial Materials," JSC is charged with ". . . curation of all extraterrestrial material under NASA control, including future NASA missions." The Directive goes on to define Curation as including documentation, preservation, preparation, and distribution of samples for research, education, and public outreach.

Assessment Report Sandia National Laboratories Fuel Cycle Technologies Quality Assurance Evaluation of FY15 SNL FCT M2 Milestone Deliverables

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

Appel, Gordon John

Sandia National Laboratories (SNL) Fuel Cycle Technologies (FCT) program activities are conducted in accordance with FCT Quality Assurance Program Document (FCT-QAPD) requirements. The FCT-QAPD interfaces with SNL approved Quality Assurance Program Description (SNL-QAPD) as explained in the Sandia National Laboratories QA Program Interface Document for FCT Activities (Interface Document). This plan describes SNL's FY16 assessment of SNL's FY15 FCT M2 milestone deliverable's compliance with program QA requirements, including SNL R&A requirements. The assessment is intended to confirm that SNL's FY15 milestone deliverables contain the appropriate authenticated review documentation and that there is a copy marked with SNL R&A numbers.

The evolution of the ISOLDE control system

NASA Astrophysics Data System (ADS)

Jonsson, O. C.; Catherall, R.; Deloose, I.; Drumm, P.; Evensen, A. H. M.; Gase, K.; Focker, G. J.; Fowler, A.; Kugler, E.; Lettry, J.; Olesen, G.; Ravn, H. L.; Isolde Collaboration

The ISOLDE on-line mass separator facility is operating on a Personal Computer based control system since spring 1992. Front End Computers accessing the hardware are controlled from consoles running Microsoft Windows ™ through a Novell NetWare4 ™ local area network. The control system is transparently integrated in the CERN wide office network and makes heavy use of the CERN standard office application programs to control and to document the running of the ISOLDE isotope separators. This paper recalls the architecture of the control system, shows its recent developments and gives some examples of its graphical user interface.

The evolution of the ISOLDE control system

NASA Astrophysics Data System (ADS)

Jonsson, O. C.; Catherall, R.; Deloose, I.; Evensen, A. H. M.; Gase, K.; Focker, G. J.; Fowler, A.; Kugler, E.; Lettry, J.; Olesen, G.; Ravn, H. L.; Drumm, P.

1996-04-01

The ISOLDE on-line mass separator facility is operating on a Personal Computer based control system since spring 1992. Front End Computers accessing the hardware are controlled from consoles running Microsoft Windows® through a Novell NetWare4® local area network. The control system is transparently integrated in the CERN wide office network and makes heavy use of the CERN standard office application programs to control and to document the running of the ISOLDE isotope separators. This paper recalls the architecture of the control system, shows its recent developments and gives some examples of its graphical user interface.

HELIOS Third Joint Working Group Meeting

NASA Technical Reports Server (NTRS)

Ousley, Gilbert; Kutzer, Ants

1970-01-01

During the past six months since the Second Helios Joint Working Group Meeting held 27-30 April 1970 at Goddard Space Flight Center, the TDS Sub-Group supported the Helios Project Office and the other Sub-Groups in the timely disposition of action items and the dissemination of information pertinent to the development of interface documentation. Of particular importance during this time period was the Project's decision to incorporate a single-channel telemetry system design aboard the spacecraft. The TDS Sub-Group participated actively in the process that led to this decision. Still under active study with TDS participation is the pending Project Office decision regarding the incorporation of a ranging capability within the telecommunications design. The TDS Sub-Group assisted the Mission Analysis and Operations Sub-Group in establishment of a study effort concerning the Near-Earth Sequence of Events from launch to launch plus 8 hours. This study, which will provide valuable data for the spacecraft telecommunications design, will include participation by the Experiment, Launch Vehicle, Spacecraft, as well as the TDS and MA&O Sub-Groups. Also during the past 6-month period, the TDS, in conjunction with the Spacecraft Sub-Group, initiated activity to develop the Helios Spacecraft/TDS Compatibility Test Plans and Procedures. Activity concerning the foregoing interface discussions has been and will continue to be based upon the "TDS Estimated Capabilities Document for the Helios Missions" (613-1), and the "DSN/Flight Project Interface Design Handbook" (810-5). These will continue to be considered TDS controlling documents until specific Helios Project/TDS interface documentation is generated and signed off by the respective parties. In addition to the above, the DSN continued the Helios Trainee Program with seven GfW/DFVLR trainees in residence at JPL. Two trainees will complete their year's residency concurrent with the Third Helios Joint Working Group Meeting, while four new trainees are expected to arrive following the Third Helios Joint Working Group Meeting. These and other activities are reported in detail in the paragraphs that follow.

Interface control document between the NASA Goddard Space Flight Center (GSFC) and Department of Interior EROS Data Center (EDC) for LANDSAT-D. Partially processed multispectral scanner High Density Tape (HDT-AM)

NASA Technical Reports Server (NTRS)

1982-01-01

The format of the HDT-AM product which contains partially processed LANDSAT D and D Prime multispectral scanner image data is defined. Recorded-data formats, tape format, and major frame types are described.

Interface control document between the NASA Goddard Space Flight Center (GSFC) and Department of Interior EROS Data Center (EDC) for LANDSAT-D. Thematic mapper high resolution 241 mm film

NASA Technical Reports Server (NTRS)

1982-01-01

The 241 mm photographic product produced by the Goddard Space Flight Center Data Management System for LANDSAT-D is described. Film type and format, image dimensions, frame ID, gray scale, resolution patterns, registration marks, etc. are addressed.

Pip pin reliability and design

NASA Technical Reports Server (NTRS)

Skyles, Lane P.

1994-01-01

Pip pins are used in many engineering applications. Of particular interest to the aerospace industry is their use in various mechanism designs. Many payloads that fly aboard our nation's Space Shuttle have at least one actuated mechanism. Often these mechanisms incorporate pip pins in their design in order to fasten interfacing parts or joints. Pip pins are most often used when an astronaut will have a direct interface with the mechanism. This interfacing can be done during Space Shuttle mission EVA's (ExtraVehicular Activity). The main reason for incorporating pip pins is convenience and their ability to provide a quick release for interfacing parts. However, there are some issues that must be taken into account when using them in a design. These issues include documented failures and quality control problems when using substandard pip pins. A history of pip pins as they relate to the aerospace industry as well as general design features is discussed.

Putting Home Data Management into Perspective

DTIC Science & Technology

2009-12-01

approaches. However, users of home and personal storage live it. Popular interfaces (e.g., iTunes , iPhoto, and even drop-down lists of recently...users of home and personal storage live it. Popular interfaces (e.g., iTunes , iPhoto, and even drop-down lists of recently-opened Word documents...live it. Popular interfaces (e.g., iTunes , iPhoto, and even drop- down lists of recently-opened Word documents) allow users to navigate file

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...

Systems engineering interfaces: A model based approach

NASA Astrophysics Data System (ADS)

Fosse, E.; Delp, C. L.

The engineering of interfaces is a critical function of the discipline of Systems Engineering. Included in interface engineering are instances of interaction. Interfaces provide the specifications of the relevant properties of a system or component that can be connected to other systems or components while instances of interaction are identified in order to specify the actual integration to other systems or components. Current Systems Engineering practices rely on a variety of documents and diagrams to describe interface specifications and instances of interaction. The SysML[1] specification provides a precise model based representation for interfaces and interface instance integration. This paper will describe interface engineering as implemented by the Operations Revitalization Task using SysML, starting with a generic case and culminating with a focus on a Flight System to Ground Interaction. The reusability of the interface engineering approach presented as well as its extensibility to more complex interfaces and interactions will be shown. Model-derived tables will support the case studies shown and are examples of model-based documentation products.

Standard Engineering Installation Package, Technical Control Facility, Technical Control Improvement Program (TCIP)

DTIC Science & Technology

1979-10-01

software. This document may not be cited for purpose of advertisement . AVAILABILITY This publication is available to non-Government agencies and may be...voltage interface requirements for repeaters. This supply occupies one slot in the 10306 mounting shelf. 1.4.2.8.5 Teletypewriter monitor. The AN/ UGC -61X...The AN/ UGC -61X keyboard send-receive (KSR) TTY set is an electromechanical apparatus that provides terminal facilities with two receive only, one KSR

Overview of ICE Project: Integration of Computational Fluid Dynamics and Experiments

NASA Technical Reports Server (NTRS)

Stegeman, James D.; Blech, Richard A.; Babrauckas, Theresa L.; Jones, William H.

2001-01-01

Researchers at the NASA Glenn Research Center have developed a prototype integrated environment for interactively exploring, analyzing, and validating information from computational fluid dynamics (CFD) computations and experiments. The Integrated CFD and Experiments (ICE) project is a first attempt at providing a researcher with a common user interface for control, manipulation, analysis, and data storage for both experiments and simulation. ICE can be used as a live, on-tine system that displays and archives data as they are gathered; as a postprocessing system for dataset manipulation and analysis; and as a control interface or "steering mechanism" for simulation codes while visualizing the results. Although the full capabilities of ICE have not been completely demonstrated, this report documents the current system. Various applications of ICE are discussed: a low-speed compressor, a supersonic inlet, real-time data visualization, and a parallel-processing simulation code interface. A detailed data model for the compressor application is included in the appendix.

Phase 111A Crew Interface Specifications Development for Inflight Maintenance and Stowage Functions

NASA Technical Reports Server (NTRS)

Carl, John G.

1973-01-01

This report presents the findings and data products developed during the Phase IIIA Crew Interface Specification Study for Inflight Maintenance and Stowage Functions, performed by General Electric for the NASA, Johnson Space Center with a set of documentation that can be used as definitive guidelines to improve the present process of defining, controlling and managing flight crew interface requirements that are related to inflight maintenance (including assembly and servicing) and stowage functions. During the Phase IIIA contract period, the following data products were developed: 1) Projected NASA Crew Procedures/Flight Data File Development Process. 2) Inflight Maintenance Management Process Description. 3) Preliminary Draft, General Specification, Inflight Maintenance Management Requirements. 4) Inflight Maintenance Operational Process Description. 5) Preliminary Draft, General Specification, Inflight Maintenance Task and Support Requirements Analysis. 6) Suggested IFM Data Processing Reports for Logistics Management The above Inflight Maintenance data products have been developed during the Phase IIIA study after review of Space Shuttle Program Documentation, including the Level II Integrated Logistics Requirements and other DOD and NASA data relative to Payloads Accommodations and Satellite On-Orbit Servicing. These Inflight Maintenance data products were developed to be in consonance with Space Shuttle Program technical and management requirements.

A Report of Bethune-Cookman College NASA JOVE Projects

NASA Technical Reports Server (NTRS)

Agba, Lawrence C.; David, Sunil K.; Rao, Narsing G.; Rahmani, Munir A.

1997-01-01

This document is the final report for the Joint Venture (JOVE) in Space Sciences, and describes the tasks, performed with the support of the contract. These tasks include work in: (1) interfacing microprocessor systems to high performance parallel interface chips, SCSI drive and memory, needed for the implementation of a Space Optical Data Recorder; (2) designing a digital interface architecture for a microprocessor controlled sensors monitoring unit for a NASA Jitter Attenuation and Dynamics Experiment (JADE) project; (3) developing an enhanced back-propagation training algorithm; (4) studying the effect of simulated spaceflight on Aortic Contractility; (5) developing a course in astronomy; and (6) improving internet access by running cables, and installing hubs in various places on the campus; and (7) researching the characteristics of Nd:YALO laser resonator.

Design Document for the Moods Data Management System (MDMS) Version 1.0

DTIC Science & Technology

1994-08-01

1 1.3 Document Overview ... . . . . . . . . . . . . . . . . . . . . 1 2 RERENCED DOCUMENTS .................... 2 3 PRELIM[INARY DESIGN... 3 3.1.1.1 CSC-: Grpical User Interfce(GUI).......... 3 3.1.112 CSC-2: Data Management Module (DMM) .................. 4 3.1.1.3 CSC- 3 : Data...5 3.1.1.6 GUI-DMM (CSC-1ICSC-2) internal interface................5 3.1.1.7 GUI-DAM (CSC-1/CSC- 3 ) Internal Interface................5

NASA-STD-(I)-6016, Standard Materials and Processes Requirements for Spacecraft

NASA Technical Reports Server (NTRS)

Pedley, Michael; Griffin, Dennis

2006-01-01

This document is directed toward Materials and Processes (M&P) used in the design, fabrication, and testing of flight components for all NASA manned, unmanned, robotic, launch vehicle, lander, in-space and surface systems, and spacecraft program/project hardware elements. All flight hardware is covered by the M&P requirements of this document, including vendor designed, off-the-shelf, and vendor furnished items. Materials and processes used in interfacing ground support equipment (GSE); test equipment; hardware processing equipment; hardware packaging; and hardware shipment shall be controlled to prevent damage to or contamination of flight hardware.

CHeCS: International Space Station Medical Hardware Catalog

NASA Technical Reports Server (NTRS)

2008-01-01

The purpose of this catalog is to provide a detailed description of each piece of hardware in the Crew Health Care System (CHeCS), including subpacks associated with the hardware, and to briefly describe the interfaces between the hardware and the ISS. The primary user of this document is the Space Medicine/Medical Operations ISS Biomedical Flight Controllers (ISS BMEs).

US Army Weapon Systems Human-Computer Interface (WSHCI) style guide, Version 1

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

Avery, L.W.; O`Mara, P.A.; Shepard, A.P.

1996-09-30

A stated goal of the U.S. Army has been the standardization of the human computer interfaces (HCIS) of its system. Some of the tools being used to accomplish this standardization are HCI design guidelines and style guides. Currently, the Army is employing a number of style guides. While these style guides provide good guidance for the command, control, communications, computers, and intelligence (C4I) domain, they do not necessarily represent the more unique requirements of the Army`s real time and near-real time (RT/NRT) weapon systems. The Office of the Director of Information for Command, Control, Communications, and Computers (DISC4), in conjunctionmore » with the Weapon Systems Technical Architecture Working Group (WSTAWG), recognized this need as part of their activities to revise the Army Technical Architecture (ATA). To address this need, DISC4 tasked the Pacific Northwest National Laboratory (PNNL) to develop an Army weapon systems unique HCI style guide. This document, the U.S. Army Weapon Systems Human-Computer Interface (WSHCI) Style Guide, represents the first version of that style guide. The purpose of this document is to provide HCI design guidance for RT/NRT Army systems across the weapon systems domains of ground, aviation, missile, and soldier systems. Each domain should customize and extend this guidance by developing their domain-specific style guides, which will be used to guide the development of future systems within their domains.« less

Human factors aspects of control room design

NASA Technical Reports Server (NTRS)

Jenkins, J. P.

1983-01-01

A plan for the design and analysis of a multistation control room is reviewed. It is found that acceptance of the computer based information system by the uses in the control room is mandatory for mission and system success. Criteria to improve computer/user interface include: match of system input/output with user; reliability, compatibility and maintainability; easy to learn and little training needed; self descriptive system; system under user control; transparent language, format and organization; corresponds to user expectations; adaptable to user experience level; fault tolerant; dialog capability user communications needs reflected in flexibility, complexity, power and information load; integrated system; and documentation.

Applying Minimal Manual Principles for Documentation of Graphical User Interfaces.

ERIC Educational Resources Information Center

Nowaczyk, Ronald H.; James, E. Christopher

1993-01-01

Investigates the need to include computer screens in documentation for software using a graphical user interface. Describes the uses and purposes of "minimal manuals" and their principles. Studies student reaction to their use of one of three on-screen manuals: screens, icon, and button. Finds some benefit for including icon and button…

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.

Dynamic Detection of Malicious Code in COTS Software

DTIC Science & Technology

2000-04-01

run the following documented hostile applets or ActiveX of these tools work only on mobile code (Java, ActiveX , controls: 16-11 Hostile Applets Tiny...Killer App Exploder Runner ActiveX Check Spy eSafe Protect Desktop 9/9 blocked NB B NB 13/17 blocked NB Surfinshield Online 9/9 blocked NB B B 13/17...Exploder is an ActiveX control top (@). that performs a clean shutdown of your computer. The interface is attractive, although rather complex, as McLain’s

Functions and requirements document for interim store solidified high-level and transuranic waste

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

Smith-Fewell, M.A., Westinghouse Hanford

1996-05-17

The functions, requirements, interfaces, and architectures contained within the Functions and Requirements (F{ampersand}R) Document are based on the information currently contained within the TWRS Functions and Requirements database. The database also documents the set of technically defensible functions and requirements associated with the solidified waste interim storage mission.The F{ampersand}R Document provides a snapshot in time of the technical baseline for the project. The F{ampersand}R document is the product of functional analysis, requirements allocation and architectural structure definition. The technical baseline described in this document is traceable to the TWRS function 4.2.4.1, Interim Store Solidified Waste, and its related requirements, architecture,more » and interfaces.« less

A Hyperbolic Ontology Visualization Tool for Model Application Programming Interface Documentation

NASA Technical Reports Server (NTRS)

Hyman, Cody

2011-01-01

Spacecraft modeling, a critically important portion in validating planned spacecraft activities, is currently carried out using a time consuming method of mission to mission model implementations and integration. A current project in early development, Integrated Spacecraft Analysis (ISCA), aims to remedy this hindrance by providing reusable architectures and reducing time spent integrating models with planning and sequencing tools. The principle objective of this internship was to develop a user interface for an experimental ontology-based structure visualization of navigation and attitude control system modeling software. To satisfy this, a number of tree and graph visualization tools were researched and a Java based hyperbolic graph viewer was selected for experimental adaptation. Early results show promise in the ability to organize and display large amounts of spacecraft model documentation efficiently and effectively through a web browser. This viewer serves as a conceptual implementation for future development but trials with both ISCA developers and end users should be performed to truly evaluate the effectiveness of continued development of such visualizations.

GMSEC Interface Specification Document 2016 March

NASA Technical Reports Server (NTRS)

Handy, Matthew

2016-01-01

The GMSEC Interface Specification Document contains the standard set of defined messages. Each GMSEC standard message contains a GMSEC Information Bus Header section and a Message Contents section. Each message section identifies required fields, optional fields, data type and recommended use of the fields. Additionally, this document includes the message subjects associated with the standard messages. The system design of the operations center should ensure the components that are selected use both the API and the defined standard messages in order to achieve full interoperability from component to component.

Rapid Equipping Force (REF) Analytical Support

DTIC Science & Technology

2007-06-01

document contains color images. 14. ABSTRACT 15. SUBJECT TERMS 16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT UU 18. NUMBER OF PAGES 44...interface and performs actions via Excel formulae, ActiveX controls, and VBA code. – Plan to provide both simple and complex weighting and scoring methods...Requirements Quad Chart. –Solution Set Information Worksheet: A spreadsheet containing detailed information concerning every potential solution considered

Voice/Natural Language Interfacing for Robotic Control.

DTIC Science & Technology

1987-11-01

THIS PAGE REPORT DOCUMENTATION PAGE Is. REPORT SECURITY CLASSIFICATION lb . RESTRICTIVE MARKINGS UNCLASSIFIED 2a. SECURITY CLASSIFICATION AUTHORITY 3...until major computing power can be profitably allocated to the speech recognition process, off-the- shelf units will never have sufficient intelligence to...coordinate transformation for a location, and opening or closing the gripper’s toggles. External to world operations, each joint may be rotated

Fine Scale Modeling and Forecasts of Upper Atmospheric Turbulence for Operational Use

DTIC Science & Technology

2014-11-30

Weather Center Digital Data Service (ADDS) fhttp://www.aviationweather.gov/adds, http://weather.aero/1 Graphical Turbulence Guidance product, GTG -2.5...analysis GTG - Graphical Turbulence Guidance HRMM - High Resolution Mesoscale/Microscale ICD - Interface Control Document IDE - Integrated Development...site (with GTG 2.5 data) http://www.aviationweather.gov/turbuience • ADDS Experimental site http://weather.aero/ • NCEP FNL data - http

Secure content objects

DOEpatents

Evans, William D [Cupertino, CA

2009-02-24

A secure content object protects electronic documents from unauthorized use. The secure content object includes an encrypted electronic document, a multi-key encryption table having at least one multi-key component, an encrypted header and a user interface device. The encrypted document is encrypted using a document encryption key associated with a multi-key encryption method. The encrypted header includes an encryption marker formed by a random number followed by a derivable variation of the same random number. The user interface device enables a user to input a user authorization. The user authorization is combined with each of the multi-key components in the multi-key encryption key table and used to try to decrypt the encrypted header. If the encryption marker is successfully decrypted, the electronic document may be decrypted. Multiple electronic documents or a document and annotations may be protected by the secure content object.

Graphical Interfaces for Simulation.

ERIC Educational Resources Information Center

Hollan, J. D.; And Others

This document presents a discussion of the development of a set of software tools to assist in the construction of interfaces to simulations and real-time systems. Presuppositions to the approach to interface design that was used are surveyed, the tools are described, and the conclusions drawn from these experiences in graphical interface design…

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

Closeout of CRADA JSA 2012S004: Chapter 5, Integrated Control System, of the document of the ESS Conceptual Design Report, publicly available at https://europeanspallationsource.se/accelerator-documents

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

Satogata, Todd

2013-04-22

The integrated control system (ICS) is responsible for the whole ESS machine and facility: accelerator, target, neutron scattering instruments and conventional facilities. This unified approach keeps the costs of development, maintenance and support relatively low. ESS has selected a standardised, field-proven controls framework, the Experimental Physics and Industrial Control System (EPICS), which was originally developed jointly by Argonne and Los Alamos National Laboratories. Complementing this selection are best practices and experience from similar facilities regarding platform standardisation, control system development and device integration and commissioning. The components of ICS include the control system core, the control boxes, the BLED databasemore » management system, and the human machine interface. The control system core is a set of systems and tools that make it possible for the control system to provide required data, information and services to engineers, operators, physicists and the facility itself. The core components are the timing system that makes possible clock synchronisation across the facility, the machine protection system (MPS) and the personnel protection system (PPS) that prevent damage to the machine and personnel, and a set of control system services. Control boxes are servers that control a collection of equipment (for example a radio frequency cavity). The integrated control system will include many control boxes that can be assigned to one supplier, such as an internal team, a collaborating institute or a commercial vendor. This approach facilitates a clear division of responsibilities and makes integration much easier. A control box is composed of a standardised hardware platform, components, development tools and services. On the top level, it interfaces with the core control system components (timing, MPS, PPS) and with the human-machine interface. At the bottom, it interfaces with the equipment and parts of the facility through a set of analog and digital signals, real-time control loops and other communication buses. The ICS central data management system is named BLED (beam line element databases). BLED is a set of databases, tools and services that is used to store, manage and access data. It holds vital control system configuration and physics-related (lattice) information about the accelerator, target and instruments. It facilitates control system configuration by bringing together direct input-output controller (IOC) con guration and real-time data from proton and neutron beam line models. BLED also simplifies development and speeds up the code-test-debug cycle. The set of tools that access BLED will be tailored to the needs of different categories of users, such as ESS staff physicists, engineers, and operators; external partner laboratories; and visiting experimental instrument users. The human-machine interface is vital to providing a high-quality experience to ICS users. It encompasses a wide array of devices and software tools, from control room screens to engineer terminal windows; from beam physics data tools to post-mortem data analysis tools. It serves users with a wide range of skills from widely varied backgrounds. The Controls Group is developing a set of user profiles to accommodate this diverse range of use-cases and users.« less

Documentation for MeshKit - Reactor Geometry (&mesh) Generator

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

Jain, Rajeev; Mahadevan, Vijay

2015-09-30

This report gives documentation for using MeshKit’s Reactor Geometry (and mesh) Generator (RGG) GUI and also briefly documents other algorithms and tools available in MeshKit. RGG is a program designed to aid in modeling and meshing of complex/large hexagonal and rectilinear reactor cores. RGG uses Argonne’s SIGMA interfaces, Qt and VTK to produce an intuitive user interface. By integrating a 3D view of the reactor with the meshing tools and combining them into one user interface, RGG streamlines the task of preparing a simulation mesh and enables real-time feedback that reduces accidental scripting mistakes that could waste hours of meshing.more » RGG interfaces with MeshKit tools to consolidate the meshing process, meaning that going from model to mesh is as easy as a button click. This report is designed to explain RGG v 2.0 interface and provide users with the knowledge and skills to pilot RGG successfully. Brief documentation of MeshKit source code, tools and other algorithms available are also presented for developers to extend and add new algorithms to MeshKit. RGG tools work in serial and parallel and have been used to model complex reactor core models consisting of conical pins, load pads, several thousands of axially varying material properties of instrumentation pins and other interstices meshes.« less

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.

Buried waste integrated demonstration human engineered control station. Final report

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

Not Available

1994-09-01

This document describes the Human Engineered Control Station (HECS) project activities including the conceptual designs. The purpose of the HECS is to enhance the effectiveness and efficiency of remote retrieval by providing an integrated remote control station. The HECS integrates human capabilities, limitations, and expectations into the design to reduce the potential for human error, provides an easy system to learn and operate, provides an increased productivity, and reduces the ultimate investment in training. The overall HECS consists of the technology interface stations, supporting engineering aids, platform (trailer), communications network (broadband system), and collision avoidance system.

NASA's Man-Systems Integration Standards: A Human Factors Engineering Standard for Everyone in the Nineties

NASA Technical Reports Server (NTRS)

Booher, Cletis R.; Goldsberry, Betty S.

1994-01-01

During the second half of the 1980s, a document was created by the National Aeronautics and Space Administration (NASA) to aid in the application of good human factors engineering and human interface practices to the design and development of hardware and systems for use in all United States manned space flight programs. This comprehensive document, known as NASA-STD-3000, the Man-Systems Integration Standards (MSIS), attempts to address, from a human factors engineering/human interface standpoint, all of the various types of equipment with which manned space flight crew members must deal. Basically, all of the human interface situations addressed in the MSIS are present in terrestrially based systems also. The premise of this paper is that, starting with this already created standard, comprehensive documents addressing human factors engineering and human interface concerns could be developed to aid in the design of almost any type of equipment or system which humans interface with in any terrestrial environment. Utilizing the systems and processes currently in place in the MSIS Development Facility at the Johnson Space Center in Houston, TX, any number of MSIS volumes addressing the human factors / human interface needs of any terrestrially based (or, for that matter, airborne) system could be created.

A Preliminary Data Model for Orbital Flight Dynamics in Shuttle Mission Control

NASA Technical Reports Server (NTRS)

ONeill, John; Shalin, Valerie L.

2000-01-01

The Orbital Flight Dynamics group in Shuttle Mission Control is investigating new user interfaces in a project called RIOTS [RIOTS 2000]. Traditionally, the individual functions of hardware and software guide the design of displays, which results in an aggregated, if not integrated interface. The human work system has then been designed and trained to navigate, operate and integrate the processors and displays. The aim of RIOTS is to reduce the cognitive demands of the flight controllers by redesigning the user interface to support the work of the flight controller. This document supports the RIOTS project by defining a preliminary data model for Orbital Flight Dynamics. Section 2 defines an information-centric perspective. An information-centric approach aims to reduce the cognitive workload of the flight controllers by reducing the need for manual integration of information across processors and displays. Section 3 describes the Orbital Flight Dynamics domain. Section 4 defines the preliminary data model for Orbital Flight Dynamics. Section 5 examines the implications of mapping the data model to Orbital Flight Dynamics current information systems. Two recurring patterns are identified in the Orbital Flight Dynamics work the iteration/rework cycle and the decision-making/information integration/mirroring role relationship. Section 6 identifies new requirements on Orbital Flight Dynamics work and makes recommendations based on changing the information environment, changing the implementation of the data model, and changing the two recurring patterns.

Minimum Hamiltonian ascent trajectory evaluation (MASTRE) program (update to automatic flight trajectory design, performance prediction, and vehicle sizing for support of shuttle and shuttle derived vehicles) users manual

NASA Technical Reports Server (NTRS)

Lyons, J. T.; Borchers, William R.

1993-01-01

Documentation for the User Interface Program for the Minimum Hamiltonian Ascent Trajectory Evaluation (MASTRE) is provided. The User Interface Program is a separate software package designed to ease the user input requirements when using the MASTRE Trajectory Program. This document supplements documentation on the MASTRE Program that consists of the MASTRE Engineering Manual and the MASTRE Programmers Guide. The User Interface Program provides a series of menus and tables using the VAX Screen Management Guideline (SMG) software. These menus and tables allow the user to modify the MASTRE Program input without the need for learning the various program dependent mnemonics. In addition, the User Interface Program allows the user to modify and/or review additional input Namelist and data files, to build and review command files, to formulate and calculate mass properties related data, and to have a plotting capability.

PAR -- Interface to the ADAM Parameter System

NASA Astrophysics Data System (ADS)

Currie, Malcolm J.; Chipperfield, Alan J.

PAR is a library of Fortran subroutines that provides convenient mechanisms for applications to exchange information with the outside world, through input-output channels called parameters. Parameters enable a user to control an application's behaviour. PAR supports numeric, character, and logical parameters, and is currently implemented only on top of the ADAM parameter system. The PAR library permits parameter values to be obtained, without or with a variety of constraints. Results may be put into parameters to be passed onto other applications. Other facilities include setting a prompt string, and suggested defaults. This document also introduces a preliminary C interface for the PAR library -- this may be subject to change in the light of experience.

Tutorial and hands-on demonstration of a fluent interpreter for CARE 3

NASA Technical Reports Server (NTRS)

Martensen, Anna L.; Bavuso, Salvatore J.

1987-01-01

This document updates one originally written as part of a workshop on the CARE 3 capability held at NASA Langley Research Center on February 22 to 24, 1984. Subsequent to the workshop, CARE 3 and its interface program were enhanced and extensive changes to the original document became necessary. This document, like its predecessor, is designed to illustrate the user interface capability and the salient CARE 3 features by describing various examples of reliability models and their solutions through the use of CARE 3.

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.

Online Learning Flight Control for Intelligent Flight Control Systems (IFCS)

NASA Technical Reports Server (NTRS)

Niewoehner, Kevin R.; Carter, John (Technical Monitor)

2001-01-01

The research accomplishments for the cooperative agreement 'Online Learning Flight Control for Intelligent Flight Control Systems (IFCS)' include the following: (1) previous IFC program data collection and analysis; (2) IFC program support site (configured IFC systems support network, configured Tornado/VxWorks OS development system, made Configuration and Documentation Management Systems Internet accessible); (3) Airborne Research Test Systems (ARTS) II Hardware (developed hardware requirements specification, developing environmental testing requirements, hardware design, and hardware design development); (4) ARTS II software development laboratory unit (procurement of lab style hardware, configured lab style hardware, and designed interface module equivalent to ARTS II faceplate); (5) program support documentation (developed software development plan, configuration management plan, and software verification and validation plan); (6) LWR algorithm analysis (performed timing and profiling on algorithm); (7) pre-trained neural network analysis; (8) Dynamic Cell Structures (DCS) Neural Network Analysis (performing timing and profiling on algorithm); and (9) conducted technical interchange and quarterly meetings to define IFC research goals.

CHeCS (Crew Health Care Systems): International Space Station (ISS) Medical Hardware Catalog. Version 10.0

NASA Technical Reports Server (NTRS)

2011-01-01

The purpose of this catalog is to provide a detailed description of each piece of hardware in the Crew Health Care System (CHeCS), including subpacks associated with the hardware, and to briefly describe the interfaces between the hardware and the ISS. The primary user of this document is the Space Medicine/Medical Operations ISS Biomedical Flight Controllers (ISS BMEs).

Development of a Software Safety Process and a Case Study of Its Use

NASA Technical Reports Server (NTRS)

Knight, J. C.

1996-01-01

Research in the year covered by this reporting period has been primarily directed toward: continued development of mock-ups of computer screens for operator of a digital reactor control system; development of a reactor simulation to permit testing of various elements of the control system; formal specification of user interfaces; fault-tree analysis including software; evaluation of formal verification techniques; and continued development of a software documentation system. Technical results relating to this grant and the remainder of the principal investigator's research program are contained in various reports and papers.

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.

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.

ARACHNE: A neural-neuroglial network builder with remotely controlled parallel computing

PubMed Central

Rusakov, Dmitri A.; Savtchenko, Leonid P.

2017-01-01

Creating and running realistic models of neural networks has hitherto been a task for computing professionals rather than experimental neuroscientists. This is mainly because such networks usually engage substantial computational resources, the handling of which requires specific programing skills. Here we put forward a newly developed simulation environment ARACHNE: it enables an investigator to build and explore cellular networks of arbitrary biophysical and architectural complexity using the logic of NEURON and a simple interface on a local computer or a mobile device. The interface can control, through the internet, an optimized computational kernel installed on a remote computer cluster. ARACHNE can combine neuronal (wired) and astroglial (extracellular volume-transmission driven) network types and adopt realistic cell models from the NEURON library. The program and documentation (current version) are available at GitHub repository https://github.com/LeonidSavtchenko/Arachne under the MIT License (MIT). PMID:28362877

The New Cloud Absorption Radiometer (CAR) Software: One Model for NASA Remote Sensing Virtual Instruments

NASA Technical Reports Server (NTRS)

Roth, Don J.; Rapchun, David A.; Jones, Hollis H.

2001-01-01

The Cloud Absorption Radiometer (CAR) instrument has been the most frequently used airborne instrument built in-house at NASA Goddard Space Flight Center, having flown scientific research missions on-board various aircraft to many locations in the United States, Azores, Brazil, and Kuwait since 1983. The CAR instrument is capable of measuring scattered light by clouds in fourteen spectral bands in UV, visible and near-infrared region. This document describes the control, data acquisition, display, and file storage software for the new version of CAR. This software completely replaces the prior CAR Data System and Control Panel with a compact and robust virtual instrument computer interface. Additionally, the instrument is now usable for the first time for taking data in an off-aircraft mode. The new instrument is controlled via a LabVIEW v5. 1.1-developed software interface that utilizes, (1) serial port writes to write commands to the controller module of the instrument, and (2) serial port reads to acquire data from the controller module of the instrument. Step-by-step operational procedures are provided in this document. A suite of other software programs has been developed to complement the actual CAR virtual instrument. These programs include: (1) a simulator mode that allows pretesting of new features that might be added in the future, as well as demonstrations to CAR customers, and development at times when the instrument/hardware is off-location, and (2) a post-experiment data viewer that can be used to view all segments of individual data cycles and to locate positions where 'start' and stop' byte sequences were incorrectly formulated by the instrument controller. The CAR software described here is expected to be the basis for CAR operation for many missions and many years to come.

An Introduction to Transient Engine Applications Using the Numerical Propulsion System Simulation (NPSS) and MATLAB

NASA Technical Reports Server (NTRS)

Chin, Jeffrey C.; Csank, Jeffrey T.; Haller, William J.; Seidel, Jonathan A.

2016-01-01

This document outlines methodologies designed to improve the interface between the Numerical Propulsion System Simulation framework and various control and dynamic analyses developed in the Matlab and Simulink environment. Although NPSS is most commonly used for steady-state modeling, this paper is intended to supplement the relatively sparse documentation on it's transient analysis functionality. Matlab has become an extremely popular engineering environment, and better methodologies are necessary to develop tools that leverage the benefits of these disparate frameworks. Transient analysis is not a new feature of the Numerical Propulsion System Simulation (NPSS), but transient considerations are becoming more pertinent as multidisciplinary trade-offs begin to play a larger role in advanced engine designs. This paper serves to supplement the relatively sparse documentation on transient modeling and cover the budding convergence between NPSS and Matlab based modeling toolsets. The following sections explore various design patterns to rapidly develop transient models. Each approach starts with a base model built with NPSS, and assumes the reader already has a basic understanding of how to construct a steady-state model. The second half of the paper focuses on further enhancements required to subsequently interface NPSS with Matlab codes. The first method being the simplest and most straightforward but performance constrained, and the last being the most abstract. These methods aren't mutually exclusive and the specific implementation details could vary greatly based on the designer's discretion. Basic recommendations are provided to organize model logic in a format most easily amenable to integration with existing Matlab control toolsets.

LANES - LOCAL AREA NETWORK EXTENSIBLE SIMULATOR

NASA Technical Reports Server (NTRS)

Gibson, J.

1994-01-01

The Local Area Network Extensible Simulator (LANES) provides a method for simulating the performance of high speed local area network (LAN) technology. LANES was developed as a design and analysis tool for networking on board the Space Station. The load, network, link and physical layers of a layered network architecture are all modeled. LANES models to different lower-layer protocols, the Fiber Distributed Data Interface (FDDI) and the Star*Bus. The load and network layers are included in the model as a means of introducing upper-layer processing delays associated with message transmission; they do not model any particular protocols. FDDI is an American National Standard and an International Organization for Standardization (ISO) draft standard for a 100 megabit-per-second fiber-optic token ring. Specifications for the LANES model of FDDI are taken from the Draft Proposed American National Standard FDDI Token Ring Media Access Control (MAC), document number X3T9.5/83-16 Rev. 10, February 28, 1986. This is a mature document describing the FDDI media-access-control protocol. Star*Bus, also known as the Fiber Optic Demonstration System, is a protocol for a 100 megabit-per-second fiber-optic star-topology LAN. This protocol, along with a hardware prototype, was developed by Sperry Corporation under contract to NASA Goddard Space Flight Center as a candidate LAN protocol for the Space Station. LANES can be used to analyze performance of a networking system based on either FDDI or Star*Bus under a variety of loading conditions. Delays due to upper-layer processing can easily be nullified, allowing analysis of FDDI or Star*Bus as stand-alone protocols. LANES is a parameter-driven simulation; it provides considerable flexibility in specifying both protocol an run-time parameters. Code has been optimized for fast execution and detailed tracing facilities have been included. LANES was written in FORTRAN 77 for implementation on a DEC VAX under VMS 4.6. It consists of two programs, a simulation program and a user-interface program. The simulation program requires the SLAM II simulation library from Pritsker and Associates, W. Lafayette IN; the user interface is implemented using the Ingres database manager from Relational Technology, Inc. Information about running the simulation program without the user-interface program is contained in the documentation. The memory requirement is 129,024 bytes. LANES was developed in 1988.

NASA Docking System (NDS) Interface Definitions Document (IDD). Revision F, Dec. 15, 2011

NASA Technical Reports Server (NTRS)

Lewis, James

2011-01-01

The NASA Docking System (NDS) mating system supports low approach velocity docking and provides a modular and reconfigurable standard interface, supporting crewed and autonomous vehicles during mating and assembly operations. The NDS is NASA s implementation for the International Docking System Standard (IDSS) using low impact docking technology. All NDS configurations can mate with the configuration specified in the IDSS Interface Definition Document (IDD), Revision A, released May 13, 2011. The NDS evolved from the Low Impact Docking System (LIDS). The term (and its associated acronym), international Low Impact Docking System (iLIDS) is also used to describe this system. NDS and iLIDS may be used interchangeability. Some of the heritage documentation and implementations (e.g., software command names) used on the NDS will continue to use the LIDS acronym.

Control integration concept for hypersonic cruise-turn maneuvers

NASA Technical Reports Server (NTRS)

Raney, David L.; Lallman, Frederick J.

1992-01-01

Piloting difficulties associated with conducting aircraft maneuvers in hypersonic flight are caused in part by the nonintuitive nature of the aircraft response and the stringent constraints anticipated on allowable angle of attack and dynamic pressure variations. An approach is documented that provides precise, coordinated maneuver control during excursions from a hypersonic cruise flight path and the necessary flight condition constraints. The approach is to achieve specified guidance commands by resolving altitude and cross range errors into a load factor and bank angle command by using a coordinate transformation that acts as an interface between outer and inner loop flight controls. This interface, referred to as a 'resolver', applies constraints on angle of attack and dynamic pressure perturbations while prioritizing altitude regulation over cross range. An unpiloted test simulation, in which the resolver was used to drive inner loop flight controls, produced time histories of responses to guidance commands and atmospheric disturbances at Mach numbers of 6, 10, 15, and 20. Angle of attack and throttle perturbation constraints, combined with high speed flight effects and the desire to maintain constant dynamic pressure, significantly impact the maneuver envelope for a hypersonic vehicle.

Aeroacoustic Codes for Rotor Harmonic and BVI Noise. CAMRAD.Mod1/HIRES: Methodology and Users' Manual

NASA Technical Reports Server (NTRS)

Boyd, D. Douglas, Jr.; Brooks, Thomas F.; Burley, Casey L.; Jolly, J. Ralph, Jr.

1998-01-01

This document details the methodology and use of the CAMRAD.Mod1/HIRES codes, which were developed at NASA Langley Research Center for the prediction of helicopter harmonic and Blade-Vortex Interaction (BVI) noise. CANMAD.Mod1 is a substantially modified version of the performance/trim/wake code CANMAD. High resolution blade loading is determined in post-processing by HIRES and an associated indicial aerodynamics code. Extensive capabilities of importance to noise prediction accuracy are documented, including a new multi-core tip vortex roll-up wake model, higher harmonic and individual blade control, tunnel and fuselage correction input, diagnostic blade motion input, and interfaces for acoustic and CFD aerodynamics codes. Modifications and new code capabilities are documented with examples. A users' job preparation guide and listings of variables and namelists are given.

Effective Use of SMSS: A Simple Strategy and Sample Implementation

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

Hensinger, David

1998-09-30

The purpose of this document is to present a strategy for effectively using SMSS (Sea.leable Mass Storage System) and to distribute a simple implementation of this strategy. This work was done as a stopgap memure to ~lOW ~ ~~yst to USe the storage Power of SMSS in the absence of a more user friendly interface. The features and functionality discussed in this document represent a minimum set of capabilities to allow a useful archiving interface functionality. The implementation presented is the most basic possible and would benefit significantly from an organized support and documentation effort.

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.

Kernel ADA Programming Support Environment (KAPSE) Interface Team Public Report. Volume 4.

DTIC Science & Technology

1984-04-30

the document until further discussion has taken place among the group metbers. RACWG announced their editor, Reed Kotler . The RACWG plans to narrow...KRUTAR, Rudy NRL *LAPLANT, Bill HQ USAF LOPER, Warren NOSC *MAGLIERI, Lucas Canadian National Defense HQ MILLER, Jo NWC MYERS, Gil NOSC *MYERS, Philip ...HUMPHREY, Dianna Control Data Corp. JOHNSON, Ron Boeing Aerospace Co. KERNER, Judy Norden Systems KOTLER , Reed Lockheed Missiles & Space LAMB, J. Eli

Usability and Safety in Electronic Medical Records Interface Design: A Review of Recent Literature and Guideline Formulation.

PubMed

Zahabi, Maryam; Kaber, David B; Swangnetr, Manida

2015-08-01

The objectives of this study were to (a) review electronic medical record (EMR) and related electronic health record (EHR) interface usability issues, (b) review how EMRs have been evaluated with safety analysis techniques along with any hazard recognition, and (c) formulate design guidelines and a concept for enhanced EMR interfaces with a focus on diagnosis and documentation processes. A major impact of information technology in health care has been the introduction of EMRs. Although numerous studies indicate use of EMRs to increase health care quality, there remain concerns with usability issues and safety. A literature search was conducted using Compendex, PubMed, CINAHL, and Web of Science databases to find EMR research published since 2000. Inclusion criteria included relevant English-language papers with subsets of keywords and any studies (manually) identified with a focus on EMR usability. Fifty studies met the inclusion criteria. Results revealed EMR and EHR usability problems to include violations of natural dialog, control consistency, effective use of language, effective information presentation, and customization principles as well as a lack of error prevention, minimization of cognitive load, and feedback. Studies focusing on EMR system safety made no objective assessments and applied only inductive reasoning methods for hazard recognition. On the basis of the identified usability problems and structure of safety analysis techniques, we provide EMR design guidelines and a design concept focused on the diagnosis process and documentation. The design guidelines and new interface concept can be used for prototyping and testing enhanced EMRs. © 2015, Human Factors and Ergonomics Society.

Use of software engineering techniques in the design of the ALEPH data acquisition system

NASA Astrophysics Data System (ADS)

Charity, T.; McClatchey, R.; Harvey, J.

1987-08-01

The SASD methodology is being used to provide a rigorous design framework for various components of the ALEPH data acquisition system. The Entity-Relationship data model is used to describe the layout and configuration of the control and acquisition systems and detector components. State Transition Diagrams are used to specify control applications such as run control and resource management and Data Flow Diagrams assist in decomposing software tasks and defining interfaces between processes. These techniques encourage rigorous software design leading to enhanced functionality and reliability. Improved documentation and communication ensures continuity over the system life-cycle and simplifies project management.

Hazard Analysis for Pneumatic Flipper Suitport/Z-1 Manned Evaluation, Chamber B, Building 32. Revision: Basic

NASA Technical Reports Server (NTRS)

2012-01-01

One of the characteristics of an effective safety program is the recognition and control of hazards before mishaps or failures occur. Conducting potentially hazardous tests necessitates a thorough hazard analysis in order to protect our personnel from injury and our equipment from damage. The purpose of this hazard analysis is to define and address the potential hazards and controls associated with the Z1 Suit Port Test in Chamber B located in building 32, and to provide the applicable team of personnel with the documented results. It is imperative that each member of the team be familiar with the hazards and controls associated with his/her particular tasks, assignments, and activities while interfacing with facility test systems, equipment, and hardware. The goal of this hazard analysis is to identify all hazards that have the potential to harm personnel and/or damage facility equipment, flight hardware, property, or harm the environment. This analysis may also assess the significance and risk, when applicable, of lost test objectives when substantial monetary value is involved. The hazards, causes, controls, verifications, and risk assessment codes have been documented on the hazard analysis work sheets in appendix A of this document. The preparation and development of this report is in accordance with JPR 1700.1, JSC Safety and Health Handbook.

Model-based software engineering for an optical navigation system for spacecraft

NASA Astrophysics Data System (ADS)

Franz, T.; Lüdtke, D.; Maibaum, O.; Gerndt, A.

2017-09-01

The project Autonomous Terrain-based Optical Navigation (ATON) at the German Aerospace Center (DLR) is developing an optical navigation system for future landing missions on celestial bodies such as the moon or asteroids. Image data obtained by optical sensors can be used for autonomous determination of the spacecraft's position and attitude. Camera-in-the-loop experiments in the Testbed for Robotic Optical Navigation (TRON) laboratory and flight campaigns with unmanned aerial vehicle (UAV) are performed to gather flight data for further development and to test the system in a closed-loop scenario. The software modules are executed in the C++ Tasking Framework that provides the means to concurrently run the modules in separated tasks, send messages between tasks, and schedule task execution based on events. Since the project is developed in collaboration with several institutes in different domains at DLR, clearly defined and well-documented interfaces are necessary. Preventing misconceptions caused by differences between various development philosophies and standards turned out to be challenging. After the first development cycles with manual Interface Control Documents (ICD) and manual implementation of the complex interactions between modules, we switched to a model-based approach. The ATON model covers a graphical description of the modules, their parameters and communication patterns. Type and consistency checks on this formal level help to reduce errors in the system. The model enables the generation of interfaces and unified data types as well as their documentation. Furthermore, the C++ code for the exchange of data between the modules and the scheduling of the software tasks is created automatically. With this approach, changing the data flow in the system or adding additional components (e.g., a second camera) have become trivial.

Model-based software engineering for an optical navigation system for spacecraft

NASA Astrophysics Data System (ADS)

Franz, T.; Lüdtke, D.; Maibaum, O.; Gerndt, A.

2018-06-01

The project Autonomous Terrain-based Optical Navigation (ATON) at the German Aerospace Center (DLR) is developing an optical navigation system for future landing missions on celestial bodies such as the moon or asteroids. Image data obtained by optical sensors can be used for autonomous determination of the spacecraft's position and attitude. Camera-in-the-loop experiments in the Testbed for Robotic Optical Navigation (TRON) laboratory and flight campaigns with unmanned aerial vehicle (UAV) are performed to gather flight data for further development and to test the system in a closed-loop scenario. The software modules are executed in the C++ Tasking Framework that provides the means to concurrently run the modules in separated tasks, send messages between tasks, and schedule task execution based on events. Since the project is developed in collaboration with several institutes in different domains at DLR, clearly defined and well-documented interfaces are necessary. Preventing misconceptions caused by differences between various development philosophies and standards turned out to be challenging. After the first development cycles with manual Interface Control Documents (ICD) and manual implementation of the complex interactions between modules, we switched to a model-based approach. The ATON model covers a graphical description of the modules, their parameters and communication patterns. Type and consistency checks on this formal level help to reduce errors in the system. The model enables the generation of interfaces and unified data types as well as their documentation. Furthermore, the C++ code for the exchange of data between the modules and the scheduling of the software tasks is created automatically. With this approach, changing the data flow in the system or adding additional components (e.g., a second camera) have become trivial.

Draper Station Analysis Tool

NASA Technical Reports Server (NTRS)

Bedrossian, Nazareth; Jang, Jiann-Woei; McCants, Edward; Omohundro, Zachary; Ring, Tom; Templeton, Jeremy; Zoss, Jeremy; Wallace, Jonathan; Ziegler, Philip

2011-01-01

Draper Station Analysis Tool (DSAT) is a computer program, built on commercially available software, for simulating and analyzing complex dynamic systems. Heretofore used in designing and verifying guidance, navigation, and control systems of the International Space Station, DSAT has a modular architecture that lends itself to modification for application to spacecraft or terrestrial systems. DSAT consists of user-interface, data-structures, simulation-generation, analysis, plotting, documentation, and help components. DSAT automates the construction of simulations and the process of analysis. DSAT provides a graphical user interface (GUI), plus a Web-enabled interface, similar to the GUI, that enables a remotely located user to gain access to the full capabilities of DSAT via the Internet and Webbrowser software. Data structures are used to define the GUI, the Web-enabled interface, simulations, and analyses. Three data structures define the type of analysis to be performed: closed-loop simulation, frequency response, and/or stability margins. DSAT can be executed on almost any workstation, desktop, or laptop computer. DSAT provides better than an order of magnitude improvement in cost, schedule, and risk assessment for simulation based design and verification of complex dynamic systems.

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.

Virtual Keyboard for Hands-Free Operations

NASA Technical Reports Server (NTRS)

Abou-Ali, Abdel-Latief; Porter, William A.

1996-01-01

The measurement of direction of gaze (d.o.g.) has been used for clinical purposes to detect illness, such as nystagmus, unusual fixation movements and many others. It also is used to determine the points of interest in objects. In this study we employ a measurement of d.o.g. as a computer interface. The interface provides a full keyboard as well as a mouse function. Such an interface is important to computer users with paralysis or in environments where hand-free machine interface is required. The study utilizes the commercially available (ISCAN Model RK426TC) headset which consists of an InfraRed (IR) source and an IR camera to sense deflection of the illuminating beam. It also incorporates image processing package that provides the position of the pupil as well as the pupil size. The study shows the ability of implementing a full keyboard, together with some control functions, imaged on a head mounted monitor screen. This document is composed of four sections: (1) The Nature of the Equipment; (2) The Calibration Process; (3) Running Process; and (4) Conclusions.

Marky: a tool supporting annotation consistency in multi-user and iterative document annotation projects.

PubMed

Pérez-Pérez, Martín; Glez-Peña, Daniel; Fdez-Riverola, Florentino; Lourenço, Anália

2015-02-01

Document annotation is a key task in the development of Text Mining methods and applications. High quality annotated corpora are invaluable, but their preparation requires a considerable amount of resources and time. Although the existing annotation tools offer good user interaction interfaces to domain experts, project management and quality control abilities are still limited. Therefore, the current work introduces Marky, a new Web-based document annotation tool equipped to manage multi-user and iterative projects, and to evaluate annotation quality throughout the project life cycle. At the core, Marky is a Web application based on the open source CakePHP framework. User interface relies on HTML5 and CSS3 technologies. Rangy library assists in browser-independent implementation of common DOM range and selection tasks, and Ajax and JQuery technologies are used to enhance user-system interaction. Marky grants solid management of inter- and intra-annotator work. Most notably, its annotation tracking system supports systematic and on-demand agreement analysis and annotation amendment. Each annotator may work over documents as usual, but all the annotations made are saved by the tracking system and may be further compared. So, the project administrator is able to evaluate annotation consistency among annotators and across rounds of annotation, while annotators are able to reject or amend subsets of annotations made in previous rounds. As a side effect, the tracking system minimises resource and time consumption. Marky is a novel environment for managing multi-user and iterative document annotation projects. Compared to other tools, Marky offers a similar visually intuitive annotation experience while providing unique means to minimise annotation effort and enforce annotation quality, and therefore corpus consistency. Marky is freely available for non-commercial use at http://sing.ei.uvigo.es/marky. Copyright © 2014 Elsevier Ireland Ltd. All rights reserved.

SU-G-TeP4-06: An Integrated Application for Radiation Therapy Treatment Plan Directives, Management, and Reporting

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

Matuszak, M; Anderson, C; Lee, C

Purpose: With electronic medical records, patient information for the treatment planning process has become disseminated across multiple applications with limited quality control and many associated failure modes. We present the development of a single application with a centralized database to manage the planning process. Methods: The system was designed to replace current functionalities of (i) static directives representing the physician intent for the prescription and planning goals, localization information for delivery, and other information, (ii) planning objective reports, (iii) localization and image guidance documents and (iv) the official radiation therapy prescription in the medical record. Using the Eclipse Scripting Applicationmore » Programming Interface, a plug-in script with an associated domain-specific SQL Server database was created to manage the information in (i)–(iv). The system’s user interface and database were designed by a team of physicians, clinical physicists, database experts, and software engineers to ensure usability and robustness for clinical use. Results: The resulting system has been fully integrated within the TPS via a custom script and database. Planning scenario templates, version control, approvals, and logic-based quality control allow this system to fully track and document the planning process as well as physician approval of tradeoffs while improving the consistency of the data. Multiple plans and prescriptions are supported along with non-traditional dose objectives and evaluation such as biologically corrected models, composite dose limits, and management of localization goals. User-specific custom views were developed for the attending physician review, physicist plan checks, treating therapists, and peer review in chart rounds. Conclusion: A method was developed to maintain cohesive information throughout the planning process within one integrated system by using a custom treatment planning management application that interfaces directly with the TPS. Future work includes quantifying the improvements in quality, safety and efficiency that are possible with the routine clinical use of this system. Supported in part by NIH-P01-CA-059827.« less

Understanding Clinician Information Demands and Synthesis of Clinical Documents in Electronic Health Record Systems

ERIC Educational Resources Information Center

Farri, Oladimeji Feyisetan

2012-01-01

Large quantities of redundant clinical data are usually transferred from one clinical document to another, making the review of such documents cognitively burdensome and potentially error-prone. Inadequate designs of electronic health record (EHR) clinical document user interfaces probably contribute to the difficulties clinicians experience while…

Generating Hierarchical Document Indices from Common Denominators in Large Document Collections.

ERIC Educational Resources Information Center

O'Kane, Kevin C.

1996-01-01

Describes an algorithm for computer generation of hierarchical indexes for document collections. The resulting index, when presented with a graphical interface, provides users with a view of a document collection that permits general browsing and informal search activities via an access method that requires no keyboard entry or prior knowledge of…

Towards the formal specification 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

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, is described. 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 approaches that were developed for modeling the PIU requirements and for composition of the PIU subcomponents at high levels of abstraction are described. These approaches were used to specify and verify a nontrivial subset of the PIU behavior. The PIU specification in Higher Order Logic (HOL) is documented in a companion NASA contractor report entitled 'Towards the Formal Specification of the Requirements and Design of a Processor Interfacs Unit - HOL Listings.' The subsequent verification approach and HOL listings are documented in NASA contractor report entitled 'Towards the Formal Verification of the Requirements and Design of a Processor Interface Unit' and NASA contractor report entitled 'Towards the Formal Verification of the Requirements and Design of a Processor Interface Unit - HOL Listings.'

A proposed application programming interface for a physical volume repository

NASA Technical Reports Server (NTRS)

Jones, Merritt; Williams, Joel; Wrenn, Richard

1996-01-01

The IEEE Storage System Standards Working Group (SSSWG) has developed the Reference Model for Open Storage Systems Interconnection, Mass Storage System Reference Model Version 5. This document, provides the framework for a series of standards for application and user interfaces to open storage systems. More recently, the SSSWG has been developing Application Programming Interfaces (APIs) for the individual components defined by the model. The API for the Physical Volume Repository is the most fully developed, but work is being done on APIs for the Physical Volume Library and for the Mover also. The SSSWG meets every other month, and meetings are open to all interested parties. The Physical Volume Repository (PVR) is responsible for managing the storage of removable media cartridges and for mounting and dismounting these cartridges onto drives. This document describes a model which defines a Physical Volume Repository, and gives a brief summary of the Application Programming Interface (API) which the IEEE Storage Systems Standards Working Group (SSSWG) is proposing as the standard interface for the PVR.

Bi-directional communication interface for microprocessor-to-system/370

NASA Technical Reports Server (NTRS)

Fischer, J. P.

1981-01-01

The design and operation of a bi-directional communication interface between a microcomputer and the IBM System/370 is documented. The hardware unit interconnects a modem to interface to the S/370, the microcomputer with an EIA I/O port, and a terminal for sending and receiving data from either the microcomputer or the S/370. Also described is the software necessary for the two-way interface. This interface is designed so that no modifications need to be made to the terminal, modem, or microcomputer.

Digitization of medical documents: an X-Windows application for fast scanning.

PubMed

Muñoz, A; Salvador, C H; Gonzalez, M A; Dueñas, A

1992-01-01

This paper deals with digitization, using a commercial scanner, of medical documents as still images for introduction into a computer-based Information System. Document management involves storing, editing and transmission. This task has usually been approached from the perspective of the difficulties posed by radiologic images because of their indisputable qualitative and quantitative significance. However, healthcare activities require the management of many other types of documents and involve the requirements of numerous users. One key to document management will be the availability of a digitizer to deal with the greatest possible number of different types of documents. This paper describes the relevant aspects of documents and the technical specifications that digitizers must fulfill. The concept of document type is introduced as the ideal set of digitizing parameters for a given document. The use of document type parameters can drastically reduce the time the user spends in scanning sessions. Presentation is made of an application based on Unix, X-Windows and OSF/Motif, with a GPIB interface, implemented around the document type concept. Finally, the results of the evaluation of the application are presented, focusing on the user interface, as well as on the viewing of color images in an X-Windows environment and the use of lossy algorithms in the compression of medical images.

Interfacing and Verifying ALHAT Safe Precision Landing Systems with the Morpheus Vehicle

NASA Technical Reports Server (NTRS)

Carson, John M., III; Hirsh, Robert L.; Roback, Vincent E.; Villalpando, Carlos; Busa, Joseph L.; Pierrottet, Diego F.; Trawny, Nikolas; Martin, Keith E.; Hines, Glenn D.

2015-01-01

The NASA Autonomous precision Landing and Hazard Avoidance Technology (ALHAT) project developed a suite of prototype sensors to enable autonomous and safe precision landing of robotic or crewed vehicles under any terrain lighting conditions. Development of the ALHAT sensor suite was a cross-NASA effort, culminating in integration and testing on-board a variety of terrestrial vehicles toward infusion into future spaceflight applications. Terrestrial tests were conducted on specialized test gantries, moving trucks, helicopter flights, and a flight test onboard the NASA Morpheus free-flying, rocket-propulsive flight-test vehicle. To accomplish these tests, a tedious integration process was developed and followed, which included both command and telemetry interfacing, as well as sensor alignment and calibration verification to ensure valid test data to analyze ALHAT and Guidance, Navigation and Control (GNC) performance. This was especially true for the flight test campaign of ALHAT onboard Morpheus. For interfacing of ALHAT sensors to the Morpheus flight system, an adaptable command and telemetry architecture was developed to allow for the evolution of per-sensor Interface Control Design/Documents (ICDs). Additionally, individual-sensor and on-vehicle verification testing was developed to ensure functional operation of the ALHAT sensors onboard the vehicle, as well as precision-measurement validity for each ALHAT sensor when integrated within the Morpheus GNC system. This paper provides some insight into the interface development and the integrated-systems verification that were a part of the build-up toward success of the ALHAT and Morpheus flight test campaigns in 2014. These campaigns provided valuable performance data that is refining the path toward spaceflight infusion of the ALHAT sensor suite.

Avionics Interface Data Summaries: A-10A, EF-111A, F-4E, F-4G, F-15A, F- 16A, F-111A, F-111E, F-111F, RF-4C

DTIC Science & Technology

1979-10-01

AIRCRAFT Flight Control ASA-32( ) Flight Director Computer TBD (Same as non -ARN-101 equipped F-4E aircraft) Air Data Computer CPK-92/A24G-34 Attitude...below. A two-inch separation between cable types is arbitrarily set as a minimum design goal. 3.2.6.4.1 Power and Control Circuits. Roucing and channel...plan in accordance with MIL-STD-461A(3) shall be the controlling document for EMIC design . 3.2.7.1 Design Reuire-nents. The generation of and suscepti

Framework and prototype for a secure XML-based electronic health records system.

PubMed

Steele, Robert; Gardner, William; Chandra, Darius; Dillon, Tharam S

2007-01-01

Security of personal medical information has always been a challenge for the advancement of Electronic Health Records (EHRs) initiatives. eXtensible Markup Language (XML), is rapidly becoming the key standard for data representation and transportation. The widespread use of XML and the prospect of its use in the Electronic Health (e-health) domain highlights the need for flexible access control models for XML data and documents. This paper presents a declarative access control model for XML data repositories that utilises an expressive XML role control model. The operational semantics of this model are illustrated by Xplorer, a user interface generation engine which supports search-browse-navigate activities on XML repositories.

Liquid hydrogen turbopump ALS advanced development program. Volume 1: Hot fire unit

NASA Technical Reports Server (NTRS)

Lindley, Bruce

1990-01-01

The interface criteria for the Turbopump Test article (TPA) and the Component Test Facility located at NASA, Stennis Space Center is defined by this interface Control Document (ICD). TPA ICD Volume 2 is submitted for the Cold Gas Drive Turbopump Test Article, which is generally similar but incorporates certain changes, particularly in fluid requirements and in instrumentation needs. For the purposes of this ICD, the test article consists of the Hot Fire Drive Turbopump mounted on its test cart, readied for installation in the component test facility. It should be emphasized that the LH2 turbopump program is still in its early concept design phase. Design of the turbopump, test cart, and spools are subject to revisions until successful conclusion of the Detail Design Review (DDR).

New generation of 3D desktop computer interfaces

NASA Astrophysics Data System (ADS)

Skerjanc, Robert; Pastoor, Siegmund

1997-05-01

Today's computer interfaces use 2-D displays showing windows, icons and menus and support mouse interactions for handling programs and data files. The interface metaphor is that of a writing desk with (partly) overlapping sheets of documents placed on its top. Recent advances in the development of 3-D display technology give the opportunity to take the interface concept a radical stage further by breaking the design limits of the desktop metaphor. The major advantage of the envisioned 'application space' is, that it offers an additional, immediately perceptible dimension to clearly and constantly visualize the structure and current state of interrelations between documents, videos, application programs and networked systems. In this context, we describe the development of a visual operating system (VOS). Under VOS, applications appear as objects in 3-D space. Users can (graphically connect selected objects to enable communication between the respective applications. VOS includes a general concept of visual and object oriented programming for tasks ranging from, e.g., low-level programming up to high-level application configuration. In order to enable practical operation in an office or at home for many hours, the system should be very comfortable to use. Since typical 3-D equipment used, e.g., in virtual-reality applications (head-mounted displays, data gloves) is rather cumbersome and straining, we suggest to use off-head displays and contact-free interaction techniques. In this article, we introduce an autostereoscopic 3-D display and connected video based interaction techniques which allow viewpoint-depending imaging (by head tracking) and visually controlled modification of data objects and links (by gaze tracking, e.g., to pick, 3-D objects just by looking at them).

Factors affecting physicians' use of a dedicated overview interface in an electronic health record: The importance of standard information and standard documentation.

PubMed

Jensen, Lotte Groth; Bossen, Claus

2016-03-01

It remains a continual challenge to present information in user interfaces in large IT systems to support overview in the best possible way. We here examine how an electronic health record (EHR) supports the creation of overview among hospital physicians with a particular focus on the use of an interface designed to provide clinicians with a patient information overview. The overview interface integrates information flexibly from diverse places in the EHR and presents this information in one screen display. Our study revealed widespread non-use of the overview interface. We explore the reasons for its use and non-use. We conducted exploratory ethnographic fieldwork among physicians in two hospitals and gathered statistical data on their use of the overview interface. From the quantitative data, we identified where the interface was used most and conducted 18 semi-structured, open-ended interviews framed by the theoretical framework and the findings of the initial ethnographic fieldwork. We interviewed both physicians and employees from the IT units in different hospitals. We then analysed notes from the ethnographic fieldwork and the interviews and ordered these into themes forming the basis for the presentation of findings. The overview interface was most used in departments or situations where the problem at hand and the need for information could be standardized-in particular, in anesthesiological departments and outpatient clinics. However, departments with complex and long patient histories did not make much use of the overview interface. Design and layout were not mentioned as decisive factors affecting its use or non-use. Many physicians questioned the completeness of data in the overview interface-either because they were skeptical about the hospital's or the department's documentation practices, or because they could not recognize the structure of the interface. This uncertainty discouraged physicians from using the overview interface. Dedicating a specific function or interface to supporting overview works best where information needs can be standardized. The narrative and contextual nature of creating clinical overview is unlikely to be optimally supported by using the overview interface alone. The use of these kinds of interfaces requires trust in data completeness and other clinicians' and administrative staff's documentation practices, as well as an understanding of the underlying structure of the EHR and how information is filtered when data are aggregated for the interface. Copyright © 2015. Published by Elsevier Ireland Ltd.

The sequence measurement system of the IR camera

NASA Astrophysics Data System (ADS)

Geng, Ai-hui; Han, Hong-xia; Zhang, Hai-bo

2011-08-01

Currently, the IR cameras are broadly used in the optic-electronic tracking, optic-electronic measuring, fire control and optic-electronic countermeasure field, but the output sequence of the most presently applied IR cameras in the project is complex and the giving sequence documents from the leave factory are not detailed. Aiming at the requirement that the continuous image transmission and image procession system need the detailed sequence of the IR cameras, the sequence measurement system of the IR camera is designed, and the detailed sequence measurement way of the applied IR camera is carried out. The FPGA programming combined with the SignalTap online observation way has been applied in the sequence measurement system, and the precise sequence of the IR camera's output signal has been achieved, the detailed document of the IR camera has been supplied to the continuous image transmission system, image processing system and etc. The sequence measurement system of the IR camera includes CameraLink input interface part, LVDS input interface part, FPGA part, CameraLink output interface part and etc, thereinto the FPGA part is the key composed part in the sequence measurement system. Both the video signal of the CmaeraLink style and the video signal of LVDS style can be accepted by the sequence measurement system, and because the image processing card and image memory card always use the CameraLink interface as its input interface style, the output signal style of the sequence measurement system has been designed into CameraLink interface. The sequence measurement system does the IR camera's sequence measurement work and meanwhile does the interface transmission work to some cameras. Inside the FPGA of the sequence measurement system, the sequence measurement program, the pixel clock modification, the SignalTap file configuration and the SignalTap online observation has been integrated to realize the precise measurement to the IR camera. Te sequence measurement program written by the verilog language combining the SignalTap tool on line observation can count the line numbers in one frame, pixel numbers in one line and meanwhile account the line offset and row offset of the image. Aiming at the complex sequence of the IR camera's output signal, the sequence measurement system of the IR camera accurately measures the sequence of the project applied camera, supplies the detailed sequence document to the continuous system such as image processing system and image transmission system and gives out the concrete parameters of the fval, lval, pixclk, line offset and row offset. The experiment shows that the sequence measurement system of the IR camera can get the precise sequence measurement result and works stably, laying foundation for the continuous system.

Data Presentation and Visualization (DPV) Interface Control Document

NASA Technical Reports Server (NTRS)

Mazzone, Rebecca A.; Conroy, Michael P.

2015-01-01

Data Presentation and Visualization (DPV) is a subset of the modeling and simulation (M&S) capabilities at Kennedy Space Center (KSC) that endeavors to address the challenges of how to present and share simulation output for analysts, stakeholders, decision makers, and other interested parties. DPV activities focus on the development and provision of visualization tools to meet the objectives identified above, as well as providing supporting tools and capabilities required to make its visualization products available and accessible across NASA.

KAPSE Interface Team (KIT) Public Report. Volume 8, Part 1

DTIC Science & Technology

1989-10-01

an issue area for export control of technology. 4. KrTIA CRI4A REPOFt Heri Fischer, KITIA chairperson reviewed the sta:us of KITIA activities: 3 e ...docment,3 the Validation Procedures document, Reference Manual and Guidebook. The E &V Team wants to find kindred spirits in the E &V area and possible new...one area of research where we feel we are significantly ahead of not only the commercial I market , but most of the research community as well

An Upgrade of the Aeroheating Software ''MINIVER''

NASA Technical Reports Server (NTRS)

Louderback, Pierce

2013-01-01

Detailed computational modeling: CFO often used to create and execute computational domains. Increasing complexity when moving from 20 to 30 geometries. Computational time increased as finer grids are used (accuracy). Strong tool, but takes time to set up and run. MINIVER: Uses theoretical and empirical correlations. Orders of magnitude faster to set up and run. Not as accurate as CFO, but gives reasonable estimations. MINIVER's Drawbacks: Rigid command-line interface. Lackluster, unorganized documentation. No central control; multiple versions exist and have diverged.

Constructing Uniform Resource Locators (URLs) for Searching the Marine Realms Information Bank

USGS Publications Warehouse

Linck, Guthrie A.; Allwardt, Alan O.; Lightsom, Frances L.

2009-01-01

The Marine Realms Information Bank (MRIB) is a digital library that provides access to free online scientific information about the oceans and coastal regions. To search its collection, MRIB uses a Common Gateway Interface (CGI) program, which allows automated search requests using Uniform Resource Locators (URLs). This document provides an overview of how to construct URLs to execute MRIB queries. The parameters listed allow detailed control of which records are retrieved, how they are returned, and how their display is formatted.

Hazard Analysis for Building 34 Vacuum Glove Box Assembly

NASA Technical Reports Server (NTRS)

Meginnis, Ian

2014-01-01

One of the characteristics of an effective safety program is the recognition and control of hazards before mishaps or failures occur. Conducting potentially hazardous tests necessitates a thorough hazard analysis in order to prevent injury to personnel, and to prevent damage to facilities and equipment. The primary purpose of this hazard analysis is to define and address the potential hazards and controls associated with the Building 34 Vacuum Glove Box Assembly, and to provide the applicable team of personnel with the documented results. It is imperative that each member of the team be familiar with the hazards and controls associated with his/her particular tasks, assignments and activities while interfacing with facility test systems, equipment and hardware. In fulfillment of the stated purposes, the goal of this hazard analysis is to identify all hazards that have the potential to harm personnel, damage the facility or its test systems or equipment, test articles, Government or personal property, or the environment. This analysis may also assess the significance and risk, when applicable, of lost test objectives when substantial monetary value is involved. The hazards, causes, controls, verifications, and risk assessment codes have been documented on the hazard analysis work sheets in Appendix A of this document. The preparation and development of this report is in accordance with JPR 1700.1, "JSC Safety and Health Handbook" and JSC 17773 Rev D "Instructions for Preparation of Hazard Analysis for JSC Ground Operations".

Site systems engineering fiscal year 1999 multi-year work plan (MYWP) update for WBS 1.8.2.2

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

GRYGIEL, M.L.

1998-10-08

Manage the Site Systems Engineering process to provide a traceable integrated requirements-driven, and technically defensible baseline. Through the Site Integration Group(SIG), Systems Engineering ensures integration of technical activities across all site projects. Systems Engineering's primary interfaces are with the RL Project Managers, the Project Direction Office and with the Project Major Subcontractors, as well as with the Site Planning organization. Systems Implementation: (1) Develops, maintains, and controls the site integrated technical baseline, ensures the Systems Engineering interfaces between projects are documented, and maintain the Site Environmental Management Specification. (2) Develops and uses dynamic simulation models for verification of the baselinemore » and analysis of alternatives. (3) Performs and documents fictional and requirements analyses. (4) Works with projects, technology management, and the SIG to identify and resolve technical issues. (5) Supports technical baseline information for the planning and budgeting of the Accelerated Cleanup Plan, Multi-Year Work Plans, Project Baseline Summaries as well as performance measure reporting. (6) Works with projects to ensure the quality of data in the technical baseline. (7) Develops, maintains and implements the site configuration management system.« less

A Tailored Concept of Operations for NASA LSP Integrated Operations

NASA Technical Reports Server (NTRS)

Owens, Clark V.

2016-01-01

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this project is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services.

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).

Abort-once-around entry corridor analysis program document

NASA Technical Reports Server (NTRS)

Kyle, H. C.

1975-01-01

The abort once around entry target corridor analysis program (ABECAP) was studied. The allowable range of flight path angles at entry interface for acceptable entry trajectories from a shuttle abort once around (AOA) situation was established. The solutions thus determined may be shown as corridor plots of entry interface flight path angle versus range from entry interface (EI) to the target.

Developing the Multimedia User Interface Component (MUSIC) for the Icarus Presentation System (IPS)

DTIC Science & Technology

1993-12-01

AD-A276 341 In-House Report December 1993 DEVELOPING THE MULTIMEDIA USER INTERFACE COMPONENT ( MUSIC ) FOR THE ICARUS PRESENTATION SYSTEM (IPS) Ingrid...DATEs COVERED 7 December 1993 Ina-House Jun - Aug 93 4 TWLE AM SL1sM1E & FUNDING NUMBERS DEVELOPING THE MULTIMEDIA USER INTERFACE COMPONENT ( MUSIC ) PE...the Multimedia User Interface Component ( MUSIC ). This report documents the initial research, design and implementation of a prototype of the MUSIC

Tags Extarction from Spatial Documents in Search Engines

NASA Astrophysics Data System (ADS)

Borhaninejad, S.; Hakimpour, F.; Hamzei, E.

2015-12-01

Nowadays the selective access to information on the Web is provided by search engines, but in the cases which the data includes spatial information the search task becomes more complex and search engines require special capabilities. The purpose of this study is to extract the information which lies in spatial documents. To that end, we implement and evaluate information extraction from GML documents and a retrieval method in an integrated approach. Our proposed system consists of three components: crawler, database and user interface. In crawler component, GML documents are discovered and their text is parsed for information extraction; storage. The database component is responsible for indexing of information which is collected by crawlers. Finally the user interface component provides the interaction between system and user. We have implemented this system as a pilot system on an Application Server as a simulation of Web. Our system as a spatial search engine provided searching capability throughout the GML documents and thus an important step to improve the efficiency of search engines has been taken.

Independent Orbiter Assessment (IOA): Analysis of the remote manipulator system

NASA Technical Reports Server (NTRS)

Tangorra, F.; Grasmeder, R. F.; Montgomery, A. D.

1987-01-01

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA approach features a top-down analysis of the hardware to determine failure modes, criticality, and potential critical items (PCIs). To preserve independence, this analysis was accomplished without reliance upon the results contained within the NASA FMEA/CIL documentation. The independent analysis results for the Orbiter Remote Manipulator System (RMS) are documented. The RMS hardware and software are primarily required for deploying and/or retrieving up to five payloads during a single mission, capture and retrieve free-flying payloads, and for performing Manipulator Foot Restraint operations. Specifically, the RMS hardware consists of the following components: end effector; displays and controls; manipulator controller interface unit; arm based electronics; and the arm. The IOA analysis process utilized available RMS hardware drawings, schematics and documents for defining hardware assemblies, components and hardware items. Each level of hardware was evaluated and analyzed for possible failure modes and effects. Criticality was assigned based upon the severity of the effect for each failure mode. Of the 574 failure modes analyzed, 413 were determined to be PCIs.

Doclet To Synthesize UML

NASA Technical Reports Server (NTRS)

Barry, Matthew R.; Osborne, Richard N.

2005-01-01

The RoseDoclet computer program extends the capability of Java doclet software to automatically synthesize Unified Modeling Language (UML) content from Java language source code. [Doclets are Java-language programs that use the doclet application programming interface (API) to specify the content and format of the output of Javadoc. Javadoc is a program, originally designed to generate API documentation from Java source code, now also useful as an extensible engine for processing Java source code.] RoseDoclet takes advantage of Javadoc comments and tags already in the source code to produce a UML model of that code. RoseDoclet applies the doclet API to create a doclet passed to Javadoc. The Javadoc engine applies the doclet to the source code, emitting the output format specified by the doclet. RoseDoclet emits a Rose model file and populates it with fully documented packages, classes, methods, variables, and class diagrams identified in the source code. The way in which UML models are generated can be controlled by use of new Javadoc comment tags that RoseDoclet provides. The advantage of using RoseDoclet is that Javadoc documentation becomes leveraged for two purposes: documenting the as-built API and keeping the design documentation up to date.

MODIS information, data and control system (MIDACS) operations concepts

NASA Technical Reports Server (NTRS)

Han, D.; Salomonson, V.; Ormsby, J.; Ardanuy, P.; Mckay, A.; Hoyt, D.; Jaffin, S.; Vallette, B.; Sharts, B.; Folta, D.

1988-01-01

The MODIS Information, Data, and Control System (MIDACS) Operations Concepts Document provides a basis for the mutual understanding between the users and the designers of the MIDACS, including the requirements, operating environment, external interfaces, and development plan. In defining the concepts and scope of the system, how the MIDACS will operate as an element of the Earth Observing System (EOS) within the EosDIS environment is described. This version follows an earlier release of a preliminary draft version. The individual operations concepts for planning and scheduling, control and monitoring, data acquisition and processing, calibration and validation, data archive and distribution, and user access do not yet fully represent the requirements of the data system needed to achieve the scientific objectives of the MODIS instruments and science teams. The teams are not yet formed; however, it is possible to develop the operations concepts based on the present concept of EosDIS, the level 1 and level 2 Functional Requirements Documents, and through interviews and meetings with key members of the scientific community. The operations concepts were exercised through the application of representative scenarios.

The management approach to the NASA space station definition studies at the Manned Spacecraft Center

NASA Technical Reports Server (NTRS)

Heberlig, J. C.

1972-01-01

The overall management approach to the NASA Phase B definition studies for space stations, which were initiated in September 1969 and completed in July 1972, is reviewed with particular emphasis placed on the management approach used by the Manned Spacecraft Center. The internal working organizations of the Manned Spacecraft Center and its prime contractor, North American Rockwell, are delineated along with the interfacing techniques used for the joint Government and industry study. Working interfaces with other NASA centers, industry, and Government agencies are briefly highlighted. The controlling documentation for the study (such as guidelines and constraints, bibliography, and key personnel) is reviewed. The historical background and content of the experiment program prepared for use in this Phase B study are outlined and management concepts that may be considered for future programs are proposed.

Low-G fluid behavior technology summaries

NASA Technical Reports Server (NTRS)

Stark, J. A.; Bradshaw, R. D.; Blatt, M. H.

1974-01-01

This report presents a summarization and categorization of the pertinent literature associated with low-g fluid behavior technology. Initially a literature search was conducted to obtain pertinent documents for review. Reports determined to be of primary significance are summarized in detail. Each summary, where applicable, consists of; (1) report identification, (2) objective(s) of the work, (3) description of pertinent work performed, (4) major results, and (5) comments of the reviewer (GD/C). Pertinent figures are presented on a single facing page separate from the text. Specific areas covered are; interface configuration, interface stability, natural frequency and damping, liquid reorientation, bubbles and droplets, fluid inflow, fluid outflow, convection, boiling and condensation heat transfer, venting effects, and fluid properties. Reports which were reviewed and not summarized, along with reasons for not summarizing, are also listed. Cryogenic thermal control and fluid management systems technology are presented.

Mid Infrared Instrument cooler subsystem test facility overview

NASA Astrophysics Data System (ADS)

Moore, B.; Zan, J.; Hannah, B.; Chui, T.; Penanen, K.; Weilert, M.

2017-12-01

The Cryocooler for the Mid Infrared Instrument (MIRI) on the James Webb Space Telescope (JWST) provides cooling at 6.2K on the instrument interface. The cooler system design has been incrementally documented in previous publications [1][2][3][4][5]. It has components that traverse three primary thermal regions on JWST: Region 1, approximated by 40K; Region 2, approximated by 100K; and Region 3, which is at the allowable flight temperatures for the spacecraft bus. However, there are several sub-regions that exist in the transition between primary regions and at the heat reject interfaces of the Cooler Compressor Assembly (CCA) and Cooler Control Electronics Assembly (CCEA). The design and performance of the test facility to provide a flight representative thermal environment for acceptance testing and characterization of the complete MIRI cooler subsystem are presented.

Information visualization: Beyond traditional engineering

NASA Technical Reports Server (NTRS)

Thomas, James J.

1995-01-01

This presentation addresses a different aspect of the human-computer interface; specifically the human-information interface. This interface will be dominated by an emerging technology called Information Visualization (IV). IV goes beyond the traditional views of computer graphics, CADS, and enables new approaches for engineering. IV specifically must visualize text, documents, sound, images, and video in such a way that the human can rapidly interact with and understand the content structure of information entities. IV is the interactive visual interface between humans and their information resources.

ooi: OpenStack OCCI interface

NASA Astrophysics Data System (ADS)

López García, Álvaro; Fernández del Castillo, Enol; Orviz Fernández, Pablo

In this document we present an implementation of the Open Grid Forum's Open Cloud Computing Interface (OCCI) for OpenStack, namely ooi (Openstack occi interface, 2015) [1]. OCCI is an open standard for management tasks over cloud resources, focused on interoperability, portability and integration. ooi aims to implement this open interface for the OpenStack cloud middleware, promoting interoperability with other OCCI-enabled cloud management frameworks and infrastructures. ooi focuses on being non-invasive with a vanilla OpenStack installation, not tied to a particular OpenStack release version.

Staggered-grid finite-difference acoustic modeling with the Time-Domain Atmospheric Acoustic Propagation Suite (TDAAPS).

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

Aldridge, David Franklin; Collier, Sandra L.; Marlin, David H.

2005-05-01

This document is intended to serve as a users guide for the time-domain atmospheric acoustic propagation suite (TDAAPS) program developed as part of the Department of Defense High-Performance Modernization Office (HPCMP) Common High-Performance Computing Scalable Software Initiative (CHSSI). TDAAPS performs staggered-grid finite-difference modeling of the acoustic velocity-pressure system with the incorporation of spatially inhomogeneous winds. Wherever practical the control structure of the codes are written in C++ using an object oriented design. Sections of code where a large number of calculations are required are written in C or F77 in order to enable better compiler optimization of these sections. Themore » TDAAPS program conforms to a UNIX style calling interface. Most of the actions of the codes are controlled by adding flags to the invoking command line. This document presents a large number of examples and provides new users with the necessary background to perform acoustic modeling with TDAAPS.« less

How to Create, Modify, and Interface Aspen In-House and User Databanks for System Configuration 1:

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

Camp, D W

2000-10-27

The goal of this document is to provide detailed instructions to create, modify, interface, and test Aspen User and In-House databanks with minimal frustration. The level of instructions are aimed at a novice Aspen Plus simulation user who is neither a programming nor computer-system expert. The instructions are tailored to Version 10.1 of Aspen Plus and the specific computing configuration summarized in the Title of this document and detailed in Section 2. Many details of setting up databanks depend on the computing environment specifics, such as the machines, operating systems, command languages, directory structures, inter-computer communications software, the version ofmore » the Aspen Engine and Graphical User Interface (GUI), and the directory structure of how these were installed.« less

A history of chagas disease transmission, control, and re-emergence in peri-rural La Joya, Peru.

PubMed

Delgado, Stephen; Castillo Neyra, Ricardo; Quispe Machaca, Víctor R; Ancca Juárez, Jenny; Chou Chu, Lily; Verastegui, Manuela Renee; Moscoso Apaza, Giovanna M; Bocángel, César D; Tustin, Aaron W; Sterling, Charles R; Comrie, Andrew C; Náquira, César; Cornejo del Carpio, Juan G; Gilman, Robert H; Bern, Caryn; Levy, Michael Z

2011-02-22

The history of Chagas disease control in Peru and many other nations is marked by scattered and poorly documented vector control campaigns. The complexities of human migration and sporadic control campaigns complicate evaluation of the burden of Chagas disease and dynamics of Trypanosoma cruzi transmission. We conducted a cross-sectional serological and entomological study to evaluate temporal and spatial patterns of T. cruzi transmission in a peri-rural region of La Joya, Peru. We use a multivariate catalytic model and Bayesian methods to estimate incidence of infection over time and thereby elucidate the complex history of transmission in the area. Of 1,333 study participants, 101 (7.6%; 95% CI: 6.2-9.0%) were confirmed T. cruzi seropositive. Spatial clustering of parasitic infection was found in vector insects, but not in human cases. Expanded catalytic models suggest that transmission was interrupted in the study area in 1996 (95% credible interval: 1991-2000), with a resultant decline in the average annual incidence of infection from 0.9% (95% credible interval: 0.6-1.3%) to 0.1% (95% credible interval: 0.005-0.3%). Through a search of archival newspaper reports, we uncovered documentation of a 1995 vector control campaign, and thereby independently validated the model estimates. High levels of T. cruzi transmission had been ongoing in peri-rural La Joya prior to interruption of parasite transmission through a little-documented vector control campaign in 1995. Despite the efficacy of the 1995 control campaign, T. cruzi was rapidly reemerging in vector populations in La Joya, emphasizing the need for continuing surveillance and control at the rural-urban interface.

A History of Chagas Disease Transmission, Control, and Re-Emergence in Peri-Rural La Joya, Peru

PubMed Central

Delgado, Stephen; Castillo Neyra, Ricardo; Quispe Machaca, Víctor R.; Ancca Juárez, Jenny; Chou Chu, Lily; Verastegui, Manuela Renee; Moscoso Apaza, Giovanna M.; Bocángel, César D.; Tustin, Aaron W.; Sterling, Charles R.; Comrie, Andrew C.; Náquira, César; Cornejo del Carpio, Juan G.; Gilman, Robert H.; Bern, Caryn; Levy, Michael Z.

2011-01-01

Background The history of Chagas disease control in Peru and many other nations is marked by scattered and poorly documented vector control campaigns. The complexities of human migration and sporadic control campaigns complicate evaluation of the burden of Chagas disease and dynamics of Trypanosoma cruzi transmission. Methodology/Principal Findings We conducted a cross-sectional serological and entomological study to evaluate temporal and spatial patterns of T. cruzi transmission in a peri-rural region of La Joya, Peru. We use a multivariate catalytic model and Bayesian methods to estimate incidence of infection over time and thereby elucidate the complex history of transmission in the area. Of 1,333 study participants, 101 (7.6%; 95% CI: 6.2–9.0%) were confirmed T. cruzi seropositive. Spatial clustering of parasitic infection was found in vector insects, but not in human cases. Expanded catalytic models suggest that transmission was interrupted in the study area in 1996 (95% credible interval: 1991–2000), with a resultant decline in the average annual incidence of infection from 0.9% (95% credible interval: 0.6–1.3%) to 0.1% (95% credible interval: 0.005–0.3%). Through a search of archival newspaper reports, we uncovered documentation of a 1995 vector control campaign, and thereby independently validated the model estimates. Conclusions/Significance High levels of T. cruzi transmission had been ongoing in peri-rural La Joya prior to interruption of parasite transmission through a little-documented vector control campaign in 1995. Despite the efficacy of the 1995 control campaign, T. cruzi was rapidly reemerging in vector populations in La Joya, emphasizing the need for continuing surveillance and control at the rural-urban interface. PMID:21364970

Implementation of Information Management System for Radiation Safety of Personnel at the Russian Northwest Center for Radioactive Waste Management 'SevRAO' - 13131

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

Chizhov, K.; Simakov, A.; Seregin, V.

2013-07-01

The report is an overview of the information-analytical system designed to assure radiation safety of workers. The system was implemented in the Northwest Radioactive Waste Management Center 'SevRAO' (which is a branch of the Federal State Unitary Enterprise 'Radioactive Waste Management Enterprise RosRAO'). The center is located in the Northwest Russia. In respect to 'SevRAO', the Federal Medical-Biological Agency is the regulatory body, which deals with issues of radiation control. The main document to regulate radiation control is 'Reference levels of radiation factors in radioactive wastes management center'. This document contains about 250 parameters. We have developed a software toolmore » to simplify control of these parameters. The software includes: input interface, the database, dose calculating module and analytical block. Input interface is used to enter radiation environment data. Dose calculating module calculates the dose on the route. Analytical block optimizes and analyzes radiation situation maps. Much attention is paid to the GUI and graphical representation of results. The operator can enter the route at the industrial site or watch the fluctuations of the dose rate field on the map. Most of the results are presented in a visual form. Here we present some analytical tasks, such as comparison of the dose rate in some point with control levels at this point, to be solved for the purpose of radiation safety control. The program helps to identify points making the largest contribution to the collective dose of the personnel. The tool can automatically calculate the route with the lowest dose, compare and choose the best route. The program uses several options to visualize the radiation environment at the industrial site. This system will be useful for radiation monitoring services during the operation, planning of works and development of scenarios. The paper presents some applications of this system on real data over three years - from March 2009 to February 2012. (authors)« less

Title V Interface Issues

EPA Pesticide Factsheets

This document may be of assistance in applying the Title V air operating permit regulations. This document is part of the Title V Policy and Guidance Database available at www2.epa.gov/title-v-operating-permits/title-v-operating-permit-policy-and-guidance-document-index. Some documents in the database are a scanned or retyped version of a paper photocopy of the original. Although we have taken considerable effort to quality assure the documents, some may contain typographical errors. Contact the office that issued the document if you need a copy of the original.

Title IV-Title V Interface Guidance for States

EPA Pesticide Factsheets

This document may be of assistance in applying the Title V air operating permit regulations. This document is part of the Title V Policy and Guidance Database available at www2.epa.gov/title-v-operating-permits/title-v-operating-permit-policy-and-guidance-document-index. Some documents in the database are a scanned or retyped version of a paper photocopy of the original. Although we have taken considerable effort to quality assure the documents, some may contain typographical errors. Contact the office that issued the document if you need a copy of the original.

An evaluation of the documented requirements of the SSP UIL and a review of commercial software packages for the development and testing of UIL prototypes

NASA Technical Reports Server (NTRS)

Gill, Esther Naomi

1986-01-01

A review was conducted of software packages currently on the market which might be integrated with the interface language and aid in reaching the objectives of customization, standardization, transparency, reliability, maintainability, language substitutions, expandability, portability, and flexibility. Recommendations are given for best choices in hardware and software acquisition for inhouse testing of these possible integrations. Software acquisition in the line of tools to aid expert-system development and/or novice program development, artificial intelligent voice technology and touch screen or joystick or mouse utilization as well as networking were recommended. Other recommendations concerned using the language Ada for the user interface language shell because of its high level of standardization, structure, and ability to accept and execute programs written in other programming languages, its DOD ownership and control, and keeping the user interface language simple so that multiples of users will find the commercialization of space within their realm of possibility which is, after all, the purpose of the Space Station.

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.

Rotational fluid flow experiment: WPI/MITRE advanced space design GASCAN 2

NASA Technical Reports Server (NTRS)

Daly, Walter F.; Harr, Lee; Paduano, Rocco; Yee, Tony; Eubbani, Eddy; Delprado, Jaime; Khanna, Ajay

1991-01-01

The design and implementation is examined of an electro-mechanical system for studying vortex behavior in a microgravity environment. Most of the existing equipment was revised and redesigned as necessary. Emphasis was placed on the documentation and integration of the mechanical and electrical subsystems. Project results include the reconfiguration and thorough testing of all the hardware subsystems, the implementation of an infrared gas entrainment detector, new signal processing circuitry for the ultrasonic fluid circulation device, improved prototype interface circuits, and software for overall control of experiment design operation.

ANOPP programmer's reference manual for the executive System. [aircraft noise prediction program

NASA Technical Reports Server (NTRS)

Gillian, R. E.; Brown, C. G.; Bartlett, R. W.; Baucom, P. H.

1977-01-01

Documentation for the Aircraft Noise Prediction Program as of release level 01/00/00 is presented in a manual designed for programmers having a need for understanding the internal design and logical concepts of the executive system software. Emphasis is placed on providing sufficient information to modify the system for enhancements or error correction. The ANOPP executive system includes software related to operating system interface, executive control, and data base management for the Aircraft Noise Prediction Program. It is written in Fortran IV for use on CDC Cyber series of computers.

4MOST systems engineering: from conceptual design to preliminary design review

NASA Astrophysics Data System (ADS)

Bellido-Tirado, Olga; Frey, Steffen; Barden, Samuel C.; Brynnel, Joar; Giannone, Domenico; Haynes, Roger; de Jong, Roelof S.; Phillips, Daniel; Schnurr, Olivier; Walcher, Jakob; Winkler, Roland

2016-08-01

The 4MOST Facility is a high-multiplex, wide-field, brief-fed spectrograph system for the ESO VISTA telescope. It aims to create a world-class spectroscopic survey facility unique in its combination of wide-field multiplex, spectral resolution, spectral coverage, and sensitivity. At the end of 2014, after a successful concept optimization design phase, 4MOST entered into its Preliminary Design Phase. Here we present the process and tools adopted during the Preliminary Design Phase to define the subsystems specifications, coordinate the interface control documents and draft the system verification procedures.

Physiology of chimpanzees in orbit. Part 2: Interface document

NASA Technical Reports Server (NTRS)

Firstenberg, A.

1972-01-01

Interface requirements are presented for the design and development of an earth orbiting experiment to be known as POCO, Physiology of Chimpanzees in Orbit. The POCO experiment may be designed to operate within an orbiting space station (provided artificial gravity measures are not employed), a Saturn 4-B workshop, an Apollo command module or service module, a Saturn-1B spacecraft LM adapter, or aboard one of the presently conceived appendages connected by an umbilical to a space station. This document sets forth the experiment definition and requirements and describes the hardware under development to accomplish these objectives.

Payload/cargo processing at the launch site

NASA Technical Reports Server (NTRS)

Ragusa, J. M.

1983-01-01

Payload processing at Kennedy Space Center is described, with emphasis on payload contamination control. Support requirements are established after documentation of the payload. The processing facilities feature enclosed, environmentally controlled conditions, with account taken of the weather conditions, door openings, accessing the payload, industrial activities, and energy conservation. Apparatus are also available for purges after Orbiter landing. The payloads are divided into horizontal, vertical, mixed, and life sciences and Getaway Special categories, which determines the processing route through the facilities. A canister/transport system features sealed containers for moving payloads from one facility building to another. All payloads are exposed to complete Orbiter bay interface checkouts in a simulator before actually being mounted in the bay.

Skylab Saturn 1B flight manual

NASA Technical Reports Server (NTRS)

1972-01-01

A Saturn 1B Flight Manual provides launch vehicle systems descriptions and predicted performance data for the Skylab missions. Vehicle SL-2 (SA-206) is the baseline for this manual; but, as a result of the great similarity, the material is representative of SL-3 and SL-4 launch vehicles, also. The Flight Manual is not a control document but is intended primarily as an aid to astronauts who are training for Skylab missions. In order to provide a comprehensive reference for that purpose, the manual also contains descriptions of the ground support interfaces, prelaunch operations, and emergency procedures. Mission variables and constraints are summarized, and mission control monitoring and data flow during launch preparation and flight are discussed.

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

Workers in SSPF monitor Multi-Equipment Interface Test.

NASA Technical Reports Server (NTRS)

2000-01-01

Workers in the Space Station Processing Facility control room check documentation during a Multi-Equipment Interface Test (MEIT) in the U.S. Lab Destiny. Members of the STS-98 crew are taking part in the MEIT checking out some of the equipment in the Lab. During the STS-98 mission, the crew will install the Lab on the station during a series of three space walks. The crew comprises five members: Commander Kenneth D. Cockrell, Pilot Mark L. Polansky, and Mission Specialists Robert L. Curbeam Jr., Thomas D. Jones (Ph.D.) and Marsha S. Ivins. The mission will provide the station with science research facilities and expand its power, life support and control capabilities. The U.S. Laboratory Module continues a long tradition of microgravity materials research, first conducted by Skylab and later Shuttle and Spacelab missions. Destiny is expected to be a major feature in future research, providing facilities for biotechnology, fluid physics, combustion, and life sciences research. The Lab is planned for launch aboard Space Shuttle Atlantis on the sixth ISS flight, currently targeted no earlier than Aug. 19, 2000.

ProXL (Protein Cross-Linking Database): A Platform for Analysis, Visualization, and Sharing of Protein Cross-Linking Mass Spectrometry Data

PubMed Central

2016-01-01

ProXL is a Web application and accompanying database designed for sharing, visualizing, and analyzing bottom-up protein cross-linking mass spectrometry data with an emphasis on structural analysis and quality control. ProXL is designed to be independent of any particular software pipeline. The import process is simplified by the use of the ProXL XML data format, which shields developers of data importers from the relative complexity of the relational database schema. The database and Web interfaces function equally well for any software pipeline and allow data from disparate pipelines to be merged and contrasted. ProXL includes robust public and private data sharing capabilities, including a project-based interface designed to ensure security and facilitate collaboration among multiple researchers. ProXL provides multiple interactive and highly dynamic data visualizations that facilitate structural-based analysis of the observed cross-links as well as quality control. ProXL is open-source, well-documented, and freely available at https://github.com/yeastrc/proxl-web-app. PMID:27302480

Study of the Alsys implementation of the Catalogue of Interface Features and Options for the Ada language for 80386 Unix

NASA Technical Reports Server (NTRS)

Gibson, James S.; Barnes, Michael J.; Ostermiller, Daniel L.

1993-01-01

A set of programs was written to test the functionality and performance of the Alsys Ada implementation of the Catalogue of Interface Features and Options (CIFO), a set of optional Ada packages for real-time applications. No problems were found with the task id, preemption control, or shared-data packages. Minor problems were found with the dispatching control, dynamic priority, events, non-waiting entry call, semaphore, and scheduling packages. The Alsys implementation is derived mostly from Release 2 of the CIFO standard, but includes some of the features of Release 3 and some modifications unique to Alsys. Performance measurements show that the semaphore and shared-data features are an order-of-magnitude faster than the same mechanisms using an Ada rendezvous. The non-waiting entry call is slightly faster than a standard rendezvous. The existence of errors in the implementation, the incompleteness of the documentation from the published standard impair the usefulness of this implementation. Despite those short-comings, the Alsys CIFO implementation might be of value in the development of real-time applications.

ProXL (Protein Cross-Linking Database): A Platform for Analysis, Visualization, and Sharing of Protein Cross-Linking Mass Spectrometry Data.

PubMed

Riffle, Michael; Jaschob, Daniel; Zelter, Alex; Davis, Trisha N

2016-08-05

ProXL is a Web application and accompanying database designed for sharing, visualizing, and analyzing bottom-up protein cross-linking mass spectrometry data with an emphasis on structural analysis and quality control. ProXL is designed to be independent of any particular software pipeline. The import process is simplified by the use of the ProXL XML data format, which shields developers of data importers from the relative complexity of the relational database schema. The database and Web interfaces function equally well for any software pipeline and allow data from disparate pipelines to be merged and contrasted. ProXL includes robust public and private data sharing capabilities, including a project-based interface designed to ensure security and facilitate collaboration among multiple researchers. ProXL provides multiple interactive and highly dynamic data visualizations that facilitate structural-based analysis of the observed cross-links as well as quality control. ProXL is open-source, well-documented, and freely available at https://github.com/yeastrc/proxl-web-app .

Thermal cycling fatigue of organic thermal interface materials using a thermal-displacement measurement technique

NASA Astrophysics Data System (ADS)

Steill, Jason Scott

The long term reliability of polymer-based thermal interface materials (TIM) is essential for modern electronic packages which require robust thermal management. The challenge for today's materials scientists and engineers is to maximize the heat flow from integrated circuits through a TIM and out the heat sink. Thermal cycling of the electronic package and non-uniformity in the heat flux with respect to the plan area can lead to void formation and delamination which re-introduces inefficient heat transfer. Measurement and understanding at the nano-scale is essential for TIM development. Finding and documenting the evolution of the defects is dependent upon a full understanding of the thermal probes response to changing environmental conditions and the effects of probe usage. The response of the thermal-displacement measurement technique was dominated by changes to the environment. Accurate measurement of the thermal performance was hindered by the inability to create a model system and control the operating conditions. This research highlights the need for continued study into the probe's thermal and mechanical response using tightly controlled test conditions.

Motivation and Design of the Sirocco Storage System Version 1.0.

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

Curry, Matthew Leon; Ward, H. Lee; Danielson, Geoffrey Charles

Sirocco is a massively parallel, high performance storage system for the exascale era. It emphasizes client-to-client coordination, low server-side coupling, and free data movement to improve resilience and performance. Its architecture is inspired by peer-to-peer and victim- cache architectures. By leveraging these ideas, Sirocco natively supports several media types, including RAM, flash, disk, and archival storage, with automatic migration between levels. Sirocco also includes storage interfaces and support that are more advanced than typical block storage. Sirocco enables clients to efficiently use key-value storage or block-based storage with the same interface. It also provides several levels of transactional data updatesmore » within a single storage command, including full ACID-compliant updates. This transaction support extends to updating several objects within a single transaction. Further support is provided for con- currency control, enabling greater performance for workloads while providing safe concurrent modification. By pioneering these and other technologies and techniques in the storage system, Sirocco is poised to fulfill a need for a massively scalable, write-optimized storage system for exascale systems. This is version 1.0 of a document reflecting the current and planned state of Sirocco. Further versions of this document will be accessible at http://www.cs.sandia.gov/Scalable_IO/ sirocco .« less

Formulation of consumables management models. Consumables flight planning worksheet utilization

NASA Technical Reports Server (NTRS)

Newman, C. M.

1977-01-01

The updated and reformatted consumables flight planning worksheet is documented. An instruction set for applying the worksheet, and a sample application of the worksheet is disclosed. The particular application is for the STS interfacing with sortie payloads and typifies the interfacing of the delivery system and payloads.

A generic, web-based clinical information system architecture using HL7 CDA: successful implementation in dermatological routine care.

PubMed

Schuler, Thilo; Boeker, Martin; Klar, Rüdiger; Müller, Marcel

2007-01-01

The requirements of highly specialized clinical domains are often underrepresented in hospital information systems (HIS). Common consequences are that documentation remains to be paper-based or external systems with insufficient HIS integration are used. This paper presents a solution to overcome this deficiency in the form of a generic framework based on the HL7 Clinical Document Architecture. The central architectural idea is the definition of customized forms using a schema-controlled XML language. These flexible form definitions drive the user interface, the data storage, and standardized data exchange. A successful proof-of-concept application in a dermatologic outpatient wound care department has been implemented, and is well accepted by the clinicians. Our work with HL7 CDA revealed the need for further practical research in the health information standards realm.

MPI-IO: A Parallel File I/O Interface for MPI Version 0.3

NASA Technical Reports Server (NTRS)

Corbett, Peter; Feitelson, Dror; Hsu, Yarsun; Prost, Jean-Pierre; Snir, Marc; Fineberg, Sam; Nitzberg, Bill; Traversat, Bernard; Wong, Parkson

1995-01-01

Thanks to MPI [9], writing portable message passing parallel programs is almost a reality. One of the remaining problems is file I/0. Although parallel file systems support similar interfaces, the lack of a standard makes developing a truly portable program impossible. Further, the closest thing to a standard, the UNIX file interface, is ill-suited to parallel computing. Working together, IBM Research and NASA Ames have drafted MPI-I0, a proposal to address the portable parallel I/0 problem. In a nutshell, this proposal is based on the idea that I/0 can be modeled as message passing: writing to a file is like sending a message, and reading from a file is like receiving a message. MPI-IO intends to leverage the relatively wide acceptance of the MPI interface in order to create a similar I/0 interface. The above approach can be materialized in different ways. The current proposal represents the result of extensive discussions (and arguments), but is by no means finished. Many changes can be expected as additional participants join the effort to define an interface for portable I/0. This document is organized as follows. The remainder of this section includes a discussion of some issues that have shaped the style of the interface. Section 2 presents an overview of MPI-IO as it is currently defined. It specifies what the interface currently supports and states what would need to be added to the current proposal to make the interface more complete and robust. The next seven sections contain the interface definition itself. Section 3 presents definitions and conventions. Section 4 contains functions for file control, most notably open. Section 5 includes functions for independent I/O, both blocking and nonblocking. Section 6 includes functions for collective I/O, both blocking and nonblocking. Section 7 presents functions to support system-maintained file pointers, and shared file pointers. Section 8 presents constructors that can be used to define useful filetypes (the role of filetypes is explained in Section 2 below). Section 9 presents how the error handling mechanism of MPI is supported by the MPI-IO interface. All this is followed by a set of appendices, which contain information about issues that have not been totally resolved yet, and about design considerations. The reader can find there the motivation behind some of our design choices. More information on this would definitely be welcome and will be included in a further release of this document. The first appendix contains a description of MPI-I0's 'hints' structure which is used when opening a file. Appendix B is a discussion of various issues in the support for file pointers. Appendix C explains what we mean in talking about atomic access. Appendix D provides detailed examples of filetype constructors, and Appendix E contains a collection of arguments for and against various design decisions.

The Development of Cockpit Display and Alerting Concepts for Interval Management (IM) in a Near-Term Environment

NASA Technical Reports Server (NTRS)

Baxley, Brian T.; Shay, Richard F.; Swieringa, Kurt A.

2014-01-01

The National Aeronautics and Space Administration (NASA) Langley Research Center (LaRC) Interval Management (IM) research team has conducted a wide spectrum of work in the recent past, ranging from development and testing of the concept, procedures, and algorithm. This document focuses on the research and evaluation of the IM pilot interfaces, cockpit displays, indications, and alerting concepts for conducting IM spacing operations. The research team incorporated knowledge of human factors research, industry standards for cockpit design, and cockpit design philosophies to develop innovative displays for conducting these spacing operations. The research team also conducted a series of human-in-the-loop (HITL) experiments with commercial pilots and air traffic controllers, in as realistic a high-density arrival operation environment as could be simulated, to evaluate the spacing guidance display features and interface requirements needed to conduct spacing operations.

FreeSASA: An open source C library for solvent accessible surface area calculations.

PubMed

Mitternacht, Simon

2016-01-01

Calculating solvent accessible surface areas (SASA) is a run-of-the-mill calculation in structural biology. Although there are many programs available for this calculation, there are no free-standing, open-source tools designed for easy tool-chain integration. FreeSASA is an open source C library for SASA calculations that provides both command-line and Python interfaces in addition to its C API. The library implements both Lee and Richards' and Shrake and Rupley's approximations, and is highly configurable to allow the user to control molecular parameters, accuracy and output granularity. It only depends on standard C libraries and should therefore be easy to compile and install on any platform. The library is well-documented, stable and efficient. The command-line interface can easily replace closed source legacy programs, with comparable or better accuracy and speed, and with some added functionality.

Sampling and Control Circuit Board for an Inertial Measurement Unit

NASA Technical Reports Server (NTRS)

Chelmins, David; Powis, Rick

2012-01-01

Spacesuit navigation is one component of NASA s efforts to return humans to the Moon. Studies performed at the NASA Glenn Research Center (GRC) considered various navigation technologies and filtering approaches to enable navigation on the lunar surface. As part of this effort, microelectromechanical systems (MEMS) inertial measurement units (IMUs) were studied to determine if they could supplement a radiometric infrastructure. MEMS IMUs were included in the Lunar Extra-Vehicular Activity Crewmember Location Determination System (LECLDS) testbed during NASA s annual Desert Research and Technology Studies (D-RATS) event in 2009 and 2010. The testbed included one IMU in 2009 and three IMUs in 2010, along with a custom circuit board interfacing between the navigation processor and each IMU. The board was revised for the 2010 test, and this paper documents the design details of this latest revision of the interface circuit board and firmware.

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.

LSST communications middleware implementation

NASA Astrophysics Data System (ADS)

Mills, Dave; Schumacher, German; Lotz, Paul

2016-07-01

The LSST communications middleware is based on a set of software abstractions; which provide standard interfaces for common communications services. The observatory requires communication between diverse subsystems, implemented by different contractors, and comprehensive archiving of subsystem status data. The Service Abstraction Layer (SAL) is implemented using open source packages that implement open standards of DDS (Data Distribution Service1) for data communication, and SQL (Standard Query Language) for database access. For every subsystem, abstractions for each of the Telemetry datastreams, along with Command/Response and Events, have been agreed with the appropriate component vendor (such as Dome, TMA, Hexapod), and captured in ICD's (Interface Control Documents).The OpenSplice (Prismtech) Community Edition of DDS provides an LGPL licensed distribution which may be freely redistributed. The availability of the full source code provides assurances that the project will be able to maintain it over the full 10 year survey, independent of the fortunes of the original providers.

Monitoring of Water and Contaminant Migration at the Groundwater-Surface Water Interface

DTIC Science & Technology

2008-08-01

seepage is occurring in a freshwater lake environment and to map the lateral extent of any subsurface contamination at the groundwater –surface water ...and Contaminant Migration at the Groundwater -Surface Water Interface August 2008 Report Documentation Page Form ApprovedOMB No. 0704-0188 Public...4. TITLE AND SUBTITLE Monitoring of Water and Contaminant Migration at the Groundwater -Surface Water Interface 5a. CONTRACT NUMBER 5b. GRANT NUMBER

Instrument constraints and interface specifications. Earth Observatory Satellite system definition study (EOS)

NASA Technical Reports Server (NTRS)

1974-01-01

The equipment specifications for the thematic mapper and high resolution pointable imager for use on the Earth Observatory Satellite (EOS) are presented. The interface requirements of the systems are defined. The interface requirements are extracted from the equipment specifications and are intended as a summary to be used by the system and spacecraft designer. The appropriate documentation from which the specifications of the equipment are established are identified.

Semi-automated sorting using holographic optical tweezers remotely controlled by eye/hand tracking camera

NASA Astrophysics Data System (ADS)

Tomori, Zoltan; Keša, Peter; Nikorovič, Matej; Kaůka, Jan; Zemánek, Pavel

2016-12-01

We proposed the improved control software for the holographic optical tweezers (HOT) proper for simple semi-automated sorting. The controller receives data from both the human interface sensors and the HOT microscope camera and processes them. As a result, the new positions of active laser traps are calculated, packed into the network format and sent to the remote HOT. Using the photo-polymerization technique, we created a sorting container consisting of two parallel horizontal walls where one wall contains "gates" representing a place where the trapped particle enters into the container. The positions of particles and gates are obtained by image analysis technique which can be exploited to achieve the higher level of automation. Sorting is documented on computer game simulation and the real experiment.

TkPl_SU: An Open-source Perl Script Builder for Seismic Unix

NASA Astrophysics Data System (ADS)

Lorenzo, J. M.

2017-12-01

TkPl_SU (beta) is a graphical user interface (GUI) to select parameters for Seismic Unix (SU) modules. Seismic Unix (Stockwell, 1999) is a widely distributed free software package for processing seismic reflection and signal processing. Perl/Tk is a mature, well-documented and free object-oriented graphical user interface for Perl. In a classroom environment, shell scripting of SU modules engages students and helps focus on the theoretical limitations and strengths of signal processing. However, complex interactive processing stages, e.g., selection of optimal stacking velocities, killing bad data traces, or spectral analysis requires advanced flows beyond the scope of introductory classes. In a research setting, special functionality from other free seismic processing software such as SioSeis (UCSD-NSF) can be incorporated readily via an object-oriented style to programming. An object oriented approach is a first step toward efficient extensible programming of multi-step processes, and a simple GUI simplifies parameter selection and decision making. Currently, in TkPl_SU, Perl 5 packages wrap 19 of the most common SU modules that are used in teaching undergraduate and first-year graduate student classes (e.g., filtering, display, velocity analysis and stacking). Perl packages (classes) can advantageously add new functionality around each module and clarify parameter names for easier usage. For example, through the use of methods, packages can isolate the user from repetitive control structures, as well as replace the names of abbreviated parameters with self-describing names. Moose, an extension of the Perl 5 object system, greatly facilitates an object-oriented style. Perl wrappers are self-documenting via Perl programming document markup language.

Systems and methods for compensating for electrical converter nonlinearities

DOEpatents

Perisic, Milun; Ransom, Ray M.; Kajouke, Lateef A.

2013-06-18

Systems and methods are provided for delivering energy from an input interface to an output interface. An electrical system includes an input interface, an output interface, an energy conversion module coupled between the input interface and the output interface, and a control module. The control module determines a duty cycle control value for operating the energy conversion module to produce a desired voltage at the output interface. The control module determines an input power error at the input interface and adjusts the duty cycle control value in a manner that is influenced by the input power error, resulting in a compensated duty cycle control value. The control module operates switching elements of the energy conversion module to deliver energy to the output interface with a duty cycle that is influenced by the compensated duty cycle control value.

MODIS information, data and control system (MIDACS) level 2 functional requirements

NASA Technical Reports Server (NTRS)

Han, D.; Salomonson, V.; Ormsby, J.; Sharts, B.; Folta, D.; Ardanuy, P.; Mckay, A.; Hoyt, D.; Jaffin, S.; Vallette, B.

1988-01-01

The MODIS Information, Data and Control System (MIDACS) Level 2 Functional Requirements Document establishes the functional requirements for MIDACS and provides a basis for the mutual understanding between the users and the designers of the EosDIS, including the requirements, operating environment, external interfaces, and development plan. In defining the requirements and scope of the system, this document describes how MIDACS will operate as an element of the EOS within the EosDIS environment. This version of the Level 2 Requirements Document follows an earlier release of a preliminary draft version. The sections on functional and performance requirements do not yet fully represent the requirements of the data system needed to achieve the scientific objectives of the MODIS instruments and science teams. Indeed, the team members have not yet been selected and the team has not yet been formed; however, it has been possible to identify many relevant requirements based on the present concept of EosDIS and through interviews and meetings with key members of the scientific community. These requirements have been grouped by functional component of the data system, and by function within each component. These requirements have been merged with the complete set of Level 1 and Level 2 context diagrams, data flow diagrams, and data dictionary.

WASTE HANDLING BUILDING ELECTRICAL SYSTEM DESCRIPTION DOCUMENT

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

S.C. Khamamkar

2000-06-23

The Waste Handling Building Electrical System performs the function of receiving, distributing, transforming, monitoring, and controlling AC and DC power to all waste handling building electrical loads. The system distributes normal electrical power to support all loads that are within the Waste Handling Building (WHB). The system also generates and distributes emergency power to support designated emergency loads within the WHB within specified time limits. The system provides the capability to transfer between normal and emergency power. The system provides emergency power via independent and physically separated distribution feeds from the normal supply. The designated emergency electrical equipment will bemore » designed to operate during and after design basis events (DBEs). The system also provides lighting, grounding, and lightning protection for the Waste Handling Building. The system is located in the Waste Handling Building System. The system consists of a diesel generator, power distribution cables, transformers, switch gear, motor controllers, power panel boards, lighting panel boards, lighting equipment, lightning protection equipment, control cabling, and grounding system. Emergency power is generated with a diesel generator located in a QL-2 structure and connected to the QL-2 bus. The Waste Handling Building Electrical System distributes and controls primary power to acceptable industry standards, and with a dependability compatible with waste handling building reliability objectives for non-safety electrical loads. It also generates and distributes emergency power to the designated emergency loads. The Waste Handling Building Electrical System receives power from the Site Electrical Power System. The primary material handling power interfaces include the Carrier/Cask Handling System, Canister Transfer System, Assembly Transfer System, Waste Package Remediation System, and Disposal Container Handling Systems. The system interfaces with the MGR Operations Monitoring and Control System for supervisory monitoring and control signals. The system interfaces with all facility support loads such as heating, ventilation, and air conditioning, office, fire protection, monitoring and control, safeguards and security, and communications subsystems.« less

Integrated Application of Active Controls (IAAC) technology to an advanced subsonic transport project. ACT/Control/Guidance System study, volume 1

NASA Technical Reports Server (NTRS)

1982-01-01

The active control technology (ACT) control/guidance system task of the integrated application of active controls (IAAC) technology project within the NASA energy efficient transport program was documented. The air traffic environment of navigation and air traffic control systems and procedures were extrapolated. An approach to listing flight functions which will be performed by systems and crew of an ACT configured airplane of the 1990s, and a determination of function criticalities to safety of flight, are the basis of candidate integrated ACT/Control/Guidance System architecture. The system mechanizes five active control functions: pitch augmented stability, angle of attack limiting, lateral/directional augmented stability, gust load alleviation, and maneuver load control. The scope and requirements of a program for simulating the integrated ACT avionics and flight deck system, with pilot in the loop, are defined, system and crew interface elements are simulated, and mechanization is recommended. Relationships between system design and crew roles and procedures are evaluated.

Applying Human Factors Evaluation and Design Guidance to a Nuclear Power Plant Digital Control System

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

Thomas Ulrich; Ronald Boring; William Phoenix

2012-08-01

The United States (U.S.) nuclear industry, like similar process control industries, has moved toward upgrading its control rooms. The upgraded control rooms typically feature digital control system (DCS) displays embedded in the panels. These displays gather information from the system and represent that information on a single display surface. In this manner, the DCS combines many previously separate analog indicators and controls into a single digital display, whereby the operators can toggle between multiple windows to monitor and control different aspects of the plant. The design of the DCS depends on the function of the system it monitors, but revolvesmore » around presenting the information most germane to an operator at any point in time. DCSs require a carefully designed human system interface. This report centers on redesigning existing DCS displays for an example chemical volume control system (CVCS) at a U.S. nuclear power plant. The crucial nature of the CVCS, which controls coolant levels and boration in the primary system, requires a thorough human factors evaluation of its supporting DCS. The initial digital controls being developed for the DCSs tend to directly mimic the former analog controls. There are, however, unique operator interactions with a digital vs. analog interface, and the differences have not always been carefully factored in the translation of an analog interface to a replacement DCS. To ensure safety, efficiency, and usability of the emerging DCSs, a human factors usability evaluation was conducted on a CVCS DCS currently being used and refined at an existing U.S. nuclear power plant. Subject matter experts from process control engineering, software development, and human factors evaluated the DCS displays to document potential usability issues and propose design recommendations. The evaluation yielded 167 potential usability issues with the DCS. These issues should not be considered operator performance problems but rather opportunities identified by experts to improve upon the design of the DCS. A set of nine design recommendations was developed to address these potential issues. The design principles addressed the following areas: (1) color, (2) pop-up window structure, (3) navigation, (4) alarms, (5) process control diagram, (6) gestalt grouping, (7) typography, (8) terminology, and (9) data entry. Visuals illustrating the improved DCS displays accompany the design recommendations. These nine design principles serve as the starting point to a planned general DCS style guide that can be used across the U.S. nuclear industry to aid in the future design of effective DCS interfaces.« less

Migration of the ATLAS Metadata Interface (AMI) to Web 2.0 and cloud

NASA Astrophysics Data System (ADS)

Odier, J.; Albrand, S.; Fulachier, J.; Lambert, F.

2015-12-01

The ATLAS Metadata Interface (AMI), a mature application of more than 10 years of existence, is currently under adaptation to some recently available technologies. The web interfaces, which previously manipulated XML documents using XSL transformations, are being migrated to Asynchronous JavaScript (AJAX). Web development is considerably simplified by the introduction of a framework based on JQuery and Twitter Bootstrap. Finally, the AMI services are being migrated to an OpenStack cloud infrastructure.

An XML-based system for the flexible classification and retrieval of clinical practice guidelines.

PubMed Central

Ganslandt, T.; Mueller, M. L.; Krieglstein, C. F.; Senninger, N.; Prokosch, H. U.

2002-01-01

Beneficial effects of clinical practice guidelines (CPGs) have not yet reached expectations due to limited routine adoption. Electronic distribution and reminder systems have the potential to overcome implementation barriers. Existing electronic CPG repositories like the National Guideline Clearinghouse (NGC) provide individual access but lack standardized computer-readable interfaces necessary for automated guideline retrieval. The aim of this paper was to facilitate automated context-based selection and presentation of CPGs. Using attributes from the NGC classification scheme, an XML-based metadata repository was successfully implemented, providing document storage, classification and retrieval functionality. Semi-automated extraction of attributes was implemented for the import of XML guideline documents using XPath. A hospital information system interface was exemplarily implemented for diagnosis-based guideline invocation. Limitations of the implemented system are discussed and possible future work is outlined. Integration of standardized computer-readable search interfaces into existing CPG repositories is proposed. PMID:12463831

Does Interface Matter? A Study of Web Authoring and Editing by Inexperienced Web Writers

ERIC Educational Resources Information Center

Dick, Rodney F.

2006-01-01

This study explores the complicated nature of the interface as a mediational tool for inexperienced writers as they composed hypertext documents. Because technology can become so quickly and inextricably connected to people's everyday lives, it is essential to explore the effects on these technologies before they become invisible. Because…

Web-Based Interactive Electronic Technical Manual (IETM) Common User Interface Style Guide, Version 2.0

DTIC Science & Technology

2003-07-01

Technical Report WEB-BASED INTERACTIVE ELECTRONIC TECHNICAL MANUAL (IETM) COMMON USER INTERFACE STYLE GUIDE Version 2.0 – July 2003 by L. John Junod ...ACKNOWLEDGEMENTS The principal authors of this document were: John Junod – NSWC, Carderock Division, Phil Deuell – AMSEC LLC, Kathleen Moore

Interfacing Optical Document Scanners: Principles and Practical Considerations.

ERIC Educational Resources Information Center

Krus, David J.; Kodimer, Dennis

1987-01-01

Handlers for interfacing the ScanTron and 2700 Optical Mark Readers with the IBM AT/XT/PC and Tandy 2000/1000/3000 iAPX 88/186/286 based computers were described. Differences between programing an RS232C serial port using BIOS interrupts and directly addressing the Motorola 8550 ART microprocessor were discussed. (Author/LMO)

DETECTION OF A GROUND-WATER/SURFACE-WATER INTERFACE WITH DIRECT-PUSH EQUIPMENT

EPA Science Inventory

A ground-water/surface-water interface (GSI) was documented at the Thermo Chem CERCLA Site in Muskegon, MI via direct-push (DP) sampling. At that time, contaminated ground water flowed from the upland area of the site into the Black Creek floodplain. DP rods equipped with a 1.5...

Multiple network interface core apparatus and method

DOEpatents

Underwood, Keith D [Albuquerque, NM; Hemmert, Karl Scott [Albuquerque, NM

2011-04-26

A network interface controller and network interface control method comprising providing a single integrated circuit as a network interface controller and employing a plurality of network interface cores on the single integrated circuit.

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.

An Evaluation and Redesign of the Conflict Prediction and Trial Planning Planview Graphical User Interface

NASA Technical Reports Server (NTRS)

Laudeman, Irene V.; Brasil, Connie L.; Stassart, Philippe

1998-01-01

The Planview Graphical User Interface (PGUI) is the primary display of air traffic for the Conflict Prediction and Trial Planning, function of the Center TRACON Automation System. The PGUI displays air traffic information that assists the user in making decisions related to conflict detection, conflict resolution, and traffic flow management. The intent of this document is to outline the human factors issues related to the design of the conflict prediction and trial planning portions of the PGUI, document all human factors related design changes made to the PGUI from December 1996 to September 1997, and outline future plans for the ongoing PGUI design.

Developing an Interface to Order and Document Health Education Videos in the Electronic Health Record.

PubMed

Wojcik, Lauren

2015-01-01

Transitioning to electronic health records (EHRs) provides an opportunity for health care systems to integrate educational content available on interactive patient systems (IPS) with the medical documentation system. This column discusses how one hospital simplified providers' workflow by making it easier to order educational videos and ensure that completed education is documented within the medical record. Integrating the EHR and IPS streamlined the provision of patient education, improved documentation, and supported the organization in meeting core requirements for Meaningful Use.

MODIS Information, Data, and Control System (MIDACS) system specifications and conceptual design

NASA Technical Reports Server (NTRS)

Han, D.; Salomonson, V.; Ormsby, J.; Ardanuy, P.; Mckay, A.; Hoyt, D.; Jaffin, S.; Vallette, B.; Sharts, B.; Folta, D.

1988-01-01

The MODIS Information, Data, and Control System (MIDACS) Specifications and Conceptual Design Document discusses system level requirements, the overall operating environment in which requirements must be met, and a breakdown of MIDACS into component subsystems, which include the Instrument Support Terminal, the Instrument Control Center, the Team Member Computing Facility, the Central Data Handling Facility, and the Data Archive and Distribution System. The specifications include sizing estimates for the processing and storage capacities of each data system element, as well as traffic analyses of data flows between the elements internally, and also externally across the data system interfaces. The specifications for the data system, as well as for the individual planning and scheduling, control and monitoring, data acquisition and processing, calibration and validation, and data archive and distribution components, do not yet fully specify the data system in the complete manner needed to achieve the scientific objectives of the MODIS instruments and science teams. The teams have not yet been formed; however, it was possible to develop the specifications and conceptual design based on the present concept of EosDIS, the Level-1 and Level-2 Functional Requirements Documents, the Operations Concept, and through interviews and meetings with key members of the scientific community.

Improved usability of a multi-infusion setup using a centralized control interface: A task-based usability test

PubMed Central

Cnossen, Fokie; Dieperink, Willem; Bult, Wouter; de Smet, Anne Marie; Touw, Daan J.; Nijsten, Maarten W.

2017-01-01

The objective of this study was to assess the usability benefits of adding a bedside central control interface that controls all intravenous (IV) infusion pumps compared to the conventional individual control of multiple infusion pumps. Eighteen dedicated ICU nurses volunteered in a between-subjects task-based usability test. A newly developed central control interface was compared to conventional control of multiple infusion pumps in a simulated ICU setting. Task execution time, clicks, errors and questionnaire responses were evaluated. Overall the central control interface outperformed the conventional control in terms of fewer user actions (40±3 vs. 73±20 clicks, p<0.001) and fewer user errors (1±1 vs. 3±2 errors, p<0.05), with no difference in task execution times (421±108 vs. 406±119 seconds, not significant). Questionnaires indicated a significant preference for the central control interface. Despite being novice users of the central control interface, ICU nurses displayed improved performance with the central control interface compared to the conventional interface they were familiar with. We conclude that the new user interface has an overall better usability than the conventional interface. PMID:28800617

Improved usability of a multi-infusion setup using a centralized control interface: A task-based usability test.

PubMed

Doesburg, Frank; Cnossen, Fokie; Dieperink, Willem; Bult, Wouter; de Smet, Anne Marie; Touw, Daan J; Nijsten, Maarten W

2017-01-01

The objective of this study was to assess the usability benefits of adding a bedside central control interface that controls all intravenous (IV) infusion pumps compared to the conventional individual control of multiple infusion pumps. Eighteen dedicated ICU nurses volunteered in a between-subjects task-based usability test. A newly developed central control interface was compared to conventional control of multiple infusion pumps in a simulated ICU setting. Task execution time, clicks, errors and questionnaire responses were evaluated. Overall the central control interface outperformed the conventional control in terms of fewer user actions (40±3 vs. 73±20 clicks, p<0.001) and fewer user errors (1±1 vs. 3±2 errors, p<0.05), with no difference in task execution times (421±108 vs. 406±119 seconds, not significant). Questionnaires indicated a significant preference for the central control interface. Despite being novice users of the central control interface, ICU nurses displayed improved performance with the central control interface compared to the conventional interface they were familiar with. We conclude that the new user interface has an overall better usability than the conventional interface.

Family history assessment for colorectal cancer (CRC) risk analysis - comparison of diagram- and questionnaire-based web interfaces.

PubMed

Schultz, Michael; Seo, Steven Bohwan; Holt, Alec; Regenbrecht, Holger

2015-11-18

Colorectal cancer (CRC) has a high incidence, especially in New Zealand. The reasons for this are unknown. While most cancers develop sporadically, a positive family history, determined by the number and age at diagnosis of affected first and second degree relatives with CRC is one of the major factors, which may increase an individual's lifetime risk. Before a patient can be enrolled in a surveillance program a detailed assessment and documentation of the family history is important but time consuming and often inaccurate. The documentation is usually paper-based. Our aim was therefore to develop and validate the usability and efficacy of a web-based family history assessment tool for CRC suitable for the general population. The tool was also to calculate the risk and make a recommendation for surveillance. Two versions of an electronic assessment tool, diagram-based and questionnaire-based, were developed with the risk analysis and recommendations for surveillance based on the New Zealand Guidelines Group recommendations. Accuracy of our tool was tested prior to the study by comparing risk calculations based on family history by experienced gastroenterologists with the electronic assessment. The general public, visiting a local science fair were asked to use and comment on the usability of the two interfaces. Ninety people assessed and commented on the two interfaces. Both interfaces were effective in assessing the risk to develop CRC through their familial history for CRC. However, the questionnaire-based interface performed with significantly better satisfaction (p = 0.001) than the diagram-based interface. There was no difference in efficacy though. We conclude that a web-based questionnaire tool can assist in the accurate documentation and analysis of the family history relevant to determine the individual risk of CRC based on local guidelines. The calculator is now implemented and assessable through the web-page of a local charity for colorectal cancer awareness and integral part of the local general practitioners' e-referral system for colonic imaging.

Controllable Grid Interface Test System | Energy Systems Integration

Science.gov Websites

Facility | NREL Controllable Grid Interface Test System Controllable Grid Interface Test System NREL's controllable grid interface (CGI) test system can reduce certification testing time and costs grid interface is the first test facility in the United States that has fault simulation capabilities

AVCS Simulator Test Plan and Design Guide

NASA Technical Reports Server (NTRS)

Shelden, Stephen

2001-01-01

Internal document for communication of AVCS direction and documentation of simulator functionality. Discusses methods for AVCS simulation evaluation of pilot functions, implementation strategy of varying functional representation of pilot tasks (by instantiations of a base AVCS to reasonably approximate the interface of various vehicles -- e.g. Altair, GlobalHawk, etc.).

DocCube: Multi-Dimensional Visualization and Exploration of Large Document Sets.

ERIC Educational Resources Information Center

Mothe, Josiane; Chrisment, Claude; Dousset, Bernard; Alaux, Joel

2003-01-01

Describes a user interface that provides global visualizations of large document sets to help users formulate the query that corresponds to their information needs. Highlights include concept hierarchies that users can browse to specify and refine information needs; knowledge discovery in databases and texts; and multidimensional modeling.…

Automation of the CAS Document Delivery Service.

ERIC Educational Resources Information Center

Steensland, M. C.; Soukup, K. M.

1986-01-01

The automation of online order retrieval for Chemical Abstracts Service Document Delivery Service was accomplished by shifting to an order retrieval/dispatch process linked to a Unix network. The Unix-based environment, its terminal emulation, page-break, and user-friendly interface software, and later enhancements are reviewed. Resultant increase…

Biotea: RDFizing PubMed Central in support for the paper as an interface to the Web of Data

PubMed Central

2013-01-01

Background The World Wide Web has become a dissemination platform for scientific and non-scientific publications. However, most of the information remains locked up in discrete documents that are not always interconnected or machine-readable. The connectivity tissue provided by RDF technology has not yet been widely used to support the generation of self-describing, machine-readable documents. Results In this paper, we present our approach to the generation of self-describing machine-readable scholarly documents. We understand the scientific document as an entry point and interface to the Web of Data. We have semantically processed the full-text, open-access subset of PubMed Central. Our RDF model and resulting dataset make extensive use of existing ontologies and semantic enrichment services. We expose our model, services, prototype, and datasets at http://biotea.idiginfo.org/ Conclusions The semantic processing of biomedical literature presented in this paper embeds documents within the Web of Data and facilitates the execution of concept-based queries against the entire digital library. Our approach delivers a flexible and adaptable set of tools for metadata enrichment and semantic processing of biomedical documents. Our model delivers a semantically rich and highly interconnected dataset with self-describing content so that software can make effective use of it. PMID:23734622

Contamination control and cleanliness level integrity for the Space Shuttle Orbiter PLB, payloads and facilities at KSC

NASA Technical Reports Server (NTRS)

Bartelson, D.

1984-01-01

The PLB, its cargo, and payload canister must satisfy the cleanliness requirements of visual clean (VC) level 1, 2, 3, or special as stated in NASA document SN-C-0005A. The specific level of cleanliness is chosen by the payload bay customer for their mission. During orbiter turnaround processing at KSC, the payload bay is exposed to the environments of the Orbiter Processing Facility (OPF) and the Payload Changeout Room (PCR). In supportive response to the orbiter payload bay/facility interface, it is necessary that the facility environment be controlled and monitored to protect the cleanliness/environmental integrity of the payload bay and its cargo. Techniques used to meet environmental requirements during orbiter processing are introduced.

A practical guide to the Piccolo autopilot

NASA Astrophysics Data System (ADS)

Mornhinweg, Anton

In support of a UAV contract the Piccolo SL and Piccolo II autopilots were installed and operated on various aircraft. Numerous problems with the autopilot setup and analysis processes were found along with numerous problems with documentation and autopilot system information. Major areas of concern are identified along with objectives to eliminate the major areas of concern. Piccolo simulator vehicle gain calculations and Piccolo generation 2 version 2.1.4 control laws are reverse engineered. A complete modeling guide is created. Methods are developed to perform and analyze doublet maneuvers. A series of flight procedures are outlined that include methods for tuning gains. A series of MATLAB graphical user interfaces were created to analyze flight data and pertinent control loop data for gain tuning.

STS-35 ASTRO-1 telescopes documented in OV-102's payload bay (PLB)

NASA Image and Video Library

1990-12-10

STS035-13-008 (2-10 Dec. 1990) --- The various components of the Astro-1 payload are seen backdropped against the blue and white Earth in this 35mm scene photographed through Columbia's aft flight deck windows. Parts of the Hopkins Ultraviolet Telescope (HUT), Ultraviolet Imaging Telescope (UIT) and the Wisconsin Ultraviolet Photo-Polarimeter Experiment (WUPPE) are visible on the Spacelab Pallet in the foreground. The Broad Band X-Ray Telescope (BBXRT) is behind this pallet and is not visible in this scene. The smaller cylinder in the foreground is the "Igloo," which is a pressurized container housing the Command and Data Management System, which interfaces with the in-cabin controllers to control the Instrument Pointing System (IPS) and the telescopes.

TAE+ 5.1 - TRANSPORTABLE APPLICATIONS ENVIRONMENT PLUS, VERSION 5.1 (HP9000 SERIES 300/400 VERSION)

NASA Technical Reports Server (NTRS)

TAE SUPPORT OFFICE

1994-01-01

TAE (Transportable Applications Environment) Plus is an integrated, portable environment for developing and running interactive window, text, and graphical object-based application systems. The program allows both programmers and non-programmers to easily construct their own custom application interface and to move that interface and application to different machine environments. TAE Plus makes both the application and the machine environment transparent, with noticeable improvements in the learning curve. The main components of TAE Plus are as follows: (1) the WorkBench, a What You See Is What You Get (WYSIWYG) tool for the design and layout of a user interface; (2) the Window Programming Tools Package (WPT), a set of callable subroutines that control an application's user interface; and (3) TAE Command Language (TCL), an easy-to-learn command language that provides an easy way to develop an executable application prototype with a run-time interpreted language. The WorkBench tool allows the application developer to interactively construct the layout of an application's display screen by manipulating a set of interaction objects including input items such as buttons, icons, and scrolling text lists. User interface interactive objects include data-driven graphical objects such as dials, thermometers, and strip charts as well as menubars, option menus, file selection items, message items, push buttons, and color loggers. The WorkBench user specifies the windows and interaction objects that will make up the user interface, then specifies the sequence of the user interface dialogue. The description of the designed user interface is then saved into resource files. For those who desire to develop the designed user interface into an operational application, the WorkBench tool also generates source code (C, C++, Ada, and TCL) which fully controls the application's user interface through function calls to the WPTs. The WPTs are the runtime services used by application programs to display and control the user interfaces. Since the WPTs access the workbench-generated resource files during each execution, details such as color, font, location, and object type remain independent from the application code, allowing changes to the user interface without recompiling and relinking. In addition to WPTs, TAE Plus can control interaction of objects from the interpreted TAE Command Language. TCL provides a means for the more experienced developer to quickly prototype an application's use of TAE Plus interaction objects and add programming logic without the overhead of compiling or linking. TAE Plus requires MIT's X Window System, Version 11 Release 4, and the Open Software Foundation's Motif. The Workbench and WPTs are written in C++ and the remaining code is written in C. TAE Plus is available by license for an unlimited time period. The licensed program product includes the TAE Plus source code and one set of supporting documentation. Additional documentation may be purchased separately at the price indicated below. The amount of disk space required to load the TAE Plus tar format tape is between 35Mb and 67Mb depending on the machine version. The recommended minimum memory is 12Mb. Each TAE Plus platform delivery tape includes pre-built libraries and executable binary code for that particular machine, as well as source code, so users do not have to do an installation. Users wishing to recompile the source will need both a C compiler and either GNU's C++ Version 1.39 or later, or a C++ compiler based on AT&T 2.0 cfront. TAE Plus was developed in 1989 and version 5.2 was released in 1993. TAE Plus 5.2 is expected to be available on media suitable for seven different machine platforms: 1) DEC VAX computers running VMS (TK50 cartridge in VAX BACKUP format), 2) IBM RS/6000 series workstations running AIX (.25 inch tape cartridge in UNIX tar format), 3) DEC RISC workstations running ULTRIX (TK50 cartridge in UNIX tar format), 4) HP9000 Series 300/400 computers running HP-UX (.25 inch HP-preformatted tape cartridge in UNIX tar format), 5) HP9000 Series 700 computers running HP-UX (HP 4mm DDS DAT tape cartridge in UNIX tar format), 6) Sun4 (SPARC) series computers running SunOS (.25 inch tape cartridge in UNIX tar format), and 7) SGI Indigo computers running IRIX (.25 inch IRIS tape cartridge in UNIX tar format). Please contact COSMIC to obtain detailed information about the supported operating system and OSF/Motif releases required for each of these machine versions. An optional Motif Object Code License is available for the Sun4 version of TAE Plus 5.2.

TAE+ 5.1 - TRANSPORTABLE APPLICATIONS ENVIRONMENT PLUS, VERSION 5.1 (VAX VMS VERSION)

NASA Technical Reports Server (NTRS)

TAE SUPPORT OFFICE

1994-01-01

TAE (Transportable Applications Environment) Plus is an integrated, portable environment for developing and running interactive window, text, and graphical object-based application systems. The program allows both programmers and non-programmers to easily construct their own custom application interface and to move that interface and application to different machine environments. TAE Plus makes both the application and the machine environment transparent, with noticeable improvements in the learning curve. The main components of TAE Plus are as follows: (1) the WorkBench, a What You See Is What You Get (WYSIWYG) tool for the design and layout of a user interface; (2) the Window Programming Tools Package (WPT), a set of callable subroutines that control an application's user interface; and (3) TAE Command Language (TCL), an easy-to-learn command language that provides an easy way to develop an executable application prototype with a run-time interpreted language. The WorkBench tool allows the application developer to interactively construct the layout of an application's display screen by manipulating a set of interaction objects including input items such as buttons, icons, and scrolling text lists. User interface interactive objects include data-driven graphical objects such as dials, thermometers, and strip charts as well as menubars, option menus, file selection items, message items, push buttons, and color loggers. The WorkBench user specifies the windows and interaction objects that will make up the user interface, then specifies the sequence of the user interface dialogue. The description of the designed user interface is then saved into resource files. For those who desire to develop the designed user interface into an operational application, the WorkBench tool also generates source code (C, C++, Ada, and TCL) which fully controls the application's user interface through function calls to the WPTs. The WPTs are the runtime services used by application programs to display and control the user interfaces. Since the WPTs access the workbench-generated resource files during each execution, details such as color, font, location, and object type remain independent from the application code, allowing changes to the user interface without recompiling and relinking. In addition to WPTs, TAE Plus can control interaction of objects from the interpreted TAE Command Language. TCL provides a means for the more experienced developer to quickly prototype an application's use of TAE Plus interaction objects and add programming logic without the overhead of compiling or linking. TAE Plus requires MIT's X Window System, Version 11 Release 4, and the Open Software Foundation's Motif. The Workbench and WPTs are written in C++ and the remaining code is written in C. TAE Plus is available by license for an unlimited time period. The licensed program product includes the TAE Plus source code and one set of supporting documentation. Additional documentation may be purchased separately at the price indicated below. The amount of disk space required to load the TAE Plus tar format tape is between 35Mb and 67Mb depending on the machine version. The recommended minimum memory is 12Mb. Each TAE Plus platform delivery tape includes pre-built libraries and executable binary code for that particular machine, as well as source code, so users do not have to do an installation. Users wishing to recompile the source will need both a C compiler and either GNU's C++ Version 1.39 or later, or a C++ compiler based on AT&T 2.0 cfront. TAE Plus was developed in 1989 and version 5.2 was released in 1993. TAE Plus 5.2 is expected to be available on media suitable for seven different machine platforms: 1) DEC VAX computers running VMS (TK50 cartridge in VAX BACKUP format), 2) IBM RS/6000 series workstations running AIX (.25 inch tape cartridge in UNIX tar format), 3) DEC RISC workstations running ULTRIX (TK50 cartridge in UNIX tar format), 4) HP9000 Series 300/400 computers running HP-UX (.25 inch HP-preformatted tape cartridge in UNIX tar format), 5) HP9000 Series 700 computers running HP-UX (HP 4mm DDS DAT tape cartridge in UNIX tar format), 6) Sun4 (SPARC) series computers running SunOS (.25 inch tape cartridge in UNIX tar format), and 7) SGI Indigo computers running IRIX (.25 inch IRIS tape cartridge in UNIX tar format). Please contact COSMIC to obtain detailed information about the supported operating system and OSF/Motif releases required for each of these machine versions. An optional Motif Object Code License is available for the Sun4 version of TAE Plus 5.2.

Rotational fluid flow experiment

NASA Technical Reports Server (NTRS)

1991-01-01

This project which began in 1986 as part of the Worcester Polytechnic Institute (WPI) Advanced Space Design Program focuses on the design and implementation of an electromechanical system for studying vortex behavior in a microgravity environment. Most of the existing equipment was revised and redesigned by this project team, as necessary. Emphasis was placed on documentation and integration of the electrical and mechanical subsystems. Project results include reconfiguration and thorough testing of all hardware subsystems, implementation of an infrared gas entrainment detector, new signal processing circuitry for the ultrasonic fluid circulation device, improved prototype interface circuits, and software for overall control of experiment operation.

ATLAS, an integrated structural analysis and design system. Volume 2: System design document

NASA Technical Reports Server (NTRS)

Erickson, W. J. (Editor)

1979-01-01

ATLAS is a structural analysis and design system, operational on the Control Data Corporation 6600/CYBER computers. The overall system design, the design of the individual program modules, and the routines in the ATLAS system library are described. The overall design is discussed in terms of system architecture, executive function, data base structure, user program interfaces and operational procedures. The program module sections include detailed code description, common block usage and random access file usage. The description of the ATLAS program library includes all information needed to use these general purpose routines.

IGDS/TRAP Interface Program (ITIP). Software Design Document

NASA Technical Reports Server (NTRS)

Jefferys, Steve; Johnson, Wendell

1981-01-01

The preliminary design of the IGDS/TRAP Interface Program (ITIP) is described. The ITIP is implemented on the PDP 11/70 and interfaces directly with the Interactive Graphics Design System and the Data Management and Retrieval System. The program provides an efficient method for developing a network flow diagram. Performance requirements, operational rquirements, and design requirements are discussed along with sources and types of input and destination and types of output. Information processing functions and data base requirements are also covered.

Shuttle payload interface verification equipment study. Volume 2: Technical document, part 1

NASA Technical Reports Server (NTRS)

1976-01-01

The technical analysis is reported that was performed during the shuttle payload interface verification equipment study. It describes: (1) the background and intent of the study; (2) study approach and philosophy covering all facets of shuttle payload/cargo integration; (3)shuttle payload integration requirements; (4) preliminary design of the horizontal IVE; (5) vertical IVE concept; and (6) IVE program development plans, schedule and cost. Also included is a payload integration analysis task to identify potential uses in addition to payload interface verification.

GRIZZLY/FAVOR Interface Project Report

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

Dickson, Terry L; Williams, Paul T; Yin, Shengjun

As part of the Light Water Reactor Sustainability (LWRS) Program, the objective of the GRIZZLY/FAVOR Interface project is to create the capability to apply GRIZZLY 3-D finite element (thermal and stress) analysis results as input to FAVOR probabilistic fracture mechanics (PFM) analyses. The one benefit of FAVOR to Grizzly is the PROBABILISTIC capability. This document describes the implementation of the GRIZZLY/FAVOR Interface, the preliminary verification and tests results and a user guide that provides detailed step-by-step instructions to run the program.

10 CFR 850 Implementation of Requirements

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

Lee, S

2012-01-05

10 CFR 850 defines a contractor as any entity, including affiliated entities, such as a parent corporation, under contract with DOE, including a subcontractor at any tier, with responsibility for performing work at a DOE site in furtherance of a DOE mission. The Chronic Beryllium Disease Prevention Program (CBDPP) applies to beryllium-related activities that are performed at the Lawrence Livermore National Laboratory (LLNL). The CBDPP or Beryllium Safety Program is integrated into the LLNL Worker Safety and Health Program and, thus, implementation documents and responsibilities are integrated in various documents and organizational structures. Program development and management of the CBDPPmore » is delegated to the Environment, Safety and Health (ES&H) Directorate, Worker Safety and Health Functional Area. As per 10 CFR 850, Lawrence Livermore National Security, LLC (LLNS) periodically submits a CBDPP to the National Nuclear Security Administration/Livermore Site Office (NNSA/LSO). The requirements of this plan are communicated to LLNS workers through ES&H Manual Document 14.4, 'Working Safely with Beryllium.' 10 CFR 850 is implemented by the LLNL CBDPP, which integrates the safety and health standards required by the regulation, components of the LLNL Integrated Safety Management System (ISMS), and incorporates other components of the LLNL ES&H Program. As described in the regulation, and to fully comply with the regulation, specific portions of existing programs and additional requirements are identified in the CBDPP. The CBDPP is implemented by documents that interface with the workers, principally through ES&H Manual Document 14.4. This document contains information on how the management practices prescribed by the LLNL ISMS are implemented, how beryllium hazards that are associated with LLNL work activities are controlled, and who is responsible for implementing the controls. Adherence to the requirements and processes described in the ES&H Manual ensures that ES&H practices across LLNL are developed in a consistent manner. Other implementing documents, such as the ES&H Manual, are integral in effectively implementing 10 CFR 850.« less

Design document for the MOODS Data Management System (MDMS), version 1.0

NASA Technical Reports Server (NTRS)

1994-01-01

The MOODS Data Management System (MDMS) provides access to the Master Oceanographic Observation Data Set (MOODS) which is maintained by the Naval Oceanographic Office (NAVOCEANO). The MDMS incorporates database technology in providing seamless access to parameter (temperature, salinity, soundspeed) vs. depth observational profile data. The MDMS is an interactive software application with a graphical user interface (GUI) that supports user control of MDMS functional capabilities. The purpose of this document is to define and describe the structural framework and logical design of the software components/units which are integrated into the major computer software configuration item (CSCI) identified as MDMS, Version 1.0. The preliminary design is based on functional specifications and requirements identified in the governing Statement of Work prepared by the Naval Oceanographic Office (NAVOCEANO) and distributed as a request for proposal by the National Aeronautics and Space Administration (NASA).

Design document for the Surface Currents Data Base (SCDB) Management System (SCDBMS), version 1.0

NASA Technical Reports Server (NTRS)

Krisnnamagaru, Ramesh; Cesario, Cheryl; Foster, M. S.; Das, Vishnumohan

1994-01-01

The Surface Currents Database Management System (SCDBMS) provides access to the Surface Currents Data Base (SCDB) which is maintained by the Naval Oceanographic Office (NAVOCEANO). The SCDBMS incorporates database technology in providing seamless access to surface current data. The SCDBMS is an interactive software application with a graphical user interface (GUI) that supports user control of SCDBMS functional capabilities. The purpose of this document is to define and describe the structural framework and logistical design of the software components/units which are integrated into the major computer software configuration item (CSCI) identified as the SCDBMS, Version 1.0. The preliminary design is based on functional specifications and requirements identified in the governing Statement of Work prepared by the Naval Oceanographic Office (NAVOCEANO) and distributed as a request for proposal by the National Aeronautics and Space Administration (NASA).

Natural brain-information interfaces: Recommending information by relevance inferred from human brain signals

PubMed Central

Eugster, Manuel J. A.; Ruotsalo, Tuukka; Spapé, Michiel M.; Barral, Oswald; Ravaja, Niklas; Jacucci, Giulio; Kaski, Samuel

2016-01-01

Finding relevant information from large document collections such as the World Wide Web is a common task in our daily lives. Estimation of a user’s interest or search intention is necessary to recommend and retrieve relevant information from these collections. We introduce a brain-information interface used for recommending information by relevance inferred directly from brain signals. In experiments, participants were asked to read Wikipedia documents about a selection of topics while their EEG was recorded. Based on the prediction of word relevance, the individual’s search intent was modeled and successfully used for retrieving new relevant documents from the whole English Wikipedia corpus. The results show that the users’ interests toward digital content can be modeled from the brain signals evoked by reading. The introduced brain-relevance paradigm enables the recommendation of information without any explicit user interaction and may be applied across diverse information-intensive applications. PMID:27929077

Clinical Documents: Attribute-Values Entity Representation, Context, Page Layout And Communication

PubMed Central

Lovis, Christian; Lamb, Alexander; Baud, Robert; Rassinoux, Anne-Marie; Fabry, Paul; Geissbühler, Antoine

2003-01-01

This paper presents how acquisition, storage and communication of clinical documents are implemented at the University Hospitals of Geneva. Careful attention has been given to user-interfaces, in order to support complex layouts, spell checking, templates management with automatic prefilling in order to facilitate acquisition. A dual architecture has been developed for storage using an attributes-values entity unified database and a consolidated, patient-centered, layout-respectful files-based storage, providing both representation power and sinsert (peed of accesses. This architecture allows great flexibility to store a continuum of data types from simple type values up to complex clinical reports. Finally, communication is entirely based on HTTP-XML internally and a HL-7 CDA interface V2 is currently studied for external communication. Some of the problem encountered, mostly concerning the typology of documents and the ontology of clinical attributes are evoked. PMID:14728202

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).

Natural brain-information interfaces: Recommending information by relevance inferred from human brain signals

NASA Astrophysics Data System (ADS)

Eugster, Manuel J. A.; Ruotsalo, Tuukka; Spapé, Michiel M.; Barral, Oswald; Ravaja, Niklas; Jacucci, Giulio; Kaski, Samuel

2016-12-01

Finding relevant information from large document collections such as the World Wide Web is a common task in our daily lives. Estimation of a user’s interest or search intention is necessary to recommend and retrieve relevant information from these collections. We introduce a brain-information interface used for recommending information by relevance inferred directly from brain signals. In experiments, participants were asked to read Wikipedia documents about a selection of topics while their EEG was recorded. Based on the prediction of word relevance, the individual’s search intent was modeled and successfully used for retrieving new relevant documents from the whole English Wikipedia corpus. The results show that the users’ interests toward digital content can be modeled from the brain signals evoked by reading. The introduced brain-relevance paradigm enables the recommendation of information without any explicit user interaction and may be applied across diverse information-intensive applications.

The feasibility of remote-controlled assistance as a search tool for patient education.

PubMed

Lin, I K; Bray, B E; Smith, J A; Lange, L L

2001-01-01

Patients often desire more information about their conditions than they receive during a physician office visit. To address the patient's information needs, a touchscreen information kiosk was implemented. Results from the first prototype identified interface, security, and technical issues. Misspelling of search terms was identified as the most observable cause of search failure. An experimental remote control assistance feature was added in the second prototype. The feature allowed a medical librarian to provide real-time remote help during searches by taking control of the patient's computer. Remote assistance improved patient satisfaction, increased ease of use, and raised document retrieval rate (86.7% vs. 56.7%). Both patients and librarians found the application useful. Reasons included its convenience and flexibility, opportunity for direct patient contact, ability to teach through direct demonstration, and complementing the librarian's role as an information gateway. The project demonstrated the feasibility of applying remote control technology to patient education.

The Multimission Image Processing Laboratory's virtual frame buffer interface

NASA Technical Reports Server (NTRS)

Wolfe, T.

1984-01-01

Large image processing systems use multiple frame buffers with differing architectures and vendor supplied interfaces. This variety of architectures and interfaces creates software development, maintenance and portability problems for application programs. Several machine-dependent graphics standards such as ANSI Core and GKS are available, but none of them are adequate for image processing. Therefore, the Multimission Image Processing laboratory project has implemented a programmer level virtual frame buffer interface. This interface makes all frame buffers appear as a generic frame buffer with a specified set of characteristics. This document defines the virtual frame uffer interface and provides information such as FORTRAN subroutine definitions, frame buffer characteristics, sample programs, etc. It is intended to be used by application programmers and system programmers who are adding new frame buffers to a system.

76 FR 23630 - Office of New Reactors; Proposed Revision 2 to Standard Review Plan, Section 1.0 on Introduction...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-04-27

... Standard Review Plan, Section 1.0 on Introduction and Interfaces AGENCY: Nuclear Regulatory Commission (NRC... Revision 2 to Standard Review Plan (SRP), Section 1.0, ``Introduction and Interfaces'' (Agencywide Documents Access and Management System (ADAMS) Accession No. ML110110573). The Office of New Reactors (NRO...

76 FR 77025 - Office of New Reactors; Notice of Availability of the Final Staff Guidance Section 1.0, Revision...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-12-09

... the Final Staff Guidance Section 1.0, Revision 2 on Introduction and Interfaces AGENCY: Nuclear... Plants: LWR Edition,'' Section 1.0, Revision 2 on ``Introduction and Interfaces'' (Agencywide Documents Access and Management System (ADAMS) Accession No. ML112730393). The NRC staff issues revisions to SRP...

Guide to the Stand-Damage Model interface management system

Treesearch

George Racin; J. J. Colbert

1995-01-01

This programmer's support document describes the Gypsy Moth Stand-Damage Model interface management system. Management of stand-damage data made it necessary to define structures to store data and provide the mechanisms to manipulate these data. The software provides a user-friendly means to manipulate files, graph and manage outputs, and edit input data. The...

Advanced information processing system: Hosting of advanced guidance, navigation and control algorithms on AIPS using ASTER

NASA Technical Reports Server (NTRS)

Brenner, Richard; Lala, Jaynarayan H.; Nagle, Gail A.; Schor, Andrei; Turkovich, John

1994-01-01

This program demonstrated the integration of a number of technologies that can increase the availability and reliability of launch vehicles while lowering costs. Availability is increased with an advanced guidance algorithm that adapts trajectories in real-time. Reliability is increased with fault-tolerant computers and communication protocols. Costs are reduced by automatically generating code and documentation. This program was realized through the cooperative efforts of academia, industry, and government. The NASA-LaRC coordinated the effort, while Draper performed the integration. Georgia Institute of Technology supplied a weak Hamiltonian finite element method for optimal control problems. Martin Marietta used MATLAB to apply this method to a launch vehicle (FENOC). Draper supplied the fault-tolerant computing and software automation technology. The fault-tolerant technology includes sequential and parallel fault-tolerant processors (FTP & FTPP) and authentication protocols (AP) for communication. Fault-tolerant technology was incrementally incorporated. Development culminated with a heterogeneous network of workstations and fault-tolerant computers using AP. Draper's software automation system, ASTER, was used to specify a static guidance system based on FENOC, navigation, flight control (GN&C), models, and the interface to a user interface for mission control. ASTER generated Ada code for GN&C and C code for models. An algebraic transform engine (ATE) was developed to automatically translate MATLAB scripts into ASTER.

MAGMA: analysis of two-channel microarrays made easy.

PubMed

Rehrauer, Hubert; Zoller, Stefan; Schlapbach, Ralph

2007-07-01

The web application MAGMA provides a simple and intuitive interface to identify differentially expressed genes from two-channel microarray data. While the underlying algorithms are not superior to those of similar web applications, MAGMA is particularly user friendly and can be used without prior training. The user interface guides the novice user through the most typical microarray analysis workflow consisting of data upload, annotation, normalization and statistical analysis. It automatically generates R-scripts that document MAGMA's entire data processing steps, thereby allowing the user to regenerate all results in his local R installation. The implementation of MAGMA follows the model-view-controller design pattern that strictly separates the R-based statistical data processing, the web-representation and the application logic. This modular design makes the application flexible and easily extendible by experts in one of the fields: statistical microarray analysis, web design or software development. State-of-the-art Java Server Faces technology was used to generate the web interface and to perform user input processing. MAGMA's object-oriented modular framework makes it easily extendible and applicable to other fields and demonstrates that modern Java technology is also suitable for rather small and concise academic projects. MAGMA is freely available at www.magma-fgcz.uzh.ch.

Pairwise Trajectory Management (PTM): Concept Description and Documentation

NASA Technical Reports Server (NTRS)

Jones, Kenneth M.; Graff, Thomas J.; Carreno, Victor; Chartrand, Ryan C.; Kibler, Jennifer L.

2018-01-01

Pairwise Trajectory Management (PTM) is an Interval Management (IM) concept that utilizes airborne and ground-based capabilities to enable the implementation of airborne pairwise spacing capabilities in oceanic regions. The goal of PTM is to use airborne surveillance and tools to manage an "at or greater than" inter-aircraft spacing. Due to the accuracy of Automatic Dependent Surveillance-Broadcast (ADS-B) information and the use of airborne spacing guidance, the minimum PTM spacing distance will be less than distances a controller can support with current automation systems that support oceanic operations. Ground tools assist the controller in evaluating the traffic picture and determining appropriate PTM clearances to be issued. Avionics systems provide guidance information that allows the flight crew to conform to the PTM clearance issued by the controller. The combination of a reduced minimum distance and airborne spacing management will increase the capacity and efficiency of aircraft operations at a given altitude or volume of airspace. This document provides an overview of the proposed application, a description of several key scenarios, a high level discussion of expected air and ground equipment and procedure changes, a description of a NASA human-machine interface (HMI) prototype for the flight crew that would support PTM operations, and initial benefits analysis results. Additionally, included as appendices, are the following documents: the PTM Operational Services and Environment Definition (OSED) document and a companion "Future Considerations for the Pairwise Trajectory Management (PTM) Concept: Potential Future Updates for the PTM OSED" paper, a detailed description of the PTM algorithm and PTM Limit Mach rules, initial PTM safety requirements and safety assessment documents, a detailed description of the design, development, and initial evaluations of the proposed flight crew HMI, an overview of the methodology and results of PTM pilot training requirements focus group and human-in-the-loop testing activities, and the PTM Pilot Guide.

Compensation for electrical converter nonlinearities

DOEpatents

Perisic, Milun; Ransom, Ray M; Kajouke, Lateef A

2013-11-19

Systems and methods are provided for delivering energy from an input interface to an output interface. An electrical system includes an input interface, an output interface, an energy conversion module between the input interface and the output interface, an inductive element between the input interface and the energy conversion module, and a control module. The control module determines a compensated duty cycle control value for operating the energy conversion module to produce a desired voltage at the output interface and operates the energy conversion module to deliver energy to the output interface with a duty cycle that is influenced by the compensated duty cycle control value. The compensated duty cycle control value is influenced by the current through the inductive element and accounts for voltage across the switching elements of the energy conversion module.

Implementation of a scalable, web-based, automated clinical decision support risk-prediction tool for chronic kidney disease using C-CDA and application programming interfaces.

PubMed

Samal, Lipika; D'Amore, John D; Bates, David W; Wright, Adam

2017-11-01

Clinical decision support tools for risk prediction are readily available, but typically require workflow interruptions and manual data entry so are rarely used. Due to new data interoperability standards for electronic health records (EHRs), other options are available. As a clinical case study, we sought to build a scalable, web-based system that would automate calculation of kidney failure risk and display clinical decision support to users in primary care practices. We developed a single-page application, web server, database, and application programming interface to calculate and display kidney failure risk. Data were extracted from the EHR using the Consolidated Clinical Document Architecture interoperability standard for Continuity of Care Documents (CCDs). EHR users were presented with a noninterruptive alert on the patient's summary screen and a hyperlink to details and recommendations provided through a web application. Clinic schedules and CCDs were retrieved using existing application programming interfaces to the EHR, and we provided a clinical decision support hyperlink to the EHR as a service. We debugged a series of terminology and technical issues. The application was validated with data from 255 patients and subsequently deployed to 10 primary care clinics where, over the course of 1 year, 569 533 CCD documents were processed. We validated the use of interoperable documents and open-source components to develop a low-cost tool for automated clinical decision support. Since Consolidated Clinical Document Architecture-based data extraction extends to any certified EHR, this demonstrates a successful modular approach to clinical decision support. © The Author 2017. Published by Oxford University Press on behalf of the American Medical Informatics Association.

Manufacturing. Technology Education-Mathematics and Science Interface Project.

ERIC Educational Resources Information Center

Smith, Kenneth L., Ed.

The curriculum materials contained in this document were developed through a cooperative effort by educators in the state of Maryland. It was a curriculum project aimed at the meaningful integration of mathematics and science. It is suggested that these materials be used in two significant ways. First, this document can serve as an instructional…

Construction. Technology Education-Mathematics and Science Interface Project.

ERIC Educational Resources Information Center

Maryland State Dept. of Education, Baltimore. Div. of Vocational-Technical Education.

The curriculum materials contained in this document were developed through a cooperative effort by educators in the state of Maryland. It was a curriculum project aimed at the meaningful integration of mathematics and science. It is suggested that these materials be used in two significant ways. First, this document can serve as an instructional…

Transportation. Technology Education-Mathematics and Science Interface Project.

ERIC Educational Resources Information Center

Smith, Kenneth L., Ed.

The curriculum materials contained in this document were developed through a cooperative effort by educators in the state of Maryland. It was a curriculum project aimed at the meaningful integration of mathematics and science. It is suggested that these materials be used in two significant ways. First, this document can serve as an instructional…

Defining Usability Heuristics for Adoption and Efficiency of an Electronic Workflow Document Management System

ERIC Educational Resources Information Center

Fuentes, Steven

2017-01-01

Usability heuristics have been established for different uses and applications as general guidelines for user interfaces. These can affect the implementation of industry solutions and play a significant role regarding cost reduction and process efficiency. The area of electronic workflow document management (EWDM) solutions, also known as…

Tailoring a ConOps for NASA LSP Integrated Operations

NASA Technical Reports Server (NTRS)

Owens, Skip Clark V., III

2017-01-01

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this paper is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services. This tailoring effort was performed as the authors final Masters Project in the Spring of 2016 for the Stevens Institute of Technology and modified for publication with INCOSE (Owens, 2016).

An implementation and evaluation of the MPI 3.0 one-sided communication interface

DOE PAGES

Dinan, James S.; Balaji, Pavan; Buntinas, Darius T.; ...

2016-01-09

The Q1 Message Passing Interface (MPI) 3.0 standard includes a significant revision to MPI’s remote memory access (RMA) interface, which provides support for one-sided communication. MPI-3 RMA is expected to greatly enhance the usability and performance ofMPI RMA.We present the first complete implementation of MPI-3 RMA and document implementation techniques and performance optimization opportunities enabled by the new interface. Our implementation targets messaging-based networks and is publicly available in the latest release of the MPICH MPI implementation. Here using this implementation, we explore the performance impact of new MPI-3 functionality and semantics. Results indicate that the MPI-3 RMA interface providesmore » significant advantages over the MPI-2 interface by enabling increased communication concurrency through relaxed semantics in the interface and additional routines that provide new window types, synchronization modes, and atomic operations.« less

An implementation and evaluation of the MPI 3.0 one-sided communication interface

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

Dinan, James S.; Balaji, Pavan; Buntinas, Darius T.

The Q1 Message Passing Interface (MPI) 3.0 standard includes a significant revision to MPI’s remote memory access (RMA) interface, which provides support for one-sided communication. MPI-3 RMA is expected to greatly enhance the usability and performance ofMPI RMA.We present the first complete implementation of MPI-3 RMA and document implementation techniques and performance optimization opportunities enabled by the new interface. Our implementation targets messaging-based networks and is publicly available in the latest release of the MPICH MPI implementation. Here using this implementation, we explore the performance impact of new MPI-3 functionality and semantics. Results indicate that the MPI-3 RMA interface providesmore » significant advantages over the MPI-2 interface by enabling increased communication concurrency through relaxed semantics in the interface and additional routines that provide new window types, synchronization modes, and atomic operations.« less

Control System Architectures, Technologies and Concepts for Near Term and Future Human Exploration of Space

NASA Technical Reports Server (NTRS)

Boulanger, Richard; Overland, David

2004-01-01

Technologies that facilitate the design and control of complex, hybrid, and resource-constrained systems are examined. This paper focuses on design methodologies, and system architectures, not on specific control methods that may be applied to life support subsystems. Honeywell and Boeing have estimated that 60-80Y0 of the effort in developing complex control systems is software development, and only 20-40% is control system development. It has also been shown that large software projects have failure rates of as high as 50-65%. Concepts discussed include the Unified Modeling Language (UML) and design patterns with the goal of creating a self-improving, self-documenting system design process. Successful architectures for control must not only facilitate hardware to software integration, but must also reconcile continuously changing software with much less frequently changing hardware. These architectures rely on software modules or components to facilitate change. Architecting such systems for change leverages the interfaces between these modules or components.

The Effect of Cartilage Fragments on Femoral Tunnel Widening After Anterior Cruciate Ligament Reconstruction: A Prospective Randomized Controlled Study.

PubMed

Zhang, Chi; Pan, Jun; Chen, Jian-De; Zhang, Yi-Jun; Gu, Peng-Cheng; Lin, Xiang-Jin; Cai, You-Zhi

2018-05-03

To analyze the effect of cartilage fragments on tunnel widening and tendon-bone integration at 2 years' follow-up after anterior cruciate ligament reconstruction (ACLR). A prospective randomized controlled study was performed in 116 patients who underwent ACLR with autologous hamstring tendons augmented with cartilage fragments (study group, n = 56) or without any augmentation (control group, n = 60). All patients were followed up for 25.6 months (range, 24-28 months), and the International Knee Documentation Committee score, Lysholm score, and visual analog scale score were determined. Computed tomography scans of all patients were obtained 2 years after surgery to evaluate the diameter of the femoral tunnel and thereby assess the amount of tunnel widening. Magnetic resonance imaging evaluation was performed 2 years postoperatively to evaluate the status of the graft in the femoral tunnel. In addition, 5 patients underwent biopsy of the tendon-bone interface at 24 months postoperatively with histologic assessment and transmission electron microscopy. A total of 107 patients completed the follow-up. There were no significant differences between the 2 groups in terms of International Knee Documentation Committee score (P = .07), Lysholm score (P = .10), and visual analog scale score (P = .57) at 24 months' follow-up. The femoral tunnel diameter and the tunnel widening percentage in the study group were significantly smaller than those in the control group (P < .001). The signal-noise quotient value of the graft in the femoral tunnel was 10.4 ± 7.0 in the study group, which was significantly lower than that in the control group (19.5 ± 9.2, P < .001). Histologic studies of the tendon-bone interface showed that there were more bone formations containing chondroid cells with aligned connective tissue in the study group compared with the control group; in addition, the diameter of the collagen fibrils in the study group was considerably thicker than that in the control group (P < .05). The use of cartilage fragments was effective in preventing femoral tunnel widening and seemed to promote the tendon-bone integration process after ACLR. Level II, prospective randomized controlled study. Copyright © 2018 Arthroscopy Association of North America. Published by Elsevier Inc. All rights reserved.

Online Remote Sensing Interface

NASA Technical Reports Server (NTRS)

Lawhead, Joel

2007-01-01

BasinTools Module 1 processes remotely sensed raster data, including multi- and hyper-spectral data products, via a Web site with no downloads and no plug-ins required. The interface provides standardized algorithms designed so that a user with little or no remote-sensing experience can use the site. This Web-based approach reduces the amount of software, hardware, and computing power necessary to perform the specified analyses. Access to imagery and derived products is enterprise-level and controlled. Because the user never takes possession of the imagery, the licensing of the data is greatly simplified. BasinTools takes the "just-in-time" inventory control model from commercial manufacturing and applies it to remotely-sensed data. Products are created and delivered on-the-fly with no human intervention, even for casual users. Well-defined procedures can be combined in different ways to extend verified and validated methods in order to derive new remote-sensing products, which improves efficiency in any well-defined geospatial domain. Remote-sensing products produced in BasinTools are self-documenting, allowing procedures to be independently verified or peer-reviewed. The software can be used enterprise-wide to conduct low-level remote sensing, viewing, sharing, and manipulating of image data without the need for desktop applications.

Future ATM Concepts Evaluation Tool (FACET) Interface Control Document

NASA Technical Reports Server (NTRS)

Grabbe, Shon R.

2017-01-01

This Interface Control Document (ICD) documents the airspace adaptation and air traffic inputs of NASA's Future ATM Concepts and Evaluation Tool (FACET). Its intended audience is the project manager, project team, development team, and stakeholders interested in interfacing with the system. FACET equips Air Traffic Management (ATM) researchers and service providers with a way to explore, develop and evaluate advanced air transportation concepts before they are field-tested and eventually deployed. FACET is a flexible software tool that is capable of quickly generating and analyzing thousands of aircraft trajectories. It provides researchers with a simulation environment for preliminary testing of advanced ATM concepts. Using aircraft performance profiles, airspace models, weather data, and flight schedules, the tool models trajectories for the climb, cruise, and descent phases of flight for each type of aircraft. An advanced graphical interface displays traffic patterns in two and three dimensions, under various current and projected conditions for specific airspace regions or over the entire continental United States. The system is able to simulate a full day's dynamic national airspace system (NAS) operations, model system uncertainty, measure the impact of different decision-makers in the NAS, and provide analysis of the results in graphical form, including sector, airport, fix, and airway usage statistics. NASA researchers test and analyze the system-wide impact of new traffic flow management algorithms under anticipated air traffic growth projections on the nation's air traffic system. In addition to modeling the airspace system for NASA research, FACET has also successfully transitioned into a valuable tool for operational use. Federal Aviation Administration (FAA) traffic flow managers and commercial airline dispatchers have used FACET technology for real-time operations planning. FACET integrates live air traffic data from FAA radar systems and weather data from the National Weather Service to summarize NAS performance. This information allows system operators to reroute flights around congested airspace and severe weather to maintain safety and minimize delay. FACET also supports the planning and post-operational evaluation of reroute strategies at the national level to maximize system efficiency. For the commercial airline passenger, strategic planning with FACET can result in fewer flight delays and cancellations. The performance capabilities of FACET are largely due to its architecture, which strikes a balance between flexibility and fidelity. FACET is capable of modeling the airspace operations for the continental United States, processing thousands of aircraft on a single computer. FACET was written in Java and C, enabling the portability of its software to a variety of operating systems. In addition, FACET was designed with a modular software architecture to facilitate rapid prototyping of diverse ATM concepts. Several advanced ATM concepts have already been implemented in FACET, including aircraft self-separation, prediction of aircraft demand and sector congestion, system-wide impact assessment of traffic flow management constraints, and wind-optimal routing.

The 2010 wildland-urban interface of the conterminous United States

Treesearch

Sebasti& #237; n Martinuzzi; Susan I. Stewart; David P. Helmers; Miranda H. Mockrin; Roger B. Hammer; Volker C. Radeloff

2015-01-01

The wildland-urban interface (WUI) is the area where structures and other human development meet or intermingle with undeveloped wildland, and it is where wildfires have their greatest impacts on people. Hence the WUI is important for wildfire management. This document and associated maps summarize the extent of the WUI in the conterminous United States in 2010. The...

System and Method for Providing a Climate Data Analytic Services Application Programming Interface Distribution Package

NASA Technical Reports Server (NTRS)

Tamkin, Glenn S. (Inventor); Duffy, Daniel Q. (Inventor); Schnase, John L. (Inventor)

2016-01-01

A system, method and computer-readable storage devices for providing a climate data analytic services application programming interface distribution package. The example system can provide various components. The system provides a climate data analytic services application programming interface library that enables software applications running on a client device to invoke the capabilities of a climate data analytic service. The system provides a command-line interface that provides a means of interacting with a climate data analytic service by issuing commands directly to the system's server interface. The system provides sample programs that call on the capabilities of the application programming interface library and can be used as templates for the construction of new client applications. The system can also provide test utilities, build utilities, service integration utilities, and documentation.

Automatic document classification of biological literature

PubMed Central

Chen, David; Müller, Hans-Michael; Sternberg, Paul W

2006-01-01

Background Document classification is a wide-spread problem with many applications, from organizing search engine snippets to spam filtering. We previously described Textpresso, a text-mining system for biological literature, which marks up full text according to a shallow ontology that includes terms of biological interest. This project investigates document classification in the context of biological literature, making use of the Textpresso markup of a corpus of Caenorhabditis elegans literature. Results We present a two-step text categorization algorithm to classify a corpus of C. elegans papers. Our classification method first uses a support vector machine-trained classifier, followed by a novel, phrase-based clustering algorithm. This clustering step autonomously creates cluster labels that are descriptive and understandable by humans. This clustering engine performed better on a standard test-set (Reuters 21578) compared to previously published results (F-value of 0.55 vs. 0.49), while producing cluster descriptions that appear more useful. A web interface allows researchers to quickly navigate through the hierarchy and look for documents that belong to a specific concept. Conclusion We have demonstrated a simple method to classify biological documents that embodies an improvement over current methods. While the classification results are currently optimized for Caenorhabditis elegans papers by human-created rules, the classification engine can be adapted to different types of documents. We have demonstrated this by presenting a web interface that allows researchers to quickly navigate through the hierarchy and look for documents that belong to a specific concept. PMID:16893465

Ontology-Driven Search and Triage: Design of a Web-Based Visual Interface for MEDLINE.

PubMed

Demelo, Jonathan; Parsons, Paul; Sedig, Kamran

2017-02-02

Diverse users need to search health and medical literature to satisfy open-ended goals such as making evidence-based decisions and updating their knowledge. However, doing so is challenging due to at least two major difficulties: (1) articulating information needs using accurate vocabulary and (2) dealing with large document sets returned from searches. Common search interfaces such as PubMed do not provide adequate support for exploratory search tasks. Our objective was to improve support for exploratory search tasks by combining two strategies in the design of an interactive visual interface by (1) using a formal ontology to help users build domain-specific knowledge and vocabulary and (2) providing multi-stage triaging support to help mitigate the information overload problem. We developed a Web-based tool, Ontology-Driven Visual Search and Triage Interface for MEDLINE (OVERT-MED), to test our design ideas. We implemented a custom searchable index of MEDLINE, which comprises approximately 25 million document citations. We chose a popular biomedical ontology, the Human Phenotype Ontology (HPO), to test our solution to the vocabulary problem. We implemented multistage triaging support in OVERT-MED, with the aid of interactive visualization techniques, to help users deal with large document sets returned from searches. Formative evaluation suggests that the design features in OVERT-MED are helpful in addressing the two major difficulties described above. Using a formal ontology seems to help users articulate their information needs with more accurate vocabulary. In addition, multistage triaging combined with interactive visualizations shows promise in mitigating the information overload problem. Our strategies appear to be valuable in addressing the two major problems in exploratory search. Although we tested OVERT-MED with a particular ontology and document collection, we anticipate that our strategies can be transferred successfully to other contexts. ©Jonathan Demelo, Paul Parsons, Kamran Sedig. Originally published in JMIR Medical Informatics (http://medinform.jmir.org), 02.02.2017.

Ontology-Driven Search and Triage: Design of a Web-Based Visual Interface for MEDLINE

PubMed Central

2017-01-01

Background Diverse users need to search health and medical literature to satisfy open-ended goals such as making evidence-based decisions and updating their knowledge. However, doing so is challenging due to at least two major difficulties: (1) articulating information needs using accurate vocabulary and (2) dealing with large document sets returned from searches. Common search interfaces such as PubMed do not provide adequate support for exploratory search tasks. Objective Our objective was to improve support for exploratory search tasks by combining two strategies in the design of an interactive visual interface by (1) using a formal ontology to help users build domain-specific knowledge and vocabulary and (2) providing multi-stage triaging support to help mitigate the information overload problem. Methods We developed a Web-based tool, Ontology-Driven Visual Search and Triage Interface for MEDLINE (OVERT-MED), to test our design ideas. We implemented a custom searchable index of MEDLINE, which comprises approximately 25 million document citations. We chose a popular biomedical ontology, the Human Phenotype Ontology (HPO), to test our solution to the vocabulary problem. We implemented multistage triaging support in OVERT-MED, with the aid of interactive visualization techniques, to help users deal with large document sets returned from searches. Results Formative evaluation suggests that the design features in OVERT-MED are helpful in addressing the two major difficulties described above. Using a formal ontology seems to help users articulate their information needs with more accurate vocabulary. In addition, multistage triaging combined with interactive visualizations shows promise in mitigating the information overload problem. Conclusions Our strategies appear to be valuable in addressing the two major problems in exploratory search. Although we tested OVERT-MED with a particular ontology and document collection, we anticipate that our strategies can be transferred successfully to other contexts. PMID:28153818

78 FR 36541 - Public Interface Control Working Group (ICWG) Meeting

Federal Register 2010, 2011, 2012, 2013, 2014

2013-06-18

... DEPARTMENT OF DEFENSE Department of the Air Force Public Interface Control Working Group (ICWG... Systems (GPS) Directorate will be hosting a Public Interface Control Working Group (ICWG) meeting for the....mil by August 7, 2013. Public Interface Control Working Group Meeting (ICWG) Date(s) and Times: 24-25...

Steamer II: Steamer prototype component inventory and user interface commands. Technical report, 1988-1989

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

Dickieson, J.L.; Thode, W.F.; Newbury, K.

1988-12-01

Over the last several years, Navy Personnel Research and Development has produced a prototype simulation of a 1200-psi steam plant. This simulation, called Steamer, is installed on an expensive Symbolics minicomputer at the Surface Warfare Officers School, Pacific Coronado, California. The fundamental research goal of the Steamer prototype system was to evaluate the potential of, what was then, new artificial intelligence (AI) hardware and software technology for supporting the construction of computer-based training systems using graphic representations of complex, dynamic systems. The area of propulsion engineering was chosen for a number of reasons. This document describes the Steamer prototype systemmore » components and user interface commands and establishes a starting point for designing, developing, and implementing Steamer II. Careful examination of the actual program code produced an inventory that describes the hardware, system software, application software, and documentation for the Steamer prototype system. Exercising all menu options systematically produced an inventory of all Steamer prototype user interface commands.« less

ADM guidance-Ceramics: all-ceramic multilayer interfaces in dentistry.

PubMed

Lohbauer, Ulrich; Scherrer, Susanne S; Della Bona, Alvaro; Tholey, Michael; van Noort, Richard; Vichi, Alessandro; Kelly, J Robert; Cesar, Paulo F

2017-06-01

This guidance document describes the specific issues involved in dental multilayer ceramic systems. The material interactions with regard to specific thermal and mechanical properties are reviewed and the characteristics of dental tooth-shaped processing parameters (sintering, geometry, thickness ratio, etc.) are discussed. Several techniques for the measurement of bond quality and residual stresses are presented with a detailed discussion of advantages and disadvantages. In essence no single technique is able to describe adequately the all-ceramic interface. Invasive or semi-invasive methods have been shown to distort the information regarding the residual stress state while non-invasive methods are limited due to resolution, field of focus or working depth. This guidance document has endeavored to provide a scientific basis for future research aimed at characterizing the ceramic interface of dental restorations. Along with the methodological discussion it is seeking to provide an introduction and guidance to relatively inexperienced researchers. Copyright © 2017 The Academy of Dental Materials. Published by Elsevier Ltd. All rights reserved.

NASA Access Mechanism: Lessons learned document

NASA Technical Reports Server (NTRS)

Burdick, Lisa; Dunbar, Rick; Duncan, Denise; Generous, Curtis; Hunter, Judy; Lycas, John; Taber-Dudas, Ardeth

1994-01-01

The six-month beta test of the NASA Access Mechanism (NAM) prototype was completed on June 30, 1993. This report documents the lessons learned from the use of this Graphical User Interface to NASA databases such as the NASA STI Database, outside databases, Internet resources, and peers in the NASA R&D community. Design decisions, such as the use of XWindows software, a client-server distributed architecture, and use of the NASA Science Internet, are explained. Users' reactions to the interface and suggestions for design changes are reported, as are the changes made by the software developers based on new technology for information discovery and retrieval. The lessons learned section also reports reactions from the public, both at demonstrations and in response to articles in the trade press and journals. Recommendations are included for future versions, such as a World Wide Web (WWW) and Mosaic based interface to heterogeneous databases, and NAM-Lite, a version which allows customization to include utilities provided locally at NASA Centers.

A new JAVA interface implementation of THESIAS: testing haplotype effects in association studies.

PubMed

Tregouet, D A; Garelle, V

2007-04-15

THESIAS (Testing Haplotype EffectS In Association Studies) is a popular software for carrying haplotype association analysis in unrelated individuals. In addition to the command line interface, a graphical JAVA interface is now proposed allowing one to run THESIAS in a user-friendly manner. Besides, new functionalities have been added to THESIAS including the possibility to analyze polychotomous phenotype and X-linked polymorphisms. The software package including documentation and example data files is freely available at http://genecanvas.ecgene.net. The source codes are also available upon request.

Software design and code generation for the engineering graphical user interface of the ASTRI SST-2M prototype for the Cherenkov Telescope Array

NASA Astrophysics Data System (ADS)

Tanci, Claudio; Tosti, Gino; Antolini, Elisa; Gambini, Giorgio F.; Bruno, Pietro; Canestrari, Rodolfo; Conforti, Vito; Lombardi, Saverio; Russo, Federico; Sangiorgi, Pierluca; Scuderi, Salvatore

2016-08-01

ASTRI is an on-going project developed in the framework of the Cherenkov Telescope Array (CTA). An end- to-end prototype of a dual-mirror small-size telescope (SST-2M) has been installed at the INAF observing station on Mt. Etna, Italy. The next step is the development of the ASTRI mini-array composed of nine ASTRI SST-2M telescopes proposed to be installed at the CTA southern site. The ASTRI mini-array is a collaborative and international effort carried on by Italy, Brazil and South-Africa and led by the Italian National Institute of Astrophysics, INAF. To control the ASTRI telescopes, a specific ASTRI Mini-Array Software System (MASS) was designed using a scalable and distributed architecture to monitor all the hardware devices for the telescopes. Using code generation we built automatically from the ASTRI Interface Control Documents a set of communication libraries and extensive Graphical User Interfaces that provide full access to the capabilities offered by the telescope hardware subsystems for testing and maintenance. Leveraging these generated libraries and components we then implemented a human designed, integrated, Engineering GUI for MASS to perform the verification of the whole prototype and test shared services such as the alarms, configurations, control systems, and scientific on-line outcomes. In our experience the use of code generation dramatically reduced the amount of effort in development, integration and testing of the more basic software components and resulted in a fast software release life cycle. This approach could be valuable for the whole CTA project, characterized by a large diversity of hardware components.

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.

Power and Energy. Technology Education-Mathematics and Science Interface Project.

ERIC Educational Resources Information Center

Maryland State Dept. of Education, Baltimore. Div. of Vocational-Technical Education.

The curriculum materials contained in this document were developed through a cooperative effort by educators in the state of Maryland. It was a curriculum project aimed at the meaningful integration of mathematics and science. It is suggested that these materials be used in two significant ways. First, this document can serve as an instructional…

Design considerations to improve cognitive ergonomic issues of unmanned vehicle interfaces utilizing video game controllers.

PubMed

Oppold, P; Rupp, M; Mouloua, M; Hancock, P A; Martin, J

2012-01-01

Unmanned (UAVs, UCAVs, and UGVs) systems still have major human factors and ergonomic challenges related to the effective design of their control interface systems, crucial to their efficient operation, maintenance, and safety. Unmanned system interfaces with a human centered approach promote intuitive interfaces that are easier to learn, and reduce human errors and other cognitive ergonomic issues with interface design. Automation has shifted workload from physical to cognitive, thus control interfaces for unmanned systems need to reduce mental workload on the operators and facilitate the interaction between vehicle and operator. Two-handed video game controllers provide wide usability within the overall population, prior exposure for new operators, and a variety of interface complexity levels to match the complexity level of the task and reduce cognitive load. This paper categorizes and provides taxonomy for 121 haptic interfaces from the entertainment industry that can be utilized as control interfaces for unmanned systems. Five categories of controllers were based on the complexity of the buttons, control pads, joysticks, and switches on the controller. This allows the selection of the level of complexity needed for a specific task without creating an entirely new design or utilizing an overly complex design.

Stand-alone digital data storage control system including user control interface

NASA Technical Reports Server (NTRS)

Wright, Kenneth D. (Inventor); Gray, David L. (Inventor)

1994-01-01

A storage control system includes an apparatus and method for user control of a storage interface to operate a storage medium to store data obtained by a real-time data acquisition system. Digital data received in serial format from the data acquisition system is first converted to a parallel format and then provided to the storage interface. The operation of the storage interface is controlled in accordance with instructions based on user control input from a user. Also, a user status output is displayed in accordance with storage data obtained from the storage interface. By allowing the user to control and monitor the operation of the storage interface, a stand-alone, user-controllable data storage system is provided for storing the digital data obtained by a real-time data acquisition system.

Do Interactive Globes and Games Help Students Learn Planetary Science?

NASA Astrophysics Data System (ADS)

Coba, Filis; Burgin, Stephen; De Paor, Declan; Georgen, Jennifer

2016-01-01

The popularity of animations and interactive visualizations in undergraduate science education might lead one to assume that these teaching aids enhance student learning. We tested this assumption for the case of the Google Earth virtual globe with a comparison of control and treatment student groups in a general education class of over 370 students at a large public university. Earth and Planetary Science course content was developed in two formats: using Keyhole Markup Language (KML) to create interactive tours in Google Earth (the treatment group) and Portable Document Format (PDF) for on-screen reading (the control group). The PDF documents contained identical text and images to the placemark balloons or "tour stops" in the Google Earth version. Some significant differences were noted between the two groups based on the immediate post-questionnaire with the KML students out-performing the PDF students, but not on the delayed measure. In a separate but related project, we undertake preliminary investigations into methods of teaching basic concepts in planetary mantle convection using numerical simulations. The goal of this project is to develop an interface with a two-dimensional finite element model that will allow students to vary parameters such as the temperatures assigned to the boundaries of the model domain, to help them actively explore important variables that control convection.

An Assessment of IMPAC - Integrated Methodology for Propulsion and Airframe Controls

NASA Technical Reports Server (NTRS)

Walker, G. P.; Wagner, E. A.; Bodden, D. S.

1996-01-01

This report documents the work done under a NASA sponsored contract to transition to industry technologies developed under the NASA Lewis Research Center IMPAC (Integrated Methodology for Propulsion and Airframe Control) program. The critical steps in IMPAC are exercised on an example integrated flight/propulsion control design for linear airframe/engine models of a conceptual STOVL (Short Take-Off and Vertical Landing) aircraft, and MATRIXX (TM) executive files to implement each step are developed. The results from the example study are analyzed and lessons learned are listed along with recommendations that will improve the application of each design step. The end product of this research is a set of software requirements for developing a user-friendly control design tool which will automate the steps in the IMPAC methodology. Prototypes for a graphical user interface (GUI) are sketched to specify how the tool will interact with the user, and it is recommended to build the tool around existing computer aided control design software packages.

INL Multi-Robot Control Interface

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

2005-03-30

The INL Multi-Robot Control Interface controls many robots through a single user interface. The interface includes a robot display window for each robot showing the robot’s condition. More than one window can be used depending on the number of robots. The user interface also includes a robot control window configured to receive commands for sending to the respective robot and a multi-robot common window showing information received from each robot.

On-Orbit Engineering and Vehicle Integration Poster Presentation

NASA Technical Reports Server (NTRS)

Heimerdinger, Madison

2014-01-01

One of the duties of the MER Managers is getting the consoles to review and sign Electronic Flight Notes (EFN) and Mission Action Requests (Chit) before they are due. Chits and EFNs and are accessible through the Mission Control Center - Houston (MCC-H) Gateway. Chits are the official means of documenting questions and answers, technical direction, real-time changes to Flight Rules (FR) and procedures, request for analysis, etc. between various consoles concerning on-orbit operations. EFNs are documents used by the Flight Control Team (FCT) to communicate precise details between console positions and manage real time changes to FR and Systems Operation Data File (SODF) procedures. On GMT 2013/345 the External Active Thermal Control System (EATCS) on the Columbus (COL) Moderate Temperature Loop (MTL) Interface Heat Exchanger (IFHX) shut down due to low temperatures. Over the next couple of days, the core temperature of COL MT IFHX dropped due to the failure of the Flow Control Valve (FCV). After the temperature drop was discovered, heaters were turned on to bring the temperatures back to nominal. After the incident occurred, a possible freeze threat was discovered that could have ruptured the heat exchanger. The COL MT IFHX rupturing would be considered a catastrophic failure and potentially result in a loss of the vehicle and/or the lives of the International Space Station (ISS) crew members

Controls on Cyclic Formation of Quaternary Early Diagenetic Dolomite

NASA Astrophysics Data System (ADS)

McCormack, J.; Bontognali, T. R. R.; Immenhauser, A.; Kwiecien, O.

2018-04-01

The origin of sedimentary dolomite and the factors that control its formation within the geological record remain speculative. In most models, dolomite formation is linked to evaporative conditions, high water temperature, increasing Mg/Ca ratio, increasing alkalinity, and high amounts of biomass. Here we challenge these archetypal views, by documenting a case example of Quaternary dolomite which formed in Lake Van at constantly low temperature (<4°C) and without direct control of the latter conditions. Dolomite occurs within highstand sediments related to suborbital climate variability (Dansgaard-Oeschger cycles). We propose that dolomite precipitation is a product of a microbially influenced process, triggered by ecological stress, resulting from reventilation of the water-sediment interface. Independently from the validity of this hypothesis, our results call for a reevaluation of the paleoenvironmental conditions often invoked for early diagenetic dolomite-rich intervals within sedimentary sequences and for caution when interpreting time series of subrecent lacustrine carbonates.

International Energy Module - NEMS Documentation

EIA Publications

2014-01-01

Summarizes the overall structure of the International Energy Model and its interface with other NEMS modules, mathematical specifications of behavioral relationships, and data sources and estimation methods.

IETM Usability: Using Empirical Studies to Improve Performance Aiding

DTIC Science & Technology

2001-05-14

is highly graphical . An example screen is shown in Figure 3. Following is a description of the design solutions incorporated in Interface B to...in enabling lesser skilled U.S. Navy maintainers to perform their jobs. This empirical study about the design and effectiveness of high level IETMs...novice preferences and performance were documented to inform future adaptive interface design efforts. The maintainers who participated were

Selenide isotope generator (SIG) for the Galileo Mission

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

Not Available

1978-09-01

This agreement establishes the procedures and defines the responsibilities that are a part of the DOE/TES/3M interface for the duration of the SIG/Galileo Mission Program. The agreement is intended to expand upon the Interface Document which is Attachment IV to both the 3M and TES Contract Statement of Work. The agreement is effective upon approval by DOE, TES and 3M Company.

PC-based Multiple Information System Interface (PC/MISI) detailed design and implementation plan

NASA Technical Reports Server (NTRS)

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

1985-01-01

The design plan for the personal computer multiple information system interface (PC/MISI) project is discussed. The document is intended to be used as a blueprint for the implementation of the system. Each component is described in the detail necessary to allow programmers to implement the system. A description of the system data flow and system file structures is given.

Interface between Education and State Policy: Australia. Asia and the Pacific Programme of Educational Innovation for Development, Education and Polity, No. 2.

ERIC Educational Resources Information Center

Hughes, Phillip; And Others

One of seven studies in the "Education and Polity" series, this document looks at alternative futures and the interface of education with four areas: communication; employment and leisure; state policy; and technology. The studies were commissioned during 1984 and were conducted by interdisciplinary teams: two in Australia, two in India,…

[The hybrid operating room. Home of high-end intraoperative imaging].

PubMed

Gebhard, F; Riepl, C; Richter, P; Liebold, A; Gorki, H; Wirtz, R; König, R; Wilde, F; Schramm, A; Kraus, M

2012-02-01

A hybrid operating room must serve the medical needs of different highly specialized disciplines. It integrates interventional techniques for cardiovascular procedures and allows operations in the field of orthopaedic surgery, neurosurgery and maxillofacial surgery. The integration of all steps such as planning, documentation and the procedure itself saves time and precious resources. The best available imaging devices and user interfaces reduce the need for extensive personnel in the OR and facilitate new minimally invasive procedures. The immediate possibility of postoperative control images in CT-like quality enables the surgeon to react to problems during the same procedure without the need for later revision.

Space station MSFC-DPD-235/DR no. MA-05 phase C/D program development plan. Volume 2: Phase C/D, programmatic requirements

NASA Technical Reports Server (NTRS)

1971-01-01

The design plan requirements define the design implementation and control requirements for Phase C/D of the Modular Space Station Project and specifically address the Initial Space Station phase of the Space Station Program (modular). It is based primarily on the specific objective of translating the requirements of the Space Station Program, Project, Interface, and Support Requirements and preliminary contract end x item specifications into detail design of the operational systems which comprise the initial space station. This document is designed to guide aerospace contractors in the planning and bidding for Phase C/D.

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.

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.

Integrated Information Support System (IISS). Volume 8. User Interface Subsystem. Part 39. Electronic Documentation System (EDS) User’s Manual

DTIC Science & Technology

1990-09-30

conveying any rights or permission to manufacture, use, or market any patented invention that may in any way be related thereto. This technical report...Definition - Select .... 7-9 7-6 Character Class Definition - Other Options 7-10 7-7 Pattern/Action/State Defintion -Select 7-11 7-8 Pattern/Action/State...representation. Compound Document: A document which may contain mixed content i.e. text, graphics, etc. Conforming SGML Application: An SGML application that

Strength of the Subduction Plate Interface beneath the Seismogenic Zone: A Microstructural Investigation of Deformation Mechanisms within a Phyllosilicate- and Amphibole-rich Shear Zone

NASA Astrophysics Data System (ADS)

Seyler, C.; Kirkpatrick, J. D.; Šilerová, D.

2017-12-01

Localization of strain at plate boundaries requires rheological weakening of the lithosphere. The rheology of the subduction plate interface is dictated by the dominant grain-scale deformation mechanisms. However, little is known about the deformation mechanisms within phases commonly found in subduction zones, such as phyllosilicates and amphiboles. We investigate the Leech River Shear Zone on Vancouver Island, British Columbia to explore deformation processes downdip of the seismogenic zone and evaluate the bulk rheology of the plate interface. This shear zone juxtaposes a metamorphosed accretionary prism against a metabasaltic oceanic plateau, representing a paleo-plate interface from the ancient Cascadia subduction zone. Preliminary geothermometry results record a prograde deformation temperature of 573.6±11.2 ˚C in the overriding accretionary wedge, and the hornblende-chlorite-epidote-plagioclase mineral assemblage suggests upper greenschist to lower amphibolite facies metamorphism of the downgoing oceanic crust. Detailed mapping of the plate interface documents a 200 m wide mylonitic shear zone developed across the lithologic contact. Asymmetric shear fabrics, isoclinal folding, boudinage, and a steeply plunging, penetrative stretching lineation are consistent with sinistral-oblique subduction. Numerous discordant quartz veins are variably sheared into sigmoidal shapes as well as isoclinally folded and boudinaged, indicating cyclical synkinematic fracture and vein formation. At the grain-scale, interconnected, anastomosing layers of muscovite, chlorite, and graphite in the accretionary prism rocks likely deformed through kinking and dislocation glide. Framework minerals such as quartz and feldspar deformed by dislocation creep. In the metabasalt, hornblende and chlorite form a continuous S—C fabric in which asymmetric hornblende porphyroclasts deformed by rigid grain rotation and dissolution-precipitation creep. The strength of the subduction plate interface beneath the seismogenic zone was therefore controlled by multiple syn-kinematic mechanisms, with overall strength dominated by the rheology of phyllosilicates and amphibole, generating very low viscosities at the plate interface and enhancing strain localization.

National Geothermal Data System: Open Access to Geoscience Data, Maps, and Documents

NASA Astrophysics Data System (ADS)

Caudill, C. M.; Richard, S. M.; Musil, L.; Sonnenschein, A.; Good, J.

2014-12-01

The U.S. National Geothermal Data System (NGDS) provides free open access to millions of geoscience data records, publications, maps, and reports via distributed web services to propel geothermal research, development, and production. NGDS is built on the US Geoscience Information Network (USGIN) data integration framework, which is a joint undertaking of the USGS and the Association of American State Geologists (AASG), and is compliant with international standards and protocols. NGDS currently serves geoscience information from 60+ data providers in all 50 states. Free and open source software is used in this federated system where data owners maintain control of their data. This interactive online system makes geoscience data easily discoverable, accessible, and interoperable at no cost to users. The dynamic project site http://geothermaldata.org serves as the information source and gateway to the system, allowing data and applications discovery and availability of the system's data feed. It also provides access to NGDS specifications and the free and open source code base (on GitHub), a map-centric and library style search interface, other software applications utilizing NGDS services, NGDS tutorials (via YouTube and USGIN site), and user-created tools and scripts. The user-friendly map-centric web-based application has been created to support finding, visualizing, mapping, and acquisition of data based on topic, location, time, provider, or key words. Geographic datasets visualized through the map interface also allow users to inspect the details of individual GIS data points (e.g. wells, geologic units, etc.). In addition, the interface provides the information necessary for users to access the GIS data from third party software applications such as GoogleEarth, UDig, and ArcGIS. A redistributable, free and open source software package called GINstack (USGIN software stack) was also created to give data providers a simple way to release data using interoperable and shareable standards, upload data and documents, and expose those data as a node in the NGDS or any larger data system through a CSW endpoint. The easy-to-use interface is supported by back-end software including Postgres, GeoServer, and custom CKAN extensions among others.

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.

Network device interface for digitally interfacing data channels to a controller a via network

NASA Technical Reports Server (NTRS)

Konz, Daniel W. (Inventor); Ellerbrock, Philip J. (Inventor); Grant, Robert L. (Inventor); Winkelmann, Joseph P. (Inventor)

2006-01-01

The present invention provides a network device interface and method for digitally connecting a plurality of data channels to a controller using a network bus. The network device interface interprets commands and data received from the controller and polls the data channels in accordance with these commands. Specifically, the network device interface receives digital commands and data from the controller, and based on these commands and data, communicates with the data channels to either retrieve data in the case of a sensor or send data to activate an actuator. In one embodiment, the bus controller transmits messages to the network device interface containing a plurality of bits having a value defined by a transition between first and second states in the bits. The network device interface determines timing of the data sequence of the message and uses the determined timing to communicate with the bus controller.

Network device interface for digitally interfacing data channels to a controller via a network

NASA Technical Reports Server (NTRS)

Konz, Daniel W. (Inventor); Winkelmann, Joseph P. (Inventor); Ellerbrock, Philip J. (Inventor); Grant, Robert L. (Inventor)

2007-01-01

The present invention provides a network device interface and method for digitally connecting a plurality of data channels, such as sensors, actuators, and subsystems, to a controller using a network bus. The network device interface interprets commands and data received from the controller and polls the data channels in accordance with these commands. Specifically, the network device interface receives digital commands and data from the controller, and based on these commands and data, communicates with the data channels to either retrieve data in the case of a sensor or send data to activate an actuator. Data retrieved from the sensor is converted into digital signals and transmitted to the controller. In some embodiments, network device interfaces associated with different data channels coordinate communications with the other interfaces based on either a transition in a command message sent by the bus controller or a synchronous clock signal.

Network device interface for digitally interfacing data channels to a controller via a network

NASA Technical Reports Server (NTRS)

Ellerbrock, Philip J. (Inventor); Winkelmann, Joseph P. (Inventor); Grant, Robert L. (Inventor); Konz, Daniel W. (Inventor)

2006-01-01

The present invention provides a network device interface and method for digitally connecting a plurality of data channels, such as sensors, actuators, and subsystems, to a controller using a network bus. The network device interface interprets commands and data received from the controller and polls the data channels in accordance with these commands. Specifically, the network device interface receives digital commands and data from the controller, and based on these commands and data, communicates with the data channels to either retrieve data in the case of a sensor or send data to activate an actuator. Data retrieved from the sensor is then converted by the network device interface into digital signals and transmitted back to the controller. In one advantageous embodiment, the network device interface is a state machine, such as an ASIC, that operates independent of a processor in communicating with the bus controller and data channels.

Digital-flight-control-system software written in automated-engineering-design language: A user's guide of verification and validation tools

NASA Technical Reports Server (NTRS)

Saito, Jim

1987-01-01

The user guide of verification and validation (V&V) tools for the Automated Engineering Design (AED) language is specifically written to update the information found in several documents pertaining to the automated verification of flight software tools. The intent is to provide, in one document, all the information necessary to adequately prepare a run to use the AED V&V tools. No attempt is made to discuss the FORTRAN V&V tools since they were not updated and are not currently active. Additionally, the current descriptions of the AED V&V tools are contained and provides information to augment the NASA TM 84276. The AED V&V tools are accessed from the digital flight control systems verification laboratory (DFCSVL) via a PDP-11/60 digital computer. The AED V&V tool interface handlers on the PDP-11/60 generate a Univac run stream which is transmitted to the Univac via a Remote Job Entry (RJE) link. Job execution takes place on the Univac 1100 and the job output is transmitted back to the DFCSVL and stored as a PDP-11/60 printfile.

Database interfaces on NASA's heterogeneous distributed database system

NASA Technical Reports Server (NTRS)

Huang, Shou-Hsuan Stephen

1989-01-01

The syntax and semantics of all commands used in the template are described. Template builders should consult this document for proper commands in the template. Previous documents (Semiannual reports) described other aspects of this project. Appendix 1 contains all substituting commands used in the system. Appendix 2 includes all repeating commands. Appendix 3 is a collection of DEFINE templates from eight different DBMS's.

Small cause - big effect: improvement in interface design results in improved data quality - a multicenter crossover study.

PubMed

Ahlbrandt, Janko; Henrich, Michael; Hartmann, Bernd A; Bundschuh, Bettina B; Schwarz, Julia; Klasen, Joachim; Röhrig, Rainer

2012-01-01

In Germany the core data set for anesthesia version 3.0 was recently introduced for external quality assurance, which includes five surgical tracer procedures. We found a low rate of correctly documented tracers when compared to procedure data (OPS-Codes) documented separately. Examination revealed that the graphical user interface (GUI) contravened the dialogue principles as defined in EN ISO 9241-110. We worked with the manufacturer to implement small improvements and roll out the software. A crossover study was conducted at a university hospital and a municipal hospital chain with five hospitals. All study sites and surgical tracer procedures combined, we found an improvement from 42% to 65% (p<0.001; N=34,610) correctly documented anesthesias. We also saw improvements for most of the observed surgical tracer procedures at all hospitals. Our results show the big effect small changes to the GUI can have on data quality. They also raise the question, if highly flexible and parameterized clinical documentation systems are suited to achieve high usability. Finding the right balance between GUIs designed by usability experts and the flexibility of parameterization by administrators will be a difficult task for the future and subject to further research.

Issues in the design of a pilot concept-based query interface for the neuroinformatics information framework.

PubMed

Marenco, Luis; Li, Yuli; Martone, Maryann E; Sternberg, Paul W; Shepherd, Gordon M; Miller, Perry L

2008-09-01

This paper describes a pilot query interface that has been constructed to help us explore a "concept-based" approach for searching the Neuroscience Information Framework (NIF). The query interface is concept-based in the sense that the search terms submitted through the interface are selected from a standardized vocabulary of terms (concepts) that are structured in the form of an ontology. The NIF contains three primary resources: the NIF Resource Registry, the NIF Document Archive, and the NIF Database Mediator. These NIF resources are very different in their nature and therefore pose challenges when designing a single interface from which searches can be automatically launched against all three resources simultaneously. The paper first discusses briefly several background issues involving the use of standardized biomedical vocabularies in biomedical information retrieval, and then presents a detailed example that illustrates how the pilot concept-based query interface operates. The paper concludes by discussing certain lessons learned in the development of the current version of the interface.

NELS 2.0 - A general system for enterprise wide information management

NASA Technical Reports Server (NTRS)

Smith, Stephanie L.

1993-01-01

NELS, the NASA Electronic Library System, is an information management tool for creating distributed repositories of documents, drawings, and code for use and reuse by the aerospace community. The NELS retrieval engine can load metadata and source files of full text objects, perform natural language queries to retrieve ranked objects, and create links to connect user interfaces. For flexibility, the NELS architecture has layered interfaces between the application program and the stored library information. The session manager provides the interface functions for development of NELS applications. The data manager is an interface between session manager and the structured data system. The center of the structured data system is the Wide Area Information Server. This system architecture provides access to information across heterogeneous platforms in a distributed environment. There are presently three user interfaces that connect to the NELS engine; an X-Windows interface, and ASCII interface and the Spatial Data Management System. This paper describes the design and operation of NELS as an information management tool and repository.

Issues in the Design of a Pilot Concept-Based Query Interface for the Neuroinformatics Information Framework

PubMed Central

Li, Yuli; Martone, Maryann E.; Sternberg, Paul W.; Shepherd, Gordon M.; Miller, Perry L.

2009-01-01

This paper describes a pilot query interface that has been constructed to help us explore a “concept-based” approach for searching the Neuroscience Information Framework (NIF). The query interface is concept-based in the sense that the search terms submitted through the interface are selected from a standardized vocabulary of terms (concepts) that are structured in the form of an ontology. The NIF contains three primary resources: the NIF Resource Registry, the NIF Document Archive, and the NIF Database Mediator. These NIF resources are very different in their nature and therefore pose challenges when designing a single interface from which searches can be automatically launched against all three resources simultaneously. The paper first discusses briefly several background issues involving the use of standardized biomedical vocabularies in biomedical information retrieval, and then presents a detailed example that illustrates how the pilot concept-based query interface operates. The paper concludes by discussing certain lessons learned in the development of the current version of the interface. PMID:18953674

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.

1993-01-01

NASA Lewis Research Center has applied artificial intelligence to an advanced ground terminal. This software application is being deployed as an experimenter interface to the link evaluation terminal (LET) and was named Space Communication Artificial Intelligence for the Link Evaluation Terminal (SCAILET). The high-burst-rate (HBR) LET provides 30-GHz-transmitting and 20-GHz-receiving, 220-Mbps capability for wide band communications technology experiments with the Advanced Communication Technology Satellite (ACTS). The HBR-LET terminal consists of seven major subsystems. A minicomputer controls and monitors these subsystems through an IEEE-488 or RS-232 protocol interface. Programming scripts (test procedures defined by design engineers) configure the HBR-LET and permit data acquisition. However, the scripts are difficult to use, require a steep learning curve, are cryptic, and are hard to maintain. This discourages experimenters from utilizing the full capabilities of the HBR-LET system. An intelligent assistant module was developed as part of the SCAILET software. The intelligent assistant addresses critical experimenter needs by solving and resolving problems that are encountered during the configuring of the HBR-LET system. The intelligent assistant is a graphical user interface with an expert system running in the background. In order to further assist and familiarize an experimenter, an on-line hypertext documentation module was developed and included in the SCAILET software.

Supervisory Control System Architecture for Advanced Small Modular Reactors

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

Cetiner, Sacit M; Cole, Daniel L; Fugate, David L

2013-08-01

This technical report was generated as a product of the Supervisory Control for Multi-Modular SMR Plants project within the Instrumentation, Control and Human-Machine Interface technology area under the Advanced Small Modular Reactor (SMR) Research and Development Program of the U.S. Department of Energy. The report documents the definition of strategies, functional elements, and the structural architecture of a supervisory control system for multi-modular advanced SMR (AdvSMR) plants. This research activity advances the state-of-the art by incorporating decision making into the supervisory control system architectural layers through the introduction of a tiered-plant system approach. The report provides a brief history ofmore » hierarchical functional architectures and the current state-of-the-art, describes a reference AdvSMR to show the dependencies between systems, presents a hierarchical structure for supervisory control, indicates the importance of understanding trip setpoints, applies a new theoretic approach for comparing architectures, identifies cyber security controls that should be addressed early in system design, and describes ongoing work to develop system requirements and hardware/software configurations.« less

TAE+ 5.2 - TRANSPORTABLE APPLICATIONS ENVIRONMENT PLUS, VERSION 5.2 (HP9000 SERIES 700/800 VERSION)

NASA Technical Reports Server (NTRS)

TAE SUPPORT OFFICE

1994-01-01

TAE (Transportable Applications Environment) Plus is an integrated, portable environment for developing and running interactive window, text, and graphical object-based application systems. The program allows both programmers and non-programmers to easily construct their own custom application interface and to move that interface and application to different machine environments. TAE Plus makes both the application and the machine environment transparent, with noticeable improvements in the learning curve. The main components of TAE Plus are as follows: (1) the WorkBench, a What You See Is What You Get (WYSIWYG) tool for the design and layout of a user interface; (2) the Window Programming Tools Package (WPT), a set of callable subroutines that control an application's user interface; and (3) TAE Command Language (TCL), an easy-to-learn command language that provides an easy way to develop an executable application prototype with a run-time interpreted language. The WorkBench tool allows the application developer to interactively construct the layout of an application's display screen by manipulating a set of interaction objects including input items such as buttons, icons, and scrolling text lists. User interface interactive objects include data-driven graphical objects such as dials, thermometers, and strip charts as well as menubars, option menus, file selection items, message items, push buttons, and color loggers. The WorkBench user specifies the windows and interaction objects that will make up the user interface, then specifies the sequence of the user interface dialogue. The description of the designed user interface is then saved into resource files. For those who desire to develop the designed user interface into an operational application, the WorkBench tool also generates source code (C, C++, Ada, and TCL) which fully controls the application's user interface through function calls to the WPTs. The WPTs are the runtime services used by application programs to display and control the user interfaces. Since the WPTs access the workbench-generated resource files during each execution, details such as color, font, location, and object type remain independent from the application code, allowing changes to the user interface without recompiling and relinking. In addition to WPTs, TAE Plus can control interaction of objects from the interpreted TAE Command Language. TCL provides a means for the more experienced developer to quickly prototype an application's use of TAE Plus interaction objects and add programming logic without the overhead of compiling or linking. TAE Plus requires MIT's X Window System and the Open Software Foundation's Motif. The HP 9000 Series 700/800 version of TAE 5.2 requires Version 11 Release 5 of the X Window System. All other machine versions of TAE 5.2 require Version 11, Release 4 of the X Window System. The Workbench and WPTs are written in C++ and the remaining code is written in C. TAE Plus is available by license for an unlimited time period. The licensed program product includes the TAE Plus source code and one set of supporting documentation. Additional documentation may be purchased separately at the price indicated below. The amount of disk space required to load the TAE Plus tar format tape is between 35Mb and 67Mb depending on the machine version. The recommended minimum memory is 12Mb. Each TAE Plus platform delivery tape includes pre-built libraries and executable binary code for that particular machine, as well as source code, so users do not have to do an installation. Users wishing to recompile the source will need both a C compiler and either GNU's C++ Version 1.39 or later, or a C++ compiler based on AT&T 2.0 cfront. TAE Plus was developed in 1989 and version 5.2 was released in 1993. TAE Plus 5.2 is available on media suitable for five different machine platforms: (1) IBM RS/6000 series workstations running AIX (.25 inch tape cartridge in UNIX tar format), (2) DEC RISC workstations running ULTRIX (TK50 cartridge in UNIX tar format), (3) HP9000 Series 700/800 computers running HP-UX 9.x and X11/R5 (HP 4mm DDS DAT tape cartridge in UNIX tar format), (4) Sun4 (SPARC) series computers running SunOS (.25 inch tape cartridge in UNIX tar format), and (5) SGI Indigo computers running IRIX (.25 inch IRIS tape cartridge in UNIX tar format). Please contact COSMIC to obtain detailed information about the supported operating system and OSF/Motif releases required for each of these machine versions. An optional Motif Object Code License is available for the Sun4 version of TAE Plus 5.2. Version 5.1 of TAE Plus remains available for DEC VAX computers running VMS, HP9000 Series 300/400 computers running HP-UX, and HP 9000 Series 700/800 computers running HP-UX 8.x and X11/R4. Please contact COSMIC for details on these versions of TAE Plus.

TAE+ 5.2 - TRANSPORTABLE APPLICATIONS ENVIRONMENT PLUS, VERSION 5.2 (IBM RS/6000 VERSION)

NASA Technical Reports Server (NTRS)

TAE SUPPORT OFFICE

1994-01-01

TAE (Transportable Applications Environment) Plus is an integrated, portable environment for developing and running interactive window, text, and graphical object-based application systems. The program allows both programmers and non-programmers to easily construct their own custom application interface and to move that interface and application to different machine environments. TAE Plus makes both the application and the machine environment transparent, with noticeable improvements in the learning curve. The main components of TAE Plus are as follows: (1) the WorkBench, a What You See Is What You Get (WYSIWYG) tool for the design and layout of a user interface; (2) the Window Programming Tools Package (WPT), a set of callable subroutines that control an application's user interface; and (3) TAE Command Language (TCL), an easy-to-learn command language that provides an easy way to develop an executable application prototype with a run-time interpreted language. The WorkBench tool allows the application developer to interactively construct the layout of an application's display screen by manipulating a set of interaction objects including input items such as buttons, icons, and scrolling text lists. User interface interactive objects include data-driven graphical objects such as dials, thermometers, and strip charts as well as menubars, option menus, file selection items, message items, push buttons, and color loggers. The WorkBench user specifies the windows and interaction objects that will make up the user interface, then specifies the sequence of the user interface dialogue. The description of the designed user interface is then saved into resource files. For those who desire to develop the designed user interface into an operational application, the WorkBench tool also generates source code (C, C++, Ada, and TCL) which fully controls the application's user interface through function calls to the WPTs. The WPTs are the runtime services used by application programs to display and control the user interfaces. Since the WPTs access the workbench-generated resource files during each execution, details such as color, font, location, and object type remain independent from the application code, allowing changes to the user interface without recompiling and relinking. In addition to WPTs, TAE Plus can control interaction of objects from the interpreted TAE Command Language. TCL provides a means for the more experienced developer to quickly prototype an application's use of TAE Plus interaction objects and add programming logic without the overhead of compiling or linking. TAE Plus requires MIT's X Window System and the Open Software Foundation's Motif. The HP 9000 Series 700/800 version of TAE 5.2 requires Version 11 Release 5 of the X Window System. All other machine versions of TAE 5.2 require Version 11, Release 4 of the X Window System. The Workbench and WPTs are written in C++ and the remaining code is written in C. TAE Plus is available by license for an unlimited time period. The licensed program product includes the TAE Plus source code and one set of supporting documentation. Additional documentation may be purchased separately at the price indicated below. The amount of disk space required to load the TAE Plus tar format tape is between 35Mb and 67Mb depending on the machine version. The recommended minimum memory is 12Mb. Each TAE Plus platform delivery tape includes pre-built libraries and executable binary code for that particular machine, as well as source code, so users do not have to do an installation. Users wishing to recompile the source will need both a C compiler and either GNU's C++ Version 1.39 or later, or a C++ compiler based on AT&T 2.0 cfront. TAE Plus was developed in 1989 and version 5.2 was released in 1993. TAE Plus 5.2 is available on media suitable for five different machine platforms: (1) IBM RS/6000 series workstations running AIX (.25 inch tape cartridge in UNIX tar format), (2) DEC RISC workstations running ULTRIX (TK50 cartridge in UNIX tar format), (3) HP9000 Series 700/800 computers running HP-UX 9.x and X11/R5 (HP 4mm DDS DAT tape cartridge in UNIX tar format), (4) Sun4 (SPARC) series computers running SunOS (.25 inch tape cartridge in UNIX tar format), and (5) SGI Indigo computers running IRIX (.25 inch IRIS tape cartridge in UNIX tar format). Please contact COSMIC to obtain detailed information about the supported operating system and OSF/Motif releases required for each of these machine versions. An optional Motif Object Code License is available for the Sun4 version of TAE Plus 5.2. Version 5.1 of TAE Plus remains available for DEC VAX computers running VMS, HP9000 Series 300/400 computers running HP-UX, and HP 9000 Series 700/800 computers running HP-UX 8.x and X11/R4. Please contact COSMIC for details on these versions of TAE Plus.

TAE+ 5.2 - TRANSPORTABLE APPLICATIONS ENVIRONMENT PLUS, VERSION 5.2 (SUN4 VERSION WITH MOTIF)

NASA Technical Reports Server (NTRS)

TAE SUPPORT OFFICE

1994-01-01

TAE (Transportable Applications Environment) Plus is an integrated, portable environment for developing and running interactive window, text, and graphical object-based application systems. The program allows both programmers and non-programmers to easily construct their own custom application interface and to move that interface and application to different machine environments. TAE Plus makes both the application and the machine environment transparent, with noticeable improvements in the learning curve. The main components of TAE Plus are as follows: (1) the WorkBench, a What You See Is What You Get (WYSIWYG) tool for the design and layout of a user interface; (2) the Window Programming Tools Package (WPT), a set of callable subroutines that control an application's user interface; and (3) TAE Command Language (TCL), an easy-to-learn command language that provides an easy way to develop an executable application prototype with a run-time interpreted language. The WorkBench tool allows the application developer to interactively construct the layout of an application's display screen by manipulating a set of interaction objects including input items such as buttons, icons, and scrolling text lists. User interface interactive objects include data-driven graphical objects such as dials, thermometers, and strip charts as well as menubars, option menus, file selection items, message items, push buttons, and color loggers. The WorkBench user specifies the windows and interaction objects that will make up the user interface, then specifies the sequence of the user interface dialogue. The description of the designed user interface is then saved into resource files. For those who desire to develop the designed user interface into an operational application, the WorkBench tool also generates source code (C, C++, Ada, and TCL) which fully controls the application's user interface through function calls to the WPTs. The WPTs are the runtime services used by application programs to display and control the user interfaces. Since the WPTs access the workbench-generated resource files during each execution, details such as color, font, location, and object type remain independent from the application code, allowing changes to the user interface without recompiling and relinking. In addition to WPTs, TAE Plus can control interaction of objects from the interpreted TAE Command Language. TCL provides a means for the more experienced developer to quickly prototype an application's use of TAE Plus interaction objects and add programming logic without the overhead of compiling or linking. TAE Plus requires MIT's X Window System and the Open Software Foundation's Motif. The HP 9000 Series 700/800 version of TAE 5.2 requires Version 11 Release 5 of the X Window System. All other machine versions of TAE 5.2 require Version 11, Release 4 of the X Window System. The Workbench and WPTs are written in C++ and the remaining code is written in C. TAE Plus is available by license for an unlimited time period. The licensed program product includes the TAE Plus source code and one set of supporting documentation. Additional documentation may be purchased separately at the price indicated below. The amount of disk space required to load the TAE Plus tar format tape is between 35Mb and 67Mb depending on the machine version. The recommended minimum memory is 12Mb. Each TAE Plus platform delivery tape includes pre-built libraries and executable binary code for that particular machine, as well as source code, so users do not have to do an installation. Users wishing to recompile the source will need both a C compiler and either GNU's C++ Version 1.39 or later, or a C++ compiler based on AT&T 2.0 cfront. TAE Plus was developed in 1989 and version 5.2 was released in 1993. TAE Plus 5.2 is available on media suitable for five different machine platforms: (1) IBM RS/6000 series workstations running AIX (.25 inch tape cartridge in UNIX tar format), (2) DEC RISC workstations running ULTRIX (TK50 cartridge in UNIX tar format), (3) HP9000 Series 700/800 computers running HP-UX 9.x and X11/R5 (HP 4mm DDS DAT tape cartridge in UNIX tar format), (4) Sun4 (SPARC) series computers running SunOS (.25 inch tape cartridge in UNIX tar format), and (5) SGI Indigo computers running IRIX (.25 inch IRIS tape cartridge in UNIX tar format). Please contact COSMIC to obtain detailed information about the supported operating system and OSF/Motif releases required for each of these machine versions. An optional Motif Object Code License is available for the Sun4 version of TAE Plus 5.2. Version 5.1 of TAE Plus remains available for DEC VAX computers running VMS, HP9000 Series 300/400 computers running HP-UX, and HP 9000 Series 700/800 computers running HP-UX 8.x and X11/R4. Please contact COSMIC for details on these versions of TAE Plus.

TAE+ 5.2 - TRANSPORTABLE APPLICATIONS ENVIRONMENT PLUS, VERSION 5.2 (SILICON GRAPHICS VERSION)

NASA Technical Reports Server (NTRS)

TAE SUPPORT OFFICE

1994-01-01

TAE (Transportable Applications Environment) Plus is an integrated, portable environment for developing and running interactive window, text, and graphical object-based application systems. The program allows both programmers and non-programmers to easily construct their own custom application interface and to move that interface and application to different machine environments. TAE Plus makes both the application and the machine environment transparent, with noticeable improvements in the learning curve. The main components of TAE Plus are as follows: (1) the WorkBench, a What You See Is What You Get (WYSIWYG) tool for the design and layout of a user interface; (2) the Window Programming Tools Package (WPT), a set of callable subroutines that control an application's user interface; and (3) TAE Command Language (TCL), an easy-to-learn command language that provides an easy way to develop an executable application prototype with a run-time interpreted language. The WorkBench tool allows the application developer to interactively construct the layout of an application's display screen by manipulating a set of interaction objects including input items such as buttons, icons, and scrolling text lists. User interface interactive objects include data-driven graphical objects such as dials, thermometers, and strip charts as well as menubars, option menus, file selection items, message items, push buttons, and color loggers. The WorkBench user specifies the windows and interaction objects that will make up the user interface, then specifies the sequence of the user interface dialogue. The description of the designed user interface is then saved into resource files. For those who desire to develop the designed user interface into an operational application, the WorkBench tool also generates source code (C, C++, Ada, and TCL) which fully controls the application's user interface through function calls to the WPTs. The WPTs are the runtime services used by application programs to display and control the user interfaces. Since the WPTs access the workbench-generated resource files during each execution, details such as color, font, location, and object type remain independent from the application code, allowing changes to the user interface without recompiling and relinking. In addition to WPTs, TAE Plus can control interaction of objects from the interpreted TAE Command Language. TCL provides a means for the more experienced developer to quickly prototype an application's use of TAE Plus interaction objects and add programming logic without the overhead of compiling or linking. TAE Plus requires MIT's X Window System and the Open Software Foundation's Motif. The HP 9000 Series 700/800 version of TAE 5.2 requires Version 11 Release 5 of the X Window System. All other machine versions of TAE 5.2 require Version 11, Release 4 of the X Window System. The Workbench and WPTs are written in C++ and the remaining code is written in C. TAE Plus is available by license for an unlimited time period. The licensed program product includes the TAE Plus source code and one set of supporting documentation. Additional documentation may be purchased separately at the price indicated below. The amount of disk space required to load the TAE Plus tar format tape is between 35Mb and 67Mb depending on the machine version. The recommended minimum memory is 12Mb. Each TAE Plus platform delivery tape includes pre-built libraries and executable binary code for that particular machine, as well as source code, so users do not have to do an installation. Users wishing to recompile the source will need both a C compiler and either GNU's C++ Version 1.39 or later, or a C++ compiler based on AT&T 2.0 cfront. TAE Plus was developed in 1989 and version 5.2 was released in 1993. TAE Plus 5.2 is available on media suitable for five different machine platforms: (1) IBM RS/6000 series workstations running AIX (.25 inch tape cartridge in UNIX tar format), (2) DEC RISC workstations running ULTRIX (TK50 cartridge in UNIX tar format), (3) HP9000 Series 700/800 computers running HP-UX 9.x and X11/R5 (HP 4mm DDS DAT tape cartridge in UNIX tar format), (4) Sun4 (SPARC) series computers running SunOS (.25 inch tape cartridge in UNIX tar format), and (5) SGI Indigo computers running IRIX (.25 inch IRIS tape cartridge in UNIX tar format). Please contact COSMIC to obtain detailed information about the supported operating system and OSF/Motif releases required for each of these machine versions. An optional Motif Object Code License is available for the Sun4 version of TAE Plus 5.2. Version 5.1 of TAE Plus remains available for DEC VAX computers running VMS, HP9000 Series 300/400 computers running HP-UX, and HP 9000 Series 700/800 computers running HP-UX 8.x and X11/R4. Please contact COSMIC for details on these versions of TAE Plus.

TAE+ 5.2 - TRANSPORTABLE APPLICATIONS ENVIRONMENT PLUS, VERSION 5.2 (SUN4 VERSION)

NASA Technical Reports Server (NTRS)

TAE SUPPORT OFFICE

1994-01-01

TAE (Transportable Applications Environment) Plus is an integrated, portable environment for developing and running interactive window, text, and graphical object-based application systems. The program allows both programmers and non-programmers to easily construct their own custom application interface and to move that interface and application to different machine environments. TAE Plus makes both the application and the machine environment transparent, with noticeable improvements in the learning curve. The main components of TAE Plus are as follows: (1) the WorkBench, a What You See Is What You Get (WYSIWYG) tool for the design and layout of a user interface; (2) the Window Programming Tools Package (WPT), a set of callable subroutines that control an application's user interface; and (3) TAE Command Language (TCL), an easy-to-learn command language that provides an easy way to develop an executable application prototype with a run-time interpreted language. The WorkBench tool allows the application developer to interactively construct the layout of an application's display screen by manipulating a set of interaction objects including input items such as buttons, icons, and scrolling text lists. User interface interactive objects include data-driven graphical objects such as dials, thermometers, and strip charts as well as menubars, option menus, file selection items, message items, push buttons, and color loggers. The WorkBench user specifies the windows and interaction objects that will make up the user interface, then specifies the sequence of the user interface dialogue. The description of the designed user interface is then saved into resource files. For those who desire to develop the designed user interface into an operational application, the WorkBench tool also generates source code (C, C++, Ada, and TCL) which fully controls the application's user interface through function calls to the WPTs. The WPTs are the runtime services used by application programs to display and control the user interfaces. Since the WPTs access the workbench-generated resource files during each execution, details such as color, font, location, and object type remain independent from the application code, allowing changes to the user interface without recompiling and relinking. In addition to WPTs, TAE Plus can control interaction of objects from the interpreted TAE Command Language. TCL provides a means for the more experienced developer to quickly prototype an application's use of TAE Plus interaction objects and add programming logic without the overhead of compiling or linking. TAE Plus requires MIT's X Window System and the Open Software Foundation's Motif. The HP 9000 Series 700/800 version of TAE 5.2 requires Version 11 Release 5 of the X Window System. All other machine versions of TAE 5.2 require Version 11, Release 4 of the X Window System. The Workbench and WPTs are written in C++ and the remaining code is written in C. TAE Plus is available by license for an unlimited time period. The licensed program product includes the TAE Plus source code and one set of supporting documentation. Additional documentation may be purchased separately at the price indicated below. The amount of disk space required to load the TAE Plus tar format tape is between 35Mb and 67Mb depending on the machine version. The recommended minimum memory is 12Mb. Each TAE Plus platform delivery tape includes pre-built libraries and executable binary code for that particular machine, as well as source code, so users do not have to do an installation. Users wishing to recompile the source will need both a C compiler and either GNU's C++ Version 1.39 or later, or a C++ compiler based on AT&T 2.0 cfront. TAE Plus was developed in 1989 and version 5.2 was released in 1993. TAE Plus 5.2 is available on media suitable for five different machine platforms: (1) IBM RS/6000 series workstations running AIX (.25 inch tape cartridge in UNIX tar format), (2) DEC RISC workstations running ULTRIX (TK50 cartridge in UNIX tar format), (3) HP9000 Series 700/800 computers running HP-UX 9.x and X11/R5 (HP 4mm DDS DAT tape cartridge in UNIX tar format), (4) Sun4 (SPARC) series computers running SunOS (.25 inch tape cartridge in UNIX tar format), and (5) SGI Indigo computers running IRIX (.25 inch IRIS tape cartridge in UNIX tar format). Please contact COSMIC to obtain detailed information about the supported operating system and OSF/Motif releases required for each of these machine versions. An optional Motif Object Code License is available for the Sun4 version of TAE Plus 5.2. Version 5.1 of TAE Plus remains available for DEC VAX computers running VMS, HP9000 Series 300/400 computers running HP-UX, and HP 9000 Series 700/800 computers running HP-UX 8.x and X11/R4. Please contact COSMIC for details on these versions of TAE Plus.

TAE+ 5.2 - TRANSPORTABLE APPLICATIONS ENVIRONMENT PLUS, VERSION 5.2 (DEC RISC ULTRIX VERSION)

NASA Technical Reports Server (NTRS)

TAE SUPPORT OFFICE

1994-01-01

TAE (Transportable Applications Environment) Plus is an integrated, portable environment for developing and running interactive window, text, and graphical object-based application systems. The program allows both programmers and non-programmers to easily construct their own custom application interface and to move that interface and application to different machine environments. TAE Plus makes both the application and the machine environment transparent, with noticeable improvements in the learning curve. The main components of TAE Plus are as follows: (1) the WorkBench, a What You See Is What You Get (WYSIWYG) tool for the design and layout of a user interface; (2) the Window Programming Tools Package (WPT), a set of callable subroutines that control an application's user interface; and (3) TAE Command Language (TCL), an easy-to-learn command language that provides an easy way to develop an executable application prototype with a run-time interpreted language. The WorkBench tool allows the application developer to interactively construct the layout of an application's display screen by manipulating a set of interaction objects including input items such as buttons, icons, and scrolling text lists. User interface interactive objects include data-driven graphical objects such as dials, thermometers, and strip charts as well as menubars, option menus, file selection items, message items, push buttons, and color loggers. The WorkBench user specifies the windows and interaction objects that will make up the user interface, then specifies the sequence of the user interface dialogue. The description of the designed user interface is then saved into resource files. For those who desire to develop the designed user interface into an operational application, the WorkBench tool also generates source code (C, C++, Ada, and TCL) which fully controls the application's user interface through function calls to the WPTs. The WPTs are the runtime services used by application programs to display and control the user interfaces. Since the WPTs access the workbench-generated resource files during each execution, details such as color, font, location, and object type remain independent from the application code, allowing changes to the user interface without recompiling and relinking. In addition to WPTs, TAE Plus can control interaction of objects from the interpreted TAE Command Language. TCL provides a means for the more experienced developer to quickly prototype an application's use of TAE Plus interaction objects and add programming logic without the overhead of compiling or linking. TAE Plus requires MIT's X Window System and the Open Software Foundation's Motif. The HP 9000 Series 700/800 version of TAE 5.2 requires Version 11 Release 5 of the X Window System. All other machine versions of TAE 5.2 require Version 11, Release 4 of the X Window System. The Workbench and WPTs are written in C++ and the remaining code is written in C. TAE Plus is available by license for an unlimited time period. The licensed program product includes the TAE Plus source code and one set of supporting documentation. Additional documentation may be purchased separately at the price indicated below. The amount of disk space required to load the TAE Plus tar format tape is between 35Mb and 67Mb depending on the machine version. The recommended minimum memory is 12Mb. Each TAE Plus platform delivery tape includes pre-built libraries and executable binary code for that particular machine, as well as source code, so users do not have to do an installation. Users wishing to recompile the source will need both a C compiler and either GNU's C++ Version 1.39 or later, or a C++ compiler based on AT&T 2.0 cfront. TAE Plus was developed in 1989 and version 5.2 was released in 1993. TAE Plus 5.2 is available on media suitable for five different machine platforms: (1) IBM RS/6000 series workstations running AIX (.25 inch tape cartridge in UNIX tar format), (2) DEC RISC workstations running ULTRIX (TK50 cartridge in UNIX tar format), (3) HP9000 Series 700/800 computers running HP-UX 9.x and X11/R5 (HP 4mm DDS DAT tape cartridge in UNIX tar format), (4) Sun4 (SPARC) series computers running SunOS (.25 inch tape cartridge in UNIX tar format), and (5) SGI Indigo computers running IRIX (.25 inch IRIS tape cartridge in UNIX tar format). Please contact COSMIC to obtain detailed information about the supported operating system and OSF/Motif releases required for each of these machine versions. An optional Motif Object Code License is available for the Sun4 version of TAE Plus 5.2. Version 5.1 of TAE Plus remains available for DEC VAX computers running VMS, HP9000 Series 300/400 computers running HP-UX, and HP 9000 Series 700/800 computers running HP-UX 8.x and X11/R4. Please contact COSMIC for details on these versions of TAE Plus.

Switch configuration for migration to optical fiber network

NASA Technical Reports Server (NTRS)

Zobrist, George W.

1993-01-01

The purpose is to investigate the migration of an Ethernet LAN segment to fiber optics. At the present time it is proposed to support a Fiber Distributed Data Interface (FDDI) backbone and to upgrade the VAX cluster to fiber optic interface. Possibly some workstations will have an FDDI interface. The remaining stations on the Ethernet LAN will be segmented. The rationale for migrating from the present Ethernet configuration to a fiber optic backbone is due to the increase in the number of workstations and the movement of applications to a windowing environment, extensive document transfers, and compute intensive applications.

Fire in the wildland-urban interface: Selecting and maintaining firewise plants for landscaping

Treesearch

J. Douglas Doran; Cotton K. Randall; Alan J. Long

2004-01-01

One of the major issues in the southern wildland-urban interface is the loss of homes to wildfire. For homeowners who live in an area with a medium to high risk of wildfire, this document provides useful information for protecting your property (see University of Florida/IFAS publication FOR 71 "Landscaping in Florida with Fire in Mind” to determine your wildfire...

The NASA Mission Operations and Control Architecture Program

NASA Technical Reports Server (NTRS)

Ondrus, Paul J.; Carper, Richard D.; Jeffries, Alan J.

1994-01-01

The conflict between increases in space mission complexity and rapidly declining space mission budgets has created strong pressures to radically reduce the costs of designing and operating spacecraft. A key approach to achieving such reductions is through reducing the development and operations costs of the supporting mission operations systems. One of the efforts which the Communications and Data Systems Division at NASA Headquarters is using to meet this challenge is the Mission Operations Control Architecture (MOCA) project. Technical direction of this effort has been delegated to the Mission Operations Division (MOD) of the Goddard Space Flight Center (GSFC). MOCA is to develop a mission control and data acquisition architecture, and supporting standards, to guide the development of future spacecraft and mission control facilities at GSFC. The architecture will reduce the need for around-the-clock operations staffing, obtain a high level of reuse of flight and ground software elements from mission to mission, and increase overall system flexibility by enabling the migration of appropriate functions from the ground to the spacecraft. The end results are to be an established way of designing the spacecraft-ground system interface for GSFC's in-house developed spacecraft, and a specification of the end to end spacecraft control process, including data structures, interfaces, and protocols, suitable for inclusion in solicitation documents for future flight spacecraft. A flight software kernel may be developed and maintained in a condition that it can be offered as Government Furnished Equipment in solicitations. This paper describes the MOCA project, its current status, and the results to date.

BCI2000: a general-purpose brain-computer interface (BCI) system.

PubMed

Schalk, Gerwin; McFarland, Dennis J; Hinterberger, Thilo; Birbaumer, Niels; Wolpaw, Jonathan R

2004-06-01

Many laboratories have begun to develop brain-computer interface (BCI) systems that provide communication and control capabilities to people with severe motor disabilities. Further progress and realization of practical applications depends on systematic evaluations and comparisons of different brain signals, recording methods, processing algorithms, output formats, and operating protocols. However, the typical BCI system is designed specifically for one particular BCI method and is, therefore, not suited to the systematic studies that are essential for continued progress. In response to this problem, we have developed a documented general-purpose BCI research and development platform called BCI2000. BCI2000 can incorporate alone or in combination any brain signals, signal processing methods, output devices, and operating protocols. This report is intended to describe to investigators, biomedical engineers, and computer scientists the concepts that the BC12000 system is based upon and gives examples of successful BCI implementations using this system. To date, we have used BCI2000 to create BCI systems for a variety of brain signals, processing methods, and applications. The data show that these systems function well in online operation and that BCI2000 satisfies the stringent real-time requirements of BCI systems. By substantially reducing labor and cost, BCI2000 facilitates the implementation of different BCI systems and other psychophysiological experiments. It is available with full documentation and free of charge for research or educational purposes and is currently being used in a variety of studies by many research groups.

Human performance interfaces in air traffic control.

PubMed

Chang, Yu-Hern; Yeh, Chung-Hsing

2010-01-01

This paper examines how human performance factors in air traffic control (ATC) affect each other through their mutual interactions. The paper extends the conceptual SHEL model of ergonomics to describe the ATC system as human performance interfaces in which the air traffic controllers interact with other human performance factors including other controllers, software, hardware, environment, and organisation. New research hypotheses about the relationships between human performance interfaces of the system are developed and tested on data collected from air traffic controllers, using structural equation modelling. The research result suggests that organisation influences play a more significant role than individual differences or peer influences on how the controllers interact with the software, hardware, and environment of the ATC system. There are mutual influences between the controller-software, controller-hardware, controller-environment, and controller-organisation interfaces of the ATC system, with the exception of the controller-controller interface. Research findings of this study provide practical insights in managing human performance interfaces of the ATC system in the face of internal or external change, particularly in understanding its possible consequences in relation to the interactions between human performance factors.

Network device interface for digitally interfacing data channels to a controller via a network

NASA Technical Reports Server (NTRS)

Konz, Daniel W. (Inventor); Ellerbrock, Philip J. (Inventor); Grant, Robert L. (Inventor); Winkelmann, Joseph P. (Inventor)

2006-01-01

The present invention provides a network device interface and method for digitally connecting a plurality of data channels, such as sensors, actuators, and subsystems, to a controller using a network bus. The network device interface interprets commands and data received from the controller and polls the data channels in accordance with these commands. Specifically, the network device interface receives digital commands and data from the controller, and based on these commands and data, communicates with the data channels to either retrieve data in the case of a sensor or send data to activate an actuator. Data retrieved from the sensor is then converted into digital signals and transmitted back to the controller. In one embodiment, the bus controller sends commands and data a defined bit rate, and the network device interface senses this bit rate and sends data back to the bus controller using the defined bit rate.

ISS and STS Commercial Off-the-Shelf Router Testing

NASA Technical Reports Server (NTRS)

Ivancie, William D.; Bell, Terry L.; Shell, Dan

2002-01-01

This report documents the results of testing performed with commercial off-the-shelf (COTS) routers and Internet Protocols (IPs) to determine if COTS equipment and IP could be utilized to upgrade NASA's current Space Transportation System (STS), the Shuttle, and the International Space Station communication infrastructure. Testing was performed by NASA Glenn Research Center (GRC) personnel within the Electronic Systems Test Laboratory (ESTE) with cooperation from the Mission Operations Directorate (MOD) Qualification and Utilization of Electronic System Technology (QUEST) personnel. The ESTE testing occurred between November 1 and 9, 2000. Additional testing was performed at NASA Glenn Research Center in a laboratory environment with equipment configured to emulate the STS. This report documents those tests and includes detailed test procedures, equipment interface requirements, test configurations and test results. The tests showed that a COTS router and standard Transmission Control Protocols and Internet Protocols (TCP/IP) could be used for both the Shuttle and the Space Station if near-error-free radio links are provided.

[Feather--data acquisition in gynaecology and obstetrics].

PubMed

Oppelt, P; Plathow, D; Oppelt, A; Stähler, J; Petrich, S; Scharl, A; Costa, S; Jesgarz, J; Kaufmann, M; Bergh, B

2002-07-01

Nowadays many types of medical documentation are based on computer facilities. Unfortunately, this involves the considerable disadvantage that almost every single department and specialty has its own software programs, with the physician having to learn a whole range of different programs. In addition, data sometimes have to be entered twice - since although open interfaces are often available, the elaborate programming required to transfer data from outside programs makes the financial costs too high. Since 1995 the University's of Frankfurt am Main Department of Gynecology and Obstetrics has therefore developed a consistent program of its own under Windows NT for in-patient facilities, as well as for some outpatient services. The program does not aim to achieve everything that is technically possible, but focuses primarily on user requirements. In addition to the general requirements for medical documentation in gynecology and obstetrics, the program can also handle perinatal inquiries and gynecological quality control (QSmed [Qualitätssicherung in der Medizin] of the BQS [Bundesgeschäftsstelle Qualitätssicherung]).

ForTrilinos Design Document

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

Young, Mitchell T.; Johnson, Seth R.; Prokopenko, Andrey V.

With the development of a Fortran Interface to Trilinos, ForTrilinos, modelers using modern Fortran will beable to provide their codes the capability to use solvers and other capabilities on exascale machines via astraightforward infrastructure that accesses Trilinos. This document outlines what Fortrilinos does andexplains briefly how it works. We show it provides a general access to packages via an entry point and usesan xml file from fortran code. With the first release, ForTrilinos will enable Teuchos to take xml parameterlists from Fortran code and set up data structures. It will provide access to linear solvers and eigensolvers.Several examples are providedmore » to illustrate the capabilities in practice. We explain what the user shouldhave already with their code and what Trilinos provides and returns to the Fortran code. We provideinformation about the build process for ForTrilinos, with a practical example. In future releases, nonlinearsolvers, time iteration, advanced preconditioning techniques, and inversion of control (IoC), to enablecallbacks to Fortran routines, will be available.« less

A polymer optoelectronic interface restores light sensitivity in blind rat retinas

NASA Astrophysics Data System (ADS)

Ghezzi, Diego; Antognazza, Maria Rosa; Maccarone, Rita; Bellani, Sebastiano; Lanzarini, Erica; Martino, Nicola; Mete, Maurizio; Pertile, Grazia; Bisti, Silvia; Lanzani, Guglielmo; Benfenati, Fabio

2013-05-01

Interfacing organic electronics with biological substrates offers new possibilities for biotechnology by taking advantage of the beneficial properties exhibited by organic conducting polymers. These polymers have been used for cellular interfaces in several applications, including cellular scaffolds, neural probes, biosensors and actuators for drug release. Recently, an organic photovoltaic blend has been used for neuronal stimulation via a photo-excitation process. Here, we document the use of a single-component organic film of poly(3-hexylthiophene) (P3HT) to trigger neuronal firing upon illumination. Moreover, we demonstrate that this bio-organic interface restores light sensitivity in explants of rat retinas with light-induced photoreceptor degeneration. These findings suggest that all-organic devices may play an important future role in subretinal prosthetic implants.

A polymer optoelectronic interface restores light sensitivity in blind rat retinas

PubMed Central

Ghezzi, Diego; Antognazza, Maria Rosa; Maccarone, Rita; Bellani, Sebastiano; Lanzarini, Erica; Martino, Nicola; Mete, Maurizio; Pertile, Grazia; Bisti, Silvia; Lanzani, Guglielmo; Benfenati, Fabio

2013-01-01

Interfacing organic electronics with biological substrates offers new possibilities for biotechnology due to the beneficial properties exhibited by organic conducting polymers. These polymers have been used for cellular interfaces in several fashions, including cellular scaffolds, neural probes, biosensors and actuators for drug release. Recently, an organic photovoltaic blend has been exploited for neuronal stimulation via a photo-excitation process. Here, we document the use of a single-component organic film of poly(3-hexylthiophene) (P3HT) to trigger neuronal firing upon illumination. Moreover, we demonstrate that this bio-organic interface restored light sensitivity in explants of rat retinas with light-induced photoreceptor degeneration. These findings suggest that all-organic devices may play an important future role in sub-retinal prosthetic implants. PMID:27158258

VIEWCACHE: An incremental pointer-base access method for distributed databases. Part 1: The universal index system design document. Part 2: The universal index system low-level design document. Part 3: User's guide. Part 4: Reference manual. Part 5: UIMS test suite

NASA Technical Reports Server (NTRS)

Kelley, Steve; Roussopoulos, Nick; Sellis, Timos

1992-01-01

The goal of the Universal Index System (UIS), is to provide an easy-to-use and reliable interface to many different kinds of database systems. The impetus for this system was to simplify database index management for users, thus encouraging the use of indexes. As the idea grew into an actual system design, the concept of increasing database performance by facilitating the use of time-saving techniques at the user level became a theme for the project. This Final Report describes the Design, the Implementation of UIS, and its Language Interfaces. It also includes the User's Guide and the Reference Manual.

Network device interface for digitally interfacing data channels to a controller via a network

NASA Technical Reports Server (NTRS)

Ellerbrock, Philip J. (Inventor); Grant, Robert L. (Inventor); Konz, Daniel W. (Inventor); Winkelmann, Joseph P. (Inventor)

2005-01-01

The present invention provides a network device interface and method for digitally connecting a plurality of data channels, such as sensors, actuators, and subsystems, to a controller using a network bus. The network device interface interprets commands and data received from the controller and polls the data channels in accordance with these commands. Specifically, the network device interface receives digital commands and data from the controller, and based on these commands and data, communicates with the data channels to either retrieve data in the case of a sensor or send data to activate an actuator. Data retrieved from the sensor is then converted by the network device interface into digital signals and transmitted back to the controller. In one advantageous embodiment, the network device interface uses a specialized protocol for communicating across the network bus that uses a low-level instruction set and has low overhead for data communication.

Network device interface for digitally interfacing data channels to a controller via a network

NASA Technical Reports Server (NTRS)

Ellerbrock, Philip J. (Inventor); Konz, Daniel W. (Inventor); Winkelmann, Joseph P. (Inventor); Grant, Robert L. (Inventor)

2004-01-01

The present invention provides a network device interface and method for digitally connecting a plurality of data channels, such as sensors, actuators, and subsystems, to a controller using a network bus. The network device interface interprets commands and data received from the controller and polls the data channels in accordance with these commands. Specifically, the network device interface receives digital commands and data from the controller, and based on these commands and data, communicates with the data channels to either retrieve data in the case of a sensor or send data to activate an actuator. Data retrieved from the sensor is then converted by the network device interface into digital signals and transmitted back to the controller. In one advantageous embodiment, the network device interface uses a specialized protocol for communicating across the network bus that uses a low-level instruction set and has low overhead for data communication.

Trans-Interface Optical Communication (TIOC)

DTIC Science & Technology

2008-01-01

communication interface 4. Bitmap stream creation 5. Display thread 6. DMD activeX control 7. DMD communication 8. System timing/control 9...o DMD activeX control o DMD communication o System timing/control o Graphical user interface (GUI) • All components are available for

Flash drive memory apparatus and method

NASA Technical Reports Server (NTRS)

Hinchey, Michael G. (Inventor)

2010-01-01

A memory apparatus includes a non-volatile computer memory, a USB mass storage controller connected to the non-volatile computer memory, the USB mass storage controller including a daisy chain component, a male USB interface connected to the USB mass storage controller, and at least one other interface for a memory device, other than a USB interface, the at least one other interface being connected to the USB mass storage controller.

Development of a Software Tool to Automate ADCO Flight Controller Console Planning Tasks

NASA Technical Reports Server (NTRS)

Anderson, Mark G.

2011-01-01

This independent study project covers the development of the International Space Station (ISS) Attitude Determination and Control Officer (ADCO) Planning Exchange APEX Tool. The primary goal of the tool is to streamline existing manual and time-intensive planning tools into a more automated, user-friendly application that interfaces with existing products and allows the ADCO to produce accurate products and timelines more effectively. This paper will survey the current ISS attitude planning process and its associated requirements, goals, documentation and software tools and how a software tool could simplify and automate many of the planning actions which occur at the ADCO console. The project will be covered from inception through the initial prototype delivery in November 2011 and will include development of design requirements and software as well as design verification and testing.

STS-35 ASTRO-1 telescopes documented in OV-102's payload bay (PLB)

NASA Image and Video Library

1990-12-10

STS035-604-058 (2-10 Dec 1990) --- The various components of the Astro-1 payload are seen backdropped against the blue and white Earth in this scene photographed through Columbia's aft flight deck windows. Parts of the Hopkins Ultraviolet Telescope (HUT), Ultraviolet Imaging Telescope (UIT) and the Wisconsin Ultraviolet Photopolarimetry Experiment (WUPPE) are visible on the Spacelab pallet in the foreground. The Broad Band X-ray Telescope (BBXRT) is behind this pallet and is not visible in this scene. The smaller cylinder in the foreground is the "Igloo," which is a pressurized container housing the Command and Data Management System, which interfaces with the in-cabin controllers to control the Instrument Pointing System (IPS) and the telescopes. The photograph was made with a handheld Rolleiflex camera aimed through Columbia's aft flight deck windows.

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.

BioCatalogue: a universal catalogue of web services for the life sciences

PubMed Central

Bhagat, Jiten; Tanoh, Franck; Nzuobontane, Eric; Laurent, Thomas; Orlowski, Jerzy; Roos, Marco; Wolstencroft, Katy; Aleksejevs, Sergejs; Stevens, Robert; Pettifer, Steve; Lopez, Rodrigo; Goble, Carole A.

2010-01-01

The use of Web Services to enable programmatic access to on-line bioinformatics is becoming increasingly important in the Life Sciences. However, their number, distribution and the variable quality of their documentation can make their discovery and subsequent use difficult. A Web Services registry with information on available services will help to bring together service providers and their users. The BioCatalogue (http://www.biocatalogue.org/) provides a common interface for registering, browsing and annotating Web Services to the Life Science community. Services in the BioCatalogue can be described and searched in multiple ways based upon their technical types, bioinformatics categories, user tags, service providers or data inputs and outputs. They are also subject to constant monitoring, allowing the identification of service problems and changes and the filtering-out of unavailable or unreliable resources. The system is accessible via a human-readable ‘Web 2.0’-style interface and a programmatic Web Service interface. The BioCatalogue follows a community approach in which all services can be registered, browsed and incrementally documented with annotations by any member of the scientific community. PMID:20484378

BioCatalogue: a universal catalogue of web services for the life sciences.

PubMed

Bhagat, Jiten; Tanoh, Franck; Nzuobontane, Eric; Laurent, Thomas; Orlowski, Jerzy; Roos, Marco; Wolstencroft, Katy; Aleksejevs, Sergejs; Stevens, Robert; Pettifer, Steve; Lopez, Rodrigo; Goble, Carole A

2010-07-01

The use of Web Services to enable programmatic access to on-line bioinformatics is becoming increasingly important in the Life Sciences. However, their number, distribution and the variable quality of their documentation can make their discovery and subsequent use difficult. A Web Services registry with information on available services will help to bring together service providers and their users. The BioCatalogue (http://www.biocatalogue.org/) provides a common interface for registering, browsing and annotating Web Services to the Life Science community. Services in the BioCatalogue can be described and searched in multiple ways based upon their technical types, bioinformatics categories, user tags, service providers or data inputs and outputs. They are also subject to constant monitoring, allowing the identification of service problems and changes and the filtering-out of unavailable or unreliable resources. The system is accessible via a human-readable 'Web 2.0'-style interface and a programmatic Web Service interface. The BioCatalogue follows a community approach in which all services can be registered, browsed and incrementally documented with annotations by any member of the scientific community.

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

Singleton, Jr., Robert; Israel, Daniel M.; Doebling, Scott William

For code verification, one compares the code output against known exact solutions. There are many standard test problems used in this capacity, such as the Noh and Sedov problems. ExactPack is a utility that integrates many of these exact solution codes into a common API (application program interface), and can be used as a stand-alone code or as a python package. ExactPack consists of python driver scripts that access a library of exact solutions written in Fortran or Python. The spatial profiles of the relevant physical quantities, such as the density, fluid velocity, sound speed, or internal energy, are returnedmore » at a time specified by the user. The solution profiles can be viewed and examined by a command line interface or a graphical user interface, and a number of analysis tools and unit tests are also provided. We have documented the physics of each problem in the solution library, and provided complete documentation on how to extend the library to include additional exact solutions. ExactPack’s code architecture makes it easy to extend the solution-code library to include additional exact solutions in a robust, reliable, and maintainable manner.« less

Basic nursing care: retrospective evaluation of communication and psychosocial interventions documented by nurses in the acute care setting.

PubMed

Juvé-Udina, Maria-Eulàlia; Pérez, Esperanza Zuriguel; Padrés, Núria Fabrellas; Samartino, Maribel Gonzalez; García, Marta Romero; Creus, Mònica Castellà; Batllori, Núria Vila; Calvo, Cristina Matud

2014-01-01

This study aimed to evaluate the frequency of psychosocial aspects of basic nursing care, as e-charted by nurses, when using an interface terminology. An observational, multicentre study was conducted in acute wards. The main outcome measure was the frequency of use of the psychosocial interventions in the electronic nursing care plans, analysed over a 12 month retrospective review. Overall, 150,494 electronic care plans were studied. Most of the intervention concepts from the interface terminology were used by registered nurses to illustrate the psychosocial aspects of fundamentals of care in the electronic care plans. The results presented help to demonstrate that the interventions of this interface terminology may be useful to inform psychosocial aspects of basic and advanced nursing care. The identification of psychosocial elements of basic nursing care in the nursing documentation may lead to obtain a deeper understanding of those caring interventions nurses consider essential to represent nurse-patient interactions. The frequency of psychosocial interventions may contribute to delineate basic and advanced nursing care. © 2013 Sigma Theta Tau International.

Manual for Getdata Version 3.1: a FORTRAN Utility Program for Time History Data

NASA Technical Reports Server (NTRS)

Maine, Richard E.

1987-01-01

This report documents version 3.1 of the GetData computer program. GetData is a utility program for manipulating files of time history data, i.e., data giving the values of parameters as functions of time. The most fundamental capability of GetData is extracting selected signals and time segments from an input file and writing the selected data to an output file. Other capabilities include converting file formats, merging data from several input files, time skewing, interpolating to common output times, and generating calculated output signals as functions of the input signals. This report also documents the interface standards for the subroutines used by GetData to read and write the time history files. All interface to the data files is through these subroutines, keeping the main body of GetData independent of the precise details of the file formats. Different file formats can be supported by changes restricted to these subroutines. Other computer programs conforming to the interface standards can call the same subroutines to read and write files in compatible formats.

Accelerator System Model (ASM) user manual with physics and engineering model documentation. ASM version 1.0

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

NONE

1993-07-01

The Accelerator System Model (ASM) is a computer program developed to model proton radiofrequency accelerators and to carry out system level trade studies. The ASM FORTRAN subroutines are incorporated into an intuitive graphical user interface which provides for the {open_quotes}construction{close_quotes} of the accelerator in a window on the computer screen. The interface is based on the Shell for Particle Accelerator Related Codes (SPARC) software technology written for the Macintosh operating system in the C programming language. This User Manual describes the operation and use of the ASM application within the SPARC interface. The Appendix provides a detailed description of themore » physics and engineering models used in ASM. ASM Version 1.0 is joint project of G. H. Gillespie Associates, Inc. and the Accelerator Technology (AT) Division of the Los Alamos National Laboratory. Neither the ASM Version 1.0 software nor this ASM Documentation may be reproduced without the expressed written consent of both the Los Alamos National Laboratory and G. H. Gillespie Associates, Inc.« less

SUSHI: an exquisite recipe for fully documented, reproducible and reusable NGS data analysis.

PubMed

Hatakeyama, Masaomi; Opitz, Lennart; Russo, Giancarlo; Qi, Weihong; Schlapbach, Ralph; Rehrauer, Hubert

2016-06-02

Next generation sequencing (NGS) produces massive datasets consisting of billions of reads and up to thousands of samples. Subsequent bioinformatic analysis is typically done with the help of open source tools, where each application performs a single step towards the final result. This situation leaves the bioinformaticians with the tasks to combine the tools, manage the data files and meta-information, document the analysis, and ensure reproducibility. We present SUSHI, an agile data analysis framework that relieves bioinformaticians from the administrative challenges of their data analysis. SUSHI lets users build reproducible data analysis workflows from individual applications and manages the input data, the parameters, meta-information with user-driven semantics, and the job scripts. As distinguishing features, SUSHI provides an expert command line interface as well as a convenient web interface to run bioinformatics tools. SUSHI datasets are self-contained and self-documented on the file system. This makes them fully reproducible and ready to be shared. With the associated meta-information being formatted as plain text tables, the datasets can be readily further analyzed and interpreted outside SUSHI. SUSHI provides an exquisite recipe for analysing NGS data. By following the SUSHI recipe, SUSHI makes data analysis straightforward and takes care of documentation and administration tasks. Thus, the user can fully dedicate his time to the analysis itself. SUSHI is suitable for use by bioinformaticians as well as life science researchers. It is targeted for, but by no means constrained to, NGS data analysis. Our SUSHI instance is in productive use and has served as data analysis interface for more than 1000 data analysis projects. SUSHI source code as well as a demo server are freely available.

Command and control interfaces for advanced neuroprosthetic applications.

PubMed

Scott, T R; Haugland, M

2001-10-01

Command and control interfaces permit the intention and situation of the user to influence the operation of the neural prosthesis. The wishes of the user are communicated via command interfaces to the neural prosthesis and the situation of the user by feedback control interfaces. Both these interfaces have been reviewed separately and are discussed in light of the current state of the art and projections for the future. It is apparent that as system functional complexity increases, the need for simpler command interfaces will increase. Such systems will demand more information to function effectively in order not to unreasonably increase user attention overhead. This will increase the need for bioelectric and biomechanical signals in a comprehensible form via elegant feedback control interfaces. Implementing such systems will also increase the computational demand on such neural prostheses.

[Differentiation of coding quality in orthopaedics by special, illustration-oriented case group analysis in the G-DRG System 2005].

PubMed

Schütz, U; Reichel, H; Dreinhöfer, K

2007-01-01

We introduce a grouping system for clinical practice which allows the separation of DRG coding in specific orthopaedic groups based on anatomic regions, operative procedures, therapeutic interventions and morbidity equivalent diagnosis groups. With this, a differentiated aim-oriented analysis of illustrated internal DRG data becomes possible. The group-specific difference of the coding quality between the DRG groups following primary coding by the orthopaedic surgeon and final coding by the medical controlling is analysed. In a consecutive series of 1600 patients parallel documentation and group-specific comparison of the relevant DRG parameters were carried out in every case after primary and final coding. Analysing the group-specific share in the additional CaseMix coding, the group "spine surgery" dominated, closely followed by the groups "arthroplasty" and "surgery due to infection, tumours, diabetes". Altogether, additional cost-weight-relevant coding was necessary most frequently in the latter group (84%), followed by group "spine surgery" (65%). In DRGs representing conservative orthopaedic treatment documented procedures had nearly no influence on the cost weight. The introduced system of case group analysis in internal DRG documentation can lead to the detection of specific problems in primary coding and cost-weight relevant changes of the case mix. As an instrument for internal process control in the orthopaedic field, it can serve as a communicative interface between an economically oriented classification of the hospital performance and a specific problem solution of the medical staff involved in the department management.

Can your software engineer program your PLC?

NASA Astrophysics Data System (ADS)

Borrowman, Alastair J.; Taylor, Philip

2016-07-01

The use of Programmable Logic Controllers (PLCs) in the control of large physics experiments is ubiquitous1, 2, 3. The programming of these controllers is normally the domain of engineers with a background in electronics, this paper introduces PLC program development from the software engineer's perspective. PLC programs provide the link between control software running on PC architecture systems and physical hardware controlled and monitored by digital and analog signals. The higher-level software running on the PC is typically responsible for accepting operator input and from this deciding when and how hardware connected to the PLC is controlled. The PLC accepts demands from the PC, considers the current state of its connected hardware and if correct to do so (based upon interlocks or other constraints) adjusts its hardware output signals appropriately for the PC's demands. A published ICD (Interface Control Document) defines the PLC memory locations available to be written and read by the PC to control and monitor the hardware. Historically the method of programming PLCs has been ladder diagrams that closely resemble circuit diagrams, however, PLC manufacturers nowadays also provide, and promote, the use of higher-level programming languages4. Based on techniques used in the development of high-level PC software to control PLCs for multiple telescopes, this paper examines the development of PLC programs to operate the hardware of a medical cyclotron beamline controlled from a PC using the Experimental Physics and Industrial Control System (EPICS), which is also widely used in telescope control5, 6, 7. The PLC used is the new generation Siemens S7-1200 programmed using Siemens Pascal based Structured Control Language (SCL), which is their implementation of Structured Text (ST). The approach described is that from a software engineer's perspective, utilising Siemens Totally Integrated Automation (TIA) Portal integrated development environment (IDE) to create modular PLC programs based upon reusable functions capable of being unit tested without the PLC connected to hardware. Emphasis has been placed on designing an interface between EPICS and SCL that enforces correct operation of hardware through stringent separation of PC accessible PLC memory and hardware I/O addresses used only by the PLC. The paper also introduces the method used to automate the creation, from the same source document, the PLC memory structure (tag) definitions (defining memory used to access hardware I/O and that accessed by the PC) and creation of the PC program data structures (EPICS database records) used to access the permitted PLC addresses. From direct experience this paper demonstrates the advantages of PLC program development being shared between electronic and software engineers, to enable use of the most appropriate processes from both the perspective of the hardware and the higher-level software used to control it.

Crew Transportation Technical Management Processes

NASA Technical Reports Server (NTRS)

Mckinnie, John M. (Compiler); Lueders, Kathryn L. (Compiler)

2013-01-01

Under the guidance of processes provided by Crew Transportation Plan (CCT-PLN-1100), this document, with its sister documents, International Space Station (ISS) Crew Transportation and Services Requirements Document (CCT-REQ-1130), Crew Transportation Technical Standards and Design Evaluation Criteria (CCT-STD-1140), Crew Transportation Operations Standards (CCT STD-1150), and ISS to Commercial Orbital Transportation Services Interface Requirements Document (SSP 50808), provides the basis for a National Aeronautics and Space Administration (NASA) certification for services to the ISS for the Commercial Provider. When NASA Crew Transportation System (CTS) certification is achieved for ISS transportation, the Commercial Provider will be eligible to provide services to and from the ISS during the services phase.

Tools & Services - SEER Registrars

Cancer.gov

View glossary for registrars. Access ICD conversion programs, SEER Abstracting Tool, SEER Data Viewer, SEER interactive drug database for coding oncology drugs, data documentation, variable recodes, and SEER Application Programming Interface for developers.

78 FR 48866 - Nationwide Categorical Waivers Under the American Recovery and Reinvestment Act of 2009 (Recovery...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-08-12

... and hood fume interface with Phoenix Controls hood. The components were specifically designed to fit... Module Assembly to repair existing Johnson Controls Lab and Hood Fume Interface with Phoenix Controls... Johnson Controls lab and hood fume interface with Phoenix Controls hood (where utilization of an American...

Interfacing the Controllogics PLC over Ethernet/IP.

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

Kasemir, K. U.; Dalesio, L. R.

2001-01-01

The Allen-Bradley ControlLogix [1] line of programmable logic controllers (PLCs) offers several interfaces: Ethernet, ControlNet, DeviceNet, RS-232 and others. The ControlLogix Ethernet interface module 1756-ENET uses EtherNet/IP, the ControlNet protocol [2], encapsulated in Ethernet packages, with specific service codes [3]. A driver for the Experimental Physics and Industrial Control System (EPICS) has been developed that utilizes this EtherNet/IP protocol for controllers running the vxWorks RTOS as well as a Win32 and Unix/Linux test program. Features, performance and limitations of this interface are presented.

Ensuring the Trust of NAND Flash Memory: Going Beyond the Published Interface

DTIC Science & Technology

2016-03-17

Ensuring the Trust of NAND Flash Memory: Going Beyond the Published Interface Austin H. Roach, Matthew J. Gadlage, James D. Ingalls, Aaron...reliability and trust of memories is very important, but because of incomplete documentation provided by commercial vendors and a lack of low-level...shown here that useful information about the trust and reliability of COTS NAND Flash components can be obtained by going beyond the standard product

NIC atomic operation unit with caching and bandwidth mitigation

DOEpatents

Hemmert, Karl Scott; Underwood, Keith D.; Levenhagen, Michael J.

2016-03-01

A network interface controller atomic operation unit and a network interface control method comprising, in an atomic operation unit of a network interface controller, using a write-through cache and employing a rate-limiting functional unit.

Network device interface for digitally interfacing data channels to a controller via a network

NASA Technical Reports Server (NTRS)

Ellerbrock, Philip J. (Inventor); Grant, Robert L. (Inventor); Winkelmann, Joseph P. (Inventor); Konz, Daniel W. (Inventor)

2009-01-01

A communications system and method are provided for digitally connecting a plurality of data channels, such as sensors, actuators, and subsystems, to a controller using a network bus. The network device interface interprets commands and data received from the controller and polls the data channels in accordance with these commands. Specifically, the network device interface receives digital commands and data from the controller, and based on these commands and data, communicates with the data channels to either retrieve data in the case of a sensor or send data to activate an actuator. Data retrieved from the sensor is converted into digital signals and transmitted to the controller. Network device interfaces associated with different data channels can coordinate communications with the other interfaces based on either a transition in a command message sent by the bus controller or a synchronous clock signal.

A Python library for FAIRer access and deposition to the Metabolomics Workbench Data Repository.

PubMed

Smelter, Andrey; Moseley, Hunter N B

2018-01-01

The Metabolomics Workbench Data Repository is a public repository of mass spectrometry and nuclear magnetic resonance data and metadata derived from a wide variety of metabolomics studies. The data and metadata for each study is deposited, stored, and accessed via files in the domain-specific 'mwTab' flat file format. In order to improve the accessibility, reusability, and interoperability of the data and metadata stored in 'mwTab' formatted files, we implemented a Python library and package. This Python package, named 'mwtab', is a parser for the domain-specific 'mwTab' flat file format, which provides facilities for reading, accessing, and writing 'mwTab' formatted files. Furthermore, the package provides facilities to validate both the format and required metadata elements of a given 'mwTab' formatted file. In order to develop the 'mwtab' package we used the official 'mwTab' format specification. We used Git version control along with Python unit-testing framework as well as continuous integration service to run those tests on multiple versions of Python. Package documentation was developed using sphinx documentation generator. The 'mwtab' package provides both Python programmatic library interfaces and command-line interfaces for reading, writing, and validating 'mwTab' formatted files. Data and associated metadata are stored within Python dictionary- and list-based data structures, enabling straightforward, 'pythonic' access and manipulation of data and metadata. Also, the package provides facilities to convert 'mwTab' files into a JSON formatted equivalent, enabling easy reusability of the data by all modern programming languages that implement JSON parsers. The 'mwtab' package implements its metadata validation functionality based on a pre-defined JSON schema that can be easily specialized for specific types of metabolomics studies. The library also provides a command-line interface for interconversion between 'mwTab' and JSONized formats in raw text and a variety of compressed binary file formats. The 'mwtab' package is an easy-to-use Python package that provides FAIRer utilization of the Metabolomics Workbench Data Repository. The source code is freely available on GitHub and via the Python Package Index. Documentation includes a 'User Guide', 'Tutorial', and 'API Reference'. The GitHub repository also provides 'mwtab' package unit-tests via a continuous integration service.

Microfluidic on-chip fluorescence-activated interface control system

PubMed Central

Haiwang, Li; Nguyen, N. T.; Wong, T. N.; Ng, S. L.

2010-01-01

A microfluidic dynamic fluorescence-activated interface control system was developed for lab-on-a-chip applications. The system consists of a straight rectangular microchannel, a fluorescence excitation source, a detection sensor, a signal conversion circuit, and a high-voltage feedback system. Aqueous NaCl as conducting fluid and aqueous glycerol as nonconducting fluid were introduced to flow side by side into the straight rectangular microchannel. Fluorescent dye was added to the aqueous NaCl to work as a signal representing the interface position. Automatic control of the liquid interface was achieved by controlling the electroosmotic effect that exists only in the conducting fluid using a high-voltage feedback system. A LABVIEW program was developed to control the output of high-voltage power supply according the actual interface position, and then the interface position is modified as the output of high-voltage power supply. At last, the interface can be moved to the desired position automatically using this feedback system. The results show that the system presented in this paper can control an arbitrary interface location in real time. The effects of viscosity ratio, flow rates, and polarity of electric field were discussed. This technique can be extended to switch the sample flow and droplets automatically. PMID:21173886

ProteoCloud: a full-featured open source proteomics cloud computing pipeline.

PubMed

Muth, Thilo; Peters, Julian; Blackburn, Jonathan; Rapp, Erdmann; Martens, Lennart

2013-08-02

We here present the ProteoCloud pipeline, a freely available, full-featured cloud-based platform to perform computationally intensive, exhaustive searches in a cloud environment using five different peptide identification algorithms. ProteoCloud is entirely open source, and is built around an easy to use and cross-platform software client with a rich graphical user interface. This client allows full control of the number of cloud instances to initiate and of the spectra to assign for identification. It also enables the user to track progress, and to visualize and interpret the results in detail. Source code, binaries and documentation are all available at http://proteocloud.googlecode.com. Copyright © 2012 Elsevier B.V. All rights reserved.

Robot Command Interface Using an Audio-Visual Speech Recognition System

NASA Astrophysics Data System (ADS)

Ceballos, Alexánder; Gómez, Juan; Prieto, Flavio; Redarce, Tanneguy

In recent years audio-visual speech recognition has emerged as an active field of research thanks to advances in pattern recognition, signal processing and machine vision. Its ultimate goal is to allow human-computer communication using voice, taking into account the visual information contained in the audio-visual speech signal. This document presents a command's automatic recognition system using audio-visual information. The system is expected to control the laparoscopic robot da Vinci. The audio signal is treated using the Mel Frequency Cepstral Coefficients parametrization method. Besides, features based on the points that define the mouth's outer contour according to the MPEG-4 standard are used in order to extract the visual speech information.

Cargo Movement Operations System (CMOS) Preliminary Interface Design Document Increment II

DTIC Science & Technology

1991-02-28

NO [ ] COMMENT DISPOSITION: ACCEPT [ ] REJECT [ ] COMMENT STATUS: OPEN [ ] CLOSED [ ] Cmnt Page Paragraph No. No. Number Comment 1. vii List of Figures Figure 3.24, METS II is listed twice. Delete the reference to page 51 here, and Figure 3.24 on page 51. 2. 52 3.30.2.1b Change "inceements" to "increments". 3. 56 3.33.2.1 Change Table ŗ.35.2.a" to 3.40.2a". 4. A-3 DAMMS-R Change "management" to "Managemn.it". 5. A-5 HOST Change "Syatem" to "System". ORIGINATOR CONTROL NUMBER: IDD-0002 PROGRAM OFFICE

Sikorsky interactive graphics surface design/manufacturing system

NASA Technical Reports Server (NTRS)

Robbins, R.

1975-01-01

An interactive graphics system conceived to be used in the design, analysis, and manufacturing of aircraft components with free form surfaces was described. In addition to the basic surface definition and viewing capabilities inherent in such a system, numerous other features are present: surface editing, automated smoothing of control curves, variable milling patch boundary definitions, surface intersection definition and viewing, automatic creation of true offset surfaces, digitizer and drafting machine interfaces, and cutter path optimization. Documented costs and time savings of better than six to one are being realized with this system. The system was written in FORTRAN and GSP for use on IBM 2250 CRT's in conjunction with an IBM 370/158 computer.

Final definition and preliminary design study for the initial atmospheric cloud physics laboratory, a Spacelab mission payload

NASA Technical Reports Server (NTRS)

1976-01-01

The following areas related to the final definition and preliminary design study of the initial atmospheric cloud physics laboratory (ACPL) were covered: (1) proposal organization, personnel, schedule, and project management, (2) proposed configurations, (3) study objectives, (4) ACPL experiment program listing and description, (5) mission/flight flexibility and modularity/commonality, (6) study plan, and (7) description of following tasks: requirement analysis and definition task flow, systems analysis and trade studies, subsystem analysis and trade studies, specifications and interface control documents, preliminary design task flow, work breakdown structure, programmatic analysis and planning, and project costs. Finally, an overview of the scientific requirements was presented.

Blasting, graphical interfaces and Unix

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

Knudsen, S.; Preece, D.S.

1993-11-01

A discrete element computer program, DMC (Distinct Motion Code) was developed to simulate blast-induced rock motion. To simplify the complex task of entering material and explosive design parameters as well as bench configuration, a full-featured graphical interface has been developed. DMC is currently executed on both Sun SPARCstation 2 and Sun SPARCstation 10 platforms and routinely used to model bench and crater blasting problems. This paper will document the design and development of the full-featured interface to DMC. The development of the interface will be tracked through the various stages, highlighting the adjustments made to allow the necessary parameters tomore » be entered in terms and units that field blasters understand. The paper also discusses a novel way of entering non-integer numbers and the techniques necessary to display blasting parameters in an understandable visual manner. A video presentation will demonstrate the graphics interface and explains its use.« less

Blasting, graphical interfaces and Unix

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

Knudsen, S.; Preece, D.S.

1994-12-31

A discrete element computer program, DMC (Distinct Motion Code) was developed to simulate blast-induced rock motion. To simplify the complex task of entering material and explosive design parameters as well as bench configuration, a full-featured graphical interface has been developed. DMC is currently executed on both Sun SPARCstation 2 and Sun SPARCstation 10 platforms and routinely used to model bench and crater blasting problems. This paper will document the design and development of the full-featured interface to DMC. The development of the interface will be tracked through the various stages, highlighting the adjustments made to allow the necessary parameters tomore » be entered in terms and units that field blasters understand. The paper also discusses a novel way of entering non-integer numbers and the techniques necessary to display blasting parameters in an understandable visual manner. A video presentation will demonstrate the graphics interface and explains its use.« less

Innovations in prosthetic interfaces for the upper extremity.

PubMed

Kung, Theodore A; Bueno, Reuben A; Alkhalefah, Ghadah K; Langhals, Nicholas B; Urbanchek, Melanie G; Cederna, Paul S

2013-12-01

Advancements in modern robotic technology have led to the development of highly sophisticated upper extremity prosthetic limbs. High-fidelity volitional control of these devices is dependent on the critical interface between the patient and the mechanical prosthesis. Recent innovations in prosthetic interfaces have focused on several control strategies. Targeted muscle reinnervation is currently the most immediately applicable prosthetic control strategy and is particularly indicated in proximal upper extremity amputations. Investigation into various brain interfaces has allowed acquisition of neuroelectric signals directly or indirectly from the central nervous system for prosthetic control. Peripheral nerve interfaces permit signal transduction from both motor and sensory nerves with a higher degree of selectivity. This article reviews the current developments in each of these interface systems and discusses the potential of these approaches to facilitate motor control and sensory feedback in upper extremity neuroprosthetic devices.

HKHC Community Dashboard: design, development, and function of a Web-based performance monitoring system.

PubMed

Bors, Philip A; Kemner, Allison; Fulton, John; Stachecki, Jessica; Brennan, Laura K

2015-01-01

As part of Robert Wood Johnson Foundation's Healthy Kids, Healthy Communities (HKHC) national grant program, a technical assistance team designed the HKHC Community Dashboard, an online progress documentation and networking system. The Dashboard was central to HKHC's multimethod program evaluation and became a communication interface for grantees and technical assistance providers. The Dashboard was designed through an iterative process of identifying needs and priorities; designing the user experience, technical development, and usability testing; and applying visual design. The system was created with an open-source content management system and support for building an online community of users. The site developer trained technical assistance providers at the national program office and evaluators, who subsequently trained all 49 grantees. Evaluators provided support for Dashboard users and populated the site with the bulk of its uploaded tools and resource documents. The system tracked progress through an interactive work plan template, regular documentation by local staff and partners, and data coding and analysis by the evaluation team. Other features included the ability to broadcast information to Dashboard users via e-mail, event calendars, discussion forums, private messaging, a resource clearinghouse, a technical assistance diary, and real-time progress reports. The average number of Dashboard posts was 694 per grantee during the grant period. Technical assistance providers and grantees uploaded a total of 1304 resource documents. The Dashboard functions with the highest grantee satisfaction were its interfaces for sharing and progress documentation. A majority of Dashboard users (69%) indicated a preference for continued access to the Dashboard's uploaded resource documents. The Dashboard was a useful and innovative tool for participatory evaluation of a large national grant program. While progress documentation added some burden to local project staff, the system proved to be a useful resource-sharing technology.

ConKit: a python interface to contact predictions.

PubMed

Simkovic, Felix; Thomas, Jens M H; Rigden, Daniel J

2017-07-15

Recent advances in protein residue contact prediction algorithms have led to the emergence of many new methods and a variety of file formats. We present ConKit , an open source, modular and extensible Python interface which allows facile conversion between formats and provides an interface to analyses of sequence alignments and sets of contact predictions. ConKit is available via the Python Package Index. The documentation can be found at http://www.conkit.org . ConKit is licensed under the BSD 3-Clause. hlfsimko@liverpool.ac.uk or drigden@liverpool.ac.uk. Supplementary data are available at Bioinformatics online. © The Author(s) 2017. Published by Oxford University Press.

Universal interface of TAUOLA: Technical and physics documentation

NASA Astrophysics Data System (ADS)

Davidson, N.; Nanava, G.; Przedziński, T.; Richter-Waş, E.; Waş, Z.

2012-03-01

Because of their narrow width, τ decays can be well separated from their production process. Only spin degrees of freedom connect these two parts of the physics process of interest for high energy collision experiments. In the following, we present a Monte Carlo algorithm which is based on that property. The interface supplements events generated by other programs, with τ decays. Effects of spin, including transverse degrees of freedom, genuine weak corrections or of new physics may be taken into account at the time when a τ decay is generated and written into an event record. The physics content of the C++ interface is already now richer than its FORTRAN predecessor.

Biotool2Web: creating simple Web interfaces for bioinformatics applications.

PubMed

Shahid, Mohammad; Alam, Intikhab; Fuellen, Georg

2006-01-01

Currently there are many bioinformatics applications being developed, but there is no easy way to publish them on the World Wide Web. We have developed a Perl script, called Biotool2Web, which makes the task of creating web interfaces for simple ('home-made') bioinformatics applications quick and easy. Biotool2Web uses an XML document containing the parameters to run the tool on the Web, and generates the corresponding HTML and common gateway interface (CGI) files ready to be published on a web server. This tool is available for download at URL http://www.uni-muenster.de/Bioinformatics/services/biotool2web/ Georg Fuellen (fuellen@alum.mit.edu).

Accessing SDO data in a pipeline environment using the VSO WSDL/SOAP interface

NASA Astrophysics Data System (ADS)

Suarez Sola, F. I.; Hourcle, J. A.; Amezcua, A.; Bogart, R.; Davey, A. R.; Gurman, J. B.; Hill, F.; Hughitt, V. K.; Martens, P. C.; Spencer, J.; Vso Team

2010-12-01

As part of the Virtual Solar Observatory (VSO) effort to support the Solar Dynamics Observatory (SDO) data, the VSO has worked on bringing up to date its WSDL document and SOAP interface to make it compatible with most widely used web services core engines. (E.g. axis2, jws, etc.) In this presentation we will explore the possibilities available for searching and/or fetching data within pipeline code. We will explain some of the WSDL/VSO-SDO interface intricacies and show how the vast amount of data that is available via the VSO can be tapped via IDL, Java, Perl or C in an uncomplicated way.

Monitoring and Control Interface Based on Virtual Sensors

PubMed Central

Escobar, Ricardo F.; Adam-Medina, Manuel; García-Beltrán, Carlos D.; Olivares-Peregrino, Víctor H.; Juárez-Romero, David; Guerrero-Ramírez, Gerardo V.

2014-01-01

In this article, a toolbox based on a monitoring and control interface (MCI) is presented and applied in a heat exchanger. The MCI was programed in order to realize sensor fault detection and isolation and fault tolerance using virtual sensors. The virtual sensors were designed from model-based high-gain observers. To develop the control task, different kinds of control laws were included in the monitoring and control interface. These control laws are PID, MPC and a non-linear model-based control law. The MCI helps to maintain the heat exchanger under operation, even if a temperature outlet sensor fault occurs; in the case of outlet temperature sensor failure, the MCI will display an alarm. The monitoring and control interface is used as a practical tool to support electronic engineering students with heat transfer and control concepts to be applied in a double-pipe heat exchanger pilot plant. The method aims to teach the students through the observation and manipulation of the main variables of the process and by the interaction with the monitoring and control interface (MCI) developed in LabVIEW©. The MCI provides the electronic engineering students with the knowledge of heat exchanger behavior, since the interface is provided with a thermodynamic model that approximates the temperatures and the physical properties of the fluid (density and heat capacity). An advantage of the interface is the easy manipulation of the actuator for an automatic or manual operation. Another advantage of the monitoring and control interface is that all algorithms can be manipulated and modified by the users. PMID:25365462

Intelligent search and retrieval of a large multimedia knowledgebase for the Hubble Space Telescope

NASA Technical Reports Server (NTRS)

Clapis, Paul J.; Byers, William S.

1990-01-01

A document-retrieval assistant (DRA) in a microcomputer format is described which incorporates hypertext and natural language capabilities. Hypertext is used to introduce an intelligent search capability, and the natural-language interface permits access to specific data without the use of keywords. The DRA can be used to access and 'browse' the large multimedia database that is composed of project documentation from the HST.

General-Purpose Serial Interface For Remote Control

NASA Technical Reports Server (NTRS)

Busquets, Anthony M.; Gupton, Lawrence E.

1990-01-01

Computer controls remote television camera. General-purpose controller developed to serve as interface between host computer and pan/tilt/zoom/focus functions on series of automated video cameras. Interface port based on 8251 programmable communications-interface circuit configured for tristated outputs, and connects controller system to any host computer with RS-232 input/output (I/O) port. Accepts byte-coded data from host, compares them with prestored codes in read-only memory (ROM), and closes or opens appropriate switches. Six output ports control opening and closing of as many as 48 switches. Operator controls remote television camera by speaking commands, in system including general-purpose controller.

Three-dimensional user interfaces for scientific visualization

NASA Technical Reports Server (NTRS)

Vandam, Andries

1995-01-01

The main goal of this project is to develop novel and productive user interface techniques for creating and managing visualizations of computational fluid dynamics (CFD) datasets. We have implemented an application framework in which we can visualize computational fluid dynamics user interfaces. This UI technology allows users to interactively place visualization probes in a dataset and modify some of their parameters. We have also implemented a time-critical scheduling system which strives to maintain a constant frame-rate regardless of the number of visualization techniques. In the past year, we have published parts of this research at two conferences, the research annotation system at Visualization 1994, and the 3D user interface at UIST 1994. The real-time scheduling system has been submitted to SIGGRAPH 1995 conference. Copies of these documents are included with this report.

Netlib services and resources

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

Browne, S.V.; Green, S.C.; Moore, K.

1994-04-01

The Netlib repository, maintained by the University of Tennessee and Oak Ridge National Laboratory, contains freely available software, documents, and databases of interest to the numerical, scientific computing, and other communities. This report includes both the Netlib User`s Guide and the Netlib System Manager`s Guide, and contains information about Netlib`s databases, interfaces, and system implementation. The Netlib repository`s databases include the Performance Database, the Conferences Database, and the NA-NET mail forwarding and Whitepages Databases. A variety of user interfaces enable users to access the Netlib repository in the manner most convenient and compatible with their networking capabilities. These interfaces includemore » the Netlib email interface, the Xnetlib X Windows client, the netlibget command-line TCP/IP client, anonymous FTP, anonymous RCP, and gopher.« less

POOL WATER TREATMENT AND COOLING SYSTEM DESCRIPTION DOCUMENT

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

V. King

2000-06-19

The Pool Water Treatment and Cooling System is located in the Waste Handling Building (WHB), and is comprised of various process subsystems designed to support waste handling operations. This system maintains the pool water temperature within an acceptable range, maintains water quality standards that support remote underwater operations and prevent corrosion, detects leakage from the pool liner, provides the capability to remove debris from the pool, controls the pool water level, and helps limit radiological exposure to personnel. The pool structure and liner, pool lighting, and the fuel staging racks in the pool are not within the scope of themore » Pool Water Treatment and Cooling System. Pool water temperature control is accomplished by circulating the pool water through heat exchangers. Adequate circulation and mixing of the pool water is provided to prevent localized thermal hotspots in the pool. Treatment of the pool water is accomplished by a water treatment system that circulates the pool water through filters, and ion exchange units. These water treatment units remove radioactive and non-radioactive particulate and dissolved solids from the water, thereby providing the water clarity needed to conduct waste handling operations. The system also controls pool water chemistry to prevent advanced corrosion of the pool liner, pool components, and fuel assemblies. Removal of radioactivity from the pool water contributes to the project ALARA (as low as is reasonably achievable) goals. A leak detection system is provided to detect and alarm leaks through the pool liner. The pool level control system monitors the water level to ensure that the minimum water level required for adequate radiological shielding is maintained. Through interface with a demineralized water system, adequate makeup is provided to compensate for loss of water inventory through evaporation and waste handling operations. Interface with the Site Radiological Monitoring System provides continuous radiological monitoring of the pool water. The Pool Water Treatment and Cooling System interfaces with the Waste Handling Building System, Site-Generated Radiological Waste Handling System, Site Radiological Monitoring System, Waste Handling Building Electrical System, Site Water System, and the Monitored Geologic Repository Operations Monitoring and Control System.« less

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.

STS-98 crew takes part in Multi-Equipment Interface Test.

NASA Technical Reports Server (NTRS)

2000-01-01

In the Space Station Processing Facility, STS-98 Mission Specialist Thomas D. Jones (Ph.D.) looks over documents as part of a Multi-Equipment Interface Test (MEIT) on the U.S. Lab Destiny. Other crew members taking part in the MEIT are Commander Kenneth D. Cockrell and Pilot Mark Polansky. The remaining members of the crew (not present for the MEIT) are and Mission Specialists Robert L. Curbeam Jr. and Marsha S. Ivins. During the STS-98 mission, the crew will install the Lab on the International Space Station during a series of three space walks. The mission will provide the station with science research facilities and expand its power, life support and control capabilities. The U.S. Laboratory Module continues a long tradition of microgravity materials research, first conducted by Skylab and later Shuttle and Spacelab missions. Destiny is expected to be a major feature in future research, providing facilities for biotechnology, fluid physics, combustion, and life sciences research. The Lab is planned for launch aboard Space Shuttle Atlantis on the sixth ISS flight, currently targeted no earlier than Aug. 19, 2000.

STS-98 crew takes part in Multi-Equipment Interface Test.

NASA Technical Reports Server (NTRS)

2000-01-01

During a Multi-Equipment Interface Test (MEIT) in the U.S. Lab Destiny, which is in the Space Station Processing Facility, astronaut James Voss (left) joins STS-98 Pilot Mark Polansky (center) and Commander Kenneth D. Cockrell (right) in checking wiring against documentation on the floor. Also participating in the MEIT is Mission Specialist Thomas D. Jones (Ph.D.). Voss is assigned to mission STS-102 as part of the second crew to occupy the International Space Station. During the STS-98 mission, the crew will install the Lab on the station during a series of three space walks. The mission will provide the station with science research facilities and expand its power, life support and control capabilities. The U.S. Laboratory Module continues a long tradition of microgravity materials research, first conducted by Skylab and later Shuttle and Spacelab missions. Destiny is expected to be a major feature in future research, providing facilities for biotechnology, fluid physics, combustion, and life sciences research. The Lab is planned for launch aboard Space Shuttle Atlantis on the sixth ISS flight, currently targeted no earlier than Aug. 19, 2000.

In-house access to PACS images and related data through World Wide Web

NASA Astrophysics Data System (ADS)

Mascarini, Christian; Ratib, Osman M.; Trayser, Gerhard; Ligier, Yves; Appel, R. D.

1996-05-01

The development of a hospital wide PACS is in progress at the University Hospital of Geneva and several archive modules are operational since 1992. This PACS is intended for wide distribution of images to clinical wards. As the PACS project and the number of archived images grow rapidly in the hospital, it was necessary to provide an easy, more widely accessible and convenient access to the PACS database for the clinicians in the different wards and clinical units of the hospital. An innovative solution has been developed using tools such as Netscape navigator and NCSA World Wide Web server as an alternative to conventional database query and retrieval software. These tools present the advantages of providing an user interface which is the same independently of the platform being used (Mac, Windows, UNIX, ...), and an easy integration of different types of documents (text, images, ...). A strict access control has been added to this interface. It allows user identification and access rights checking, as defined by the in-house hospital information system, before allowing the navigation through patient data records.

An integrated knowledge system for wind tunnel testing - Project Engineers' Intelligent Assistant

NASA Technical Reports Server (NTRS)

Lo, Ching F.; Shi, George Z.; Hoyt, W. A.; Steinle, Frank W., Jr.

1993-01-01

The Project Engineers' Intelligent Assistant (PEIA) is an integrated knowledge system developed using artificial intelligence technology, including hypertext, expert systems, and dynamic user interfaces. This system integrates documents, engineering codes, databases, and knowledge from domain experts into an enriched hypermedia environment and was designed to assist project engineers in planning and conducting wind tunnel tests. PEIA is a modular system which consists of an intelligent user-interface, seven modules and an integrated tool facility. Hypermedia technology is discussed and the seven PEIA modules are described. System maintenance and updating is very easy due to the modular structure and the integrated tool facility provides user access to commercial software shells for documentation, reporting, or database updating. PEIA is expected to provide project engineers with technical information, increase efficiency and productivity, and provide a realistic tool for personnel training.

Automated software system for checking the structure and format of ACM SIG documents

NASA Astrophysics Data System (ADS)

Mirza, Arsalan Rahman; Sah, Melike

2017-04-01

Microsoft (MS) Office Word is one of the most commonly used software tools for creating documents. MS Word 2007 and above uses XML to represent the structure of MS Word documents. Metadata about the documents are automatically created using Office Open XML (OOXML) syntax. We develop a new framework, which is called ADFCS (Automated Document Format Checking System) that takes the advantage of the OOXML metadata, in order to extract semantic information from MS Office Word documents. In particular, we develop a new ontology for Association for Computing Machinery (ACM) Special Interested Group (SIG) documents for representing the structure and format of these documents by using OWL (Web Ontology Language). Then, the metadata is extracted automatically in RDF (Resource Description Framework) according to this ontology using the developed software. Finally, we generate extensive rules in order to infer whether the documents are formatted according to ACM SIG standards. This paper, introduces ACM SIG ontology, metadata extraction process, inference engine, ADFCS online user interface, system evaluation and user study evaluations.

Small computer interface to a stepper motor

NASA Technical Reports Server (NTRS)

Berry, Fred A., Jr.

1986-01-01

A Commodore VIC-20 computer has been interfaced with a stepper motor to provide an inexpensive stepper motor controller. Only eight transistors and two integrated circuits compose the interface. The software controls the parallel interface of the computer and provides the four phase drive signals for the motor. Optical sensors control the zeroing of the 12-inch turntable positioned by the controller. The computer calculates the position information and movement of the table and may be programmed in BASIC to execute automatic sequences.

Conceptual design of data acquisition and control system for two Rf driver based negative ion source for fusion R&D

NASA Astrophysics Data System (ADS)

Soni, Jigensh; Yadav, R. K.; Patel, A.; Gahlaut, A.; Mistry, H.; Parmar, K. G.; Mahesh, V.; Parmar, D.; Prajapati, B.; Singh, M. J.; Bandyopadhyay, M.; Bansal, G.; Pandya, K.; Chakraborty, A.

2013-02-01

Twin Source - An Inductively coupled two RF driver based 180 kW, 1 MHz negative ion source experimental setup is initiated at IPR, Gandhinagar, under Indian program, with the objective of understanding the physics and technology of multi-driver coupling. Twin Source [1] (TS) also provides an intermediate platform between operational ROBIN [2] [5] and eight RF drivers based Indian test facility -INTF [3]. A twin source experiment requires a central system to provide control, data acquisition and communication interface, referred as TS-CODAC, for which a software architecture similar to ITER CODAC core system has been decided for implementation. The Core System is a software suite for ITER plant system manufacturers to use as a template for the development of their interface with CODAC. The ITER approach, in terms of technology, has been adopted for the TS-CODAC so as to develop necessary expertise for developing and operating a control system based on the ITER guidelines as similar configuration needs to be implemented for the INTF. This cost effective approach will provide an opportunity to evaluate and learn ITER CODAC technology, documentation, information technology and control system processes, on an operational machine. Conceptual design of the TS-CODAC system has been completed. For complete control of the system, approximately 200 Nos. control signals and 152 acquisition signals are needed. In TS-CODAC, control loop time required is within the range of 5ms - 10 ms, therefore for the control system, PLC (Siemens S-7 400) has been chosen as suggested in the ITER slow controller catalog. For the data acquisition, the maximum sampling interval required is 100 micro second, and therefore National Instruments (NI) PXIe system and NI 6259 digitizer cards have been selected as suggested in the ITER fast controller catalog. This paper will present conceptual design of TS -CODAC system based on ITER CODAC Core software and applicable plant system integration processes.

New control system for the 1.5m and 0.9m telescopes at Sierra Nevada Observatory

NASA Astrophysics Data System (ADS)

Costillo, Luis P.; Ramos, J. Luis; Ibáñez, J. Miguel; Aparicio, Beatriz; Herránz, Miguel; García, Antonio J.

2006-06-01

The Sierra Nevada Observatory (Granada, Spain) has a number of telescopes. Our study will focus on two Nasmyth telescopes with apertures of 1.5m and 0.9m and an equatorial mount. The system currently installed to control these telescopes is a 1995 centralized VME module. However, given the problems which have arisen due to the number of wires and other complications, we have decided to change this control module. We will control each telescope with a distributed control philosophy, using a serial linear communication bus between independent nodes, although all system capabilities are accessible from a central unit anywhere and at any time via internet. We have divided the tasks and have one node for alpha control, another for delta control, one for the dome, one for the focus and the central unit to interface with a pc. The nodes for alpha, delta and the dome will be used by means of FPGA's in order to efficiently sample the encoders and the control algorithms, and to generate the output for the motors and the servo. The focus will have a microcontroller, and the system is easy to expand in the event of the inclusion of more nodes. After having studied several fieldbus systems, we have opted for the CAN bus, because of its reliability and broadcasting possibilities. In this way, all the important information will be on the bus, and every node will be able to access the information at any time. This document explains the new design made in the IAA for the new consoles of control whose basic characteristics are, the distributed control, the hardware simplify, the cable remove, the safety and maintenance improve and facilitating the observation improving the interface with the user, and finally to prepare the system for the remote observation.

Object library for a new generation of experiment-controlling applications under the UNIX operating system.

PubMed

Gaponov, Y A; Ito, K; Amemiya, Y

1998-05-01

The Interface Object Library based on the Motif extension of the X Windows system and on the ESONE SVIC-VCC Library is presented. Some features of the applications for controlling a synchrotron radiation experiment are discussed. The Interface Object Library is written in the object-oriented C++ language. The library class-hierarchy structure is presented and discussed. Several interfaces were realized in the Interface Object Library: the Windows interface, the CAMAC interface and the interface for supporting the experiment. The behaviour of the objects describing the CAMAC crate and CAMAC block is discussed. The application of these protocols for controlling the fast one-coordinate position-sensitive X-ray detector OD3 is presented.

NASA Tech Briefs, June 2004

NASA Technical Reports Server (NTRS)

2004-01-01

Topics covered include: COTS MEMS Flow-Measurement Probes; Measurement of an Evaporating Drop on a Reflective Substrate; Airplane Ice Detector Based on a Microwave Transmission Line; Microwave/Sonic Apparatus Measures Flow and Density in Pipe; Reducing Errors by Use of Redundancy in Gravity Measurements; Membrane-Based Water Evaporator for a Space Suit; Compact Microscope Imaging System with Intelligent Controls; Chirped-Superlattice, Blocked-Intersubband QWIP; Charge-Dissipative Electrical Cables; Deep-Sea Video Cameras Without Pressure Housings; RFID and Memory Devices Fabricated Integrally on Substrates; Analyzing Dynamics of Cooperating Spacecraft; Spacecraft Attitude Maneuver Planning Using Genetic Algorithms; Forensic Analysis of Compromised Computers; Document Concurrence System; Managing an Archive of Images; MPT Prediction of Aircraft-Engine Fan Noise; Improving Control of Two Motor Controllers; Electro-deionization Using Micro-separated Bipolar Membranes; Safer Electrolytes for Lithium-Ion Cells; Rotating Reverse-Osmosis for Water Purification; Making Precise Resonators for Mesoscale Vibratory Gyroscopes; Robotic End Effectors for Hard-Rock Climbing; Improved Nutation Damper for a Spin-Stabilized Spacecraft; Exhaust Nozzle for a Multitube Detonative Combustion Engine; Arc-Second Pointer for Balloon-Borne Astronomical Instrument; Compact, Automated Centrifugal Slide-Staining System; Two-Armed, Mobile, Sensate Research Robot; Compensating for Effects of Humidity on Electronic Noses; Brush/Fin Thermal Interfaces; Multispectral Scanner for Monitoring Plants; Coding for Communication Channels with Dead-Time Constraints; System for Better Spacing of Airplanes En Route; Algorithm for Training a Recurrent Multilayer Perceptron; Orbiter Interface Unit and Early Communication System; White-Light Nulling Interferometers for Detecting Planets; and Development of Methodology for Programming Autonomous Agents.

Protein-protein recognition control by modulating electrostatic interactions.

PubMed

Han, Song; Yin, Shijin; Yi, Hong; Mouhat, Stéphanie; Qiu, Su; Cao, Zhijian; Sabatier, Jean-Marc; Wu, Yingliang; Li, Wenxin

2010-06-04

Protein-protein control recognition remains a huge challenge, and its development depends on understanding the chemical and biological mechanisms by which these interactions occur. Here we describe a protein-protein control recognition technique based on the dominant electrostatic interactions occurring between the proteins. We designed a potassium channel inhibitor, BmP05-T, that was 90.32% identical to wild-type BmP05. Negatively charged residues were translocated from the nonbinding interface to the binding interface of BmP05 inhibitor, such that BmP05-T now used BmP05 nonbinding interface as the binding interface. This switch demonstrated that nonbinding interfaces were able to control the orientation of protein binding interfaces in the process of protein-protein recognition. The novel function findings of BmP05-T peptide suggested that the control recognition technique described here had the potential for use in designing and utilizing functional proteins in many biological scenarios.

T-LECS: The Control Software System for MOIRCS

NASA Astrophysics Data System (ADS)

Yoshikawa, T.; Omata, K.; Konishi, M.; Ichikawa, T.; Suzuki, R.; Tokoku, C.; Katsuno, Y.; Nishimura, T.

2006-07-01

MOIRCS (Multi-Object Infrared Camera and Spectrograph) is a new instrument for the Subaru Telescope. We present the system design of the control software system for MOIRCS, named T-LECS (Tohoku University - Layered Electronic Control System). T-LECS is a PC-Linux based network distributed system. Two PCs equipped with the focal plane array system operate two HAWAII2 detectors, respectively, and another PC is used for user interfaces and a database server. Moreover, these PCs control various devices for observations distributed on a TCP/IP network. T-LECS has three interfaces; interfaces to the devices and two user interfaces. One of the user interfaces is to the integrated observation control system (Subaru Observation Software System) for observers, and another one provides the system developers the direct access to the devices of MOIRCS. In order to help the communication between these interfaces, we employ an SQL database system.

ISS Crew Transportation and Services Requirements Document

NASA Technical Reports Server (NTRS)

Lueders, Kathryn L. (Compiler)

2015-01-01

Under the guidance of processes provided by Crew Transportation Plan (CCT-PLN-1100), this document with its sister documents, Crew Transportation Technical Management Processes (CCT-PLN-1120), Crew Transportation Technical Standards and Design Evaluation Criteria (CCT-STD-1140), and Crew Transportation Operations Standards (CCT-STD-1150), and International Space Station (ISS) to Commercial Orbital Transportation Services Interface Requirements Document (SSP 50808), provides the basis for a National Aeronautics and Space Administration (NASA) certification for services to the ISS for the Commercial Provider. When NASA Crew Transportation System (CTS) certification is achieved for ISS transportation, the Commercial Provider will be eligible to provide services to and from the ISS during the services phase of the NASA Commercial Crew Program (CCP).

Ontology-based reusable clinical document template production system.

PubMed

Nam, Sejin; Lee, Sungin; Kim, James G Boram; Kim, Hong-Gee

2012-01-01

Clinical documents embody professional clinical knowledge. This paper shows an effective clinical document template (CDT) production system that uses a clinical description entity (CDE) model, a CDE ontology, and a knowledge management system called STEP that manages ontology-based clinical description entities. The ontology represents CDEs and their inter-relations, and the STEP system stores and manages CDE ontology-based information regarding CDTs. The system also provides Web Services interfaces for search and reasoning over clinical entities. The system was populated with entities and relations extracted from 35 CDTs that were used in admission, discharge, and progress reports, as well as those used in nursing and operation functions. A clinical document template editor is shown that uses STEP.

Eye-gaze and intent: Application in 3D interface control

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

Schryver, J.C.; Goldberg, J.H.

1993-06-01

Computer interface control is typically accomplished with an input ``device`` such as keyboard, mouse, trackball, etc. An input device translates a users input actions, such as mouse clicks and key presses, into appropriate computer commands. To control the interface, the user must first convert intent into the syntax of the input device. A more natural means of computer control is possible when the computer can directly infer user intent, without need of intervening input devices. We describe an application of eye-gaze-contingent control of an interactive three-dimensional (3D) user interface. A salient feature of the user interface is natural input, withmore » a heightened impression of controlling the computer directly by the mind. With this interface, input of rotation and translation are intuitive, whereas other abstract features, such as zoom, are more problematic to match with user intent. This paper describes successes with implementation to date, and ongoing efforts to develop a more sophisticated intent inferencing methodology.« less

Eye-gaze and intent: Application in 3D interface control

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

Schryver, J.C.; Goldberg, J.H.

1993-01-01

Computer interface control is typically accomplished with an input device'' such as keyboard, mouse, trackball, etc. An input device translates a users input actions, such as mouse clicks and key presses, into appropriate computer commands. To control the interface, the user must first convert intent into the syntax of the input device. A more natural means of computer control is possible when the computer can directly infer user intent, without need of intervening input devices. We describe an application of eye-gaze-contingent control of an interactive three-dimensional (3D) user interface. A salient feature of the user interface is natural input, withmore » a heightened impression of controlling the computer directly by the mind. With this interface, input of rotation and translation are intuitive, whereas other abstract features, such as zoom, are more problematic to match with user intent. This paper describes successes with implementation to date, and ongoing efforts to develop a more sophisticated intent inferencing methodology.« less

Human-computer interface including haptically controlled interactions

DOEpatents

Anderson, Thomas G.

2005-10-11

The present invention provides a method of human-computer interfacing that provides haptic feedback to control interface interactions such as scrolling or zooming within an application. Haptic feedback in the present method allows the user more intuitive control of the interface interactions, and allows the user's visual focus to remain on the application. The method comprises providing a control domain within which the user can control interactions. For example, a haptic boundary can be provided corresponding to scrollable or scalable portions of the application domain. The user can position a cursor near such a boundary, feeling its presence haptically (reducing the requirement for visual attention for control of scrolling of the display). The user can then apply force relative to the boundary, causing the interface to scroll the domain. The rate of scrolling can be related to the magnitude of applied force, providing the user with additional intuitive, non-visual control of scrolling.

The International River Interface Cooperative: Public Domain Software for River Flow and Morphodynamics (Invited)

NASA Astrophysics Data System (ADS)

Nelson, J. M.; Shimizu, Y.; McDonald, R.; Takebayashi, H.

2009-12-01

The International River Interface Cooperative is an informal organization made up of academic faculty and government scientists with the goal of developing, distributing and providing education for a public-domain software interface for modeling river flow and morphodynamics. Formed in late 2007, the group released the first version of this interface (iRIC) in late 2009. iRIC includes models for two and three-dimensional flow, sediment transport, bed evolution, groundwater-surface water interaction, topographic data processing, and habitat assessment, as well as comprehensive data and model output visualization, mapping, and editing tools. All the tools in iRIC are specifically designed for use in river reaches and utilize common river data sets. The models are couched within a single graphical user interface so that a broad spectrum of models are available to users without learning new pre- and post-processing tools. The first version of iRIC was developed by combining the USGS public-domain Multi-Dimensional Surface Water Modeling System (MD_SWMS), developed at the USGS Geomorphology and Sediment Transport Laboratory in Golden, Colorado, with the public-domain river modeling code NAYS developed by the Universities of Hokkaido and Kyoto, Mizuho Corporation, and the Foundation of the River Disaster Prevention Research Institute in Sapporo, Japan. Since this initial effort, other Universities and Agencies have joined the group, and the interface has been expanded to allow users to integrate their own modeling code using Executable Markup Language (XML), which provides easy access and expandability to the iRIC software interface. In this presentation, the current components of iRIC are described and results from several practical modeling applications are presented to illustrate the capabilities and flexibility of the software. In addition, some future extensions to iRIC are demonstrated, including software for Lagrangian particle tracking and the prediction of bedform development and response to time-varying flows. Education and supporting documentation for iRIC, including detailed tutorials, are available at www.i-ric.org. The iRIC model codes, interface, and all supporting documentation are in the public domain.

Safety and Security Interface Technology Initiative

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

Dr. Michael A. Lehto; Kevin J. Carroll; Dr. Robert Lowrie

Safety and Security Interface Technology Initiative Mr. Kevin J. Carroll Dr. Robert Lowrie, Dr. Micheal Lehto BWXT Y12 NSC Oak Ridge, TN 37831 865-576-2289/865-241-2772 carrollkj@y12.doe.gov Work Objective. Earlier this year, the Energy Facility Contractors Group (EFCOG) was asked to assist in developing options related to acceleration deployment of new security-related technologies to assist meeting design base threat (DBT) needs while also addressing the requirements of 10 CFR 830. NNSA NA-70, one of the working group participants, designated this effort the Safety and Security Interface Technology Initiative (SSIT). Relationship to Workshop Theme. “Supporting Excellence in Operations Through Safety Analysis,” (workshop theme)more » includes security and safety personnel working together to ensure effective and efficient operations. One of the specific workshop elements listed in the call for papers is “Safeguards/Security Integration with Safety.” This paper speaks directly to this theme. Description of Work. The EFCOG Safety Analysis Working Group (SAWG) and the EFCOG Security Working Group formed a core team to develop an integrated process involving both safety basis and security needs allowing achievement of the DBT objectives while ensuring safety is appropriately considered. This effort garnered significant interest, starting with a two day breakout session of 30 experts at the 2006 Safety Basis Workshop. A core team was formed, and a series of meetings were held to develop that process, including safety and security professionals, both contractor and federal personnel. A pilot exercise held at Idaho National Laboratory (INL) in mid-July 2006 was conducted as a feasibility of concept review. Work Results. The SSIT efforts resulted in a topical report transmitted from EFCOG to DOE/NNSA in August 2006. Elements of the report included: Drivers and Endstate, Control Selections Alternative Analysis Process, Terminology Crosswalk, Safety Basis/Security Documentation Integration, Configuration Control, and development of a shared ‘tool box’ of information/successes. Specific Benefits. The expectation or end state resulting from the topical report and associated implementation plan includes: (1) A recommended process for handling the documentation of the security and safety disciplines, including an appropriate change control process and participation by all stakeholders. (2) A means to package security systems with sufficient information to help expedite the flow of that system through the process. In addition, a means to share successes among sites, to include information and safety basis to the extent such information is transportable. (3) Identification of key security systems and associated essential security elements being installed and an arrangement for the sites installing these systems to host an appropriate team to review a specific system and determine what information is exportable. (4) Identification of the security systems’ essential elements and appropriate controls required for testing of these essential elements in the facility. (5) The ability to help refine and improve an agreed to control set at the manufacture stage.« less

Operator interface for vehicles

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

Bissontz, Jay E

2015-03-10

A control interface for drivetrain braking provided by a regenerative brake and a non-regenerative brake is implemented using a combination of switches and graphic interface elements. The control interface comprises a control system for allocating drivetrain braking effort between the regenerative brake and the non-regenerative brake, a first operator actuated control for enabling operation of the drivetrain braking, and a second operator actuated control for selecting a target braking effort for drivetrain braking. A graphic display displays to an operator the selected target braking effort and can be used to further display actual braking effort achieved by drivetrain braking.

WRAP low level waste restricted waste management (LLW RWM) glovebox acceptance test report

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

Leist, K.J.

1997-11-24

On April 22, 1997, the Low Level Waste Restricted Waste Management (LLW RWM) glovebox was tested using acceptance test procedure 13027A-87. Mr. Robert L. Warmenhoven served as test director, Mr. Kendrick Leist acted as test operator and test witness, and Michael Lane provided miscellaneous software support. The primary focus of the glovebox acceptance test was to examine glovebox control system interlocks, operator Interface Unit (OIU) menus, alarms, and messages. Basic drum port and lift table control sequences were demonstrated. OIU menus, messages, and alarm sequences were examined, with few exceptions noted. Barcode testing was bypassed, due to the lack ofmore » installed equipment as well as the switch from basic reliance on fixed bar code readers to the enhanced use of portable bar code readers. Bar code testing was completed during performance of the LLW RWM OTP. Mechanical and control deficiencies were documented as Test Exceptions during performance of this Acceptance Test. These items are attached as Appendix A to this report.« less

Flight Telerobotic Servicer prototype simulator

NASA Astrophysics Data System (ADS)

Schein, Rob; Krauze, Linda; Hartley, Craig; Dickenson, Alan; Lavecchia, Tom; Working, Bob

A prototype simulator for the Flight Telerobotic Servicer (FTS) system is described for use in the design development of the FTS, emphasizing the hand controller and user interface. The simulator utilizes a graphics workstation based on rapid prototyping tools for systems analyses of the use of the user interface and the hand controller. Kinematic modeling, manipulator-control algorithms, and communications programs are contained in the software for the simulator. The hardwired FTS panels and operator interface for use on the STS Orbiter are represented graphically, and the simulated controls function as the final FTS system configuration does. The robotic arm moves based on the user hand-controller interface, and the joint angles and other data are given on the prototype of the user interface. This graphics simulation tool provides the means for familiarizing crewmembers with the FTS system operation, displays, and controls.

FSW of Aluminum Tailor Welded Blanks across Machine Platforms

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

Hovanski, Yuri; Upadhyay, Piyush; Carlson, Blair

2015-02-16

Development and characterization of friction stir welded aluminum tailor welded blanks was successfully carried out on three separate machine platforms. Each was a commercially available, gantry style, multi-axis machine designed specifically for friction stir welding. Weld parameters were developed to support high volume production of dissimilar thickness aluminum tailor welded blanks at speeds of 3 m/min and greater. Parameters originally developed on an ultra-high stiffness servo driven machine where first transferred to a high stiffness servo-hydraulic friction stir welding machine, and subsequently transferred to a purpose built machine designed to accommodate thin sheet aluminum welding. The inherent beam stiffness, bearingmore » compliance, and control system for each machine were distinctly unique, which posed specific challenges in transferring welding parameters across machine platforms. This work documents the challenges imposed by successfully transferring weld parameters from machine to machine, produced from different manufacturers and with unique control systems and interfaces.« less

[A new concept for integration of image databanks into a comprehensive patient documentation].

PubMed

Schöll, E; Holm, J; Eggli, S

2001-05-01

Image processing and archiving are of increasing importance in the practice of modern medicine. Particularly due to the introduction of computer-based investigation methods, physicians are dealing with a wide variety of analogue and digital picture archives. On the other hand, clinical information is stored in various text-based information systems without integration of image components. The link between such traditional medical databases and picture archives is a prerequisite for efficient data management as well as for continuous quality control and medical education. At the Department of Orthopedic Surgery, University of Berne, a software program was developed to create a complete multimedia electronic patient record. The client-server system contains all patients' data, questionnaire-based quality control, and a digital picture archive. Different interfaces guarantee the integration into the hospital's data network. This article describes our experiences in the development and introduction of a comprehensive image archiving system at a large orthopedic center.

A low-cost programmable pulse generator for physiology and behavior

PubMed Central

Sanders, Joshua I.; Kepecs, Adam

2014-01-01

Precisely timed experimental manipulations of the brain and its sensory environment are often employed to reveal principles of brain function. While complex and reliable pulse trains for temporal stimulus control can be generated with commercial instruments, contemporary options remain expensive and proprietary. We have developed Pulse Pal, an open source device that allows users to create and trigger software-defined trains of voltage pulses with high temporal precision. Here we describe Pulse Pal’s circuitry and firmware, and characterize its precision and reliability. In addition, we supply online documentation with instructions for assembling, testing and installing Pulse Pal. While the device can be operated as a stand-alone instrument, we also provide application programming interfaces in several programming languages. As an inexpensive, flexible and open solution for temporal control, we anticipate that Pulse Pal will be used to address a wide range of instrumentation timing challenges in neuroscience research. PMID:25566051

Keep it clean: a visual approach to reinforce hand hygiene compliance in the emergency department.

PubMed

Wiles, Lynn L; Roberts, Chris; Schmidt, Kim

2015-03-01

Although hand hygiene strategies significantly reduce health care-associated infections, multiple studies have documented that hand hygiene is the most overlooked and poorly performed infection control intervention. Emergency nurses and technicians (n = 95) in a 41-bed emergency department in eastern Virginia completed pretests and posttests, an education module, and two experiential learning activities reinforcing hand hygiene and infection control protocols. Posttest scores were significantly higher than pretest scores (t (108) = -6.928, P = .048). Hand hygiene compliance rates improved at the conclusion of the project and 3 months after the study (F (2, 15) = 9.89, P = .002). Interfaces with staff as they completed the interactive exercise, as well as anecdotal notes collected during the study, identified key times when compliance suffered and offered opportunities to further improve hand hygiene and, ultimately, patient safety. Copyright © 2015 Emergency Nurses Association. Published by Elsevier Inc. All rights reserved.

Abstracts of SIG Sessions.

ERIC Educational Resources Information Center

Proceedings of the ASIS Annual Meeting, 1996

1996-01-01

Includes abstracts of special interest group (SIG) sessions. Highlights include digital imagery; text summarization; browsing; digital libraries; icons and the Web; information management; curricula planning; interfaces; information systems; theories; scholarly and scientific communication; global development; archives; document delivery;…

SMM-UVSP ozone profile inversion programs

NASA Technical Reports Server (NTRS)

Smith, H. J. P.

1983-01-01

The documentation and user manual for the software used to invert the UVSP aeronomy data taken by the SMM are provided. The programs are described together with their interfaces and what inputs are required from the user.

Astronomy sortie missions definition study. Volume 2, book 2: Appendix

NASA Technical Reports Server (NTRS)

1972-01-01

An updated and coordinated baseline experiment definition document is presented for each of the candidate astronomy sortie mission telescopes and arrays. The experiment objectives, requirements, interfaces, timelines, and programmatic considerations are included.

Math Description Engine Software Development Kit

NASA Technical Reports Server (NTRS)

Shelton, Robert O.; Smith, Stephanie L.; Dexter, Dan E.; Hodgson, Terry R.

2010-01-01

The Math Description Engine Software Development Kit (MDE SDK) can be used by software developers to make computer-rendered graphs more accessible to blind and visually-impaired users. The MDE SDK generates alternative graph descriptions in two forms: textual descriptions and non-verbal sound renderings, or sonification. It also enables display of an animated trace of a graph sonification on a visual graph component, with color and line-thickness options for users having low vision or color-related impairments. A set of accessible graphical user interface widgets is provided for operation by end users and for control of accessible graph displays. Version 1.0 of the MDE SDK generates text descriptions for 2D graphs commonly seen in math and science curriculum (and practice). The mathematically rich text descriptions can also serve as a virtual math and science assistant for blind and sighted users, making graphs more accessible for everyone. The MDE SDK has a simple application programming interface (API) that makes it easy for programmers and Web-site developers to make graphs accessible with just a few lines of code. The source code is written in Java for cross-platform compatibility and to take advantage of Java s built-in support for building accessible software application interfaces. Compiled-library and NASA Open Source versions are available with API documentation and Programmer s Guide at http:/ / prim e.jsc.n asa. gov.

Chemical Control of Lead Sulfide Quantum Dot Shape, Self-Assembly, and Charge Transport

NASA Astrophysics Data System (ADS)

McPhail, Martin R.

Lead(II) sulfide quantum dots (PbS QDs) are a promising excitonic material for numerous application that require that control of fluxes of charge and energy at nanoscale interfaces, such as solar energy conversion, photo- and electrocatalysis, light emitting diodes, chemical sensing, single-electron logic elements, field effect transistors, and photovoltaics. PbS QDs are particularly suitable for photonics applications because they exhibit size-tunable band-edge absorption and fluorescence across the entire near-infrared spectrum, undergo efficient multi-exciton generation, exhibit a long radiative lifetime, and possess an eight-fold degenerate ground-state. The effective integration of PbS QDs into these applications requires a thorough understanding of how to control their synthesis, self-assembly, and charge transport phenomena. In this document, I describe a series of experiments to elucidate three levels of chemical control on the emergent properties of PbS QDs: (1) the role of surface chemistry in controlling PbS QD shape during solvothermal synthesis, (2) the role of QD shape and ligand functionalization in self-assembly at a liquid-air interface, and (3) the role of QD packing structure on steady-state conductivity and transient current dynamics. At the synthetic level (1), I show that the final shape and surface chemistry of PbS QDs is highly sensitive to the formation of organosulfur byproducts by commonly used sulfur reagents. The insight into PbS QD growth gained from this work is then developed to controllably tune PbS QD shape from cubic to octahedral to hexapodal while maintaining QD size. At the following level of QD self-assembly (2), I show how QD size and shape dictate packing geometry in extended 2D arrays and how this packing can be controllably interrupted in mixed monolayers. I also study the role of ligand structure on the reorganization of QD arrays at a liquid-air interface and find that the specific packing defects in QD arrays vary depending on exchange kinetics and ligand binding geometry. At the final level of emergent macroscopic properties (3), I show that while the size-dependent conductivity of quasi-2D PbS QD arrays can be explained by a simple diffusional hopping model that only accounts for nearest-neighbor interactions, the transient photocurrent dynamics are extremely sensitive to the morphology of the entire percolation network formed by the QDs.

PNNI Performance Validation Test Report

NASA Technical Reports Server (NTRS)

Dimond, Robert P.

1999-01-01

Two Private Network-Network Interface (PNNI) neighboring peers were monitored with a protocol analyzer to understand and document how PNNI works with regards to initialization and recovery processes. With the processes documented, pertinent events were found and measured to determine the protocols behavior in several environments, which consisted of congestion and/or delay. Subsequent testing of the protocol in these environments was conducted to determine the protocol's suitability for use in satellite-terrestrial network architectures.

ICESat (GLAS) Science Processing Software Document Series. Volume 2; Science Data Management Plan; 4.0

NASA Technical Reports Server (NTRS)

Jester, Peggy L.; Hancock, David W., III

1999-01-01

This document provides the Data Management Plan for the GLAS Standard Data Software (SDS) supporting the GLAS instrument of the EOS ICESat Spacecraft. The SDS encompasses the ICESat Science Investigator-led Processing System (I-SIPS) Software and the Instrument Support Facility (ISF) Software. This Plan addresses the identification, authority, and description of the interface nodes associated with the GLAS Standard Data Products and the GLAS Ancillary Data.

Electromigration-induced drift in damascene and plasma-etched Al(Cu). II. Mass transport mechanisms in bamboo interconnects

NASA Astrophysics Data System (ADS)

Proost, Joris; Maex, Karen; Delacy, Luc

2000-01-01

We have discussed electromigration (EM)-induced drift in polycrystalline damascene versus reactive ion etched (RIE) Al(Cu) in part I. For polycrystalline Al(Cu), mass transport is well documented to occur through sequential stages : an incubation period (attributed to Cu depletion beyond a critical length) followed by the Al drift stage. In this work, the drift behavior of bamboo RIE and damascene Al(Cu) is analyzed. Using Blech-type test structures, mass transport in RIE lines was shown to proceed both by lattice and interfacial diffusion. The dominating mechanism depends on the Cu distribution in the line, as was evidenced by comparing as-patterned (lattice EM) and RTP-annealed (interface EM) samples. The interfacial EM only occurs at metallic interfaces. In that case, Cu alloying was observed to retard Al interfacial mass transport, giving rise to an incubation time. Although the activation energy for the incubation time was found similar to the one controlling Al lattice drift, for which no incubation time was observed, lattice EM is preferred over interfacial EM because it is insensitive to enhancing geometrical effects upon scaling. When comparing interfacial electromigration in RIE with bamboo damascene Al(Cu), with the incubation time rate controlling for both, the higher EM threshold observed for damascene was shown to be insufficient to compensate for its significantly increased Cu depletion rate, contrary to the case of polycrystalline Al(Cu) interconnects. Two factors were demonstrated to contribute. First, there are more metallic interfaces, intrinsically related to the use of wetting or barrier layers in recessed features. Second, specific to this study, the additional formation of TiAl3 at the trench sidewalls further enhanced the Cu depletion rate, and reduced the rate-controlling incubation time. A separate drift study on RIE via-type test structures indicated that it is very difficult to suppress interfacial mass transport in favor of lattice EM upon TiAl3 formation.

Human factors in air traffic control: problems at the interfaces.

PubMed

Shouksmith, George

2003-10-01

The triangular ISIS model for describing the operation of human factors in complex sociotechnical organisations or systems is applied in this research to a large international air traffic control system. A large sample of senior Air Traffic Controllers were randomly assigned to small focus discussion groups, whose task was to identify problems occurring at the interfaces of the three major human factor components: individual, system impacts, and social. From these discussions, a number of significant interface problems, which could adversely affect the functioning of the Air Traffic Control System, emerged. The majority of these occurred at the Individual-System Impact and Individual-Social interfaces and involved a perceived need for further interface centered training.

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.

Updating Human Factors Engineering Guidelines for Conducting Safety Reviews of Nuclear Power Plants

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

O, J.M.; Higgins, J.; Stephen Fleger - NRC

The U.S. Nuclear Regulatory Commission (NRC) reviews the human factors engineering (HFE) programs of applicants for nuclear power plant construction permits, operating licenses, standard design certifications, and combined operating licenses. The purpose of these safety reviews is to help ensure that personnel performance and reliability are appropriately supported. Detailed design review procedures and guidance for the evaluations is provided in three key documents: the Standard Review Plan (NUREG-0800), the HFE Program Review Model (NUREG-0711), and the Human-System Interface Design Review Guidelines (NUREG-0700). These documents were last revised in 2007, 2004 and 2002, respectively. The NRC is committed to the periodicmore » update and improvement of the guidance to ensure that it remains a state-of-the-art design evaluation tool. To this end, the NRC is updating its guidance to stay current with recent research on human performance, advances in HFE methods and tools, and new technology being employed in plant and control room design. This paper describes the role of HFE guidelines in the safety review process and the content of the key HFE guidelines used. Then we will present the methodology used to develop HFE guidance and update these documents, and describe the current status of the update program.« less

Human Factors Engineering Program Review Model (NUREG-0711)Revision 3: Update Methodology and Key Revisions

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

OHara J. M.; Higgins, J.; Fleger, S.

The U.S. Nuclear Regulatory Commission (NRC) reviews the human factors engineering (HFE) programs of applicants for nuclear power plant construction permits, operating licenses, standard design certifications, and combined operating licenses. The purpose of these safety reviews is to help ensure that personnel performance and reliability are appropriately supported. Detailed design review procedures and guidance for the evaluations is provided in three key documents: the Standard Review Plan (NUREG-0800), the HFE Program Review Model (NUREG-0711), and the Human-System Interface Design Review Guidelines (NUREG-0700). These documents were last revised in 2007, 2004 and 2002, respectively. The NRC is committed to the periodicmore » update and improvement of the guidance to ensure that it remains a state-of-the-art design evaluation tool. To this end, the NRC is updating its guidance to stay current with recent research on human performance, advances in HFE methods and tools, and new technology being employed in plant and control room design. NUREG-0711 is the first document to be addressed. We present the methodology used to update NUREG-0711 and summarize the main changes made. Finally, we discuss the current status of the update program and the future plans.« less

Control of interface shape during high melting sesquioxide crystal growth by HEM technique

NASA Astrophysics Data System (ADS)

Hu, Kaiwei; Zheng, Lili; Zhang, Hui

2018-02-01

During crystal growth in heat exchanger method (HEM) system, the shape of the growth interface changes with the proceeding of the growth process, which limits the crystal size and reduces the quality of the crystal. In this paper, a modified HEM system is proposed to control the interface shape for growth of sesquioxide crystals. Numerical simulation is performed to predict heat transfer, melt flow and interface shape during growth of high melting sesquioxide crystals by the heat exchanger method. The results show that a flat or slightly convex interface shape is beneficial to reduce the solute pileup in front of the melt/crystal interface and decrease the radial temperature gradient inside the crystal during growth of sesquioxide crystals. The interface shape can be controlled by adjusting the gap size d and lower resistance heater power during growth. The growth rate and the melt/crystal interface position can be obtained by two measured temperatures.

Combined Cycle Engine Large-Scale Inlet for Mode Transition Experiments: System Identification Rack Hardware Design

NASA Technical Reports Server (NTRS)

Thomas, Randy; Stueber, Thomas J.

2013-01-01

The System Identification (SysID) Rack is a real-time hardware-in-the-loop data acquisition (DAQ) and control instrument rack that was designed and built to support inlet testing in the NASA Glenn Research Center 10- by 10-Foot Supersonic Wind Tunnel. This instrument rack is used to support experiments on the Combined-Cycle Engine Large-Scale Inlet for Mode Transition Experiment (CCE? LIMX). The CCE?LIMX is a testbed for an integrated dual flow-path inlet configuration with the two flow paths in an over-and-under arrangement such that the high-speed flow path is located below the lowspeed flow path. The CCE?LIMX includes multiple actuators that are designed to redirect airflow from one flow path to the other; this action is referred to as "inlet mode transition." Multiple phases of experiments have been planned to support research that investigates inlet mode transition: inlet characterization (Phase-1) and system identification (Phase-2). The SysID Rack hardware design met the following requirements to support Phase-1 and Phase-2 experiments: safely and effectively move multiple actuators individually or synchronously; sample and save effector control and position sensor feedback signals; automate control of actuator positioning based on a mode transition schedule; sample and save pressure sensor signals; and perform DAQ and control processes operating at 2.5 KHz. This document describes the hardware components used to build the SysID Rack including their function, specifications, and system interface. Furthermore, provided in this document are a SysID Rack effectors signal list (signal flow); system identification experiment setup; illustrations indicating a typical SysID Rack experiment; and a SysID Rack performance overview for Phase-1 and Phase-2 experiments. The SysID Rack described in this document was a useful tool to meet the project objectives.

Interacting with Petabytes of Earth Science Data using Jupyter Notebooks, IPython Widgets and Google Earth Engine

NASA Astrophysics Data System (ADS)

Erickson, T. A.; Granger, B.; Grout, J.; Corlay, S.

2017-12-01

The volume of Earth science data gathered from satellites, aircraft, drones, and field instruments continues to increase. For many scientific questions in the Earth sciences, managing this large volume of data is a barrier to progress, as it is difficult to explore and analyze large volumes of data using the traditional paradigm of downloading datasets to a local computer for analysis. Furthermore, methods for communicating Earth science algorithms that operate on large datasets in an easily understandable and reproducible way are needed. Here we describe a system for developing, interacting, and sharing well-documented Earth Science algorithms that combines existing software components: Jupyter Notebook: An open-source, web-based environment that supports documents that combine code and computational results with text narrative, mathematics, images, and other media. These notebooks provide an environment for interactive exploration of data and development of well documented algorithms. Jupyter Widgets / ipyleaflet: An architecture for creating interactive user interface controls (such as sliders, text boxes, etc.) in Jupyter Notebooks that communicate with Python code. This architecture includes a default set of UI controls (sliders, dropboxes, etc.) as well as APIs for building custom UI controls. The ipyleaflet project is one example that offers a custom interactive map control that allows a user to display and manipulate geographic data within the Jupyter Notebook. Google Earth Engine: A cloud-based geospatial analysis platform that provides access to petabytes of Earth science data via a Python API. The combination of Jupyter Notebooks, Jupyter Widgets, ipyleaflet, and Google Earth Engine makes it possible to explore and analyze massive Earth science datasets via a web browser, in an environment suitable for interactive exploration, teaching, and sharing. Using these environments can make Earth science analyses easier to understand and reproducible, which may increase the rate of scientific discoveries and the transition of discoveries into real-world impacts.

An overview of the evaluation plan for PC/MISI: PC-based Multiple Information System Interface

NASA Technical Reports Server (NTRS)

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

1985-01-01

An initial evaluation plan for the personal computer multiple information system interface (PC/MISI) project is discussed. The document is intend to be used as a blueprint for the evaluation of this system. Each objective of the design project is discussed along with the evaluation parameters and methodology to be used in the evaluation of the implementation's achievement of those objectives. The potential of the system for research activities related to more general aspects of information retrieval is also discussed.

pytc: Open-Source Python Software for Global Analyses of Isothermal Titration Calorimetry Data.

PubMed

Duvvuri, Hiranmayi; Wheeler, Lucas C; Harms, Michael J

2018-05-08

Here we describe pytc, an open-source Python package for global fits of thermodynamic models to multiple isothermal titration calorimetry experiments. Key features include simplicity, the ability to implement new thermodynamic models, a robust maximum likelihood fitter, a fast Bayesian Markov-Chain Monte Carlo sampler, rigorous implementation, extensive documentation, and full cross-platform compatibility. pytc fitting can be done using an application program interface or via a graphical user interface. It is available for download at https://github.com/harmslab/pytc .

The ADAMS interactive interpreter

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

Rietscha, E.R.

1990-12-17

The ADAMS (Advanced DAta Management System) project is exploring next generation database technology. Database management does not follow the usual programming paradigm. Instead, the database dictionary provides an additional name space environment that should be interactively created and tested before writing application code. This document describes the implementation and operation of the ADAMS Interpreter, an interactive interface to the ADAMS data dictionary and runtime system. The Interpreter executes individual statements of the ADAMS Interface Language, providing a fast, interactive mechanism to define and access persistent databases. 5 refs.

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.

Intelligent Multi-Media Integrated Interface Project

DTIC Science & Technology

1990-06-01

RADC (COES) Griffiss AFB NY 13441-5700. This will assist us in main- taining a current mailing list. Do not return copies of this report unless...contractual obligations or notices on a specific document require that it be returned. INTELLIGENT MULTI-MEDIA INTEGRATED INTERFACE PROJECT J. G. Neal J. M...lure ag. A = W qMN 1. AGENCY USE ONLY AM BW 2. REPORT DATE R,,PE AND DATES COYERED June 1990 Final Oct 87 to Oct 89 4. TTLE AND SUIlllLE S. FUNDING

Interface For Fault-Tolerant Control System

NASA Technical Reports Server (NTRS)

Shaver, Charles; Williamson, Michael

1989-01-01

Interface unit and controller emulator developed for research on electronic helicopter-flight-control systems equipped with artificial intelligence. Interface unit interrupt-driven system designed to link microprocessor-based, quadruply-redundant, asynchronous, ultra-reliable, fault-tolerant control system (controller) with electronic servocontrol unit that controls set of hydraulic actuators. Receives digital feedforward messages from, and transmits digital feedback messages to, controller through differential signal lines or fiber-optic cables (thus far only differential signal lines have been used). Analog signals transmitted to and from servocontrol unit via coaxial cables.

Comparison of tongue interface with keyboard for control of an assistive robotic arm.

PubMed

Struijk, Lotte N S Andreasen; Lontis, Romulus

2017-07-01

This paper demonstrates how an assistive 6 DoF robotic arm with a gripper can be controlled manually using a tongue interface. The proposed method suggests that it possible for a user to manipulate the surroundings with his or her tongue using the inductive tongue control system as deployed in this study. The sensors of an inductive tongue-computer interface were mapped to the Cartesian control of an assistive robotic arm. The resulting control system was tested manually in order to compare manual control of the robot using a standard keyboard and using the tongue interface. Two healthy subjects controlled the robotic arm to precisely move a bottle of water from one location to another. The results shows that the tongue interface was able to fully control the robotic arm in a similar manner as the standard keyboard resulting in the same number of successful manipulations and an average increase in task duration of up to 30% as compared with the standard keyboard.

Factors associated with interest in novel interfaces for upper limb prosthesis control

PubMed Central

Engdahl, Susannah M.; Chestek, Cynthia A.; Kelly, Brian; Davis, Alicia

2017-01-01

Background Surgically invasive interfaces for upper limb prosthesis control may allow users to operate advanced, multi-articulated devices. Given the potential medical risks of these invasive interfaces, it is important to understand what factors influence an individual’s decision to try one. Methods We conducted an anonymous online survey of individuals with upper limb loss. A total of 232 participants provided personal information (such as age, amputation level, etc.) and rated how likely they would be to try noninvasive (myoelectric) and invasive (targeted muscle reinnervation, peripheral nerve interfaces, cortical interfaces) interfaces for prosthesis control. Bivariate relationships between interest in each interface and 16 personal descriptors were examined. Significant variables from the bivariate analyses were then entered into multiple logistic regression models to predict interest in each interface. Results While many of the bivariate relationships were significant, only a few variables remained significant in the regression models. The regression models showed that participants were more likely to be interested in all interfaces if they had unilateral limb loss (p ≤ 0.001, odds ratio ≥ 2.799). Participants were more likely to be interested in the three invasive interfaces if they were younger (p < 0.001, odds ratio ≤ 0.959) and had acquired limb loss (p ≤ 0.012, odds ratio ≥ 3.287). Participants who used a myoelectric device were more likely to be interested in myoelectric control than those who did not (p = 0.003, odds ratio = 24.958). Conclusions Novel prosthesis control interfaces may be accepted most readily by individuals who are young, have unilateral limb loss, and/or have acquired limb loss However, this analysis did not include all possible factors that may have influenced participant’s opinions on the interfaces, so additional exploration is warranted. PMID:28767716

Factors associated with interest in novel interfaces for upper limb prosthesis control.

PubMed

Engdahl, Susannah M; Chestek, Cynthia A; Kelly, Brian; Davis, Alicia; Gates, Deanna H

2017-01-01

Surgically invasive interfaces for upper limb prosthesis control may allow users to operate advanced, multi-articulated devices. Given the potential medical risks of these invasive interfaces, it is important to understand what factors influence an individual's decision to try one. We conducted an anonymous online survey of individuals with upper limb loss. A total of 232 participants provided personal information (such as age, amputation level, etc.) and rated how likely they would be to try noninvasive (myoelectric) and invasive (targeted muscle reinnervation, peripheral nerve interfaces, cortical interfaces) interfaces for prosthesis control. Bivariate relationships between interest in each interface and 16 personal descriptors were examined. Significant variables from the bivariate analyses were then entered into multiple logistic regression models to predict interest in each interface. While many of the bivariate relationships were significant, only a few variables remained significant in the regression models. The regression models showed that participants were more likely to be interested in all interfaces if they had unilateral limb loss (p ≤ 0.001, odds ratio ≥ 2.799). Participants were more likely to be interested in the three invasive interfaces if they were younger (p < 0.001, odds ratio ≤ 0.959) and had acquired limb loss (p ≤ 0.012, odds ratio ≥ 3.287). Participants who used a myoelectric device were more likely to be interested in myoelectric control than those who did not (p = 0.003, odds ratio = 24.958). Novel prosthesis control interfaces may be accepted most readily by individuals who are young, have unilateral limb loss, and/or have acquired limb loss However, this analysis did not include all possible factors that may have influenced participant's opinions on the interfaces, so additional exploration is warranted.

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.

Improvements to the User Interface for LHCb's Software continuous integration system.

NASA Astrophysics Data System (ADS)

Clemencic, M.; Couturier, B.; Kyriazi, S.

2015-12-01

The purpose of this paper is to identify a set of steps leading to an improved interface for LHCb's Nightly Builds Dashboard. The goal is to have an efficient application that meets the needs of both the project developers, by providing them with a user friendly interface, as well as those of the computing team supporting the system, by providing them with a dashboard allowing for better monitoring of the build job themselves. In line with what is already used by LHCb, the web interface has been implemented with the Flask Python framework for future maintainability and code clarity. The Database chosen to host the data is the schema-less CouchDB[7], serving the purpose of flexibility in document form changes. To improve the user experience, we use JavaScript libraries such as JQuery[11].

Chemical Bonding Technology: Direct Investigation of Interfacial Bonds

NASA Technical Reports Server (NTRS)

Koenig, J. L.; Boerio, F. J.; Plueddemann, E. P.; Miller, J.; Willis, P. B.; Cuddihy, E. F.

1986-01-01

This is the third Flat-Plate Solar Array (FSA) Project document reporting on chemical bonding technology for terrestrial photovoltaic (PV) modules. The impetus for this work originated in the late 1970s when PV modules employing silicone encapsulation materials were undergoing delamination during outdoor exposure. At that time, manufacturers were not employing adhesion promoters and, hence, module interfaces in common with the silicone materials were only in physical contact and therefore easily prone to separation if, for example, water were to penetrate to the interfaces. Delamination with silicone materials virtually vanished when adhesion promoters, recommended by silicone manufacturers, were used. The activities related to the direct investigation of chemically bonded interfaces are described.

Comparison of electromyography and force as interfaces for prosthetic control.

PubMed

Corbett, Elaine A; Perreault, Eric J; Kuiken, Todd A

2011-01-01

The ease with which persons with upper-limb amputations can control their powered prostheses is largely determined by the efficacy of the user command interface. One needs to understand the abilities of the human operator regarding the different available options. Electromyography (EMG) is widely used to control powered upper-limb prostheses. It is an indirect estimator of muscle force and may be expected to limit the control capabilities of the prosthesis user. This study compared EMG control with force control, an interface that is used in everyday interactions with the environment. We used both methods to perform a position-tracking task. Direct-position control of the wrist provided an upper bound for human-operator capabilities. The results demonstrated that an EMG control interface is as effective as force control for the position-tracking task. We also examined the effects of gain and tracking frequency on EMG control to explore the limits of this control interface. We found that information transmission rates for myoelectric control were best at higher tracking frequencies than at the frequencies previously reported for position control. The results may be useful for the design of prostheses and prosthetic controllers.

Attoliter Control of Microliquid

NASA Astrophysics Data System (ADS)

Imura, Fumito; Kuroiwa, Hiroyuki; Nakada, Akira; Kosaka, Kouji; Kubota, Hiroshi

2007-11-01

The technology of the sub-femtoliter volume control of liquids in nanometer range pipettes (nanopipettes) has been developed for carrying out surgical operations on living cells. We focus attention on an interface forming between oil and water in a nanopipette. The interface position can be moved by increasing or decreasing the input pressure. If the volume of liquid in the nanopipette can be controlled by moving the position of the interface, cell organelles can be discharged or suctioned and a drug-solution can be injected into the cell. Quantity volume control in the pico-attoliter range using a tapered nanopipette is controlled by the condition of an interface with a convex shape toward the top of the nanopipette. The volume can be controlled by the input pressure corresponding to the interfacial radius without the use of a microscope by preliminarily preparing the pipette shape and the interface radius as a function of the input pressure.

An Overview of Radiation-Induced Interface Traps in MOS (Metal-Oxide Semiconductor) Structures

DTIC Science & Technology

1989-11-01

to be Controlled by hole transport to the Si/S1 02 interface and by neutral hydrogen diffusion, respectively. ’We also discuss several models which...trivalent Si which is undergo a dispersive hopping transport which not mobile and a mobile nonbridging oxygen. controls the rate of interface state... control the buildup of ping event itself seems to be a phonon-assisted radiation-induced interface states are subjects tunneling transition between

Defining brain-machine interface applications by matching interface performance with device requirements.

PubMed

Tonet, Oliver; Marinelli, Martina; Citi, Luca; Rossini, Paolo Maria; Rossini, Luca; Megali, Giuseppe; Dario, Paolo

2008-01-15

Interaction with machines is mediated by human-machine interfaces (HMIs). Brain-machine interfaces (BMIs) are a particular class of HMIs and have so far been studied as a communication means for people who have little or no voluntary control of muscle activity. In this context, low-performing interfaces can be considered as prosthetic applications. On the other hand, for able-bodied users, a BMI would only be practical if conceived as an augmenting interface. In this paper, a method is introduced for pointing out effective combinations of interfaces and devices for creating real-world applications. First, devices for domotics, rehabilitation and assistive robotics, and their requirements, in terms of throughput and latency, are described. Second, HMIs are classified and their performance described, still in terms of throughput and latency. Then device requirements are matched with performance of available interfaces. Simple rehabilitation and domotics devices can be easily controlled by means of BMI technology. Prosthetic hands and wheelchairs are suitable applications but do not attain optimal interactivity. Regarding humanoid robotics, the head and the trunk can be controlled by means of BMIs, while other parts require too much throughput. Robotic arms, which have been controlled by means of cortical invasive interfaces in animal studies, could be the next frontier for non-invasive BMIs. Combining smart controllers with BMIs could improve interactivity and boost BMI applications.

Speedy Alchemy.

ERIC Educational Resources Information Center

Deininger, Rolf A.; Berger, Carl F., Jr.

1983-01-01

Provides instructions for interfacing a pH meter directly to an Apple II microcomputer without an analog-to-digital converter. Includes program listing (with enough remark statements to make it self-documenting) in Integer Basic to display the pH readings. (Author/JN)

Efficient Verification of Holograms Using Mobile Augmented Reality.

PubMed

Hartl, Andreas Daniel; Arth, Clemens; Grubert, Jens; Schmalstieg, Dieter

2016-07-01

Paper documents such as passports, visas and banknotes are frequently checked by inspection of security elements. In particular, optically variable devices such as holograms are important, but difficult to inspect. Augmented Reality can provide all relevant information on standard mobile devices. However, hologram verification on mobiles still takes long and provides lower accuracy than inspection by human individuals using appropriate reference information. We aim to address these drawbacks by automatic matching combined with a special parametrization of an efficient goal-oriented user interface which supports constrained navigation. We first evaluate a series of similarity measures for matching hologram patches to provide a sound basis for automatic decisions. Then a re-parametrized user interface is proposed based on observations of typical user behavior during document capture. These measures help to reduce capture time to approximately 15 s with better decisions regarding the evaluated samples than what can be achieved by untrained users.

Challenges And Concepts for Design of An Interaction Region With Push-Pull Arrangement of Detectors - An Interface Document

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

Parker, B.; /Brookhaven; Herve, Alain

2011-10-14

Two experimental detectors working in a push-pull mode has been considered for the Interaction Region of the International Linear Collider. The push-pull mode of operation sets specific requirements and challenges for many systems of detector and machine, in particular for the IR magnets, for the cryogenics and alignment system, for beamline shielding, for detector design and overall integration, and so on. These challenges and the identified conceptual solutions discussed in the paper intend to form a draft of the Interface Document which will be developed further in the nearest future. The authors of the present paper include the organizers andmore » conveners of working groups of the workshop on engineering design of interaction region IRENG07, the leaders of the IR Integration within Global Design Effort Beam Delivery System, and the representatives from each detector concept submitting the Letters Of Intent.« less

Medical record management systems: criticisms and new perspectives.

PubMed

Frénot, S; Laforest, F

1999-06-01

The first generation of computerized medical records stored the data as text, but these records did not bring any improvement in information manipulation. The use of a relational database management system (DBMS) has largely solved this problem as it allows for data requests by using SQL. However, this requires data structuring which is not very appropriate to medicine. Moreover, the use of templates and icon user interfaces has introduced a deviation from the paper-based record (still existing). The arrival of hypertext user interfaces has proven to be of interest to fill the gap between the paper-based medical record and its electronic version. We think that further improvement can be accomplished by using a fully document-based system. We present the architecture, advantages and disadvantages of classical DBMS-based and Web/DBMS-based solutions. We also present a document-based solution and explain its advantages, which include communication, security, flexibility and genericity.

Step 1: C3 Flight Demo Data Analysis Plan

NASA Technical Reports Server (NTRS)

2005-01-01

The Data Analysis Plan (DAP) describes the data analysis that the C3 Work Package (WP) will perform in support of the Access 5 Step 1 C3 flight demonstration objectives as well as the processes that will be used by the Flight IPT to gather and distribute the data collected to satisfy those objectives. In addition to C3 requirements, this document will encompass some Human Systems Interface (HSI) requirements in performing the C3 flight demonstrations. The C3 DAP will be used as the primary interface requirements document between the C3 Work Package and Flight Test organizations (Flight IPT and Non-Access 5 Flight Programs). In addition to providing data requirements for Access 5 flight test (piggyback technology demonstration flights, dedicated C3 technology demonstration flights, and Airspace Operations Demonstration flights), the C3 DAP will be used to request flight data from Non- Access 5 flight programs for C3 related data products

Speech Recognition as a Transcription Aid: A Randomized Comparison With Standard Transcription

PubMed Central

Mohr, David N.; Turner, David W.; Pond, Gregory R.; Kamath, Joseph S.; De Vos, Cathy B.; Carpenter, Paul C.

2003-01-01

Objective. Speech recognition promises to reduce information entry costs for clinical information systems. It is most likely to be accepted across an organization if physicians can dictate without concerning themselves with real-time recognition and editing; assistants can then edit and process the computer-generated document. Our objective was to evaluate the use of speech-recognition technology in a randomized controlled trial using our institutional infrastructure. Design. Clinical note dictations from physicians in two specialty divisions were randomized to either a standard transcription process or a speech-recognition process. Secretaries and transcriptionists also were assigned randomly to each of these processes. Measurements. The duration of each dictation was measured. The amount of time spent processing a dictation to yield a finished document also was measured. Secretarial and transcriptionist productivity, defined as hours of secretary work per minute of dictation processed, was determined for speech recognition and standard transcription. Results. Secretaries in the endocrinology division were 87.3% (confidence interval, 83.3%, 92.3%) as productive with the speech-recognition technology as implemented in this study as they were using standard transcription. Psychiatry transcriptionists and secretaries were similarly less productive. Author, secretary, and type of clinical note were significant (p < 0.05) predictors of productivity. Conclusion. When implemented in an organization with an existing document-processing infrastructure (which included training and interfaces of the speech-recognition editor with the existing document entry application), speech recognition did not improve the productivity of secretaries or transcriptionists. PMID:12509359

Temperature and melt solid interface control during crystal growth

NASA Technical Reports Server (NTRS)

Batur, Celal

1990-01-01

Findings on the adaptive control of a transparent Bridgman crystal growth furnace are summarized. The task of the process controller is to establish a user specified axial temperature profile by controlling the temperatures in eight heating zones. The furnace controller is built around a computer. Adaptive PID (Proportional Integral Derivative) and Pole Placement control algorithms are applied. The need for adaptive controller stems from the fact that the zone dynamics changes with respect to time. The controller was tested extensively on the Lead Bromide crystal growth. Several different temperature profiles and ampoule's translational rates are tried. The feasibility of solid liquid interface quantification by image processing was determined. The interface is observed by a color video camera and the image data file is processed to determine if the interface is flat, convex or concave.

An EMG-based robot control scheme robust to time-varying EMG signal features.

PubMed

Artemiadis, Panagiotis K; Kyriakopoulos, Kostas J

2010-05-01

Human-robot control interfaces have received increased attention during the past decades. With the introduction of robots in everyday life, especially in providing services to people with special needs (i.e., elderly, people with impairments, or people with disabilities), there is a strong necessity for simple and natural control interfaces. In this paper, electromyographic (EMG) signals from muscles of the human upper limb are used as the control interface between the user and a robot arm. EMG signals are recorded using surface EMG electrodes placed on the user's skin, making the user's upper limb free of bulky interface sensors or machinery usually found in conventional human-controlled systems. The proposed interface allows the user to control in real time an anthropomorphic robot arm in 3-D space, using upper limb motion estimates based only on EMG recordings. Moreover, the proposed interface is robust to EMG changes with respect to time, mainly caused by muscle fatigue or adjustments of contraction level. The efficiency of the method is assessed through real-time experiments, including random arm motions in the 3-D space with variable hand speed profiles.

Serial Interface through Stream Protocol on EPICS Platform for Distributed Control and Monitoring

NASA Astrophysics Data System (ADS)

Das Gupta, Arnab; Srivastava, Amit K.; Sunil, S.; Khan, Ziauddin

2017-04-01

Remote operation of any equipment or device is implemented in distributed systems in order to control and proper monitoring of process values. For such remote operations, Experimental Physics and Industrial Control System (EPICS) is used as one of the important software tool for control and monitoring of a wide range of scientific parameters. A hardware interface is developed for implementation of EPICS software so that different equipment such as data converters, power supplies, pump controllers etc. could be remotely operated through stream protocol. EPICS base was setup on windows as well as Linux operating system for control and monitoring while EPICS modules such as asyn and stream device were used to interface the equipment with standard RS-232/RS-485 protocol. Stream Device protocol communicates with the serial line with an interface to asyn drivers. Graphical user interface and alarm handling were implemented with Motif Editor and Display Manager (MEDM) and Alarm Handler (ALH) command line channel access utility tools. This paper will describe the developed application which was tested with different equipment and devices serially interfaced to the PCs on a distributed network.

System and methods for reducing harmonic distortion in electrical converters

DOEpatents

Kajouke, Lateef A; Perisic, Milun; Ransom, Ray M

2013-12-03

Systems and methods are provided for delivering energy using an energy conversion module. An exemplary method for delivering energy from an input interface to an output interface using an energy converison module coupled between the input interface and the output interface comprises the steps of determining an input voltage reference for the input interface based on a desired output voltage and a measured voltage and the output interface, determining a duty cycle control value based on a ratio of the input voltage reference and the measured voltage, operating one or more switching elements of the energy conversion module to deliver energy from the input interface to the output interface to the output interface with a duty cycle influenced by the dute cycle control value.

Technology Developments Integrating a Space Network Communications Testbed

NASA Technical Reports Server (NTRS)

Kwong, Winston; Jennings, Esther; Clare, Loren; Leang, Dee

2006-01-01

As future manned and robotic space explorations missions involve more complex systems, it is essential to verify, validate, and optimize such systems through simulation and emulation in a low cost testbed environment. The goal of such a testbed is to perform detailed testing of advanced space and ground communications networks, technologies, and client applications that are essential for future space exploration missions. We describe the development of new technologies enhancing our Multi-mission Advanced Communications Hybrid Environment for Test and Evaluation (MACHETE) that enable its integration in a distributed space communications testbed. MACHETE combines orbital modeling, link analysis, and protocol and service modeling to quantify system performance based on comprehensive considerations of different aspects of space missions. It can simulate entire networks and can interface with external (testbed) systems. The key technology developments enabling the integration of MACHETE into a distributed testbed are the Monitor and Control module and the QualNet IP Network Emulator module. Specifically, the Monitor and Control module establishes a standard interface mechanism to centralize the management of each testbed component. The QualNet IP Network Emulator module allows externally generated network traffic to be passed through MACHETE to experience simulated network behaviors such as propagation delay, data loss, orbital effects and other communications characteristics, including entire network behaviors. We report a successful integration of MACHETE with a space communication testbed modeling a lunar exploration scenario. This document is the viewgraph slides of the presentation.

Lunar Entry Downmode Options for Orion

NASA Technical Reports Server (NTRS)

Smith, Kelly M.; Rea, Jeremy

2016-01-01

For Exploration Missions 1 and 2, the Orion capsules will be entering the Earth's atmosphere with speeds in excess of 11 km/s. In the event of a degraded Guidance, Navigation, and Control system, attempting the nominal guided entry may be inadvisable due to the potential for failures that result in a loss of vehicle (or crew, when crew are aboard). In such a case, a method of assuring Earth capture, water landing, and observence of trajectory constraints (heating, loads) is desired. Such a method should also be robust to large state uncertainty and variations in entry interface states. This document will explore four approaches evaluated and their performance in ensuring a safe return of the Orion capsule in the event of onboard system degradation.

COMPUTATIONAL FLUID DYNAMICS MODELING OF SCALED HANFORD DOUBLE SHELL TANK MIXING - CFD MODELING SENSITIVITY STUDY RESULTS

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

JACKSON VL

2011-08-31

The primary purpose of the tank mixing and sampling demonstration program is to mitigate the technical risks associated with the ability of the Hanford tank farm delivery and celtification systems to measure and deliver a uniformly mixed high-level waste (HLW) feed to the Waste Treatment and Immobilization Plant (WTP) Uniform feed to the WTP is a requirement of 24590-WTP-ICD-MG-01-019, ICD-19 - Interface Control Document for Waste Feed, although the exact definition of uniform is evolving in this context. Computational Fluid Dynamics (CFD) modeling has been used to assist in evaluating scaleup issues, study operational parameters, and predict mixing performance atmore » full-scale.« less

Systematically evaluating interfaces for RNA-seq analysis from a life scientist perspective.

PubMed

Poplawski, Alicia; Marini, Federico; Hess, Moritz; Zeller, Tanja; Mazur, Johanna; Binder, Harald

2016-03-01

RNA-sequencing (RNA-seq) has become an established way for measuring gene expression in model organisms and humans. While methods development for refining the corresponding data processing and analysis pipeline is ongoing, protocols for typical steps have been proposed and are widely used. Several user interfaces have been developed for making such analysis steps accessible to life scientists without extensive knowledge of command line tools. We performed a systematic search and evaluation of such interfaces to investigate to what extent these can indeed facilitate RNA-seq data analysis. We found a total of 29 open source interfaces, and six of the more widely used interfaces were evaluated in detail. Central criteria for evaluation were ease of configuration, documentation, usability, computational demand and reporting. No interface scored best in all of these criteria, indicating that the final choice will depend on the specific perspective of users and the corresponding weighting of criteria. Considerable technical hurdles had to be overcome in our evaluation. For many users, this will diminish potential benefits compared with command line tools, leaving room for future improvement of interfaces. © The Author 2015. Published by Oxford University Press. For Permissions, please email: journals.permissions@oup.com.

ARC SDK: A toolbox for distributed computing and data applications

NASA Astrophysics Data System (ADS)

Skou Andersen, M.; Cameron, D.; Lindemann, J.

2014-06-01

Grid middleware suites provide tools to perform the basic tasks of job submission and retrieval and data access, however these tools tend to be low-level, operating on individual jobs or files and lacking in higher-level concepts. User communities therefore generally develop their own application-layer software catering to their specific communities' needs on top of the Grid middleware. It is thus important for the Grid middleware to provide a friendly, well documented and simple to use interface for the applications to build upon. The Advanced Resource Connector (ARC), developed by NorduGrid, provides a Software Development Kit (SDK) which enables applications to use the middleware for job and data management. This paper presents the architecture and functionality of the ARC SDK along with an example graphical application developed with the SDK. The SDK consists of a set of libraries accessible through Application Programming Interfaces (API) in several languages. It contains extensive documentation and example code and is available on multiple platforms. The libraries provide generic interfaces and rely on plugins to support a given technology or protocol and this modular design makes it easy to add a new plugin if the application requires supporting additional technologies.The ARC Graphical Clients package is a graphical user interface built on top of the ARC SDK and the Qt toolkit and it is presented here as a fully functional example of an application. It provides a graphical interface to enable job submission and management at the click of a button, and allows data on any Grid storage system to be manipulated using a visual file system hierarchy, as if it were a regular file system.

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.

A component-based, distributed object services architecture for a clinical workstation.

PubMed

Chueh, H C; Raila, W F; Pappas, J J; Ford, M; Zatsman, P; Tu, J; Barnett, G O

1996-01-01

Attention to an architectural framework in the development of clinical applications can promote reusability of both legacy systems as well as newly designed software. We describe one approach to an architecture for a clinical workstation application which is based on a critical middle tier of distributed object-oriented services. This tier of network-based services provides flexibility in the creation of both the user interface and the database tiers. We developed a clinical workstation for ambulatory care using this architecture, defining a number of core services including those for vocabulary, patient index, documents, charting, security, and encounter management. These services can be implemented through proprietary or more standard distributed object interfaces such as CORBA and OLE. Services are accessed over the network by a collection of user interface components which can be mixed and matched to form a variety of interface styles. These services have also been reused with several applications based on World Wide Web browser interfaces.

A component-based, distributed object services architecture for a clinical workstation.

PubMed Central

Chueh, H. C.; Raila, W. F.; Pappas, J. J.; Ford, M.; Zatsman, P.; Tu, J.; Barnett, G. O.

1996-01-01

Attention to an architectural framework in the development of clinical applications can promote reusability of both legacy systems as well as newly designed software. We describe one approach to an architecture for a clinical workstation application which is based on a critical middle tier of distributed object-oriented services. This tier of network-based services provides flexibility in the creation of both the user interface and the database tiers. We developed a clinical workstation for ambulatory care using this architecture, defining a number of core services including those for vocabulary, patient index, documents, charting, security, and encounter management. These services can be implemented through proprietary or more standard distributed object interfaces such as CORBA and OLE. Services are accessed over the network by a collection of user interface components which can be mixed and matched to form a variety of interface styles. These services have also been reused with several applications based on World Wide Web browser interfaces. PMID:8947744

Ground Software Maintenance Facility (GSMF) user's manual

NASA Technical Reports Server (NTRS)

Aquila, V.; Derrig, D.; Griffith, G.

1986-01-01

Instructions for the Ground Software Maintenance Facility (GSMF) system user is provided to operate the GSMF in all modes. The GSMF provides the resources for the Automatic Test Equipment (ATE) computer program maintenance (GCOS and GOAL). Applicable reference documents are listed. An operational overview and descriptions of the modes in terms of operator interface, options, equipment, material utilization, and operational procedures are contained. Test restart procedures are described. The GSMF documentation tree is presented including the user manual.

FIM Avionics Operations Manual

NASA Technical Reports Server (NTRS)

Alves, Erin E.

2017-01-01

This document describes the operation and use of the Flight Interval Management (FIM) Application installed on an electronic flight bag (EFB). Specifically, this document includes: 1) screen layouts for each page of the interface; 2) step-by-step instructions for data entry, data verification, and input error correction; 3) algorithm state messages and error condition alerting messages; 4) aircraft speed guidance and deviation indications; and 5) graphical display of the spatial relationships between the Ownship aircraft and the Target aircraft.

Space Communication Artificial Intelligence for Link Evaluation Terminal (SCAILET)

NASA Technical Reports Server (NTRS)

Shahidi, Anoosh K.; Schlegelmilch, Richard F.; Petrik, Edward J.; Walters, Jerry L.

1992-01-01

A software application to assist end-users of the high burst rate (HBR) link evaluation terminal (LET) for satellite communications is being developed. The HBR LET system developed at NASA Lewis Research Center is an element of the Advanced Communications Technology Satellite (ACTS) Project. The HBR LET is divided into seven major subsystems, each with its own expert. Programming scripts, test procedures defined by design engineers, set up the HBR LET system. These programming scripts are cryptic, hard to maintain and require a steep learning curve. These scripts were developed by the system engineers who will not be available for the end-users of the system. To increase end-user productivity a friendly interface needs to be added to the system. One possible solution is to provide the user with adequate documentation to perform the needed tasks. With the complexity of this system the vast amount of documentation needed would be overwhelming and the information would be hard to retrieve. With limited resources, maintenance is another reason for not using this form of documentation. An advanced form of interaction is being explored using current computer techniques. This application, which incorporates a combination of multimedia and artificial intelligence (AI) techniques to provided end-users with an intelligent interface to the HBR LET system, is comprised of an intelligent assistant, intelligent tutoring, and hypermedia documentation. The intelligent assistant and tutoring systems address the critical programming needs of the end-user.

Section 4. The GIS Weasel User's Manual

USGS Publications Warehouse

Viger, Roland J.; Leavesley, George H.

2007-01-01

INTRODUCTION The GIS Weasel was designed to aid in the preparation of spatial information for input to lumped and distributed parameter hydrologic or other environmental models. The GIS Weasel provides geographic information system (GIS) tools to help create maps of geographic features relevant to a user's model and to generate parameters from those maps. The operation of the GIS Weasel does not require the user to be a GIS expert, only that the user have an understanding of the spatial information requirements of the environmental simulation model being used. The GIS Weasel software system uses a GIS-based graphical user interface (GUI), the C programming language, and external scripting languages. The software will run on any computing platform where ArcInfo Workstation (version 8.0.2 or later) and the GRID extension are accessible. The user controls the processing of the GIS Weasel by interacting with menus, maps, and tables. The purpose of this document is to describe the operation of the software. This document is not intended to describe the usage of this software in support of any particular environmental simulation model. Such guides are published separately.

PanMetaDocs - A tool for collecting and managing the long tail of "small science data"

NASA Astrophysics Data System (ADS)

Klump, J.; Ulbricht, D.

2011-12-01

In the early days of thinking about cyberinfrastructure the focus was on "big science data". Today, the challenge is not anymore to store several terabytes of data, but to manage data objects in a way that facilitates their re-use. Key to re-use by a user as a data consumer is proper documentation of the data. Also, data consumers need discovery metadata to find the data they need and they need descriptive metadata to be able to use the data they retrieved. Thus, data documentation faces the challenge to extensively and completely describe these objects, hold the items easily accessible at a sustainable cost level. However, data curation and documentation do not rank high in the everyday work of a scientist as a data producer. Data producers are often frustrated by being asked to provide metadata on their data over and over again, information that seemed very obvious from the context of their work. A challenge to data archives is the wide variety of metadata schemata in use, which creates a number of maintenance and design challenges of its own. PanMetaDocs addresses these issues by allowing an uploaded files to be described by more than one metadata object. PanMetaDocs, which was developed from PanMetaWorks, is a PHP based web application that allow to describe data with any xml-based metadata schema. Its user interface is browser based and was developed to collect metadata and data in collaborative scientific projects situated at one or more institutions. The metadata fields can be filled with static or dynamic content to reduce the number of fields that require manual entries to a minimum and make use of contextual information in a project setting. In the development of PanMetaDocs the business logic of panMetaWorks is reused, except for the authentication and data management functions of PanMetaWorks, which are delegated to the eSciDoc framework. The eSciDoc repository framework is designed as a service oriented architecture that can be controlled through a REST interface to create version controlled items with metadata records in XML format. PanMetaDocs utilizes the eSciDoc items model to add multiple metadata records that describe uploaded files in different metadata schemata. While datasets are collected and described, shared to collaborate with other scientists and finally published, data objects are transferred from a shared data curation domain into a persistent data curation domain. Through an RSS interface for recent datasets PanMetaWorks allows project members to be informed about data uploaded by other project members. The implementation of the OAI-PMH interface can be used to syndicate data catalogs to research data portals, such as the panFMP data portal framework. Once data objects are uploaded to the eSciDoc infrastructure it is possible to drop the software instance that was used for collecting the data, while the compiled data and metadata are accessible for other authorized applications through the institution's eSciDoc middleware. This approach of "expendable data curation tools" allows for a significant reduction in costs for software maintenance as expensive data capture applications do not need to be maintained indefinitely to ensure long term access to the stored data.

Interactions Between Ocean Circulation and Topography in Icy Worlds

NASA Astrophysics Data System (ADS)

Goodman, J. C.

2018-05-01

To what extent does topography at the water-rock interface control the general circulation patterns of icy world oceans? And contrariwise, to what extent does liquid flow control the topography at the ice-water interface (or interfaces)?

Ocular attention-sensing interface system

NASA Technical Reports Server (NTRS)

Zaklad, Allen; Glenn, Floyd A., III; Iavecchia, Helene P.; Stokes, James M.

1986-01-01

The purpose of the research was to develop an innovative human-computer interface based on eye movement and voice control. By eliminating a manual interface (keyboard, joystick, etc.), OASIS provides a control mechanism that is natural, efficient, accurate, and low in workload.

In-vehicle crash avoidance warning systems : human factors considerations

DOT National Transportation Integrated Search

1997-02-01

This document represents the final report of the work performed under contract DTNH22-91 C-07004, In-Vehicle Crash Avoidance Warning Systems: Human Factors Considerations. This project was performed to develop guidelines for the interface desig...

Discovering DISCOVER

DTIC Science & Technology

1997-10-01

used to establish associations between source code and Adobe FrameMaker documents. The associations are represented as links that facilitate...possible (such as that provided with FrameMaker ). There is no scripting interface that would enable end-user programming of its modules. The suite of

Electronic flight bag (EFB) : 2007 industry review

DOT National Transportation Integrated Search

2007-04-01

This document, which is based on information from March 2007, proivdes an overview of Electronic Flight Bag (EFB) systems and capabilities, with particular focus on the systems' human interface. It updates the April 2005 EFB Industry Review (Yeh and ...

Panorama: A Targeted Proteomics Knowledge Base

PubMed Central

2015-01-01

Panorama is a web application for storing, sharing, analyzing, and reusing targeted assays created and refined with Skyline,1 an increasingly popular Windows client software tool for targeted proteomics experiments. Panorama allows laboratories to store and organize curated results contained in Skyline documents with fine-grained permissions, which facilitates distributed collaboration and secure sharing of published and unpublished data via a web-browser interface. It is fully integrated with the Skyline workflow and supports publishing a document directly to a Panorama server from the Skyline user interface. Panorama captures the complete Skyline document information content in a relational database schema. Curated results published to Panorama can be aggregated and exported as chromatogram libraries. These libraries can be used in Skyline to pick optimal targets in new experiments and to validate peak identification of target peptides. Panorama is open-source and freely available. It is distributed as part of LabKey Server,2 an open source biomedical research data management system. Laboratories and organizations can set up Panorama locally by downloading and installing the software on their own servers. They can also request freely hosted projects on https://panoramaweb.org, a Panorama server maintained by the Department of Genome Sciences at the University of Washington. PMID:25102069

Mass and charge transport in IPMC actuators with fractal interfaces

NASA Astrophysics Data System (ADS)

Chang, Longfei; Wu, Yucheng; Zhu, Zicai; Li, Heng

2016-04-01

Ionic Polymer-Metal Composite (IPMC) actuators have been attracting a growing interest in extensive applications, which consequently raises the demands on the accuracy of its theoretical modeling. For the last few years, rough landscape of the interface between the electrode and the ionic membrane of IPMC has been well-documented as one of the key elements to ensure a satisfied performance. However, in most of the available work, the interface morphology of IPMC was simplified with structural idealization, which lead to perplexity in the physical interpretation on its interface mechanism. In this paper, the quasi-random rough interface of IPMC was described with fractal dimension and scaling parameters. And the electro-chemical field was modeled by Poisson equation and a properly simplified Nernst-Planck equation set. Then, by simulation with Finite Element Method, a comprehensive analysis on he inner mass and charge transportation in IPMC actuators with different fractal interfaces was provided, which may be further adopted to instruct the performance-oriented interface design for ionic electro-active actuators. The results also verified that rough interface can impact the electrical and mechanical response of IPMC, not only from the respect of the real surface increase, but also from mass distribution difference caused by the complexity of the micro profile.

Gesture-Controlled Interfaces for Self-Service Machines

NASA Technical Reports Server (NTRS)

Cohen, Charles J.; Beach, Glenn

2006-01-01

Gesture-controlled interfaces are software- driven systems that facilitate device control by translating visual hand and body signals into commands. Such interfaces could be especially attractive for controlling self-service machines (SSMs) for example, public information kiosks, ticket dispensers, gasoline pumps, and automated teller machines (see figure). A gesture-controlled interface would include a vision subsystem comprising one or more charge-coupled-device video cameras (at least two would be needed to acquire three-dimensional images of gestures). The output of the vision system would be processed by a pure software gesture-recognition subsystem. Then a translator subsystem would convert a sequence of recognized gestures into commands for the SSM to be controlled; these could include, for example, a command to display requested information, change control settings, or actuate a ticket- or cash-dispensing mechanism. Depending on the design and operational requirements of the SSM to be controlled, the gesture-controlled interface could be designed to respond to specific static gestures, dynamic gestures, or both. Static and dynamic gestures can include stationary or moving hand signals, arm poses or motions, and/or whole-body postures or motions. Static gestures would be recognized on the basis of their shapes; dynamic gestures would be recognized on the basis of both their shapes and their motions. Because dynamic gestures include temporal as well as spatial content, this gesture- controlled interface can extract more information from dynamic than it can from static gestures.

A Collection of Nonlinear Aircraft Simulations in MATLAB

NASA Technical Reports Server (NTRS)

Garza, Frederico R.; Morelli, Eugene A.

2003-01-01

Nonlinear six degree-of-freedom simulations for a variety of aircraft were created using MATLAB. Data for aircraft geometry, aerodynamic characteristics, mass / inertia properties, and engine characteristics were obtained from open literature publications documenting wind tunnel experiments and flight tests. Each nonlinear simulation was implemented within a common framework in MATLAB, and includes an interface with another commercially-available program to read pilot inputs and produce a three-dimensional (3-D) display of the simulated airplane motion. Aircraft simulations include the General Dynamics F-16 Fighting Falcon, Convair F-106B Delta Dart, Grumman F-14 Tomcat, McDonnell Douglas F-4 Phantom, NASA Langley Free-Flying Aircraft for Sub-scale Experimental Research (FASER), NASA HL-20 Lifting Body, NASA / DARPA X-31 Enhanced Fighter Maneuverability Demonstrator, and the Vought A-7 Corsair II. All nonlinear simulations and 3-D displays run in real time in response to pilot inputs, using contemporary desktop personal computer hardware. The simulations can also be run in batch mode. Each nonlinear simulation includes the full nonlinear dynamics of the bare airframe, with a scaled direct connection from pilot inputs to control surface deflections to provide adequate pilot control. Since all the nonlinear simulations are implemented entirely in MATLAB, user-defined control laws can be added in a straightforward fashion, and the simulations are portable across various computing platforms. Routines for trim, linearization, and numerical integration are included. The general nonlinear simulation framework and the specifics for each particular aircraft are documented.

AXAF user interfaces for heterogeneous analysis environments

NASA Technical Reports Server (NTRS)

Mandel, Eric; Roll, John; Ackerman, Mark S.

1992-01-01

The AXAF Science Center (ASC) will develop software to support all facets of data center activities and user research for the AXAF X-ray Observatory, scheduled for launch in 1999. The goal is to provide astronomers with the ability to utilize heterogeneous data analysis packages, that is, to allow astronomers to pick the best packages for doing their scientific analysis. For example, ASC software will be based on IRAF, but non-IRAF programs will be incorporated into the data system where appropriate. Additionally, it is desired to allow AXAF users to mix ASC software with their own local software. The need to support heterogeneous analysis environments is not special to the AXAF project, and therefore finding mechanisms for coordinating heterogeneous programs is an important problem for astronomical software today. The approach to solving this problem has been to develop two interfaces that allow the scientific user to run heterogeneous programs together. The first is an IRAF-compatible parameter interface that provides non-IRAF programs with IRAF's parameter handling capabilities. Included in the interface is an application programming interface to manipulate parameters from within programs, and also a set of host programs to manipulate parameters at the command line or from within scripts. The parameter interface has been implemented to support parameter storage formats other than IRAF parameter files, allowing one, for example, to access parameters that are stored in data bases. An X Windows graphical user interface called 'agcl' has been developed, layered on top of the IRAF-compatible parameter interface, that provides a standard graphical mechanism for interacting with IRAF and non-IRAF programs. Users can edit parameters and run programs for both non-IRAF programs and IRAF tasks. The agcl interface allows one to communicate with any command line environment in a transparent manner and without any changes to the original environment. For example, the authors routinely layer the GUI on top of IRAF, ksh, SMongo, and IDL. The agcl, based on the facilities of a system called Answer Garden, also has sophisticated support for examining documentation and help files, asking questions of experts, and developing a knowledge base of frequently required information. Thus, the GUI becomes a total environment for running programs, accessing information, examining documents, and finding human assistance. Because the agcl can communicate with any command-line environment, most projects can make use of it easily. New applications are continually being found for these interfaces. It is the authors' intention to evolve the GUI and its underlying parameter interface in response to these needs - from users as well as developers - throughout the astronomy community. This presentation describes the capabilities and technology of the above user interface mechanisms and tools. It also discusses the design philosophies guiding the work, as well as hopes for the future.

Interface control of bulk ferroelectric polarization

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

Yu, P; Luo, Weidong; Yi, D.

2012-01-01

The control of material interfaces at the atomic level has led to no- vel interfacial properties and functionalities. In particular, the study of polar discontinuities at interfaces between complex oxides lies at the frontier of modern condensed matter research. Here we em- ploy a combination of experimental measurements and theoretical calculations to demonstrate the control of a bulk property, namely ferroelectric polarization, of a heteroepitaxial bilayer by precise atomic-scale interface engineering. More specifically, the control is achieved by exploiting the interfacial valence mismatch to influence the electrostatic potential step across the interface, which manifests itself as the biased-voltage in ferroelectricmore » hysteresis loops and determines the ferroelectric state. A broad study of diverse systems comprising different ferroelectrics and conducting perovskite un- derlayers extends the generality of this phenomenon.« less

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.

Open ISEmeter: An open hardware high-impedance interface for potentiometric detection.

PubMed

Salvador, C; Mesa, M S; Durán, E; Alvarez, J L; Carbajo, J; Mozo, J D

2016-05-01

In this work, a new open hardware interface based on Arduino to read electromotive force (emf) from potentiometric detectors is presented. The interface has been fully designed with the open code philosophy and all documentation will be accessible on web. The paper describes a comprehensive project including the electronic design, the firmware loaded on Arduino, and the Java-coded graphical user interface to load data in a computer (PC or Mac) for processing. The prototype was tested by measuring the calibration curve of a detector. As detection element, an active poly(vinyl chloride)-based membrane was used, doped with cetyltrimethylammonium dodecylsulphate (CTA(+)-DS(-)). The experimental measures of emf indicate Nernstian behaviour with the CTA(+) content of test solutions, as it was described in the literature, proving the validity of the developed prototype. A comparative analysis of performance was made by using the same chemical detector but changing the measurement instrumentation.

Assisted navigation based on shared-control, using discrete and sparse human-machine interfaces.

PubMed

Lopes, Ana C; Nunes, Urbano; Vaz, Luis; Vaz, Luís

2010-01-01

This paper presents a shared-control approach for Assistive Mobile Robots (AMR), which depends on the user's ability to navigate a semi-autonomous powered wheelchair, using a sparse and discrete human-machine interface (HMI). This system is primarily intended to help users with severe motor disabilities that prevent them to use standard human-machine interfaces. Scanning interfaces and Brain Computer Interfaces (BCI), characterized to provide a small set of commands issued sparsely, are possible HMIs. This shared-control approach is intended to be applied in an Assisted Navigation Training Framework (ANTF) that is used to train users' ability in steering a powered wheelchair in an appropriate manner, given the restrictions imposed by their limited motor capabilities. A shared-controller based on user characterization, is proposed. This controller is able to share the information provided by the local motion planning level with the commands issued sparsely by the user. Simulation results of the proposed shared-control method, are presented.

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

"I'm Keeping Those There, Are You?": The Role of a New User Interface Paradigm--Separate Control of Shared Space (SCOSS)--in the Collaborative Decision-Making Process

ERIC Educational Resources Information Center

Kerawalla, Lucinda; Pearce, Darren; Yuill, Nicola; Luckin, Rosemary; Harris, Amanda

2008-01-01

We take a socio-cultural approach to comparing how dual control of a new user interface paradigm--Separate Control of Shared Space (SCOSS)--and dual control of a single user interface can work to mediate the collaborative decision-making process between pairs of children carrying out a multiple categorisation word task on a shared computer.…

75 FR 8928 - Announcement of IS-GPS-200, IS-GPS-705, IS-GPS-800 Interface Control Working Group (ICWG...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-02-26

... DEPARTMENT OF DEFENSE Department of the Air Force Announcement of IS-GPS-200, IS-GPS-705, IS-GPS-800Interface Control Working Group (ICWG) Teleconference Meeting AGENCY: Department of the Air Force, DoD... Positioning Systems Wing will be hosting an Interface Control Working Group (ICWG) teleconference meeting for...

Transfer of control system interface solutions from other domains to the thermal power industry.

PubMed

Bligård, L-O; Andersson, J; Osvalder, A-L

2012-01-01

In a thermal power plant the operators' roles are to control and monitor the process to achieve efficient and safe production. To achieve this, the human-machine interfaces have a central part. The interfaces need to be updated and upgraded together with the technical functionality to maintain optimal operation. One way of achieving relevant updates is to study other domains and see how they have solved similar issues in their design solutions. The purpose of this paper is to present how interface design solution ideas can be transferred from domains with operator control to thermal power plants. In the study 15 domains were compared using a model for categorisation of human-machine systems. The result from the domain comparison showed that nuclear power, refinery and ship engine control were most similar to thermal power control. From the findings a basic interface structure and three specific display solutions were proposed for thermal power control: process parameter overview, plant overview, and feed water view. The systematic comparison of the properties of a human-machine system allowed interface designers to find suitable objects, structures and navigation logics in a range of domains that could be transferred to the thermal power domain.

Suggestions for Layout and Functional Behavior of Software-Based Voice Switch Keysets

NASA Technical Reports Server (NTRS)

Scott, David W.

2010-01-01

Marshall Space Flight Center (MSFC) provides communication services for a number of real time environments, including Space Shuttle Propulsion support and International Space Station (ISS) payload operations. In such settings, control team members speak with each other via multiple voice circuits or loops. Each loop has a particular purpose and constituency, and users are assigned listen and/or talk capabilities for a given loop based on their role in fulfilling the purpose. A voice switch is a given facility's hardware and software that supports such communication, and may be interconnected with other facilities switches to create a large network that, from an end user perspective, acts like a single system. Since users typically monitor and/or respond to several voice loops concurrently for hours on end and real time operations can be very dynamic and intense, it s vital that a control panel or keyset for interfacing with the voice switch be a servant that reduces stress, not a master that adds it. Implementing the visual interface on a computer screen provides tremendous flexibility and configurability, but there s a very real risk of overcomplication. (Remember how office automation made life easier, which led to a deluge of documents that made life harder?) This paper a) discusses some basic human factors considerations related to keysets implemented as application software windows, b) suggests what to standardize at the facility level and what to leave to the user's preference, and c) provides screen shot mockups for a robust but reasonably simple user experience. Concepts apply to keyset needs in almost any type of operations control or support center.

Programs for transferring data between a relational data base and a finite element structural analysis program

NASA Technical Reports Server (NTRS)

Johnson, S. C.

1982-01-01

An interface system for passing data between a relational information management (RIM) data base complex and engineering analysis language (EAL), a finite element structural analysis program is documented. The interface system, implemented on a CDC Cyber computer, is composed of two FORTRAN programs called RIM2EAL and EAL2RIM. The RIM2EAL reads model definition data from RIM and creates a file of EAL commands to define the model. The EAL2RIM reads model definition and EAL generated analysis data from EAL's data library and stores these data dirctly in a RIM data base. These two interface programs and the format for the RIM data complex are described.

Heuristic evaluation of eNote: an electronic notes system.

PubMed

Bright, Tiffani J; Bakken, Suzanne; Johnson, Stephen B

2006-01-01

eNote is an electronic health record (EHR) system based on semi-structured narrative documents. A heuristic evaluation was conducted with a sample of five usability experts. eNote performed highly in: 1)consistency with standards and 2)recognition rather than recall. eNote needs improvement in: 1)help and documentation, 2)aesthetic and minimalist design, 3)error prevention, 4)helping users recognize, diagnosis, and recover from errors, and 5)flexibility and efficiency of use. The heuristic evaluation was an efficient method of evaluating our interface.

Space Launch System (SLS) Mission Planner's Guide

NASA Technical Reports Server (NTRS)

Smith, David Alan

2017-01-01

The purpose of this Space Launch System (SLS) Mission Planner's Guide (MPG) is to provide future payload developers/users with sufficient insight to support preliminary SLS mission planning. Consequently, this SLS MPG is not intended to be a payload requirements document; rather, it organizes and details SLS interfaces/accommodations in a manner similar to that of current Expendable Launch Vehicle (ELV) user guides to support early feasibility assessment. Like ELV Programs, once approved to fly on SLS, specific payload requirements will be defined in unique documentation.