Search NASA⌕ Search

SEARCH · Search NASA

Results for “User Interface”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 613 records · Page 34

IRAF in the nineties

The Interactive Data Reduction and Analysis Facility (IRAF) data reduction and analysis system has been around since 1981. Today it is a mature system with hundreds of applications, and is supported on all the major platforms. Many institutions, projects, and individuals around the US and around the world have developed software for IRAF. Some of these packages are comparable in size to the IRAF core system itself. IRAF is both a data analysis system, and a programming environment. As a data analysis system it can be easily installed by a user at a remote site and immediately used to view and process data. As a programming environment IRAF contains a wealth of high and low level facilities for developing new applications for interactive and automated processing of astronomical or other data. As important as the applications programs and user interfaces are to the scientist using IRAF, the heart of the IRAF system is the programming environment. The programming environment determines to a large extent the types of applications which can be built within IRAF, what they will look like, and how they will interact with one another and with the user. While applications can be easily added to or removed from a software system, the programming environment must remain fairly stable, with carefully planned evolution and growth, over the lifetime of a system. The IRAF programming environment is the framework on which the rest of the IRAF system is built. The IRAF programming environment as it exists in 1992, and the work currently underway to enhance the environment are discussed. The structure of the programming environment as a class hierarchy is discussed, with emphasis on the work being done on the image data structures, graphics and image display interfaces, and user interfaces. The new technologies which we feel IRAF must deal with successfully over the coming years are discussed. Finally, a preview of what IRAF might look like to the user by the end of the decade is presented.

Tody, D.↗

Bioinformatic teaching resources - for educators, by educators - using KBase, a free, user-friendly, open source platform

Over the past year, biology educators and staff at the Department of Energy Systems Biology Knowledgebase (KBase) initiated a collaborative effort to develop a curriculum for bioinformatics education. KBase is a free and easily accessible data science platform that integrates many bioinformatics resources into a graphical user interface built upon reproducible analysis notebooks. KBase held conversations with college and high school instructors to understand how KBase could potentially support their educational goals. These conversations morphed into a working group of biological and data science instructors that adapted the KBase platform to their curriculum needs, specifically around concepts in Genomics, Metagenomics, Pangenomics, and Phylogenetics. The KBase Educators Working Group developed modular, adaptable, and customizable instructional units. Each instructional module contains teaching resources, publicly available data, analysis tools, and markdown capability to tailor instructions and learning goals for each class. The online user interface enables students to conduct hands-on data science research and analyses without requiring programming skills or their own computational resources (these are provided by KBase). Alongside these resources, KBase continues to work with instructors, supporting the development of additional curriculum modules. For anyone new to the platform, KBase, and the growing KBase Educators Organization, provides a community network, accompanied by community-sourced guidelines, instructional templates, and peer support to use KBase within a classroom whether virtual or in-person.

59 BASIC BIOLOGICAL SCIENCES↗

PROVIDING PLANT DATA ANALYTICS THROUGH A SEAMLESS DIGITAL ENVIRONMENT

As technology continues to evolve and become more integrated into a worker’s daily routine in the Nuclear Power industry the need for easy access to data becomes a priority. Not only does the need for data increase but the amount of data collected increases. In most cases the data is collected and stored in various software applications, many of which are legacy systems, which do not offer any other option to access the data except through the application’s user interface. Furthermore the data gets grouped in “silos” according to work function and not necessarily by subject. Hence, in order to access all the information needed for a particular task or analysis one may have to access multiple applications to gather all the data needed. The industry and the research community have identified the need for a digital architecture and more importantly the need for a Seamless Digital Environment. An SDE provides a means to access multiple applications, gather the data points needed, conduct the analysis requested, and present the result to the user with minimal or no effort by the user. In addition, the nuclear utilities have identified the need for research focused on data analytics. The effort should develop and evaluate use cases for data mining and analytics for employing information from plant sensors and database for use in developing improved business analytics. Idaho National Laboratory is leading such effort, which is conducted in close collaboration with vendors, nuclear utilities, Institute of Nuclear Power Operations, and Electric Power Research Institute. The goal of the study is to research potential approaches to building an analytics solution for equipment reliability, on a small scale, focusing on either a single piece of equipment or a single system. The analytics solution will likely consist of a data integration layer, predictive and machine learning layer and the user interface layer that will display the output of the analysis in a straight forward, easy to consume manner. This paper will describe the study and the initial results.

