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
Advanced EVA system design requirements study: EVAS/space station system interface requirements
NASA Technical Reports Server (NTRS)
Woods, T. G.
1985-01-01
The definition of the Extravehicular Activity (EVA) systems interface requirements and accomodations for effective integration of a production EVA capability into the space station are contained. A description of the EVA systems for which the space station must provide the various interfaces and accomodations are provided. The discussion and analyses of the various space station areas in which the EVA interfaces are required and/or from which implications for EVA system design requirements are derived, are included. The rationale is provided for all EVAS mechanical, fluid, electrical, communications, and data system interfaces as well as exterior and interior requirements necessary to facilitate EVA operations. Results of the studies supporting these discussions are presented in the appendix.
Ground Systems Development Environment (GSDE) interface requirements analysis: Operations scenarios
NASA Technical Reports Server (NTRS)
Church, Victor E.; Phillips, John
1991-01-01
This report is a preliminary assessment of the functional and data interface requirements to the link between the GSDE GS/SPF (Amdahl) and the Space Station Control Center (SSCC) and Space Station Training Facility (SSTF) Integration, Verification, and Test Environments (IVTE's). These interfaces will be involved in ground software development of both the control center and the simulation and training systems. Our understanding of the configuration management (CM) interface and the expected functional characteristics of the Amdahl-IVTE interface is described. A set of assumptions and questions that need to be considered and resolved in order to complete the interface functional and data requirements definitions are presented. A listing of information items defined to describe software configuration items in the GSDE CM system is included. It also includes listings of standard reports of CM information and of CM-related tools in the GSDE.
Atmosphere explorer missions C, D, and E. Spacecraft experiment interface definition study
NASA Technical Reports Server (NTRS)
1972-01-01
The Atmosphere Explorer Missions C, D, & E Spacecraft/Experiment Interface Definition Study is discussed. The objectives of the study included an analysis of the accommodation requirements of the experiments for the three missions, an assessment of the overall effect of these requirements on the spacecraft system design and performance, and the detailed definition of all experiment/spacecraft electrical, mechanical, and environmental interfaces. In addition, the study included the identification and definition of system characteristics required to ensure compatibility with the consolidated STADAN and MSFN communications networks.
ECLSS evolution: Advanced instrumentation interface requirements. Volume 3: Appendix C
NASA Technical Reports Server (NTRS)
1991-01-01
An Advanced ECLSS (Environmental Control and Life Support System) Technology Interfaces Database was developed primarily to provide ECLSS analysts with a centralized and portable source of ECLSS technologies interface requirements data. The database contains 20 technologies which were previously identified in the MDSSC ECLSS Technologies database. The primary interfaces of interest in this database are fluid, electrical, data/control interfaces, and resupply requirements. Each record contains fields describing the function and operation of the technology. Fields include: an interface diagram, description applicable design points and operating ranges, and an explaination of data, as required. A complete set of data was entered for six of the twenty components including Solid Amine Water Desorbed (SAWD), Thermoelectric Integrated Membrane Evaporation System (TIMES), Electrochemical Carbon Dioxide Concentrator (EDC), Solid Polymer Electrolysis (SPE), Static Feed Electrolysis (SFE), and BOSCH. Additional data was collected for Reverse Osmosis Water Reclaimation-Potable (ROWRP), Reverse Osmosis Water Reclaimation-Hygiene (ROWRH), Static Feed Solid Polymer Electrolyte (SFSPE), Trace Contaminant Control System (TCCS), and Multifiltration Water Reclamation - Hygiene (MFWRH). A summary of the database contents is presented in this report.
Advanced aerosense display interfaces
NASA Astrophysics Data System (ADS)
Hopper, Darrel G.; Meyer, Frederick M.
1998-09-01
High-resolution display technologies are being developed to meet the ever-increasing demand for realistic detail. The requirement for evermore visual information exceeds the capacity of fielded aerospace display interfaces. In this paper we begin an exploration of display interfaces and evolving aerospace requirements. Current and evolving standards for avionics, commercial, and flat panel displays are summarized and compared to near term goals for military and aerospace applications. Aerospace and military applications prior to 2005 up to UXGA and digital HDTV resolution can be met by using commercial interface standard developments. Advanced aerospace requirements require yet higher resolutions (2560 X 2048 color pixels, 5120 X 4096 color pixels at 85 Hz, etc.) and necessitate the initiation of discussion herein of an 'ultra digital interface standard (UDIS)' which includes 'smart interface' features such as large memory and blazingly fast resizing microcomputer. Interface capacity, IT, increased about 105 from 1973 to 1998; 102 more is needed for UDIS.
Flexible Architecture for FPGAs in Embedded Systems
NASA Technical Reports Server (NTRS)
Clark, Duane I.; Lim, Chester N.
2012-01-01
Commonly, field-programmable gate arrays (FPGAs) being developed in cPCI embedded systems include the bus interface in the FPGA. This complicates the development because the interface is complicated and requires a lot of development time and FPGA resources. In addition, flight qualification requires a substantial amount of time be devoted to just this interface. Another complication of putting the cPCI interface into the FPGA being developed is that configuration information loaded into the device by the cPCI microprocessor is lost when a new bit file is loaded, requiring cumbersome operations to return the system to an operational state. Finally, SRAM-based FPGAs are typically programmed via specialized cables and software, with programming files being loaded either directly into the FPGA, or into PROM devices. This can be cumbersome when doing FPGA development in an embedded environment, and does not have an easy path to flight. Currently, FPGAs used in space applications are usually programmed via multiple space-qualified PROM devices that are physically large and require extra circuitry (typically including a separate one-time programmable FPGA) to enable them to be used for this application. This technology adds a cPCI interface device with a simple, flexible, high-performance backend interface supporting multiple backend FPGAs. It includes a mechanism for programming the FPGAs directly via the microprocessor in the embedded system, eliminating specialized hardware, software, and PROM devices and their associated circuitry. It has a direct path to flight, and no extra hardware and minimal software are required to support reprogramming in flight. The device added is currently a small FPGA, but an advantage of this technology is that the design of the device does not change, regardless of the application in which it is being used. This means that it needs to be qualified for flight only once, and is suitable for one-time programmable devices or an application specific integrated circuit (ASIC). An application programming interface (API) further reduces the development time needed to use the interface device in a system.
Orbiter CIU/IUS communications hardware evaluation
NASA Technical Reports Server (NTRS)
Huth, G. K.
1979-01-01
The DOD and NASA inertial upper stage communication system design, hardware specifications and interfaces were analyzed to determine their compatibility with the Orbiter payload communications equipment (Payload Interrogator, Payload Signal Processors, Communications Interface Unit, and the Orbiter operational communications equipment (the S-Band and Ku-band systems). Topics covered include (1) IUS/shuttle Orbiter communications interface definition; (2) Orbiter avionics equipment serving the IUS; (3) IUS communication equipment; (4) IUS/shuttle Orbiter RF links; (5) STDN/TDRS S-band related activities; and (6) communication interface unit/Orbiter interface issues. A test requirement plan overview is included.
Inertial Upper Stage (IUS) software analysis
NASA Technical Reports Server (NTRS)
Grayson, W. L.; Nickel, C. E.; Rose, P. L.; Singh, R. P.
1979-01-01
The Inertial Upper Stage (IUS) System, an extension of the Space Transportation System (STS) operating regime to include higher orbits, orbital plane changes, geosynchronous orbits, and interplanetary trajectories is presented. The IUS software design, the IUS software interfaces with other systems, and the cost effectiveness in software verification are described. Tasks of the IUS discussed include: (1) design analysis; (2) validation requirements analysis; (3) interface analysis; and (4) requirements analysis.
TRU waste lead organization -- WIPP Project Office Interface Management semi-annual report
DOE Office of Scientific and Technical Information (OSTI.GOV)
Guerrero, J.V.; Gorton, J.M.
1985-05-01
The Charter establishing the Interface Control Board and the administrative organization to manage the interface of the TRU Waste Lead Organization and the WIPP Project Office also requires preparation of a summary report describing significant interface activities.'' This report includes a discussion of Interface Working Group (IWG) recommendations and resolutions considered and implemented'' over the reporting period October 1984 to March 1985.
Interface Shape Control Using Localized Heating during Bridgman Growth
NASA Technical Reports Server (NTRS)
Volz, M. P.; Mazuruk, K.; Aggarwal, M. D.; Croll, A.
2008-01-01
Numerical calculations were performed to assess the effect of localized radial heating on the melt-crystal interface shape during vertical Bridgman growth. System parameters examined include the ampoule, melt and crystal thermal conductivities, the magnitude and width of localized heating, and the latent heat of crystallization. Concave interface shapes, typical of semiconductor systems, could be flattened or made convex with localized heating. Although localized heating caused shallower thermal gradients ahead of the interface, the magnitude of the localized heating required for convexity was less than that which resulted in a thermal inversion ahead of the interface. A convex interface shape was most readily achieved with ampoules of lower thermal conductivity. Increasing melt convection tended to flatten the interface, but the amount of radial heating required to achieve a convex interface was essentially independent of the convection intensity.
NASA Technical Reports Server (NTRS)
1993-01-01
The purpose is to describe at a high level the common interface provisions and constraints placed on the NOAA-2000 instruments and the interfacing spacecraft elements in the following areas: electrical interface, mechanical interface, thermal interface, magnetic interface, electromagnetic compatibility, structural/mechanical environmental interface, contamination control, and the ionizing radiation environment. The requirements reflect the fact that these instruments must be compatible with a number of different polar orbiting satellite vehicles including the NOAA-OPQ satellites and the EUMETSAT METOP satellites.
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.
Space Generic Open Avionics Architecture (SGOAA) standard specification
NASA Technical Reports Server (NTRS)
Wray, Richard B.; Stovall, John R.
1994-01-01
This standard establishes the Space Generic Open Avionics Architecture (SGOAA). The SGOAA includes a generic functional model, processing structural model, and an architecture interface model. This standard defines the requirements for applying these models to the development of spacecraft core avionics systems. The purpose of this standard is to provide an umbrella set of requirements for applying the generic architecture models to the design of a specific avionics hardware/software processing system. This standard defines a generic set of system interface points to facilitate identification of critical services and interfaces. It establishes the requirement for applying appropriate low level detailed implementation standards to those interfaces points. The generic core avionics functions and processing structural models provided herein are robustly tailorable to specific system applications and provide a platform upon which the interface model is to be applied.
Enhancing the Human Factors Engineering Role in an Austere Fiscal Environment
NASA Technical Reports Server (NTRS)
Stokes, Jack W.
2003-01-01
An austere fiscal environment in the aerospace community creates pressures to reduce program costs, often minimizing or sometimes even deleting the human interface requirements from the design process. With an assumption that the flight crew can recover real time from a poorly human factored space vehicle design, the classical crew interface requirements have been either not included in the design or not properly funded, though carried as requirements. Cost cuts have also affected quality of retained human factors engineering personnel. In response to this concern, planning is ongoing to correct the acting issues. Herein are techniques for ensuring that human interface requirements are integrated into a flight design, from proposal through verification and launch activation. This includes human factors requirements refinement and consolidation across flight programs; keyword phrases in the proposals; closer ties with systems engineering and other classical disciplines; early planning for crew-interface verification; and an Agency integrated human factors verification program, under the One NASA theme. Importance is given to communication within the aerospace human factors discipline, and utilizing the strengths of all government, industry, and academic human factors organizations in an unified research and engineering approach. A list of recommendations and concerns are provided in closing.
NASA Technical Reports Server (NTRS)
Fura, David A.; Windley, Phillip J.; Cohen, Gerald C.
1993-01-01
This technical report contains the Higher-Order Logic (HOL) listings of the partial verification of the requirements and design for a commercially developed processor interface unit (PIU). The PIU is an interface chip performing memory interface, bus interface, and additional support services for a commercial microprocessor within a fault tolerant computer system. This system, the Fault Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance-free operation, or both. This report contains the actual HOL listings of the PIU verification as it currently exists. Section two of this report contains general-purpose HOL theories and definitions that support the PIU verification. These include arithmetic theories dealing with inequalities and associativity, and a collection of tactics used in the PIU proofs. Section three contains the HOL listings for the completed PIU design verification. Section 4 contains the HOL listings for the partial requirements verification of the P-Port.
IUS/TUG orbital operations and mission support study. Volume 4: Project planning data
NASA Technical Reports Server (NTRS)
1975-01-01
Planning data are presented for the development phases of interim upper stage (IUS) and tug systems. Major project planning requirements, major event schedules, milestones, system development and operations process networks, and relevant support research and technology requirements are included. Topics discussed include: IUS flight software; tug flight software; IUS/tug ground control center facilities, personnel, data systems, software, and equipment; IUS mission events; tug mission events; tug/spacecraft rendezvous and docking; tug/orbiter operations interface, and IUS/orbiter operations interface.
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.
Shuttle vehicle and mission simulation requirements report, volume 1
NASA Technical Reports Server (NTRS)
Burke, J. F.
1972-01-01
The requirements for the space shuttle vehicle and mission simulation are developed to analyze the systems, mission, operations, and interfaces. The requirements are developed according to the following subject areas: (1) mission envelope, (2) orbit flight dynamics, (3) shuttle vehicle systems, (4) external interfaces, (5) crew procedures, (6) crew station, (7) visual cues, and (8) aural cues. Line drawings and diagrams of the space shuttle are included to explain the various systems and components.
IUS/TUG orbital operations and mission support study. Volume 3: Space tug operations
NASA Technical Reports Server (NTRS)
1975-01-01
A study was conducted to develop space tug operational concepts and baseline operations plan, and to provide cost estimates for space tug operations. Background data and study results are presented along with a transition phase analysis (the transition from interim upper state to tug operations). A summary is given of the tug operational and interface requirements with emphasis on the on-orbit checkout requirements, external interface operational requirements, safety requirements, and system operational interface requirements. Other topics discussed include reference missions baselined for the tug and details for the mission functional flows and timelines derived for the tug mission, tug subsystems, tug on-orbit operations prior to the tug first burn, spacecraft deployment and retrieval by the tug, operations centers, mission planning, potential problem areas, and cost data.
MIL-STD-1553 dynamic bus controller/remote terminal hybrid set
NASA Astrophysics Data System (ADS)
Friedman, S. N.
This paper describes the performance, physical and electrical requirements of a Dual Redundant BUS Interface Unit (BIU) acting as a BUS Controller Interface Unit (BCIU) or Remote Terminal Unit (RTU) between a Motorola 68000 VME BUS and MIL-STD-1553B Multiplex Data Bus. A discussion of how the BIU Hybrid set is programmed, and operates as a BCIU or RTU, will be included. This paper will review Dynamic Bus Control and other Mode Code capabilities. The BIU Hybrid Set interfaces to a 68000 Microprocessor with a VME Bus using programmed I/O transfers. This special interface will be discussed along with the internal Dual Access Memory (4K x 16) used to support the data exchanges between the CPU and the BIU Hybrid Set. The hybrid set's physical size and power requirements will be covered. This includes the present Double Eurocard the BIU function is presently being offered on.
NASA Technical Reports Server (NTRS)
1976-01-01
General physical, functional, and operational interface control requirements for instruments on the first AMPS payload are presented. Interface specifications are included to satisfy ground handling, prelaunch, launch, stowage, operation, and landing activities. Applicable supporting documentation to implement the information is also given.
Space shuttle on-orbit flight control software requirements, preliminary version
NASA Technical Reports Server (NTRS)
1975-01-01
Software modules associated with various flight control functions for the space shuttle orbiter are described. Data flow, interface requirements, initialization requirements and module sequencing requirements are considered. Block diagrams and tables are included.
Selectivity and Longevity of Peripheral-Nerve and Machine Interfaces: A Review
Ghafoor, Usman; Kim, Sohee; Hong, Keum-Shik
2017-01-01
For those individuals with upper-extremity amputation, a daily normal living activity is no longer possible or it requires additional effort and time. With the aim of restoring their sensory and motor functions, theoretical and technological investigations have been carried out in the field of neuroprosthetic systems. For transmission of sensory feedback, several interfacing modalities including indirect (non-invasive), direct-to-peripheral-nerve (invasive), and cortical stimulation have been applied. Peripheral nerve interfaces demonstrate an edge over the cortical interfaces due to the sensitivity in attaining cortical brain signals. The peripheral nerve interfaces are highly dependent on interface designs and are required to be biocompatible with the nerves to achieve prolonged stability and longevity. Another criterion is the selection of nerves that allows minimal invasiveness and damages as well as high selectivity for a large number of nerve fascicles. In this paper, we review the nerve-machine interface modalities noted above with more focus on peripheral nerve interfaces, which are responsible for provision of sensory feedback. The invasive interfaces for recording and stimulation of electro-neurographic signals include intra-fascicular, regenerative-type interfaces that provide multiple contact channels to a group of axons inside the nerve and the extra-neural-cuff-type interfaces that enable interaction with many axons around the periphery of the nerve. Section Current Prosthetic Technology summarizes the advancements made to date in the field of neuroprosthetics toward the achievement of a bidirectional nerve-machine interface with more focus on sensory feedback. In the Discussion section, the authors propose a hybrid interface technique for achieving better selectivity and long-term stability using the available nerve interfacing techniques. PMID:29163122
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.
NASA Technical Reports Server (NTRS)
Siegert, C. E.; Gourash, F.; Vasicek, R. W.
1977-01-01
The electrical and environmental requirements for a power processor system (PPS) designed to supply the appropriate voltages and currents to a 200-watt traveling wave tube (TWT) for a communication technology satellite is described. A block diagram of the PPS, the interface requirements between the PPS and spacecraft, the interface requirements between the PPS and 200-watt TWT, and the environmental requirements of the PPS are presented. Also included are discussions of protection circuits, interlocking sequences, and transient requirements. Predictions of the flight performance, based on ground test data, are provided.
ERIC Educational Resources Information Center
Jesberg, Robert O.; Dowden, Edward
1986-01-01
Explains how computer and game port interfacing reduces the time required for data collection and organization and also stimulates student interest in science laboratory exercises. Illustrates this approach through a description of a population-variation lab. Includes diagrams for the construction of the interface box. (ML)
Advanced EVA system design requirements study
NASA Technical Reports Server (NTRS)
Woods, T. G.
1988-01-01
The results are presented of a study to identify specific criteria regarding space station extravehicular activity system (EVAS) hardware requirements. Key EVA design issues include maintainability, technology readiness, LSS volume vs. EVA time available, suit pressure/cabin pressure relationship and productivity effects, crew autonomy, integration of EVA as a program resource, and standardization of task interfaces. A variety of DOD EVA systems issues were taken into consideration. Recommendations include: (1) crew limitations, not hardware limitations; (2) capability to perform all of 15 generic missions; (3) 90 days on-orbit maintainability with 50 percent duty cycle as minimum; and (4) use by payload sponsors of JSC document 10615A plus a Generic Tool Kit and Specialized Tool Kit description. EVA baseline design requirements and criteria, including requirements of various subsystems, are outlined. Space station/EVA system interface requirements and EVA accommodations are discussed in the areas of atmosphere composition and pressure, communications, data management, logistics, safe haven, SS exterior and interior requirements, and SS airlock.
Human Computer Interface Design Criteria. Volume 1. User Interface Requirements
2010-03-19
Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry. (c) All training...Shelf CSS Cascading Style Sheets DII Defense Information Infrastructure DISA Defense Information Systems Agency DoD Department of Defense
Man-machine interface requirements - advanced technology
NASA Technical Reports Server (NTRS)
Remington, R. W.; Wiener, E. L.
1984-01-01
Research issues and areas are identified where increased understanding of the human operator and the interaction between the operator and the avionics could lead to improvements in the performance of current and proposed helicopters. Both current and advanced helicopter systems and avionics are considered. Areas critical to man-machine interface requirements include: (1) artificial intelligence; (2) visual displays; (3) voice technology; (4) cockpit integration; and (5) pilot work loads and performance.
The virtual windtunnel: Visualizing modern CFD datasets with a virtual environment
NASA Technical Reports Server (NTRS)
Bryson, Steve
1993-01-01
This paper describes work in progress on a virtual environment designed for the visualization of pre-computed fluid flows. The overall problems involved in the visualization of fluid flow are summarized, including computational, data management, and interface issues. Requirements for a flow visualization are summarized. Many aspects of the implementation of the virtual windtunnel were uniquely determined by these requirements. The user interface is described in detail.
NASA Technical Reports Server (NTRS)
Voellmer, George M.
1992-01-01
Mechanism enables robot to change tools on end of arm. Actuated by motion of robot: requires no additional electrical or pneumatic energy to make or break connection between tool and wrist at end of arm. Includes three basic subassemblies: wrist interface plate attached to robot arm at wrist, tool interface plate attached to tool, and holster. Separate tool interface plate and holster provided for each tool robot uses.
Graphical Requirements for Force Level Planning. Volume 2
1991-09-01
technology review includes graphics algorithms, computer hardware, computer software, and design methodologies. The technology can either exist today or...level graphics language. 7.4 User Interface Design Tools As user interfaces have become more sophisticated, they have become harder to develop. Xl...Setphen M. Pizer, editors. Proceedings 1986 Workshop on Interactive 31) Graphics , October 1986. 18 J. S. Dumas. Designing User Interface Software. Prentice
NASA Technical Reports Server (NTRS)
1991-01-01
Summary reports on each of the eight tasks undertaken by this contract are given. Discussed here is an evaluation of a Closed Ecological Life Support System (CELSS), including modeling and analysis of Physical/Chemical Closed Loop Life Support (P/C CLLS); the Environmental Control and Life Support Systems (ECLSS) evolution - Intermodule Ventilation study; advanced technologies interface requirements relative to ECLSS; an ECLSS resupply analysis; the ECLSS module addition relocation systems engineering analysis; an ECLSS cost/benefit analysis to identify rack-level interface requirements of the alternate technologies evaluated in the ventilation study, with a comparison of these with the rack level interface requirements for the baseline technologies; advanced instrumentation - technology database enhancement; and a clean room survey and assessment of various ECLSS evaluation options for different growth scenarios.
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.
NASA Technical Reports Server (NTRS)
Fura, David A.; Windley, Phillip J.; Cohen, Gerald C.
1993-01-01
This technical report contains the HOL listings of the specification of the design and major portions of the requirements for a commercially developed processor interface unit (or PIU). The PIU is an interface chip performing memory interface, bus interface, and additional support services for a commercial microprocessor within a fault-tolerant computer system. This system, the Fault-Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance-free operation, or both. This report contains the actual HOL listings of the PIU specification as it currently exists. Section two of this report contains general-purpose HOL theories that support the PIU specification. These theories include definitions for the hardware components used in the PIU, our implementation of bit words, and our implementation of temporal logic. Section three contains the HOL listings for the PIU design specification. Aside from the PIU internal bus (I-Bus), this specification is complete. Section four contains the HOL listings for a major portion of the PIU requirements specification. Specifically, it contains most of the definition for the PIU behavior associated with memory accesses initiated by the local processor.
Adaptation of the Camera Link Interface for Flight-Instrument Applications
NASA Technical Reports Server (NTRS)
Randall, David P.; Mahoney, John C.
2010-01-01
COTS (commercial-off-the-shelf) hard ware using an industry-standard Camera Link interface is proposed to accomplish the task of designing, building, assembling, and testing electronics for an airborne spectrometer that would be low-cost, but sustain the required data speed and volume. The focal plane electronics were designed to support that hardware standard. Analysis was done to determine how these COTS electronics could be interfaced with space-qualified camera electronics. Interfaces available for spaceflight application do not support the industry standard Camera Link interface, but with careful design, COTS EGSE (electronics ground support equipment), including camera interfaces and camera simulators, can still be used.
Controllable Grid Interface | Grid Modernization | NREL
groundbreaking apparatus for testing and demonstrating advanced controls for wind and solar power generation at requirements. These requirements involve various aspects of renewable power plant operation, including fault respond directly to grid conditions measured on plant terminals, including: "Nasty" and "
Flat-panel display solutions for ground-environment military displays (Invited Paper)
NASA Astrophysics Data System (ADS)
Thomas, J., II; Roach, R.
2005-05-01
Displays for military vehicles have very distinct operational and cost requirements that differ from other military applications. These requirements demand that display suppliers to Army and Marine ground-environments provide low cost equipment that is capable of operation across environmental extremes. Inevitably, COTS components form the foundation of these "affordable" display solutions. This paper will outline the major display requirements and review the options that satisfy conflicting and difficult operational demands, using newly developed equipment as an example. Recently, a new supplier was selected for the Drivers Vision Enhancer (DVE) equipment, including the Display Control Module (DCM). The paper will outline the DVE and describe development of a new DCM solution. The DVE programme, with several thousand units presently in service and operational in conflicts such as "Operation Iraqi Freedom", represents a critical balance between cost and performance. We shall describe design considerations that include selection of COTS sources, the need to minimise display modification; video interfaces, power interfaces, operator interfaces and new provisions to optimise displayed video content.
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.
Development of hermetic electrical connectors for SSC spool pieces
DOE Office of Scientific and Technical Information (OSTI.GOV)
Kountanis, B.; Kalny, L.
1993-05-01
The Superconducting Super Collider ring is about 54 miles (87 km circumference) and primarily includes a series of magnets. Spool piece assemblies are interspaced in the ring at predetermined intervals to provide specific functions such as cryogenic interfaces, vacuum interface, magnet power, magnet power dump, quench heater power, and special instrumentation. Electrical connectors serve as interfaces for instrumentation and quench heater circuits. These connectors have to meet stringent requirements.
An intelligent interface for satellite operations: Your Orbit Determination Assistant (YODA)
NASA Technical Reports Server (NTRS)
Schur, Anne
1988-01-01
An intelligent interface is often characterized by the ability to adapt evaluation criteria as the environment and user goals change. Some factors that impact these adaptations are redefinition of task goals and, hence, user requirements; time criticality; and system status. To implement adaptations affected by these factors, a new set of capabilities must be incorporated into the human-computer interface design. These capabilities include: (1) dynamic update and removal of control states based on user inputs, (2) generation and removal of logical dependencies as change occurs, (3) uniform and smooth interfacing to numerous processes, databases, and expert systems, and (4) unobtrusive on-line assistance to users of concepts were applied and incorporated into a human-computer interface using artificial intelligence techniques to create a prototype expert system, Your Orbit Determination Assistant (YODA). YODA is a smart interface that supports, in real teime, orbit analysts who must determine the location of a satellite during the station acquisition phase of a mission. Also described is the integration of four knowledge sources required to support the orbit determination assistant: orbital mechanics, spacecraft specifications, characteristics of the mission support software, and orbit analyst experience. This initial effort is continuing with expansion of YODA's capabilities, including evaluation of results of the orbit determination task.
Service offerings and interfaces for the ACTS network of Earth stations
NASA Technical Reports Server (NTRS)
Coney, Thom A.
1988-01-01
The Advanced Communications Satellite (ACTS) is capable of two modes of communication. Mode 1 is a mesh network of Earth stations using baseband-switched, time-division multiple-access (BBS-TDMA) and hopping beams. Mode 2 is a mesh network using satellite-switched, time-division multiple-access (SS-TDMA) and fixed (or hopping) beams. The purpose of this paper is to present the functional requirements and the design of the ACTS Mode 1 Earth station terrestrial interface. Included among the requirements are that: (1) the interface support standard telecommunications service offerings (i.e., voice, video and data at rates ranging from 9.6 kbps to 44 Mbps); (2) the interface support the unique design characteristics of the ACTS communications systems (e.g., the real time demand assignment of satellite capacity); and (3) the interface support test hardware capable of validating ACTS communications processes. The resulting interface design makes use of an appropriate combination of T1 or T3 multiplexers and a small central office (maximum capacity 56 subscriber lines per unit).
Communications interface for wireless communications headset
NASA Technical Reports Server (NTRS)
Culotta, Jr., Anthony Joseph (Inventor); Seibert, Marc A. (Inventor)
2004-01-01
A universal interface adapter circuit interfaces, for example, a wireless communications headset with any type of communications system, including those that require push-to-talk (PTT) signaling. The interface adapter is comprised of several main components, including an RF signaling receiver, a microcontroller and associated circuitry for decoding and processing the received signals, and programmable impedance matching and line interfacing circuitry for interfacing a wireless communications headset system base to a communications system. A signaling transmitter, which is preferably portable (e.g., handheld), is employed by the wireless headset user to send signals to the signaling receiver. In an embodiment of the invention directed specifically to push-to-talk (PTT) signaling, the wireless headset user presses a button on the signaling transmitter when they wish to speak. This sends a signal to the microcontroller which decodes the signal and recognizes the signal as being a PTT request. In response, the microcontroller generates a control signal that closes a switch to complete a voice connection between the headset system base and the communications system so that the user can communicate with the communications system. With this arrangement, the wireless headset can be interfaced to any communications system that requires PTT signaling, without modification of the headset device. In addition, the interface adapter can also be configured to respond to or deliver any other types of signals, such as dual-tone-multiple-frequency (DTMF) tones, and on/off hook signals. The present invention is also scalable, and permits multiple wireless users to operate independently in the same environment through use of a plurality of the interface adapters.
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).
NASA Astrophysics Data System (ADS)
Steigerwald, R. L.; Ferraro, A.; Turnbull, F. G.
1983-04-01
Power conditioning systems that interface with photovoltaic arrays are presently investigated for the cases of 5-30 kW residential systems interfacing with a 240-V single-phase utility connection, and 30-200 kW intermediate systems interfacing with a 480-V three-phase utility connection. Both systems require an isolation transformer between the array and the utility interface. A tradeoff study is conducted for numerous transistor and thyristor circuits and configurations, with weighting criteria that include full- and part-load efficiency, size, weight, reliability, ease of control, injected harmonics, reactive power requirements, and parts cost. On the basis of study results, a 10-kW high frequency transistor inverter feeding a high frequency isolation transformer with a sinusoidally shaped current wave was selected.
19 CFR 128.23 - Entry requirements.
Code of Federal Regulations, 2010 CFR
2010-04-01
... utilizing the procedures in this part shall comply with the requirements of the Customs Automated Commercial System (ACS). These requirements include those under the Automated Manifest System (AMS), Cargo Selectivity, Statement Processing, the Automated Broker Interface System (ABI), and enhancements of ACS. (2...
Space transportation system payload interface verification
NASA Technical Reports Server (NTRS)
Everline, R. T.
1977-01-01
The paper considers STS payload-interface verification requirements and the capability provided by STS to support verification. The intent is to standardize as many interfaces as possible, not only through the design, development, test and evaluation (DDT and E) phase of the major payload carriers but also into the operational phase. The verification process is discussed in terms of its various elements, such as the Space Shuttle DDT and E (including the orbital flight test program) and the major payload carriers DDT and E (including the first flights). Five tools derived from the Space Shuttle DDT and E are available to support the verification process: mathematical (structural and thermal) models, the Shuttle Avionics Integration Laboratory, the Shuttle Manipulator Development Facility, and interface-verification equipment (cargo-integration test equipment).
Crew interface definition study, phase 1
NASA Technical Reports Server (NTRS)
Callihan, J. C.; Kraemer, J. W.; Alles, J. A.
1971-01-01
The timeline analysis of the Shuttle orbiter missions which was conducted in the Phase I Crew Interface Definition Study and the requirements for the man-in-the-loop simulation study are presented. Mission definitions and objectives are presented as they relate to various Shuttle Orbiter missions. The requirements for crew participation and the information required by the crew are discussed, and finally the rationale behind the display concept and calling procedures is given. The simulation objectives, the simulation mechanization, including a detailed presentation of the display and control concept, the simulator test plan and the results are discussed.
Area health education center libraries and medical school libraries: establishing an interface.
Bandy, C R
1978-01-01
Establishing an interface between area health education center (AHEC) libraries and medical school libraries requires careful planning, including: the overall plan, needs assessment, resource evaluation, a developmental plan, monitoring and evaluation, institutional agreements, and publicity. This paper reports on the development of AHEC libraries in North Dakota. PMID:708958
Computer interfaces for the visually impaired
NASA Technical Reports Server (NTRS)
Higgins, Gerry
1991-01-01
Information access via computer terminals extends to blind and low vision persons employed in many technical and nontechnical disciplines. Two aspects are detailed of providing computer technology for persons with a vision related handicap. First, research into the most effective means of integrating existing adaptive technologies into information systems was made. This was conducted to integrate off the shelf products with adaptive equipment for cohesive integrated information processing systems. Details are included that describe the type of functionality required in software to facilitate its incorporation into a speech and/or braille system. The second aspect is research into providing audible and tactile interfaces to graphics based interfaces. Parameters are included for the design and development of the Mercator Project. The project will develop a prototype system for audible access to graphics based interfaces. The system is being built within the public domain architecture of X windows to show that it is possible to provide access to text based applications within a graphical environment. This information will be valuable to suppliers to ADP equipment since new legislation requires manufacturers to provide electronic access to the visually impaired.
Constellation Program Human-System Integration Requirements. Revision E, Nov. 19, 2010
NASA Technical Reports Server (NTRS)
Dory, Jonathan
2010-01-01
The Human-Systems Integration Requirements (HSIR) in this document drive the design of space vehicles, their systems, and equipment with which humans interface in the Constellation Program (CxP). These requirements ensure that the design of Constellation (Cx) systems is centered on the needs, capabilities, and limitations of the human. The HSIR provides requirements to ensure proper integration of human-to-system interfaces. These requirements apply to all mission phases, including pre-launch, ascent, Earth orbit, trans-lunar flight, lunar orbit, lunar landing, lunar ascent, Earth return, Earth entry, Earth landing, post-landing, and recovery. The Constellation Program must meet NASA's Agency-level human rating requirements, which are intended to ensure crew survival without permanent disability. The HSIR provides a key mechanism for achieving human rating of Constellation systems.
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.
7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.
Code of Federal Regulations, 2012 CFR
2012-01-01
... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...
7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.
Code of Federal Regulations, 2013 CFR
2013-01-01
... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...
7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.
Code of Federal Regulations, 2014 CFR
2014-01-01
... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...
7 CFR 1755.910 - RUS specification for outside plant housings and serving area interface systems.
Code of Federal Regulations, 2011 CFR
2011-01-01
... requirements are interrelated to several tests designed to determine the performance aspects of terminals and... environments. Included are the mechanical, electrical, and environmental requirements, desired design features, and test methods for evaluation of the product. (2) The housing and terminal requirements reflect the...
HAL/S-FC compiler system functional specification
NASA Technical Reports Server (NTRS)
1974-01-01
The functional requirements to be met by the HAL/S-FC compiler, and the hardware and software compatibilities between the compiler system and the environment in which it operates are defined. Associated runtime facilities and the interface with the Software Development Laboratory are specified. The construction of the HAL/S-FC system as functionally separate units and the interfaces between those units is described. An overview of the system's capabilities is presented and the hardware/operating system requirements are specified. The computer-dependent aspects of the HAL/S-FC are also specified. Compiler directives are included.
Geographic information system/watershed model interface
Fisher, Gary T.
1989-01-01
Geographic information systems allow for the interactive analysis of spatial data related to water-resources investigations. A conceptual design for an interface between a geographic information system and a watershed model includes functions for the estimation of model parameter values. Design criteria include ease of use, minimal equipment requirements, a generic data-base management system, and use of a macro language. An application is demonstrated for a 90.1-square-kilometer subbasin of the Patuxent River near Unity, Maryland, that performs automated derivation of watershed parameters for hydrologic modeling.
Viper cabin-fuselage structural design concept with engine installation and wing structural design
NASA Technical Reports Server (NTRS)
Marchesseault, B.; Carr, D.; Mccorkle, T.; Stevens, C.; Turner, D.
1993-01-01
This report describes the process and considerations in designing the cabin, nose, drive shaft, and wing assemblies for the 'Viper' concept aircraft. Interfaces of these assemblies, as well as interfaces with the sections of the aircraft aft of the cabin, are also discussed. The results of the design process are included. The goal of this project is to provide a structural design which complies with FAR 23 requirements regarding occupant safety, emergency landing loads, and maneuvering loads. The design must also address the interfaces of the various systems in the cabin, nose, and wing, including the drive shaft, venting, vacuum, electrical, fuel, and control systems. Interfaces between the cabin assembly and the wing carrythrough and empennage assemblies were required, as well. In the design of the wing assemblies, consistency with the existing cabin design was required. The major areas considered in this report are materials and construction, loading, maintenance, environmental considerations, wing assembly fatigue, and weight. The first three areas are developed separately for the nose, cabin, drive shaft, and wing assemblies, while the last three are discussed for the entire design. For each assembly, loading calculations were performed to determine the proper sizing of major load carrying components. Table 1.0 lists the resulting margins of safety for these key components, along with the types of the loads involved, and the page number upon which they are discussed.
Z-2 Architecture Description and Requirements Verification Results
NASA Technical Reports Server (NTRS)
Graziosi, Dave; Jones, Bobby; Ferl, Jinny; Scarborough, Steve; Hewes, Linda; Ross, Amy; Rhodes, Richard
2016-01-01
The Z-2 Prototype Planetary Extravehicular Space Suit Assembly is a continuation of NASA's Z series of spacesuits. The Z-2 is another step in NASA's technology development roadmap leading to human exploration of the Martian surface. The suit was designed for maximum mobility at 8.3 psid, reduced mass, and to have high fidelity life support interfaces. As Z-2 will be man-tested at full vacuum in NASA JSC's Chamber B, it was manufactured as Class II, making it the most flight-like planetary walking suit produced to date. The Z-2 suit architecture is an evolution of previous EVA suits, namely the ISS EMU, Mark III, Rear Entry I-Suit and Z-1 spacesuits. The suit is a hybrid hard and soft multi-bearing, rear entry spacesuit. The hard upper torso (HUT) is an all-composite structure and includes a 2-bearing rolling convolute shoulder with Vernier sizing mechanism, removable suit port interface plate (SIP), elliptical hemispherical helmet and self-don/doff shoulder harness. The hatch is a hybrid aluminum and composite construction with Apollo style gas connectors, custom water pass-thru, removable hatch cage and interfaces to primary and auxiliary life support feed water bags. The suit includes Z-1 style lower arms with cam brackets for Vernier sizing and government furnished equipment (GFE) Phase VI gloves. The lower torso includes a telescopic waist sizing system, waist bearing, rolling convolute waist joint, hard brief, 2 bearing soft hip thigh, Z-1 style legs with ISS EMU style cam brackets for sizing, and conformal walking boots with ankle bearings. The Z-2 Requirements Verification Plan includes the verification of more than 200 individual requirements. The verification methods include test, analysis, inspection, demonstration or a combination of methods. Examples of unmanned requirements include suit leakage, proof pressure testing, operational life, mass, isometric man-loads, sizing adjustment ranges, internal and external interfaces such as in-suit drink bag, partial pressure relief valve, purge valve, donning stand and ISS Body Restraint Tether (BRT). Examples of manned requirements include verification of anthropometric range, suit self-don/doff, secondary suit exit method, donning stand self-ingress/egress and manned mobility covering eight functional tasks. The eight functional tasks include kneeling with object pick-up, standing toe touch, cross-body reach, walking, reach to the SIP and helmet visor. This paper will provide an overview of the Z-2 design. Z-2 requirements verification testing was performed with NASA at the ILC Houston test facility. This paper will also discuss pre-delivery manned and unmanned test results as well as analysis performed in support of requirements verification.
EOS image data processing system definition study
NASA Technical Reports Server (NTRS)
Gilbert, J.; Honikman, T.; Mcmahon, E.; Miller, E.; Pietrzak, L.; Yorsz, W.
1973-01-01
The Image Processing System (IPS) requirements and configuration are defined for NASA-sponsored advanced technology Earth Observatory System (EOS). The scope included investigation and definition of IPS operational, functional, and product requirements considering overall system constraints and interfaces (sensor, etc.) The scope also included investigation of the technical feasibility and definition of a point design reflecting system requirements. The design phase required a survey of present and projected technology related to general and special-purpose processors, high-density digital tape recorders, and image recorders.
Code of Federal Regulations, 2012 CFR
2012-10-01
... physical relationships in the subsystem or system; (2) A description of the railroad operation or... requirements; (5) A preliminary human factors analysis, including a complete description of all human-machine interfaces and the impact of interoperability requirements on the same; (6) An analysis of the applicability...
Code of Federal Regulations, 2011 CFR
2011-10-01
... physical relationships in the subsystem or system; (2) A description of the railroad operation or... requirements; (5) A preliminary human factors analysis, including a complete description of all human-machine interfaces and the impact of interoperability requirements on the same; (6) An analysis of the applicability...
Code of Federal Regulations, 2013 CFR
2013-10-01
... physical relationships in the subsystem or system; (2) A description of the railroad operation or... requirements; (5) A preliminary human factors analysis, including a complete description of all human-machine interfaces and the impact of interoperability requirements on the same; (6) An analysis of the applicability...
Code of Federal Regulations, 2014 CFR
2014-10-01
... physical relationships in the subsystem or system; (2) A description of the railroad operation or... requirements; (5) A preliminary human factors analysis, including a complete description of all human-machine interfaces and the impact of interoperability requirements on the same; (6) An analysis of the applicability...
NASA Technical Reports Server (NTRS)
Radtke, Robert; Woolley, Charles; Arnold, Lana
1993-01-01
The purpose of the NASA Space Assembly and Servicing Working Group (SASWG) is to study enabling technologies for on-orbit spacecraft maintenance and servicing. One key technology required for effective space logistics activity is the development of standard spacecraft interfaces, including the 'Basic Set' defined by NASA, the U.S. Space Command, and industry panelists to be the following: (1) navigation aids; (2) grasping, berthing, and docking; and (3) utility connections for power, data, and fluids. Draft standards have been prepared and referred to professional standards organizations, including the AIAA, EIA, and SAE space standards committee. The objective of the SASWG is to support these committees with the technical expertise required to prepare standards, guidelines, and recommended practices which will be accepted by the ANSI and international standards organizations, including the ISO, IEC, and PASC.
We can't explore space without it - Common human space needs for exploration spaceflight
NASA Technical Reports Server (NTRS)
Daues, K. R.; Erwin, H. O.
1992-01-01
An overview is conducted of physiological, psychological, and human-interface requirements for manned spaceflight programs to establish common criteria. Attention is given to the comfort levels relevant to human support in exploration mission spacecraft and planetary habitats, and three comfort levels (CLs) are established. The levels include: (1) CL-1 for basic crew life support; (2) CL-2 for enabling the nominal completion of mission science; and (3) CL-3 which provides for enhanced life support and user-friendly interface systems. CL-2 support systems can include systems for EVA, workstations, and activity centers for repairs and enhanced utilization of payload and human/machine integration. CL-3 supports can be useful for maintaining crew psychological and physiological health as well as the design of comfortable and earthlike surroundings. While all missions require CL-1 commonality, CL-2 commonality is required only for EVA systems, display nomenclature, and restraint designs.
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.
US Search and Rescue Mission Control Center functions
NASA Technical Reports Server (NTRS)
1977-01-01
A satellite aided Search and Rescue (SAR) Mission concept consisting of a local coverage bent pipe system, and a global coverage system is described. The SAR instrument is to consist of a Canadian repeater and a French processor for which Canada and France, respectively are to evaluate health and trends. Performance evaluations of each system were provided. The United States and Canada will each have a Search and Rescue Mission Control Center (MCC) and their functions were also examined. A summary of the interface requirements necessary to perform each function was included as well as the information requirements between the USMCC and each of its interfaces. Physical requirements such as location, manning etc. of the USMCC were discussed.
NASA Technical Reports Server (NTRS)
Lewis, Clayton; Wilde, Nick
1989-01-01
Space construction will require heavy investment in the development of a wide variety of user interfaces for the computer-based tools that will be involved at every stage of construction operations. Using today's technology, user interface development is very expensive for two reasons: (1) specialized and scarce programming skills are required to implement the necessary graphical representations and complex control regimes for high-quality interfaces; (2) iteration on prototypes is required to meet user and task requirements, since these are difficult to anticipate with current (and foreseeable) design knowledge. We are attacking this problem by building a user interface development tool based on extensions to the spreadsheet model of computation. The tool provides high-level support for graphical user interfaces and permits dynamic modification of interfaces, without requiring conventional programming concepts and skills.
Basic concepts and development of an all-purpose computer interface for ROC/FROC observer study.
Shiraishi, Junji; Fukuoka, Daisuke; Hara, Takeshi; Abe, Hiroyuki
2013-01-01
In this study, we initially investigated various aspects of requirements for a computer interface employed in receiver operating characteristic (ROC) and free-response ROC (FROC) observer studies which involve digital images and ratings obtained by observers (radiologists). Secondly, by taking into account these aspects, an all-purpose computer interface utilized for these observer performance studies was developed. Basically, the observer studies can be classified into three paradigms, such as one rating for one case without an identification of a signal location, one rating for one case with an identification of a signal location, and multiple ratings for one case with identification of signal locations. For these paradigms, display modes on the computer interface can be used for single/multiple views of a static image, continuous viewing with cascade images (i.e., CT, MRI), and dynamic viewing of movies (i.e., DSA, ultrasound). Various functions on these display modes, which include windowing (contrast/level), magnifications, and annotations, are needed to be selected by an experimenter corresponding to the purpose of the research. In addition, the rules of judgment for distinguishing between true positives and false positives are an important factor for estimating diagnostic accuracy in an observer study. We developed a computer interface which runs on a Windows operating system by taking into account all aspects required for various observer studies. This computer interface requires experimenters to have sufficient knowledge about ROC/FROC observer studies, but allows its use for any purpose of the observer studies. This computer interface will be distributed publicly in the near future.
Knowledge-based control of an adaptive interface
NASA Technical Reports Server (NTRS)
Lachman, Roy
1989-01-01
The analysis, development strategy, and preliminary design for an intelligent, adaptive interface is reported. The design philosophy couples knowledge-based system technology with standard human factors approaches to interface development for computer workstations. An expert system has been designed to drive the interface for application software. The intelligent interface will be linked to application packages, one at a time, that are planned for multiple-application workstations aboard Space Station Freedom. Current requirements call for most Space Station activities to be conducted at the workstation consoles. One set of activities will consist of standard data management services (DMS). DMS software includes text processing, spreadsheets, data base management, etc. Text processing was selected for the first intelligent interface prototype because text-processing software can be developed initially as fully functional but limited with a small set of commands. The program's complexity then can be increased incrementally. The intelligent interface includes the operator's behavior and three types of instructions to the underlying application software are included in the rule base. A conventional expert-system inference engine searches the data base for antecedents to rules and sends the consequents of fired rules as commands to the underlying software. Plans for putting the expert system on top of a second application, a database management system, will be carried out following behavioral research on the first application. The intelligent interface design is suitable for use with ground-based workstations now common in government, industrial, and educational organizations.
The Overgrid Interface for Computational Simulations on Overset Grids
NASA Technical Reports Server (NTRS)
Chan, William M.; Kwak, Dochan (Technical Monitor)
2002-01-01
Computational simulations using overset grids typically involve multiple steps and a variety of software modules. A graphical interface called OVERGRID has been specially designed for such purposes. Data required and created by the different steps include geometry, grids, domain connectivity information and flow solver input parameters. The interface provides a unified environment for the visualization, processing, generation and diagnosis of such data. General modules are available for the manipulation of structured grids and unstructured surface triangulations. Modules more specific for the overset approach include surface curve generators, hyperbolic and algebraic surface grid generators, a hyperbolic volume grid generator, Cartesian box grid generators, and domain connectivity: pre-processing tools. An interface provides automatic selection and viewing of flow solver boundary conditions, and various other flow solver inputs. For problems involving multiple components in relative motion, a module is available to build the component/grid relationships and to prescribe and animate the dynamics of the different components.
Natural interaction for unmanned systems
NASA Astrophysics Data System (ADS)
Taylor, Glenn; Purman, Ben; Schermerhorn, Paul; Garcia-Sampedro, Guillermo; Lanting, Matt; Quist, Michael; Kawatsu, Chris
2015-05-01
Military unmanned systems today are typically controlled by two methods: tele-operation or menu-based, search-andclick interfaces. Both approaches require the operator's constant vigilance: tele-operation requires constant input to drive the vehicle inch by inch; a menu-based interface requires eyes on the screen in order to search through alternatives and select the right menu item. In both cases, operators spend most of their time and attention driving and minding the unmanned systems rather than on being a warfighter. With these approaches, the platform and interface become more of a burden than a benefit. The availability of inexpensive sensor systems in products such as Microsoft Kinect™ or Nintendo Wii™ has resulted in new ways of interacting with computing systems, but new sensors alone are not enough. Developing useful and usable human-system interfaces requires understanding users and interaction in context: not just what new sensors afford in terms of interaction, but how users want to interact with these systems, for what purpose, and how sensors might enable those interactions. Additionally, the system needs to reliably make sense of the user's inputs in context, translate that interpretation into commands for the unmanned system, and give feedback to the user. In this paper, we describe an example natural interface for unmanned systems, called the Smart Interaction Device (SID), which enables natural two-way interaction with unmanned systems including the use of speech, sketch, and gestures. We present a few example applications SID to different types of unmanned systems and different kinds of interactions.
Universal Design and the Smart Home.
Pennick, Tim; Hessey, Sue; Craigie, Roland
2016-01-01
The related concepts of Universal Design, Inclusive Design, and Design For All, all recognise that no one solution will fit the requirements of every possible user. This paper considers the extent to which current developments in smart home technology can help to reduce the numbers of users for whom mainstream technology is not sufficiently inclusive, proposing a flexible approach to user interface (UI) implementation focussed on the capabilities of the user. This implies development of the concepts underlying Universal Design to include the development of a flexible inclusive support infrastructure, servicing the requirements of individual users and their personalised user interface devices.
NASA Technical Reports Server (NTRS)
Harrison, P. Ann
1993-01-01
All the NASA VEGetation Workbench (VEG) goals except the Learning System provide the scientist with several different techniques. When VEG is run, rules assist the scientist in selecting the best of the available techniques to apply to the sample of cover type data being studied. The techniques are stored in the VEG knowledge base. The design and implementation of an interface that allows the scientist to add new techniques to VEG without assistance from the developer were completed. A new interface that enables the scientist to add techniques to VEG without assistance from the developer was designed and implemented. This interface does not require the scientist to have a thorough knowledge of Knowledge Engineering Environment (KEE) by Intellicorp or a detailed knowledge of the structure of VEG. The interface prompts the scientist to enter the required information about the new technique. It prompts the scientist to enter the required Common Lisp functions for executing the technique and the left hand side of the rule that causes the technique to be selected. A template for each function and rule and detailed instructions about the arguments of the functions, the values they should return, and the format of the rule are displayed. Checks are made to ensure that the required data were entered, the functions compiled correctly, and the rule parsed correctly before the new technique is stored. The additional techniques are stored separately from the VEG knowledge base. When the VEG knowledge base is loaded, the additional techniques are not normally loaded. The interface allows the scientist the option of adding all the previously defined new techniques before running VEG. When the techniques are added, the required units to store the additional techniques are created automatically in the correct places in the VEG knowledge base. The methods file containing the functions required by the additional techniques is loaded. New rule units are created to store the new rules. The interface that allow the scientist to select which techniques to use is updated automatically to include the new techniques. Task H was completed. The interface that allows the scientist to add techniques to VEG was implemented and comprehensively tested. The Common Lisp code for the Add Techniques system is listed in Appendix A.
A mobile phone user interface for image-based dietary assessment
NASA Astrophysics Data System (ADS)
Ahmad, Ziad; Khanna, Nitin; Kerr, Deborah A.; Boushey, Carol J.; Delp, Edward J.
2014-02-01
Many chronic diseases, including obesity and cancer, are related to diet. Such diseases may be prevented and/or successfully treated by accurately monitoring and assessing food and beverage intakes. Existing dietary assessment methods such as the 24-hour dietary recall and the food frequency questionnaire, are burdensome and not generally accurate. In this paper, we present a user interface for a mobile telephone food record that relies on taking images, using the built-in camera, as the primary method of recording. We describe the design and implementation of this user interface while stressing the solutions we devised to meet the requirements imposed by the image analysis process, yet keeping the user interface easy to use.
A Mobile Phone User Interface for Image-Based Dietary Assessment
Ahmad, Ziad; Khanna, Nitin; Kerr, Deborah A.; Boushey, Carol J.; Delp, Edward J.
2016-01-01
Many chronic diseases, including obesity and cancer, are related to diet. Such diseases may be prevented and/or successfully treated by accurately monitoring and assessing food and beverage intakes. Existing dietary assessment methods such as the 24-hour dietary recall and the food frequency questionnaire, are burdensome and not generally accurate. In this paper, we present a user interface for a mobile telephone food record that relies on taking images, using the built-in camera, as the primary method of recording. We describe the design and implementation of this user interface while stressing the solutions we devised to meet the requirements imposed by the image analysis process, yet keeping the user interface easy to use. PMID:28572696
A Mobile Phone User Interface for Image-Based Dietary Assessment.
Ahmad, Ziad; Khanna, Nitin; Kerr, Deborah A; Boushey, Carol J; Delp, Edward J
2014-02-02
Many chronic diseases, including obesity and cancer, are related to diet. Such diseases may be prevented and/or successfully treated by accurately monitoring and assessing food and beverage intakes. Existing dietary assessment methods such as the 24-hour dietary recall and the food frequency questionnaire, are burdensome and not generally accurate. In this paper, we present a user interface for a mobile telephone food record that relies on taking images, using the built-in camera, as the primary method of recording. We describe the design and implementation of this user interface while stressing the solutions we devised to meet the requirements imposed by the image analysis process, yet keeping the user interface easy to use.
NASA Technical Reports Server (NTRS)
Shaykhian, Gholam Ali
2007-01-01
The Java seminar covers the fundamentals of Java programming language. No prior programming experience is required for participation in the seminar. The first part of the seminar covers introductory concepts in Java programming including data types (integer, character, ..), operators, functions and constants, casts, input, output, control flow, scope, conditional statements, and arrays. Furthermore, introduction to Object-Oriented programming in Java, relationships between classes, using packages, constructors, private data and methods, final instance fields, static fields and methods, and overloading are explained. The second part of the seminar covers extending classes, inheritance hierarchies, polymorphism, dynamic binding, abstract classes, protected access. The seminar conclude by introducing interfaces, properties of interfaces, interfaces and abstract classes, interfaces and cailbacks, basics of event handling, user interface components with swing, applet basics, converting applications to applets, the applet HTML tags and attributes, exceptions and debugging.
Interface Management for a NASA Flight Project Using Model-Based Systems Engineering (MBSE)
NASA Technical Reports Server (NTRS)
Vipavetz, Kevin; Shull, Thomas A.; Infeld, Samatha; Price, Jim
2016-01-01
The goal of interface management is to identify, define, control, and verify interfaces; ensure compatibility; provide an efficient system development; be on time and within budget; while meeting stakeholder requirements. This paper will present a successful seven-step approach to interface management used in several NASA flight projects. The seven-step approach using Model Based Systems Engineering will be illustrated by interface examples from the Materials International Space Station Experiment-X (MISSE-X) project. The MISSE-X was being developed as an International Space Station (ISS) external platform for space environmental studies, designed to advance the technology readiness of materials and devices critical for future space exploration. Emphasis will be given to best practices covering key areas such as interface definition, writing good interface requirements, utilizing interface working groups, developing and controlling interface documents, handling interface agreements, the use of shadow documents, the importance of interface requirement ownership, interface verification, and product transition.
Ground Systems Development Environment (GSDE) interface requirements analysis
NASA Technical Reports Server (NTRS)
Church, Victor E.; Philips, John; Hartenstein, Ray; Bassman, Mitchell; Ruskin, Leslie; Perez-Davila, Alfredo
1991-01-01
A set of procedural and functional requirements are presented for the interface between software development environments and software integration and test systems used for space station ground systems software. The requirements focus on the need for centralized configuration management of software as it is transitioned from development to formal, target based testing. This concludes the GSDE Interface Requirements study. A summary is presented of findings concerning the interface itself, possible interface and prototyping directions for further study, and results of the investigation of the Cronus distributed applications environment.
NASA Technical Reports Server (NTRS)
Wiley, Lowell F.
1985-01-01
The purpose of this requirements document is to develop the foundation for concept development for the Life Sciences Research Facility (LSRF) on the Space Station. These requirements are developed from the perspective of a Space Station laboratory module outfitter. Science and mission requirements including those related to specimens are set forth. System requirements, including those for support, are detailed. Functional and design requirements are covered in the areas of structures, mechanisms, electrical power, thermal systems, data management system, life support, and habitability. Finally, interface requirements for the Command Module and Logistics Module are described.
Detailed requirements document for the Interactive Financial Management System (IFMS), volume 1
NASA Technical Reports Server (NTRS)
Dodson, D. B.
1975-01-01
The detailed requirements for phase 1 (online fund control, subauthorization accounting, and accounts receivable functional capabilities) of the Interactive Financial Management System (IFMS) are described. This includes information on the following: systems requirements, performance requirements, test requirements, and production implementation. Most of the work is centered on systems requirements, and includes discussions on the following processes: resources authority, allotment, primary work authorization, reimbursable order acceptance, purchase request, obligation, cost accrual, cost distribution, disbursement, subauthorization performance, travel, accounts receivable, payroll, property, edit table maintenance, end-of-year, backup input. Other subjects covered include: external systems interfaces, general inquiries, general report requirements, communication requirements, and miscellaneous. Subjects covered under performance requirements include: response time, processing volumes, system reliability, and accuracy. Under test requirements come test data sources, general test approach, and acceptance criteria. Under production implementation come data base establishment, operational stages, and operational requirements.
Functional Interface Considerations within an Exploration Life Support System Architecture
NASA Technical Reports Server (NTRS)
Perry, Jay L.; Sargusingh, Miriam J.; Toomarian, Nikzad
2016-01-01
As notional life support system (LSS) architectures are developed and evaluated, myriad options must be considered pertaining to process technologies, components, and equipment assemblies. Each option must be evaluated relative to its impact on key functional interfaces within the LSS architecture. A leading notional architecture has been developed to guide the path toward realizing future crewed space exploration goals. This architecture includes atmosphere revitalization, water recovery and management, and environmental monitoring subsystems. Guiding requirements for developing this architecture are summarized and important interfaces within the architecture are discussed. The role of environmental monitoring within the architecture is described.
'Fly Like This': Natural Language Interface for UAV Mission Planning
NASA Technical Reports Server (NTRS)
Chandarana, Meghan; Meszaros, Erica L.; Trujillo, Anna; Allen, B. Danette
2017-01-01
With the increasing presence of unmanned aerial vehicles (UAVs) in everyday environments, the user base of these powerful and potentially intelligent machines is expanding beyond exclusively highly trained vehicle operators to include non-expert system users. Scientists seeking to augment costly and often inflexible methods of data collection historically used are turning towards lower cost and reconfigurable UAVs. These new users require more intuitive and natural methods for UAV mission planning. This paper explores two natural language interfaces - gesture and speech - for UAV flight path generation through individual user studies. Subjects who participated in the user studies also used a mouse-based interface for a baseline comparison. Each interface allowed the user to build flight paths from a library of twelve individual trajectory segments. Individual user studies evaluated performance, efficacy, and ease-of-use of each interface using background surveys, subjective questionnaires, and observations on time and correctness. Analysis indicates that natural language interfaces are promising alternatives to traditional interfaces. The user study data collected on the efficacy and potential of each interface will be used to inform future intuitive UAV interface design for non-expert users.
Marvel, Skylar W; To, Kimberly; Grimm, Fabian A; Wright, Fred A; Rusyn, Ivan; Reif, David M
2018-03-05
Drawing integrated conclusions from diverse source data requires synthesis across multiple types of information. The ToxPi (Toxicological Prioritization Index) is an analytical framework that was developed to enable integration of multiple sources of evidence by transforming data into integrated, visual profiles. Methodological improvements have advanced ToxPi and expanded its applicability, necessitating a new, consolidated software platform to provide functionality, while preserving flexibility for future updates. We detail the implementation of a new graphical user interface for ToxPi (Toxicological Prioritization Index) that provides interactive visualization, analysis, reporting, and portability. The interface is deployed as a stand-alone, platform-independent Java application, with a modular design to accommodate inclusion of future analytics. The new ToxPi interface introduces several features, from flexible data import formats (including legacy formats that permit backward compatibility) to similarity-based clustering to options for high-resolution graphical output. We present the new ToxPi interface for dynamic exploration, visualization, and sharing of integrated data models. The ToxPi interface is freely-available as a single compressed download that includes the main Java executable, all libraries, example data files, and a complete user manual from http://toxpi.org .
Statolith action by the numbers: Physics and feasbility
NASA Astrophysics Data System (ADS)
Todd, Paul; Yoder, Thomas; Staehelin, L. Andrew
2016-07-01
All modern (and ancient) studies make it clear that statolith motion is required for gravisensing, and some evidence indicates a role for statolith-microfilament interaction. In this study two components of statolith action are considered quantitatively: (1) the movement of statoliths through the columella cell cytoplasm and (2) forces at the site of action of the statolith. (1) Statoliths move through the cytoplasm in the presence of viscous and elastic forces that may be considered separately. The viscous component may be characterized as a solution with a viscosity of approximately 40 centiPoise. Statoliths are deflected from perfectly vertical trajectories by various obstacles, including actin filaments, and their velocities are influenced by interactions between statoliths. Channeling flow is commonly observed, but this cannot be due to the breaking of actin filaments by the force of the sedimenting statolith, as about 600 pN force is required to break a filament, and the force due to gravity on the amyloplast is about 0.07 pN. Under least viscous conditions the randomly-directed Brownian diffusion velocity of the amyloplast is about 10% the sedimentation velocity. (2) Intimate association of statoliths with the cortical ER region requiring gravitational force is postulated. Thin-section micrographs clearly show an interface between the cortex and the central cytoplasm of the columella cell in vascular plant species that have been studied. Whether or not an exchange of chemical components is required, experiments, including observations in low gravity, have demonstrated that the statolith is shallowly embedded in this cortical region to the extent that deformation occurs consistent with Newton's third law. Relieving the gravitational force results in instantaneous motion of the amyloplast away from the cortex. The following inquiry was made concerning the physics at the interface between the statolith and the material of the cortical ER region. How much force does the statolith exert on the interface between the ER cortex and inner cytoplasm? What is the origin of the elastic force that opposes the penetration of the statolith and that causes it to rebound when the gravitational force is relieved? Candidates considered included actin filaments, endoplasmic membrane, an immiscible-phase interface, and a miscible-phase interface. Forces estimated to produce a 300nm indentation in such interfaces were 100, 30, 0.3, and <1 pN, respectively. The gravitational force on a single statolith is typically 0.1 pN or less. These numbers suggest that the statolith is interacting with an aqueous-aqueous interface with low interfacial tension (<1 μN/m). Further quantitative testing of these notions should be performed on forthcoming low-gravity sub-orbital crewed flights on which dynamic microscopy can be performed during several seconds of increased g-loading followed by some ten minutes of reduced gravity.
Large Advanced Space Systems (LASS) computer-aided design program additions
NASA Technical Reports Server (NTRS)
Farrell, C. E.
1982-01-01
The LSS preliminary and conceptual design requires extensive iteractive analysis because of the effects of structural, thermal, and control intercoupling. A computer aided design program that will permit integrating and interfacing of required large space system (LSS) analyses is discussed. The primary objective of this program is the implementation of modeling techniques and analysis algorithms that permit interactive design and tradeoff studies of LSS concepts. Eight software modules were added to the program. The existing rigid body controls module was modified to include solar pressure effects. The new model generator modules and appendage synthesizer module are integrated (interfaced) to permit interactive definition and generation of LSS concepts. The mass properties module permits interactive specification of discrete masses and their locations. The other modules permit interactive analysis of orbital transfer requirements, antenna primary beam n, and attitude control requirements.
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.
Computer interface for mechanical arm
NASA Technical Reports Server (NTRS)
Derocher, W. L.; Zermuehlen, R. O.
1978-01-01
Man/machine interface commands computer-controlled mechanical arm. Remotely-controlled arm has six degrees of freedom and is controlled through "supervisory-control" mode, in which all motions of arm follow set of preprogramed sequences. For simplicity, few prescribed commands are required to accomplish entire operation. Applications include operating computer-controlled arm to handle radioactive of explosive materials or commanding arm to perform functions in hostile environments. Modified version using displays may be applied in medicine.
40 CFR 85.2231 - On-board diagnostic test equipment requirements.
Code of Federal Regulations, 2012 CFR
2012-07-01
... 40 Protection of Environment 19 2012-07-01 2012-07-01 false On-board diagnostic test equipment... Warranty Short Tests § 85.2231 On-board diagnostic test equipment requirements. (a) The test system interface to the vehicle shall include a plug that conforms to SAE J1962 “Diagnostic Connector.” The...
40 CFR 85.2231 - On-board diagnostic test equipment requirements.
Code of Federal Regulations, 2011 CFR
2011-07-01
... 40 Protection of Environment 18 2011-07-01 2011-07-01 false On-board diagnostic test equipment... Warranty Short Tests § 85.2231 On-board diagnostic test equipment requirements. (a) The test system interface to the vehicle shall include a plug that conforms to SAE J1962 “Diagnostic Connector.” The...
40 CFR 85.2231 - On-board diagnostic test equipment requirements.
Code of Federal Regulations, 2013 CFR
2013-07-01
... 40 Protection of Environment 19 2013-07-01 2013-07-01 false On-board diagnostic test equipment... Warranty Short Tests § 85.2231 On-board diagnostic test equipment requirements. (a) The test system interface to the vehicle shall include a plug that conforms to SAE J1962 “Diagnostic Connector.” The...
Water, water everywhere... integrated riparian research in the North Central Region
Lynne M. Westphal
2003-01-01
Riparian areas are important for many reasons including timber, residential areas, biodiversity, recreation, and industry. Because of the intricate land/water interface, these lands require special care. Determining what this care should be requires more knowledge than we currently have. Hence, the North Central Research Station (NCRS) has initiated the Sustaining...
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 Primer for Telemetry Interfacing in Accordance with NASA Standards Using Low Cost FPGAs
NASA Astrophysics Data System (ADS)
McCoy, Jake; Schultz, Ted; Tutt, James; Rogers, Thomas; Miles, Drew; McEntaffer, Randall
2016-03-01
Photon counting detector systems on sounding rocket payloads often require interfacing asynchronous outputs with a synchronously clocked telemetry (TM) stream. Though this can be handled with an on-board computer, there are several low cost alternatives including custom hardware, microcontrollers and field-programmable gate arrays (FPGAs). This paper outlines how a TM interface (TMIF) for detectors on a sounding rocket with asynchronous parallel digital output can be implemented using low cost FPGAs and minimal custom hardware. Low power consumption and high speed FPGAs are available as commercial off-the-shelf (COTS) products and can be used to develop the main component of the TMIF. Then, only a small amount of additional hardware is required for signal buffering and level translating. This paper also discusses how this system can be tested with a simulated TM chain in the small laboratory setting using FPGAs and COTS specialized data acquisition products.
A Finite Element Method for Simulation of Compressible Cavitating Flows
NASA Astrophysics Data System (ADS)
Shams, Ehsan; Yang, Fan; Zhang, Yu; Sahni, Onkar; Shephard, Mark; Oberai, Assad
2016-11-01
This work focuses on a novel approach for finite element simulations of multi-phase flows which involve evolving interface with phase change. Modeling problems, such as cavitation, requires addressing multiple challenges, including compressibility of the vapor phase, interface physics caused by mass, momentum and energy fluxes. We have developed a mathematically consistent and robust computational approach to address these problems. We use stabilized finite element methods on unstructured meshes to solve for the compressible Navier-Stokes equations. Arbitrary Lagrangian-Eulerian formulation is used to handle the interface motions. Our method uses a mesh adaptation strategy to preserve the quality of the volumetric mesh, while the interface mesh moves along with the interface. The interface jump conditions are accurately represented using a discontinuous Galerkin method on the conservation laws. Condensation and evaporation rates at the interface are thermodynamically modeled to determine the interface velocity. We will present initial results on bubble cavitation the behavior of an attached cavitation zone in a separated boundary layer. We acknowledge the support from Army Research Office (ARO) under ARO Grant W911NF-14-1-0301.
Simulating compressible-incompressible two-phase flows
NASA Astrophysics Data System (ADS)
Denner, Fabian; van Wachem, Berend
2017-11-01
Simulating compressible gas-liquid flows, e.g. air-water flows, presents considerable numerical issues and requires substantial computational resources, particularly because of the stiff equation of state for the liquid and the different Mach number regimes. Treating the liquid phase (low Mach number) as incompressible, yet concurrently considering the gas phase (high Mach number) as compressible, can improve the computational performance of such simulations significantly without sacrificing important physical mechanisms. A pressure-based algorithm for the simulation of two-phase flows is presented, in which a compressible and an incompressible fluid are separated by a sharp interface. The algorithm is based on a coupled finite-volume framework, discretised in conservative form, with a compressive VOF method to represent the interface. The bulk phases are coupled via a novel acoustically-conservative interface discretisation method that retains the acoustic properties of the compressible phase and does not require a Riemann solver. Representative test cases are presented to scrutinize the proposed algorithm, including the reflection of acoustic waves at the compressible-incompressible interface, shock-drop interaction and gas-liquid flows with surface tension. Financial support from the EPSRC (Grant EP/M021556/1) is gratefully acknowledged.
A design of hardware haptic interface for gastrointestinal endoscopy simulation.
Gu, Yunjin; Lee, Doo Yong
2011-01-01
Gastrointestinal endoscopy simulations have been developed to train endoscopic procedures which require hundreds of practices to be competent in the skills. Even though realistic haptic feedback is important to provide realistic sensation to the user, most of previous simulations including commercialized simulation have mainly focused on providing realistic visual feedback. In this paper, we propose a novel design of portable haptic interface, which provides 2DOF force feedback, for the gastrointestinal endoscopy simulation. The haptic interface consists of translational and rotational force feedback mechanism which are completely decoupled, and gripping mechanism for controlling connection between the endoscope and the force feedback mechanism.
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.
Performance of Wireless Unattended Sensor Network in Maritime Applications
2007-06-01
longevity. Crossbow Technologies produces a number of gateways for use with their motes which include the MIB510, the MIB600 and the Stargate . The...MIB510 and MIB600 gateways require interface directly with a PC while he Stargate gateway interfaces remotely using the IEEE 802.11 standard for access...dedicated PC is unfeasible, the Stargate gateway allows remote access using the IEEE 802.11 standard. This can be accomplished via a Personal Computer
Demonstration of a Spoken Dialogue Interface for Planning Activities of a Semi-autonomous Robot
NASA Technical Reports Server (NTRS)
Dowding, John; Frank, Jeremy; Hockey, Beth Ann; Jonsson, Ari; Aist, Gregory
2002-01-01
Planning and scheduling in the face of uncertainty and change pushes the capabilities of both planning and dialogue technologies by requiring complex negotiation to arrive at a workable plan. Planning for use of semi-autonomous robots involves negotiation among multiple participants with competing scientific and engineering goals to co-construct a complex plan. In NASA applications this plan construction is done under severe time pressure so having a dialogue interface to the plan construction tools can aid rapid completion of the process. But, this will put significant demands on spoken dialogue technology, particularly in the areas of dialogue management and generation. The dialogue interface will need to be able to handle the complex dialogue strategies that occur in negotiation dialogues, including hypotheticals and revisions, and the generation component will require an ability to summarize complex plans. This demonstration will describe a work in progress towards building a spoken dialogue interface to the EUROPA planner for the purposes of planning and scheduling the activities of a semi-autonomous robot. A prototype interface has been built for planning the schedule of the Personal Satellite Assistant (PSA), a mobile robot designed for micro-gravity environments that is intended for use on the Space Shuttle and International Space Station. The spoken dialogue interface gives the user the capability to ask for a description of the plan, ask specific questions about the plan, and update or modify the plan. We anticipate that a spoken dialogue interface to the planner will provide a natural augmentation or alternative to the visualization interface, in situations in which the user needs very targeted information about the plan, in situations where natural language can express complex ideas more concisely than GUI actions, or in situations in which a graphical user interface is not appropriate.
Human-computer interface including haptically controlled interactions
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.
Design requirements for ubiquitous computing environments for healthcare professionals.
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.
Human computer interface guide, revision A
NASA Technical Reports Server (NTRS)
1993-01-01
The Human Computer Interface Guide, SSP 30540, is a reference document for the information systems within the Space Station Freedom Program (SSFP). The Human Computer Interface Guide (HCIG) provides guidelines for the design of computer software that affects human performance, specifically, the human-computer interface. This document contains an introduction and subparagraphs on SSFP computer systems, users, and tasks; guidelines for interactions between users and the SSFP computer systems; human factors evaluation and testing of the user interface system; and example specifications. The contents of this document are intended to be consistent with the tasks and products to be prepared by NASA Work Package Centers and SSFP participants as defined in SSP 30000, Space Station Program Definition and Requirements Document. The Human Computer Interface Guide shall be implemented on all new SSFP contractual and internal activities and shall be included in any existing contracts through contract changes. This document is under the control of the Space Station Control Board, and any changes or revisions will be approved by the deputy director.
Laboratory process control using natural language commands from a personal computer
NASA Technical Reports Server (NTRS)
Will, Herbert A.; Mackin, Michael A.
1989-01-01
PC software is described which provides flexible natural language process control capability with an IBM PC or compatible machine. Hardware requirements include the PC, and suitable hardware interfaces to all controlled devices. Software required includes the Microsoft Disk Operating System (MS-DOS) operating system, a PC-based FORTRAN-77 compiler, and user-written device drivers. Instructions for use of the software are given as well as a description of an application of the system.
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.
A process for prototyping onboard payload displays for Space Station Freedom
NASA Technical Reports Server (NTRS)
Moore, Loretta A.
1992-01-01
Significant advances have been made in the area of Human-Computer Interface design. However, there is no well-defined process for going from user interface requirements to user interface design. Developing and designing a clear and consistent user interface for medium to large scale systems is a very challenging and complex task. The task becomes increasingly difficult when there is very little guidance and procedures on how the development process should flow from one stage to the next. Without a specific sequence of development steps each design becomes difficult to repeat, to evaluate, to improve, and to articulate to others. This research contributes a process which identifies the phases of development and products produced as a result of each phase for a rapid prototyping process to be used to develop requirements for the onboard payload displays for Space Station Freedom. The functional components of a dynamic prototyping environment in which this process can be carried out is also discussed. Some of the central questions which are answered here include: How does one go from specifications to an actual prototype? How is a prototype evaluated? How is usability defined and thus measured? How do we use the information from evaluation in redesign of an interface? and Are there techniques which allow for convergence on a design?
A software architecture for automating operations processes
NASA Technical Reports Server (NTRS)
Miller, Kevin J.
1994-01-01
The Operations Engineering Lab (OEL) at JPL has developed a software architecture based on an integrated toolkit approach for simplifying and automating mission operations tasks. The toolkit approach is based on building adaptable, reusable graphical tools that are integrated through a combination of libraries, scripts, and system-level user interface shells. The graphical interface shells are designed to integrate and visually guide a user through the complex steps in an operations process. They provide a user with an integrated system-level picture of an overall process, defining the required inputs and possible output through interactive on-screen graphics. The OEL has developed the software for building these process-oriented graphical user interface (GUI) shells. The OEL Shell development system (OEL Shell) is an extension of JPL's Widget Creation Library (WCL). The OEL Shell system can be used to easily build user interfaces for running complex processes, applications with extensive command-line interfaces, and tool-integration tasks. The interface shells display a logical process flow using arrows and box graphics. They also allow a user to select which output products are desired and which input sources are needed, eliminating the need to know which program and its associated command-line parameters must be executed in each case. The shells have also proved valuable for use as operations training tools because of the OEL Shell hypertext help environment. The OEL toolkit approach is guided by several principles, including the use of ASCII text file interfaces with a multimission format, Perl scripts for mission-specific adaptation code, and programs that include a simple command-line interface for batch mode processing. Projects can adapt the interface shells by simple changes to the resources configuration file. This approach has allowed the development of sophisticated, automated software systems that are easy, cheap, and fast to build. This paper will discuss our toolkit approach and the OEL Shell interface builder in the context of a real operations process example. The paper will discuss the design and implementation of a Ulysses toolkit for generating the mission sequence of events. The Sequence of Events Generation (SEG) system provides an adaptable multimission toolkit for producing a time-ordered listing and timeline display of spacecraft commands, state changes, and required ground activities.
Teleoperation of Robonaut Using Finger Tracking
NASA Technical Reports Server (NTRS)
Champoux, Rachel G.; Luo, Victor
2012-01-01
With the advent of new finger tracking systems, the idea of a more expressive and intuitive user interface is being explored and implemented. One practical application for this new kind of interface is that of teleoperating a robot. For humanoid robots, a finger tracking interface is required due to the level of complexity in a human-like hand, where a joystick isn't accurate. Moreover, for some tasks, using one's own hands allows the user to communicate their intentions more effectively than other input. The purpose of this project was to develop a natural user interface for someone to teleoperate a robot that is elsewhere. Specifically, this was designed to control Robonaut on the international space station to do tasks too dangerous and/or too trivial for human astronauts. This interface was developed by integrating and modifying 3Gear's software, which includes a library of gestures and the ability to track hands. The end result is an interface in which the user can manipulate objects in real time in the user interface. then, the information is relayed to a simulator, the stand in for Robonaut, at a slight delay.
Development of mining guidance and control systems
NASA Technical Reports Server (NTRS)
1979-01-01
New fundamental interface sensor concepts were identified and investigated including tabulation of the physical and performance characteristics of two new interface detector concepts: - natural background radiation and magnetic spin resonance. Studies of guidance and control techniques for the longwall miner identified three basic systems for use in automated/remote controlled longwall mining. The following projects were initiated: system study which will more completely define the longwall guidance and control system design concepts; integration of the various control functions (vertical, yaw, and roll); and hardware technical requirements.
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.
1976-03-01
atmosphere,as well as very fine grid cloud models and cloud probability models. Some of the new requirements that will be supported with this system are a...including the Advanced Prediction Model for the global atmosphere, as well as very fine grid cloud models and cloud proba- bility models. Some of the new...with the mapping and gridding function (imput and output)? Should the capability exist to interface raw ungridded data with the SID interface
IAC - INTEGRATED ANALYSIS CAPABILITY
NASA Technical Reports Server (NTRS)
Frisch, H. P.
1994-01-01
The objective of the Integrated Analysis Capability (IAC) system is to provide a highly effective, interactive analysis tool for the integrated design of large structures. With the goal of supporting the unique needs of engineering analysis groups concerned with interdisciplinary problems, IAC was developed to interface programs from the fields of structures, thermodynamics, controls, and system dynamics with an executive system and database to yield a highly efficient multi-disciplinary system. Special attention is given to user requirements such as data handling and on-line assistance with operational features, and the ability to add new modules of the user's choice at a future date. IAC contains an executive system, a data base, general utilities, interfaces to various engineering programs, and a framework for building interfaces to other programs. IAC has shown itself to be effective in automatic data transfer among analysis programs. IAC 2.5, designed to be compatible as far as possible with Level 1.5, contains a major upgrade in executive and database management system capabilities, and includes interfaces to enable thermal, structures, optics, and control interaction dynamics analysis. The IAC system architecture is modular in design. 1) The executive module contains an input command processor, an extensive data management system, and driver code to execute the application modules. 2) Technical modules provide standalone computational capability as well as support for various solution paths or coupled analyses. 3) Graphics and model generation interfaces are supplied for building and viewing models. Advanced graphics capabilities are provided within particular analysis modules such as INCA and NASTRAN. 4) Interface modules provide for the required data flow between IAC and other modules. 5) User modules can be arbitrary executable programs or JCL procedures with no pre-defined relationship to IAC. 6) Special purpose modules are included, such as MIMIC (Model Integration via Mesh Interpolation Coefficients), which transforms field values from one model to another; LINK, which simplifies incorporation of user specific modules into IAC modules; and DATAPAC, the National Bureau of Standards statistical analysis package. The IAC database contains structured files which provide a common basis for communication between modules and the executive system, and can contain unstructured files such as NASTRAN checkpoint files, DISCOS plot files, object code, etc. The user can define groups of data and relations between them. A full data manipulation and query system operates with the database. The current interface modules comprise five groups: 1) Structural analysis - IAC contains a NASTRAN interface for standalone analysis or certain structural/control/thermal combinations. IAC provides enhanced structural capabilities for normal modes and static deformation analysis via special DMAP sequences. IAC 2.5 contains several specialized interfaces from NASTRAN in support of multidisciplinary analysis. 2) Thermal analysis - IAC supports finite element and finite difference techniques for steady state or transient analysis. There are interfaces for the NASTRAN thermal analyzer, SINDA/SINFLO, and TRASYS II. FEMNET, which converts finite element structural analysis models to finite difference thermal analysis models, is also interfaced with the IAC database. 3) System dynamics - The DISCOS simulation program which allows for either nonlinear time domain analysis or linear frequency domain analysis, is fully interfaced to the IAC database management capability. 4) Control analysis - Interfaces for the ORACLS, SAMSAN, NBOD2, and INCA programs allow a wide range of control system analyses and synthesis techniques. Level 2.5 includes EIGEN, which provides tools for large order system eigenanalysis, and BOPACE, which allows for geometric capabilities and finite element analysis with nonlinear material. Also included in IAC level 2.5 is SAMSAN 3.1, an engineering analysis program which contains a general purpose library of over 600 subroutines for numerical analysis. 5) Graphics - The graphics package IPLOT is included in IAC. IPLOT generates vector displays of tabular data in the form of curves, charts, correlation tables, etc. Either DI3000 or PLOT-10 graphics software is required for full graphic capability. In addition to these analysis tools, IAC 2.5 contains an IGES interface which allows the user to read arbitrary IGES files into an IAC database and to edit and output new IGES files. IAC is available by license for a period of 10 years to approved U.S. licensees. The licensed program product includes one set of supporting documentation. Additional copies may be purchased separately. IAC is written in FORTRAN 77 and has been implemented on a DEC VAX series computer operating under VMS. IAC can be executed by multiple concurrent users in batch or interactive mode. The program is structured to allow users to easily delete those program capabilities and "how to" examples they do not want in order to reduce the size of the package. The basic central memory requirement for IAC is approximately 750KB. The following programs are also available from COSMIC as separate packages: NASTRAN, SINDA/SINFLO, TRASYS II, DISCOS, ORACLS, SAMSAN, NBOD2, and INCA. The development of level 2.5 of IAC was completed in 1989.
Training Manual for Elements of Interface Definition and Control
NASA Technical Reports Server (NTRS)
Lalli, Vincent R. (Editor); Kastner, Robert E. (Editor); Hartt, Henry N. (Editor)
1997-01-01
The primary thrust of this manual is to ensure that the format and information needed to control interfaces between equipment are clear and understandable. The emphasis is on controlling the engineering design of the interface and not on the functional performance requirements of the system or the internal workings of the interfacing equipment. Interface control should take place, with rare exception, at the interfacing elements and no further. There are two essential sections of the manual. Chapter 2, Principles of Interface Control, discusses how interfaces are defined. It describes different types of interfaces to be considered and recommends a format for the documentation necessary for adequate interface control. Chapter 3, The Process: Through the Design Phases, provides tailored guidance for interface definition and control. This manual can be used to improve planned or existing interface control processes during system design and development. It can also be used to refresh and update the corporate knowledge base. The information presented herein will reduce the amount of paper and data required in interface definition and control processes by as much as 50 percent and will shorten the time required to prepare an interface control document. It also highlights the essential technical parameters that ensure that flight subsystems will indeed fit together and function as intended after assembly and checkout.
Space transfer vehicle concepts and requirements study. Volume 2, book 3: STV system interfaces
NASA Technical Reports Server (NTRS)
Weber, Gary A.
1991-01-01
This report presents the results of systems analyses and conceptual design of space transfer vehicles (STV). The missions examined included piloted and unpiloted lunar outpost support and spacecraft servicing, and unpiloted payload delivery to various earth and solar orbits. The study goal was to examine the mission requirements and provide a decision data base for future programmatic development plans. The final lunar transfer vehicles provided a wide range of capabilities and interface requirements while maintaining a constant payload mission model. Launch vehicle and space station sensitivity was examined, with the final vehicles as point design covering the range of possible options. Development programs were defined and technology readiness levels for different options were determined. Volume 1 presents the executive summary, volume 2 provides the study results, and volume 3 the cost and WBS data.
A Wireless Biomedical Signal Interface System-on-Chip for Body Sensor Networks.
Lei Wang; Guang-Zhong Yang; Jin Huang; Jinyong Zhang; Li Yu; Zedong Nie; Cumming, D R S
2010-04-01
Recent years have seen the rapid development of biosensor technology, system-on-chip design, wireless technology. and ubiquitous computing. When assembled into an autonomous body sensor network (BSN), the technologies become powerful tools in well-being monitoring, medical diagnostics, and personal connectivity. In this paper, we describe the first demonstration of a fully customized mixed-signal silicon chip that has most of the attributes required for use in a wearable or implantable BSN. Our intellectual-property blocks include low-power analog sensor interface for temperature and pH, a data multiplexing and conversion module, a digital platform based around an 8-b microcontroller, data encoding for spread-spectrum wireless transmission, and a RF section requiring very few off-chip components. The chip has been fully evaluated and tested by connection to external sensors, and it satisfied typical system requirements.
Orbit targeting specialist function: Level C formulation requirements
NASA Technical Reports Server (NTRS)
Dupont, A.; Mcadoo, S.; Jones, H.; Jones, A. K.; Pearson, D.
1978-01-01
A definition of the level C requirements for onboard maneuver targeting software is provided. Included are revisions of the level C software requirements delineated in JSC IN 78-FM-27, Proximity Operations Software; Level C Requirements, dated May 1978. The software supports the terminal phase midcourse (TPM) maneuver, braking and close-in operations as well as supporting computation of the rendezvous corrective combination maneuver (NCC), and the terminal phase initiation (TPI). Specific formulation is contained here for the orbit targeting specialist function including the processing logic, linkage, and data base definitions for all modules. The crew interface with the software is through the keyboard and the ORBIT-TGT display.
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.
NASA Technical Reports Server (NTRS)
Cork, M. J.; Barnett, P. M.; Shaffer, J., Jr.; Doran, B. J.
1979-01-01
Earth escape mission requirements on Solar Electric Propulsion System (SEPS), and the interface definition and planned integration between SEPS, user spacecraft, and other elements of the STS. Emphasis is placed on the Comet rendezvous mission, scheduled to be the first SEPS user. Interactive SEPS interface characteristics with spacecraft and mission, as well as the multiple organizations and inter-related development schedules required to integrate the SEPS with spacecraft and STS, require early attention to definition of interfaces in order to assure a successful path to the first SEPS launch in July 1985
Multiple IMU system hardware interface design, volume 2
NASA Technical Reports Server (NTRS)
Landey, M.; Brown, D.
1975-01-01
The design of each system component is described. Emphasis is placed on functional requirements unique in this system, including data bus communication, data bus transmitters and receivers, and ternary-to-binary torquing decision logic. Mechanization drawings are presented.
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.
Biomedical and Human Factors Requirements for a Manned Earth-Orbiting Station
NASA Technical Reports Server (NTRS)
Reynolds, J. B.
1963-01-01
The study reported here has presented a measurement data pool for the determination of biomedical and behavioral effects of long-term exposure to weightlessness. This includes measures, techniques, equipment, and requirements in terms of weight, power, volume, time, crew activities, subsystem interfaces and experimental programs and designs, and confidence ratings for their effectiveness for determining weightlessness effects.
NASA Technical Reports Server (NTRS)
1972-01-01
An evaluation of the compatibility of the space shuttle and Agena rocket vehicle was conducted. The Agena space tug configuration design is described in terms of the total vehicle system as well as the individual subsystems and major assemblies and components. The complete interface between the Agena space tug and the space shuttle orbiter is defined for in-flight and ground operations. The derivation and design of an evolutionary stage is also presented. This vehicle conforms to the same guidelines and interface requirements as the Agena space tug. Performance data developed for both vehicles for each of the three study baseline missions are included.
Design criteria for a PC-based common user interface to remote information systems
NASA Technical Reports Server (NTRS)
Dominick, Wayne D. (Editor); Hall, Philip P.
1984-01-01
A set of design criteria are presented which will allow the implementation of an interface to multiple remote information systems on a microcomputer. The focus of the design description is on providing the user with the functionality required to retrieve, store and manipulate data residing in remote information systems through the utilization of a standardized interface system. The intent is to spare the user from learning the details of retrieval from specific systems while retaining the full capabilities of each system. The system design includes multi-level capabilities to enhance usability by a wide range of users and utilizes microcomputer graphics capabilities where applicable. A data collection subsystem for evaluation purposes is also described.
Zhang, Yi; Monsen, Karen A; Adam, Terrence J; Pieczkiewicz, David S; Daman, Megan; Melton, Genevieve B
2011-01-01
Time and motion (T&M) studies provide an objective method to measure the expenditure of time by clinicians. While some instruments for T&M studies have been designed to evaluate health information technology (HIT), these instruments have not been designed for nursing workflow. We took an existing open source HIT T&M study application designed to evaluate physicians in the ambulatory setting and rationally adapted it through empiric observations to record nursing activities in the inpatient setting and linked this instrument to an existing interface terminology, the Omaha System. Nursing activities involved several dimensions and could include multiple activities occurring simultaneously, requiring significant instrument redesign. 94% of the activities from the study instrument mapped adequately to the Omaha System. T&M study instruments require customization in design optimize them for different environments, such as inpatient nursing, to enable optimal data collection. Interface terminologies show promise as a framework for recording and analyzing T&M study data. PMID:22195228
12-bit 32 channel 500 MS/s low-latency ADC for particle accelerators real-time control
NASA Astrophysics Data System (ADS)
Karnitski, Anton; Baranauskas, Dalius; Zelenin, Denis; Baranauskas, Gytis; Zhankevich, Alexander; Gill, Chris
2017-09-01
Particle beam control systems require real-time low latency digital feedback with high linearity and dynamic range. Densely packed electronic systems employ high performance multichannel digitizers causing excessive heat dissipation. Therefore, low power dissipation is another critical requirement for these digitizers. A described 12-bit 500 MS/s ADC employs a sub-ranging architecture based on a merged sample & hold circuit, a residue C-DAC and a shared 6-bit flash core ADC. The core ADC provides a sequential coarse and fine digitization featuring a latency of two clock cycles. The ADC is implemented in a 28 nm CMOS process and consumes 4 mW of power per channel from a 0.9 V supply (interfacing and peripheral circuits are excluded). Reduced power consumption and small on-chip area permits the implementation of 32 ADC channels on a 10.7 mm2 chip. The ADC includes a JESD204B standard compliant output data interface operated at the 7.5 Gbps/ch rate. To minimize the data interface related time latency, a special feature permitting to bypass the JESD204B interface is built in. DoE Phase I Award Number: DE-SC0017213.
Geospatial interface and model for predicting potential seagrass habitat
Restoration of ecosystem services provided by seagrass habitats in estuaries requires a clear understanding of the modes of action of multiple interacting stressors including nutrients, climate change, coastal land-use change, and habitat modification. We have developed a geos...
Viking lander camera radiometry calibration report, volume 2
NASA Technical Reports Server (NTRS)
Wolf, M. R.; Atwood, D. L.; Morrill, M. E.
1977-01-01
The requirements the performance validation, and interfaces for the RADCAM program, to convert Viking lander camera image data to radiometric units were established. A proposed algorithm is described, and an appendix summarizing the planned reduction of camera test data was included.
ERIC Educational Resources Information Center
Terry, John
1987-01-01
Discusses the feasibility of using fermenters in secondary school laboratories. Includes discussions of equipment, safety, and computer interfacing. Describes how a simple fermenter could be used to simulate large-scale processes. Concludes that, although teachers and technicians will require additional training, the prospects for biotechnology in…
i-PI: A Python interface for ab initio path integral molecular dynamics simulations
NASA Astrophysics Data System (ADS)
Ceriotti, Michele; More, Joshua; Manolopoulos, David E.
2014-03-01
Recent developments in path integral methodology have significantly reduced the computational expense of including quantum mechanical effects in the nuclear motion in ab initio molecular dynamics simulations. However, the implementation of these developments requires a considerable programming effort, which has hindered their adoption. Here we describe i-PI, an interface written in Python that has been designed to minimise the effort required to bring state-of-the-art path integral techniques to an electronic structure program. While it is best suited to first principles calculations and path integral molecular dynamics, i-PI can also be used to perform classical molecular dynamics simulations, and can just as easily be interfaced with an empirical forcefield code. To give just one example of the many potential applications of the interface, we use it in conjunction with the CP2K electronic structure package to showcase the importance of nuclear quantum effects in high-pressure water. Catalogue identifier: AERN_v1_0 Program summary URL: http://cpc.cs.qub.ac.uk/summaries/AERN_v1_0.html Program obtainable from: CPC Program Library, Queen’s University, Belfast, N. Ireland Licensing provisions: GNU General Public License, version 3 No. of lines in distributed program, including test data, etc.: 138626 No. of bytes in distributed program, including test data, etc.: 3128618 Distribution format: tar.gz Programming language: Python. Computer: Multiple architectures. Operating system: Linux, Mac OSX, Windows. RAM: Less than 256 Mb Classification: 7.7. External routines: NumPy Nature of problem: Bringing the latest developments in the modelling of nuclear quantum effects with path integral molecular dynamics to ab initio electronic structure programs with minimal implementational effort. Solution method: State-of-the-art path integral molecular dynamics techniques are implemented in a Python interface. Any electronic structure code can be patched to receive the atomic coordinates from the Python interface, and to return the forces and energy that are used to integrate the equations of motion. Restrictions: This code only deals with distinguishable particles. It does not include fermonic or bosonic exchanges between equivalent nuclei, which can become important at very low temperatures. Running time: Depends dramatically on the nature of the simulation being performed. A few minutes for short tests with empirical force fields, up to several weeks for production calculations with ab initio forces. The examples provided with the code run in less than an hour.
Space tug/shuttle interface compatibility study. Volume 1: Executive summary
NASA Technical Reports Server (NTRS)
1975-01-01
Shuttle interfaces required for space tug accommodation are primarily involved with supporting and servicing the tug during launch countdown, flight, and postlanding; deploying and retrieving the tug on orbit; and maintaining control over the tug when it is in or near the orbiter. Each of these interface areas was investigated to determine the best physical and operational method of accomplishing the required functions, with an overriding goal of establishing simple and flexible orbiter interface requirements suitable for tug, tug payloads, IUS and other cargo. It is concluded the orbiter payload accommodations and the MSFC baseline tug are generally interface compatible. Specific minor changes to tug and orbiter interfaces were identified to provide full compatibility. A system concept for supporting and deploying tug from orbiter is described.
Space Station Furnace Facility Management Information System (SSFF-MIS) Development
NASA Technical Reports Server (NTRS)
Meade, Robert M.
1996-01-01
This report summarizes the chronology, results, and lessons learned from the development of the SSFF-MIS. This system has been nearly two years in development and has yielded some valuable insights into specialized MIS development. General: In December of 1994, the Camber Corporation and Science Applications International Corporation (SAIC) were contracted to design, develop, and implement a MIS for Marshall Space Flight Center's Space Station Furnace Facility Project. The system was to be accessible from both EBM-Compatible PC and Macintosh platforms. The system was required to contain data manually entered into the MIS as well as data imported from other MSFC sources. Electronic interfaces were established for each data source and retrieval was to be performed at prescribed time intervals. The SOW requirement that predominantly drove the development software selection was the dual-platform (IBM-PC and Macintosh) requirement. The requirement that the system would be maintained by Government personnel influenced the selection of Commercial Off-the-shelf software because of its inherent stability and readily available documentation and support. Microsoft FoxPro Professional 2.6 for Windows and Macintosh was selected as the development tool. This is a software development tool that has been in use for many years. It is stable and powerful. Microsoft has since released the replacement for this product, Microsoft Visual FoxPro, but at the time of this development, it was only available on the Windows platform. The initial contract included included the requirement for capabilities relating to the Work- and Organizational Breakdown Structures, cost (plan and actuals), workforce (plan and actuals), critical path scheduling, trend analysis, procurements and contracts, interface to manufacturing, Safety and Mission Assurance, risk analysis, and technical performance indicators. It also required full documentation of the system and training of users. During the course of the contract, the requirements for Safety and Mission Assurance interface, risk analysis, and technical performance indicators were deleted. Additional capabilities were added as reflected in the Contract Chronology below. Modification 4 added the requirement for Support Contractor manpower data, the ability to manually input data not imported from non-nal sources, a general 'health' indicator screen, and remote usage. Mod 6 included the ability to change the level of planning of Civil Service Manpower at any time and the ability to manually enter Op Codes in the manufacturing data where such codes were not provided by the EMPACS database. Modification 9 included a number of changes to report contents and formats. Modification 11 required the preparation of a detailed System Design Document.
Screening mechanisms at polar oxide heterointerfaces
Hong, Seungbum; Nakhmanson, Serge M.; Fong, Dillon D.
2016-06-16
The interfaces of polar oxide heterostructures can display electronic properties unique from the oxides they border, as they require screening from either internal or external sources of charge. The screening mechanism depends on a variety of factors, including the band structure at the interface, the presence of point defects or adsorbates, whether or not the oxide is ferroelectric, and whether or not an external field is applied. In this review, we discuss both theoretical and experimental aspects of different screening mechanisms, giving special emphasis to ways in which the mechanism can be altered to provide novel or tunable functionalities. Wemore » begin with a theoretical introduction to the problem and highlight recent progress in understanding the impact of point defects on polar interfaces. Different case studies are then discussed, for both the high thickness regime, where interfaces must be screened and each interface can be considered separately, and the low thickness regime, where the degree and nature of screening can be manipulated and the interfaces are close enough to interact. As a result, we end with a brief outlook toward new developments in this rapidly progressing field.« less
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.
Adsorption of Small Molecules at Water--Hexane and Water--Membrane Interfaces
NASA Astrophysics Data System (ADS)
Wilson, Michael A.
1996-03-01
The interaction of solutes with aqueous interfaces plays a significant role in a variety of physical processes, including general anesthesia and atmospheric chemistry. We present molecular dynamics results for the transfer of several small solutes across water liquid--vapor, water--hexane and water--GMO bilayer membrane interfaces. (A. Pohorille and M. A. Wilson, J. Chem. Phys. (in press, 1995).)^, (A. Pohorille, P. CIeplak, and M. A. Wilson, Chem. Phys. (in press, 1995).) The free energies of transferring small polar molecules across the interface exhibit fairly deep minima while those of nonpolar molecules do not. This is due to a balance between nonelectrostatic contributions --- primarily the work required to create a cavity large enough to accommodate the solute --- and the solute--solvent electrostatic interactions.^1 The surface excess of solute is calculated and compared with experimental results from the Gibbs adsorption isotherm. The interfacial solubilities correlate with measured anesthetic potencies of these compounds, implying that the binding sites for anesthetics are located near the water--membrane interface.
Epitaxial growth of silicon for layer transfer
Teplin, Charles; Branz, Howard M
2015-03-24
Methods of preparing a thin crystalline silicon film for transfer and devices utilizing a transferred crystalline silicon film are disclosed. The methods include preparing a silicon growth substrate which has an interface defining substance associated with an exterior surface. The methods further include depositing an epitaxial layer of silicon on the silicon growth substrate at the surface and separating the epitaxial layer from the substrate substantially along the plane or other surface defined by the interface defining substance. The epitaxial layer may be utilized as a thin film of crystalline silicon in any type of semiconductor device which requires a crystalline silicon layer. In use, the epitaxial transfer layer may be associated with a secondary substrate.
Geostationary platform systems concepts definition study. Volume 2: Technical, book 3
NASA Technical Reports Server (NTRS)
1980-01-01
The supporting research and technology, and space demonstrations required to support the 1990s operational geostationary platforms are identified. Also the requirements on and interfaces with the Space Transportation System hardware elements supporting the geostationary platform program, including the shuttle, orbital transfer vehicles, teleoperator, etc., are investigated to provide integrated support requirements. Finally, a preliminary evaluation of the practicability and capabilities of an experimental platform from the standpoint of technology, schedule, and cost is given.
Subsea approach to work systems development
NASA Technical Reports Server (NTRS)
Gernhardt, M. L.; Frisbie, F. R.; Brown, C. E.
1988-01-01
Self-contained undersea working environments with applications to space station EVA environments are discussed. Physiological limitations include decompression, inert gas narcosis, high-pressure nervous system, gas toxicity, and thermal limitations. Work task requirements include drilling support, construction, inspection, and repair. Work systems include hyperbaric diving, atmospheric work systems, tele-operated work systems, and hybrid systems. Each type of work system is outlined in terms of work capabilities, special interface requirements, and limitations. Various operational philosophies are discussed. The evolution of work systems in the subsea industry has been the result of direct operational experience in a competitive market.
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).
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.
Transparent Information Systems through Gateways, Front Ends, Intermediaries, and Interfaces.
ERIC Educational Resources Information Center
Williams, Martha E.
1986-01-01
Provides overview of design requirements for transparent information retrieval (implies that user sees through complexity of retrieval activities sequence). Highlights include need for transparent systems; history of transparent retrieval research; information retrieval functions (automated converters, routers, selectors, evaluators/analyzers);…
Proceedings of the 3rd Annual Conference on Aerospace Computational Control, volume 1
NASA Technical Reports Server (NTRS)
Bernard, Douglas E. (Editor); Man, Guy K. (Editor)
1989-01-01
Conference topics included definition of tool requirements, advanced multibody component representation descriptions, model reduction, parallel computation, real time simulation, control design and analysis software, user interface issues, testing and verification, and applications to spacecraft, robotics, and aircraft.
Selecting Appropriate Functionality and Technologies for EPSS.
ERIC Educational Resources Information Center
McGraw, Karen L.
1995-01-01
Presents background information that describes the major components of an embedded performance support system, compares levels of functionality, and discusses some of the required technologies. Highlights include the human-computer interface; online help; advisors; training and tutoring; hypermedia; and artificial intelligence techniques. (LRW)
On-board multispectral classification study. Volume 2: Supplementary tasks. [adaptive control
NASA Technical Reports Server (NTRS)
Ewalt, D.
1979-01-01
The operational tasks of the onboard multispectral classification study were defined. These tasks include: sensing characteristics for future space applications; information adaptive systems architectural approaches; data set selection criteria; and onboard functional requirements for interfacing with global positioning satellites.
Forsell, M; Häggström, M; Johansson, O; Sjögren, P
2008-11-08
To develop a personal digital assistant (PDA) application for oral health assessment fieldwork, including back-office and database systems (MobilDent). System design, construction and implementation of PDA, back-office and database systems. System requirements for MobilDent were collected, analysed and translated into system functions. User interfaces were implemented and system architecture was outlined. MobilDent was based on a platform with. NET (Microsoft) components, using an SQL Server 2005 (Microsoft) for data storage with Windows Mobile (Microsoft) operating system. The PDA devices were Dell Axim. System functions and user interfaces were specified for MobilDent. User interfaces for PDA, back-office and database systems were based on. NET programming. The PDA user interface was based on Windows suitable to a PDA display, whereas the back-office interface was designed for a normal-sized computer screen. A synchronisation module (MS Active Sync, Microsoft) was used to enable download of field data from PDA to the database. MobilDent is a feasible application for oral health assessment fieldwork, and the oral health assessment database may prove a valuable source for care planning, educational and research purposes. Further development of the MobilDent system will include wireless connectivity with download-on-demand technology.
Color group selection for computer interfaces
NASA Astrophysics Data System (ADS)
Lyons, Paul; Moretti, Giovanni; Wilson, Mark
2000-06-01
We describe a low-impact method for coloring interfaces harmoniously. The method uses a model that characterizes the overall image including the need for distinguishability between interface components. The degree of visual distinction between one component and other components, and its color strength (which increases with its importance and decreases with its size and longevity), are used in generating a rigid ball-and-stick 'color molecule,' which represents the color relationships between the interface components. The shape of the color molecule is chosen to conform to standard principles of color harmony (like colors harmonize, complementary colors harmonize, cycles in the color space harmonize, and so on). The color molecule's shape is fixed, but its position and orientation within the perceptually uniform color solid are not. The end user of the application chooses a new color scheme for the complete interface by repositioning the molecule within the color space. The molecule's shape and rigidity, and the space's perceptual uniformity, ensures the distinguishability and color harmony of the components are maintained. The system produces a selection of color schemes which often include subtle 'nameless' colors that people rarely choose using conventional color controls, but which blend smoothly into a harmonious color scheme. A new set of equally harmonious color schemes only requires repositioning the color molecule within the space.
Glass Solder Approach for Robust, Low-Loss, Fiber-to-Waveguide Coupling
NASA Technical Reports Server (NTRS)
McNeil, Shirley; Battle, Philip; Hawthorne, Todd; Lower, John; Wiley, Robert; Clark, Brett
2012-01-01
The key advantages of this approach include the fact that the index of interface glass (such as Pb glass n = 1.66) greatly reduces Fresnel losses at the fiber-to-waveguide interface, resulting in lower optical losses. A contiguous structure cannot be misaligned and readily lends itself for use on aircraft or space operation. The epoxy-free, fiber-to-waveguide interface provides an optically pure, sealed interface for low-loss, highpower coupling. Proof of concept of this approach has included successful attachment of the low-melting-temperature glass to the x-y plane of the crystal, successful attachment of the low-meltingtemperature glass to the end face of a standard SMF (single-mode fiber), and successful attachment of a wetted lowmelting- temperature glass SMF to the end face of a KTP crystal. There are many photonic components on the market whose performance and robustness could benefit from this coupling approach once fully developed. It can be used in a variety of fibercoupled waveguide-based components, such as frequency conversion modules, and amplitude and phase modulators. A robust, epoxy-free, contiguous optical interface lends itself to components that require low-loss, high-optical-power handling capability, and good performance in adverse environments such as flight or space operation.
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...
NASA Technical Reports Server (NTRS)
1993-01-01
The information required by a programmer using the Minimum Hamiltonian AScent Trajectory Evaluation (MASTRE) Program is provided. This document enables the programmer to either modify the program or convert the program to computers other than the VAX computer. Documentation for each subroutine or function based on providing the definitions of the variables and a source listing are included. Questions concerning the equations, techniques, or input requirements should be answered by either the Engineering or User's manuals. Three appendices are also included which provide a listing of the Root-Sum-Square (RSS) program, a listing of subroutine names and definitions used in the MASTRE User Friendly Interface Program, and listing of the subroutine names and definitions used in the Mass Properties Program. The RSS Program is used to aid in the performance of dispersion analyses. The RSS program reads a file generated by the MASTRE Program, calculates dispersion parameters, and generates output tables and output plot files. UFI Program provides a screen user interface to aid the user in providing input to the model. The Mass Properties Program defines the mass properties data for the MASTRE program through the use of user interface software.
NASA Astrophysics Data System (ADS)
Zhao, Xiaosong; Zhao, Xiaofeng; Yin, Liang
2018-03-01
This paper presents a interface circuit for nano-polysilicon thin films pressure sensor. The interface circuit includes consist of instrument amplifier and Analog-to-Digital converter (ADC). The instrumentation amplifier with a high common mode rejection ratio (CMRR) is implemented by three stages current feedback structure. At the same time, in order to satisfy the high precision requirements of pressure sensor measure system, the 1/f noise corner of 26.5 mHz can be achieved through chopping technology at a noise density of 38.2 nV/sqrt(Hz).Ripple introduced by chopping technology adopt continuous ripple reduce circuit (RRL), which achieves the output ripple level is lower than noise. The ADC achieves 16 bits significant digit by adopting sigma-delta modulator with fourth-order single-bit structure and digital decimation filter, and finally achieves high precision integrated pressure sensor interface circuit.
Software systems for modeling articulated figures
NASA Technical Reports Server (NTRS)
Phillips, Cary B.
1989-01-01
Research in computer animation and simulation of human task performance requires sophisticated geometric modeling and user interface tools. The software for a research environment should present the programmer with a powerful but flexible substrate of facilities for displaying and manipulating geometric objects, yet insure that future tools have a consistent and friendly user interface. Jack is a system which provides a flexible and extensible programmer and user interface for displaying and manipulating complex geometric figures, particularly human figures in a 3D working environment. It is a basic software framework for high-performance Silicon Graphics IRIS workstations for modeling and manipulating geometric objects in a general but powerful way. It provides a consistent and user-friendly interface across various applications in computer animation and simulation of human task performance. Currently, Jack provides input and control for applications including lighting specification and image rendering, anthropometric modeling, figure positioning, inverse kinematics, dynamic simulation, and keyframe animation.
NASA Technical Reports Server (NTRS)
Averill, Ronald C.
2002-01-01
An effective and robust interface element technology able to connect independently modeled finite element subdomains has been developed. This method is based on the use of penalty constraints and allows coupling of finite element models whose nodes do not coincide along their common interface. Additionally, the present formulation leads to a computational approach that is very efficient and completely compatible with existing commercial software. A significant effort has been directed toward identifying those model characteristics (element geometric properties, material properties, and loads) that most strongly affect the required penalty parameter, and subsequently to developing simple 'formulae' for automatically calculating the proper penalty parameter for each interface constraint. This task is especially critical in composite materials and structures, where adjacent sub-regions may be composed of significantly different materials or laminates. This approach has been validated by investigating a variety of two-dimensional problems, including composite laminates.
Waldbaur, Ansgar; Kittelmann, Jörg; Radtke, Carsten P; Hubbuch, Jürgen; Rapp, Bastian E
2013-06-21
We describe a generic microfluidic interface design that allows the connection of microfluidic chips to established industrial liquid handling stations (LHS). A molding tool has been designed that allows fabrication of low-cost disposable polydimethylsiloxane (PDMS) chips with interfaces that provide convenient and reversible connection of the microfluidic chip to industrial LHS. The concept allows complete freedom of design for the microfluidic chip itself. In this setup all peripheral fluidic components (such as valves and pumps) usually required for microfluidic experiments are provided by the LHS. Experiments (including readout) can be carried out fully automated using the hardware and software provided by LHS manufacturer. Our approach uses a chip interface that is compatible with widely used and industrially established LHS which is a significant advancement towards near-industrial experimental design in microfluidics and will greatly facilitate the acceptance and translation of microfluidics technology in industry.
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.
A single-scattering correction for the seismo-acoustic parabolic equation.
Collins, Michael D
2012-04-01
An efficient single-scattering correction that does not require iterations is derived and tested for the seismo-acoustic parabolic equation. The approach is applicable to problems involving gradual range dependence in a waveguide with fluid and solid layers, including the key case of a sloping fluid-solid interface. The single-scattering correction is asymptotically equivalent to a special case of a single-scattering correction for problems that only have solid layers [Küsel et al., J. Acoust. Soc. Am. 121, 808-813 (2007)]. The single-scattering correction has a simple interpretation (conservation of interface conditions in an average sense) that facilitated its generalization to problems involving fluid layers. Promising results are obtained for problems in which the ocean bottom interface has a small slope.
Silvey, Garry M.; Lobach, David F.; Macri, Jennifer M.; Hunt, Megan; Kacmaz, Roje O.; Lee, Paul P.
2006-01-01
Collecting clinical data directly from clinicians is a challenge. Many standard development environments designed to expedite the creation of user interfaces for electronic healthcare applications do not provide acceptable components for satisfying the requirements for collecting and displaying clinical data at the point of care on the tablet computer. Through an iterative design and testing approach using think-aloud sessions in the eye care setting, we were able to identify and resolve several user interface issues. Issues that we discovered and subsequently resolved included checkboxes that were too small to be selectable with a stylus, radio buttons that could not be unselected, and font sizes that were too small to be read at arm’s length. PMID:17238715
An optical/digital processor - Hardware and applications
NASA Technical Reports Server (NTRS)
Casasent, D.; Sterling, W. M.
1975-01-01
A real-time two-dimensional hybrid processor consisting of a coherent optical system, an optical/digital interface, and a PDP-11/15 control minicomputer is described. The input electrical-to-optical transducer is an electron-beam addressed potassium dideuterium phosphate (KD2PO4) light valve. The requirements and hardware for the output optical-to-digital interface, which is constructed from modular computer building blocks, are presented. Initial experimental results demonstrating the operation of this hybrid processor in phased-array radar data processing, synthetic-aperture image correlation, and text correlation are included. The applications chosen emphasize the role of the interface in the analysis of data from an optical processor and possible extensions to the digital feedback control of an optical processor.
NASA Astrophysics Data System (ADS)
Henry de Frahan, Marc T.; Varadan, Sreenivas; Johnsen, Eric
2015-01-01
Although the Discontinuous Galerkin (DG) method has seen widespread use for compressible flow problems in a single fluid with constant material properties, it has yet to be implemented in a consistent fashion for compressible multiphase flows with shocks and interfaces. Specifically, it is challenging to design a scheme that meets the following requirements: conservation, high-order accuracy in smooth regions and non-oscillatory behavior at discontinuities (in particular, material interfaces). Following the interface-capturing approach of Abgrall [1], we model flows of multiple fluid components or phases using a single equation of state with variable material properties; discontinuities in these properties correspond to interfaces. To represent compressible phenomena in solids, liquids, and gases, we present our analysis for equations of state belonging to the Mie-Grüneisen family. Within the DG framework, we propose a conservative, high-order accurate, and non-oscillatory limiting procedure, verified with simple multifluid and multiphase problems. We show analytically that two key elements are required to prevent spurious pressure oscillations at interfaces and maintain conservation: (i) the transport equation(s) describing the material properties must be solved in a non-conservative weak form, and (ii) the suitable variables must be limited (density, momentum, pressure, and appropriate properties entering the equation of state), coupled with a consistent reconstruction of the energy. Further, we introduce a physics-based discontinuity sensor to apply limiting in a solution-adaptive fashion. We verify this approach with one- and two-dimensional problems with shocks and interfaces, including high pressure and density ratios, for fluids obeying different equations of state to illustrate the robustness and versatility of the method. The algorithm is implemented on parallel graphics processing units (GPU) to achieve high speedup.
2013-12-01
Economy Trials, Vertical Takeoff Unmanned Aerial Vehicle Dynamic Interface Testing, Advanced Stabilized Glide Scope Indicators Testing, Surface Warfare...to include 1) DISR mandated GIG IT standards and profiles identified in the TV-1, 2) DISR The system must fully support execution of all...requirements for Net- Centric military operations to include 1) DISR mandated GIG IT standards and profiles identified in the TV-1, 2
19 CFR 122.49d - Passenger Name Record (PNR) information.
Code of Federal Regulations, 2011 CFR
2011-04-01
.../departure control systems correctly interface with the U.S. Customs Data Center, Customs Headquarters, as...) Required carrier system interface with Customs Data Center to facilitate Customs retrieval of requested PNR data—(1) Carrier requirements for interface with Customs. Within the time specified in paragraph (c)(2...
Manned geosynchronous mission requirements and systems analysis study. Volume 1: Executive summary
NASA Technical Reports Server (NTRS)
Boyland, R. E.; Sherman, S. W.; Morfin, H. W.
1979-01-01
The crew capsule of the MOTV was studied with emphasis on crew accommodations, crew capsule functional requirements, subsystem interface definition between crew module and propulsion module, and man rating requirements. Competing mission modes were studied covering a wide range of propulsion concepts. These included one stage, one and one half stage, and two stage concepts using either the standard STS or an augmented STS. Several deorbit concepts were considered, including all propulsive modes, direct re-entry, and aeromaneuvering skip in skip out in the upper reaches of Earth's atmosphere. A five year plan covering costs, schedules, and critical technology issues is discussed.
A versatile program for the calculation of linear accelerator room shielding.
Hassan, Zeinab El-Taher; Farag, Nehad M; Elshemey, Wael M
2018-03-22
This work aims at designing a computer program to calculate the necessary amount of shielding for a given or proposed linear accelerator room design in radiotherapy. The program (Shield Calculation in Radiotherapy, SCR) has been developed using Microsoft Visual Basic. It applies the treatment room shielding calculations of NCRP report no. 151 to calculate proper shielding thicknesses for a given linear accelerator treatment room design. The program is composed of six main user-friendly interfaces. The first enables the user to upload their choice of treatment room design and to measure the distances required for shielding calculations. The second interface enables the user to calculate the primary barrier thickness in case of three-dimensional conventional radiotherapy (3D-CRT), intensity modulated radiotherapy (IMRT) and total body irradiation (TBI). The third interface calculates the required secondary barrier thickness due to both scattered and leakage radiation. The fourth and fifth interfaces provide a means to calculate the photon dose equivalent for low and high energy radiation, respectively, in door and maze areas. The sixth interface enables the user to calculate the skyshine radiation for photons and neutrons. The SCR program has been successfully validated, precisely reproducing all of the calculated examples presented in NCRP report no. 151 in a simple and fast manner. Moreover, it easily performed the same calculations for a test design that was also calculated manually, and produced the same results. The program includes a new and important feature that is the ability to calculate required treatment room thickness in case of IMRT and TBI. It is characterised by simplicity, precision, data saving, printing and retrieval, in addition to providing a means for uploading and testing any proposed treatment room shielding design. The SCR program provides comprehensive, simple, fast and accurate room shielding calculations in radiotherapy.
ERIC Educational Resources Information Center
Shaw, David D.; Pease, Leonard F., III.
2014-01-01
Grading can be accelerated to make time for more effective instruction. This article presents specific time management strategies selected to decrease administrative time required of faculty and teaching assistants, including a multiple answer multiple choice interface for exams, a three-tier grading system for open ended problem solving, and a…
ANALYTICAL TOOLS INTERFACE FOR LANDSCAPE ASSESSMENTS (ATTILA) USER MANUAL
ATtlLA is an ArcView extension that allows users to easily calculate many common landscape metrics. GIS expertise is not required, but some experience with ArcView is recommended. Four metric groups are currently included in ATtILA: landscape characteristics, riparian characteris...
Decommissioning of the Northrop TRIGA reactor
DOE Office of Scientific and Technical Information (OSTI.GOV)
Cozens, George B.; Woo, Harry; Benveniste, Jack
1986-07-01
An overview of the administrative and operational aspects of decommissioning and dismantling the Northrop Mark F TRIGA Reactor, including: planning and preparation, personnel requirements, government interfacing, costs, contractor negotiations, fuel shipments, demolition, disposal of low level waste, final survey and disposition of the concrete biological shielding. (author)
Servicing capability for the evolutionary Space Station
NASA Technical Reports Server (NTRS)
Thomas, Edward F.; Grems, Edward G., III; Corbo, James E.
1990-01-01
Since the beginning of the Space Station Freedom (SSF) program the concept of on-orbit servicing of user hardware has been an integral part of the program implementation. The user servicing system architecture has been divided into a baseline and a growth phase. The baseline system consists of the following hardware elements that will support user servicing - flight telerobotic servicer, crew and equipment translation aid, crew intravehicular and extravehicular servicing support, logistics supply system, mobile servicing center, and the special purpose dextrous manipulator. The growth phase incorporates a customer servicing facility (CSF), a station-based orbital maneuvering vehicle and an orbital spacecraft consumables resupply system. The requirements for user servicing were derived from the necessity to service attached payloads, free flyers and coorbiting platforms. These requirements include: orbital replacement units (ORU) and instrument changeout, National Space Transportation System cargo bay loading and unloading, contamination control and monitoring, thermal protection, payload berthing, storage, access to SSF distributed systems, functional checkout, and fluid replenishment. The baseline user servicing capabilities accommodate ORU and instrument changeout. However, this service is limited to attached payloads, either in situ or at a locally adjacent site. The growth phase satisfies all identified user servicing requirements by expanding servicing capabilities to include complex servicing tasks for attached payloads, free-flyers and coorbiting platforms at a dedicated, protected Servicing site. To provide a smooth evolution of user servicing the SSF interfaces that are necessary to accommodate the growth phase have been identified. The interface requirements on SSF have been greatly simplified by accommodating the growth servicing support elements within the CSF. This results in a single SSF interface: SSF to the CSF.
Space Generic Open Avionics Architecture (SGOAA) standard specification
NASA Technical Reports Server (NTRS)
Wray, Richard B.; Stovall, John R.
1993-01-01
The purpose of this standard is to provide an umbrella set of requirements for applying the generic architecture interface model to the design of a specific avionics hardware/software system. This standard defines a generic set of system interface points to facilitate identification of critical interfaces and establishes the requirements for applying appropriate low level detailed implementation standards to those interface points. The generic core avionics system and processing architecture models provided herein are robustly tailorable to specific system applications and provide a platform upon which the interface model is to be applied.
Design for interaction between humans and intelligent systems during real-time fault management
NASA Technical Reports Server (NTRS)
Malin, Jane T.; Schreckenghost, Debra L.; Thronesbery, Carroll G.
1992-01-01
Initial results are reported to provide guidance and assistance for designers of intelligent systems and their human interfaces. The objective is to achieve more effective human-computer interaction (HCI) for real time fault management support systems. Studies of the development of intelligent fault management systems within NASA have resulted in a new perspective of the user. If the user is viewed as one of the subsystems in a heterogeneous, distributed system, system design becomes the design of a flexible architecture for accomplishing system tasks with both human and computer agents. HCI requirements and design should be distinguished from user interface (displays and controls) requirements and design. Effective HCI design for multi-agent systems requires explicit identification of activities and information that support coordination and communication between agents. The effects are characterized of HCI design on overall system design and approaches are identified to addressing HCI requirements in system design. The results include definition of (1) guidance based on information level requirements analysis of HCI, (2) high level requirements for a design methodology that integrates the HCI perspective into system design, and (3) requirements for embedding HCI design tools into intelligent system development environments.
NASA Technical Reports Server (NTRS)
Hockensmith, R.; Devine, E.; Digiacomo, M.; Hager, F.; Moss, R.
1983-01-01
Satellites that use the NASA Tracking and Data Relay Satellite System (TDRSS) require antennas that are crucial for performing and achieving reliable TDRSS link performance at the desired data rate. Technical guidelines are presented to assist the prospective TDRSS medium-and high-data rate user in selecting and procuring a viable, steerable high-gain antenna system. Topics addressed include the antenna gain/transmitter power/data rate relationship; Earth power flux-density limitations; electromechanical requirements dictated by the small beam widths, desired angular coverage, and minimal torque disturbance to the spacecraft; weight and moment considerations; mechanical, electrical and thermal interfaces; design lifetime failure modes; and handling and storage. Proven designs are cited and space-qualified assemblies and components are identified.
Szostak, Katarzyna M.; Grand, Laszlo; Constandinou, Timothy G.
2017-01-01
Implantable neural interfaces for central nervous system research have been designed with wire, polymer, or micromachining technologies over the past 70 years. Research on biocompatible materials, ideal probe shapes, and insertion methods has resulted in building more and more capable neural interfaces. Although the trend is promising, the long-term reliability of such devices has not yet met the required criteria for chronic human application. The performance of neural interfaces in chronic settings often degrades due to foreign body response to the implant that is initiated by the surgical procedure, and related to the probe structure, and material properties used in fabricating the neural interface. In this review, we identify the key requirements for neural interfaces for intracortical recording, describe the three different types of probes—microwire, micromachined, and polymer-based probes; their materials, fabrication methods, and discuss their characteristics and related challenges. PMID:29270103
Szostak, Katarzyna M; Grand, Laszlo; Constandinou, Timothy G
2017-01-01
Implantable neural interfaces for central nervous system research have been designed with wire, polymer, or micromachining technologies over the past 70 years. Research on biocompatible materials, ideal probe shapes, and insertion methods has resulted in building more and more capable neural interfaces. Although the trend is promising, the long-term reliability of such devices has not yet met the required criteria for chronic human application. The performance of neural interfaces in chronic settings often degrades due to foreign body response to the implant that is initiated by the surgical procedure, and related to the probe structure, and material properties used in fabricating the neural interface. In this review, we identify the key requirements for neural interfaces for intracortical recording, describe the three different types of probes-microwire, micromachined, and polymer-based probes; their materials, fabrication methods, and discuss their characteristics and related challenges.
Microwave intersatellite links for communications satellites
NASA Technical Reports Server (NTRS)
Welti, G. R.
1982-01-01
Applications and interface requirements for intersatellite links (ISLs) between commercial communications satellites are reviewed, ranging from ISLs between widely separated satellites to ISLs between clustered satellites. On-board processing architectures for ISLs employing a variety of modulation schemes are described. These schemes include FM remodulation and QPSK regeneration in combination with switching and buffering. The various architectures are compared in terms of complexity, required performance, antenna size, mass, and power.
Nanotechnology: The Next Industrial Revolution - Military and Societal Implications
2005-01-15
nanoscale and then processed into components. Second, the components would have to be connected and made to interface with the macroenvironment . Third...includes market entry requirements as well as requirements for recordkeeping and adverse effect reporting and the EPA can apply these regulations...answered; a number of employee and soldier issues are prominent; for example, how do the following factors impact on the ability to work in
24/7 Operational Effectiveness Toolset: Mishap Investigation Interface
2008-10-01
analysis software product. The toolset was based upon the Sleep, Activity, Fatigue, and Task Effectiveness (SAFTE™; Hursh et al., 2004). The SAFTE...meeting was for the purpose of requirements analysis , in which the designers elicited task information from the SMEs. The second meeting included a...investigators who also served as our SMEs. The requirements analysis revealed how fatigue related information is entered into the report of an Air Force
Collaborative engineering and design management for the Hobby-Eberly Telescope tracker upgrade
NASA Astrophysics Data System (ADS)
Mollison, Nicholas T.; Hayes, Richard J.; Good, John M.; Booth, John A.; Savage, Richard D.; Jackson, John R.; Rafal, Marc D.; Beno, Joseph H.
2010-07-01
The engineering and design of systems as complex as the Hobby-Eberly Telescope's* new tracker require that multiple tasks be executed in parallel and overlapping efforts. When the design of individual subsystems is distributed among multiple organizations, teams, and individuals, challenges can arise with respect to managing design productivity and coordinating successful collaborative exchanges. This paper focuses on design management issues and current practices for the tracker design portion of the Hobby-Eberly Telescope Wide Field Upgrade project. The scope of the tracker upgrade requires engineering contributions and input from numerous fields including optics, instrumentation, electromechanics, software controls engineering, and site-operations. Successful system-level integration of tracker subsystems and interfaces is critical to the telescope's ultimate performance in astronomical observation. Software and process controls for design information and workflow management have been implemented to assist the collaborative transfer of tracker design data. The tracker system architecture and selection of subsystem interfaces has also proven to be a determining factor in design task formulation and team communication needs. Interface controls and requirements change controls will be discussed, and critical team interactions are recounted (a group-participation Failure Modes and Effects Analysis [FMEA] is one of special interest). This paper will be of interest to engineers, designers, and managers engaging in multi-disciplinary and parallel engineering projects that require coordination among multiple individuals, teams, and organizations.
EPA has published a Direct Final Rule that addresses requirements for parties that handle pipeline interface as well as addresses downstream quality assurance requirements for refiners (EPA publication # EPA-420-F-06-039).
Federal Register 2010, 2011, 2012, 2013, 2014
2011-03-17
... public safety broadband networks to employ the Long Term Evolution (LTE) broadband standard, specifically... and Order further requires that these networks support certain LTE interfaces. These requirements were... network deployment, that its network will support the required LTE interfaces. This requirement will...
Wang, Huai-Song; Song, Min; Hang, Tai-Jun
2016-02-10
The high-value applications of functional polymers in analytical science generally require well-defined interfaces, including precisely synthesized molecular architectures and compositions. Controlled/living radical polymerization (CRP) has been developed as a versatile and powerful tool for the preparation of polymers with narrow molecular weight distributions and predetermined molecular weights. Among the CRP system, atom transfer radical polymerization (ATRP) and reversible addition-fragmentation chain transfer (RAFT) are well-used to develop new materials for analytical science, such as surface-modified core-shell particles, monoliths, MIP micro- or nanospheres, fluorescent nanoparticles, and multifunctional materials. In this review, we summarize the emerging functional interfaces constructed by RAFT and ATRP for applications in analytical science. Various polymers with precisely controlled architectures including homopolymers, block copolymers, molecular imprinted copolymers, and grafted copolymers were synthesized by CRP methods for molecular separation, retention, or sensing. We expect that the CRP methods will become the most popular technique for preparing functional polymers that can be broadly applied in analytical chemistry.
Zero-G life support for Space Station Freedom
NASA Technical Reports Server (NTRS)
Kolodney, Matthew; Dall-Bauman, L.
1992-01-01
Optimal design of spacecraft environmental control and life support systems (ECLSS) for long duration missions requires an understanding of microgravity and its long-term influence on ECLSS performance characteristics. This understanding will require examination of the fundamental processes associated with air revitalization and water recovery in a microgravity environment. Short term testing can be performed on NASA's reduced gravity aircraft (a KC-135), but longer tests will need to be conducted on the shuttle or Space Station Freedom. Conceptual designs have been prepared for ECLSS test beds that will allow extended testing of equipment under microgravity conditions. Separate designs have been formulated for air revitalization and water recovery test beds. In order to allow testing of a variety of hardware with minimal alteration of the beds themselves, the designs include storage tanks, plumbing, and limited instrumentation that would be expected to be common to all air (or water) treatment equipment of interest. In the interest of minimizing spacecraft/test bed interface requirements, the beds are designed to recycle process fluids to the greatest extent possible. In most cases, only cooling water and power interfaces are required. A volume equal to that of two SSF lockers was allowed for each design. These bed dimensions would limit testing to equipment with a 0.5- to 1.5-person-equivalent throughput. The mass, volume, and power requirements for the air revitalization test bed are estimated at 125-280 kg, 1.0- 1.4 cubic meters, and 170 min 1070 W. Corresponding ranges for the water recovery test bed are 325-375 kg, 1.0- 1.1 cubic meters, and 350-850 W. These figures include individual test articles and accompanying hardware as well as the tanks, plumbing, and instrumentation included in the bed designs. Process fluid weight (i.e., water weight) is also included.
Man-systems distributed system for Space Station Freedom
NASA Technical Reports Server (NTRS)
Lewis, J. L.
1990-01-01
Viewgraphs on man-systems distributed system for Space Station Freedom are presented. Topics addressed include: description of man-systems (definition, requirements, scope, subsystems, and topologies); implementation (approach, tools); man-systems interfaces (system to element and system to system); prime/supporting development relationship; selected accomplishments; and technical challenges.
HAL/S-FC compiler system functional specification
NASA Technical Reports Server (NTRS)
1974-01-01
Compiler organization is discussed, including overall compiler structure, internal data transfer, compiler development, and code optimization. The user, system, and SDL interfaces are described, along with compiler system requirements. Run-time software support package and restrictions and dependencies are also considered of the HAL/S-FC system.
AGUIA: autonomous graphical user interface assembly for clinical trials semantic data services.
Correa, Miria C; Deus, Helena F; Vasconcelos, Ana T; Hayashi, Yuki; Ajani, Jaffer A; Patnana, Srikrishna V; Almeida, Jonas S
2010-10-26
AGUIA is a front-end web application originally developed to manage clinical, demographic and biomolecular patient data collected during clinical trials at MD Anderson Cancer Center. The diversity of methods involved in patient screening and sample processing generates a variety of data types that require a resource-oriented architecture to capture the associations between the heterogeneous data elements. AGUIA uses a semantic web formalism, resource description framework (RDF), and a bottom-up design of knowledge bases that employ the S3DB tool as the starting point for the client's interface assembly. The data web service, S3DB, meets the necessary requirements of generating the RDF and of explicitly distinguishing the description of the domain from its instantiation, while allowing for continuous editing of both. Furthermore, it uses an HTTP-REST protocol, has a SPARQL endpoint, and has open source availability in the public domain, which facilitates the development and dissemination of this application. However, S3DB alone does not address the issue of representing content in a form that makes sense for domain experts. We identified an autonomous set of descriptors, the GBox, that provides user and domain specifications for the graphical user interface. This was achieved by identifying a formalism that makes use of an RDF schema to enable the automatic assembly of graphical user interfaces in a meaningful manner while using only resources native to the client web browser (JavaScript interpreter, document object model). We defined a generalized RDF model such that changes in the graphic descriptors are automatically and immediately (locally) reflected into the configuration of the client's interface application. The design patterns identified for the GBox benefit from and reflect the specific requirements of interacting with data generated by clinical trials, and they contain clues for a general purpose solution to the challenge of having interfaces automatically assembled for multiple and volatile views of a domain. By coding AGUIA in JavaScript, for which all browsers include a native interpreter, a solution was found that assembles interfaces that are meaningful to the particular user, and which are also ubiquitous and lightweight, allowing the computational load to be carried by the client's machine.
The New Web-Based Hera Data Processing System at the HEASARC
NASA Technical Reports Server (NTRS)
Pence, W.
2011-01-01
The HEASARC at NASA/GSFC has provide an on-line astronomical data processing system called Hera for several years. Hera provides a complete data processing environment, including installed software packages, local data storage, and the CPU resources needed to process the user's data. The original design of Hera, however, has 2 requirements that has limited it's usefulness for some users, namely, that 1) the user must download and install a small helper program on their own computer before using Hera, and 2) Hera requires that several computer ports/sockets be allowed to communicate through any local firewalls on the users machine. Both of these restrictions can be problematic for some users, therefore we are now migrating Hera into a purely Web based environment which only requires a standard Web browser. The first release of Web Hera is now publicly available at http://heasarc.gsfc.nasa.gov/webheara/. It currently provides a standard graphical interface for running hundreds of different data processing programs that are available in the HEASARC's ftools software package. Over the next year we to add more features to Web Hera, including an interactive command line interface, and more display and line capabilities.
Spreadsheets for Analyzing and Optimizing Space Missions
NASA Technical Reports Server (NTRS)
Some, Raphael R.; Agrawal, Anil K.; Czikmantory, Akos J.; Weisbin, Charles R.; Hua, Hook; Neff, Jon M.; Cowdin, Mark A.; Lewis, Brian S.; Iroz, Juana; Ross, Rick
2009-01-01
XCALIBR (XML Capability Analysis LIBRary) is a set of Extensible Markup Language (XML) database and spreadsheet- based analysis software tools designed to assist in technology-return-on-investment analysis and optimization of technology portfolios pertaining to outer-space missions. XCALIBR is also being examined for use in planning, tracking, and documentation of projects. An XCALIBR database contains information on mission requirements and technological capabilities, which are related by use of an XML taxonomy. XCALIBR incorporates a standardized interface for exporting data and analysis templates to an Excel spreadsheet. Unique features of XCALIBR include the following: It is inherently hierarchical by virtue of its XML basis. The XML taxonomy codifies a comprehensive data structure and data dictionary that includes performance metrics for spacecraft, sensors, and spacecraft systems other than sensors. The taxonomy contains >700 nodes representing all levels, from system through subsystem to individual parts. All entries are searchable and machine readable. There is an intuitive Web-based user interface. The software automatically matches technologies to mission requirements. The software automatically generates, and makes the required entries in, an Excel return-on-investment analysis software tool. The results of an analysis are presented in both tabular and graphical displays.
User interface issues in supporting human-computer integrated scheduling
NASA Technical Reports Server (NTRS)
Cooper, Lynne P.; Biefeld, Eric W.
1991-01-01
Explored here is the user interface problems encountered with the Operations Missions Planner (OMP) project at the Jet Propulsion Laboratory (JPL). OMP uses a unique iterative approach to planning that places additional requirements on the user interface, particularly to support system development and maintenance. These requirements are necessary to support the concepts of heuristically controlled search, in-progress assessment, and iterative refinement of the schedule. The techniques used to address the OMP interface needs are given.
International Docking Standard (IDSS) Interface Definition Document (IDD) . E; Revision
NASA Technical Reports Server (NTRS)
Kelly, Sean M.; Cryan, Scott P.
2016-01-01
This International Docking System Standard (IDSS) Interface Definition Document (IDD) is the result of a collaboration by the International Space Station membership to establish a standard docking interface to enable on-orbit crew rescue operations and joint collaborative endeavors utilizing different spacecraft. This IDSS IDD details the physical geometric mating interface and design loads requirements. The physical geometric interface requirements must be strictly followed to ensure physical spacecraft mating compatibility. This includes both defined components and areas that are void of components. The IDD also identifies common design parameters as identified in section 3.0, e.g., docking initial conditions and vehicle mass properties. This information represents a recommended set of design values enveloping a broad set of design reference missions and conditions, which if accommodated in the docking system design, increases the probability of successful docking between different spacecraft. This IDD does not address operational procedures or off-nominal situations, nor does it dictate implementation or design features behind the mating interface. It is the responsibility of the spacecraft developer to perform all hardware verification and validation, and to perform final docking analyses to ensure the needed docking performance and to develop the final certification loads for their application. While there are many other critical requirements needed in the development of a docking system such as fault tolerance, reliability, and environments (e.g. vibration, etc.), it is not the intent of the IDSS IDD to mandate all of these requirements; these requirements must be addressed as part of the specific developer's unique program, spacecraft and mission needs. This approach allows designers the flexibility to design and build docking mechanisms to their unique program needs and requirements. The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions.The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions. The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions.
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.
Ground Systems Development Environment (GSDE) interface requirements and prototyping plan
NASA Technical Reports Server (NTRS)
Church, Victor E.; Philips, John; Bassman, Mitchell; Williams, C.
1990-01-01
This report describes the data collection and requirements analysis effort of the Ground System Development Environment (GSDE) Interface Requirements study. It identifies potential problems in the interfaces among applications and processors in the heterogeneous systems that comprises the GSDE. It describes possible strategies for addressing those problems. It also identifies areas for further research and prototyping to demonstrate the capabilities and feasibility of those strategies and defines a plan for building the necessary software prototypes.
A novel asynchronous access method with binary interfaces
2008-01-01
Background Traditionally synchronous access strategies require users to comply with one or more time constraints in order to communicate intent with a binary human-machine interface (e.g., mechanical, gestural or neural switches). Asynchronous access methods are preferable, but have not been used with binary interfaces in the control of devices that require more than two commands to be successfully operated. Methods We present the mathematical development and evaluation of a novel asynchronous access method that may be used to translate sporadic activations of binary interfaces into distinct outcomes for the control of devices requiring an arbitrary number of commands to be controlled. With this method, users are required to activate their interfaces only when the device under control behaves erroneously. Then, a recursive algorithm, incorporating contextual assumptions relevant to all possible outcomes, is used to obtain an informed estimate of user intention. We evaluate this method by simulating a control task requiring a series of target commands to be tracked by a model user. Results When compared to a random selection, the proposed asynchronous access method offers a significant reduction in the number of interface activations required from the user. Conclusion This novel access method offers a variety of advantages over traditionally synchronous access strategies and may be adapted to a wide variety of contexts, with primary relevance to applications involving direct object manipulation. PMID:18959797
NASA Astrophysics Data System (ADS)
Brenckle, Mark
Recent efforts in bioelectronics and biooptics have led to a shift in the materials and form factors used to make medical devices, including high performance, implantable, and wearable sensors. In this context, biopolymer-based devices must be processed to interface the soft, curvilinear biological world with the rigid, inorganic world of traditional electronics and optics. This poses new material-specific fabrication challenges in designing such devices, which in turn requires further understanding of the fundamental physical behaviors of the materials in question. As a biopolymer, silk fibroin protein has remarkable promise in this space, due to its bioresorbability, mechanical strength, optical clarity, ability to be reshaped on the micro- and nano-scale, and ability to stabilize labile compounds. Application of this material to devices at the biotic/abiotic interface will require the development of fabrication techniques for nano-patterning, lithography, multilayer adhesion, and transfer printing in silk materials. In this work, we address this need through fundamental study of the thermal and diffusional properties of silk protein as it relates to these fabrication strategies. We then leverage these properties to fabricate devices well suited to the biotic/abiotic interface in three areas: shelf-ready sensing, implantable transient electronics, and wearable biosensing. These example devices will illustrate the advantages of silk in this class of bioelectronic and biooptical devices, from fundamentals through application, and contribute to a silk platform for the development of future devices that combine biology with high technology.
Research the mobile phone operation interfaces for vision-impairment.
Yao, Yen-Ting; Leung, Cherng-Yee
2012-01-01
Due to the vision-impaired users commonly having difficulty with mobile-phone function operations and adaption any manufacturer's user interface design, the goals for this research are established for evaluating how to improve for them the function operation convenience and user interfaces of either mobile phones or electronic appliances in the market currently. After applying collecting back 30 effective questionnaires from 30 vision-impairment, the comments have been concluded from this research include: (1) All mobile phone manufactures commonly ignorant of the vision-impairment difficulty with operating mobile phone user interfaces; (2) The vision-impairment preferential with audio alert signals; (3) The vision-impairment incapable of mobile-phone procurement independently unless with assistance from others; (4) Preferential with adding touch-usage interface design by the vision-impairment; in contrast with the least requirement for such functions as braille, enlarging keystroke size and diversifying-function control panel. With exploring the vision-impairment's necessary improvements and obstacles for mobile phone interface operation, this research is established with goals for offering reference possibly applied in electronic appliance design and . Hopefully, the analysis results of this research could be used as data references for designing electronic and high-tech products and promoting more usage convenience for those vision-impaired.
An interface capturing scheme for modeling atomization in compressible flows
NASA Astrophysics Data System (ADS)
Garrick, Daniel P.; Hagen, Wyatt A.; Regele, Jonathan D.
2017-09-01
The study of atomization in supersonic flow is critical to ensuring reliable ignition of scramjet combustors under startup conditions. Numerical methods incorporating surface tension effects have largely focused on the incompressible regime as most atomization applications occur at low Mach numbers. Simulating surface tension effects in compressible flow requires robust numerical methods that can handle discontinuities caused by both shocks and material interfaces with high density ratios. In this work, a shock and interface capturing scheme is developed that uses the Harten-Lax-van Leer-Contact (HLLC) Riemann solver while a Tangent of Hyperbola for INterface Capturing (THINC) interface reconstruction scheme retains the fluid immiscibility condition in the volume fraction and phasic densities in the context of the five equation model. The approach includes the effects of compressibility, surface tension, and molecular viscosity. One and two-dimensional benchmark problems demonstrate the desirable interface sharpening and conservation properties of the approach. Simulations of secondary atomization of a cylindrical water column after its interaction with a shockwave show good qualitative agreement with experimentally observed behavior. Three-dimensional examples of primary atomization of a liquid jet in a Mach 2 crossflow demonstrate the robustness of the method.
Improved 3-D turbomachinery CFD algorithm
NASA Technical Reports Server (NTRS)
Janus, J. Mark; Whitfield, David L.
1988-01-01
The building blocks of a computer algorithm developed for the time-accurate flow analysis of rotating machines are described. The flow model is a finite volume method utilizing a high resolution approximate Riemann solver for interface flux definitions. This block LU implicit numerical scheme possesses apparent unconditional stability. Multi-block composite gridding is used to orderly partition the field into a specified arrangement. Block interfaces, including dynamic interfaces, are treated such as to mimic interior block communication. Special attention is given to the reduction of in-core memory requirements by placing the burden on secondary storage media. Broad applicability is implied, although the results presented are restricted to that of an even blade count configuration. Several other configurations are presently under investigation, the results of which will appear in subsequent publications.
Polymer-grafted Lignin: Molecular Design and Interfacial Activities
NASA Astrophysics Data System (ADS)
Gupta, Chetali
The broader technical objective of this work is to develop a strategy for using the biopolymer lignin in a wide variety of surfactant applications through polymer grafting. These applications include emulsion stabilizers, dispersants and foaming agents. The scientific objective of the research performed within this thesis is to understand the effect of molecular architecture and polymer grafting on the interfacial activity at the air-liquid, liquid-liquid and solid-liquid interface. Research has focused on designing of these lignopolymers with controlled architecture using polyethylene glycol, poly(acrylic acid) and polyacrylamide grafts. The interfacial activity for all polymer grafts has been tested at all three interfaces using a broad range of techniques specific to the interface. Results have shown that the hydrophobicity of the lignin core is responsible for enhanced interfacial activity at the air-liquid and liquid-liquid interface. Conversely, improved hydrophilicity and "electrosteric" interactions are required for higher interfacial activity of the lignin at the liquid-solid interface. The high interfacial activity of the polymer-grafted lignin observed in the air-liquid and liquid-liquid interfaces not only resulted in viscosity reduction but also strength enhancement at the liquid-solid interface. The broader implication of this study is to be able to predict what chemical functionalities need to be adjusted to get the desired viscosity reduction.
Ecohydrological interfaces as hot spots of ecosystem processes
NASA Astrophysics Data System (ADS)
Krause, Stefan; Lewandowski, Jörg; Grimm, Nancy B.; Hannah, David M.; Pinay, Gilles; McDonald, Karlie; Martí, Eugènia; Argerich, Alba; Pfister, Laurent; Klaus, Julian; Battin, Tom; Larned, Scott T.; Schelker, Jacob; Fleckenstein, Jan; Schmidt, Christian; Rivett, Michael O.; Watts, Glenn; Sabater, Francesc; Sorolla, Albert; Turk, Valentina
2017-08-01
The movement of water, matter, organisms, and energy can be altered substantially at ecohydrological interfaces, the dynamic transition zones that often develop within ecotones or boundaries between adjacent ecosystems. Interdisciplinary research over the last two decades has indicated that ecohydrological interfaces are often "hot spots" of ecological, biogeochemical, and hydrological processes and may provide refuge for biota during extreme events. Ecohydrological interfaces can have significant impact on global hydrological and biogeochemical cycles, biodiversity, pollutant removal, and ecosystem resilience to disturbance. The organizational principles (i.e., the drivers and controls) of spatially and temporally variable processes at ecohydrological interfaces are poorly understood and require the integrated analysis of hydrological, biogeochemical, and ecological processes. Our rudimentary understanding of the interactions between different drivers and controls critically limits our ability to predict complex system responses to change. In this paper, we explore similarities and contrasts in the functioning of diverse freshwater ecohydrological interfaces across spatial and temporal scales. We use this comparison to develop an integrated, interdisciplinary framework, including a roadmap for analyzing ecohydrological processes and their interactions in ecosystems. We argue that, in order to fully account for their nonlinear process dynamics, ecohydrological interfaces need to be conceptualized as unique, spatially and temporally dynamic entities, which represents a step change from their current representation as boundary conditions at investigated ecosystems.
Current trends in hardware and software for brain-computer interfaces (BCIs)
NASA Astrophysics Data System (ADS)
Brunner, P.; Bianchi, L.; Guger, C.; Cincotti, F.; Schalk, G.
2011-04-01
A brain-computer interface (BCI) provides a non-muscular communication channel to people with and without disabilities. BCI devices consist of hardware and software. BCI hardware records signals from the brain, either invasively or non-invasively, using a series of device components. BCI software then translates these signals into device output commands and provides feedback. One may categorize different types of BCI applications into the following four categories: basic research, clinical/translational research, consumer products, and emerging applications. These four categories use BCI hardware and software, but have different sets of requirements. For example, while basic research needs to explore a wide range of system configurations, and thus requires a wide range of hardware and software capabilities, applications in the other three categories may be designed for relatively narrow purposes and thus may only need a very limited subset of capabilities. This paper summarizes technical aspects for each of these four categories of BCI applications. The results indicate that BCI technology is in transition from isolated demonstrations to systematic research and commercial development. This process requires several multidisciplinary efforts, including the development of better integrated and more robust BCI hardware and software, the definition of standardized interfaces, and the development of certification, dissemination and reimbursement procedures.
Orion Passive Thermal Control Overview
NASA Technical Reports Server (NTRS)
Miller, Stephen W.
2007-01-01
An viewgraph presentation of Orion's passive thermal control system is shown. The topics include: 1) Orion in CxP Hierarchy; 2) General Orion Description/Orientation; 3) Module Descriptions and Images; 4) Orion PTCS Overview; 5) Requirements/Interfaces; 6) Design Reference Missions; 7) Natural Environments; 8) Thermal Models; 9) Challenges/Issues; and 10) Testing
Intelligent CAI: An Author Aid for a Natural Language Interface.
ERIC Educational Resources Information Center
Burton, Richard R.; Brown, John Seely
This report addresses the problems of using natural language (English) as the communication language for advanced computer-based instructional systems. The instructional environment places requirements on a natural language understanding system that exceed the capabilities of all existing systems, including: (1) efficiency, (2) habitability, (3)…
15 CFR 2301.7 - Eligible and ineligible project costs.
Code of Federal Regulations, 2012 CFR
2012-01-01
... 15 Commerce and Foreign Trade 3 2012-01-01 2012-01-01 false Eligible and ineligible project costs... TELECOMMUNICATIONS FACILITIES PROGRAM Application Requirements § 2301.7 Eligible and ineligible project costs. (a... wherever the two types of apparatus interface. (c) Total project costs do not include the value of eligible...
15 CFR 2301.7 - Eligible and ineligible project costs.
Code of Federal Regulations, 2011 CFR
2011-01-01
... 15 Commerce and Foreign Trade 3 2011-01-01 2011-01-01 false Eligible and ineligible project costs... TELECOMMUNICATIONS FACILITIES PROGRAM Application Requirements § 2301.7 Eligible and ineligible project costs. (a... wherever the two types of apparatus interface. (c) Total project costs do not include the value of eligible...
15 CFR 2301.7 - Eligible and ineligible project costs.
Code of Federal Regulations, 2014 CFR
2014-01-01
... 15 Commerce and Foreign Trade 3 2014-01-01 2014-01-01 false Eligible and ineligible project costs... TELECOMMUNICATIONS FACILITIES PROGRAM Application Requirements § 2301.7 Eligible and ineligible project costs. (a... wherever the two types of apparatus interface. (c) Total project costs do not include the value of eligible...
15 CFR 2301.7 - Eligible and ineligible project costs.
Code of Federal Regulations, 2013 CFR
2013-01-01
... 15 Commerce and Foreign Trade 3 2013-01-01 2013-01-01 false Eligible and ineligible project costs... TELECOMMUNICATIONS FACILITIES PROGRAM Application Requirements § 2301.7 Eligible and ineligible project costs. (a... wherever the two types of apparatus interface. (c) Total project costs do not include the value of eligible...
15 CFR 2301.7 - Eligible and ineligible project costs.
Code of Federal Regulations, 2010 CFR
2010-01-01
... 15 Commerce and Foreign Trade 3 2010-01-01 2010-01-01 false Eligible and ineligible project costs... TELECOMMUNICATIONS FACILITIES PROGRAM Application Requirements § 2301.7 Eligible and ineligible project costs. (a... wherever the two types of apparatus interface. (c) Total project costs do not include the value of eligible...
DocML: A Digital Library of University Data.
ERIC Educational Resources Information Center
Papadakis, Ioannis; Karakoidas, Vassileios; Chrissikopoulos, Vassileios
2002-01-01
Describes DocML, a Web-based digital library of university data that is used to build a system capable of preserving and managing student assignments. Topics include requirements for a digital library of university data; metadata and XML; three-tier architecture; user interface; searching; browsing; content delivery; and administrative issues.…
Support of surgical process modeling by using adaptable software user interfaces
NASA Astrophysics Data System (ADS)
Neumuth, T.; Kaschek, B.; Czygan, M.; Goldstein, D.; Strauß, G.; Meixensberger, J.; Burgert, O.
2010-03-01
Surgical Process Modeling (SPM) is a powerful method for acquiring data about the evolution of surgical procedures. Surgical Process Models are used in a variety of use cases including evaluation studies, requirements analysis and procedure optimization, surgical education, and workflow management scheme design. This work proposes the use of adaptive, situation-aware user interfaces for observation support software for SPM. We developed a method to support the modeling of the observer by using an ontological knowledge base. This is used to drive the graphical user interface for the observer to restrict the search space of terminology depending on the current situation. In the evaluation study it is shown, that the workload of the observer was decreased significantly by using adaptive user interfaces. 54 SPM observation protocols were analyzed by using the NASA Task Load Index and it was shown that the use of the adaptive user interface disburdens the observer significantly in workload criteria effort, mental demand and temporal demand, helping him to concentrate on his essential task of modeling the Surgical Process.
Transport properties at fluids interfaces: a molecular study for a macroscopic modelling
NASA Astrophysics Data System (ADS)
Russo, Antonio; Morciano, Matteo; Sibley, David N.; Nold, Andreas; Goddard, Benjamin D.; Asinari, Pietro; Kalliadasis, Serafim
2017-11-01
Rapid developments in the field of micro- and nano-fluidics require detailed analysis of the properties of matter at the molecular level. But despite numerous works in the literature, appropriate macroscopic relations able to integrate a microscopic description of fluid and soft matter properties at liquid-vapour and multi-fluid interfaces are missing. As a consequence, studies on interfacial phenomena and micro-device designs often rely on oversimplified assumptions, e.g. that the viscosities can be considered constant across interfaces. In our work, we present non-equilibrium MD simulations to scrutinise efficiently and systematically, through the tools of statistical mechanics, the anisotropic properties of fluids, namely density variations, stress tensor, and shear viscosity, at the fluid interfaces between liquid and vapour and between two partially miscible fluids. Our analysis has led to the formulation of a general relation between shear viscosity and density variations validated for a wide spectrum of interfacial fluid problems. In addition, it provides a rational description of other interfacial quantities of interest, including surface tension and its origins, and more generally, it offers valuable insight of molecular transport phenomena at interfaces.
High order solution of Poisson problems with piecewise constant coefficients and interface jumps
NASA Astrophysics Data System (ADS)
Marques, Alexandre Noll; Nave, Jean-Christophe; Rosales, Rodolfo Ruben
2017-04-01
We present a fast and accurate algorithm to solve Poisson problems in complex geometries, using regular Cartesian grids. We consider a variety of configurations, including Poisson problems with interfaces across which the solution is discontinuous (of the type arising in multi-fluid flows). The algorithm is based on a combination of the Correction Function Method (CFM) and Boundary Integral Methods (BIM). Interface and boundary conditions can be treated in a fast and accurate manner using boundary integral equations, and the associated BIM. Unfortunately, BIM can be costly when the solution is needed everywhere in a grid, e.g. fluid flow problems. We use the CFM to circumvent this issue. The solution from the BIM is used to rewrite the problem as a series of Poisson problems in rectangular domains-which requires the BIM solution at interfaces/boundaries only. These Poisson problems involve discontinuities at interfaces, of the type that the CFM can handle. Hence we use the CFM to solve them (to high order of accuracy) with finite differences and a Fast Fourier Transform based fast Poisson solver. We present 2-D examples of the algorithm applied to Poisson problems involving complex geometries, including cases in which the solution is discontinuous. We show that the algorithm produces solutions that converge with either 3rd or 4th order of accuracy, depending on the type of boundary condition and solution discontinuity.
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)
Toward Enhancing OpenMP's Work-Sharing Directives
DOE Office of Scientific and Technical Information (OSTI.GOV)
Chapman, B M; Huang, L; Jin, H
2006-05-17
OpenMP provides a portable programming interface for shared memory parallel computers (SMPs). Although this interface has proven successful for small SMPs, it requires greater flexibility in light of the steadily growing size of individual SMPs and the recent advent of multithreaded chips. In this paper, we describe two application development experiences that exposed these expressivity problems in the current OpenMP specification. We then propose mechanisms to overcome these limitations, including thread subteams and thread topologies. Thus, we identify language features that improve OpenMP application performance on emerging and large-scale platforms while preserving ease of programming.
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.
IAC - INTEGRATED ANALYSIS CAPABILITY
NASA Technical Reports Server (NTRS)
Frisch, H. P.
1994-01-01
The objective of the Integrated Analysis Capability (IAC) system is to provide a highly effective, interactive analysis tool for the integrated design of large structures. With the goal of supporting the unique needs of engineering analysis groups concerned with interdisciplinary problems, IAC was developed to interface programs from the fields of structures, thermodynamics, controls, and system dynamics with an executive system and database to yield a highly efficient multi-disciplinary system. Special attention is given to user requirements such as data handling and on-line assistance with operational features, and the ability to add new modules of the user's choice at a future date. IAC contains an executive system, a data base, general utilities, interfaces to various engineering programs, and a framework for building interfaces to other programs. IAC has shown itself to be effective in automatic data transfer among analysis programs. IAC 2.5, designed to be compatible as far as possible with Level 1.5, contains a major upgrade in executive and database management system capabilities, and includes interfaces to enable thermal, structures, optics, and control interaction dynamics analysis. The IAC system architecture is modular in design. 1) The executive module contains an input command processor, an extensive data management system, and driver code to execute the application modules. 2) Technical modules provide standalone computational capability as well as support for various solution paths or coupled analyses. 3) Graphics and model generation interfaces are supplied for building and viewing models. Advanced graphics capabilities are provided within particular analysis modules such as INCA and NASTRAN. 4) Interface modules provide for the required data flow between IAC and other modules. 5) User modules can be arbitrary executable programs or JCL procedures with no pre-defined relationship to IAC. 6) Special purpose modules are included, such as MIMIC (Model Integration via Mesh Interpolation Coefficients), which transforms field values from one model to another; LINK, which simplifies incorporation of user specific modules into IAC modules; and DATAPAC, the National Bureau of Standards statistical analysis package. The IAC database contains structured files which provide a common basis for communication between modules and the executive system, and can contain unstructured files such as NASTRAN checkpoint files, DISCOS plot files, object code, etc. The user can define groups of data and relations between them. A full data manipulation and query system operates with the database. The current interface modules comprise five groups: 1) Structural analysis - IAC contains a NASTRAN interface for standalone analysis or certain structural/control/thermal combinations. IAC provides enhanced structural capabilities for normal modes and static deformation analysis via special DMAP sequences. IAC 2.5 contains several specialized interfaces from NASTRAN in support of multidisciplinary analysis. 2) Thermal analysis - IAC supports finite element and finite difference techniques for steady state or transient analysis. There are interfaces for the NASTRAN thermal analyzer, SINDA/SINFLO, and TRASYS II. FEMNET, which converts finite element structural analysis models to finite difference thermal analysis models, is also interfaced with the IAC database. 3) System dynamics - The DISCOS simulation program which allows for either nonlinear time domain analysis or linear frequency domain analysis, is fully interfaced to the IAC database management capability. 4) Control analysis - Interfaces for the ORACLS, SAMSAN, NBOD2, and INCA programs allow a wide range of control system analyses and synthesis techniques. Level 2.5 includes EIGEN, which provides tools for large order system eigenanalysis, and BOPACE, which allows for geometric capabilities and finite element analysis with nonlinear material. Also included in IAC level 2.5 is SAMSAN 3.1, an engineering analysis program which contains a general purpose library of over 600 subroutin
Rapid Prototyping of Hydrologic Model Interfaces with IPython
NASA Astrophysics Data System (ADS)
Farthing, M. W.; Winters, K. D.; Ahmadia, A. J.; Hesser, T.; Howington, S. E.; Johnson, B. D.; Tate, J.; Kees, C. E.
2014-12-01
A significant gulf still exists between the state of practice and state of the art in hydrologic modeling. Part of this gulf is due to the lack of adequate pre- and post-processing tools for newly developed computational models. The development of user interfaces has traditionally lagged several years behind the development of a particular computational model or suite of models. As a result, models with mature interfaces often lack key advancements in model formulation, solution methods, and/or software design and technology. Part of the problem has been a focus on developing monolithic tools to provide comprehensive interfaces for the entire suite of model capabilities. Such efforts require expertise in software libraries and frameworks for creating user interfaces (e.g., Tcl/Tk, Qt, and MFC). These tools are complex and require significant investment in project resources (time and/or money) to use. Moreover, providing the required features for the entire range of possible applications and analyses creates a cumbersome interface. For a particular site or application, the modeling requirements may be simplified or at least narrowed, which can greatly reduce the number and complexity of options that need to be accessible to the user. However, monolithic tools usually are not adept at dynamically exposing specific workflows. Our approach is to deliver highly tailored interfaces to users. These interfaces may be site and/or process specific. As a result, we end up with many, customized interfaces rather than a single, general-use tool. For this approach to be successful, it must be efficient to create these tailored interfaces. We need technology for creating quality user interfaces that is accessible and has a low barrier for integration into model development efforts. Here, we present efforts to leverage IPython notebooks as tools for rapid prototyping of site and application-specific user interfaces. We provide specific examples from applications in near-shore environments as well as levee analysis. We discuss our design decisions and methodology for developing customized interfaces, strategies for delivery of the interfaces to users in various computing environments, as well as implications for the design/implementation of simulation models.
Programmable neural processing on a smartdust for brain-computer interfaces.
Yuwen Sun; Shimeng Huang; Oresko, Joseph J; Cheng, Allen C
2010-10-01
Brain-computer interfaces (BCIs) offer tremendous promise for improving the quality of life for disabled individuals. BCIs use spike sorting to identify the source of each neural firing. To date, spike sorting has been performed by either using off-chip analysis, which requires a wired connection penetrating the skull to a bulky external power/processing unit, or via custom application-specific integrated circuits that lack the programmability to perform different algorithms and upgrades. In this research, we propose and test the feasibility of performing on-chip, real-time spike sorting on a programmable smartdust, including feature extraction, classification, compression, and wireless transmission. A detailed power/performance tradeoff analysis using DVFS is presented. Our experimental results show that the execution time and power density meet the requirements to perform real-time spike sorting and wireless transmission on a single neural channel.
Experiment module concepts study. Volume 2: Experiments and mission operations
NASA Technical Reports Server (NTRS)
Macdonald, J. M.
1970-01-01
The baseline experiment program is concerned with future space experiments and cover the scientific disciplines of astronomy, space physics, space biology, biomedicine and biotechnology, earth applications, materials science, and advanced technology. The experiments within each discipline are grouped into functional program elements according to experiments that support a particular area of research or investigation and experiments that impose similar or related demand on space station support systems. The experiment requirements on module subsystems, experiment operating modes and time profiles, and the role of the astronaut are discussed. Launch and rendezvous with the space station, disposal, and on-orbit operations are delineated. The operational interfaces between module and other system elements are presented and include space station and logistic system interfaces. Preliminary launch and on-orbit environmental criteria and requirements are discussed, and experiment equipment weights by functional program elements are tabulated.
NASA Technical Reports Server (NTRS)
Easley, W. C.; Tanguy, J. S.
1986-01-01
An upgrade of the transport systems research vehicle (TSRV) experimental flight system retained the original monochrome display system. The original host computer was replaced with a Norden 11/70, a new digital autonomous terminal access communication (DATAC) data bus was installed for data transfer between display system and host, while a new data interface method was required. The new display data interface uses four split phase bipolar (SPBP) serial busses. The DATAC bus uses a shared interface ram (SIR) for intermediate storage of its data transfer. A display interface unit (DIU) was designed and configured to read from and write to the SIR to properly convert the data from parallel to SPBP serial and vice versa. It is found that separation of data for use by each SPBP bus and synchronization of data tranfer throughout the entire experimental flight system are major problems which require solution in DIU design. The techniques used to accomplish these new data interface requirements are described.
Space Station Human Factors Research Review. Volume 1: EVA Research and Development
NASA Technical Reports Server (NTRS)
Cohen, Marc M. (Editor); Vykukal, H. C. (Editor)
1988-01-01
An overview is presented of extravehicular activity (EVA) research and development activities at Ames. The majority of the program was devoted to presentations by the three contractors working in parallel on the EVA System Phase A Study, focusing on Implications for Man-Systems Design. Overhead visuals are included for a mission results summary, space station EVA requirements and interface accommodations summary, human productivity study cross-task coordination, and advanced EVAS Phase A study implications for man-systems design. Articles are also included on subsea approach to work systems development and advanced EVA system design requirements.
The evaluation and extension of TAE in the development of a user interface management system
NASA Technical Reports Server (NTRS)
Burkhart, Brenda; Sugar, Ross
1986-01-01
The development of a user interface management system (UIMS) for an information gathering and display system is discussed. The system interface requirements are outlined along with the UIMS functional characteristics. Those systems requirements which are supported by the current Transportable Applications Executive (TAE) are listed and necessary modifications to the TAE are described.
Software and Human-Machine Interface Development for Environmental Controls Subsystem Support
NASA Technical Reports Server (NTRS)
Dobson, Matthew
2018-01-01
The Space Launch System (SLS) is the next premier launch vehicle for NASA. It is the next stage of manned space exploration from American soil, and will be the platform in which we push further beyond Earth orbit. In preparation of the SLS maiden voyage on Exploration Mission 1 (EM-1), the existing ground support architecture at Kennedy Space Center required significant overhaul and updating. A comprehensive upgrade of controls systems was necessary, including programmable logic controller software, as well as Launch Control Center (LCC) firing room and local launch pad displays for technician use. Environmental control acts as an integral component in these systems, being the foremost system for conditioning the pad and extremely sensitive launch vehicle until T-0. The Environmental Controls Subsystem (ECS) required testing and modification to meet the requirements of the designed system, as well as the human factors requirements of NASA software for Validation and Verification (V&V). This term saw significant strides in the progress and functionality of the human-machine interfaces used at the launch pad, and improved integration with the controller code.
Using RDF and Git to Realize a Collaborative Metadata Repository.
Stöhr, Mark R; Majeed, Raphael W; Günther, Andreas
2018-01-01
The German Center for Lung Research (DZL) is a research network with the aim of researching respiratory diseases. The participating study sites' register data differs in terms of software and coding system as well as data field coverage. To perform meaningful consortium-wide queries through one single interface, a uniform conceptual structure is required covering the DZL common data elements. No single existing terminology includes all our concepts. Potential candidates such as LOINC and SNOMED only cover specific subject areas or are not granular enough for our needs. To achieve a broadly accepted and complete ontology, we developed a platform for collaborative metadata management. The DZL data management group formulated detailed requirements regarding the metadata repository and the user interfaces for metadata editing. Our solution builds upon existing standard technologies allowing us to meet those requirements. Its key parts are RDF and the distributed version control system Git. We developed a software system to publish updated metadata automatically and immediately after performing validation tests for completeness and consistency.
NASA Technical Reports Server (NTRS)
Bullington, Stanley F.
1992-01-01
The following list of requirements specifies the proposed revisions to the Experiment Scheduling Program (ESP2) which deal with schedule repair. These requirements are divided into those which are general in nature, those which relate to measurement and analysis functions of the software, those which relate specifically to conflict resolution, and those relating directly to the user interface. (This list is not a complete list of requirements for the user interface, but only a list of those schedule repair requirements which relate to the interface.) Some of the requirements relate only to uses of the software in real-time operations. Others are clearly for future versions of the software, beyond the upcoming revision. In either case, the fact will be clearly stated.
NASA Technical Reports Server (NTRS)
Viterna, Larry A.
1991-01-01
Detailed understanding of heat transfer and fluid flow is required for many aerospace thermal systems. These systems often include phase change and operate over a range of accelerations or effective gravitational fields. An approach to analyzing such systems is presented which requires the simultaneous solution of the conservation laws of energy, momentum, and mass, as well as an equation of state. The variable property form of the governing equations are developed in two-dimensional Cartesian coordinates for a Newtonian fluid. A numerical procedure for solving the governing equations is presented and implemented in a computer program. The Galerkin form of the finite element method is used to solve the spatial variation of the field variables, along with the implicit Crank-Nicolson time marching algorithm. Quadratic Langrangian elements are used for the internal energy and the two components of velocity. Linear Lagrangian elements are used for the pressure. The location of the solid/liquid interface as well as the temperatures are determined form the calculated internal energy and pressure. This approach is quite general in that it can describe heat transfer without phase change, phase change with a sharp interface, and phase change without an interface. Analytical results from this model are compared to those of other researchers studying transient conduction, convection, and phase change and are found to be in good agreement. The numerical procedure presented requires significant computer resources, but this is not unusual when compared to similar studies by other researchers. Several methods are suggested to reduce the computational times.
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).
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).
Earth radiation budget measurement from a spinning satellite: Conceptual design of detectors
NASA Technical Reports Server (NTRS)
Sromovsky, L. A.; Revercomb, H. E.; Suomi, V. E.
1975-01-01
The conceptual design, sensor characteristics, sensor performance and accuracy, and spacecraft and orbital requirements for a spinning wide-field-of-view earth energy budget detector were investigated. The scientific requirements for measurement of the earth's radiative energy budget are presented. Other topics discussed include the observing system concept, solar constant radiometer design, plane flux wide FOV sensor design, fast active cavity theory, fast active cavity design and error analysis, thermopile detectors as an alternative, pre-flight and in-flight calibration plane, system error summary, and interface requirements.
Steered Molecular Dynamics Simulations Predict Conformational Stability of Glutamate Receptors.
Musgaard, Maria; Biggin, Philip C
2016-09-26
The stability of protein-protein interfaces can be essential for protein function. For ionotropic glutamate receptors, a family of ligand-gated ion channels vital for normal function of the central nervous system, such an interface exists between the extracellular ligand binding domains (LBDs). In the full-length protein, the LBDs are arranged as a dimer of dimers. Agonist binding to the LBDs opens the ion channel, and briefly after activation the receptor desensitizes. Several residues at the LBD dimer interface are known to modulate desensitization, and conformational changes around these residues are believed to be involved in the state transition. The general hypothesis is that the interface is disrupted upon desensitization, and structural evidence suggests that the disruption might be substantial. However, when cross-linking the central part of this interface, functional data suggest that the receptor can still undergo desensitization, contradicting the hypothesis of major interface disruption. Here, we illustrate how opening the dimer interface using steered molecular dynamics (SMD) simulations, and analyzing the work values required, provides a quantitative measure for interface stability. For one subtype of glutamate receptors, which is regulated by ion binding to the dimer interface, we show that opening the interface without ions bound requires less work than with ions present, suggesting that ion binding indeed stabilizes the interface. Likewise, for interface mutants with longer-lived active states, the interface is more stable, while the work required to open the interface is reduced for less active mutants. Moreover, a cross-linked mutant can still undergo initial interface opening motions similar to the native receptor and at similar energetic cost. Thus, our results support that interface opening is involved in desensitization. Furthermore, they provide reconciliation of apparently opposing data and demonstrate that SMD simulations can give relevant biological insight into longer time scale processes without the need for expensive calculations.
Recent Advances in Neural Electrode-Tissue Interfaces.
Woeppel, Kevin; Yang, Qianru; Cui, Xinyan Tracy
2017-12-01
Neurotechnology is facing an exponential growth in the recent decades. Neural electrode-tissue interface research has been well recognized as an instrumental component of neurotechnology development. While satisfactory long-term performance was demonstrated in some applications, such as cochlear implants and deep brain stimulators, more advanced neural electrode devices requiring higher resolution for single unit recording or microstimulation still face significant challenges in reliability and longevity. In this article, we review the most recent findings that contribute to our current understanding of the sources of poor reliability and longevity in neural recording or stimulation, including the material failure, biological tissue response and the interplay between the two. The newly developed characterization tools are introduced from electrophysiology models, molecular and biochemical analysis, material characterization to live imaging. The effective strategies that have been applied to improve the interface are also highlighted. Finally, we discuss the challenges and opportunities in improving the interface and achieving seamless integration between the implanted electrodes and neural tissue both anatomically and functionally.
Research and implementation on improving I/O performance of streaming media storage system
NASA Astrophysics Data System (ADS)
Lu, Zheng-wu; Wang, Yu-de; Jiang, Guo-song
2008-12-01
In this paper, we study the special requirements of a special storage system: streaming media server, and propose a solution to improve I/O performance of RAID storage system. The solution is suitable for streaming media applications. A streaming media storage subsystem includes the I/O interfaces, RAID arrays, I/O scheduling and device drivers. The solution is implemented on the top of the storage subsystem I/O Interface. Storage subsystem is the performance bottlenecks of a streaming media system, and I/O interface directly affect the performance of the storage subsystem. According to theoretical analysis, 64 KB block-size is most appropriate for streaming media applications. We carry out experiment in detail, and verified that the proper block-size really is 64KB. It is in accordance with our analysis. The experiment results also show that by using DMA controller, efficient memory management technology and mailbox interface design mechanism, streaming media storage system achieves a high-speed data throughput.
NASA Technical Reports Server (NTRS)
Ruiz, Ian B.; Burke, Gary R.; Lung, Gerald; Whitaker, William D.; Nowicki, Robert M.
2004-01-01
The Jet Propulsion Laboratory (JPL) has developed a command interface chip-set that primarily consists of two mixed-signal ASICs'; the Command Interface ASIC (CIA) and Analog Interface ASIC (AIA). The Open-systems architecture employed during the design of this chip-set enables its use as both an intelligent gateway between the system's flight computer and the control, actuation, and activation of the spacecraft's loads, valves, and pyrotechnics respectfully as well as the regulator of the spacecraft power bus. Furthermore, the architecture is highly adaptable and employed fault-tolerant design methods enabling a host of other mission uses including reliable remote data collection. The objective of this design is to both provide a needed flight component that meets the stringent environmental requirements of current deep space missions and to add a new element to a growing library that can be used as a standard building block for future missions to the outer planets.
A Programmable Plug & Play Sensor Interface for WSN Applications
Vera, Sergio D.; Bayo, Alberto; Medrano, Nicolás; Calvo, Belén; Celma, Santiago
2011-01-01
Cost reduction in wireless sensor networks (WSN) becomes a priority when extending their application to fields where a great number of sensors is needed, such as habitat monitoring, precision agriculture or diffuse greenhouse emission measurement. In these cases, the use of smart sensors is expensive, consequently requiring the use of low-cost sensors. The solution to convert such generic low-cost sensors into intelligent ones leads to the implementation of a versatile system with enhanced processing and storage capabilities to attain a plug and play electronic interface able to adapt to all the sensors used. This paper focuses on this issue and presents a low-voltage plug & play reprogrammable interface capable of adapting to different sensor types and achieving an optimum reading performance for every sensor. The proposed interface, which includes both electronic and software elements so that it can be easily integrated in WSN nodes, is described and experimental test results to validate its performance are given. PMID:22164118
Intelligent systems technology infrastructure for integrated systems
NASA Technical Reports Server (NTRS)
Lum, Henry, Jr.
1991-01-01
Significant advances have occurred during the last decade in intelligent systems technologies (a.k.a. knowledge-based systems, KBS) including research, feasibility demonstrations, and technology implementations in operational environments. Evaluation and simulation data obtained to date in real-time operational environments suggest that cost-effective utilization of intelligent systems technologies can be realized for Automated Rendezvous and Capture applications. The successful implementation of these technologies involve a complex system infrastructure integrating the requirements of transportation, vehicle checkout and health management, and communication systems without compromise to systems reliability and performance. The resources that must be invoked to accomplish these tasks include remote ground operations and control, built-in system fault management and control, and intelligent robotics. To ensure long-term evolution and integration of new validated technologies over the lifetime of the vehicle, system interfaces must also be addressed and integrated into the overall system interface requirements. An approach for defining and evaluating the system infrastructures including the testbed currently being used to support the on-going evaluations for the evolutionary Space Station Freedom Data Management System is presented and discussed. Intelligent system technologies discussed include artificial intelligence (real-time replanning and scheduling), high performance computational elements (parallel processors, photonic processors, and neural networks), real-time fault management and control, and system software development tools for rapid prototyping capabilities.
Design of Epidemia - an Ecohealth Informatics System for Integrated Forecasting of Malaria Epidemics
NASA Astrophysics Data System (ADS)
Wimberly, M. C.; Bayabil, E.; Beyane, B.; Bishaw, M.; Henebry, G. M.; Lemma, A.; Liu, Y.; Merkord, C. L.; Mihretie, A.; Senay, G. B.; Yalew, W.
2014-12-01
Early warning of the timing and locations of malaria epidemics can facilitate the targeting of resources for prevention and emergency response. In response to this need, we are developing the Epidemic Prognosis Incorporating Disease and Environmental Monitoring for Integrated Assessment (EPIDEMIA) computer system. The system incorporates software for capturing, processing, and integrating environmental and epidemiological data from multiple sources; data assimilation techniques that continually update models and forecasts; and a web-based interface that makes the resulting information available to public health decision makers. This technology will enable forecasts based on lagged responses to environmental risk factors as well as information about recent trends in malaria cases. Environmental driving variables will include a variety of remote-sensed hydrological indicators. EPIDEMIA will be implemented and tested in the Amhara Region of Ethiopia in collaboration with local stakeholders. We conducted an initial co-design workshop in July 2014 that included environmental scientists, software engineers, and participants from the NGO, academic, and public health sectors in Ethiopia. A prototype of the EPIDEMIA web interface was presented and a requirements analysis was conducted to characterize the main use cases for the public health community, identify the critical data requirements for malaria risk modeling, and develop of a list of baseline features for the public health interface. Several critical system features were identified, including a secure web-based interface for uploading and validating surveillance data; a flexible query system to allow retrieval of environmental and epidemiological data summaries as tables, charts, and maps; and an alert system to provide automatic warnings in response to environmental and epidemiological risk factors for malaria. Future system development will involve a cycle of implementation, training, usability testing, and upgrading. This innovative translational bioinformatics approach will allow us to assess the practical effectiveness of these tools as we continually improve the technologies.
Shuttle infrared telescope facility (SIRTF) preliminary design study
NASA Technical Reports Server (NTRS)
1976-01-01
An overall picture of the SIRTF system is first presented, including the telescope, focal plane instruments, cryogen supply, shuttle and spacelab support subsystems, mechanical and data interfaces with the vehicles, ground support equipment, and system requirements. The optical, mechanical, and thermal characteristics of the telescope are then evaluated, followed by a description of the SIRTF internal stabilization subsystem and its interface with the IPS. Expected performance in the shuttle environment is considered. Tradeoff studies are described, including the Gregorian versus the Cassegrain telescope, aperture diameter tradeoff, a CCD versus an image dissector for the star tracker, the large ambient telescope versus the SIRTF, and a dedicated gimbal versus the IPS. Operations from integration through launch and recovery are also discussed and cost estimates for the program are presented.
Ghanakota, Phani; van Vlijmen, Herman; Sherman, Woody; Beuming, Thijs
2018-04-23
The ability to target protein-protein interactions (PPIs) with small molecule inhibitors offers great promise in expanding the druggable target space and addressing a broad range of untreated diseases. However, due to their nature and function of interacting with protein partners, PPI interfaces tend to extend over large surfaces without the typical pockets of enzymes and receptors. These features present unique challenges for small molecule inhibitor design. As such, determining whether a particular PPI of interest could be pursued with a small molecule discovery strategy requires an understanding of the characteristics of the PPI interface and whether it has hotspots that can be leveraged by small molecules to achieve desired potency. Here, we assess the ability of mixed-solvent molecular dynamic (MSMD) simulations to detect hotspots at PPI interfaces. MSMD simulations using three cosolvents (acetonitrile, isopropanol, and pyrimidine) were performed on a large test set of 21 PPI targets that have been experimentally validated by small molecule inhibitors. We compare MSMD, which includes explicit solvent and full protein flexibility, to a simpler approach that does not include dynamics or explicit solvent (SiteMap) and find that MSMD simulations reveal additional information about the characteristics of these targets and the ability for small molecules to inhibit the PPI interface. In the few cases were MSMD simulations did not detect hotspots, we explore the shortcomings of this technique and propose future improvements. Finally, using Interleukin-2 as an example, we highlight the advantage of the MSMD approach for detecting transient cryptic druggable pockets that exists at PPI interfaces.
Duffy, Fergal J; O'Donovan, Darragh; Devocelle, Marc; Moran, Niamh; O'Connell, David J; Shields, Denis C
2015-03-23
Protein-protein and protein-peptide interactions are responsible for the vast majority of biological functions in vivo, but targeting these interactions with small molecules has historically been difficult. What is required are efficient combined computational and experimental screening methods to choose among a number of potential protein interfaces worthy of targeting lead macrocyclic compounds for further investigation. To achieve this, we have generated combinatorial 3D virtual libraries of short disulfide-bonded peptides and compared them to pharmacophore models of important protein-protein and protein-peptide structures, including short linear motifs (SLiMs), protein-binding peptides, and turn structures at protein-protein interfaces, built from 3D models available in the Protein Data Bank. We prepared a total of 372 reference pharmacophores, which were matched against 108,659 multiconformer cyclic peptides. After normalization to exclude nonspecific cyclic peptides, the top hits notably are enriched for mimetics of turn structures, including a turn at the interaction surface of human α thrombin, and also feature several protein-binding peptides. The top cyclic peptide hits also cover the critical "hot spot" interaction sites predicted from the interaction crystal structure. We have validated our method by testing cyclic peptides predicted to inhibit thrombin, a key protein in the blood coagulation pathway of important therapeutic interest, identifying a cyclic peptide inhibitor with lead-like activity. We conclude that protein interfaces most readily targetable by cyclic peptides and related macrocyclic drugs may be identified computationally among a set of candidate interfaces, accelerating the choice of interfaces against which lead compounds may be screened.
10 CFR 73.58 - Safety/security interface requirements for nuclear power reactors.
Code of Federal Regulations, 2010 CFR
2010-01-01
... 10 Energy 2 2010-01-01 2010-01-01 false Safety/security interface requirements for nuclear power reactors. 73.58 Section 73.58 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) PHYSICAL PROTECTION OF... requirements for nuclear power reactors. (a) Each operating nuclear power reactor licensee with a license...
10 CFR 73.58 - Safety/security interface requirements for nuclear power reactors.
Code of Federal Regulations, 2013 CFR
2013-01-01
... 10 Energy 2 2013-01-01 2013-01-01 false Safety/security interface requirements for nuclear power reactors. 73.58 Section 73.58 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) PHYSICAL PROTECTION OF... requirements for nuclear power reactors. (a) Each operating nuclear power reactor licensee with a license...
10 CFR 73.58 - Safety/security interface requirements for nuclear power reactors.
Code of Federal Regulations, 2014 CFR
2014-01-01
... 10 Energy 2 2014-01-01 2014-01-01 false Safety/security interface requirements for nuclear power reactors. 73.58 Section 73.58 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) PHYSICAL PROTECTION OF... requirements for nuclear power reactors. (a) Each operating nuclear power reactor licensee with a license...
10 CFR 73.58 - Safety/security interface requirements for nuclear power reactors.
Code of Federal Regulations, 2011 CFR
2011-01-01
... 10 Energy 2 2011-01-01 2011-01-01 false Safety/security interface requirements for nuclear power reactors. 73.58 Section 73.58 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) PHYSICAL PROTECTION OF... requirements for nuclear power reactors. (a) Each operating nuclear power reactor licensee with a license...
10 CFR 73.58 - Safety/security interface requirements for nuclear power reactors.
Code of Federal Regulations, 2012 CFR
2012-01-01
... 10 Energy 2 2012-01-01 2012-01-01 false Safety/security interface requirements for nuclear power reactors. 73.58 Section 73.58 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) PHYSICAL PROTECTION OF... requirements for nuclear power reactors. (a) Each operating nuclear power reactor licensee with a license...
HomPPI: a class of sequence homology based protein-protein interface prediction methods
2011-01-01
Background Although homology-based methods are among the most widely used methods for predicting the structure and function of proteins, the question as to whether interface sequence conservation can be effectively exploited in predicting protein-protein interfaces has been a subject of debate. Results We studied more than 300,000 pair-wise alignments of protein sequences from structurally characterized protein complexes, including both obligate and transient complexes. We identified sequence similarity criteria required for accurate homology-based inference of interface residues in a query protein sequence. Based on these analyses, we developed HomPPI, a class of sequence homology-based methods for predicting protein-protein interface residues. We present two variants of HomPPI: (i) NPS-HomPPI (Non partner-specific HomPPI), which can be used to predict interface residues of a query protein in the absence of knowledge of the interaction partner; and (ii) PS-HomPPI (Partner-specific HomPPI), which can be used to predict the interface residues of a query protein with a specific target protein. Our experiments on a benchmark dataset of obligate homodimeric complexes show that NPS-HomPPI can reliably predict protein-protein interface residues in a given protein, with an average correlation coefficient (CC) of 0.76, sensitivity of 0.83, and specificity of 0.78, when sequence homologs of the query protein can be reliably identified. NPS-HomPPI also reliably predicts the interface residues of intrinsically disordered proteins. Our experiments suggest that NPS-HomPPI is competitive with several state-of-the-art interface prediction servers including those that exploit the structure of the query proteins. The partner-specific classifier, PS-HomPPI can, on a large dataset of transient complexes, predict the interface residues of a query protein with a specific target, with a CC of 0.65, sensitivity of 0.69, and specificity of 0.70, when homologs of both the query and the target can be reliably identified. The HomPPI web server is available at http://homppi.cs.iastate.edu/. Conclusions Sequence homology-based methods offer a class of computationally efficient and reliable approaches for predicting the protein-protein interface residues that participate in either obligate or transient interactions. For query proteins involved in transient interactions, the reliability of interface residue prediction can be improved by exploiting knowledge of putative interaction partners. PMID:21682895
An Intuitive Graphical User Interface for Small UAS
2013-05-01
reduced from two to one . The stock displays, including video with text overlay on one and FalconView on the other, are replaced with a single, graphics...INTRODUCTION Tactical UAVs such as the Raven, Puma and Wasp are often used by dismounted warfighters on missions that require a high degree of mobility by...the operators on the ground. The current ground control stations (GCS) for the Wasp, Raven and Puma tactical UAVs require two people and two user
Product assurance technology for custom LSI/VLSI electronics
NASA Technical Reports Server (NTRS)
Buehler, M. G.; Blaes, B. R.; Jennings, G. A.; Moore, B. T.; Nixon, R. H.; Pina, C. A.; Sayah, H. R.; Sievers, M. W.; Stahlberg, N. F.
1985-01-01
The technology for obtaining custom integrated circuits from CMOS-bulk silicon foundries using a universal set of layout rules is presented. The technical efforts were guided by the requirement to develop a 3 micron CMOS test chip for the Combined Release and Radiation Effects Satellite (CRRES). This chip contains both analog and digital circuits. The development employed all the elements required to obtain custom circuits from silicon foundries, including circuit design, foundry interfacing, circuit test, and circuit qualification.
1988-01-01
system requirements, design guidelines, and interface requirements has been prepared and included as Volume II of this Task 1 topical report. The Volume ...WAESD-TR-88-0002 Conceptual Design Of A Space-Based Multimegawatt MHD Power System ffA«kjjjjjTfc Task 1 Topical Report Volume I: Technical...Space-Based Multimegawatt MHD Power System: Task 1 Topical Report, Volume I: Technical Discussion Personal Author: Dana, RA. Corporate Author Or
Description of waste pretreatment and interfacing systems dynamic simulation model
DOE Office of Scientific and Technical Information (OSTI.GOV)
Garbrick, D.J.; Zimmerman, B.D.
1995-05-01
The Waste Pretreatment and Interfacing Systems Dynamic Simulation Model was created to investigate the required pretreatment facility processing rates for both high level and low level waste so that the vitrification of tank waste can be completed according to the milestones defined in the Tri-Party Agreement (TPA). In order to achieve this objective, the processes upstream and downstream of the pretreatment facilities must also be included. The simulation model starts with retrieval of tank waste and ends with vitrification for both low level and high level wastes. This report describes the results of three simulation cases: one based on suggestedmore » average facility processing rates, one with facility rates determined so that approximately 6 new DSTs are required, and one with facility rates determined so that approximately no new DSTs are required. It appears, based on the simulation results, that reasonable facility processing rates can be selected so that no new DSTs are required by the TWRS program. However, this conclusion must be viewed with respect to the modeling assumptions, described in detail in the report. Also included in the report, in an appendix, are results of two sensitivity cases: one with glass plant water recycle steams recycled versus not recycled, and one employing the TPA SST retrieval schedule versus a more uniform SST retrieval schedule. Both recycling and retrieval schedule appear to have a significant impact on overall tank usage.« less
NASA Technical Reports Server (NTRS)
Chupp, Raymond E.; Hendricks, Robert C.; Lattime, Scott B.; Steinetz, Bruce M.
2006-01-01
Clearance control is of paramount importance to turbomachinery designers and is required to meet today's aggressive power output, efficiency, and operational life goals. Excessive clearances lead to losses in cycle efficiency, flow instabilities, and hot gas ingestion into disk cavities. Insufficient clearances limit coolant flows and cause interface rubbing, overheating downstream components and damaging interfaces, thus limiting component life. Designers have put renewed attention on clearance control, as it is often the most cost effective method to enhance system performance. Advanced concepts and proper material selection continue to play important roles in maintaining interface clearances to enable the system to meet design goals. This work presents an overview of turbomachinery sealing to control clearances. Areas covered include: characteristics of gas and steam turbine sealing applications and environments, benefits of sealing, types of standard static and dynamics seals, advanced seal designs, as well as life and limitations issues.
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).
A PLATFORM FOR CONTEXTUAL MOBILE PRIVACY
2017-12-01
cen- tralizes all permission management functionality. “Streamline the interface to require less touches to find the information about permissions...APPROVED FOR PUBLIC RELEASE; DISTRIBUTION UNLIMITED STINFO COPY AIR FORCE RESEARCH LABORATORY INFORMATION DIRECTORATE...public, including foreign nationals. Copies may be obtained from the Defense Technical Information Center (DTIC) (http://www.dtic.mil). AFRL
ERIC Educational Resources Information Center
Combs, Joseph, Jr.
1995-01-01
Reviews the Total Library Computerization program, which can be used to manage small to midsized libraries. Discusses costs; operating system requirements; security features; user-interface styles; and system modules including online cataloging, circulation, serials control, acquisitions, authorities control, and interlibrary loan. (Author/JMV)
Bringing Text Display Digital Radio to Consumers with Hearing Loss
ERIC Educational Resources Information Center
Sheffield, Ellyn G.; Starling, Michael; Schwab, Daniel
2011-01-01
Radio is migrating to digital transmission, expanding its offerings to include captioning for individuals with hearing loss. Text display radio requires a large amount of word throughput with minimal screen display area, making good user interface design crucial to its success. In two experiments, we presented hearing, hard-of-hearing, and deaf…
2015-01-27
placed on the user by the required tasks. Design areas that are of concern include seating , input and output device location and design , ambient...software, hardware, and workspace design for the test function of operability that influence operator performance in a computer-based system. 15...PRESENTATION ................... 23 APPENDIX A. SAMPLE DESIGN CHECKLISTS ...................................... A-1 B. SAMPLE TASK CHECKLISTS
Rhizobium–legume symbiosis shares an exocytotic pathway required for arbuscule formation
Ivanov, Sergey; Fedorova, Elena E.; Limpens, Erik; De Mita, Stephane; Genre, Andrea; Bonfante, Paola; Bisseling, Ton
2012-01-01
Endosymbiotic interactions are characterized by the formation of specialized membrane compartments, by the host in which the microbes are hosted, in an intracellular manner. Two well-studied examples, which are of major agricultural and ecological importance, are the widespread arbuscular mycorrhizal symbiosis and the Rhizobium–legume symbiosis. In both symbioses, the specialized host membrane that surrounds the microbes forms a symbiotic interface, which facilitates the exchange of, for example, nutrients in a controlled manner and, therefore, forms the heart of endosymbiosis. Despite their key importance, the molecular and cellular mechanisms underlying the formation of these membrane interfaces are largely unknown. Recent studies strongly suggest that the Rhizobium–legume symbiosis coopted a signaling pathway, including receptor, from the more ancient arbuscular mycorrhizal symbiosis to form a symbiotic interface. Here, we show that two highly homologous exocytotic vesicle-associated membrane proteins (VAMPs) are required for formation of the symbiotic membrane interface in both interactions. Silencing of these Medicago VAMP72 genes has a minor effect on nonsymbiotic plant development and nodule formation. However, it blocks symbiosome as well as arbuscule formation, whereas root colonization by the microbes is not affected. Identification of these VAMP72s as common symbiotic regulators in exocytotic vesicle trafficking suggests that the ancient exocytotic pathway forming the periarbuscular membrane compartment has also been coopted in the Rhizobium–legume symbiosis. PMID:22566631
Srinivasan, Sathish; Danjoux, Jean-Pierre
2018-01-01
The number of laser in situ keratomileusis (LASIK) procedures is continuing to rise. Since its first application for correcting simple refractive errors over 25 years ago, the role of LASIK has extended to treat other conditions, including postkeratoplasty astigmatism/ametropia, postcataract surgery refractive error and presbyopia, among others. The long-term effectiveness, predictability and safety have been well established by many large studies. However, due to the creation of a potential interface between the flap and the underlying stroma, interface complications such as infectious keratitis, diffuse lamellar keratitis and epithelial ingrowth may occur. Post-LASIK epithelial ingrowth (PLEI) is an uncommon complication that usually arises during the early postoperative period. The reported incidence of PLEI ranged from 0%–3.9% in primary treatment to 10%–20% in retreatment cases. It can cause a wide spectrum of clinical presentations, ranging from asymptomatic interface changes to severe visual impairment and flap melt requiring keratoplasty. PLEI can usually be treated with mechanical debridement of the affected interface; however, additional interventions, such as alcohol, mitomycin C, fibrin glue, ocular hydrogel sealant, neodymium:yttriumaluminum garnet laser and amniotic membrane graft, may be required for recurrent or refractory cases. The aims of this review are to determine the prevalence and risk factors of PLEI; to describe its pathogenesis and clinical features and to summarise the therapeutic armamentarium and the visual outcome of PLEI. PMID:29657982
Ting, Darren Shu Jeng; Srinivasan, Sathish; Danjoux, Jean-Pierre
2018-01-01
The number of laser in situ keratomileusis (LASIK) procedures is continuing to rise. Since its first application for correcting simple refractive errors over 25 years ago, the role of LASIK has extended to treat other conditions, including postkeratoplasty astigmatism/ametropia, postcataract surgery refractive error and presbyopia, among others. The long-term effectiveness, predictability and safety have been well established by many large studies. However, due to the creation of a potential interface between the flap and the underlying stroma, interface complications such as infectious keratitis, diffuse lamellar keratitis and epithelial ingrowth may occur. Post-LASIK epithelial ingrowth (PLEI) is an uncommon complication that usually arises during the early postoperative period. The reported incidence of PLEI ranged from 0%-3.9% in primary treatment to 10%-20% in retreatment cases. It can cause a wide spectrum of clinical presentations, ranging from asymptomatic interface changes to severe visual impairment and flap melt requiring keratoplasty. PLEI can usually be treated with mechanical debridement of the affected interface; however, additional interventions, such as alcohol, mitomycin C, fibrin glue, ocular hydrogel sealant, neodymium:yttriumaluminum garnet laser and amniotic membrane graft, may be required for recurrent or refractory cases. The aims of this review are to determine the prevalence and risk factors of PLEI; to describe its pathogenesis and clinical features and to summarise the therapeutic armamentarium and the visual outcome of PLEI.
Kobayashi, Norio; Ishii, Manabu; Takahashi, Satoshi; Mochizuki, Yoshiki; Matsushima, Akihiro; Toyoda, Tetsuro
2011-07-01
Global cloud frameworks for bioinformatics research databases become huge and heterogeneous; solutions face various diametric challenges comprising cross-integration, retrieval, security and openness. To address this, as of March 2011 organizations including RIKEN published 192 mammalian, plant and protein life sciences databases having 8.2 million data records, integrated as Linked Open or Private Data (LOD/LPD) using SciNetS.org, the Scientists' Networking System. The huge quantity of linked data this database integration framework covers is based on the Semantic Web, where researchers collaborate by managing metadata across public and private databases in a secured data space. This outstripped the data query capacity of existing interface tools like SPARQL. Actual research also requires specialized tools for data analysis using raw original data. To solve these challenges, in December 2009 we developed the lightweight Semantic-JSON interface to access each fragment of linked and raw life sciences data securely under the control of programming languages popularly used by bioinformaticians such as Perl and Ruby. Researchers successfully used the interface across 28 million semantic relationships for biological applications including genome design, sequence processing, inference over phenotype databases, full-text search indexing and human-readable contents like ontology and LOD tree viewers. Semantic-JSON services of SciNetS.org are provided at http://semanticjson.org.
Integrating Human Factors into Crew Exploration Vehicle Design
NASA Technical Reports Server (NTRS)
Whitmore, Mihriban; Baggerman, Susan; Campbell, paul
2007-01-01
With NASA's new Vision for Exploration to send humans beyond Earth orbit, it is critical to consider the human as a system that demands early and continuous user involvement, and an iterative prototype/test/redesign process. Addressing human-system interface issues early on can be very cost effective even cost reducing when performed early in the design and development cycle. To achieve this goal within Crew Exploration Vehicle (CEV) Project Office, human engineering (HE) team is formed. Key tasks are to apply HE requirements and guidelines to hardware/software, and provide HE design, analysis and evaluation of crew interfaces. Initial activities included many practice-orientated evaluations using low-fidelity CEV mock-ups. What follows is a description of such evaluations that focused on a HE requirement regarding Net Habitable Volume (NHV). NHV is defined as the total remaining pressurized volume available to on-orbit crew after accounting for the loss of volume due to deployed hardware and structural inefficiencies which decrease functional volume. The goal of the NHV evaluations was to develop requirements providing sufficient CEV NHV for crewmembers to live and perform tasks in support of mission goals. Efforts included development of a standard NHV calculation method using computer models and physical mockups, and crew/ stakeholder evaluations. Nine stakeholders and ten crewmembers participated in the unsuited evaluations. Six crewmembers also participated in a suited evaluation. The mock-up was outfitted with volumetric representation of sub-systems such as seats, and stowage bags. Thirteen scenarios were developed to represent mission/crew tasks and considered to be primary volume drivers (e.g., suit donning) for the CEV. Unsuited evaluations included a structured walkthrough of these tasks. Suited evaluations included timed donning of the existing launch and entry suit to simulate a contingency scenario followed by doffing/ stowing of the suits. All mockup evaluations were videotaped. Structured questionnaires were used to document user interface issues and volume impacts of layout configuration. Computer model and physical measures of the NHV agreed within 1 percent. This included measurement of the gross habitable volume, subtraction of intrusive volumes, and other non-habitable spaces. Calculation method developed was validated as a standard means of measuring NHV, and was recommended as a verification method for the NHV requirements. Evaluations confirmed that there was adequate volume for unsuited scenarios and suit donning/ doffing activity. Seats, suit design stowage and waste hygiene system noted to be critical volume drivers. The low-fidelity mock-up evaluations along with human modeling analysis generated discussions that will lead to high-level systems requirements and human-centered design decisions. This approach allowed HE requirements and operational concepts to evolve in parallel with engineering system concepts and design requirements. As the CEV design matures, these evaluations will continue and help with design decisions, and assessment, verification and validation of HE requirements.
VIRTUAL FRAME BUFFER INTERFACE
NASA Technical Reports Server (NTRS)
Wolfe, T. L.
1994-01-01
Large image processing systems use multiple frame buffers with differing architectures and vendor supplied user interfaces. This variety of architectures and interfaces creates software development, maintenance, and portability problems for application programs. The Virtual Frame Buffer Interface program makes all frame buffers appear as a generic frame buffer with a specified set of characteristics, allowing programmers to write code which will run unmodified on all supported hardware. The Virtual Frame Buffer Interface converts generic commands to actual device commands. The virtual frame buffer consists of a definition of capabilities and FORTRAN subroutines that are called by application programs. The virtual frame buffer routines may be treated as subroutines, logical functions, or integer functions by the application program. Routines are included that allocate and manage hardware resources such as frame buffers, monitors, video switches, trackballs, tablets and joysticks; access image memory planes; and perform alphanumeric font or text generation. The subroutines for the various "real" frame buffers are in separate VAX/VMS shared libraries allowing modification, correction or enhancement of the virtual interface without affecting application programs. The Virtual Frame Buffer Interface program was developed in FORTRAN 77 for a DEC VAX 11/780 or a DEC VAX 11/750 under VMS 4.X. It supports ADAGE IK3000, DEANZA IP8500, Low Resolution RAMTEK 9460, and High Resolution RAMTEK 9460 Frame Buffers. It has a central memory requirement of approximately 150K. This program was developed in 1985.
The weak interfaces within tough natural composites: experiments on three types of nacre.
Khayer Dastjerdi, Ahmad; Rabiei, Reza; Barthelat, Francois
2013-03-01
Mineralization is a typical strategy used in natural materials to achieve high stiffness and hardness for structural functions such as skeletal support, protection or predation. High mineral content generally leads to brittleness, yet natural materials such as bone, mollusk shells or glass sponge achieve relatively high toughness considering the weakness of their constituents through intricate microstructures. In particular, nanometers thick organic interfaces organized in micro-architectures play a key role in providing toughness by various processes including crack deflection, crack bridging or energy dissipation. While these interfaces are critical in these materials, their composition, structure and mechanics is often poorly understood. In this work we focus on nacre, one of the most impressive hard biological materials in terms of toughness. We performed interfacial fracture tests on chevron notched nacre samples from three different species: red abalone, top shell and pearl oyster. We found that the intrinsic toughness of the interfaces is indeed found to be extremely low, in the order of the toughness of the mineral inclusions themselves. Such low toughness is required for the cracks to follow the interfaces, and to deflect and circumvent the mineral tablets. This result highlights the efficacy of toughening mechanisms in natural materials, turning low-toughness inclusions and interfaces into high-performance composites. We found that top shell nacre displayed the highest interfacial toughness, because of higher surface roughness and a more resilient organic material, and also through extrinsic toughening mechanisms including crack deflection, crack bridging and process zone. In the context of biomimetics, the main implication of this finding is that the interface in nacre-like composite does not need to be tough; the extensibility or ductility of the interfaces may be more important than their strength and toughness to produce toughness at the macroscale. Copyright © 2012 Elsevier Ltd. All rights reserved.
Standardized Modular Power Interfaces for Future Space Explorations Missions
NASA Technical Reports Server (NTRS)
Oeftering, Richard
2015-01-01
Earlier studies show that future human explorations missions are composed of multi-vehicle assemblies with interconnected electric power systems. Some vehicles are often intended to serve as flexible multi-purpose or multi-mission platforms. This drives the need for power architectures that can be reconfigured to support this level of flexibility. Power system developmental costs can be reduced, program wide, by utilizing a common set of modular building blocks. Further, there are mission operational and logistics cost benefits of using a common set of modular spares. These benefits are the goals of the Advanced Exploration Systems (AES) Modular Power System (AMPS) project. A common set of modular blocks requires a substantial level of standardization in terms of the Electrical, Data System, and Mechanical interfaces. The AMPS project is developing a set of proposed interface standards that will provide useful guidance for modular hardware developers but not needlessly constrain technology options, or limit future growth in capability. In 2015 the AMPS project focused on standardizing the interfaces between the elements of spacecraft power distribution and energy storage. The development of the modular power standard starts with establishing mission assumptions and ground rules to define design application space. The standards are defined in terms of AMPS objectives including Commonality, Reliability-Availability, Flexibility-Configurability and Supportability-Reusability. The proposed standards are aimed at assembly and sub-assembly level building blocks. AMPS plans to adopt existing standards for spacecraft command and data, software, network interfaces, and electrical power interfaces where applicable. Other standards including structural encapsulation, heat transfer, and fluid transfer, are governed by launch and spacecraft environments and bound by practical limitations of weight and volume. Developing these mechanical interface standards is more difficult but an essential part of defining physical building blocks of modular power. This presentation describes the AMPS projects progress towards standardized modular power interfaces.
Federal Register 2010, 2011, 2012, 2013, 2014
2011-05-23
... Evolution (LTE) broadband standard, specifically at least 3GPP Standard E-UTRA Release 8 and associated... LTE interfaces. These requirements were designed to ensure that networks operated in this spectrum... required LTE interfaces. This requirement will enable the Bureau to monitor network deployment and ensure...
Deepak Condenser Model (DeCoM)
NASA Technical Reports Server (NTRS)
Patel, Deepak
2013-01-01
Development of the DeCoM comes from the requirement of analyzing the performance of a condenser. A component of a loop heat pipe (LHP), the condenser, is interfaced with the radiator in order to reject heat. DeCoM simulates the condenser, with certain input parameters. Systems Improved Numerical Differencing Analyzer (SINDA), a thermal analysis software, calculates the adjoining component temperatures, based on the DeCoM parameters and interface temperatures to the radiator. Application of DeCoM is (at the time of this reporting) restricted to small-scale analysis, without the need for in-depth LHP component integrations. To efficiently develop a model to simulate the LHP condenser, DeCoM was developed to meet this purpose with least complexity. DeCoM is a single-condenser, single-pass simulator for analyzing its behavior. The analysis is done based on the interactions between condenser fluid, the wall, and the interface between the wall and the radiator. DeCoM is based on conservation of energy, two-phase equations, and flow equations. For two-phase, the Lockhart- Martinelli correlation has been used in order to calculate the convection value between fluid and wall. Software such as SINDA (for thermal analysis analysis) and Thermal Desktop (for modeling) are required. DeCoM also includes the ability to implement a condenser into a thermal model with the capability of understanding the code process and being edited to user-specific needs. DeCoM requires no license, and is an open-source code. Advantages to DeCoM include time dependency, reliability, and the ability for the user to view the code process and edit to their needs.
Lowekamp, Bradley C; Chen, David T; Ibáñez, Luis; Blezek, Daniel
2013-01-01
SimpleITK is a new interface to the Insight Segmentation and Registration Toolkit (ITK) designed to facilitate rapid prototyping, education and scientific activities via high level programming languages. ITK is a templated C++ library of image processing algorithms and frameworks for biomedical and other applications, and it was designed to be generic, flexible and extensible. Initially, ITK provided a direct wrapping interface to languages such as Python and Tcl through the WrapITK system. Unlike WrapITK, which exposed ITK's complex templated interface, SimpleITK was designed to provide an easy to use and simplified interface to ITK's algorithms. It includes procedural methods, hides ITK's demand driven pipeline, and provides a template-less layer. Also SimpleITK provides practical conveniences such as binary distribution packages and overloaded operators. Our user-friendly design goals dictated a departure from the direct interface wrapping approach of WrapITK, toward a new facade class structure that only exposes the required functionality, hiding ITK's extensive template use. Internally SimpleITK utilizes a manual description of each filter with code-generation and advanced C++ meta-programming to provide the higher-level interface, bringing the capabilities of ITK to a wider audience. SimpleITK is licensed as open source software library under the Apache License Version 2.0 and more information about downloading it can be found at http://www.simpleitk.org.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Baranowski, S.T.; Culp, L.R.; Jonas, T.S.
1995-12-31
The Clean Air Act Amendments of 1990 require all Phase 1 and 2 utilities to install Continuous Emissions Monitoring Systems (CEMS), which can consist of instrumentation including analyzers and a Data Acquisition and Handling System (DAHS). To meet these requirements, Basin Electric Power Cooperative contracted with Black and Veatch to design and develop a DAHS which would meet all 40 CFR Part 75 requirements. Basin Electric provided the specifications for the DAHS and the graphical user interface, and B and V designed, developed, and installed a DAHS at 3 units at Laramie River Station, 2 units at Antelope Valley Station,more » and 2 units at Leland Olds Station. B and V utilized the existing equipment, adding to it a unique DAHS design. B and V designed and implemented the DAHS which operates in the OS/2 environment to interface with multiple programmable logic controllers. This unique software was written in modular form so that multiple programs run in unison, monitoring each other for errors to ensure continuous operation. The reporting structure is flexible to allow for a variety of formats, including those specifically required by the state to meet CAAA guidelines. Today, these seven units are in operation and comply with the CAAA. This paper describes the issues faced during specification, general design, compliance, and implementation of the DAHS at BEPC, including the lessons learned. The continuous emissions monitoring (CEM) system for each unit at BEPC consisted of a set of dilution probe analyzers for measuring SO{sub 2}, NO{sub x}, and CO{sub 2}.« less
Language workbench user interfaces for data analysis
Benson, Victoria M.
2015-01-01
Biological data analysis is frequently performed with command line software. While this practice provides considerable flexibility for computationally savy individuals, such as investigators trained in bioinformatics, this also creates a barrier to the widespread use of data analysis software by investigators trained as biologists and/or clinicians. Workflow systems such as Galaxy and Taverna have been developed to try and provide generic user interfaces that can wrap command line analysis software. These solutions are useful for problems that can be solved with workflows, and that do not require specialized user interfaces. However, some types of analyses can benefit from custom user interfaces. For instance, developing biomarker models from high-throughput data is a type of analysis that can be expressed more succinctly with specialized user interfaces. Here, we show how Language Workbench (LW) technology can be used to model the biomarker development and validation process. We developed a language that models the concepts of Dataset, Endpoint, Feature Selection Method and Classifier. These high-level language concepts map directly to abstractions that analysts who develop biomarker models are familiar with. We found that user interfaces developed in the Meta-Programming System (MPS) LW provide convenient means to configure a biomarker development project, to train models and view the validation statistics. We discuss several advantages of developing user interfaces for data analysis with a LW, including increased interface consistency, portability and extension by language composition. The language developed during this experiment is distributed as an MPS plugin (available at http://campagnelab.org/software/bdval-for-mps/). PMID:25755929
Walsh, Tiffany R
2017-07-18
An in-depth appreciation of how to manipulate the molecular-level recognition between peptides and aqueous materials interfaces, including nanoparticles, will advance technologies based on self-organized metamaterials for photonics and plasmonics, biosensing, catalysis, energy generation and harvesting, and nanomedicine. Exploitation of the materials-selective binding of biomolecules is pivotal to success in these areas and may be particularly key to producing new hierarchically structured biobased materials. These applications could be accomplished by realizing preferential adsorption of a given biomolecule onto one materials composition over another, one surface facet over another, or one crystalline polymorph over another. Deeper knowledge of the aqueous abiotic-biotic interface, to establish clear structure-property relationships in these systems, is needed to meet this goal. In particular, a thorough structural characterization of the surface-adsorbed peptides is essential for establishing these relationships but can often be challenging to accomplish via experimental approaches alone. In addition to myriad existing challenges associated with determining the detailed molecular structure of any molecule adsorbed at an aqueous interface, experimental characterization of materials-binding peptides brings new, complex challenges because many materials-binding peptides are thought to be intrinsically disordered. This means that these peptides are not amenable to experimental techniques that rely on the presence of well-defined secondary structure in the peptide when in the adsorbed state. To address this challenge, and in partnership with experiment, molecular simulations at the atomistic level can bring complementary and critical insights into the origins of this abiotic/biotic recognition and suggest routes for manipulating this phenomenon to realize new types of hybrid materials. For the reasons outlined above, molecular simulation approaches also face challenges in their successful application to model the biotic-abiotic interface, related to several factors. For instance, simulations require a plausible description of the chemistry and the physics of the interface, which comprises two very different states of matter, in the presence of liquid water. Also, it is essential that the conformational ensemble be comprehensively characterized under these conditions; this is especially challenging because intrinsically disordered peptides do not typically admit one single structure or set of structures. Moreover, a plausible structural model of the substrate is required, which may require a high level of detail, even for single-element materials such as Au surfaces or graphene. Developing and applying strategies to make credible predictions of the conformational ensemble of adsorbed peptides and using these to construct structure-property relationships of these interfaces have been the goals of our efforts. We have made substantial progress in developing interatomic potentials for these interfaces and adapting advanced conformational sampling approaches for these purposes. This Account summarizes our progress in the development and deployment of interfacial force fields and molecular simulation techniques for the purpose of elucidating these insights at biomolecule-materials interfaces, using examples from our laboratories ranging from noble-metal interfaces to graphitic substrates (including carbon nanotubes and graphene) and oxide materials (such as titania). In addition to the well-established application areas of plasmonic materials, biosensing, and the production of medical implant materials, we outline new directions for this field that have the potential to bring new advances in areas such as energy materials and regenerative medicine.
NASA Astrophysics Data System (ADS)
Pillans, Luke; Harmer, Jack; Edwards, Tim; Richardson, Lee
2016-05-01
Geolocation is the process of calculating a target position based on bearing and range relative to the known location of the observer. A high performance thermal imager with integrated geolocation functions is a powerful long range targeting device. Firefly is a software defined camera core incorporating a system-on-a-chip processor running the AndroidTM operating system. The processor has a range of industry standard serial interfaces which were used to interface to peripheral devices including a laser rangefinder and a digital magnetic compass. The core has built in Global Positioning System (GPS) which provides the third variable required for geolocation. The graphical capability of Firefly allowed flexibility in the design of the man-machine interface (MMI), so the finished system can give access to extensive functionality without appearing cumbersome or over-complicated to the user. This paper covers both the hardware and software design of the system, including how the camera core influenced the selection of peripheral hardware, and the MMI design process which incorporated user feedback at various stages.
Automatic control of a primary electric thrust subsystem
NASA Technical Reports Server (NTRS)
Macie, T. W.; Macmedan, M. L.
1975-01-01
A concept for automatic control of the thrust subsystem has been developed by JPL and participating NASA Centers. This paper reports on progress in implementing the concept at JPL. Control of the Thrust Subsystem (TSS) is performed by the spacecraft computer command subsystem, and telemetry data is extracted by the spacecraft flight data subsystem. The Data and Control Interface Unit, an element of the TSS, provides the interface with the individual elements of the TSS. The control philosophy and implementation guidelines are presented. Control requirements are listed, and the control mechanism, including the serial digital data intercommunication system, is outlined. The paper summarizes progress to Fall 1974.
NASA Technical Reports Server (NTRS)
1975-01-01
User-oriented panels were formed to examine practical applications of information or services derived from earth orbiting satellites. Topics discussed include: weather and climate; uses of communication; land use planning; agriculture, forest, and range; inland water resources; retractable resources; environmental quality; marine and maritime uses; and materials processing in space. Emphasis was placed on the interface of the space transportation system (STS) with the applications envisioned by the user panels. User requirements were compared with expected STS capabilities in terms of availability, carrying payload to orbit, and estimated costs per launch. Conclusions and recommendations were reported.
Integrated geometry and grid generation system for complex configurations
NASA Technical Reports Server (NTRS)
Akdag, Vedat; Wulf, Armin
1992-01-01
A grid generation system was developed that enables grid generation for complex configurations. The system called ICEM/CFD is described and its role in computational fluid dynamics (CFD) applications is presented. The capabilities of the system include full computer aided design (CAD), grid generation on the actual CAD geometry definition using robust surface projection algorithms, interfacing easily with known CAD packages through common file formats for geometry transfer, grid quality evaluation of the volume grid, coupling boundary condition set-up for block faces with grid topology generation, multi-block grid generation with or without point continuity and block to block interface requirement, and generating grid files directly compatible with known flow solvers. The interactive and integrated approach to the problem of computational grid generation not only substantially reduces manpower time but also increases the flexibility of later grid modifications and enhancements which is required in an environment where CFD is integrated into a product design cycle.
Interior ice/mineral/water interface dynamics (Invited)
NASA Astrophysics Data System (ADS)
Rempel, A. W.
2009-12-01
The search for life begins with the search for liquid water. In our solar system, persistent water reservoirs are invariably found together with ice. On Earth, organisms have evolved to thrive at sub-zero temperatures in ice-bound habitats that have numerous analogues throughout our solar system and beyond. To assess the potential for life requires a thorough investigation of the dynamic interactions within these deposits. Well-established thermodynamic principles govern the stable coexistence of premelted liquid at the interface between ice and other minerals. Foreign constituents are efficiently rejected from the ice crystal lattice and are concentrated in residual liquid regions instead. This gains added importance with the recognition that the most fundamental requirements for survival include a food source and the removal of waste. This talk reviews the astrobiological implications of the availability, behavior, and properties of liquid water in association with the interiors of icy bodies and ice-mineral interfacial regions.
CADBIT II - Computer-Aided Design for Built-In Test. Volume 1
1993-06-01
data provided in the CADBIT I Final Report, as indicated in Figure 1.2. "• CADBIT II IMPLEMENTS SYSTEM CONCEPT, REQUIREMENTS, AND DATA DEVELOPED DURING...CADBIT II software was developed using de facto computer standards including Unix, C, and the X Windows-based OSF/Motif graphical user interface... export connectivity infermation. Design Architect is a package for designers that includes schematic capture, VHDL editor, and libraries of digital
AGUIA: autonomous graphical user interface assembly for clinical trials semantic data services
2010-01-01
Background AGUIA is a front-end web application originally developed to manage clinical, demographic and biomolecular patient data collected during clinical trials at MD Anderson Cancer Center. The diversity of methods involved in patient screening and sample processing generates a variety of data types that require a resource-oriented architecture to capture the associations between the heterogeneous data elements. AGUIA uses a semantic web formalism, resource description framework (RDF), and a bottom-up design of knowledge bases that employ the S3DB tool as the starting point for the client's interface assembly. Methods The data web service, S3DB, meets the necessary requirements of generating the RDF and of explicitly distinguishing the description of the domain from its instantiation, while allowing for continuous editing of both. Furthermore, it uses an HTTP-REST protocol, has a SPARQL endpoint, and has open source availability in the public domain, which facilitates the development and dissemination of this application. However, S3DB alone does not address the issue of representing content in a form that makes sense for domain experts. Results We identified an autonomous set of descriptors, the GBox, that provides user and domain specifications for the graphical user interface. This was achieved by identifying a formalism that makes use of an RDF schema to enable the automatic assembly of graphical user interfaces in a meaningful manner while using only resources native to the client web browser (JavaScript interpreter, document object model). We defined a generalized RDF model such that changes in the graphic descriptors are automatically and immediately (locally) reflected into the configuration of the client's interface application. Conclusions The design patterns identified for the GBox benefit from and reflect the specific requirements of interacting with data generated by clinical trials, and they contain clues for a general purpose solution to the challenge of having interfaces automatically assembled for multiple and volatile views of a domain. By coding AGUIA in JavaScript, for which all browsers include a native interpreter, a solution was found that assembles interfaces that are meaningful to the particular user, and which are also ubiquitous and lightweight, allowing the computational load to be carried by the client's machine. PMID:20977768
Human/Computer Interfacing in Educational Environments.
ERIC Educational Resources Information Center
Sarti, Luigi
1992-01-01
This discussion of educational applications of user interfaces covers the benefits of adopting database techniques in organizing multimedia materials; the evolution of user interface technology, including teletype interfaces, analogic overlay graphics, window interfaces, and adaptive systems; application design problems, including the…
Functioning of the dimeric GABAB receptor extracellular domain revealed by glycan wedge scanning
Rondard, Philippe; Huang, Siluo; Monnier, Carine; Tu, Haijun; Blanchard, Bertrand; Oueslati, Nadia; Malhaire, Fanny; Li, Ying; Trinquet, Eric; Labesse, Gilles; Pin, Jean-Philippe; Liu, Jianfeng
2008-01-01
The G-protein-coupled receptor (GPCR) activated by the neurotransmitter GABA is made up of two subunits, GABAB1 and GABAB2. GABAB1 binds agonists, whereas GABAB2 is required for trafficking GABAB1 to the cell surface, increasing agonist affinity to GABAB1, and activating associated G proteins. These subunits each comprise two domains, a Venus flytrap domain (VFT) and a heptahelical transmembrane domain (7TM). How agonist binding to the GABAB1 VFT leads to GABAB2 7TM activation remains unknown. Here, we used a glycan wedge scanning approach to investigate how the GABAB VFT dimer controls receptor activity. We first identified the dimerization interface using a bioinformatics approach and then showed that introducing an N-glycan at this interface prevents the association of the two subunits and abolishes all activities of GABAB2, including agonist activation of the G protein. We also identified a second region in the VFT where insertion of an N-glycan does not prevent dimerization, but blocks agonist activation of the receptor. These data provide new insight into the function of this prototypical GPCR and demonstrate that a change in the dimerization interface is required for receptor activation. PMID:18388862
SAGE III on ISS Lessons Learned on Thermal Interface Design
NASA Technical Reports Server (NTRS)
Davis, Warren
2015-01-01
The Stratospheric Aerosol and Gas Experiment III (SAGE III) instrument - the fifth in a series of instruments developed for monitoring vertical distribution of aerosols, ozone, and other trace gases in the Earth's stratosphere and troposphere - is currently scheduled for delivery to the International Space Station (ISS) via the SpaceX Dragon vehicle in 2016. The Instrument Adapter Module (IAM), one of many SAGE III subsystems, continuously dissipates a considerable amount of thermal energy during mission operations. Although a portion of this energy is transferred via its large radiator surface area, the majority must be conductively transferred to the ExPRESS Payload Adapter (ExPA) to satisfy thermal mitigation requirements. The baseline IAM-ExPA mechanical interface did not afford the thermal conductance necessary to prevent the IAM from overheating in hot on-orbit cases, and high interfacial conductance was difficult to achieve given the large span between mechanical fasteners, less than stringent flatness specifications, and material usage constraints due to strict contamination requirements. This paper will examine the evolution of the IAM-ExPA thermal interface over the course of three design iterations and will include discussion on design challenges, material selection, testing successes and failures, and lessons learned.
MCC level C formulation requirements. Shuttle TAEM targeting
NASA Technical Reports Server (NTRS)
Carman, G. L.; Montez, M. N.
1980-01-01
The level C requirements for the shuttle orbiter terminal area energy management (TAEM) guidance and flight control functions to be incorporated into the Mission Control Center entry profile planning processor are described. This processor is used for preentry evaluation of the entry through landing maneuvers, and includes a simplified three degree-of-freedom model of the body rotational dynamics that is necessary to account for the effects of attitude response on the trajectory dynamics. This simulation terminates at TAEM-autoland interface.
Space Generic Open Avionics Architecture (SGOAA) reference model technical guide
NASA Technical Reports Server (NTRS)
Wray, Richard B.; Stovall, John R.
1993-01-01
This report presents a full description of the Space Generic Open Avionics Architecture (SGOAA). The SGOAA consists of a generic system architecture for the entities in spacecraft avionics, a generic processing architecture, and a six class model of interfaces in a hardware/software system. The purpose of the SGOAA is to provide an umbrella set of requirements for applying the generic architecture interface model to the design of specific avionics hardware/software systems. The SGOAA defines a generic set of system interface points to facilitate identification of critical interfaces and establishes the requirements for applying appropriate low level detailed implementation standards to those interface points. The generic core avionics system and processing architecture models provided herein are robustly tailorable to specific system applications and provide a platform upon which the interface model is to be applied.
Crew interface specifications preparation for in-flight maintenance and stowage functions
NASA Technical Reports Server (NTRS)
Parker, F. W.; Carlton, B. E.
1972-01-01
The findings and data products developed during the Phase 2 crew interface specification study are presented. Five new NASA general specifications were prepared: operations location coding system for crew interfaces; loose equipment and stowage management requirements; loose equipment and stowage data base information requirements; spacecraft loose equipment stowage drawing requirements; and inflight stowage management data requirements. Additional data was developed defining inflight maintenance processes and related data concepts for inflight troubleshooting, remove/repair/replace and scheduled maintenance activities. The process of maintenance task and equipment definition during spacecraft design and development was also defined and related data concepts were identified for futher development into formal NASA specifications during future follow-on study phases of the contract.
Evolution of MPCV Service Module Propulsion and GNC Interface Requirements
NASA Technical Reports Server (NTRS)
Hickman, Heather K.; Dickens, Kevin W.; Madsen, Jennifer M.; Gutkowski, Jeffrey P.; Ierardo, Nicola; Jaeger, Markus; Lux, Johannes; Freundenberger, John L.; Paisley, Jonathan
2014-01-01
The Orion Multi-Purpose Crew Vehicle Service Module Propulsion Subsystem provides propulsion for the integrated Crew and Service Module. Updates in the exploration architecture between Constellation and MPCV as well as NASA's partnership with the European Space Agency have resulted in design changes to the SM Propulsion Subsystem and updates to the Propulsion interface requirements with Guidance Navigation and Control. This paper focuses on the Propulsion and GNC interface requirement updates between the Constellation Service Module and the European Service Module and how the requirement updates were driven or supported by architecture updates and the desired use of hardware with heritage to United States and European spacecraft for the Exploration Missions, EM-1 and EM-2.
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.
Circling motion and screen edges as an alternative input method for on-screen target manipulation.
Ka, Hyun W; Simpson, Richard C
2017-04-01
To investigate a new alternative interaction method, called circling interface, for manipulating on-screen objects. To specify a target, the user makes a circling motion around the target. To specify a desired pointing command with the circling interface, each edge of the screen is used. The user selects a command before circling the target. To evaluate the circling interface, we conducted an experiment with 16 participants, comparing the performance on pointing tasks with different combinations of selection method (circling interface, physical mouse and dwelling interface) and input device (normal computer mouse, head pointer and joystick mouse emulator). A circling interface is compatible with many types of pointing devices, not requiring physical activation of mouse buttons, and is more efficient than dwell-clicking. Across all common pointing operations, the circling interface had a tendency to produce faster performance with a head-mounted mouse emulator than with a joystick mouse. The performance accuracy of the circling interface outperformed the dwelling interface. It was demonstrated that the circling interface has the potential as another alternative pointing method for selecting and manipulating objects in a graphical user interface. Implications for Rehabilitation A circling interface will improve clinical practice by providing an alternative pointing method that does not require physically activating mouse buttons and is more efficient than dwell-clicking. The Circling interface can also work with AAC devices.
NASA Technical Reports Server (NTRS)
1976-01-01
The interfaces between AMPS Payload No.(TBD) and Spacelab are described. The interfaces specified cover the AMPS physical, electrical, and thermal interfaces that are established to prescribe the standard Spacelab configuration required to perform the mission. If the configuration definition changes due to change of Spacelab equipment model, or serial numbers, then reidentification of the Labcraft payload may be required.
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.
MSFC Propulsion Systems Department Knowledge Management Project
NASA Technical Reports Server (NTRS)
Caraccioli, Paul A.
2007-01-01
This slide presentation reviews the Knowledge Management (KM) project of the Propulsion Systems Department at Marshall Space Flight Center. KM is needed to support knowledge capture, preservation and to support an information sharing culture. The presentation includes the strategic plan for the KM initiative, the system requirements, the technology description, the User Interface and custom features, and a search demonstration.
Reducing Lifecycle Sustainment Costs
2015-05-01
ahead of government systems – Specific O&S needs in government: depots, software centers, VAMOSC/ ERP interfaces Implications of ERP Systems...funding is not allocated for its implementation . Technology Refresh often requires non-recurring engineering investment, but the Working Capital Funds...VAMOSC Systems – Cost and Software Data Reports (CSDRs) • Contractor Logistics Support Contracts • Includes subcontractor reporting – Effects of
RoMPS concept review automatic control of space robot, volume 2
NASA Technical Reports Server (NTRS)
Dobbs, M. E.
1991-01-01
Topics related to robot operated materials processing in space (RoMPS) are presented in view graph form and include: (1) system concept; (2) Hitchhiker Interface Requirements; (3) robot axis control concepts; (4) Autonomous Experiment Management System; (5) Zymate Robot Controller; (6) Southwest SC-4 Computer; (7) oven control housekeeping data; and (8) power distribution.
Carol Rice
1995-01-01
Dr. Biswell's approach to fire management balanced fire prevention, suppression, and fuel management. Dr. Biswell maintained that with increased support for fire prevention and fuel management, several profound changes would be anticipated, including a decrease in the number of wildfires, as well as a decrease in requirements for suppression. Interested persons...
High density tape/head interface study
NASA Technical Reports Server (NTRS)
Csengery, L. C.
1983-01-01
The high energy (H sub c approximately or = to 650 oersteds) tapes and high track density (84 tracks per inch) heads investigated had, as its goal, the definition of optimum combinations of head and tape, including the control required of their interfacial dynamics that would enable the manufacture of high rate (150 Mbps) digital tape recorders for unattended space flight.
Requirements Specification Language (RSL) and supporting tools
NASA Technical Reports Server (NTRS)
Frincke, Deborah; Wolber, Dave; Fisher, Gene; Cohen, Gerald C.
1992-01-01
This document describes a general purpose Requirement Specification Language (RSL). RSL is a hybrid of features found in several popular requirement specification languages. The purpose of RSL is to describe precisely the external structure of a system comprised of hardware, software, and human processing elements. To overcome the deficiencies of informal specification languages, RSL includes facilities for mathematical specification. Two RSL interface tools are described. The Browser view contains a complete document with all details of the objects and operations. The Dataflow view is a specialized, operation-centered depiction of a specification that shows how specified operations relate in terms of inputs and outputs.
Ver-i-Fus: an integrated access control and information monitoring and management system
NASA Astrophysics Data System (ADS)
Thomopoulos, Stelios C.; Reisman, James G.; Papelis, Yiannis E.
1997-01-01
This paper describes the Ver-i-Fus Integrated Access Control and Information Monitoring and Management (IAC-I2M) system that INTELNET Inc. has developed. The Ver-i-Fus IAC-I2M system has been designed to meet the most stringent security and information monitoring requirements while allowing two- way communication between the user and the system. The systems offers a flexible interface that permits to integrate practically any sensing device, or combination of sensing devices, including a live-scan fingerprint reader, thus providing biometrics verification for enhanced security. Different configurations of the system provide solutions to different sets of access control problems. The re-configurable hardware interface, tied together with biometrics verification and a flexible interface that allows to integrate Ver-i-Fus with an MIS, provide an integrated solution to security, time and attendance, labor monitoring, production monitoring, and payroll applications.
A programmable controller based on CAN field bus embedded microprocessor and FPGA
NASA Astrophysics Data System (ADS)
Cai, Qizhong; Guo, Yifeng; Chen, Wenhei; Wang, Mingtao
2008-10-01
One kind of new programmable controller(PLC) is introduced in this paper. The advanced embedded microprocessor and Field-Programmable Gate Array (FPGA) device are applied in the PLC system. The PLC system structure was presented in this paper. It includes 32 bits Advanced RISC Machines (ARM) embedded microprocessor as control core, FPGA as control arithmetic coprocessor and CAN bus as data communication criteria protocol connected the host controller and its various extension modules. It is detailed given that the circuits and working principle, IiO interface circuit between ARM and FPGA and interface circuit between ARM and FPGA coprocessor. Furthermore the interface circuit diagrams between various modules are written. In addition, it is introduced that ladder chart program how to control the transfer info of control arithmetic part in FPGA coprocessor. The PLC, through nearly two months of operation to meet the design of the basic requirements.
Atomically engineered epitaxial anatase TiO2 metal-semiconductor field-effect transistors
NASA Astrophysics Data System (ADS)
Kim, Brian S. Y.; Minohara, Makoto; Hikita, Yasuyuki; Bell, Christopher; Hwang, Harold Y.
2018-03-01
Anatase TiO2 is a promising material for a vast array of electronic, energy, and environmental applications, including photocatalysis, photovoltaics, and sensors. A key requirement for these applications is the ability to modulate its electrical properties without dominant dopant scattering and while maintaining high carrier mobility. Here, we demonstrate the room temperature field-effect modulation of the conducting epitaxial interface between anatase TiO2 and LaAlO3 (001), which arises for LaO-terminated LaAlO3, while the AlO2-terminated interface is insulating. This approach, together with the metal-semiconductor field-effect transistor geometry, naturally bypasses the gate/channel interface traps, resulting in a high field-effect mobility μ FE of 3.14 cm2 (V s)-1 approaching 98% of the corresponding Hall mobility μ Hall . Accordingly, the channel conductivity is modulated over 6 orders of magnitude over a gate voltage range of ˜4 V.
Communication interface and graphic module for audiometry equipment.
Gutiérrez Martinez, Josefina; Barraza López, Fernando; Guadarrama Lara, Alberto; Núñez Gaona, Marco Antonio; Delgado Esquerra, Ruth; Gutiérrez Farfán, Ileana
2009-01-01
The National Rehabilitation Institute (INR) in Mexico City purchased 12 Madsen Orbiter 922 audiometers in 2006. While this audiometer is excellent for diagnosing the degree and type of hearing loss, it has presented problems in transfering, saving and printing the results of special tests and logoaudiometry from audiometer to workstation with the NOAH-3 system. The data are lost when the audiometer is turned off or a new patient is captured. There is no database storing and, shortly after the results have been printed on the thermal paper, the audiograms are erased. This problem was addressed by designing and implementing the InterAudio (AAMS) communication and graphical interface. The limitations and scope of the Automatic Audiometric Measurement System were analyzed, then a search of technical information was performed that included the resources for designing, developing and implementing the transfer interface, the user's graphical module requirements, and the tools for printing and saving the study.
Evaluation of Different Speech and Touch Interfaces to In-Vehicle Music Retrieval Systems
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
Arnold, Corey W; Wallace, W Dean; Chen, Shawn; Oh, Andrea; Abtin, Fereidoun; Genshaft, Scott; Binder, Scott; Aberle, Denise; Enzmann, Dieter
2016-01-01
The current paradigm of cancer diagnosis involves uncoordinated communication of findings from radiology and pathology to downstream physicians. Discordance between these findings can require additional time from downstream users to resolve, or given incorrect resolution, may adversely impact treatment decisions. To mitigate this problem, we developed a web-based system, called RadPath, for correlating and integrating radiology and pathology reporting. RadPath includes interfaces to our institution's clinical information systems, which are used to retrieve reports, images, and test results that are structured into an interactive compendium for a diagnostic patient case. The system includes an editing interface for physicians, allowing for the inclusion of additional clinical data, as well as the ability to retrospectively correlate and contextualize imaging findings following pathology diagnosis. During pilot deployment and testing over the course of 1 year, physicians at our institution have completed 60 RadPath cases, requiring an average of 128 seconds from a radiologist and an average of 93 seconds from a pathologist per case. Several technical and workflow challenges were encountered during development, including interfacing with diverse clinical information systems, automatically structuring report contents, and determining the appropriate physicians to create RadPath summaries. Reaction to RadPath has been positive, with users valuing the system's ability to consolidate diagnostic information. With the increasing complexity of medicine and the movement toward team-based disease management, there is a need for improved clinical communication and information exchange. RadPath provides a platform for generating coherent and correlated diagnostic summaries in cancer diagnosis with minimal additional effort from physicians. Copyright © 2016 The Association of University Radiologists. Published by Elsevier Inc. All rights reserved.
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.
An ovine model of cerebral catheter venography for implantation of an endovascular neural interface.
Oxley, Thomas James; Opie, Nicholas Lachlan; Rind, Gil Simon; Liyanage, Kishan; John, Sam Emmanuel; Ronayne, Stephen; McDonald, Alan James; Dornom, Anthony; Lovell, Timothy John Haynes; Mitchell, Peter John; Bennett, Iwan; Bauquier, Sebastien; Warne, Leon Norris; Steward, Chris; Grayden, David Bruce; Desmond, Patricia; Davis, Stephen M; O'Brien, Terence John; May, Clive N
2018-04-01
OBJECTIVE Neural interface technology may enable the development of novel therapies to treat neurological conditions, including motor prostheses for spinal cord injury. Intracranial neural interfaces currently require a craniotomy to achieve implantation and may result in chronic tissue inflammation. Novel approaches are required that achieve less invasive implantation methods while maintaining high spatial resolution. An endovascular stent electrode array avoids direct brain trauma and is able to record electrocorticography in local cortical tissue from within the venous vasculature. The motor area in sheep runs in a parasagittal plane immediately adjacent to the superior sagittal sinus (SSS). The authors aimed to develop a sheep model of cerebral venography that would enable validation of an endovascular neural interface. METHODS Cerebral catheter venography was performed in 39 consecutive sheep. Contrast-enhanced MRI of the brain was performed on 13 animals. Multiple telescoping coaxial catheter systems were assessed to determine the largest wide-bore delivery catheter that could be delivered into the anterior SSS. Measurements of SSS diameter and distance from the motor area were taken. The location of the motor area was determined in relation to lateral and superior projections of digital subtraction venography images and confirmed on MRI. RESULTS The venous pathway from the common jugular vein (7.4 mm) to the anterior SSS (1.2 mm) was technically challenging to selectively catheterize. The SSS coursed immediately adjacent to the motor cortex (< 1 mm) for a length of 40 mm, or the anterior half of the SSS. Attempted access with 5-Fr and 6-Fr delivery catheters was associated with longer procedure times and higher complication rates. A 4-Fr catheter (internal lumen diameter 1.1 mm) was successful in accessing the SSS in 100% of cases with no associated complications. Complications included procedure-related venous dissection in two major areas: the torcular herophili, and the anterior formation of the SSS. The bifurcation of the cruciate sulcal veins with the SSS was a reliable predictor of the commencement of the motor area. CONCLUSIONS The ovine model for cerebral catheter venography has generalizability to the human cerebral venous system in relation to motor cortex location. This novel model may facilitate the development of the novel field of endovascular neural interfaces that may include preclinical investigations for cortical recording applications such as paralysis and epilepsy, as well as other potential applications in neuromodulation.
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.
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.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Vondy, D.R.; Fowler, T.B.; Cunningham, G.W.
1979-07-01
User input data requirements are presented for certain special processors in a nuclear reactor computation system. These processors generally read data in formatted form and generate binary interface data files. Some data processing is done to convert from the user oriented form to the interface file forms. The VENTURE diffusion theory neutronics code and other computation modules in this system use the interface data files which are generated.
A validated methodology for determination of laboratory instrument computer interface efficacy
NASA Astrophysics Data System (ADS)
1984-12-01
This report is intended to provide a methodology for determining when, and for which instruments, direct interfacing of laboratory instrument and laboratory computers is beneficial. This methodology has been developed to assist the Tri-Service Medical Information Systems Program Office in making future decisions regarding laboratory instrument interfaces. We have calculated the time savings required to reach a break-even point for a range of instrument interface prices and corresponding average annual costs. The break-even analyses used empirical data to estimate the number of data points run per day that are required to meet the break-even point. The results indicate, for example, that at a purchase price of $3,000, an instrument interface will be cost-effective if the instrument is utilized for at least 154 data points per day if operated in the continuous mode, or 216 points per day if operated in the discrete mode. Although this model can help to ensure that instrument interfaces are cost effective, additional information should be considered in making the interface decisions. A reduction in results transcription errors may be a major benefit of instrument interfacing.
A universal data access and protocol integration mechanism for smart home
NASA Astrophysics Data System (ADS)
Shao, Pengfei; Yang, Qi; Zhang, Xuan
2013-03-01
With the lack of standardized or completely missing communication interfaces in home electronics, there is no perfect solution to address every aspect in smart homes based on existing protocols and technologies. In addition, the central control unit (CCU) of smart home system working point-to-point between the multiple application interfaces and the underlying hardware interfaces leads to its complicated architecture and unpleasant performance. A flexible data access and protocol integration mechanism is required. The current paper offers a universal, comprehensive data access and protocol integration mechanism for a smart home. The universal mechanism works as a middleware adapter with unified agreements of the communication interfaces and protocols, offers an abstraction of the application level from the hardware specific and decoupling the hardware interface modules from the application level. Further abstraction for the application interfaces and the underlying hardware interfaces are executed based on adaption layer to provide unified interfaces for more flexible user applications and hardware protocol integration. This new universal mechanism fundamentally changes the architecture of the smart home and in some way meets the practical requirement of smart homes more flexible and desirable.
Integrating interface slicing into software engineering processes
NASA Technical Reports Server (NTRS)
Beck, Jon
1993-01-01
Interface slicing is a tool which was developed to facilitate software engineering. As previously presented, it was described in terms of its techniques and mechanisms. The integration of interface slicing into specific software engineering activities is considered by discussing a number of potential applications of interface slicing. The applications discussed specifically address the problems, issues, or concerns raised in a previous project. Because a complete interface slicer is still under development, these applications must be phrased in future tenses. Nonetheless, the interface slicing techniques which were presented can be implemented using current compiler and static analysis technology. Whether implemented as a standalone tool or as a module in an integrated development or reverse engineering environment, they require analysis no more complex than that required for current system development environments. By contrast, conventional slicing is a methodology which, while showing much promise and intuitive appeal, has yet to be fully implemented in a production language environment despite 12 years of development.
Requirements Document for Development of a Livermore Tomography Tools Interface
DOE Office of Scientific and Technical Information (OSTI.GOV)
Seetho, I. M.
In this document, we outline an exercise performed at LLNL to evaluate the user interface deficits of a LLNL-developed CT reconstruction software package, Livermore Tomography Tools (LTT). We observe that a difficult-to-use command line interface and the lack of support functions compound to generate a bottleneck in the CT reconstruction process when input parameters to key functions are not well known. Through the exercise of systems engineering best practices, we generate key performance parameters for a LTT interface refresh, and specify a combination of back-end (“test-mode” functions) and front-end (graphical user interface visualization and command scripting tools) solutions to LTT’smore » poor user interface that aim to mitigate issues and lower costs associated with CT reconstruction using LTT. Key functional and non-functional requirements and risk mitigation strategies for the solution are outlined and discussed.« less
HFI Bolometer Detectors Programmatic CDR
NASA Technical Reports Server (NTRS)
Lange, Andrew E.
2002-01-01
Programmatic Critical Design Review (CDR) of the High Frequency Instrument (HFI) Bolometer Detector on the Planck Surveyor is presented. The topics include: 1) Scientific Requirements and Goals; 2) Silicon Nitride Micromesh 'Spider-Web' Bolometers; 3) Sub-Orbital Heritage: BOOMERANG; 4) Noise stability demonstrated in BOOMERANG; 5) Instrument Partners; 6) Bolometer Environment on Planck/HFI; 7) Bolometer Modules; and 8) Mechanical Interface. Also included are the status of the receivables and delivery plans with Europe. This paper is presented in viewgraph form.
Application-Program-Installer Builder
NASA Technical Reports Server (NTRS)
Wolgast, Paul; Demore, Martha; Lowik, Paul
2007-01-01
A computer program builds application programming interfaces (APIs) and related software components for installing and uninstalling application programs in any of a variety of computers and operating systems that support the Java programming language in its binary form. This program is partly similar in function to commercial (e.g., Install-Shield) software. This program is intended to enable satisfaction of a quasi-industry-standard set of requirements for a set of APIs that would enable such installation and uninstallation and that would avoid the pitfalls that are commonly encountered during installation of software. The requirements include the following: 1) Properly detecting prerequisites to an application program before performing the installation; 2) Properly registering component requirements; 3) Correctly measuring the required hard-disk space, including accounting for prerequisite components that have already been installed; and 4) Correctly uninstalling an application program. Correct uninstallation includes (1) detecting whether any component of the program to be removed is required by another program, (2) not removing that component, and (3) deleting references to requirements of the to-be-removed program for components of other programs so that those components can be properly removed at a later time.
Guidelines for mission integration, a summary report
NASA Technical Reports Server (NTRS)
1979-01-01
Guidelines are presented for instrument/experiment developers concerning hardware design, flight verification, and operations and mission implementation requirements. Interface requirements between the STS and instruments/experiments are defined. Interface constraints and design guidelines are presented along with integrated payload requirements for Spacelab Missions 1, 2, and 3. Interim data are suggested for use during hardware development until more detailed information is developed when a complete mission and an integrated payload system are defined. Safety requirements, flight verification requirements, and operations procedures are defined.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Steich, D J; Brugger, S T; Kallman, J S
2000-02-01
This final report describes our efforts on the Three-Dimensional Massively Parallel CEM Technologies LDRD project (97-ERD-009). Significant need exists for more advanced time domain computational electromagnetics modeling. Bookkeeping details and modifying inflexible software constitute a vast majority of the effort required to address such needs. The required effort escalates rapidly as problem complexity increases. For example, hybrid meshes requiring hybrid numerics on massively parallel platforms (MPPs). This project attempts to alleviate the above limitations by investigating flexible abstractions for these numerical algorithms on MPPs using object-oriented methods, providing a programming environment insulating physics from bookkeeping. The three major design iterationsmore » during the project, known as TIGER-I to TIGER-III, are discussed. Each version of TIGER is briefly discussed along with lessons learned during the development and implementation. An Application Programming Interface (API) of the object-oriented interface for Tiger-III is included in three appendices. The three appendices contain the Utilities, Entity-Attribute, and Mesh libraries developed during the project. The API libraries represent a snapshot of our latest attempt at insulated the physics from the bookkeeping.« less
A Generic Inner-Loop Control Law Structure for Six-Degree-of-Freedom Conceptual Aircraft Design
NASA Technical Reports Server (NTRS)
Cox, Timothy H.; Cotting, M. Christopher
2005-01-01
A generic control system framework for both real-time and batch six-degree-of-freedom simulations is presented. This framework uses a simplified dynamic inversion technique to allow for stabilization and control of any type of aircraft at the pilot interface level. The simulation, designed primarily for the real-time simulation environment, also can be run in a batch mode through a simple guidance interface. Direct vehicle-state acceleration feedback is required with the simplified dynamic inversion technique. The estimation of surface effectiveness within real-time simulation timing constraints also is required. The generic framework provides easily modifiable control variables, allowing flexibility in the variables that the pilot commands. A direct control allocation scheme is used to command aircraft effectors. Primary uses for this system include conceptual and preliminary design of aircraft, when vehicle models are rapidly changing and knowledge of vehicle six-degree-of-freedom performance is required. A simulated airbreathing hypersonic vehicle and simulated high-performance fighter aircraft are used to demonstrate the flexibility and utility of the control system.
A Generic Inner-Loop Control Law Structure for Six-Degree-of-Freedom Conceptual Aircraft Design
NASA Technical Reports Server (NTRS)
Cox, Timothy H.; Cotting, Christopher
2005-01-01
A generic control system framework for both real-time and batch six-degree-of-freedom (6-DOF) simulations is presented. This framework uses a simplified dynamic inversion technique to allow for stabilization and control of any type of aircraft at the pilot interface level. The simulation, designed primarily for the real-time simulation environment, also can be run in a batch mode through a simple guidance interface. Direct vehicle-state acceleration feedback is required with the simplified dynamic inversion technique. The estimation of surface effectiveness within real-time simulation timing constraints also is required. The generic framework provides easily modifiable control variables, allowing flexibility in the variables that the pilot commands. A direct control allocation scheme is used to command aircraft effectors. Primary uses for this system include conceptual and preliminary design of aircraft, when vehicle models are rapidly changing and knowledge of vehicle 6-DOF performance is required. A simulated airbreathing hypersonic vehicle and simulated high-performance fighter aircraft are used to demonstrate the flexibility and utility of the control system.
Comparison of helmet-mounted display designs in support of wayfinding
NASA Astrophysics Data System (ADS)
Kumagai, Jason K.; Massel, Lisa; Tack, David; Bossi, Linda
2003-09-01
The Canadian Soldier Information Requirements Technology Demonstration (SIREQ TD) soldier modernization research and development program has conducted experiments to help determine the types and amount of information needed to support wayfinding across a range of terrain environments, the most effective display modality for providing the information (visual, auditory or tactile) that will minimize conflict with other infantry tasks, and to optimize interface design. In this study, seven different visual helmet-mounted display (HMD) designs were developed based on soldier feedback from previous studies. The displays and an in-service compass condition were contrasted to investigate how the visual HMD interfaces influenced navigation performance. Displays varied with respect to their information content, frame of reference, point of view, and display features. Twelve male infantry soldiers used all eight experimental conditions to locate bearings to waypoints. From a constant location, participants were required to face waypoints presented at offset bearings of 25, 65, and 120 degrees. Performance measures included time to identify waypoints, accuracy, and head misdirection errors. Subjective measures of performance included ratings of ease of use, acceptance for land navigation, and mental demand. Comments were collected to identify likes, dislikes and possible improvements required for HMDs. Results underlined the potential performance enhancement of GPS-based navigation with HMDs, the requirement for explicit directional information, the desirability of both analog and digital information, the performance benefits of an egocentric frame of reference, the merit of a forward field of view, and the desirability of a guide to help landmark. Implications for the information requirements and human factors design of HMDs for land-based navigational tasks are discussed.
2014-01-01
Background Clinical practice guidelines are useful for physicians, and guidelines are available on the Internet from various websites such as Vidal Recos. However, these guidelines are long and difficult to read, especially during consultation. Similar difficulties have been encountered with drug summaries of product characteristics. In a previous work, we have proposed an iconic language (called VCM, for Visualization of Concepts in Medicine) for representing patient conditions, treatments and laboratory tests, and we have used these icons to design a user interface that graphically indexes summaries of product characteristics. In the current study, our objective was to design and evaluate an iconic user interface for the consultation of clinical practice guidelines by physicians. Methods Focus groups of physicians were set up to identify the difficulties encountered when reading guidelines. Icons were integrated into Vidal Recos, taking human factors into account. The resulting interface includes a graphical summary and an iconic indexation of the guideline. The new interface was evaluated. We compared the response times and the number of errors recorded when physicians answered questions about two clinical scenarios using the interactive iconic interface or a textual interface. Users’ perceived usability was evaluated with the System Usability Scale. Results The main difficulties encountered by physicians when reading guidelines were obtaining an overview and finding recommendations for patients corresponding to “particular cases”. We designed a graphical interface for guideline consultation, using icons to identify particular cases and providing a graphical summary of the icons organized by anatomy and etiology. The evaluation showed that physicians gave clinical responses more rapidly with the iconic interface than the textual interface (25.2 seconds versus 45.6, p < 0.05). The physicians appreciated the new interface, and the System Usability Scale score value was 75 (between good and excellent). Conclusion An interactive iconic interface can provide physicians with an overview of clinical practice guidelines, and can decrease the time required to access the content of such guidelines. PMID:25158762
Pereira, Suzanne; Hassler, Sylvain; Hamek, Saliha; Boog, César; Leroy, Nicolas; Beuscart-Zéphir, Marie-Catherine; Favre, Madeleine; Venot, Alain; Duclos, Catherine; Lamy, Jean-Baptiste
2014-08-26
Clinical practice guidelines are useful for physicians, and guidelines are available on the Internet from various websites such as Vidal Recos. However, these guidelines are long and difficult to read, especially during consultation. Similar difficulties have been encountered with drug summaries of product characteristics. In a previous work, we have proposed an iconic language (called VCM, for Visualization of Concepts in Medicine) for representing patient conditions, treatments and laboratory tests, and we have used these icons to design a user interface that graphically indexes summaries of product characteristics. In the current study, our objective was to design and evaluate an iconic user interface for the consultation of clinical practice guidelines by physicians. Focus groups of physicians were set up to identify the difficulties encountered when reading guidelines. Icons were integrated into Vidal Recos, taking human factors into account. The resulting interface includes a graphical summary and an iconic indexation of the guideline. The new interface was evaluated. We compared the response times and the number of errors recorded when physicians answered questions about two clinical scenarios using the interactive iconic interface or a textual interface. Users' perceived usability was evaluated with the System Usability Scale. The main difficulties encountered by physicians when reading guidelines were obtaining an overview and finding recommendations for patients corresponding to "particular cases". We designed a graphical interface for guideline consultation, using icons to identify particular cases and providing a graphical summary of the icons organized by anatomy and etiology. The evaluation showed that physicians gave clinical responses more rapidly with the iconic interface than the textual interface (25.2 seconds versus 45.6, p < 0.05). The physicians appreciated the new interface, and the System Usability Scale score value was 75 (between good and excellent). An interactive iconic interface can provide physicians with an overview of clinical practice guidelines, and can decrease the time required to access the content of such guidelines.
Ion dehydration controls adsorption at the micellar interface: hydrotropic ions.
Lima, Filipe S; Andrade, Marcos F C; Mortara, Laura; Gustavo Dias, Luís; Cuccovia, Iolanda M; Chaimovich, Hernan
2017-11-22
The properties of ionic micelles depend on the nature of the counterion, and these effects become more evident as the ion adsorption at the interface increases. Prediction of the relative extent of ion adsorption is required for rational design of ionic micellar aggregates. Unlike the well understood adsorption of monatomic ions, the adsorption of polyatomic ions is not easily predicted. We combined experimental and computational methods to evaluate the affinity of hydrotropic ions, i.e., ions with polar and apolar regions, to the surface of positively charged micelles. We analyzed cationic micelles of dodecyltrimethylammonium and six hydrotropic counterions: methanesulfonate, trifluoromethanesulfonate, benzenesulfonate, acetate, trifluoroacetate and benzoate. Our results demonstrated that the apolar region of hydrotropic ions had the largest influence on micellar properties. The dehydration of the apolar region of hydrotropic ions upon their adsorption at the micellar interface determined the ion adsorption extension, differently to what was expected based on Collins' law of matching affinities. These results may lead to more general models to describe the adsorption of ions, including polyatomic ions, at the micellar interface.
Rojas, Mario; Ponce, Pedro; Molina, Arturo
2016-08-01
This paper presents the evaluation, under standardized metrics, of alternative input methods to steer and maneuver a semi-autonomous electric wheelchair. The Human-Machine Interface (HMI), which includes a virtual joystick, head movements and speech recognition controls, was designed to facilitate mobility skills for severely disabled people. Thirteen tasks, which are common to all the wheelchair users, were attempted five times by controlling it with the virtual joystick and the hands-free interfaces in different areas for disabled and non-disabled people. Even though the prototype has an intelligent navigation control, based on fuzzy logic and ultrasonic sensors, the evaluation was done without assistance. The scored values showed that both controls, the head movements and the virtual joystick have similar capabilities, 92.3% and 100%, respectively. However, the 54.6% capacity score obtained for the speech control interface indicates the needs of the navigation assistance to accomplish some of the goals. Furthermore, the evaluation time indicates those skills which require more user's training with the interface and specifications to improve the total performance of the wheelchair.
NASA Astrophysics Data System (ADS)
Miot, Jennyfer; Benzerara, Karim; Kappler, Andreas
2014-05-01
Microbe-mineral interactions occur in diverse modern environments, from the deep sea and subsurface rocks to soils and surface aquatic environments. They may have played a central role in the geochemical cycling of major (e.g., C, Fe, Ca, Mn, S, P) and trace (e.g., Ni, Mo, As, Cr) elements over Earth's history. Such interactions include electron transfer at the microbe-mineral interface that left traces in the rock record. Geomicrobiology consists in studying interactions at these organic-mineral interfaces in modern samples and looking for traces of past microbe-mineral interactions recorded in ancient rocks. Specific tools are required to probe these interfaces and to understand the mechanisms of interaction between microbes and minerals from the scale of the biofilm to the nanometer scale. In this review, we focus on recent advances in electron microscopy, in particular in cryoelectron microscopy, and on a panel of electrochemical and synchrotron-based methods that have recently provided new understanding and imaging of the microbe-mineral interface, ultimately opening new fields to be explored.
Earth Observatory Satellite system definition study. Report 6: Space shuttle interfaces/utilization
NASA Technical Reports Server (NTRS)
1974-01-01
An analysis was conducted to determine the compatibility of the Earth Observatory Satellite (EOS) with the space shuttle. The mechanical interfaces and provisions required for a launch or retrieval of the EOS by the space shuttle are summarized. The space shuttle flight support equipment required for the operation is defined. Diagrams of the space shuttle in various configurations are provised to show the mission capability with the EOS. The subjects considered are as follows: (1) structural and mechanical interfaces, (2) spacecraft retention and deployment, (3) spacecraft retrieval, (4) electrical interfaces, (5) payload shuttle operations, (6) shuttle mode cost analysis, (7) shuttle orbit trades, and (8) safety considerations.
Development of Miniaturized Optimized Smart Sensors (MOSS) for space plasmas
NASA Technical Reports Server (NTRS)
Young, D. T.
1993-01-01
The cost of space plasma sensors is high for several reasons: (1) Most are one-of-a-kind and state-of-the-art, (2) the cost of launch to orbit is high, (3) ruggedness and reliability requirements lead to costly development and test programs, and (4) overhead is added by overly elaborate or generalized spacecraft interface requirements. Possible approaches to reducing costs include development of small 'sensors' (defined as including all necessary optics, detectors, and related electronics) that will ultimately lead to cheaper missions by reducing (2), improving (3), and, through work with spacecraft designers, reducing (4). Despite this logical approach, there is no guarantee that smaller sensors are necessarily either better or cheaper. We have previously advocated applying analytical 'quality factors' to plasma sensors (and spacecraft) and have begun to develop miniaturized particle optical systems by applying quantitative optimization criteria. We are currently designing a Miniaturized Optimized Smart Sensor (MOSS) in which miniaturized electronics (e.g., employing new power supply topology and extensive us of gate arrays and hybrid circuits) are fully integrated with newly developed particle optics to give significant savings in volume and mass. The goal of the SwRI MOSS program is development of a fully self-contained and functional plasma sensor weighing 1 lb and requiring 1 W. MOSS will require only a typical spacecraft DC power source (e.g., 30 V) and command/data interfaces in order to be fully functional, and will provide measurement capabilities comparable in most ways to current sensors.
Using a data base management system for modelling SSME test history data
NASA Technical Reports Server (NTRS)
Abernethy, K.
1985-01-01
The usefulness of a data base management system (DBMS) for modelling historical test data for the complete series of static test firings for the Space Shuttle Main Engine (SSME) was assessed. From an analysis of user data base query requirements, it became clear that a relational DMBS which included a relationally complete query language would permit a model satisfying the query requirements. Representative models and sample queries are discussed. A list of environment-particular evaluation criteria for the desired DBMS was constructed; these criteria include requirements in the areas of user-interface complexity, program independence, flexibility, modifiability, and output capability. The evaluation process included the construction of several prototype data bases for user assessement. The systems studied, representing the three major DBMS conceptual models, were: MIRADS, a hierarchical system; DMS-1100, a CODASYL-based network system; ORACLE, a relational system; and DATATRIEVE, a relational-type system.
Railroad track inspection interface demonstration : final report.
DOT National Transportation Integrated Search
2016-01-01
This project developed a track data user interface utilizing the Google Glass optical display device. The interface allows the user : to recall data stored remotely and view the data on the Google Glass. The technical effort required developing a com...
Kinjo, Akira R; Nakamura, Haruki
2013-01-01
Protein functions are mediated by interactions between proteins and other molecules. One useful approach to analyze protein functions is to compare and classify the structures of interaction interfaces of proteins. Here, we describe the procedures for compiling a database of interface structures and efficiently comparing the interface structures. To do so requires a good understanding of the data structures of the Protein Data Bank (PDB). Therefore, we also provide a detailed account of the PDB exchange dictionary necessary for extracting data that are relevant for analyzing interaction interfaces and secondary structures. We identify recurring structural motifs by classifying similar interface structures, and we define a coarse-grained representation of supersecondary structures (SSS) which represents a sequence of two or three secondary structure elements including their relative orientations as a string of four to seven letters. By examining the correspondence between structural motifs and SSS strings, we show that no SSS string has particularly high propensity to be found interaction interfaces in general, indicating any SSS can be used as a binding interface. When individual structural motifs are examined, there are some SSS strings that have high propensity for particular groups of structural motifs. In addition, it is shown that while the SSS strings found in particular structural motifs for nonpolymer and protein interfaces are as abundant as in other structural motifs that belong to the same subunit, structural motifs for nucleic acid interfaces exhibit somewhat stronger preference for SSS strings. In regard to protein folds, many motif-specific SSS strings were found across many folds, suggesting that SSS may be a useful description to investigate the universality of ligand binding modes.
Kobayashi, Norio; Ishii, Manabu; Takahashi, Satoshi; Mochizuki, Yoshiki; Matsushima, Akihiro; Toyoda, Tetsuro
2011-01-01
Global cloud frameworks for bioinformatics research databases become huge and heterogeneous; solutions face various diametric challenges comprising cross-integration, retrieval, security and openness. To address this, as of March 2011 organizations including RIKEN published 192 mammalian, plant and protein life sciences databases having 8.2 million data records, integrated as Linked Open or Private Data (LOD/LPD) using SciNetS.org, the Scientists' Networking System. The huge quantity of linked data this database integration framework covers is based on the Semantic Web, where researchers collaborate by managing metadata across public and private databases in a secured data space. This outstripped the data query capacity of existing interface tools like SPARQL. Actual research also requires specialized tools for data analysis using raw original data. To solve these challenges, in December 2009 we developed the lightweight Semantic-JSON interface to access each fragment of linked and raw life sciences data securely under the control of programming languages popularly used by bioinformaticians such as Perl and Ruby. Researchers successfully used the interface across 28 million semantic relationships for biological applications including genome design, sequence processing, inference over phenotype databases, full-text search indexing and human-readable contents like ontology and LOD tree viewers. Semantic-JSON services of SciNetS.org are provided at http://semanticjson.org. PMID:21632604
Electro-optic architecture (EOA) for sensors and actuators in aircraft propulsion systems
NASA Technical Reports Server (NTRS)
Glomb, W. L., Jr.
1989-01-01
Results of a study to design an optimal architecture for electro-optical sensing and control in advanced aircraft and space systems are described. The propulsion full authority digital Electronic Engine Control (EEC) was the focus for the study. The recommended architecture is an on-engine EEC which contains electro-optic interface circuits for fiber-optic sensors on the engine. Size and weight are reduced by multiplexing arrays of functionally similar sensors on a pair of optical fibers to common electro-optical interfaces. The architecture contains common, multiplex interfaces to seven sensor groups: (1) self luminous sensors; (2) high temperatures; (3) low temperatures; (4) speeds and flows; (5) vibration; (6) pressures; and (7) mechanical positions. Nine distinct fiber-optic sensor types were found to provide these sensing functions: (1) continuous wave (CW) intensity modulators; (2) time division multiplexing (TDM) digital optic codeplates; (3) time division multiplexing (TDM) analog self-referenced sensors; (4) wavelength division multiplexing (WDM) digital optic code plates; (5) wavelength division multiplexing (WDM) analog self-referenced intensity modulators; (6) analog optical spectral shifters; (7) self-luminous bodies; (8) coherent optical interferometers; and (9) remote electrical sensors. The report includes the results of a trade study including engine sensor requirements, environment, the basic sensor types, and relevant evaluation criteria. These figures of merit for the candidate interface types were calculated from the data supplied by leading manufacturers of fiber-optic sensors.
NASA Technical Reports Server (NTRS)
Flores, Sarah L.; Chapman, Bruce D.; Tung, Waye W.; Zheng, Yang
2011-01-01
This new interface will enable Principal Investigators (PIs), as well as UAVSAR (Uninhabited Aerial Vehicle Synthetic Aperture Radar) members to do their own flight planning and time estimation without having to request flight lines through the science coordinator. It uses an all-in-one Google Maps interface, a JPL hosted database, and PI flight requirements to design an airborne flight plan. The application will enable users to see their own flight plan being constructed interactively through a map interface, and then the flight planning software will generate all the files necessary for the flight. Afterward, the UAVSAR team can then complete the flight request, including calendaring and supplying requisite flight request files in the expected format for processing by NASA s airborne science program. Some of the main features of the interface include drawing flight lines on the map, nudging them, adding them to the current flight plan, and reordering them. The user can also search and select takeoff, landing, and intermediate airports. As the flight plan is constructed, all of its components are constantly being saved to the database, and the estimated flight times are updated. Another feature is the ability to import flight lines from previously saved flight plans. One of the main motivations was to make this Web application as simple and intuitive as possible, while also being dynamic and robust. This Web application can easily be extended to support other airborne instruments.
NASA Technical Reports Server (NTRS)
Zamora, M. A.
1977-01-01
Consumables analysis/crew training simulator interface requirements were defined. Two aspects were investigated: consumables analysis support techniques to crew training simulator for advanced spacecraft programs, and the applicability of the above techniques to the crew training simulator for the space shuttle program in particular.
NASA Technical Reports Server (NTRS)
Malin, Jane T.; Schreckenghost, Debra L.; Woods, David D.; Potter, Scott S.; Johannesen, Leila; Holloway, Matthew; Forbus, Kenneth D.
1991-01-01
Initial results are reported from a multi-year, interdisciplinary effort to provide guidance and assistance for designers of intelligent systems and their user interfaces. The objective is to achieve more effective human-computer interaction (HCI) for systems with real time fault management capabilities. Intelligent fault management systems within the NASA were evaluated for insight into the design of systems with complex HCI. Preliminary results include: (1) a description of real time fault management in aerospace domains; (2) recommendations and examples for improving intelligent systems design and user interface design; (3) identification of issues requiring further research; and (4) recommendations for a development methodology integrating HCI design into intelligent system design.
NASA Technical Reports Server (NTRS)
1975-01-01
The primary objectives during this portion of the extended mission were to assure survival of the spacecraft for a third Mercury encounter through conservation of attitude control gas and to conduct trajectory correction maneuvers (TCMs) as necessary to target the spacecraft for a solar occultation zone pass. Special support activities included TCMs 6 and 7 conducted on October 30, 1974 and on February 12-13, 1975, respectively. This period also saw the DSN interface organization involved in (1) the allocation of sufficient coverage to assure accurate orbit determination solutions, (2) monitoring of DSN implementation for Viking to assure maintenance of compatible interfaces and capabilities required for Mariner 10, and (3) the development of encounter coverage, sequences, and readiness test plans.
Lowekamp, Bradley C.; Chen, David T.; Ibáñez, Luis; Blezek, Daniel
2013-01-01
SimpleITK is a new interface to the Insight Segmentation and Registration Toolkit (ITK) designed to facilitate rapid prototyping, education and scientific activities via high level programming languages. ITK is a templated C++ library of image processing algorithms and frameworks for biomedical and other applications, and it was designed to be generic, flexible and extensible. Initially, ITK provided a direct wrapping interface to languages such as Python and Tcl through the WrapITK system. Unlike WrapITK, which exposed ITK's complex templated interface, SimpleITK was designed to provide an easy to use and simplified interface to ITK's algorithms. It includes procedural methods, hides ITK's demand driven pipeline, and provides a template-less layer. Also SimpleITK provides practical conveniences such as binary distribution packages and overloaded operators. Our user-friendly design goals dictated a departure from the direct interface wrapping approach of WrapITK, toward a new facade class structure that only exposes the required functionality, hiding ITK's extensive template use. Internally SimpleITK utilizes a manual description of each filter with code-generation and advanced C++ meta-programming to provide the higher-level interface, bringing the capabilities of ITK to a wider audience. SimpleITK is licensed as open source software library under the Apache License Version 2.0 and more information about downloading it can be found at http://www.simpleitk.org. PMID:24416015
A Multi-purpose Brain-Computer Interface Output Device
Thompson, David E; Huggins, Jane E
2012-01-01
While brain-computer interfaces (BCIs) are a promising alternative access pathway for individuals with severe motor impairments, many BCI systems are designed as standalone communication and control systems, rather than as interfaces to existing systems built for these purposes. While an individual communication and control system may be powerful or flexible, no single system can compete with the variety of options available in the commercial assistive technology (AT) market. BCIs could instead be used as an interface to these existing AT devices and products, which are designed for improving access and agency of people with disabilities and are highly configurable to individual user needs. However, interfacing with each AT device and program requires significant time and effort on the part of researchers and clinicians. This work presents the Multi-Purpose BCI Output Device (MBOD), a tool to help researchers and clinicians provide BCI control of many forms of AT in a plug-and-play fashion, i.e. without the installation of drivers or software on the AT device, and a proof-of-concept of the practicality of such an approach. The MBOD was designed to meet the goals of target device compatibility, BCI input device compatibility, convenience, and intuitive command structure. The MBOD was successfully used to interface a BCI with multiple AT devices (including two wheelchair seating systems), as well as computers running Windows (XP and 7), Mac and Ubuntu Linux operating systems. PMID:22208120
A multi-purpose brain-computer interface output device.
Thompson, David E; Huggins, Jane E
2011-10-01
While brain-computer interfaces (BCIs) are a promising alternative access pathway for individuals with severe motor impairments, many BCI systems are designed as stand-alone communication and control systems, rather than as interfaces to existing systems built for these purposes. An individual communication and control system may be powerful or flexible, but no single system can compete with the variety of options available in the commercial assistive technology (AT) market. BCls could instead be used as an interface to these existing AT devices and products, which are designed for improving access and agency of people with disabilities and are highly configurable to individual user needs. However, interfacing with each AT device and program requires significant time and effort on the part of researchers and clinicians. This work presents the Multi-Purpose BCI Output Device (MBOD), a tool to help researchers and clinicians provide BCI control of many forms of AT in a plug-and-play fashion, i.e., without the installation of drivers or software on the AT device, and a proof-of-concept of the practicality of such an approach. The MBOD was designed to meet the goals of target device compatibility, BCI input device compatibility, convenience, and intuitive command structure. The MBOD was successfully used to interface a BCI with multiple AT devices (including two wheelchair seating systems), as well as computers running Windows (XP and 7), Mac and Ubuntu Linux operating systems.
Kikinzon, Evgeny; Shashkov, Mikhail Jurievich; Garimella, Rao Veerabhadra
2018-05-29
Real world problems are typically multi-material, combining materials such as gases, liquids and solids that have very different properties. The material interfaces may be fixed in time or can be a part of the solution, as in fluid-structure interactions or air-water dynamics, and therefore move and change shape. In such problems the computational mesh may be non-conformal to interfaces due to complexity of these interfaces, presence of small fractions of materials, or because the mesh does not move with the flow, as in the arbitrary Lagrangian–Eulerian (ALE) methods. In order to solve problems of interest on such meshes, interface reconstructionmore » methods are usually used to recover an approximation of material regions within the cells. For a cell intersecting multiple material regions, these approximations of contained subregions can be considered as single-material subcells in a local mesh that we call a minimesh. In this paper, we discuss some of the requirements that discretization methods have on topological information in the resulting hierarchical meshes and present an approach that allows incorporating the buildup of sufficiently detailed topology into the nested dissections based PLIC-type reconstruction algorithms (e.g. Volume-of-Fluid, Moment-of-Fluid) in an efficient and robust manner. Specifically, we describe the X-MOF interface reconstruction algorithm in 2D, which extends the Moment-Of-Fluid (MOF) method to include the topology of minimeshes created inside of multi-material cells and parent-child relations between corresponding mesh entities on different hierarchy levels. X-MOF retains the property of being local to a cell and not requiring external communication, which makes it suitable for massively parallel applications. Here, we demonstrate some scaling results for the X-MOF implementation in Tangram, a modern interface reconstruction framework for exascale computing.« less
Effective matrix-free preconditioning for the augmented immersed interface method
NASA Astrophysics Data System (ADS)
Xia, Jianlin; Li, Zhilin; Ye, Xin
2015-12-01
We present effective and efficient matrix-free preconditioning techniques for the augmented immersed interface method (AIIM). AIIM has been developed recently and is shown to be very effective for interface problems and problems on irregular domains. GMRES is often used to solve for the augmented variable(s) associated with a Schur complement A in AIIM that is defined along the interface or the irregular boundary. The efficiency of AIIM relies on how quickly the system for A can be solved. For some applications, there are substantial difficulties involved, such as the slow convergence of GMRES (particularly for free boundary and moving interface problems), and the inconvenience in finding a preconditioner (due to the situation that only the products of A and vectors are available). Here, we propose matrix-free structured preconditioning techniques for AIIM via adaptive randomized sampling, using only the products of A and vectors to construct a hierarchically semiseparable matrix approximation to A. Several improvements over existing schemes are shown so as to enhance the efficiency and also avoid potential instability. The significance of the preconditioners includes: (1) they do not require the entries of A or the multiplication of AT with vectors; (2) constructing the preconditioners needs only O (log N) matrix-vector products and O (N) storage, where N is the size of A; (3) applying the preconditioners needs only O (N) flops; (4) they are very flexible and do not require any a priori knowledge of the structure of A. The preconditioners are observed to significantly accelerate the convergence of GMRES, with heuristical justifications of the effectiveness. Comprehensive tests on several important applications are provided, such as Navier-Stokes equations on irregular domains with traction boundary conditions, interface problems in incompressible flows, mixed boundary problems, and free boundary problems. The preconditioning techniques are also useful for several other problems and methods.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Kikinzon, Evgeny; Shashkov, Mikhail Jurievich; Garimella, Rao Veerabhadra
Real world problems are typically multi-material, combining materials such as gases, liquids and solids that have very different properties. The material interfaces may be fixed in time or can be a part of the solution, as in fluid-structure interactions or air-water dynamics, and therefore move and change shape. In such problems the computational mesh may be non-conformal to interfaces due to complexity of these interfaces, presence of small fractions of materials, or because the mesh does not move with the flow, as in the arbitrary Lagrangian–Eulerian (ALE) methods. In order to solve problems of interest on such meshes, interface reconstructionmore » methods are usually used to recover an approximation of material regions within the cells. For a cell intersecting multiple material regions, these approximations of contained subregions can be considered as single-material subcells in a local mesh that we call a minimesh. In this paper, we discuss some of the requirements that discretization methods have on topological information in the resulting hierarchical meshes and present an approach that allows incorporating the buildup of sufficiently detailed topology into the nested dissections based PLIC-type reconstruction algorithms (e.g. Volume-of-Fluid, Moment-of-Fluid) in an efficient and robust manner. Specifically, we describe the X-MOF interface reconstruction algorithm in 2D, which extends the Moment-Of-Fluid (MOF) method to include the topology of minimeshes created inside of multi-material cells and parent-child relations between corresponding mesh entities on different hierarchy levels. X-MOF retains the property of being local to a cell and not requiring external communication, which makes it suitable for massively parallel applications. Here, we demonstrate some scaling results for the X-MOF implementation in Tangram, a modern interface reconstruction framework for exascale computing.« less
A COTS-MQS shipborne EO/IR imaging system
NASA Astrophysics Data System (ADS)
Hutchinson, Mark A.; Miller, John L.; Weaver, James
2005-05-01
The Sea Star SAFIRE is a commercially developed, off the shelf, military qualified system (COTS-MQS) consisting of a 640 by 480 InSb infrared imager, laser rangefinder and visible imager in a gyro-stabilized platform designed for shipborne applications. These applications include search and rescue, surveillance, fire control, fisheries patrol, harbor security, and own-vessel perimeter security and self protection. Particularly challenging considerations unique to shipborne systems include the demanding environment conditions, man-machine interfaces, and effects of atmospheric conditions on sensor performance. Shipborne environmental conditions requiring special attention include electromagnetic fields, as well as resistance to rain, ice and snow, shock, vibration, and salt. Features have been implemented to withstand exposure to water and high humidity; anti-ice/de-ice capability for exposure to snow and ice; wash/wipe of external windows; corrosion resistance for exposure to water and salt spray. A variety of system controller configurations provide man-machine interfaces suitable for operation on ships. EO sensor developments that address areas of haze penetration, glint, and scintillation will be presented.
Clinician-Oriented Access to Data - C.O.A.D.: A Natural Language Interface to a VA DHCP Database
Levy, Christine; Rogers, Elizabeth
1995-01-01
Hospitals collect enormous amounts of data related to the on-going care of patients. Unfortunately, a clinicians access to the data is limited by complexities of the database structure and/or programming skills required to access the database. The COAD project attempts to bridge the gap between the clinical user's need for specific information from the database, and the wealth of data residing in the hospital information system. The project design includes a natural language interface to data contained in a VA DHCP database. We have developed a prototype which links natural language software to certain DHCP data elements, including, patient demographics, prescriptions, diagnoses, laboratory data, and provider information. English queries can by typed onto the system, and answers to the questions are returned. Future work includes refinement of natural language/DHCP connections to enable more sophisticated queries, and optimization of the system to reduce response time to user questions.
Digital avionics systems - Principles and practices (2nd revised and enlarged edition)
NASA Technical Reports Server (NTRS)
Spitzer, Cary R.
1993-01-01
The state of the art in digital avionics systems is surveyed. The general topics addressed include: establishing avionics system requirements; avionics systems essentials in data bases, crew interfaces, and power; fault tolerance, maintainability, and reliability; architectures; packaging and fitting the system into the aircraft; hardware assessment and validation; software design, assessment, and validation; determining the costs of avionics.
A high speed telemetry data link for an autonomous roving vehicle
NASA Technical Reports Server (NTRS)
Cipolle, D. J.
1980-01-01
A data link system used on a prototype autonomous roving vehicle is described. This system provides a means of acquiring, formatting, and transmitting information on board the vehicle to a controlling computer. Included is a statement of requirements and the design philosophy. Additionally, interfacing with the rover systems is discussed, along with the overall performance of the telemetry link.
ERIC Educational Resources Information Center
Butler, E. Sonny
Much of what librarians do today requires adeptness in creating and manipulating databases. Many new computers bought by libraries every year come packaged with Microsoft Office and include Microsoft Access. This database program features a seamless interface between Microsoft Office's other programs like Word, Excel, and PowerPoint. This book…
Space Segment (SS) and the Navigation User Segment (US) Interface Control Document (ICD)
DOT National Transportation Integrated Search
1993-10-10
This Interface Control Document (ICD) defines the requirements related to the interface between the Space Segment (SS) of the Global Positioning System (GPS) and the Navigation Users Segment of the GPS. 2880k, 154p.
Designing the Instructional Interface.
ERIC Educational Resources Information Center
Lohr, L. L.
2000-01-01
Designing the instructional interface is a challenging endeavor requiring knowledge and skills in instructional and visual design, psychology, human-factors, ergonomic research, computer science, and editorial design. This paper describes the instructional interface, the challenges of its development, and an instructional systems approach to its…
Ground test program for a full-size solar dynamic heat receiver
NASA Technical Reports Server (NTRS)
Sedgwick, L. M.; Kaufmann, K. J.; Mclallin, K. L.; Kerslake, T. W.
1991-01-01
Test hardware, facilities, and procedures were developed to conduct ground testing of a full-size, solar dynamic heat receiver in a partially simulated, low earth orbit environment. The heat receiver was designed to supply 102 kW of thermal energy to a helium and xenon gas mixture continuously over a 94 minute orbit, including up to 36 minutes of eclipse. The purpose of the test program was to quantify the receiver thermodynamic performance, its operating temperatures, and thermal response to changes in environmental and power module interface boundary conditions. The heat receiver was tested in a vacuum chamber using liquid nitrogen cold shrouds and an aperture cold plate. Special test equipment was designed to provide the required ranges in interface boundary conditions that typify those expected or required for operation as part of the solar dynamic power module on the Space Station Freedom. The support hardware includes an infrared quartz lamp heater with 30 independently controllable zones and a closed-Brayton cycle engine simulator to circulate and condition the helium-xenon gas mixture. The test article, test support hardware, facilities, and instrumentation developed to conduct the ground test program are all described.
Ground test program for a full-size solar dynamic heat receiver
NASA Technical Reports Server (NTRS)
Sedgwick, L. M.; Kaufmann, K. J.; Mclallin, K. L.; Kerslake, T. W.
1991-01-01
Test hardware, facilities, and procedures were developed to conduct ground testing of a full size, solar dynamic heat receiver in a partially simulated, low Earth orbit environment. The heat receiver was designed to supply 102 kW of thermal energy to a helium and xenon gas mixture continuously over a 94 minute orbit, including up to 36 minutes of eclipse. The purpose of the test program was to quantify the receiver thermodynamic performance, its operating temperatures, and thermal response to changes in environmental and power module interface boundary conditions. The heat receiver was tested in a vacuum chamber using liquid nitrogen cold shrouds and an aperture cold plate. Special test equipment were designed to provide the required ranges in interface boundary conditions that typify those expected or required for operation as part of the solar dynamic power module on the Space Station Freedom. The support hardware includes an infrared quartz lamp heater with 30 independently controllable zones and a closed Brayton cycle engine simulator to circulate and condition the helium xenon gas mixture. The test article, test support hardware, facilities, and instrumentation developed to conduct the ground test program are all described.
Ground test program for a full-size solar dynamic heat receiver
NASA Astrophysics Data System (ADS)
Sedgwick, L. M.; Kaufmann, K. J.; McLallin, K. L.; Kerslake, T. W.
Test hardware, facilities, and procedures were developed to conduct ground testing of a full-size, solar dynamic heat receiver in a partially simulated, low earth orbit environment. The heat receiver was designed to supply 102 kW of thermal energy to a helium and xenon gas mixture continuously over a 94 minute orbit, including up to 36 minutes of eclipse. The purpose of the test program was to quantify the receiver thermodynamic performance, its operating temperatures, and thermal response to changes in environmental and power module interface boundary conditions. The heat receiver was tested in a vacuum chamber using liquid nitrogen cold shrouds and an aperture cold plate. Special test equipment was designed to provide the required ranges in interface boundary conditions that typify those expected or required for operation as part of the solar dynamic power module on the Space Station Freedom. The support hardware includes an infrared quartz lamp heater with 30 independently controllable zones and a closed-Brayton cycle engine simulator to circulate and condition the helium-xenon gas mixture. The test article, test support hardware, facilities, and instrumentation developed to conduct the ground test program are all described.
NASA Technical Reports Server (NTRS)
Fishkind, Stanley; Harris, Richard N.; Pfeiffer, William A.
1996-01-01
The methodologies of the NASA requirements processing system, originally designed to enhance NASA's customer interface and response time, are reviewed. The response of NASA to the problems associated with the system is presented, and it is shown what was done to facilitate the process and to improve customer relations. The requirements generation system (RGS), a computer-supported client-server system, adopted by NASA is presented. The RGS system is configurable on a per-mission basis and can be structured to allow levels of requirements. The details provided concerning the RGS include the recommended configuration, information on becoming an RGS user and network connectivity worksheets for computer users.
Glanville, Julie M; Duffy, Steven; McCool, Rachael; Varley, Danielle
2014-07-01
Since 2005, International Committee of Medical Journal Editors (ICMJE) member journals have required that clinical trials be registered in publicly available trials registers before they are considered for publication. The research explores whether it is adequate, when searching to inform systematic reviews, to search for relevant clinical trials using only public trials registers and to identify the optimal search approaches in trials registers. A search was conducted in ClinicalTrials.gov and the International Clinical Trials Registry Platform (ICTRP) for research studies that had been included in eight systematic reviews. Four search approaches (highly sensitive, sensitive, precise, and highly precise) were performed using the basic and advanced interfaces in both resources. On average, 84% of studies were not listed in either resource. The largest number of included studies was retrieved in ClinicalTrials.gov and ICTRP when a sensitive search approach was used in the basic interface. The use of the advanced interface maintained or improved sensitivity in 16 of 19 strategies for Clinicaltrials.gov and 8 of 18 for ICTRP. No single search approach was sensitive enough to identify all studies included in the 6 reviews. Trials registers cannot yet be relied upon as the sole means to locate trials for systematic reviews. Trials registers lag behind the major bibliographic databases in terms of their search interfaces. For systematic reviews, trials registers and major bibliographic databases should be searched. Trials registers should be searched using sensitive approaches, and both the registers consulted in this study should be searched.
Simplex GPS and InSAR Inversion Software
NASA Technical Reports Server (NTRS)
Donnellan, Andrea; Parker, Jay W.; Lyzenga, Gregory A.; Pierce, Marlon E.
2012-01-01
Changes in the shape of the Earth's surface can be routinely measured with precisions better than centimeters. Processes below the surface often drive these changes and as a result, investigators require models with inversion methods to characterize the sources. Simplex inverts any combination of GPS (global positioning system), UAVSAR (uninhabited aerial vehicle synthetic aperture radar), and InSAR (interferometric synthetic aperture radar) data simultaneously for elastic response from fault and fluid motions. It can be used to solve for multiple faults and parameters, all of which can be specified or allowed to vary. The software can be used to study long-term tectonic motions and the faults responsible for those motions, or can be used to invert for co-seismic slip from earthquakes. Solutions involving estimation of fault motion and changes in fluid reservoirs such as magma or water are possible. Any arbitrary number of faults or parameters can be considered. Simplex specifically solves for any of location, geometry, fault slip, and expansion/contraction of a single or multiple faults. It inverts GPS and InSAR data for elastic dislocations in a half-space. Slip parameters include strike slip, dip slip, and tensile dislocations. It includes a map interface for both setting up the models and viewing the results. Results, including faults, and observed, computed, and residual displacements, are output in text format, a map interface, and can be exported to KML. The software interfaces with the QuakeTables database allowing a user to select existing fault parameters or data. Simplex can be accessed through the QuakeSim portal graphical user interface or run from a UNIX command line.
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.
Explicit solution techniques for impact with contact constraints
NASA Technical Reports Server (NTRS)
Mccarty, Robert E.
1993-01-01
Modern military aircraft transparency systems, windshields and canopies, are complex systems which must meet a large and rapidly growing number of requirements. Many of these transparency system requirements are conflicting, presenting difficult balances which must be achieved. One example of a challenging requirements balance or trade is shaping for stealth versus aircrew vision. The large number of requirements involved may be grouped in a variety of areas including man-machine interface; structural integration with the airframe; combat hazards; environmental exposures; and supportability. Some individual requirements by themselves pose very difficult, severely nonlinear analysis problems. One such complex problem is that associated with the dynamic structural response resulting from high energy bird impact. An improved analytical capability for soft-body impact simulation was developed.
Explicit solution techniques for impact with contact constraints
NASA Astrophysics Data System (ADS)
McCarty, Robert E.
1993-08-01
Modern military aircraft transparency systems, windshields and canopies, are complex systems which must meet a large and rapidly growing number of requirements. Many of these transparency system requirements are conflicting, presenting difficult balances which must be achieved. One example of a challenging requirements balance or trade is shaping for stealth versus aircrew vision. The large number of requirements involved may be grouped in a variety of areas including man-machine interface; structural integration with the airframe; combat hazards; environmental exposures; and supportability. Some individual requirements by themselves pose very difficult, severely nonlinear analysis problems. One such complex problem is that associated with the dynamic structural response resulting from high energy bird impact. An improved analytical capability for soft-body impact simulation was developed.
Controlling Laboratory Processes From A Personal Computer
NASA Technical Reports Server (NTRS)
Will, H.; Mackin, M. A.
1991-01-01
Computer program provides natural-language process control from IBM PC or compatible computer. Sets up process-control system that either runs without operator or run by workers who have limited programming skills. Includes three smaller programs. Two of them, written in FORTRAN 77, record data and control research processes. Third program, written in Pascal, generates FORTRAN subroutines used by other two programs to identify user commands with device-driving routines written by user. Also includes set of input data allowing user to define user commands to be executed by computer. Requires personal computer operating under MS-DOS with suitable hardware interfaces to all controlled devices. Also requires FORTRAN 77 compiler and device drivers written by user.
Ecohydrological Interfaces as Dynamic Hotspots of Biogeochemical Cycling
NASA Astrophysics Data System (ADS)
Krause, Stefan; Lewandowski, Joerg; Hannah, David; McDonald, Karlie; Folegot, Silvia; Baranov, Victor
2016-04-01
Ecohydrological interfaces, represent the boundaries between water-dependent ecosystems that can alter substantially the fluxes of energy and matter. There is still a critical gap of understanding the organisational principles of the drivers and controls of spatially and temporally variable ecohydrological interface functions. This knowledge gap limits our capacity to efficiently quantify, predict and manage the services provided by complex ecosystems. Many ecohydrological interfaces are characterized by step changes in microbial metabolic activity, steep redox gradients and often even thermodynamic phase shifts, for instance at the interfaces between atmosphere and water or soil matrix and macro-pores interfaces. This paper integrates investigations from point scale laboratory microcosm experiments with reach and subcatchment scale tracer experiments and numerical modeling studies to elaborate similarities in the drivers and controls that constitute the enhanced biogeochemical activity of different types of ecohydrologica interfaces across a range of spatial and temporal scales. We therefore combine smart metabolic activity tracers to quantify the impact of bioturbating benthic fauna onto ecosystem respiration and oxygen consumption and investigate at larger scale, how microbial metabolic activity and carbon turnover at the water-sediment interface are controlled by sediment physical and chemical properties as well as water temperatures. Numerical modeling confirmed that experimentally identified hotspots of streambed biogeochemical cycling were controlled by patterns of physical properties such as hydraulic conductivities or bioavailability of organic matter, impacting on residence time distributions and hence reaction times. In contrast to previous research, our investigations thus confirmed that small-scale variability of physical and chemical interface properties had a major impact on biogeochemical processing at the investigated ecohydrological interfaces. Our results furthermore indicate that to fully understand spatial patterns and temporal dynamics of ecohydrological interface functioning, including hotspots and hot moments, detailed knowledge of the impacts of biological behavior on the physic-chemical ecosystem conditions, and vice-versa, is required.
Ecohydrological Interfaces as Dynamic Hotspots of Biogeochemical Cycling
NASA Astrophysics Data System (ADS)
Krause, S.
2015-12-01
Ecohydrological interfaces, represent the boundaries between water-dependent ecosystems that can alter substantially the fluxes of energy and matter. There is still a critical gap of understanding the organisational principles of the drivers and controls of spatially and temporally variable ecohydrological interface functions. This knowledge gap limits our capacity to efficiently quantify, predict and manage the services provided by complex ecosystems. Many ecohydrological interfaces are characterized by step changes in microbial metabolic activity, steep redox gradients and often even thermodynamic phase shifts, for instance at the interfaces between atmosphere and water or soil matrix and macro-pores interfaces. This paper integrates investigations from point scale microcosm experiments with reach and subcatchment scale tracer experiments and numerical modeling studies to elaborate similarities in the drivers and controls that constitute the enhanced biogeochemical activity of different types of ecohydrologica interfaces across a range of spatial and temporal scales. We therefore combine smart metabolic activity tracers to quantify the impact of bioturbating benthic fauna onto ecosystem respiration and oxygen consumption and investigate at larger scale, how microbial metabolic activity and carbon turnover at the water-sediment interface are controlled by sediment physical and chemical properties as well as water temperatures. Numerical modeling confirmed that experimentally identified hotspots of streambed biogeochemical cycling were controlled by patterns of physical properties such as hydraulic conductivities or bioavailability of organic matter, impacting on residence time distributions and hence reaction times. In contrast to previous research, our investigations thus confirmed that small-scale variability of physical and chemical interface properties had a major impact on biogeochemical processing at the investigated ecohydrological interfaces. Our results furthermore indicate that to fully understand spatial patterns and temporal dynamics of ecohydrological interface functioning, including hotspots and hot moments, detailed knowledge of the impacts of biological behavior on the physic-chemical ecosystem conditions, and vice-versa, is required.
Shuttle mission simulator baseline definition report, volume 1
NASA Technical Reports Server (NTRS)
Burke, J. F.; Small, D. E.
1973-01-01
A baseline definition of the space shuttle mission simulator is presented. The subjects discussed are: (1) physical arrangement of the complete simulator system in the appropriate facility, with a definition of the required facility modifications, (2) functional descriptions of all hardware units, including the operational features, data demands, and facility interfaces, (3) hardware features necessary to integrate the items into a baseline simulator system to include the rationale for selecting the chosen implementation, and (4) operating, maintenance, and configuration updating characteristics of the simulator hardware.
A scanning laser rangefinder for a robotic vehicle
NASA Technical Reports Server (NTRS)
Lewis, R. A.; Johnston, A. R.
1977-01-01
A scanning Laser Rangefinder (LRF) which operates in conjunction with a minicomputer as part of a robotic vehicle is described. The description, in sufficient detail for replication, modification, and maintenance, includes both hardware and software. Also included is a discussion of functional requirements relative to a detailing of the instrument and its performance, a summary of the robot system in which the LRF functions, the software organization, interfaces and description, and the applications to which the LRF has been put.
Chemical Transformation System: Cloud Based ...
Integrated Environmental Modeling (IEM) systems that account for the fate/transport of organics frequently require physicochemical properties as well as transformation products. A myriad of chemical property databases exist but these can be difficult to access and often do not contain the proprietary chemicals that environmental regulators must consider. We are building the Chemical Transformation System (CTS) to facilitate model parameterization and analysis. CTS integrates a number of physicochemical property calculators into the system including EPI Suite, SPARC, TEST and ChemAxon. The calculators are heterogeneous in their scientific methodologies, technology implementations and deployment stacks. CTS also includes a chemical transformation processing engine that has been loaded with reaction libraries for human biotransformation, abiotic reduction and abiotic hydrolysis. CTS implements a common interface for the disparate calculators accepting molecular identifiers (SMILES, IUPAC, CAS#, user-drawn molecule) before submission for processing. To make the system as accessible as possible and provide a consistent programmatic interface, we wrapped the calculators in a standardized RESTful Application Programming Interface (API) which makes it capable of servicing a much broader spectrum of clients without constraints to interoperability such as operating system or programming language. CTS is hosted in a shared cloud environment, the Quantitative Environmental
NASA Astrophysics Data System (ADS)
Shukla, Rajesh Kumar; Patel, Virendra; Kumar, Arvind
2018-02-01
The coating deposit on the substrate in thermal spray coating process develops by solidification of individual molten particle which impacts, flattens and solidifies on the surface of the substrate. Droplet flattening and solidification typically involves rapid cooling. In this paper, a model for non-equilibrium rapid solidification of a molten droplet spreading onto a substrate is presented. Transient flow during droplet impact and its subsequent spreading is considered using the volume of fluid surface tracking method which was fully coupled with the rapid solidification model. The rapid solidification model includes undercooling, nucleation, interface tracking, non-equilibrium solidification kinetics and combined heat transfer and fluid flow as required to treat a non-stagnant splat formed from droplet flattening. The model is validated with the literature results on stagnant splats. Subsequently, using the model the characteristics of the rapidly solidifying interface for non-stagnant splat, such as interface velocity and interface temperature, are described and the effect of undercooling and interfacial heat transfer coefficient are highlighted. In contrast to the stagnant splat, the non-stagnant splat considered in this study displays interesting features in the rapidly solidifying interface. These are attributed to droplet thinning and droplet recoiling that occur during the droplet spreading process.
Monitoring and controlling ATLAS data management: The Rucio web user interface
NASA Astrophysics Data System (ADS)
Lassnig, M.; Beermann, T.; Vigne, R.; Barisits, M.; Garonne, V.; Serfon, C.
2015-12-01
The monitoring and controlling interfaces of the previous data management system DQ2 followed the evolutionary requirements and needs of the ATLAS collaboration. The new data management system, Rucio, has put in place a redesigned web-based interface based upon the lessons learnt from DQ2, and the increased volume of managed information. This interface encompasses both a monitoring and controlling component, and allows easy integration for usergenerated views. The interface follows three design principles. First, the collection and storage of data from internal and external systems is asynchronous to reduce latency. This includes the use of technologies like ActiveMQ or Nagios. Second, analysis of the data into information is done massively parallel due to its volume, using a combined approach with an Oracle database and Hadoop MapReduce. Third, sharing of the information does not distinguish between human or programmatic access, making it easy to access selective parts of the information both in constrained frontends like web-browsers as well as remote services. This contribution will detail the reasons for these principles and the design choices taken. Additionally, the implementation, the interactions with external systems, and an evaluation of the system in production, both from a technological and user perspective, conclude this contribution.
NASA Technical Reports Server (NTRS)
Blumberg, F. C.; Reedy, A.; Yodis, E.
1986-01-01
For the past two years, PRC has been transporting and installing a software engineering environment framework, the Automated Product control Environment (APCE), at a number of PRC and government sites on a variety of different hardware. The APCE was designed using a layered architecture which is based on a standardized set of interfaces to host system services. This interface set called the APCE Interface Set (AIS), was designed to support many of the same goals as the Common Ada Programming Support Environment (APSE) Interface Set (CAIS). The APCE was developed to provide support for the full software lifecycle. Specific requirements of the APCE design included: automation of labor intensive administrative and logistical tasks: freedom for project team members to use existing tools: maximum transportability for APCE programs, interoperability of APCE database data, and distributability of both processes and data: and maximum performance on a wide variety of operating systems. A brief description is given of the APCE and AIS, a comparison of the AIS and CAIS both in terms of functionality and of philosophy and approach and a presentation of PRC's experience in rehosting AIS and transporting APCE programs and project data. Conclusions are drawn from this experience with respect to both the CAIS efforts and Space Station plans.
NASA Technical Reports Server (NTRS)
1976-01-01
The AMPS to Spacelab Interface Control Document which is to be used as a guide for format and information content in generating specific AMPS Mission ICDs is presented. This document is meant to supplement the Spacelab Payload Accommodations Handbook in that it only defines interfaces which are not discussed in the handbook to the level required for design purposes. The AMPS Top Level Requirements Tree, illustrates this ICD by a shaded area and its relationship to the other AMPS technical documents. Other interface documents shown are the Level II, AMPS to Space Shuttle Vehicle ICD and the Level III, AMPS to Instruments ICD.
Requirements of frictional debonding at fiber/matrix interfaces for tough ceramic composites
NASA Astrophysics Data System (ADS)
Hsueh, Chun-Hway
1992-11-01
Optimum toughening of fiber-reinforced ceramic composites requires debonding at fiber/matrix interfaces and subsequent frictional sliding between the fibers and the matrix as the main crack extends through the composite. Criteria of both interfacial debonding vs fiber fracture, and frictional debonding vs frictionless debonding, are illustrated. To achieve interfacial debonding, the ratio of the fiber strength to the interfacial shear strength must exceed a critical value; to achieve a frictional interface after interfacial debonding, the ratio of the interfacial residual clamping stress to the interfacial shear strength must also exceed a critical value. While interfacial debonding is not sensitive to Poisson's effect, the frictional interface is sensitive to Poisson's effect.
Ground Handling of Batteries at Test and Launch-site Facilities
NASA Technical Reports Server (NTRS)
Jeevarajan, Judith A.; Hohl, Alan R.
2008-01-01
Ground handling of flight as well as engineering batteries at test facilities and launch-site facilities is a safety critical process. Test equipment interfacing with the batteries should have the required controls to prevent a hazardous failure of the batteries. Test equipment failures should not induce catastrophic failures on the batteries. Transportation requirements for batteries should also be taken into consideration for safe transportation. This viewgraph presentation includes information on the safe handling of batteries for ground processing at test facilities as well as launch-site facilities.
Information Management System for the California State Water Resources Control Board (SWRCB)
NASA Technical Reports Server (NTRS)
Heald, T. C.; Redmann, G. H.
1973-01-01
A study was made to establish the requirements for an integrated state-wide information management system for water quality control and water quality rights for the State of California. The data sources and end requirements were analyzed for the data collected and used by the numerous agencies, both State and Federal, as well as the nine Regional Boards under the jurisdiction of the State Board. The report details the data interfaces and outlines the system design. A program plan and statement of work for implementation of the project is included.
Detailed requirements document for the integrated structural analysis system, phase B
NASA Technical Reports Server (NTRS)
Rainey, J. A.
1976-01-01
The requirements are defined for a software system entitled integrated Structural Analysis System (ISAS) Phase B which is being developed to provide the user with a tool by which a complete and detailed analysis of a complex structural system can be performed. This software system will allow for automated interface with numerous structural analysis batch programs and for user interaction in the creation, selection, and validation of data. This system will include modifications to the 4 functions developed for ISAS, and the development of 25 new functions. The new functions are described.
Shuttle program. MCC level C formulation requirements: Shuttle TAEM guidance and flight control
NASA Technical Reports Server (NTRS)
Carman, G. L.
1980-01-01
The Level C requirements for the shuttle orbiter terminal area energy management (TAEM) guidance and flight control functions to be incorporated into the Mission Control Center entry profile planning processor are defined. This processor will be used for preentry evaluation of the entry through landing maneuvers, and will include a simplified three degree-of-freedom model of the body rotational dynamics that is necessary to account for the effects of attitude response on the trajectory dynamics. This simulation terminates at TAEM-autoland interface.
Shuttle/GPSPAC experimentation study
NASA Technical Reports Server (NTRS)
Moses, J.; Flack, J. F.
1977-01-01
The utilization is discussed of the GPSPAC, which is presently being developed to be used on the low altitude host vehicle (LAHV), for possible use in the shuttle avionics system to evaluate shuttle/GPS navigation performance. Analysis and tradeoffs of the shuttle/GPS link, shuttle signal interface requirements, oscillator tradeoffs and GPSPAC mechanical modifications for shuttle are included. Only the on-orbit utilization of GPSPAC for the shuttle is discussed. Other phases are briefly touched upon. Recommendations are provided for using the present GPSPAC and the changes required to perform shuttle on-orbit navigation.
French, Deborah; Terrazas, Enrique
2013-01-01
Interfacing complex laboratory equipment to laboratory information systems (LIS) has become a more commonly encountered problem in clinical laboratories, especially for instruments that do not have an interface provided by the vendor. Liquid chromatography-tandem mass spectrometry is a great example of such complex equipment, and has become a frequent addition to clinical laboratories. As the testing volume on such instruments can be significant, manual data entry will also be considerable and the potential for concomitant transcription errors arises. Due to this potential issue, our aim was to interface an AB SCIEX™ mass spectrometer to our Sunquest(®) LIS. WE LICENSED SOFTWARE FOR THE DATA MANAGEMENT INTERFACE FROM THE UNIVERSITY OF PITTSBURGH, BUT EXTENDED THIS WORK AS FOLLOWS: The interface was designed so that it would accept a text file exported from the AB SCIEX™ × 5500 QTrap(®) mass spectrometer, pre-process the file (using newly written code) into the correct format and upload it into Sunquest(®) via file transfer protocol. The licensed software handled the majority of the interface tasks with the exception of converting the output from the Analyst(®) software to the required Sunquest(®) import format. This required writing of a "pre-processor" by one of the authors which was easily integrated with the supplied software. We successfully implemented the data management interface licensed from the University of Pittsburgh. Given the coding that was required to write the pre-processor, and alterations to the source code that were performed when debugging the software, we would suggest that before a laboratory decides to implement such an interface, it would be necessary to have a competent computer programmer available.
Space station commonality analysis
NASA Technical Reports Server (NTRS)
1988-01-01
This study was conducted on the basis of a modification to Contract NAS8-36413, Space Station Commonality Analysis, which was initiated in December, 1987 and completed in July, 1988. The objective was to investigate the commonality aspects of subsystems and mission support hardware while technology experiments are accommodated on board the Space Station in the mid-to-late 1990s. Two types of mission are considered: (1) Advanced solar arrays and their storage; and (2) Satellite servicing. The point of departure for definition of the technology development missions was a set of missions described in the Space Station Mission Requirements Data Base. (MRDB): TDMX 2151 Solar Array/Energy Storage Technology; TDMX 2561 Satellite Servicing and Refurbishment; TDMX 2562 Satellite Maintenance and Repair; TDMX 2563 Materials Resupply (to a free-flyer materials processing platform); TDMX 2564 Coatings Maintenance Technology; and TDMX 2565 Thermal Interface Technology. Issues to be addressed according to the Statement of Work included modularity of programs, data base analysis interactions, user interfaces, and commonality. The study was to consider State-of-the-art advances through the 1990s and to select an appropriate scale for the technology experiments, considering hardware commonality, user interfaces, and mission support requirements. The study was to develop evolutionary plans for the technology advancement missions.
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.
NASA Astrophysics Data System (ADS)
Jaworski, Allan
1993-08-01
The Earth Observing System (EOS) Data and Information System (EOSDIS) will serve as a major resource for the earth science community, supporting both command and control of complex instruments onboard the EOS spacecraft and the archiving, distribution, and analysis of data. The scale of EOSDIS and the volume of multidisciplinary research to be conducted using EOSDIS resources will produce unparalleled needs for technology transparency, data integration, and system interoperability. The scale of this effort far outscopes any previous scientific data system in its breadth or operational and performance needs. Modern hardware technology can meet the EOSDIS technical challenge. Multiprocessing speeds of many giga-flops are being realized by modern computers. Online storage disk, optical disk, and videocassette libraries with storage capacities of many terabytes are now commercially available. Radio frequency and fiber optics communications networks with gigabit rates are demonstrable today. It remains, of course, to perform the system engineering to establish the requirements, architectures, and designs that will implement the EOSDIS systems. Software technology, however, has not enjoyed the price/performance advances of hardware. Although we have learned to engineer hardware systems which have several orders of magnitude greater complexity and performance than those built in the 1960's, we have not made comparable progress in dramatically reducing the cost of software development. This lack of progress may significantly reduce our capabilities to achieve economically the types of highly interoperable, responsive, integraded, and productive environments which are needed by the earth science community. This paper describes some of the EOSDIS software requirements and current activities in the software community which are applicable to meeting the EOSDIS challenge. Some of these areas include intelligent user interfaces, software reuse libraries, and domain engineering. Also included are discussions of applicable standards in the areas of operating systems interfaces, user interfaces, communications interfaces, data transport, and science algorithm support, and their role in supporting the software development process.
Intelligent user interface concept for space station
NASA Technical Reports Server (NTRS)
Comer, Edward; Donaldson, Cameron; Bailey, Elizabeth; Gilroy, Kathleen
1986-01-01
The space station computing system must interface with a wide variety of users, from highly skilled operations personnel to payload specialists from all over the world. The interface must accommodate a wide variety of operations from the space platform, ground control centers and from remote sites. As a result, there is a need for a robust, highly configurable and portable user interface that can accommodate the various space station missions. The concept of an intelligent user interface executive, written in Ada, that would support a number of advanced human interaction techniques, such as windowing, icons, color graphics, animation, and natural language processing is presented. The user interface would provide intelligent interaction by understanding the various user roles, the operations and mission, the current state of the environment and the current working context of the users. In addition, the intelligent user interface executive must be supported by a set of tools that would allow the executive to be easily configured and to allow rapid prototyping of proposed user dialogs. This capability would allow human engineering specialists acting in the role of dialog authors to define and validate various user scenarios. The set of tools required to support development of this intelligent human interface capability is discussed and the prototyping and validation efforts required for development of the Space Station's user interface are outlined.
Telemetry Monitoring and Display Using LabVIEW
NASA Technical Reports Server (NTRS)
Wells, George; Baroth, Edmund C.
1993-01-01
The Measurement Technology Center of the Instrumentation Section configures automated data acquisition systems to meet the diverse needs of JPL's experimental research community. These systems are based on personal computers or workstations (Apple, IBM/Compatible, Hewlett-Packard, and Sun Microsystems) and often include integrated data analysis, visualization and experiment control functions in addition to data acquisition capabilities. These integrated systems may include sensors, signal conditioning, data acquisition interface cards, software, and a user interface. Graphical programming is used to simplify configuration of such systems. Employment of a graphical programming language is the most important factor in enabling the implementation of data acquisition, analysis, display and visualization systems at low cost. Other important factors are the use of commercial software packages and off-the-shelf data acquisition hardware where possible. Understanding the experimenter's needs is also critical. An interactive approach to user interface construction and training of operators is also important. One application was created as a result of a competative effort between a graphical programming language team and a text-based C language programming team to verify the advantages of using a graphical programming language approach. With approximately eight weeks of funding over a period of three months, the text-based programming team accomplished about 10% of the basic requirements, while the Macintosh/LabVIEW team accomplished about 150%, having gone beyond the original requirements to simulate a telemetry stream and provide utility programs. This application verified that using graphical programming can significantly reduce software development time. As a result of this initial effort, additional follow-on work was awarded to the graphical programming team.
NASA Astrophysics Data System (ADS)
Klemm, Richard; Schattschneider, Sebastian; Jahn, Tobias; Hlawatsch, Nadine; Julich, Sandra; Becker, Holger; Gärtner, Claudia
2013-05-01
The ability to integrate complete assays on a microfluidic chip helps to greatly simplify instrument requirements and allows the use of lab-on-a-chip technology in the field. A core application for such field-portable systems is the detection of pathogens in a CBRNE scenario such as permanent monitoring of airborne pathogens, e.g. in metro stations or hospitals etc. As one assay methodology for the pathogen identification, enzymatic assays were chosen. In order evaluate different detection strategies, the realized on-chip enzyme assay module has been designed as a general platform chip. In all application cases, the assays are based on immobilized probes located in microfluidic channels. Therefore a microfluidic chip was realized containing a set of three individually addressable channels, not only for detection of the sample itself also to have a set of references for a quantitative analysis. It furthermore includes two turning valves and a waste container for clear and sealed storage of potential pathogenic liquids to avoid contamination of the environment. All liquids remain in the chip and can be disposed of in proper way subsequently to the analysis. The chip design includes four inlet ports consisting of one sample port (Luer interface) and three mini Luer interfaces for fluidic support of e.g. washing buffer, substrate and enzyme solution. The sample can be applied via a special, sealable sampling vessel with integrated female Luer interface. Thereby also pre-anaytical contamination of the environment can be provided. Other reagents that are required for analysis will be stored off chip.
Evaluation of total knee mechanics using a crouching simulator with a synthetic knee substitute.
Lowry, Michael; Rosenbaum, Heather; Walker, Peter S
2016-05-01
Mechanical evaluation of total knees is frequently required for aspects such as wear, strength, kinematics, contact areas, and force transmission. In order to carry out such tests, we developed a crouching simulator, based on the Oxford-type machine, with novel features including a synthetic knee including ligaments. The instrumentation and data processing methods enabled the determination of contact area locations and interface forces and moments, for a full flexion-extension cycle. To demonstrate the use of the simulator, we carried out a comparison of two different total knee designs, cruciate retaining and substituting. The first part of the study describes the simulator design and the methodology for testing the knees without requiring cadaveric knee specimens. The degrees of freedom of the anatomic hip and ankle joints were reproduced. Flexion-extension was obtained by changing quadriceps length, while variable hamstring forces were applied using springs. The knee joint was represented by three-dimensional printed blocks on to which the total knee components were fixed. Pretensioned elastomeric bands of realistic stiffnesses passed through holes in the block at anatomical locations to represent ligaments. Motion capture of the knees during flexion, together with laser scanning and computer modeling, was used to reconstruct contact areas on the bearing surfaces. A method was also developed for measuring tibial component interface forces and moments as a comparative assessment of fixation. The method involved interposing Tekscan pads at locations on the interface. Overall, the crouching machine and the methodology could be used for many different mechanical measurements of total knee designs, adapted especially for comparative or parametric studies. © IMechE 2016.
Human Systems Integration Competency Development for Navy Systems Commands
2012-09-01
cognizance of Applied Engineering /Psychology relative to knowledge engineering, training, teamwork, user interface design and decision sciences. KSA...cognizance of Applied Engineering /Psychology relative to knowledge engineering, training, teamwork, user interface design and decision sciences...requirements (as required). Fundamental cognizance of Applied Engineering / Psychology relative to knowledge engineering, training, team work, user
Atmospheric Modeling And Sensor Simulation (AMASS) study
NASA Technical Reports Server (NTRS)
Parker, K. G.
1985-01-01
A 4800 band synchronous communications link was established between the Perkin-Elmer (P-E) 3250 Atmospheric Modeling and Sensor Simulation (AMASS) system and the Cyber 205 located at the Goddard Space Flight Center. An extension study of off-the-shelf array processors offering standard interface to the Perkin-Elmer was conducted to determine which would meet computational requirements of the division. A Floating Point Systems AP-120B was borrowed from another Marshall Space Flight Center laboratory for evaluation. It was determined that available array processors did not offer significantly more capabilities than the borrowed unit, although at least three other vendors indicated that standard Perkin-Elmer interfaces would be marketed in the future. Therefore, the recommendation was made to continue to utilize the 120B ad to keep monitoring the AP market. Hardware necessary to support requirements of the ASD as well as to enhance system performance was specified and procured. Filters were implemented on the Harris/McIDAS system including two-dimensional lowpass, gradient, Laplacian, and bicubic interpolation routines.
Research in image management and access
NASA Technical Reports Server (NTRS)
Vondran, Raymond F.; Barron, Billy J.
1993-01-01
Presently, the problem of over-all library system design has been compounded by the accretion of both function and structure to a basic framework of requirements. While more device power has led to increased functionality, opportunities for reducing system complexity at the user interface level have not always been pursued with equal zeal. The purpose of this book is therefore to set forth and examine these opportunities, within the general framework of human factors research in man-machine interfaces. Human factors may be viewed as a series of trade-off decisions among four polarized objectives: machine resources and user specifications; functionality and user requirements. In the past, a limiting factor was the availability of systems. However, in the last two years, over one hundred libraries supported by many different software configurations have been added to the Internet. This document includes a statistical analysis of human responses to five Internet library systems by key features, development of the ideal online catalog system, and ideal online catalog systems for libraries and information centers.
Kennedy Space Center's Command and Control System - "Toasters to Rocket Ships"
NASA Technical Reports Server (NTRS)
Lougheed, Kirk; Mako, Cheryle
2011-01-01
This slide presentation reviews the history of the development of the command and control system at Kennedy Space Center. From a system that could be brought to Florida in the trunk of a car in the 1950's. Including the development of larger and more complex launch vehicles with the Apollo program where human launch controllers managed the launch process with a hardware only system that required a dedicated human interface to perform every function until the Apollo vehicle lifted off from the pad. Through the development of the digital computer that interfaced with ground launch processing systems with the Space Shuttle program. Finally, showing the future control room being developed to control the missions to return to the moon and Mars, which will maximize the use of Commercial-Off-The Shelf (COTS) hardware and software which was standards based and not tied to a single vendor. The system is designed to be flexible and adaptable to support the requirements of future spacecraft and launch vehicles.
Load Balancing Strategies for Multiphase Flows on Structured Grids
NASA Astrophysics Data System (ADS)
Olshefski, Kristopher; Owkes, Mark
2017-11-01
The computation time required to perform large simulations of complex systems is currently one of the leading bottlenecks of computational research. Parallelization allows multiple processing cores to perform calculations simultaneously and reduces computational times. However, load imbalances between processors waste computing resources as processors wait for others to complete imbalanced tasks. In multiphase flows, these imbalances arise due to the additional computational effort required at the gas-liquid interface. However, many current load balancing schemes are only designed for unstructured grid applications. The purpose of this research is to develop a load balancing strategy while maintaining the simplicity of a structured grid. Several approaches are investigated including brute force oversubscription, node oversubscription through Message Passing Interface (MPI) commands, and shared memory load balancing using OpenMP. Each of these strategies are tested with a simple one-dimensional model prior to implementation into the three-dimensional NGA code. Current results show load balancing will reduce computational time by at least 30%.
Asteroid Redirect Crewed Mission Space Suit and EVA System Maturation
NASA Technical Reports Server (NTRS)
Bowie, Jonathan T.; Kelly, Cody; Buffington, Jesse; Watson, Richard D.
2015-01-01
The Asteroid Redirect Crewed Mission (ARCM) requires a Launch/Entry/Abort (LEA) suit capability and short duration Extra Vehicular Activity (EVA) capability from the Orion spacecraft. For this mission, the pressure garment that was selected, for both functions, is the Modified Advanced Crew Escape Suit (MACES) with EVA enhancements and the life support option that was selected is the Exploration Portable Life Support System (PLSS). The proposed architecture was found to meet the mission constraints, but much more work is required to determine the details of the required suit upgrades, the integration with the PLSS, and the rest of the tools and equipment required to accomplish the mission. This work has continued over the last year to better define the operations and hardware maturation of these systems. EVA simulations have been completed in the NBL and interfacing options have been prototyped and analyzed with testing planned for late 2014. For NBL EVA simulations, in 2013, components were procured to allow in-house build up for four new suits with mobility enhancements built into the arms. Boots outfitted with clips that fit into foot restraints have also been added to the suit and analyzed for possible loads. Major suit objectives accomplished this year in testing include: evaluation of mobility enhancements, ingress/egress of foot restraint, use of foot restraint for worksite stability, ingress/egress of Orion hatch with PLSS mockup, and testing with two crew members in the water at one time to evaluate the crew's ability to help one another. Major tool objectives accomplished this year include using various other methods for worksite stability, testing new methods for asteroid geologic sampling and improving the fidelity of the mockups and crew equipment. These tests were completed on a medium fidelity capsule mockup, asteroid vehicle mockup, and asteroid mockups that were more accurate for an asteroid type EVA than previous tests. Another focus was the design and fabrication of the interface between the MACES and the PLSS. The MACES was not designed to interface with a PLSS, hence an interface kit must accommodate the unique design qualities of the MACES and provide the necessary life support function connections to the PLSS. A prototype interface kit for MACES to PLSS has been designed and fabricated. Unmanned and manned testing of the interface will show the usability of the kit while wearing a MACES. The testing shows viability of the kit approach as well as the operations concept. The design will be vetted through suit and PLSS experts and, with the findings from the testing, the best path forward will be determined. As the Asteroid Redirect Mission matures, the suit/life support portion of the mission will mature along with it and EVA Tools & Equipment can be iterated to accommodate the overall mission objectives and compromises inherent in EVA Suit optimization. The goal of the EVA architecture for ARCM is to continue to build on the previously developed technologies and lessons learned, and accomplish the ARCM EVAs while providing a stepping stone to future missions and destinations.
Military Medical Decision Support for Homeland Defense During Emergency
2004-12-01
abstraction hierarchy, three levels of information requirement for designing emergency training interface are recognized. These are epistemological ...support human decision making process is considered to be decision-centric. A typical decision-centric interface is supported by at least four design ... Designing Emergency Training Interface ......................................................................................... 5 Epistemological
Distributed Planning in a Mixed-Initiative Environment
2008-06-01
Knowledge Sources Control Remote Blackboard Remote Knowledge Sources Remot e Data Remot e Data Java Distributed Blackboard Figure 3 - Distributed...an interface agent or planning agent and the second type is a critic agent. Agents in the DEEP architecture extend and use the Java Agent...chosen because it is fully implemented in Java , and supports these requirements. 2.3.3 Interface Agents Interface agents are the interfaces through
Advanced flight control system study
NASA Technical Reports Server (NTRS)
Mcgough, J.; Moses, K.; Klafin, J. F.
1982-01-01
The architecture, requirements, and system elements of an ultrareliable, advanced flight control system are described. The basic criteria are functional reliability of 10 to the minus 10 power/hour of flight and only 6 month scheduled maintenance. A distributed system architecture is described, including a multiplexed communication system, reliable bus controller, the use of skewed sensor arrays, and actuator interfaces. Test bed and flight evaluation program are proposed.
Houska, Treva
2012-01-01
The EarthExplorer trifold provides basic information for on-line access to remotely-sensed data from the U.S. Geological Survey Earth Resources Observation and Science (EROS) Center archive. The EarthExplorer (http://earthexplorer.usgs.gov/) client/server interface allows users to search and download aerial photography, satellite data, elevation data, land-cover products, and digitized maps. Minimum computer system requirements and customer service contact information also are included in the brochure.
Study of airborne science experiment management concepts for application to space shuttle, volume 2
NASA Technical Reports Server (NTRS)
Mulholland, D. R.; Reller, J. O., Jr.; Neel, C. B.; Haughney, L. C.
1973-01-01
Airborne research management and shuttle sortie planning at the Ames Research Center are reported. Topics discussed include: basic criteria and procedures for the formulation and approval of airborne missions; ASO management structure and procedures; experiment design, development, and testing aircraft characteristics and experiment interfaces; information handling for airborne science missions; mission documentation requirements; and airborne science methods and shuttle sortie planning.
Smart Shutdown Guidebook: Considerations for a Successful Shutdown
2014-01-01
multiple countries, multiple contractors) or in number of subsystems and interfaces • State of the contract (is the procuring contract officer ( PCO ...assigned tasks. • Includes the procuring, administrative, and terminating contracting officers ( PCOs , ACOs, and TCOs). 6 • Assigns full authority and...assist the PCO and TCO with their correspondence requirements with contractors and to assist higher leadership in its communication with external
Apollo experience report: Engineering and analysis mission support
NASA Technical Reports Server (NTRS)
Fricke, R. W., Jr.
1975-01-01
The tasks performed by the team of specialists that evaluated hardware performance during prelaunch checkout and in-flight operation are discussed. The organizational structure, operational procedures, and interfaces as well as the facilities and software required to perform these tasks are discussed. The scope of the service performed by the team and the evaluation philosophy are described. Summaries of problems and their resolution are included as appendixes.
MOD-1 Wind Turbine Generator Analysis and Design Report, Volume 2
NASA Technical Reports Server (NTRS)
1979-01-01
The MOD-1 detail design is appended. The supporting analyses presented include a parametric system trade study, a verification of the computer codes used for rotor loads analysis, a metal blade study, and a definition of the design loads at each principal wind turbine generator interface for critical loading conditions. Shipping and assembly requirements, composite blade development, and electrical stability are also discussed.
A Graphical User Interface for the Low Cost Combat Direction System
1991-09-16
the same tasks. These shipboard tasks, which include contact management , moving geometry calculations, intelligence compila- tion, area plotting and...Display Defaults Analysis This category covers a wide range of required data input and system configuration issues. To keep the screen display manageable ...parts or dialog boxes. The implementation of an Ada application using STARS is quite straightforward, although knowlede of X Protocol primitives is
Collective Protection (COLPRO) Novel Closures Testing
2013-03-28
science and technology programs for future ColPro systems may include interfaces such as novel designs using zippers, hook-and-pile closures, and...necessitate new testing procedures. Additionally, stand- ards of performance must be adjusted as technologies advance. Test procedures and parameters...listed in this TOP may require updating to accommodate new technologies in test items or in test instrumentation. Any variation to the TOP procedures
Advanced Transport Operating System (ATOPS) utility library software description
NASA Technical Reports Server (NTRS)
Clinedinst, Winston C.; Slominski, Christopher J.; Dickson, Richard W.; Wolverton, David A.
1993-01-01
The individual software processes used in the flight computers on-board the Advanced Transport Operating System (ATOPS) aircraft have many common functional elements. A library of commonly used software modules was created for general uses among the processes. The library includes modules for mathematical computations, data formatting, system database interfacing, and condition handling. The modules available in the library and their associated calling requirements are described.
Development of Avionics Installation Interface Standards.
1981-12-01
design and manufacturing process routinely used to minimize the susceptibility of the equipment to corrosion . 4.2.7 Form/Fit Working Group The Form...since it would include both the LRU repack- aging and the required aircraft reconfiguration. The smallest impact is achieved when an avionics or...Smith ARINC Research Corporation X D. Snell Boeing Aerospace Corporation .. Steele Masterite Industries E. Straub ARINC Research Corporation X 1
ANALOG I/O MODULE TEST SYSTEM BASED ON EPICS CA PROTOCOL AND ACTIVEX CA INTERFACE
DOE Office of Scientific and Technical Information (OSTI.GOV)
YENG,YHOFF,L.
2003-10-13
Analog input (ADC) and output (DAC) modules play a substantial role in device level control of accelerator and large experiment physics control system. In order to get the best performance some features of analog modules including linearity, accuracy, crosstalk, thermal drift and so on have to be evaluated during the preliminary design phase. Gain and offset error calibration and thermal drift compensation (if needed) may have to be done in the implementation phase as well. A natural technique for performing these tasks is to interface the analog VO modules and GPIB interface programmable test instruments with a computer, which canmore » complete measurements or calibration automatically. A difficulty is that drivers of analog modules and test instruments usually work on totally different platforms (vxworks VS Windows). Developing new test routines and drivers for testing instruments under VxWorks (or any other RTOS) platform is not a good solution because such systems have relatively poor user interface and developing such software requires substantial effort. EPICS CA protocol and ActiveX CA interface provide another choice, a PC and LabVIEW based test system. Analog 110 module can be interfaced from LabVIEW test routines via ActiveX CA interface. Test instruments can be controlled via LabVIEW drivers, most of which are provided by instrument vendors or by National Instruments. Labview also provides extensive data analysis and process functions. Using these functions, users can generate powerful test routines very easily. Several applications built for Spallation Neutron Source (SNS) Beam Loss Monitor (BLM) system are described in this paper.« less
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.
Transforming Collaborative Process Models into Interface Process Models by Applying an MDA Approach
NASA Astrophysics Data System (ADS)
Lazarte, Ivanna M.; Chiotti, Omar; Villarreal, Pablo D.
Collaborative business models among enterprises require defining collaborative business processes. Enterprises implement B2B collaborations to execute these processes. In B2B collaborations the integration and interoperability of processes and systems of the enterprises are required to support the execution of collaborative processes. From a collaborative process model, which describes the global view of the enterprise interactions, each enterprise must define the interface process that represents the role it performs in the collaborative process in order to implement the process in a Business Process Management System. Hence, in this work we propose a method for the automatic generation of the interface process model of each enterprise from a collaborative process model. This method is based on a Model-Driven Architecture to transform collaborative process models into interface process models. By applying this method, interface processes are guaranteed to be interoperable and defined according to a collaborative process.
A haptic interface for virtual simulation of endoscopic surgery.
Rosenberg, L B; Stredney, D
1996-01-01
Virtual reality can be described as a convincingly realistic and naturally interactive simulation in which the user is given a first person illusion of being immersed within a computer generated environment While virtual reality systems offer great potential to reduce the cost and increase the quality of medical training, many technical challenges must be overcome before such simulation platforms offer effective alternatives to more traditional training means. A primary challenge in developing effective virtual reality systems is designing the human interface hardware which allows rich sensory information to be presented to users in natural ways. When simulating a given manual procedure, task specific human interface requirements dictate task specific human interface hardware. The following paper explores the design of human interface hardware that satisfies the task specific requirements of virtual reality simulation of Endoscopic surgical procedures. Design parameters were derived through direct cadaver studies and interviews with surgeons. Final hardware design is presented.
Petrides, Athena K; Tanasijevic, Milenko J; Goonan, Ellen M; Landman, Adam B; Kantartjis, Michalis; Bates, David W; Melanson, Stacy E F
2017-10-01
Recent U.S. government regulations incentivize implementation of an electronic health record (EHR) with computerized order entry and structured results display. Many institutions have also chosen to interface their EHR to their laboratory information system (LIS). Reported long-term benefits include increased efficiency and improved quality and safety. In order to successfully implement an interfaced EHR-LIS, institutions must plan years in advance and anticipate the impact of an integrated system. It can be challenging to fully understand the technical, workflow and resource aspects and adequately prepare for a potentially protracted system implementation and the subsequent stabilization. We describe the top ten challenges that we encountered in our clinical laboratories following the implementation of an interfaced EHR-LIS and offer suggestions on how to overcome these challenges. This study was performed at a 777-bed, tertiary care center which recently implemented an interfaced EHR-LIS. Challenges were recorded during EHR-LIS implementation and stabilization and the authors describe the top ten. Our top ten challenges were selection and harmonization of test codes, detailed training for providers on test ordering, communication with EHR provider champions during the build process, fluid orders and collections, supporting specialized workflows, sufficient reports and metrics, increased volume of inpatient venipunctures, adequate resources during stabilization, unanticipated changes to laboratory workflow and ordering specimens for anatomic pathology. A few suggestions to overcome these challenges include regular meetings with clinical champions, advanced considerations of reports and metrics that will be needed, adequate training of laboratory staff on new workflows in the EHR and defining all tests including anatomic pathology in the LIS. EHR-LIS implementations have many challenges requiring institutions to adapt and develop new infrastructures. This article should be helpful to other institutions facing or undergoing a similar endeavor. Copyright © 2017 Elsevier B.V. All rights reserved.
DMA shared byte counters in a parallel computer
Chen, Dong; Gara, Alan G.; Heidelberger, Philip; Vranas, Pavlos
2010-04-06
A parallel computer system is constructed as a network of interconnected compute nodes. Each of the compute nodes includes at least one processor, a memory and a DMA engine. The DMA engine includes a processor interface for interfacing with the at least one processor, DMA logic, a memory interface for interfacing with the memory, a DMA network interface for interfacing with the network, injection and reception byte counters, injection and reception FIFO metadata, and status registers and control registers. The injection FIFOs maintain memory locations of the injection FIFO metadata memory locations including its current head and tail, and the reception FIFOs maintain the reception FIFO metadata memory locations including its current head and tail. The injection byte counters and reception byte counters may be shared between messages.
Development of a task analysis tool to facilitate user interface design
NASA Technical Reports Server (NTRS)
Scholtz, Jean C.
1992-01-01
A good user interface is one that facilitates the user in carrying out his task. Such interfaces are difficult and costly to produce. The most important aspect in producing a good interface is the ability to communicate to the software designers what the user's task is. The Task Analysis Tool is a system for cooperative task analysis and specification of the user interface requirements. This tool is intended to serve as a guide to development of initial prototypes for user feedback.
Formal design specification of a Processor Interface Unit
NASA Technical Reports Server (NTRS)
Fura, David A.; Windley, Phillip J.; Cohen, Gerald C.
1992-01-01
This report describes work to formally specify the requirements and design of a processor interface unit (PIU), a single-chip subsystem providing memory-interface bus-interface, and additional support services for a commercial microprocessor within a fault-tolerant computer system. This system, the Fault-Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance-free operation, or both. The need for high-quality design assurance in such applications is an undisputed fact, given the disastrous consequences that even a single design flaw can produce. Thus, the further development and application of formal methods to fault-tolerant systems is of critical importance as these systems see increasing use in modern society.
NASA Technical Reports Server (NTRS)
Jefferys, S.; Johnson, W.; Lewis, R.; Rich, R.
1981-01-01
The software modules which comprise the IGDS/TRAP Interface Program are described. A hierarchical input processing output (HIPO) chart for each user command is given. The description consists of: (1) function of the user command; (2) calling sequence; (3) moduls which call this use command; (4) modules called by this user command; (5) IGDS commands used by this user command; and (6) local usage of global registers. Each HIPO contains the principal functions performed within the module. Also included with each function are a list of the inputs which may be required to perform the function and a list of the outputs which may be created as a result of performing the function.
Shuttle/payload communications and data systems interface analysis
NASA Technical Reports Server (NTRS)
Huth, G. K.
1980-01-01
The payload/orbiter functional command signal flow and telemetry signal flow are discussed. Functional descriptions of the various orbiter communication/avionic equipment involved in processing a command to a payload either from the ground through the orbiter by the payload specialist on the orbiter are included. Functional descriptions of the various orbiter communication/avionic equipment involved in processing telemetry data by the orbiter and transmitting the processed data to the ground are presented. The results of the attached payload/orbiter single processing and data handling system evaluation are described. The causes of the majority of attached payload/orbiter interface problems are delineated. A refined set of required flux density values for a detached payload to communicate with the orbiter is presented.
Graphical Language for Data Processing
NASA Technical Reports Server (NTRS)
Alphonso, Keith
2011-01-01
A graphical language for processing data allows processing elements to be connected with virtual wires that represent data flows between processing modules. The processing of complex data, such as lidar data, requires many different algorithms to be applied. The purpose of this innovation is to automate the processing of complex data, such as LIDAR, without the need for complex scripting and programming languages. The system consists of a set of user-interface components that allow the user to drag and drop various algorithmic and processing components onto a process graph. By working graphically, the user can completely visualize the process flow and create complex diagrams. This innovation supports the nesting of graphs, such that a graph can be included in another graph as a single step for processing. In addition to the user interface components, the system includes a set of .NET classes that represent the graph internally. These classes provide the internal system representation of the graphical user interface. The system includes a graph execution component that reads the internal representation of the graph (as described above) and executes that graph. The execution of the graph follows the interpreted model of execution in that each node is traversed and executed from the original internal representation. In addition, there are components that allow external code elements, such as algorithms, to be easily integrated into the system, thus making the system infinitely expandable.
Four-Channel PC/104 MIL-STD-1553 Circuit Board
NASA Technical Reports Server (NTRS)
Cox, Gary L.
2004-01-01
The mini bus interface card (miniBIC) is the first four-channel electronic circuit board that conforms to MIL-STD-1553 and to the electrical-footprint portion of PC/104. [MIL-STD-1553 is a military standard that encompasses a method of communication and electrical- interface requirements for digital electronic subsystems connected to a data bus. PC/104 is an industry standard for compact, stackable modules that are fully compatible (in architecture, hardware, and software) with personal-computer data- and power-bus circuitry.] Prior to the development of the miniBIC, only one- and two-channel PC/104 MIL-STD-1553 boards were available. To obtain four channels, it was necessary to include at least two boards in a PC/104 stack. In comparison with such a two-board stack, the miniBIC takes up less space, consumes less power, and is more reliable. In addition, the miniBIC includes 32 digital input/output channels. The miniBIC (see figure) contains four MIL-STD-1553B hybrid integrated circuits (ICs), four transformers, a field-programmable gate array (FPGA), and an Industry Standard Architecture (ISA) interface. Each hybrid IC includes a MILSTD-1553 dual transceiver, memory-management circuitry, processor interface logic circuitry, and 64Kx16 bits of shared static random access memory. The memory is used to configure message and data blocks. In addition, 23 16-bit registers are available for (1) configuring the hybrid IC for, and starting it in, various modes of operation; (2) reading the status of the functionality of the hybrid IC; and (3) resetting the hybrid IC to a known state. The miniBIC can operate as a remote terminal, bus controller, or bus monitor. The FPGA provides the chip-select and data-strobe signals needed for operation of the hybrid ICs. The FPGA also receives interruption signals and forwards them to the ISA bus. The ISA interface connects the address, data, and control interfaces of the hybrid ICs to the ISA backplane. Each channel is, in effect, a MIL-STD-1553 interface that can operate either independently of the others or else as a redundant version of one of the others. The transformer in each channel provides electrical isolation between the rest of the miniBIC circuitry and the bus to which that channel is connected.
Visual Elements and Container Metaphors for Multi-Media.
ERIC Educational Resources Information Center
Howarth, Mike
1997-01-01
An interactive version of an educational radio program can be developed quickly and easily with a main menu interface that takes into account physical classroom conditions; interactive learning interfaces that accommodate eye and vision requirements of children; and a story interface design informed by the "container" metaphor and the 2-D…
NASA Technical Reports Server (NTRS)
Byrne, R.; Scharf, M.; Doan, D.; Liu, J.; Willems, A.
2004-01-01
An advanced network interface was designed and implemented by a team from the Jet Propulsion Lab with support from the European Space Operations Center. This poster shows the requirements for the interface, the design, the topology, the testing and lessons learned from the whole implementation.
Graphical Interface for the Study of Gas-Phase Reaction Kinetics: Cyclopentene Vapor Pyrolysis
NASA Astrophysics Data System (ADS)
Marcotte, Ronald E.; Wilson, Lenore D.
2001-06-01
The undergraduate laboratory experiment on the pyrolysis of gaseous cyclopentene has been modernized to improve safety, speed, and precision and to better reflect the current practice of physical chemistry. It now utilizes virtual instrument techniques to create a graphical computer interface for the collection and display of experimental data. An electronic pressure gauge has replaced the mercury manometer formerly needed in proximity to the 500 °C pyrolysis oven. Students have much better real-time information available to them and no longer require multiple lab periods to get rate constants and acceptable Arrhenius parameters. The time saved on manual data collection is used to give the students a tour of the computer interfacing hardware and software and a hands-on introduction to gas-phase reagent preparation using a research-grade high-vacuum system. This includes loading the sample, degassing it by the freeze-pump-thaw technique, handling liquid nitrogen and working through the logic necessary for each reconfiguration of the diffusion pump section and the submanifolds.
Atomically engineered epitaxial anatase TiO 2 metal-semiconductor field-effect transistors
DOE Office of Scientific and Technical Information (OSTI.GOV)
Kim, Brian S. Y.; Minohara, Makoto; Hikita, Yasuyuki
Here, anatase TiO 2 is a promising material for a vast array of electronic, energy, and environmental applications, including photocatalysis, photovoltaics, and sensors. A key requirement for these applications is the ability to modulate its electrical properties without dominant dopant scattering and while maintaining high carrier mobility. Here, we demonstrate the room temperature field-effect modulation of the conducting epitaxial interface between anatase TiO 2 and LaAlO 3 (001), which arises for LaO-terminated LaAlO 3, while the AlO 2-terminated interface is insulating. This approach, together with the metal-semiconductor field-effect transistor geometry, naturally bypasses the gate/channel interface traps, resulting in a highmore » field-effect mobility μ FE of 3.14 cm 2 (V s) –1 approaching 98% of the corresponding Hall mobility μ Hall. Accordingly, the channel conductivity is modulated over 6 orders of magnitude over a gate voltage range of ~4 V.« less
NASA Astrophysics Data System (ADS)
Dieguez Salgado, Uxia; Weiß, Christian; Michelic, Susanne K.; Bernhard, Christian
2018-05-01
Since nonmetallic inclusions (NMIs) in steel cannot be completely avoided, a greater understanding of their development and evolution during the steelmaking process is required. In particular, this includes the adhesion of microinclusions to the refractory/steel interface in the flow control system between the tundish and the mold. This phenomenon, commonly referred to as clogging, causes losses in productivity and product quality. Inclusions transported from the bulk melt to the boundary layer may adhere to the refractory/steel interface due to formation of a fluid cavity. A detailed model was derived for the detachment of NMIs adhering to a nozzle wall and is based on the local hydrodynamic conditions combined with the specific interfacial properties in the system consisting of the inclusions, the refractories, and the steel. The model is evaluated for three different application-oriented cases. This study has been focused on providing a better understanding of fluid flow in the near-wall region in order to reduce clogging during steelmaking.
JPL Space Telecommunications Radio System Operating Environment
NASA Technical Reports Server (NTRS)
Lux, James P.; Lang, Minh; Peters, Kenneth J.; Taylor, Gregory H.; Duncan, Courtney B.; Orozco, David S.; Stern, Ryan A.; Ahten, Earl R.; Girard, Mike
2013-01-01
A flight-qualified implementation of a Software Defined Radio (SDR) Operating Environment for the JPL-SDR built for the CoNNeCT Project has been developed. It is compliant with the NASA Space Telecommunications Radio System (STRS) Architecture Standard, and provides the software infrastructure for STRS compliant waveform applications. This software provides a standards-compliant abstracted view of the JPL-SDR hardware platform. It uses industry standard POSIX interfaces for most functions, as well as exposing the STRS API (Application Programming In terface) required by the standard. This software includes a standardized interface for IP components instantiated within a Xilinx FPGA (Field Programmable Gate Array). The software provides a standardized abstracted interface to platform resources such as data converters, file system, etc., which can be used by STRS standards conformant waveform applications. It provides a generic SDR operating environment with a much smaller resource footprint than similar products such as SCA (Software Communications Architecture) compliant implementations, or the DoD Joint Tactical Radio Systems (JTRS).
NASA Technical Reports Server (NTRS)
Gould, Kevin E.; Satyanarayana, Arunkumar; Bogert, Philip B.
2016-01-01
Analysis performed in this study substantiates the need for high fidelity vehicle level progressive damage analyses (PDA) structural models for use in the verification and validation of proposed sub-scale structural models and to support required full-scale vehicle level testing. PDA results are presented that capture and correlate the responses of sub-scale 3-stringer and 7-stringer panel models and an idealized 8-ft diameter fuselage model, which provides a vehicle level environment for the 7-stringer sub-scale panel model. Two unique skin-stringer attachment assumptions are considered and correlated in the models analyzed: the TIE constraint interface versus the cohesive element (COH3D8) interface. Evaluating different interfaces allows for assessing a range of predicted damage modes, including delamination and crack propagation responses. Damage models considered in this study are the ABAQUS built-in Hashin procedure and the COmplete STress Reduction (COSTR) damage procedure implemented through a VUMAT user subroutine using the ABAQUS/Explicit code.
Atomically engineered epitaxial anatase TiO 2 metal-semiconductor field-effect transistors
Kim, Brian S. Y.; Minohara, Makoto; Hikita, Yasuyuki; ...
2018-03-26
Here, anatase TiO 2 is a promising material for a vast array of electronic, energy, and environmental applications, including photocatalysis, photovoltaics, and sensors. A key requirement for these applications is the ability to modulate its electrical properties without dominant dopant scattering and while maintaining high carrier mobility. Here, we demonstrate the room temperature field-effect modulation of the conducting epitaxial interface between anatase TiO 2 and LaAlO 3 (001), which arises for LaO-terminated LaAlO 3, while the AlO 2-terminated interface is insulating. This approach, together with the metal-semiconductor field-effect transistor geometry, naturally bypasses the gate/channel interface traps, resulting in a highmore » field-effect mobility μ FE of 3.14 cm 2 (V s) –1 approaching 98% of the corresponding Hall mobility μ Hall. Accordingly, the channel conductivity is modulated over 6 orders of magnitude over a gate voltage range of ~4 V.« less
A compressible multiphase framework for simulating supersonic atomization
NASA Astrophysics Data System (ADS)
Regele, Jonathan D.; Garrick, Daniel P.; Hosseinzadeh-Nik, Zahra; Aslani, Mohamad; Owkes, Mark
2016-11-01
The study of atomization in supersonic combustors is critical in designing efficient and high performance scramjets. Numerical methods incorporating surface tension effects have largely focused on the incompressible regime as most atomization applications occur at low Mach numbers. Simulating surface tension effects in high speed compressible flow requires robust numerical methods that can handle discontinuities caused by both material interfaces and shocks. A shock capturing/diffused interface method is developed to simulate high-speed compressible gas-liquid flows with surface tension effects using the five-equation model. This includes developments that account for the interfacial pressure jump that occurs in the presence of surface tension. A simple and efficient method for computing local interface curvature is developed and an acoustic non-dimensional scaling for the surface tension force is proposed. The method successfully captures a variety of droplet breakup modes over a range of Weber numbers and demonstrates the impact of surface tension in countering droplet deformation in both subsonic and supersonic cross flows.
Mission Peculiar Equipment (MPE) For Spacelab Mission 1 Payload
NASA Astrophysics Data System (ADS)
Sims, John H.; Dodeck, Hauke
1982-02-01
Spacelab interfaces and services for payloads are advertised in the Spacelab Payload Accommodations Handbook (SPAH). These accommodations are available to the total payload and must be managed and apportioned by a payload integrator. A major part of the integration task is satisfying all instruments/facilities servicing requirements which vary with each item of payload equipment and, when totalled, sometimes exceed the capabilities as defined in SPAH. Such a determination is an output of the integrated payload design and integration effort which consists of analytical assessments based on individual payload equipment requirements inputs, STS and Spacelab available accommodations and constraints, and programmatic considerations. This systems engineering activity spans all engineering disciplines, assesses the module and pallet layouts and simultaneous operation of instrument/facility combinations, and requires a detailed knowledge of the Spacelab design. Introduction of a broad range of payload integrator-provided Mission Peculiar Equipment (MPE) into the Spacelab Mission 1 payload complement was necessary to be added to the Spacelab provisions in order to satisfy the interface and service requirements for each payload developer. This paper provides insight into various aspects of this MPE; including why it is needed, driving design considerations, design and development problems, and conclusions and recommendations for the future. MPE identified for Spacelab Mission 1 begins an inventory that will continue to expand as other mission requirements are identified and the Spacelab flight frequency increases.
Ecological Interface Design for Computer Network Defense.
Bennett, Kevin B; Bryant, Adam; Sushereba, Christen
2018-05-01
A prototype ecological interface for computer network defense (CND) was developed. Concerns about CND run high. Although there is a vast literature on CND, there is some indication that this research is not being translated into operational contexts. Part of the reason may be that CND has historically been treated as a strictly technical problem, rather than as a socio-technical problem. The cognitive systems engineering (CSE)/ecological interface design (EID) framework was used in the analysis and design of the prototype interface. A brief overview of CSE/EID is provided. EID principles of design (i.e., direct perception, direct manipulation and visual momentum) are described and illustrated through concrete examples from the ecological interface. Key features of the ecological interface include (a) a wide variety of alternative visual displays, (b) controls that allow easy, dynamic reconfiguration of these displays, (c) visual highlighting of functionally related information across displays, (d) control mechanisms to selectively filter massive data sets, and (e) the capability for easy expansion. Cyber attacks from a well-known data set are illustrated through screen shots. CND support needs to be developed with a triadic focus (i.e., humans interacting with technology to accomplish work) if it is to be effective. Iterative design and formal evaluation is also required. The discipline of human factors has a long tradition of success on both counts; it is time that HF became fully involved in CND. Direct application in supporting cyber analysts.
CoNNeCT Baseband Processor Module Boot Code SoftWare (BCSW)
NASA Technical Reports Server (NTRS)
Yamamoto, Clifford K.; Orozco, David S.; Byrne, D. J.; Allen, Steven J.; Sahasrabudhe, Adit; Lang, Minh
2012-01-01
This software provides essential startup and initialization routines for the CoNNeCT baseband processor module (BPM) hardware upon power-up. A command and data handling (C&DH) interface is provided via 1553 and diagnostic serial interfaces to invoke operational, reconfiguration, and test commands within the code. The BCSW has features unique to the hardware it is responsible for managing. In this case, the CoNNeCT BPM is configured with an updated CPU (Atmel AT697 SPARC processor) and a unique set of memory and I/O peripherals that require customized software to operate. These features include configuration of new AT697 registers, interfacing to a new HouseKeeper with a flash controller interface, a new dual Xilinx configuration/scrub interface, and an updated 1553 remote terminal (RT) core. The BCSW is intended to provide a "safe" mode for the BPM when initially powered on or when an unexpected trap occurs, causing the processor to reset. The BCSW allows the 1553 bus controller in the spacecraft or payload controller to operate the BPM over 1553 to upload code; upload Xilinx bit files; perform rudimentary tests; read, write, and copy the non-volatile flash memory; and configure the Xilinx interface. Commands also exist over 1553 to cause the CPU to jump or call a specified address to begin execution of user-supplied code. This may be in the form of a real-time operating system, test routine, or specific application code to run on the BPM.
Adhesion of Silicone Elastomer Seals for NASA's Crew Exploration Vehicle
NASA Technical Reports Server (NTRS)
deGroh, Henry C., III; Miller, Sharon K. R.; Smith, Ian M.; Daniels, Christopher C.; Steinetz, Bruce M
2008-01-01
Silicone rubber seals are being considered for a number of interfaces on NASA's Crew Exploration Vehicle (CEV). Some of these joints include the docking system, hatches, and heat shield-to-back shell interface. A large diameter molded silicone seal is being developed for the Low Impact Docking System (LIDS) that forms an effective seal between the CEV and International Space Station (ISS) and other future Constellation Program spacecraft. Seals between the heat shield and back shell prevent high temperature reentry gases from leaking into the interface. Silicone rubber seals being considered for these locations have inherent adhesive tendencies that would result in excessive forces required to separate the joints if left unchecked. This paper summarizes adhesion assessments for both as-received and adhesion-mitigated seals for the docking system and the heat shield interface location. Three silicone elastomers were examined: Parker Hannifin S0899-50 and S0383-70 compounds, and Esterline ELA-SA-401 compound. For the docking system application various levels of exposure to atomic oxygen (AO) were evaluated. Moderate AO treatments did not lower the adhesive properties of S0899-50 sufficiently. However, AO pretreatments of approximately 10(exp 20) atoms/sq cm did lower the adhesion of S0383-70 and ELA-SA-401 to acceptable levels. For the heat shield-to-back shell interface application, a fabric covering was also considered. Molding Nomex fabric into the heat shield pressure seal appreciably reduced seal adhesion for the heat shield-to-back shell interface application.
A CBLT and MCST capable VME slave interface
DOE Office of Scientific and Technical Information (OSTI.GOV)
Wuerthwein, F.; Strohman, C.; Honscheid, K.
1996-12-31
We report on the development of a VME slave interface for the CLEO III detector implemented in an ALTERA EPM7256 CPLD. This includes the first implementation of the chained block transfer protocol (CBLT) and multi-cast cycles (MCST) as defined by the VME-P task group of VIPA. Within VME64 there is no operation that guarantees efficient readout of large blocks of data that are sparsely distributed among a series of slave modules in a VME crate. This has led the VME-P task group of VIPA to specify protocols that enable a master to address many slaves at a single address. Whichmore » slave is to drive the data bus is determined by a token passing mechanism that uses the *IACKOUT, *IACKIN daisy chain. This protocol requires no special features from the master besides conformance to VME64. Non-standard features are restricted to the VME slave interface. The CLEO III detector comprises {approximately}400,000 electronic channels that have to be digitized, sparsified, and stored within 20{mu}s in order to incur less than 2% dead time at an anticipated trigger rate of 1000Hz. 95% of these channels are accounted for by only two detector subsystems, the silicon microstrip detector (125,000 channels), and the ring imaging Cerenkov detector (RICH) (230,400 channels). After sparsification either of these two detector subsystems is expected to provide event fragments on the order of 10KBytes, spread over 4, and 8 VME crates, respectively. We developed a chip set that sparsifies, tags, and stores the incoming digital data on the data boards, and includes a VME slave interface that implements MCST and CUT protocols. In this poster, we briefly describe this chip set and then discuss the VME slave interface in detail.« less
Coupled gamma/alpha phase transformations in low-carbon steels
NASA Astrophysics Data System (ADS)
Mizutani, Yasushi
Since steels have been the most prevalently utilized materials for many years, the desire for steels with low alloying components with a well-balanced combination of high strength and toughness is increasing. Low carbon steels consisting of bainitic microstructures are ideally suited to meeting such technological and economic requirements. Thus it is extremely important to fully clarify the mechanism of bainite formation in order to produce this type of engineering steel by optimized alloy and process design. This research focuses on understanding the mechanism of coupled displacive/diffusional gamma/alpha transformation in low-carbon steels including bainitic and martensitic transformation, and establishing a more comprehensive and physically rational computational model for predictive control of coupled gamma/alpha transformation phenomena. Models for coupled gamma/alpha phase transformation proposed in this study are based on a mechanistic and unified theory and the following assumptions: (1) The energy dissipation due to interface motion can be linearly combined with the energy dissipation due to carbon diffusion. (2) The carbon concentrations at the interface in both gamma and alpha phases are constrained by an interface solute trapping law. (3) Interface motion during nucleation is also governed by the carbon diffusion field velocity. (4) The response function of glissile interface motion can be expressed in the form of thermally activated dislocation glide. In contrast to the conventional semi-empirical models of the previous literature, the computational model proposed in this study is demonstrated to successfully provide a comprehensive and quantitative prediction of the effects of temperature, composition, microstructure, and the interactions among them. This includes the effects of substitutional solutes, morphology of the parent gamma phase, density of nucleation sites, temperature dependent variation of flow stress of matrix, and dynamic recovery of forest dislocations on the kinetics of coupled gamma/alpha phase transformation.
Optimizing growth and post treatment of diamond for high capacitance neural interfaces.
Tong, Wei; Fox, Kate; Zamani, Akram; Turnley, Ann M; Ganesan, Kumaravelu; Ahnood, Arman; Cicione, Rosemary; Meffin, Hamish; Prawer, Steven; Stacey, Alastair; Garrett, David J
2016-10-01
Electrochemical and biological properties are two crucial criteria in the selection of the materials to be used as electrodes for neural interfaces. For neural stimulation, materials are required to exhibit high capacitance and to form intimate contact with neurons for eliciting effective neural responses at acceptably low voltages. Here we report on a new high capacitance material fabricated using nitrogen included ultrananocrystalline diamond (N-UNCD). After exposure to oxygen plasma for 3 h, the activated N-UNCD exhibited extremely high electrochemical capacitance greater than 1 mF/cm(2), which originates from the special hybrid sp(2)/sp(3) structure of N-UNCD. The in vitro biocompatibility of the activated N-UNCD was then assessed using rat cortical neurons and surface roughness was found to be critical for healthy neuron growth, with best results observed on surfaces with a roughness of approximately 20 nm. Therefore, by using oxygen plasma activated N-UNCD with appropriate surface roughness, and considering the chemical and mechanical stability of diamond, the fabricated neural interfaces are expected to exhibit high efficacy, long-term stability and a healthy neuron/electrode interface. Copyright © 2016 Elsevier Ltd. All rights reserved.
NASA Technical Reports Server (NTRS)
Stefanescu, Doru M.; Moitra, Avijit; Kacar, A. Sedat; Dhindaw, Brij K.
1990-01-01
Directional solidification experiments in a Bridgman-type furnace were used to study particle behavior at the liquid/solid interface in aluminum metal matrix composites. Graphite or silicon-carbide particles were first dispersed in aluminum-base alloys via a mechanically stirred vortex. Then, 100-mm-diameter and 120-mm-long samples were cast in steel dies and used for directional solidification. The processing variables controlled were the direction and velocity of solidification and the temperature gradient at the interface. The material variables monitored were the interface energy, the liquid/particle density difference, the particle/liquid thermal conductivity ratio, and the volume fraction of particles. These properties were changed by selecting combinations of particles (graphite or silicon carbide) and alloys (Al-Cu, Al-Mg, Al-Ni). A model which consideres process thermodynamics, process kinetics (including the role of buoyant forces), and thermophysical properties was developed. Based on solidification direction and velocity, and on materials properties, four types of behavior were predicted. Sessile drop experiments were also used to determine some of the interface energies required in calculation with the proposed model. Experimental results compared favorably with model predictions.
Human-machine interface for a VR-based medical imaging environment
NASA Astrophysics Data System (ADS)
Krapichler, Christian; Haubner, Michael; Loesch, Andreas; Lang, Manfred K.; Englmeier, Karl-Hans
1997-05-01
Modern 3D scanning techniques like magnetic resonance imaging (MRI) or computed tomography (CT) produce high- quality images of the human anatomy. Virtual environments open new ways to display and to analyze those tomograms. Compared with today's inspection of 2D image sequences, physicians are empowered to recognize spatial coherencies and examine pathological regions more facile, diagnosis and therapy planning can be accelerated. For that purpose a powerful human-machine interface is required, which offers a variety of tools and features to enable both exploration and manipulation of the 3D data. Man-machine communication has to be intuitive and efficacious to avoid long accustoming times and to enhance familiarity with and acceptance of the interface. Hence, interaction capabilities in virtual worlds should be comparable to those in the real work to allow utilization of our natural experiences. In this paper the integration of hand gestures and visual focus, two important aspects in modern human-computer interaction, into a medical imaging environment is shown. With the presented human- machine interface, including virtual reality displaying and interaction techniques, radiologists can be supported in their work. Further, virtual environments can even alleviate communication between specialists from different fields or in educational and training applications.
NASA Astrophysics Data System (ADS)
Stefanescu, Doru M.; Moitra, Avijit; Kacar, A. Sedat; Dhindaw, Brij K.
1990-01-01
Directional solidification experiments in a Bridgman-type furnace were used to study particle behavior at the liquid/solid interface in aluminum metal matrix composites. Graphite or siliconcarbide particles were first dispersed in aluminum-base alloys via a mechanically stirred vortex. Then, 100-mm-diameter and 120-mm-long samples were cast in steel dies and used for directional solidification. The processing variables controlled were the direction and velocity of solidification and the temperature gradient at the interface. The material variables monitored were the interface energy, the liquid/particle density difference, the particle/liquid thermal conductivity ratio, and the volume fraction of particles. These properties were changed by selecting combinations of particles (graphite or silicon carbide) and alloys (Al-Cu, Al-Mg, Al-Ni). A model which considers process thermodynamics, process kinetics (including the role of buoyant forces), and thermophysical properties was developed. Based on solidification direction and velocity, and on materials properties, four types of behavior were predicted. Sessile drop experiments were also used to determine some of the interface energies required in calculation with the proposed model. Experimental results compared favorably with model predictions.
Human-telerobot interactions - Information, control, and mental models
NASA Technical Reports Server (NTRS)
Smith, Randy L.; Gillan, Douglas J.
1987-01-01
A part of the NASA's Space Station will be a teleoperated robot (telerobot) with arms for grasping and manipulation, feet for holding onto objects, and television cameras for visual feedback. The objective of the work described in this paper is to develop the requirements and specifications for the user-telerobot interface and to determine through research and testing that the interface results in efficient system operation. The focus of the development of the user-telerobot interface is on the information required by the user, the user inputs, and the design of the control workstation. Closely related to both the information required by the user and the user's control of the telerobot is the user's mental model of the relationship between the control inputs and the telerobot's actions.
Lunar Reconnaissance Orbiter (LRO) Command and Data Handling Flight Electronics Subsystem
NASA Technical Reports Server (NTRS)
Nguyen, Quang; Yuknis, William; Haghani, Noosha; Pursley, Scott; Haddad, Omar
2012-01-01
A document describes a high-performance, modular, and state-of-the-art Command and Data Handling (C&DH) system developed for use on the Lunar Reconnaissance Orbiter (LRO) mission. This system implements a complete hardware C&DH subsystem in a single chassis enclosure that includes a processor card, 48 Gbytes of solid-state recorder memory, data buses including MIL-STD-1553B, custom RS-422, SpaceWire, analog collection, switched power services, and interfaces to the Ka-Band and S-Band RF communications systems. The C&DH team capitalized on extensive experience with hardware and software with PCI bus design, SpaceWire networking, Actel FPGA design, digital flight design techniques, and the use of VxWorks for the real-time operating system. The resulting hardware architecture was implemented to meet the LRO mission requirements. The C&DH comprises an enclosure, a backplane, a low-voltage power converter, a single-board computer, a communications interface board, four data storage boards, a housekeeping and digital input/output board, and an analog data acquisition board. The interfaces between the C&DH and the instruments and avionics are connected through a SpaceWire network, a MIL-STD-1553 bus, and a combination of synchronous and asynchronous serial data transfers over RS-422 and LVDS (low-voltage differential-signaling) electrical interfaces. The C&DH acts as the spacecraft data system with an instrument data manager providing all software and internal bus scheduling, ingestion of science data, distribution of commands, and performing science operations in real time.
NASA Technical Reports Server (NTRS)
Malone, T. B.
1972-01-01
Requirements were determined analytically for the man machine interface for a teleoperator system performing on-orbit satellite retrieval and servicing. Requirements are basically of two types; mission/system requirements, and design requirements or design criteria. Two types of teleoperator systems were considered: a free flying vehicle, and a shuttle attached manipulator. No attempt was made to evaluate the relative effectiveness or efficiency of the two system concepts. The methodology used entailed an application of the Essex Man-Systems analysis technique as well as a complete familiarization with relevant work being performed at government agencies and by private industry.
Finite-Element Analysis of a Mach-8 Flight Test Article Using Nonlinear Contact Elements
NASA Technical Reports Server (NTRS)
Richards, W. Lance
1997-01-01
A flight test article, called a glove, is required for a Mach-8 boundary-layer experiment to be conducted on a flight mission of the air-launched Pegasus(reg) space booster. The glove is required to provide a smooth, three-dimensional, structurally stable, aerodynamic surface and includes instrumentation to determine when and where boundary-layer transition occurs during the hypersonic flight trajectory. A restraint mechanism has been invented to attach the glove to the wing of the space booster. The restraint mechanism securely attaches the glove to the wing in directions normal to the wing/glove interface surface, but allows the glove to thermally expand and contract to alleviate stresses in directions parallel to the interface surface. A finite-element analysis has been performed using nonlinear contact elements to model the complex behavior of the sliding restraint mechanism. This paper provides an overview of the glove design and presents details of the analysis that were essential to demonstrate the flight worthiness of the wing-glove test article. Results show that all glove components are well within the allowable stress and deformation requirements to satisfy the objectives of the flight research experiment.
Risk Mitigation Approach to Commercial Resupply to the International Space Station
NASA Technical Reports Server (NTRS)
Koons, Diane S.; Schreiber, Craig
2010-01-01
In August 2006, NASA awarded Space Act Agreements (SAAs) for Commercial Orbital Transportation Services (COTS) under the Commercial Crew and Cargo Project Office at Johnson Space Center. One of the goals of the SAAs is to facilitate U.S. private industry demonstration of cargo transportation capabilities, ultimately achieving reliable, cost effective access to low-Earth orbit (LEO). Each COTS provider is required to complete International Space Stations (ISS) Integration activities, which includes meeting the physical and functional interfaces and interface requirements between the ISS and COTS vehicles. These requirements focus on the areas of risk to the ISS during rendezvous and proximity operations, as well as the integration operations while the COTS vehicle is berthed to the ISS. On December 23, 2008, NASA awarded Commercial Resupply Service (CRS) contracts to provide resupply services to the ISS, following the Shuttle retirement. In addition to performing any ISS Integration activities, NASA will be performing independent assessments of the launch vehicle and orbital vehicle to evaluate the readiness of the contractor to deliver NASA cargo safely to the ISS. This paper will address the activities NASA Centers, both JSC and KSC, in the oversight and insight function over commercial visiting vehicles to the ISS.
Human factors issues in telerobotic systems for Space Station Freedom servicing
NASA Technical Reports Server (NTRS)
Malone, Thomas B.; Permenter, Kathryn E.
1990-01-01
Requirements for Space Station Freedom servicing are described and the state-of-the-art for telerobotic system on-orbit servicing of spacecraft is defined. The projected requirements for the Space Station Flight Telerobotic Servicer (FTS) are identified. Finally, the human factors issues in telerobotic servicing are discussed. The human factors issues are basically three: the definition of the role of the human versus automation in system control; the identification of operator-device interface design requirements; and the requirements for development of an operator-machine interface simulation capability.
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.
Development of Web Interfaces for Analysis Codes
NASA Astrophysics Data System (ADS)
Emoto, M.; Watanabe, T.; Funaba, H.; Murakami, S.; Nagayama, Y.; Kawahata, K.
Several codes have been developed to analyze plasma physics. However, most of them are developed to run on supercomputers. Therefore, users who typically use personal computers (PCs) find it difficult to use these codes. In order to facilitate the widespread use of these codes, a user-friendly interface is required. The authors propose Web interfaces for these codes. To demonstrate the usefulness of this approach, the authors developed Web interfaces for two analysis codes. One of them is for FIT developed by Murakami. This code is used to analyze the NBI heat deposition, etc. Because it requires electron density profiles, electron temperatures, and ion temperatures as polynomial expressions, those unfamiliar with the experiments find it difficult to use this code, especially visitors from other institutes. The second one is for visualizing the lines of force in the LHD (large helical device) developed by Watanabe. This code is used to analyze the interference caused by the lines of force resulting from the various structures installed in the vacuum vessel of the LHD. This code runs on PCs; however, it requires that the necessary parameters be edited manually. Using these Web interfaces, users can execute these codes interactively.
NASA Technical Reports Server (NTRS)
Lu, George C.
2003-01-01
The purpose of the EXPRESS (Expedite the PRocessing of Experiments to Space Station) rack project is to provide a set of predefined interfaces for scientific payloads which allow rapid integration into a payload rack on International Space Station (ISS). VxWorks' was selected as the operating system for the rack and payload resource controller, primarily based on the proliferation of VME (Versa Module Eurocard) products. These products provide needed flexibility for future hardware upgrades to meet everchanging science research rack configuration requirements. On the International Space Station, there are multiple science research rack configurations, including: 1) Human Research Facility (HRF); 2) EXPRESS ARIS (Active Rack Isolation System); 3) WORF (Window Observational Research Facility); and 4) HHR (Habitat Holding Rack). The RIC (Rack Interface Controller) connects payloads to the ISS bus architecture for data transfer between the payload and ground control. The RIC is a general purpose embedded computer which supports multiple communication protocols, including fiber optic communication buses, Ethernet buses, EIA-422, Mil-Std-1553 buses, SMPTE (Society Motion Picture Television Engineers)-170M video, and audio interfaces to payloads and the ISS. As a cost saving and software reliability strategy, the Boeing Payload Software Organization developed reusable common software where appropriate. These reusable modules included a set of low-level driver software interfaces to 1553B. RS232, RS422, Ethernet buses, HRDL (High Rate Data Link), video switch functionality, telemetry processing, and executive software hosted on the FUC computer. These drivers formed the basis for software development of the HRF, EXPRESS, EXPRESS ARIS, WORF, and HHR RIC executable modules. The reusable RIC common software has provided extensive benefits, including: 1) Significant reduction in development flow time; 2) Minimal rework and maintenance; 3) Improved reliability; and 4) Overall reduction in software life cycle cost. Due to the limited number of crew hours available on ISS for science research, operational efficiency is a critical customer concern. The current method of upgrading RIC software is a time consuming process; thus, an improved methodology for uploading RIC software is currently under evaluation.
Test Telemetry And Command System (TTACS)
NASA Technical Reports Server (NTRS)
Fogel, Alvin J.
1994-01-01
The Jet Propulsion Laboratory has developed a multimission Test Telemetry and Command System (TTACS) which provides a multimission telemetry and command data system in a spacecraft test environment. TTACS reuses, in the spacecraft test environment, components of the same data system used for flight operations; no new software is developed for the spacecraft test environment. Additionally, the TTACS is transportable to any spacecraft test site, including the launch site. The TTACS is currently operational in the Galileo spacecraft testbed; it is also being provided to support the Cassini and Mars Surveyor Program projects. Minimal personnel data system training is required in the transition from pre-launch spacecraft test to post-launch flight operations since test personnel are already familiar with the data system's operation. Additionally, data system components, e.g. data display, can be reused to support spacecraft software development; and the same data system components will again be reused during the spacecraft integration and system test phases. TTACS usage also results in early availability of spacecraft data to data system development and, as a result, early data system development feedback to spacecraft system developers. The TTACS consists of a multimission spacecraft support equipment interface and components of the multimission telemetry and command software adapted for a specific project. The TTACS interfaces to the spacecraft, e.g., Command Data System (CDS), support equipment. The TTACS telemetry interface to the CDS support equipment performs serial (RS-422)-to-ethernet conversion at rates between 1 bps and 1 mbps, telemetry data blocking and header generation, guaranteed data transmission to the telemetry data system, and graphical downlink routing summary and control. The TTACS command interface to the CDS support equipment is nominally a command file transferred in non-real-time via ethernet. The CDS support equipment is responsible for metering the commands to the CDS; additionally for Galileo, TTACS includes a real-time-interface to the CDS support equipment. The TTACS provides the basic functionality of the multimission telemetry and command data system used during flight operations. TTACS telemetry capabilities include frame synchronization, Reed-Solomon decoding, packet extraction and channelization, and data storage/query. Multimission data display capabilities are also available. TTACS command capabilities include command generation verification, and storage.
Development of simulation computer complex specification
NASA Technical Reports Server (NTRS)
1973-01-01
The Training Simulation Computer Complex Study was one of three studies contracted in support of preparations for procurement of a shuttle mission simulator for shuttle crew training. The subject study was concerned with definition of the software loads to be imposed on the computer complex to be associated with the shuttle mission simulator and the development of procurement specifications based on the resulting computer requirements. These procurement specifications cover the computer hardware and system software as well as the data conversion equipment required to interface the computer to the simulator hardware. The development of the necessary hardware and software specifications required the execution of a number of related tasks which included, (1) simulation software sizing, (2) computer requirements definition, (3) data conversion equipment requirements definition, (4) system software requirements definition, (5) a simulation management plan, (6) a background survey, and (7) preparation of the specifications.
Space Station module Power Management And Distribution (PMAD) system
NASA Technical Reports Server (NTRS)
Walls, Bryan
1990-01-01
This project consists of several tasks which are unified toward experimentally demonstrating the operation of a highly autonomous, user-supportive power management and distribution system for Space Station Freedom (SSF) habitation/laboratory modules. This goal will be extended to a demonstration of autonomous, cooperative power system operation for the whole SSF power system through a joint effort with NASA's Lewis Research Center, using their Autonomous Power System. Short term goals for the space station module power management and distribution include having an operational breadboard reflecting current plans for SSF, improving performance of the system communications, and improving the organization and mutability of the artificial intelligence (AI) systems. In the middle term, intermediate levels of autonomy will be added, user interfaces will be modified, and enhanced modeling capabilities will be integrated in the system. Long term goals involve conversion of all software into Ada, vigorous verification and validation efforts and, finally, seeing an impact of this research on the operation of SSF. Conversion of the system to a DC Star configuration is now in progress, and should be completed by the end of October, 1989. This configuration reflects the latest SSF module architecture. Hardware is now being procured which will improve system communications significantly. The Knowledge-Based Management System (KBMS) is initially developed and the rules from FRAMES have been implemented in the KBMS. Rules in the other two AI systems are also being grouped modularly, making them more tractable, and easier to eventually move into the KBMS. Adding an intermediate level of autonomy will require development of a planning utility, which will also be built using the KBMS. These changes will require having the user interface for the whole system available from one interface. An Enhanced Model will be developed, which will allow exercise of the system through the interface without requiring all of the power hardware to be operational. The functionality of the AI systems will continue to be advanced, including incipient failure detection. Ada conversion will begin with the lowest level processor (LLP) code. Then selected pieces of the higher level functionality will be recorded in Ada and, where possible, moved to the LLP level. Validation and verification will be done on the Ada code, and will complete sometimes after completion of the Ada conversion.
Mars rover/sample return mission requirements affecting space station
NASA Technical Reports Server (NTRS)
1988-01-01
The possible interfaces between the Space Station and the Mars Rover/Sample Return (MRSR) mission are defined. In order to constrain the scope of the report a series of seven design reference missions divided into three major types were assumed. These missions were defined to span the probable range of Space Station-MRSR interactions. The options were reduced, the MRSR sample handling requirements and baseline assumptions about the MRSR hardware and the key design features and requirements of the Space Station are summarized. Only the aspects of the design reference missions necessary to define the interfaces, hooks and scars, and other provisions on the Space Station are considered. An analysis of each of the three major design reference missions, is reported, presenting conceptual designs of key hardware to be mounted on the Space Station, a definition of weights, interfaces, and required hooks and scars.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Shoup, R.W.; Long, F.; Martin, T.H.
Sandia is developing PBFA-Z, a 20-MA driver for z-pinch experiments by replacing the water lines, insulator stack, and MITLs on PBFA II with new hardware. The design of the vacuum insulator stack was dictated by the drive voltage, the electric field stress and grading requirements, the water line and MITL interface requirements, and the machine operations and maintenance requirements. The insulator stack will consist of four separate modules, each of a different design because of different voltage drive and hardware interface requirements. The shape of the components in each module, i.e., grading rings, insulator rings, flux excluders, anode and cathodemore » conductors, and the design of the water line and MITL interfaces, were optimized by using the electrostatic analysis codes, ELECTRO and JASON. The time dependent performance of the insulator stack was evaluated using IVORY, a 2-D PIC code. This paper will describe the insulator stack design and present the results of the ELECTRO and IVORY analyses.« less
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.
AQBE — QBE Style Queries for Archetyped Data
NASA Astrophysics Data System (ADS)
Sachdeva, Shelly; Yaginuma, Daigo; Chu, Wanming; Bhalla, Subhash
Large-scale adoption of electronic healthcare applications requires semantic interoperability. The new proposals propose an advanced (multi-level) DBMS architecture for repository services for health records of patients. These also require query interfaces at multiple levels and at the level of semi-skilled users. In this regard, a high-level user interface for querying the new form of standardized Electronic Health Records system has been examined in this study. It proposes a step-by-step graphical query interface to allow semi-skilled users to write queries. Its aim is to decrease user effort and communication ambiguities, and increase user friendliness.
Lunar Extravehicular Activity Program
NASA Technical Reports Server (NTRS)
Heartsill, Amy Ellison
2006-01-01
Extravehicular Activity (EVA) has proven an invaluable tool for space exploration since the inception of the space program. There are situations in which the best means to evaluate, observe, explore and potentially troubleshoot space systems are accomplished by direct human intervention. EVA provides this unique capability. There are many aspects of the technology required to enable a "miniature spaceship" to support individuals in a hostile environment in order to accomplish these tasks. This includes not only the space suit assembly itself, but the tools, design interfaces of equipment on which EVA must work and the specific vehicles required to support transfer of humans between habitation areas and the external world. This lunar mission program will require EVA support in three primary areas. The first of these areas include Orbital stage EVA or micro-gravity EVA which includes both Low Earth Orbit (LEO), transfer and Lunar Orbit EVA. The second area is Lunar Lander EVA capability, which is lunar surface EVA and carries slightly different requirements from micro-gravity EVA. The third and final area is Lunar Habitat based surface EVA, which is the final system supporting a long-term presence on the moon.
NEXT Single String Integration Test Results
NASA Technical Reports Server (NTRS)
Soulas, George C.; Patterson, Michael J.; Pinero, Luis; Herman, Daniel A.; Snyder, Steven John
2010-01-01
As a critical part of NASA's Evolutionary Xenon Thruster (NEXT) test validation process, a single string integration test was performed on the NEXT ion propulsion system. The objectives of this test were to verify that an integrated system of major NEXT ion propulsion system elements meets project requirements, to demonstrate that the integrated system is functional across the entire power processor and xenon propellant management system input ranges, and to demonstrate to potential users that the NEXT propulsion system is ready for transition to flight. Propulsion system elements included in this system integration test were an engineering model ion thruster, an engineering model propellant management system, an engineering model power processor unit, and a digital control interface unit simulator that acted as a test console. Project requirements that were verified during this system integration test included individual element requirements ; integrated system requirements, and fault handling. This paper will present the results of these tests, which include: integrated ion propulsion system demonstrations of performance, functionality and fault handling; a thruster re-performance acceptance test to establish baseline performance: a risk-reduction PMS-thruster integration test: and propellant management system calibration checks.
Influence of Learning Styles on Graphical User Interface Preferences for e-Learners
ERIC Educational Resources Information Center
Dedic, Velimir; Markovic, Suzana
2012-01-01
Implementing Web-based educational environment requires not only developing appropriate architectures, but also incorporating human factors considerations. User interface becomes the major channel to convey information in e-learning context: a well-designed and friendly enough interface is thus the key element in helping users to get the best…
Methods for Improving the User-Computer Interface. Technical Report.
ERIC Educational Resources Information Center
McCann, Patrick H.
This summary of methods for improving the user-computer interface is based on a review of the pertinent literature. Requirements of the personal computer user are identified and contrasted with computer designer perspectives towards the user. The user's psychological needs are described, so that the design of the user-computer interface may be…
M"Health" for Higher Education
ERIC Educational Resources Information Center
Aburas, Abdurazzag A.; Ayran, Mujgan
2013-01-01
Better education is required better advanced tools to be used for students. Smart phone becomes main part of our daily life. New medical design interface is introduced for medicine student based mobile. The Graphic User Interface must be easy and simple. The main interface design issue for mobile is simple and easy to use. Human Mobile…
Picosecond laser bonding of highly dissimilar materials
NASA Astrophysics Data System (ADS)
Carter, Richard M.; Troughton, Michael; Chen, Jianyong; Elder, Ian; Thomson, Robert R.; Lamb, Robert A.; Esser, M. J. Daniel; Hand, Duncan P.
2016-10-01
We report on recent progress in developing an industrially relevant, robust technique to bond dissimilar materials through ultra-fast microwelding. This technique is based on the use of a 5.9ps, 400kHz Trumpf laser operating at 1030nm. Tight focusing of the laser radiation at, or around, the interface between two materials allows for simultaneous absorption in both. This absorption rapidly, and locally, heats the material forming plasma from both materials. With suitable surface preparation this plasma can be confined to the interface region where it mixes, cools and forms a weld between the two materials. The use of ps pulses results in a short interaction time. This enables a bond to form whilst limiting the heat affected zone (HAZ) to a region of only a few hundred micrometres across. This small scale allows for the bonding of materials with highly dissimilar thermal properties, and in particular coefficients of thermal expansion e.g. glass-metal bonding. We report on our results for a range of material combinations including, Al-Bk7, Al-SiO2 and Nd:YAG-AlSi. Emphasis will be laid on the technical requirements for bonding including the required surface preparation of the two materials and on the laser parameters required. The quality of the resultant bonds are characterized through shear force measurements (where strengths equal to and exceeding equivalent adhesives will be presented). The lifetime of the welds is also discussed, paying particular attention to the results of thermal cycling tests.
General-Purpose Electronic System Tests Aircraft
NASA Technical Reports Server (NTRS)
Glover, Richard D.
1989-01-01
Versatile digital equipment supports research, development, and maintenance. Extended aircraft interrogation and display system is general-purpose assembly of digital electronic equipment on ground for testing of digital electronic systems on advanced aircraft. Many advanced features, including multiple 16-bit microprocessors, pipeline data-flow architecture, advanced operating system, and resident software-development tools. Basic collection of software includes program for handling many types of data and for displays in various formats. User easily extends basic software library. Hardware and software interfaces to subsystems provided by user designed for flexibility in configuration to meet user's requirements.
Multidisciplinary propulsion simulation using NPSS
NASA Technical Reports Server (NTRS)
Claus, Russell W.; Evans, Austin L.; Follen, Gregory J.
1992-01-01
The current status of the Numerical Propulsion System Simulation (NPSS) program, a cooperative effort of NASA, industry, and universities to reduce the cost and time of advanced technology propulsion system development, is reviewed. The technologies required for this program include (1) interdisciplinary analysis to couple the relevant disciplines, such as aerodynamics, structures, heat transfer, combustion, acoustics, controls, and materials; (2) integrated systems analysis; (3) a high-performance computing platform, including massively parallel processing; and (4) a simulation environment providing a user-friendly interface. Several research efforts to develop these technologies are discussed.
Handheld portable real-time tracking and communications device
Wiseman, James M [Albuquerque, NM; Riblett, Jr., Loren E.; Green, Karl L [Albuquerque, NM; Hunter, John A [Albuquerque, NM; Cook, III, Robert N.; Stevens, James R [Arlington, VA
2012-05-22
Portable handheld real-time tracking and communications devices include; a controller module, communications module including global positioning and mesh network radio module, data transfer and storage module, and a user interface module enclosed in a water-resistant enclosure. Real-time tracking and communications devices can be used by protective force, security and first responder personnel to provide situational awareness allowing for enhance coordination and effectiveness in rapid response situations. Such devices communicate to other authorized devices via mobile ad-hoc wireless networks, and do not require fixed infrastructure for their operation.
NASA Technical Reports Server (NTRS)
1974-01-01
The charactertistics and performance capability of the current Viking '75 Gas Chromatograph/Mass Spectrometer Instrument are reviewed and documented for the purpose of possible integration with a wet chemistry instrument. Interface, high mass discrimination, and vacuum requirements were determined in a simulated flight investigation. Suggestions for future investigations, tradeoff studies, and design modifications are presented, along with the results of column bleed measurements. A preliminary design of an integrated Wet Chemistry/Mass Spectrometer instrument for amino acid analysis is shown, including estimates of additional weight, volume, and power requirements.
Phase C/D program development plan. Volume 1: Program plan
NASA Technical Reports Server (NTRS)
1971-01-01
The Phase C/D definition of the Modular Space Station has been developed. The modular approach selected during the option period was evaluated, requirements were defined, and program definition and preliminary design were accomplished. The Space Station Project is covered in depth, the research applications module is limited to a project-level definition, and the shuttle operations are included for interface requirements identification, scheduling, and costing. Discussed in detail are: (1) baseline program and project descriptions; (2) phase project planning; (3) modular space station program schedule; (4) program management plan; (5) operations; (6) facilities; (7) logistics; and (8) manpower.
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.
Propulsion/flight control integration technology (PROFIT) design analysis status
NASA Technical Reports Server (NTRS)
Carlin, C. M.; Hastings, W. J.
1978-01-01
The propulsion flight control integration technology (PROFIT) program was designed to develop a flying testbed dedicated to controls research. The preliminary design, analysis, and feasibility studies conducted in support of the PROFIT program are reported. The PROFIT system was built around existing IPCS hardware. In order to achieve the desired system flexibility and capability, additional interfaces between the IPCS hardware and F-15 systems were required. The requirements for additions and modifications to the existing hardware were defined. Those interfaces involving the more significant changes were studied. The DCU memory expansion to 32K with flight qualified hardware was completed on a brassboard basis. The uplink interface breadboard and a brassboard of the central computer interface were also tested. Two preliminary designs and corresponding program plans are presented.
Development of a graphical user interface for the global land information system (GLIS)
Alstad, Susan R.; Jackson, David A.
1993-01-01
The process of developing a Motif Graphical User Interface for the Global Land Information System (GLIS) involved incorporating user requirements, in-house visual and functional design requirements, and Open Software Foundation (OSF) Motif style guide standards. Motif user interface windows have been developed using the software to support Motif window functions war written using the C programming language. The GLIS architecture was modified to support multiple servers and remote handlers running the X Window System by forming a network of servers and handlers connected by TCP/IP communications. In April 1993, prior to release the GLIS graphical user interface and system architecture modifications were test by developers and users located at the EROS Data Center and 11 beta test sites across the country.
Experiences in Interagency and International Interfaces for Mission Support
NASA Technical Reports Server (NTRS)
Dell, G. T.; Mitchell, W. J.; Thompson, T. W.; Cappellari, J. O., Jr.; Flores-Amaya, F.
1996-01-01
The Flight Dynamics Division (FDD) of the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GFSC) provides extensive support and products for Space Shuttle missions, expendable launch vehicle launches, and routine on-orbit operations for a variety of spacecraft. A major challenge in providing support for these missions is defining and generating the products required for mission support and developing the method by which these products are exchanged between supporting agencies. As interagency and international cooperation has increased in the space community, the FDD customer base has grown and with it the number and variety of external interfaces and product definitions. Currently, the FDD has working interfaces with the NASA Space and Ground Networks, the Johnson Space Center, the White Sands Complex, the Jet propulsion Laboratory (including the Deep Space Network), the United States Air Force, the Centre National d'Etudes Spatiales, the German Spaceflight Operations Center, the European Space Agency, and the National Space Development Agency of Japan. With the increasing spectrum of possible data product definitions and delivery methods, the FDD is using its extensive interagency experience to improve its support of established customers and to provide leadership in adapting/developing new interfaces. This paper describes the evolution of the interfaces between the FDD and its customers, discusses many of the joint activities ith these customers, and summarizes key lessons learned that can be applied to current and future support.
Plutonium Immobilization Project System Design Description for Can Loading System
DOE Office of Scientific and Technical Information (OSTI.GOV)
Kriikku, E.
2001-02-15
The purpose of this System Design Description (SDD) is to specify the system and component functions and requirements for the Can Loading System and provide a complete description of the system (design features, boundaries, and interfaces), principles of operation (including upsets and recovery), and the system maintenance approach. The Plutonium Immobilization Project (PIP) will immobilize up to 13 metric tons (MT) of U.S. surplus weapons usable plutonium materials.
Thermal Design, Analysis, and Testing of the Quench Module Insert Bread Board
NASA Technical Reports Server (NTRS)
Breeding, Shawn; Khodabandeh, Julia
2002-01-01
Contents include the following: Quench Module Insert (QMI) science requirements. QMI interfaces. QMI design layout. QMI thermal analysis and design methodology. QMI bread board testing and instrumentation approach. QMI thermal probe design parameters. Design features for gradient measurement. Design features for heated zone measurements. Thermal gradient analysis results. Heated zone analysis results. Bread board thermal probe layout. QMI bread board correlation and performance. Summary and conclusions.
Shuttle orbiter S-band communications equipment design evaluation
NASA Technical Reports Server (NTRS)
Springett, J. C.
1979-01-01
An assessment of S-band communication equipment includes: (1) the review and analysis of the ability of the various subsystem avionic equipment designs to interface with, and operate on signals from/to adjoining equipment; (2) the performance peculiarities of the hardware against the overall specified system requirements; and (3) the evaluation of EMC EMI test results of the various equipment with respect to the possibility of mutual interferences.
A life sciences Spacelab mission simulation
NASA Technical Reports Server (NTRS)
Mason, J. A.; Musgrave, F. S.; Morrison, D. R.
1977-01-01
The paper describes the purposes of a seven-day simulated life-sciences mission conducted in a Spacelab simulator. A major objective was the evaluation of in-orbit Spacelab operations and those mission control support functions which will be required from the Payload Operations Center. Tested equipment and procedures included experiment racks, common operational research equipment, commercial off-the-shelf equipment, experiment hardware interfaces with Spacelab, experiment data handling concepts, and Spacelab trash management.
2014-09-01
efficient yet safe operations. • Further understanding of human psychology in the operation of autonomous systems. • Interfaces, be they visual...that system, especially when included in aspects or during times where automation backup is required, when the human-operators anticipatory skills...political and psychological domains, where it connotes self-determination (Christman 2009). The autonomous systems domain that has evolved since
Integration of advanced teleoperation technologies for control of space robots
NASA Technical Reports Server (NTRS)
Stagnaro, Michael J.
1993-01-01
Teleoperated robots require one or more humans to control actuators, mechanisms, and other robot equipment given feedback from onboard sensors. To accomplish this task, the human or humans require some form of control station. Desirable features of such a control station include operation by a single human, comfort, and natural human interfaces (visual, audio, motion, tactile, etc.). These interfaces should work to maximize performance of the human/robot system by streamlining the link between human brain and robot equipment. This paper describes development of a control station testbed with the characteristics described above. Initially, this testbed will be used to control two teleoperated robots. Features of the robots include anthropomorphic mechanisms, slaving to the testbed, and delivery of sensory feedback to the testbed. The testbed will make use of technologies such as helmet mounted displays, voice recognition, and exoskeleton masters. It will allow tor integration and testing of emerging telepresence technologies along with techniques for coping with control link time delays. Systems developed from this testbed could be applied to ground control of space based robots. During man-tended operations, the Space Station Freedom may benefit from ground control of IVA or EVA robots with science or maintenance tasks. Planetary exploration may also find advanced teleoperation systems to be very useful.
Scalable polylithic on-package integratable apparatus and method
DOE Office of Scientific and Technical Information (OSTI.GOV)
Khare, Surhud; Somasekhar, Dinesh; Borkar, Shekhar Y.
Described is an apparatus which comprises: a first die including: a processing core; a crossbar switch coupled to the processing core; and a first edge interface coupled to the crossbar switch; and a second die including: a first edge interface positioned at a periphery of the second die and coupled to the first edge interface of the first die, wherein the first edge interface of the first die and the first edge interface of the second die are positioned across each other; a clock synchronization circuit coupled to the second edge interface; and a memory interface coupled to the clockmore » synchronization circuit.« less
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.
The MOLGENIS toolkit: rapid prototyping of biosoftware at the push of a button.
Swertz, Morris A; Dijkstra, Martijn; Adamusiak, Tomasz; van der Velde, Joeri K; Kanterakis, Alexandros; Roos, Erik T; Lops, Joris; Thorisson, Gudmundur A; Arends, Danny; Byelas, George; Muilu, Juha; Brookes, Anthony J; de Brock, Engbert O; Jansen, Ritsert C; Parkinson, Helen
2010-12-21
There is a huge demand on bioinformaticians to provide their biologists with user friendly and scalable software infrastructures to capture, exchange, and exploit the unprecedented amounts of new *omics data. We here present MOLGENIS, a generic, open source, software toolkit to quickly produce the bespoke MOLecular GENetics Information Systems needed. The MOLGENIS toolkit provides bioinformaticians with a simple language to model biological data structures and user interfaces. At the push of a button, MOLGENIS' generator suite automatically translates these models into a feature-rich, ready-to-use web application including database, user interfaces, exchange formats, and scriptable interfaces. Each generator is a template of SQL, JAVA, R, or HTML code that would require much effort to write by hand. This 'model-driven' method ensures reuse of best practices and improves quality because the modeling language and generators are shared between all MOLGENIS applications, so that errors are found quickly and improvements are shared easily by a re-generation. A plug-in mechanism ensures that both the generator suite and generated product can be customized just as much as hand-written software. In recent years we have successfully evaluated the MOLGENIS toolkit for the rapid prototyping of many types of biomedical applications, including next-generation sequencing, GWAS, QTL, proteomics and biobanking. Writing 500 lines of model XML typically replaces 15,000 lines of hand-written programming code, which allows for quick adaptation if the information system is not yet to the biologist's satisfaction. Each application generated with MOLGENIS comes with an optimized database back-end, user interfaces for biologists to manage and exploit their data, programming interfaces for bioinformaticians to script analysis tools in R, Java, SOAP, REST/JSON and RDF, a tab-delimited file format to ease upload and exchange of data, and detailed technical documentation. Existing databases can be quickly enhanced with MOLGENIS generated interfaces using the 'ExtractModel' procedure. The MOLGENIS toolkit provides bioinformaticians with a simple model to quickly generate flexible web platforms for all possible genomic, molecular and phenotypic experiments with a richness of interfaces not provided by other tools. All the software and manuals are available free as LGPLv3 open source at http://www.molgenis.org.
EXiO-A Brain-Controlled Lower Limb Exoskeleton for Rhesus Macaques.
Vouga, Tristan; Zhuang, Katie Z; Olivier, Jeremy; Lebedev, Mikhail A; Nicolelis, Miguel A L; Bouri, Mohamed; Bleuler, Hannes
2017-02-01
Recent advances in the field of brain-machine interfaces (BMIs) have demonstrated enormous potential to shape the future of rehabilitation and prosthetic devices. Here, a lower-limb exoskeleton controlled by the intracortical activity of an awake behaving rhesus macaque is presented as a proof-of-concept for a locomotorBMI. A detailed description of the mechanical device, including its innovative features and first experimental results, is provided. During operation, BMI-decoded position and velocity are directly mapped onto the bipedal exoskeleton's motions, which then move the monkey's legs as the monkey remains physicallypassive. To meet the unique requirements of such an application, the exoskeleton's features include: high output torque with backdrivable actuation, size adjustability, and safe user-robot interface. In addition, a novel rope transmission is introduced and implemented. To test the performance of the exoskeleton, a mechanical assessment was conducted, which yielded quantifiable results for transparency, efficiency, stiffness, and tracking performance. Usage under both brain control and automated actuation demonstrates the device's capability to fulfill the demanding needs of this application. These results lay the groundwork for further advancement in BMI-controlled devices for primates including humans.
Payload/orbiter contamination control requirement study: Spacelab configuration contamination study
NASA Technical Reports Server (NTRS)
Bareiss, L. E.; Hetrick, M. A.; Ress, E. B.; Strange, D. A.
1976-01-01
The assessment of the Spacelab carrier induced contaminant environment was continued, and the ability of Spacelab to meet established contamination control criteria for the space transportation system program was determined. The primary areas considered included: (1) updating, refining, and improving the Spacelab contamination computer model and contamination analysis methodology, (2) establishing the resulting adjusted induced environment predictions for comparison with the applicable criteria, (3) determining the Spacelab design and operational requirements necessary to meet the criteria, (4) conducting mission feasibility analyses of the combined Spacelab/Orbiter contaminant environment for specific proposed mission and payload mixes, and (5) establishing a preliminary Spacelab mission support plan as well as model interface requirements; A summary of those activities conducted to date with respect to the modelling, analysis, and predictions of the induced environment, including any modifications in approach or methodology utilized in the contamination assessment of the Spacelab carrier, was presented.
DOE Office of Scientific and Technical Information (OSTI.GOV)
Markel, T.; Meintz, A.; Hardy, K.
2015-05-28
The report begins with a discussion of the current state of the energy and transportation systems, followed by a summary of some VGI scenarios and opportunities. The current efforts to create foundational interface standards are detailed, and the requirements for enabling PEVs as a grid resource are presented. Existing technology demonstrations that include vehicle to grid functions are summarized. The report also includes a data-based discussion on the magnitude and variability of PEVs as a grid resource, followed by an overview of existing simulation tools that vi This report is available at no cost from the National Renewable Energy Laboratorymore » (NREL) at www.nrel.gov/publications. can be used to explore the expansion of VGI to larger grid functions that might offer system and customer value. The document concludes with a summary of the requirements and potential action items that would support greater adoption of VGI.« less
Research needs for a commercial passenger tiltrotor
NASA Technical Reports Server (NTRS)
Unger, George; Alexander, Harold
1991-01-01
The National Aeronautics and Space Administration (NASA) recently completed a series of contracts and studies that examined the technology needs for a tiltrotor aircraft in commercial service as well as military missions. The commercial needs arise out of market-driven requirements that include vertiport location and design, passenger comfort levels and competitive costs. The military needs are derived from time-sensitive missions and combat effectiveness. In response to these results, NASA has decided to address the commercial needs first, recognizing that there will be eventual payoff to military missions as well. Research goals were explored in acoustics, flight dynamics, human factors and displays, dynamics and loads, propulsion, safety, and configuration design. The paper describes the development of these goals from the market requirements and the implications for possible research activities. The aircraft issues that were addressed include number of blades, advanced blade planforms, steep approach requirements and pilot-cockpit interface for civil operations.
P43-S Computational Biology Applications Suite for High-Performance Computing (BioHPC.net)
Pillardy, J.
2007-01-01
One of the challenges of high-performance computing (HPC) is user accessibility. At the Cornell University Computational Biology Service Unit, which is also a Microsoft HPC institute, we have developed a computational biology application suite that allows researchers from biological laboratories to submit their jobs to the parallel cluster through an easy-to-use Web interface. Through this system, we are providing users with popular bioinformatics tools including BLAST, HMMER, InterproScan, and MrBayes. The system is flexible and can be easily customized to include other software. It is also scalable; the installation on our servers currently processes approximately 8500 job submissions per year, many of them requiring massively parallel computations. It also has a built-in user management system, which can limit software and/or database access to specified users. TAIR, the major database of the plant model organism Arabidopsis, and SGN, the international tomato genome database, are both using our system for storage and data analysis. The system consists of a Web server running the interface (ASP.NET C#), Microsoft SQL server (ADO.NET), compute cluster running Microsoft Windows, ftp server, and file server. Users can interact with their jobs and data via a Web browser, ftp, or e-mail. The interface is accessible at http://cbsuapps.tc.cornell.edu/.
Multi-Material ALE with AMR for Modeling Hot Plasmas and Cold Fragmenting Materials
NASA Astrophysics Data System (ADS)
Alice, Koniges; Nathan, Masters; Aaron, Fisher; David, Eder; Wangyi, Liu; Robert, Anderson; David, Benson; Andrea, Bertozzi
2015-02-01
We have developed a new 3D multi-physics multi-material code, ALE-AMR, which combines Arbitrary Lagrangian Eulerian (ALE) hydrodynamics with Adaptive Mesh Refinement (AMR) to connect the continuum to the microstructural regimes. The code is unique in its ability to model hot radiating plasmas and cold fragmenting solids. New numerical techniques were developed for many of the physics packages to work efficiently on a dynamically moving and adapting mesh. We use interface reconstruction based on volume fractions of the material components within mixed zones and reconstruct interfaces as needed. This interface reconstruction model is also used for void coalescence and fragmentation. A flexible strength/failure framework allows for pluggable material models, which may require material history arrays to determine the level of accumulated damage or the evolving yield stress in J2 plasticity models. For some applications laser rays are propagating through a virtual composite mesh consisting of the finest resolution representation of the modeled space. A new 2nd order accurate diffusion solver has been implemented for the thermal conduction and radiation transport packages. One application area is the modeling of laser/target effects including debris/shrapnel generation. Other application areas include warm dense matter, EUV lithography, and material wall interactions for fusion devices.
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.
NASA Technical Reports Server (NTRS)
Raible, E.
1994-01-01
The Panel Library and Editor is a graphical user interface (GUI) builder for the Silicon Graphics IRIS workstation family. The toolkit creates "widgets" which can be manipulated by the user. Its appearance is similar to that of the X-Windows System. The Panel Library is written in C and is used by programmers writing user-friendly mouse-driven applications for the IRIS. GUIs built using the Panel Library consist of "actuators" and "panels." Actuators are buttons, dials, sliders, or other mouse-driven symbols. Panels are groups of actuators that occupy separate windows on the IRIS workstation. The application user can alter variables in the graphics program, or fire off functions with a click on a button. The evolution of data values can be tracked with meters and strip charts, and dialog boxes with text processing can be built. Panels can be stored as icons when not in use. The Panel Editor is a program used to interactively create and test panel library interfaces in a simple and efficient way. The Panel Editor itself uses a panel library interface, so all actions are mouse driven. Extensive context-sensitive on-line help is provided. Programmers can graphically create and test the user interface without writing a single line of code. Once an interface is judged satisfactory, the Panel Editor will dump it out as a file of C code that can be used in an application. The Panel Library (v9.8) and Editor (v1.1) are written in C-Language (63%) and Scheme, a dialect of LISP, (37%) for Silicon Graphics 4D series workstations running IRIX 3.2 or higher. Approximately 10Mb of disk space is required once compiled. 1.5Mb of main memory is required to execute the panel editor. This program is available on a .25 inch streaming magnetic tape cartridge in UNIX tar format for an IRIS, and includes a copy of XScheme, the public-domain Scheme interpreter used by the Panel Editor. The Panel Library Programmer's Manual is included on the distribution media. The Panel Library and Editor were released to COSMIC in 1991. Silicon Graphics, IRIS, and IRIX are trademarks of Silicon Graphics, Inc. X-Window System is a trademark of Massachusetts Institute of Technology.
A Frequency-Domain Substructure System Identification Algorithm
NASA Technical Reports Server (NTRS)
Blades, Eric L.; Craig, Roy R., Jr.
1996-01-01
A new frequency-domain system identification algorithm is presented for system identification of substructures, such as payloads to be flown aboard the Space Shuttle. In the vibration test, all interface degrees of freedom where the substructure is connected to the carrier structure are either subjected to active excitation or are supported by a test stand with the reaction forces measured. The measured frequency-response data is used to obtain a linear, viscous-damped model with all interface-degree of freedom entries included. This model can then be used to validate analytical substructure models. This procedure makes it possible to obtain not only the fixed-interface modal data associated with a Craig-Bampton substructure model, but also the data associated with constraint modes. With this proposed algorithm, multiple-boundary-condition tests are not required, and test-stand dynamics is accounted for without requiring a separate modal test or finite element modeling of the test stand. Numerical simulations are used in examining the algorithm's ability to estimate valid reduced-order structural models. The algorithm's performance when frequency-response data covering narrow and broad frequency bandwidths is used as input is explored. Its performance when noise is added to the frequency-response data and the use of different least squares solution techniques are also examined. The identified reduced-order models are also compared for accuracy with other test-analysis models and a formulation for a Craig-Bampton test-analysis model is also presented.
Dynamical modeling and multi-experiment fitting with PottersWheel
Maiwald, Thomas; Timmer, Jens
2008-01-01
Motivation: Modelers in Systems Biology need a flexible framework that allows them to easily create new dynamic models, investigate their properties and fit several experimental datasets simultaneously. Multi-experiment-fitting is a powerful approach to estimate parameter values, to check the validity of a given model, and to discriminate competing model hypotheses. It requires high-performance integration of ordinary differential equations and robust optimization. Results: We here present the comprehensive modeling framework Potters-Wheel (PW) including novel functionalities to satisfy these requirements with strong emphasis on the inverse problem, i.e. data-based modeling of partially observed and noisy systems like signal transduction pathways and metabolic networks. PW is designed as a MATLAB toolbox and includes numerous user interfaces. Deterministic and stochastic optimization routines are combined by fitting in logarithmic parameter space allowing for robust parameter calibration. Model investigation includes statistical tests for model-data-compliance, model discrimination, identifiability analysis and calculation of Hessian- and Monte-Carlo-based parameter confidence limits. A rich application programming interface is available for customization within own MATLAB code. Within an extensive performance analysis, we identified and significantly improved an integrator–optimizer pair which decreases the fitting duration for a realistic benchmark model by a factor over 3000 compared to MATLAB with optimization toolbox. Availability: PottersWheel is freely available for academic usage at http://www.PottersWheel.de/. The website contains a detailed documentation and introductory videos. The program has been intensively used since 2005 on Windows, Linux and Macintosh computers and does not require special MATLAB toolboxes. Contact: maiwald@fdm.uni-freiburg.de Supplementary information: Supplementary data are available at Bioinformatics online. PMID:18614583
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
Ahmed, Adil; Chandra, Subhash; Herasevich, Vitaly; Gajic, Ognjen; Pickering, Brian W
2011-07-01
The care of critically ill patients generates large quantities of data. Increasingly, these data are presented to the provider within an electronic medical record. The manner in which data are organized and presented can impact on the ability of users to synthesis that data into meaningful information. The objective of this study was to test the hypothesis that novel user interfaces, which prioritize the display of high-value data to providers within system-based packages, reduce task load, and result in fewer errors of cognition compared with established user interfaces that do not. Randomized crossover study. Academic tertiary referral center. Attending, resident and fellow critical care physicians. Novel health care record user interface. Subjects randomly assigned to either a standard electronic medical record or a novel user interface, were asked to perform a structured task. The task required the subjects to use the assigned electronic environment to review the medical record of an intensive care unit patient said to be actively bleeding for data that formed the basis of answers to clinical questions posed in the form of a structured questionnaire. The primary outcome was task load, measured using the paper version of the NASA-task load index. Secondary outcome measures included time to task completion, number of errors of cognition measured by comparison of subject to post hoc gold standard questionnaire responses, and the quantity of information presented to subjects by each environment. Twenty subjects completed the task on eight patients, resulting in 160 patient-provider encounters (80 in each group). The standard electronic medical record contained a much larger data volume with a median (interquartile range) number of data points per patient of 1008 (895-1183) compared with 102 (77-112) contained within the novel user interface. The median (interquartile range) NASA-task load index values were 38.8 (32-45) and 58 (45-65) for the novel user interface compared with the standard electronic medical record (p < .001). The median (interquartile range) times in seconds taken to complete the task for four consecutive patients were 93 (57-132), 60 (48-71), 68 (48-80), and 54 (42-64) for the novel user interface compared with 145 (109-201), 125 (113-162), 129 (100-145), and 112 (92-123) for the standard interface (p < .0001), respectively. The median (interquartile range) number of errors per provider was 0.5 (0-1) and two (0.25-3) for the novel user interface and standard electronic medical record interface, respectively (p = .007). A novel user interface was designed based on the information needs of intensive care unit providers with a specific goal of development being the reduction of task load and errors of cognition associated with filtering, extracting, and using medical data contained within a comprehensive electronic medical record. The results of this simulated clinical experiment suggest that the configuration of the intensive care unit user interface contributes significantly to the task load, time to task completion, and number of errors of cognition associated with the identification, and subsequent use, of relevant patient data. Task-specific user interfaces, developed from an understanding of provider information requirements, offer advantages over interfaces currently available within a standard electronic medical record.
Leaf seal for transition duct in turbine system
Flanagan, James Scott; LeBegue, Jeffrey Scott; McMahan, Kevin Weston; Dillard, Daniel Jackson; Pentecost, Ronnie Ray
2013-06-11
A turbine system is disclosed. In one embodiment, the turbine system includes a transition duct. The transition duct includes an inlet, an outlet, and a passage extending between the inlet and the outlet and defining a longitudinal axis, a radial axis, and a tangential axis. The outlet of the transition duct is offset from the inlet along the longitudinal axis and the tangential axis. The transition duct further includes an interface member for interfacing with a turbine section. The turbine system further includes a leaf seal contacting the interface member to provide a seal between the interface member and the turbine section.
Intelligent subsystem interface for modular hardware system
NASA Technical Reports Server (NTRS)
Caffrey, Robert T. (Inventor); Krening, Douglas N. (Inventor); Lannan, Gregory B. (Inventor); Schneiderwind, Michael J. (Inventor); Schneiderwind, Robert A. (Inventor)
2000-01-01
A single chip application specific integrated circuit (ASIC) which provides a flexible, modular interface between a subsystem and a standard system bus. The ASIC includes a microcontroller/microprocessor, a serial interface for connection to the bus, and a variety of communications interface devices available for coupling to the subsystem. A three-bus architecture, utilizing arbitration, provides connectivity within the ASIC and between the ASIC and the subsystem. The communication interface devices include UART (serial), parallel, analog, and external device interface utilizing bus connections paired with device select signals. A low power (sleep) mode is provided as is a processor disable option.
Automated Tracking of Cell Migration with Rapid Data Analysis.
DuChez, Brian J
2017-09-01
Cell migration is essential for many biological processes including development, wound healing, and metastasis. However, studying cell migration often requires the time-consuming and labor-intensive task of manually tracking cells. To accelerate the task of obtaining coordinate positions of migrating cells, we have developed a graphical user interface (GUI) capable of automating the tracking of fluorescently labeled nuclei. This GUI provides an intuitive user interface that makes automated tracking accessible to researchers with no image-processing experience or familiarity with particle-tracking approaches. Using this GUI, users can interactively determine a minimum of four parameters to identify fluorescently labeled cells and automate acquisition of cell trajectories. Additional features allow for batch processing of numerous time-lapse images, curation of unwanted tracks, and subsequent statistical analysis of tracked cells. Statistical outputs allow users to evaluate migratory phenotypes, including cell speed, distance, displacement, and persistence, as well as measures of directional movement, such as forward migration index (FMI) and angular displacement. © 2017 by John Wiley & Sons, Inc. Copyright © 2017 John Wiley & Sons, Inc.
CLIPS 6.0 - C LANGUAGE INTEGRATED PRODUCTION SYSTEM, VERSION 6.0 (UNIX VERSION)
NASA Technical Reports Server (NTRS)
Donnell, B.
1994-01-01
CLIPS, the C Language Integrated Production System, is a complete environment for developing expert systems -- programs which are specifically intended to model human expertise or knowledge. It is designed to allow artificial intelligence research, development, and delivery on conventional computers. CLIPS 6.0 provides a cohesive tool for handling a wide variety of knowledge with support for three different programming paradigms: rule-based, object-oriented, and procedural. Rule-based programming allows knowledge to be represented as heuristics, or "rules-of-thumb" which specify a set of actions to be performed for a given situation. Object-oriented programming allows complex systems to be modeled as modular components (which can be easily reused to model other systems or create new components). The procedural programming capabilities provided by CLIPS 6.0 allow CLIPS to represent knowledge in ways similar to those allowed in languages such as C, Pascal, Ada, and LISP. Using CLIPS 6.0, one can develop expert system software using only rule-based programming, only object-oriented programming, only procedural programming, or combinations of the three. CLIPS provides extensive features to support the rule-based programming paradigm including seven conflict resolution strategies, dynamic rule priorities, and truth maintenance. CLIPS 6.0 supports more complex nesting of conditional elements in the if portion of a rule ("and", "or", and "not" conditional elements can be placed within a "not" conditional element). In addition, there is no longer a limitation on the number of multifield slots that a deftemplate can contain. The CLIPS Object-Oriented Language (COOL) provides object-oriented programming capabilities. Features supported by COOL include classes with multiple inheritance, abstraction, encapsulation, polymorphism, dynamic binding, and message passing with message-handlers. CLIPS 6.0 supports tight integration of the rule-based programming features of CLIPS with COOL (that is, a rule can pattern match on objects created using COOL). CLIPS 6.0 provides the capability to define functions, overloaded functions, and global variables interactively. In addition, CLIPS can be embedded within procedural code, called as a subroutine, and integrated with languages such as C, FORTRAN and Ada. CLIPS can be easily extended by a user through the use of several well-defined protocols. CLIPS provides several delivery options for programs including the ability to generate stand alone executables or to load programs from text or binary files. CLIPS 6.0 provides support for the modular development and execution of knowledge bases with the defmodule construct. CLIPS modules allow a set of constructs to be grouped together such that explicit control can be maintained over restricting the access of the constructs by other modules. This type of control is similar to global and local scoping used in languages such as C or Ada. By restricting access to deftemplate and defclass constructs, modules can function as blackboards, permitting only certain facts and instances to be seen by other modules. Modules are also used by rules to provide execution control. The CRSV (Cross-Reference, Style, and Verification) utility included with previous version of CLIPS is no longer supported. The capabilities provided by this tool are now available directly within CLIPS 6.0 to aid in the development, debugging, and verification of large rule bases. COSMIC offers four distribution versions of CLIPS 6.0: UNIX (MSC-22433), VMS (MSC-22434), MACINTOSH (MSC-22429), and IBM PC (MSC-22430). Executable files, source code, utilities, documentation, and examples are included on the program media. All distribution versions include identical source code for the command line version of CLIPS 6.0. This source code should compile on any platform with an ANSI C compiler. Each distribution version of CLIPS 6.0, except that for the Macintosh platform, includes an executable for the command line version. For the UNIX version of CLIPS 6.0, the command line interface has been successfully implemented on a Sun4 running SunOS, a DECstation running DEC RISC ULTRIX, an SGI Indigo Elan running IRIX, a DEC Alpha AXP running OSF/1, and an IBM RS/6000 running AIX. Command line interface executables are included for Sun4 computers running SunOS 4.1.1 or later and for the DEC RISC ULTRIX platform. The makefiles may have to be modified slightly to be used on other UNIX platforms. The UNIX, Macintosh, and IBM PC versions of CLIPS 6.0 each have a platform specific interface. Source code, a makefile, and an executable for the Windows 3.1 interface version of CLIPS 6.0 are provided only on the IBM PC distribution diskettes. Source code, a makefile, and an executable for the Macintosh interface version of CLIPS 6.0 are provided only on the Macintosh distribution diskettes. Likewise, for the UNIX version of CLIPS 6.0, only source code and a makefile for an X-Windows interface are provided. The X-Windows interface requires MIT's X Window System, Version 11, Release 4 (X11R4), the Athena Widget Set, and the Xmu library. The source code for the Athena Widget Set is provided on the distribution medium. The X-Windows interface has been successfully implemented on a Sun4 running SunOS 4.1.2 with the MIT distribution of X11R4 (not OpenWindows), an SGI Indigo Elan running IRIX 4.0.5, and a DEC Alpha AXP running OSF/1 1.2. The VAX version of CLIPS 6.0 comes only with the generic command line interface. ASCII makefiles for the command line version of CLIPS are provided on all the distribution media for UNIX, VMS, and DOS. Four executables are provided with the IBM PC version: a windowed interface executable for Windows 3.1 built using Borland C++ v3.1, an editor for use with the windowed interface, a command line version of CLIPS for Windows 3.1, and a 386 command line executable for DOS built using Zortech C++ v3.1. All four executables are capable of utilizing extended memory and require an 80386 CPU or better. Users needing an 8086/8088 or 80286 executable must recompile the CLIPS source code themselves. Users who wish to recompile the DOS executable using Borland C++ or MicroSoft C must use a DOS extender program to produce an executable capable of using extended memory. The version of CLIPS 6.0 for IBM PC compatibles requires DOS v3.3 or later and/or Windows 3.1 or later. It is distributed on a set of three 1.4Mb 3.5 inch diskettes. A hard disk is required. The Macintosh version is distributed in compressed form on two 3.5 inch 1.4Mb Macintosh format diskettes, and requires System 6.0.5, or higher, and 1Mb RAM. The version for DEC VAX/VMS is available in VAX BACKUP format on a 1600 BPI 9-track magnetic tape (standard distribution medium) or a TK50 tape cartridge. The UNIX version is distributed in UNIX tar format on a .25 inch streaming magnetic tape cartridge (Sun QIC-24). For the UNIX version, alternate distribution media and formats are available upon request. The CLIPS 6.0 documentation includes a User's Guide and a three volume Reference Manual consisting of Basic and Advanced Programming Guides and an Interfaces Guide. An electronic version of the documentation is provided on the distribution medium for each version: in MicroSoft Word format for the Macintosh and PC versions of CLIPS, and in both PostScript format and MicroSoft Word for Macintosh format for the UNIX and DEC VAX versions of CLIPS. CLIPS was developed in 1986 and Version 6.0 was released in 1993.
CLIPS 6.0 - C LANGUAGE INTEGRATED PRODUCTION SYSTEM, VERSION 6.0 (IBM PC VERSION)
NASA Technical Reports Server (NTRS)
Donnell, B.
1994-01-01
CLIPS, the C Language Integrated Production System, is a complete environment for developing expert systems -- programs which are specifically intended to model human expertise or knowledge. It is designed to allow artificial intelligence research, development, and delivery on conventional computers. CLIPS 6.0 provides a cohesive tool for handling a wide variety of knowledge with support for three different programming paradigms: rule-based, object-oriented, and procedural. Rule-based programming allows knowledge to be represented as heuristics, or "rules-of-thumb" which specify a set of actions to be performed for a given situation. Object-oriented programming allows complex systems to be modeled as modular components (which can be easily reused to model other systems or create new components). The procedural programming capabilities provided by CLIPS 6.0 allow CLIPS to represent knowledge in ways similar to those allowed in languages such as C, Pascal, Ada, and LISP. Using CLIPS 6.0, one can develop expert system software using only rule-based programming, only object-oriented programming, only procedural programming, or combinations of the three. CLIPS provides extensive features to support the rule-based programming paradigm including seven conflict resolution strategies, dynamic rule priorities, and truth maintenance. CLIPS 6.0 supports more complex nesting of conditional elements in the if portion of a rule ("and", "or", and "not" conditional elements can be placed within a "not" conditional element). In addition, there is no longer a limitation on the number of multifield slots that a deftemplate can contain. The CLIPS Object-Oriented Language (COOL) provides object-oriented programming capabilities. Features supported by COOL include classes with multiple inheritance, abstraction, encapsulation, polymorphism, dynamic binding, and message passing with message-handlers. CLIPS 6.0 supports tight integration of the rule-based programming features of CLIPS with COOL (that is, a rule can pattern match on objects created using COOL). CLIPS 6.0 provides the capability to define functions, overloaded functions, and global variables interactively. In addition, CLIPS can be embedded within procedural code, called as a subroutine, and integrated with languages such as C, FORTRAN and Ada. CLIPS can be easily extended by a user through the use of several well-defined protocols. CLIPS provides several delivery options for programs including the ability to generate stand alone executables or to load programs from text or binary files. CLIPS 6.0 provides support for the modular development and execution of knowledge bases with the defmodule construct. CLIPS modules allow a set of constructs to be grouped together such that explicit control can be maintained over restricting the access of the constructs by other modules. This type of control is similar to global and local scoping used in languages such as C or Ada. By restricting access to deftemplate and defclass constructs, modules can function as blackboards, permitting only certain facts and instances to be seen by other modules. Modules are also used by rules to provide execution control. The CRSV (Cross-Reference, Style, and Verification) utility included with previous version of CLIPS is no longer supported. The capabilities provided by this tool are now available directly within CLIPS 6.0 to aid in the development, debugging, and verification of large rule bases. COSMIC offers four distribution versions of CLIPS 6.0: UNIX (MSC-22433), VMS (MSC-22434), MACINTOSH (MSC-22429), and IBM PC (MSC-22430). Executable files, source code, utilities, documentation, and examples are included on the program media. All distribution versions include identical source code for the command line version of CLIPS 6.0. This source code should compile on any platform with an ANSI C compiler. Each distribution version of CLIPS 6.0, except that for the Macintosh platform, includes an executable for the command line version. For the UNIX version of CLIPS 6.0, the command line interface has been successfully implemented on a Sun4 running SunOS, a DECstation running DEC RISC ULTRIX, an SGI Indigo Elan running IRIX, a DEC Alpha AXP running OSF/1, and an IBM RS/6000 running AIX. Command line interface executables are included for Sun4 computers running SunOS 4.1.1 or later and for the DEC RISC ULTRIX platform. The makefiles may have to be modified slightly to be used on other UNIX platforms. The UNIX, Macintosh, and IBM PC versions of CLIPS 6.0 each have a platform specific interface. Source code, a makefile, and an executable for the Windows 3.1 interface version of CLIPS 6.0 are provided only on the IBM PC distribution diskettes. Source code, a makefile, and an executable for the Macintosh interface version of CLIPS 6.0 are provided only on the Macintosh distribution diskettes. Likewise, for the UNIX version of CLIPS 6.0, only source code and a makefile for an X-Windows interface are provided. The X-Windows interface requires MIT's X Window System, Version 11, Release 4 (X11R4), the Athena Widget Set, and the Xmu library. The source code for the Athena Widget Set is provided on the distribution medium. The X-Windows interface has been successfully implemented on a Sun4 running SunOS 4.1.2 with the MIT distribution of X11R4 (not OpenWindows), an SGI Indigo Elan running IRIX 4.0.5, and a DEC Alpha AXP running OSF/1 1.2. The VAX version of CLIPS 6.0 comes only with the generic command line interface. ASCII makefiles for the command line version of CLIPS are provided on all the distribution media for UNIX, VMS, and DOS. Four executables are provided with the IBM PC version: a windowed interface executable for Windows 3.1 built using Borland C++ v3.1, an editor for use with the windowed interface, a command line version of CLIPS for Windows 3.1, and a 386 command line executable for DOS built using Zortech C++ v3.1. All four executables are capable of utilizing extended memory and require an 80386 CPU or better. Users needing an 8086/8088 or 80286 executable must recompile the CLIPS source code themselves. Users who wish to recompile the DOS executable using Borland C++ or MicroSoft C must use a DOS extender program to produce an executable capable of using extended memory. The version of CLIPS 6.0 for IBM PC compatibles requires DOS v3.3 or later and/or Windows 3.1 or later. It is distributed on a set of three 1.4Mb 3.5 inch diskettes. A hard disk is required. The Macintosh version is distributed in compressed form on two 3.5 inch 1.4Mb Macintosh format diskettes, and requires System 6.0.5, or higher, and 1Mb RAM. The version for DEC VAX/VMS is available in VAX BACKUP format on a 1600 BPI 9-track magnetic tape (standard distribution medium) or a TK50 tape cartridge. The UNIX version is distributed in UNIX tar format on a .25 inch streaming magnetic tape cartridge (Sun QIC-24). For the UNIX version, alternate distribution media and formats are available upon request. The CLIPS 6.0 documentation includes a User's Guide and a three volume Reference Manual consisting of Basic and Advanced Programming Guides and an Interfaces Guide. An electronic version of the documentation is provided on the distribution medium for each version: in MicroSoft Word format for the Macintosh and PC versions of CLIPS, and in both PostScript format and MicroSoft Word for Macintosh format for the UNIX and DEC VAX versions of CLIPS. CLIPS was developed in 1986 and Version 6.0 was released in 1993.
CLIPS 6.0 - C LANGUAGE INTEGRATED PRODUCTION SYSTEM, VERSION 6.0 (MACINTOSH VERSION)
NASA Technical Reports Server (NTRS)
Riley, G.
1994-01-01
CLIPS, the C Language Integrated Production System, is a complete environment for developing expert systems -- programs which are specifically intended to model human expertise or knowledge. It is designed to allow artificial intelligence research, development, and delivery on conventional computers. CLIPS 6.0 provides a cohesive tool for handling a wide variety of knowledge with support for three different programming paradigms: rule-based, object-oriented, and procedural. Rule-based programming allows knowledge to be represented as heuristics, or "rules-of-thumb" which specify a set of actions to be performed for a given situation. Object-oriented programming allows complex systems to be modeled as modular components (which can be easily reused to model other systems or create new components). The procedural programming capabilities provided by CLIPS 6.0 allow CLIPS to represent knowledge in ways similar to those allowed in languages such as C, Pascal, Ada, and LISP. Using CLIPS 6.0, one can develop expert system software using only rule-based programming, only object-oriented programming, only procedural programming, or combinations of the three. CLIPS provides extensive features to support the rule-based programming paradigm including seven conflict resolution strategies, dynamic rule priorities, and truth maintenance. CLIPS 6.0 supports more complex nesting of conditional elements in the if portion of a rule ("and", "or", and "not" conditional elements can be placed within a "not" conditional element). In addition, there is no longer a limitation on the number of multifield slots that a deftemplate can contain. The CLIPS Object-Oriented Language (COOL) provides object-oriented programming capabilities. Features supported by COOL include classes with multiple inheritance, abstraction, encapsulation, polymorphism, dynamic binding, and message passing with message-handlers. CLIPS 6.0 supports tight integration of the rule-based programming features of CLIPS with COOL (that is, a rule can pattern match on objects created using COOL). CLIPS 6.0 provides the capability to define functions, overloaded functions, and global variables interactively. In addition, CLIPS can be embedded within procedural code, called as a subroutine, and integrated with languages such as C, FORTRAN and Ada. CLIPS can be easily extended by a user through the use of several well-defined protocols. CLIPS provides several delivery options for programs including the ability to generate stand alone executables or to load programs from text or binary files. CLIPS 6.0 provides support for the modular development and execution of knowledge bases with the defmodule construct. CLIPS modules allow a set of constructs to be grouped together such that explicit control can be maintained over restricting the access of the constructs by other modules. This type of control is similar to global and local scoping used in languages such as C or Ada. By restricting access to deftemplate and defclass constructs, modules can function as blackboards, permitting only certain facts and instances to be seen by other modules. Modules are also used by rules to provide execution control. The CRSV (Cross-Reference, Style, and Verification) utility included with previous version of CLIPS is no longer supported. The capabilities provided by this tool are now available directly within CLIPS 6.0 to aid in the development, debugging, and verification of large rule bases. COSMIC offers four distribution versions of CLIPS 6.0: UNIX (MSC-22433), VMS (MSC-22434), MACINTOSH (MSC-22429), and IBM PC (MSC-22430). Executable files, source code, utilities, documentation, and examples are included on the program media. All distribution versions include identical source code for the command line version of CLIPS 6.0. This source code should compile on any platform with an ANSI C compiler. Each distribution version of CLIPS 6.0, except that for the Macintosh platform, includes an executable for the command line version. For the UNIX version of CLIPS 6.0, the command line interface has been successfully implemented on a Sun4 running SunOS, a DECstation running DEC RISC ULTRIX, an SGI Indigo Elan running IRIX, a DEC Alpha AXP running OSF/1, and an IBM RS/6000 running AIX. Command line interface executables are included for Sun4 computers running SunOS 4.1.1 or later and for the DEC RISC ULTRIX platform. The makefiles may have to be modified slightly to be used on other UNIX platforms. The UNIX, Macintosh, and IBM PC versions of CLIPS 6.0 each have a platform specific interface. Source code, a makefile, and an executable for the Windows 3.1 interface version of CLIPS 6.0 are provided only on the IBM PC distribution diskettes. Source code, a makefile, and an executable for the Macintosh interface version of CLIPS 6.0 are provided only on the Macintosh distribution diskettes. Likewise, for the UNIX version of CLIPS 6.0, only source code and a makefile for an X-Windows interface are provided. The X-Windows interface requires MIT's X Window System, Version 11, Release 4 (X11R4), the Athena Widget Set, and the Xmu library. The source code for the Athena Widget Set is provided on the distribution medium. The X-Windows interface has been successfully implemented on a Sun4 running SunOS 4.1.2 with the MIT distribution of X11R4 (not OpenWindows), an SGI Indigo Elan running IRIX 4.0.5, and a DEC Alpha AXP running OSF/1 1.2. The VAX version of CLIPS 6.0 comes only with the generic command line interface. ASCII makefiles for the command line version of CLIPS are provided on all the distribution media for UNIX, VMS, and DOS. Four executables are provided with the IBM PC version: a windowed interface executable for Windows 3.1 built using Borland C++ v3.1, an editor for use with the windowed interface, a command line version of CLIPS for Windows 3.1, and a 386 command line executable for DOS built using Zortech C++ v3.1. All four executables are capable of utilizing extended memory and require an 80386 CPU or better. Users needing an 8086/8088 or 80286 executable must recompile the CLIPS source code themselves. Users who wish to recompile the DOS executable using Borland C++ or MicroSoft C must use a DOS extender program to produce an executable capable of using extended memory. The version of CLIPS 6.0 for IBM PC compatibles requires DOS v3.3 or later and/or Windows 3.1 or later. It is distributed on a set of three 1.4Mb 3.5 inch diskettes. A hard disk is required. The Macintosh version is distributed in compressed form on two 3.5 inch 1.4Mb Macintosh format diskettes, and requires System 6.0.5, or higher, and 1Mb RAM. The version for DEC VAX/VMS is available in VAX BACKUP format on a 1600 BPI 9-track magnetic tape (standard distribution medium) or a TK50 tape cartridge. The UNIX version is distributed in UNIX tar format on a .25 inch streaming magnetic tape cartridge (Sun QIC-24). For the UNIX version, alternate distribution media and formats are available upon request. The CLIPS 6.0 documentation includes a User's Guide and a three volume Reference Manual consisting of Basic and Advanced Programming Guides and an Interfaces Guide. An electronic version of the documentation is provided on the distribution medium for each version: in MicroSoft Word format for the Macintosh and PC versions of CLIPS, and in both PostScript format and MicroSoft Word for Macintosh format for the UNIX and DEC VAX versions of CLIPS. CLIPS was developed in 1986 and Version 6.0 was released in 1993.
CLIPS 6.0 - C LANGUAGE INTEGRATED PRODUCTION SYSTEM, VERSION 6.0 (DEC VAX VMS VERSION)
NASA Technical Reports Server (NTRS)
Donnell, B.
1994-01-01
CLIPS, the C Language Integrated Production System, is a complete environment for developing expert systems -- programs which are specifically intended to model human expertise or knowledge. It is designed to allow artificial intelligence research, development, and delivery on conventional computers. CLIPS 6.0 provides a cohesive tool for handling a wide variety of knowledge with support for three different programming paradigms: rule-based, object-oriented, and procedural. Rule-based programming allows knowledge to be represented as heuristics, or "rules-of-thumb" which specify a set of actions to be performed for a given situation. Object-oriented programming allows complex systems to be modeled as modular components (which can be easily reused to model other systems or create new components). The procedural programming capabilities provided by CLIPS 6.0 allow CLIPS to represent knowledge in ways similar to those allowed in languages such as C, Pascal, Ada, and LISP. Using CLIPS 6.0, one can develop expert system software using only rule-based programming, only object-oriented programming, only procedural programming, or combinations of the three. CLIPS provides extensive features to support the rule-based programming paradigm including seven conflict resolution strategies, dynamic rule priorities, and truth maintenance. CLIPS 6.0 supports more complex nesting of conditional elements in the if portion of a rule ("and", "or", and "not" conditional elements can be placed within a "not" conditional element). In addition, there is no longer a limitation on the number of multifield slots that a deftemplate can contain. The CLIPS Object-Oriented Language (COOL) provides object-oriented programming capabilities. Features supported by COOL include classes with multiple inheritance, abstraction, encapsulation, polymorphism, dynamic binding, and message passing with message-handlers. CLIPS 6.0 supports tight integration of the rule-based programming features of CLIPS with COOL (that is, a rule can pattern match on objects created using COOL). CLIPS 6.0 provides the capability to define functions, overloaded functions, and global variables interactively. In addition, CLIPS can be embedded within procedural code, called as a subroutine, and integrated with languages such as C, FORTRAN and Ada. CLIPS can be easily extended by a user through the use of several well-defined protocols. CLIPS provides several delivery options for programs including the ability to generate stand alone executables or to load programs from text or binary files. CLIPS 6.0 provides support for the modular development and execution of knowledge bases with the defmodule construct. CLIPS modules allow a set of constructs to be grouped together such that explicit control can be maintained over restricting the access of the constructs by other modules. This type of control is similar to global and local scoping used in languages such as C or Ada. By restricting access to deftemplate and defclass constructs, modules can function as blackboards, permitting only certain facts and instances to be seen by other modules. Modules are also used by rules to provide execution control. The CRSV (Cross-Reference, Style, and Verification) utility included with previous version of CLIPS is no longer supported. The capabilities provided by this tool are now available directly within CLIPS 6.0 to aid in the development, debugging, and verification of large rule bases. COSMIC offers four distribution versions of CLIPS 6.0: UNIX (MSC-22433), VMS (MSC-22434), MACINTOSH (MSC-22429), and IBM PC (MSC-22430). Executable files, source code, utilities, documentation, and examples are included on the program media. All distribution versions include identical source code for the command line version of CLIPS 6.0. This source code should compile on any platform with an ANSI C compiler. Each distribution version of CLIPS 6.0, except that for the Macintosh platform, includes an executable for the command line version. For the UNIX version of CLIPS 6.0, the command line interface has been successfully implemented on a Sun4 running SunOS, a DECstation running DEC RISC ULTRIX, an SGI Indigo Elan running IRIX, a DEC Alpha AXP running OSF/1, and an IBM RS/6000 running AIX. Command line interface executables are included for Sun4 computers running SunOS 4.1.1 or later and for the DEC RISC ULTRIX platform. The makefiles may have to be modified slightly to be used on other UNIX platforms. The UNIX, Macintosh, and IBM PC versions of CLIPS 6.0 each have a platform specific interface. Source code, a makefile, and an executable for the Windows 3.1 interface version of CLIPS 6.0 are provided only on the IBM PC distribution diskettes. Source code, a makefile, and an executable for the Macintosh interface version of CLIPS 6.0 are provided only on the Macintosh distribution diskettes. Likewise, for the UNIX version of CLIPS 6.0, only source code and a makefile for an X-Windows interface are provided. The X-Windows interface requires MIT's X Window System, Version 11, Release 4 (X11R4), the Athena Widget Set, and the Xmu library. The source code for the Athena Widget Set is provided on the distribution medium. The X-Windows interface has been successfully implemented on a Sun4 running SunOS 4.1.2 with the MIT distribution of X11R4 (not OpenWindows), an SGI Indigo Elan running IRIX 4.0.5, and a DEC Alpha AXP running OSF/1 1.2. The VAX version of CLIPS 6.0 comes only with the generic command line interface. ASCII makefiles for the command line version of CLIPS are provided on all the distribution media for UNIX, VMS, and DOS. Four executables are provided with the IBM PC version: a windowed interface executable for Windows 3.1 built using Borland C++ v3.1, an editor for use with the windowed interface, a command line version of CLIPS for Windows 3.1, and a 386 command line executable for DOS built using Zortech C++ v3.1. All four executables are capable of utilizing extended memory and require an 80386 CPU or better. Users needing an 8086/8088 or 80286 executable must recompile the CLIPS source code themselves. Users who wish to recompile the DOS executable using Borland C++ or MicroSoft C must use a DOS extender program to produce an executable capable of using extended memory. The version of CLIPS 6.0 for IBM PC compatibles requires DOS v3.3 or later and/or Windows 3.1 or later. It is distributed on a set of three 1.4Mb 3.5 inch diskettes. A hard disk is required. The Macintosh version is distributed in compressed form on two 3.5 inch 1.4Mb Macintosh format diskettes, and requires System 6.0.5, or higher, and 1Mb RAM. The version for DEC VAX/VMS is available in VAX BACKUP format on a 1600 BPI 9-track magnetic tape (standard distribution medium) or a TK50 tape cartridge. The UNIX version is distributed in UNIX tar format on a .25 inch streaming magnetic tape cartridge (Sun QIC-24). For the UNIX version, alternate distribution media and formats are available upon request. The CLIPS 6.0 documentation includes a User's Guide and a three volume Reference Manual consisting of Basic and Advanced Programming Guides and an Interfaces Guide. An electronic version of the documentation is provided on the distribution medium for each version: in MicroSoft Word format for the Macintosh and PC versions of CLIPS, and in both PostScript format and MicroSoft Word for Macintosh format for the UNIX and DEC VAX versions of CLIPS. CLIPS was developed in 1986 and Version 6.0 was released in 1993.
PPP/nonreal-time trajectory program interface requirements and capabilities
NASA Technical Reports Server (NTRS)
Mcgavern, J. L.; Arbet, J. D.
1975-01-01
The selection process for interfacing a nonreal time trajectory program with the procedures and performance program is outlined; the interface provides summary data timelines for any desired trajectory profile. Consideration was given to two separate digital programs for satisfying capabilities. One was the CDC 6400 digital program BANDITO, and the second was the UNIVAC 1110 SVDS program.
NASA Technical Reports Server (NTRS)
Mehrbach, E.; Turkel, S. H.
1972-01-01
A summary of the findings of the data management group of the orbital operations study is presented. Element interfaces, alternate approaches, design concepts, operational procedures, functional requirements, design influences, and approach selection are described. The following interfacing activities are considered: (1) communications, (2) rendezvous, (3) stationkeeping, and (4) detached element operations.
Integrated command, control, communications and computation system functional architecture
NASA Technical Reports Server (NTRS)
Cooley, C. G.; Gilbert, L. E.
1981-01-01
The functional architecture for an integrated command, control, communications, and computation system applicable to the command and control portion of the NASA End-to-End Data. System is described including the downlink data processing and analysis functions required to support the uplink processes. The functional architecture is composed of four elements: (1) the functional hierarchy which provides the decomposition and allocation of the command and control functions to the system elements; (2) the key system features which summarize the major system capabilities; (3) the operational activity threads which illustrate the interrelationahip between the system elements; and (4) the interfaces which illustrate those elements that originate or generate data and those elements that use the data. The interfaces also provide a description of the data and the data utilization and access techniques.
Operability of Space Station Freedom's meteoroid/debris protection system
NASA Technical Reports Server (NTRS)
Kahl, Maggie S.; Stokes, Jack W.
1992-01-01
The design of Space Station Freedom's external structure must not only protect the spacecraft from the hazardous environment, but also must be compatible with the extra vehicular activity system for assembly and maintenance. The external procedures for module support are utility connections, external orbital replaceable unit changeout, and maintenance of the meteoroid/debris shields and multilayer insulation. All of these interfaces require proper man-machine engineering to be compatible with the extra vehicular activity and manipulator systems. This paper discusses design solutions, including those provided for human interface, to the Space Station Freedom meteoroid/debris protection system. The system advantages and current access capabilities are illustrated through analysis of its configuration over the Space Station Freedom resource nodes and common modules, with emphasis on the cylindrical sections and endcones.
Fresenius AS.TEC204 blood cell separator.
Sugai, Mikiya
2003-02-01
Fresenius AS.TEC204 is a third-generation blood cell separator that incorporates the continuous centrifugal separation method and automatic control of the cell separation process. Continuous centrifugation separates cell components according to their specific gravity, and different cell components are either harvested or eliminated as needed. The interface between the red blood cell and plasma is optically detected, and the Interface Control (IFC) cooperates with different pumps, monitors and detectors to harvest required components automatically. The system is composed of three major sections; the Front Panel Unit; the Pump Unit, and the Centrifuge Unit. This unit can be used for a wide variety of clinical applications including collection of platelets, peripheral blood stem cells, bone marrow stem cells, granulocytes, mononuclear cells, and exchange of plasma or red cells, and for plasma treatment.
A 0.5 cm(3) four-channel 1.1 mW wireless biosignal interface with 20 m range.
Morrison, Tim; Nagaraju, Manohar; Winslow, Brent; Bernard, Amy; Otis, Brian P
2014-02-01
This paper presents a self-contained, single-chip biosignal monitoring system with wireless programmability and telemetry interface suitable for mainstream healthcare applications. The system consists of low-noise front end amplifiers, ADC, MICS/ISM transmitter and infrared programming capability to configure the state of the chip. An on-chip packetizer ensures easy pairing with standard off-the-shelf receivers. The chip is realized in the IBM 130 nm CMOS process with an area of 2×2 mm(2). The entire system consumes 1.07 mW from a 1.2 V supply. It weighs 0.6 g including a zinc-air battery. The system has been extensively tested in in vivo biological experiments and requires minimal human interaction or calibration.
GPS system simulation methodology
NASA Technical Reports Server (NTRS)
Ewing, Thomas F.
1993-01-01
The following topics are presented: background; Global Positioning System (GPS) methodology overview; the graphical user interface (GUI); current models; application to space nuclear power/propulsion; and interfacing requirements. The discussion is presented in vugraph form.
NASA Technical Reports Server (NTRS)
Jovic, Srba
2015-01-01
This Interface Control Document (ICD) documents and tracks the necessary information required for the Live Virtual and Constructive (LVC) systems components as well as protocols for communicating with them in order to achieve all research objectives captured by the experiment requirements. The purpose of this ICD is to clearly communicate all inputs and outputs from the subsystem components.
Hands-Free, Heads-Up Control System for Unmanned Ground Vehicles
2011-08-10
interface evaluation Industry evaluated two commercial-off-the-shelf (COTS) brain computer interfaces from two companies – Neurosky and Emotiv ...useless, resulting in very low command recognition accuracy. In addition, latency issues plagued the system. Figure 6 Emotiv Headset The... Emotiv system, unlike the Neurosky, required great effort to use and calibrate. It requires 16 foam tips to be wet with saline solution and then
Microcomputer Program Design Considerations for the Novice User
1987-03-01
relatively recent, widespread proliferation of microcomputers into both the home and work place has resulted in a shifting of computer operation and...design decisions be made with respect to both the requirements specifications and interface considerations. Since a project’s requirement...expertise, may be quite meaningless or confusing to the end user. It is therefore proposed that interface design decisions should be made under the assumption