47 OTHER INSTRUMENTATION↗

Providing plant data analytics through a seamless digital environment - 211

As technology continues to evolve and become more integrated into a worker's daily routine in the commercial nuclear power industry the need for easy access to data becomes a priority. Not only does the need for data increase but the amount of data collected increases. In most cases the data is collected and stored in various software applications, many of which are legacy systems, which do not offer any other option to access the data except through the application's user interface. Furthermore the data get grouped in 'silos' according to work function and not necessarily by subject. Hence, in order to access all the information needed for a particular task or analysis one may have to access multiple applications to gather all the data needed. The industry and the research community have identified the need for a digital architecture and more importantly the need for a Seamless Digital Environment (SDE). An SDE provides a means to access multiple applications, gather the data points needed, conduct the analysis requested, and present the result to the user with minimal or no effort by the user. The study researches the potential approaches to building an analytics solution for equipment reliability, on a small scale, focusing on either a single piece of equipment or a single system. The analytics solution will consist of a data integration layer, predictive and machine learning layer and the user interface layer that will display the output of the analysis in a straight forward, easy to consume manner. (authors)

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Development and Demonstration of a Security Core Component

In recent years, the convergence of a number of trends has resulted in Cyber Security becoming a much greater concern for electric utilities. A short list of these trends includes: · Industrial Control Systems (ICSs) have evolved from depending on proprietary hardware and operating software toward using standard off-the-shelf hardware and operating software. This has meant that these ICSs can no longer depend on “security through obscurity. · Similarly, these same systems have evolved toward using standard communications protocols, further reducing their ability to rely upon obscurity. · The rise of the Internet and the accompanying demand for more data about virtually everything has resulted in formerly isolated ICSs becoming at least partially accessible via Internet-connected networks. · “Cyber crime” has become commonplace, whether it be for industrial espionage, reconnaissance for a possible cyber attack, theft, or because some individual or group “has something to prove.” Electric utility system operators are experts at running the power grid. The reality is, especially at small and mid-sized utilities, these SCADA operators will by default be “on the front line” if and when a cyber attack occurs against their systems. These people are not computer software, networking, or cyber security experts, so they are ill-equipped to deal with a cyber security incident. Cyber Security Manager (CSM) was conceived, designed, and built so that it can be configured to know what a utility’s SCADA/EMS/DMS system looks like under normal conditions. To do this, CSM monitors log messages from any device that uses the syslog standard. It can also monitor a variety of statistics from the computers that make up the SCADA/EMS/DMS: outputs from host-based security tools, intrusion detection systems, SCADA alarms, and real-time SCADA values – even results from a SIEM (Security Information and Event Management) system. When the system deviates from “normal,” CSM can alert the operator in language that they understand that an incident may be occurring, provide actionable intelligence, and informing them what actions to take. These alarms may be viewed on CSM’s built-in user interface, sent to a SCADA alarm list, or communicated via email, phone, pager, or SMS message. In recognition of the fact that “real world” training for cyber security events is impractical, CSM has a built-in Operator Training Simulator capability. This can be used stand alone to create simulated event scenarios for training purposes. It may also be used in conjunction with the recipient’s SCADA/EMS/DMS Operator Training Simulator. In addition to providing cyber security situational awareness for electric utility operators, CSM also provides tools for analysts and support personnel; in fact, the majority of user interface displays are designed for use in analyzing current and past security events. CSM keeps security-related information in long-term storage, as well as writing any decisions it makes to a (syslog) log for use forensic or other post-event analysis.

Turke, Andy↗

Concept Mapping as a Support for Mars Landing-Site Selection

The NASA Ames' Center for Mars Exploration (CMEX) serves to coordinate Mars programmatic research at ARC in the sciences, in information technology and in aero-assist and other technologies. Most recently, CMEX has been working with the Institute for Human and Machine Cognition at the University of West Florida to develop a new kind of web browser based on the application of concept maps. These Cmaps, which are demonstrably effective in science teaching, can be used to provide a new kind of information navigation tool that can make web or CD based information more meaningful and more easily navigable. CMEX expects that its 1999 CD-ROM will have this new user interface. CMEX is also engaged with the Mars Surveyor Project Office at JPL in developing an Internet-based source of materials to support the process of selecting landing sites for the next series of Mars landers. This activity -- identifying the most promising sites from which to return samples relevant to the search for evidence of life -- is one that is expected to engage the general public as well as the science community. To make the landing site data easily accessible and meaningful to the public, CMEX is planning to use the IHMC Cmap browser as its user interface.

Cabrol, Nathalie A.↗

Automated qualification data tool for high temperature metallic materials

This report describes a framework for storing, processing, and displaying qualification data for high temperature mechanical properties. The framework automates the process of generating design data from mechanical test results, for example for a data qualification report for the ASME Boiler \& Pressure Vessel Code. The framework has three parts: a data storage model with common formats for several types of typical mechanical property tests, a backend based on the \pycreep Python library for correlating and extrapolating the data to generate design material properties and allowable stresses, and a demonstration user interface for displaying, sorting, and filtering the data and exploring different options for modeling the design mechanical properties. The report discusses the options available for data processing, with illustrations from real test data on Alloy 617, Alloy 709, Alloy 740H, and Laser-Powder Bed Fusion 316H. The framework is complete for ASME type data analysis and will be used to store test data generated by the Department of Energy, Office of Nuclear Energy, Advanced Materials and Manufacturing Technologies sponsored qualification programs. Future work could extend the tool to other types of material properties and/or expand the demo user interface to make it accessible across the AMMT program.

36 MATERIALS SCIENCE↗

Integration of design information

The overall concepts of the integrated programs for aerospace-vehicle design (IPAD) from the user's viewpoint are discussed. Also a top-level view of what the user requires from such a system is provided, and the interactions between the system and user are described. The four major components discussed are design process; data storage, management and manipulation; user interface; and project management. Although an outgrowth of aerospace production experience, the basic concepts discussed, and especially their emphasis on integration, are considered applicable to all problem solving. Thus, these concepts may offer a broad base for exploitation by industry in general. This is the first in a set of three papers, the other two being Future Integrated Design Process, by D. D. Mayer, and Requirements for Company-Wide Management of Engineering Information, by J. W. Southall. In addition to tying the three together, how project management can be handled in a computing environment and also the user interface needs are discussed in detail.

Anderton, G. L.↗

The waterSHED Model: User Guide

The ideal design and operation of small hydropower plants is a complex optimization problem with economic, social, and environmental objectives. The waterSHED (Water Allocation Tool Enabling Rapid Small Hydropower Environmental Design) model is a user-friendly tool that allows hydropower stakeholders to model the trade-offs among these objectives using the Standard Modular Hydropower (SMH) framework. The SMH framework employs modular technologies that can be represented as blackbox objects and combined within a river to create a hydropower facility. For a given site, the waterSHED model aims to determine which modules should be placed in a facility and how those modules should be operated. This user guide describes how to use the graphical user interface and related functionalities. This document also summarizes the background research and mathematical formulations that are explained indepth in the accompanying doctoral dissertation. This model is an early step toward a new hydropower design process that employs standardization and modularity to reduce costs, development timelines, and challenges regarding social and environmental mitigation measures for low-head, small hydropower development. The waterSHED model is a Python application that will require the ability to download a GitHub repository, import the necessary packages, and run a set of Python script files using an integrated development environment. The script produces a graphical user interface to coordinate inputs, simulate operation, and visualize results, so no coding experience is needed once the script is running. Additionally, the waterSHED Workbook is a Microsoft Excel file that works with the Python script to facilitate data entry

13 HYDRO ENERGY↗

FPGA Trigger System to Run Klystrons

The Klystron Department is in need of a new trigger system to update the laboratory capabilities. The objective of the research is to develop the trigger system using Field Programmable Gate Array (FPGA) technology with a user interface that will allow one to communicate with the FPGA via a Universal Serial Bus (USB). This trigger system will be used for the testing of klystrons. The key materials used consists of the Xilinx Integrated Software Environment (ISE) Foundation, a Programmable Read Only Memory (Prom) XCF04S, a Xilinx Spartan 3E 35S500E FPGA, Xilinx Platform Cable USB II, a Printed Circuit Board (PCB), a 100 MHz oscillator, and an oscilloscope. Key considerations include eight triggers, two of which have variable phase shifting capabilities. Once the project was completed the output signals were able to be manipulated via a Graphical User Interface by varying the delay and width of the signal. This was as planned; however, the ability to vary the phase was not completed. Future work could consist of being able to vary the phase. This project will give the operators in the Klystron Department more flexibility to run various tests.

43 PARTICLE ACCELERATORS↗

Modern control system applications at Fermilab with Dart and Flutter

The control system at Fermilab is undergoing an unprecedented modernization effort. Hundreds of legacy applications originally developed with technology from the early nineties will be replaced with a suite of modern web applications. The selection of an user interface framework is a key technology decision that will impact on all the applications developed over the next decade. The Controls department at Fermilab has decided to use Google’s Dart language and Flutter framework for future application development. In this paper we will discuss the decision process that selected Dart/Flutter and the development of early general purpose control system applications with the framework.

Diamond, John [Fermilab]↗

RApid Blade and Blade-Vortex InTeraction (RABBIT) Reimagined: Algorithm Improvement and User-Friendly Interface Implementation

Rotorcraft noise source identification and reduction is crucial to the emergence of the Urban Air Mobility (UAM) market. One key rotor noise source is Blade Vortex Interaction (BVI), caused by the rotor blades interacting with the rotor wake. The low-fidelity RApid Blade and Blade-Vortex InTeraction (RABBIT) tool was created to predict the location and characteristics of BVI noise. RABBIT enables engineers to quickly design and simulate UAM configurations and understand BVI occurrences for a desired flight condition. Furthermore, RABBIT can also identify the time and location of blade overlap for coaxial rotors. RABBIT is not a general acoustic prediction tool, but instead utilizes vortex and wake parameters to visualize and predict BVI aerodynamics. RABBIT algorithm has been further developed including reduction of computational time, accounting for BVI source time arrival, improved vortex strength modeling, and BVI impulse factor. A user-friendly app is presented with the intent of bringing RABBIT to the masses to allow engineers from various educational backgrounds to design and begin to understand BVI. Furthermore, RABBIT capabilities are highlighted by a parameter study highlighting key parameters that impact BVIalong with highlighting RABBIT’s ability to identify BVI occurrences from other rotors.

RApid↗

Geometric modeling for computer aided design

The primary goal of this grant has been the design and implementation of software to be used in the conceptual design of aerospace vehicles particularly focused on the elements of geometric design, graphical user interfaces, and the interaction of the multitude of software typically used in this engineering environment. This has resulted in the development of several analysis packages and design studies. These include two major software systems currently used in the conceptual level design of aerospace vehicles. These tools are SMART, the Solid Modeling Aerospace Research Tool, and EASIE, the Environment for Software Integration and Execution. Additional software tools were designed and implemented to address the needs of the engineer working in the conceptual design environment. SMART provides conceptual designers with a rapid prototyping capability and several engineering analysis capabilities. In addition, SMART has a carefully engineered user interface that makes it easy to learn and use. Finally, a number of specialty characteristics have been built into SMART which allow it to be used efficiently as a front end geometry processor for other analysis packages. EASIE provides a set of interactive utilities that simplify the task of building and executing computer aided design systems consisting of diverse, stand-alone, analysis codes. Resulting in a streamlining of the exchange of data between programs reducing errors and improving the efficiency. EASIE provides both a methodology and a collection of software tools to ease the task of coordinating engineering design and analysis codes.

Schwing, James L.↗

Design of Autonomous Medical Response Agent (AMRA) Aggregate Information Dashboard (AID)

Future astronauts in deep space missions will rely on tools and technologies empowering them to self-diagnose and self-treat medical conditions. Given communications delays and limited bandwidth in future long-duration exploration missions (LDEMs), medical decision support technologies must empower the crew to manage routine medical activities, acute medical incidents, as well as emergency medical scenarios independently from ground support.The Autonomous Medical Response Agent (AMRA) is envisioned as a digital tool enabling crew to issue medical complaints and interact with a medical decision support algorithm which develops a differential diagnosis and recommends a treatment protocol for the condition. AMRA will draw from individual crew medical history in addition to crew symptoms to more efficiently identify high-risk medical conditions. A new symptom could be indicative of a chronic condition or a normal adaptation to long-duration spaceflight, but could just as easily be indicative of an adverse vehicle condition affecting the entire crew.While real-time communication with a flight surgeon may not possible, the crew will nonetheless require a means to communicate and document both routine and emergency medical incidents to ground support. Conversely, flight surgeons and medical specialists on the ground will need to understand information such as crew vitals or responses to medical check-ups and examinations within the larger context of crew schedule, mission activities, and vehicle performance. A user interface which establishes communication protocols between an individual crew member and AMRA, as well as ground support to the crew is a significant area of research demanding input and consideration.The design of AMRA AID is intended to: a) represent routine medical activities as well as new (unplanned) medical incidents within the larger context of crew schedule and mission activities, and b) increase confidence between ground support and crew members over the course of LDEMs. Maintaining situation awareness of unplanned medical incidents between ground and crew will be a critical element within LDEMs. Two medical incidents headache and difficulty breathing are being explored within a user interface prototype which captures communications protocols between crew members and mission control, human health monitoring, vehicle or environmental monitoring, as well as crew schedule and mission activities holistically.

Yashar, M.↗

Collection And Analysis Of Telemetry For The Cyote Heuristic

CATCH CLI focuses on gathering telemetry data, storing it in the Neo4j database, querying for Mitre ATT&CK patterns, and creating STIX 2.1 reports. Key Components: Analysis Modules: Analyze data to detect attack patterns. GoSTOTS Collection Engines: Collect telemetry data. These tools can be used together or individually. Analysis modules rely on data from specific engines to identify attack patterns. Source Code Organization: Engines: CATCH/catch/cmd/collection Modules: CATCH/catch/cmd/analysis CGUI Overview CATCH Graphical User Interface (CGUI) offers a graphical shell to execute CATCH CLI, allowing easy editing of: Analysis Modules Database configurations Profiles (collection and device settings) Neo4j Overview Neo4j is a graph database using the Cypher query language, storing data in JSON. It seamlessly integrates with STIX 2.1 data for: Data Submission: CATCH Collection Engines Data Querying: Analysis Modules CATCH modifies STIX 2.1 data for Neo4j submission and reverts it back during querying. STIG Overview Structured Threat Intelligence Graph (STIG) is a tool for creating, editing, querying, analyzing, and visualizing threat intelligence using STIX 2.1 and storing data in Neo4j. Usage Tools can be run: Manually (CLI): Refer to CATCH documentation User Interface: Run ./cgui/CGUI or go run ./cgui/ Additional Information Logging System: Detailed in the config documentation Further Documentation: Available for CATCH and CGUI

Madsen, MichaelJ. [Idaho National Laboratory (INL)↗

Astrobee Operations on the Iss: Gui’S Impact on the Operators’ Cognitive Load

The Astrobee free-flying robots have completed their fifth successful year of operations housed in the Japanese Experimental Module (JEM) on the International Space Station (ISS). In this paper, we introduce two Graphical User Interfaces (GUI) used to operate and monitor in real-time the Astrobee free-flying robots onboard the ISS and report on the impact these GUIs have in the operator’s cognitive load. A review of the state-of-the-art GUI design for remotely teleoperated scenarios with minimal time delay is presented and the study’s conclusion used to determine the elements and recommendations to create an interface that minimizes its impact on the overall performance of an operator during an activity at the ISS. The Ground Data System (GDS) is one of the two GUIs in the study: it contains several tabs, each of which displays a different set of controls for specific tasks e.g. Overview, Run Plan, Teleoperate, Guest Science; some also display video and a three-dimensional (3D) representation of the ISS and robot based on the Astrobee’s telemetry. Most tabs enable a single operator-robot connection, however some of its tabs are capable to monitor and control up to three Astrobees simultaneously. The GDS Helper is a text-based user interface created to facilitate commanding and monitoring of an Astrobee robot directly from an SSH session. In full interactive mode it displays a maximum of 5 sections: general commanding, feedback/ack, telemetry, guest science commanding, and data, all in one view. In batch mode, it enables complex command scripting while retaining some interactive capabilities. A comparative analysis between these GUIs is carried out at an analogous ISS environment at the NASA Ames Research Center’s Granite Lab and its results presented. While GDS is able to provide an operator with control and situational awareness via its video and 3D displays, its several tabs may introduce an overwhelming amount of information confusing and delaying the operator especially during time-sensitive maneuvers where the operator may need to switch back and forth between them. GDS helper in the other hand does not provide video or 3D displays thus not allowing an operator to attain situational awareness, however it provides the operator with a design displaying commonly used data in a single window, enabling the operator to understand the state of the robot at a glance and control it through a commands entered via keyboard instead of a combination of mouse clicks and keyboard input. The results of the experiments measure the cognitive load across several operators maneuvering Astrobee to accomplish tasks ranging from fully manual to supervised activities. A GUI combining a single window displaying data along video and a 3D display is expected to reduce the operator’s cognitive load.

Astrobee↗

FASTSim™ (Future Automotive Systems Technology Simulator) [SWR-20-101 and SWR-12-07]

The Future Automotive Systems Technology Simulator (FASTSim™) provides a simple way to compare powertrains and estimate the impact of technology improvements on light-, medium-, and heavy-duty vehicle efficiency, performance, cost, and battery life. This extremely fast simulation tool features a streamlined user interface and can rapidly perform a variety of tasks using basic computing resources: • less than 0.1 second to simulate second-by-second standard duty cycles • less than 10 seconds to estimate vehicle efficiency, fuel economy, acceleration, battery life, and cost • less than 5 minutes to perform powertrain comparisons of efficiency and cost. FASTSim models a variety of vehicle powertrains and fuel converter types: • Conventional vehicles - spark ignition, Atkinson, diesel, and hybrid diesel • Electric-drive vehicles - hybrid, plug-in hybrid, and all-electric • Hydrogen fuel cell vehicles. The default model includes a variety of vehicles and duty cycles and an option for adding additional vehicles and custom cycles: • Packaged with more than 20 vehicles • User interface enables addition of more vehicles • Includes standard U.S. drive cycles as well as European and Japanese cycles. FASTSim is available for download in Microsoft Excel and Python formats here: https://www.nrel.gov/transportation/fastsim.html

Baker, Chad↗

Software Design Document for the AMP Nuclear Fuel Performance Code

The purpose of this document is to describe the design of the AMP nuclear fuel performance code. It provides an overview of the decomposition into separable components, an overview of what those components will do, and the strategic basis for the design. The primary components of a computational physics code include a user interface, physics packages, material properties, mathematics solvers, and computational infrastructure. Some capability from established off-the-shelf (OTS) packages will be leveraged in the development of AMP, but the primary physics components will be entirely new. The material properties required by these physics operators include many highly non-linear properties, which will be replicated from FRAPCON and LIFE where applicable, as well as some computationally-intensive operations, such as gap conductance, which depends upon the plenum pressure. Because there is extensive capability in off-the-shelf leadership class computational solvers, AMP will leverage the Trilinos, PETSc, and SUNDIALS packages. The computational infrastructure includes a build system, mesh database, and other building blocks of a computational physics package. The user interface will be developed through a collaborative effort with the Nuclear Energy Advanced Modeling and Simulation (NEAMS) Capability Transfer program element as much as possible and will be discussed in detail in a future document.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