Search NASA⌕ Search

SEARCH · Search NASA

Results for “Software interfaces”

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 343 records · Page 19
All sourcesNASA NTRSDOE OSTI
NASA NTRS1996

An Overview of the NASA F-18 High Alpha Research Vehicle

This paper gives an overview of the NASA F-18 High Alpha Research Vehicle. The three flight phases of the program are introduced, along with the specific goals and data examples taken during each phase. The aircraft configuration and systems needed to perform the disciplinary and inter-disciplinary research are discussed. The specific disciplines involved with the flight research are introduced, including aerodynamics, controls, propulsion, systems, and structures. Decisions that were made early in the planning of the aircraft project and the results of those decisions are briefly discussed. Each of the three flight phases corresponds to a particular aircraft configuration, and the research dictated the configuration to be flown. The first phase gathered data with the baseline F-18 configuration. The second phase was the thrust-vectoring phase. The third phase used a modified forebody with deployable nose strakes. Aircraft systems supporting these flights included extensive instrumentation systems, integrated research flight controls using flight control hardware and corresponding software, analog interface boxes to control forebody strakes, a thrust-vectoring system using external post-exit vanes around axisymmetric nozzles, a forebody vortex control system with strakes, and backup systems using battery-powered emergency systems and a spin recovery parachute.

Bowers, Albion H.↗
NASA NTRS1999

Simulations of the Unsteady Flow through the Fastrac Supersonic Turbine

Analysis of the unsteady aerodynamic environment in the Fastrac supersonic turbine is presented. Modal analysis of the turbine blades indicated possible resonance in crucial operating ranges of the turbopump. Unsteady computational fluid dynamics (CFD) analysis was conducted to support the aerodynamic and structural dynamic assessments of the turbine. Before beginning the analysis, two major problems with current unsteady analytical capabilities had to be addressed: modeling a straight centerline nozzle with the turbine blades and exit guide vanes (EGVs), and reducing run times significantly while maintaining physical accuracy. Modifications were made to the CFD code used in this study to allow the coupled nozzle/blade/EGV analysis and to incorporate Message Passing Interface (MPI) software. Because unsteadiness is a key issue for the Fastrac turbine [and future rocket engine turbines such as for the Reusable Launch Vehicle (RI.V)], calculations were performed for two nozzle-to-blade axial gaps. Calculations were also performed for the nozzle alone, and the results were imposed as an inlet boundary condition for a blade/EGV calculation for the large gap case. These results are compared to the nozzle/blade/EGV results.

Griffin, Lisa W.↗
NASA NTRS2001

Visualization of CFD Results in Immersive Virtual Environments

An object-oriented event-driven immersive virtual environment (VE) is described for the visualization of computational fluid dynamics (CFD) results. The VE incorporates the following types of primitive software objects: interface objects, support objects, geometric entities, and finite elements. The fluid domain is discretized using either a multi-block structured grid or an unstructured finite element mesh. The VE allows natural 'fly-through' visualization of the model, the CFD grid, and the model's surroundings. In order to help visualize the flow and its effects on the model, the VE incorporates the following objects: stream objects (lines, surface-restricted lines. ribbons. and volumes); colored surfaces; elevation surfaces; surface arrows; global and local iso-surfaces; vortex cores; and separation/attachment surfaces and lines. Most of these objects can be used for dynamically probing the flow. Particles and arrow animations can be displayed on top of stream objects. Primitive response quantities as well as derived quantities can be used. A recursive tree search algorithm is used for real-time point and value search in the CFD grid.

Wasfy, Tamer M.↗
NASA NTRS2003

Development of the Next Generation Gas Trap for the Space Station Internal Thermal Control System

The current dual-membrane gas trap is designed to remove non-condensed gases (NCG) from the Internal Thermal Control System (ITCS) coolant on board the International Space Station (ISS). To date it has successfully served its purpose of preventing depriming, overspeed, and shutdown of the ITCS pump. However, contamination in the ITCS coolant has adversely affected the gas venting rate and lifetime of the gas trap, warranting a development effort for a next-generation gas trap. Design goals are to meet or exceed the current requirements to (1) include greater operating ranges and conditions, (2) eliminate reliance on the current hydrophilic tube fabrication process, and (3) increase operational life and tolerance to particulate and microbial growth fouling. In addition, the next generation gas trap will essentially be a 'dropin" design such that no modifications to the ITCS pump package assembly (PPA) will be required, and the implementation of the new design will not affect changes to the ITCS operational conditions, interfaces, or software. This paper will present the initial membrane module design and development work which has included (1) a trade study among several conceptual designs, (2) performance modeling of a hydrophobic-only design, and (3) small-scale development test data for the hydrophobic-only design. Testing has shown that the hydrophobic-only design is capable of performing even better than the current dual-membrane design for both steady-state gas removal and gas slug removal.

Leimkuehler, Thomas O.↗
NASA NTRS2002

Spacewire on Earth orbiting scatterometers

The need for a high speed, reliable and easy to implement communication link has led to the development of a space flight oriented version of IEEE 1355 called SpaceWire. SpaceWire is based on high-speed (200 Mbps) serial point-to-point links using Low Voltage Differential Signaling (LVDS). SpaceWIre has provisions for routing messages between a large network of processors, using wormhole routing for low overhead and latency. {additionally, there are available space qualified hybrids, which provide the Link layer to the user's bus}. A test bed of multiple digital signal processor breadboards, demonstrating the ability to meet signal processing requirements for an orbiting scatterometer has been implemented using three Astrium MCM-DSPs, each breadboard consists of a Multi Chip Module (MCM) that combines a space qualified Digital Signal Processor and peripherals, including IEEE-1355 links. With the addition of appropriate physical layer interfaces and software on the DSP, the SpaceWire link is used to communicate between processors on the test bed, e.g. sending timing references, commands, status, and science data among the processors. Results are presented on development issues surrounding the use of SpaceWire in this environment, from physical layer implementation (cables, connectors, LVDS drivers) to diagnostic tools, driver firmware, and development methodology. The tools, methods, and hardware, software challenges and preliminary performance are investigated and discussed.

serial↗
NASA NTRS2008

Pratt and Whitney Overview and Advanced Health Management Program

Hardware Development Activity: Design and Test Custom Multi-layer Circuit Boards for use in the Fault Emulation Unit; Logic design performed using VHDL; Layout power system for lab hardware; Work lab issues with software developers and software testers; Interface with Engine Systems personnel with performance of Engine hardware components; Perform off nominal testing with new engine hardware.

Inabinett, Calvin↗
NASA NTRS2011

Wallops Ship Surveillance System

Approved as a Wallops control center backup system, the Wallops Ship Surveillance Software is a day-of-launch risk analysis tool for spaceport activities. The system calculates impact probabilities and displays ship locations relative to boundary lines. It enables rapid analysis of possible flight paths to preclude the need to cancel launches and allow execution of launches in a timely manner. Its design is based on low-cost, large-customer- base elements including personal computers, the Windows operating system, C/C++ object-oriented software, and network interfaces. In conformance with the NASA software safety standard, the system is designed to ensure that it does not falsely report a safe-for-launch condition. To improve the current ship surveillance method, the system is designed to prevent delay of launch under a safe-for-launch condition. A single workstation is designated the controller of the official ship information and the official risk analysis. Copies of this information are shared with other networked workstations. The program design is divided into five subsystems areas: 1. Communication Link -- threads that control the networking of workstations; 2. Contact List -- a thread that controls a list of protected item (ocean vessel) information; 3. Hazard List -- threads that control a list of hazardous item (debris) information and associated risk calculation information; 4. Display -- threads that control operator inputs and screen display outputs; and 5. Archive -- a thread that controls archive file read and write access. Currently, most of the hazard list thread and parts of other threads are being reused as part of a new ship surveillance system, under the SureTrak project.

Smith, Donna C.↗
NASA NTRS2011

Improving Data Collection and Analysis Interface for the Data Acquisition Software of the Spin Laboratory at NASA Glenn Research Center

In jet engines, turbines spin at high rotational speeds. The forces generated from these high speeds make the rotating components of the turbines susceptible to developing cracks that can lead to major engine failures. The current inspection technologies only allow periodic examinations to check for cracks and other anomalies due to the requirements involved, which often necessitate entire engine disassembly. Also, many of these technologies cannot detect cracks that are below the surface or closed when the crack is at rest. Therefore, to overcome these limitations, efforts at NASA Glenn Research Center are underway to develop techniques and algorithms to detect cracks in rotating engine components. As a part of these activities, a high-precision spin laboratory is being utilized to expand and conduct highly specialized tests to develop methodologies that can assist in detecting predetermined cracks in a rotating turbine engine rotor. This paper discusses the various features involved in the ongoing testing at the spin laboratory and elaborates on its functionality and on the supporting data system tools needed to enable successfully running optimal tests and collecting accurate results. The data acquisition system and the associated software were updated and customized to adapt to the changes implemented on the test rig system and to accommodate the data produced by various sensor technologies. Discussion and presentation of these updates and the new attributes implemented are herein reported

Abdul-Aziz, Ali↗
NASA NTRS2017

Battery Data MI Importer Template Quick Start Guide

In order to ensure the persistent availability and reliability of test data generated over the course of the project, the M-SHELLS Project has decided to store acquired test data, as well as associated pedigree information, in the Granta Materials Intelligence (MI) database. To facilitate that effort, an importer template and associated graphical user interface (GUI) software have been developed, with this guide providing the operating instructions for their use. The template and automation software GUI are contained in the BatteryDataImporter.xlsm Excel workbook, and are to be used to import M-SHELLS summary, or pedigree, data and the associated raw test data results into an importer template-based file, formatted in such a way as to be ready for immediate upload to the Test Data: Battery Performance table of the Granta MI database. The provided GUI enables the user to select the appropriate summary data file(s), with each file containing the required information to identify any associated raw test data file(s) to be processed. In addition to describing the setup and operation of the importer template and GUI software, this guide also provides instructions for uploading processed data to the database and for viewing the data following upload.

Levinson, Laurie H.↗
NASA NTRSDate not supplied

End-to-End Trajectory Optimization Using Copernicus and Program to Optimize Simulated Trajectories II

As current and future NASA missions become increasingly more complex, the need to ensure requirements are met across the many phases of flight is more pertinent. Accurately modeling the individual phases of flight is difficult alone, but verifying that the overall mission is characterized properly presents additional challenges. In previous works, there have been successful demonstrations of interfacing multiple software applications to provide a more detailed end-to-end optimized simulation. The work herein will focus on leveraging two NASA built tools that have been successfully utilized on NASA missions: Copernicus and the Program to Optimize Simulated Trajectories II (POST2).

Anthony Williams↗
NASA NTRSDate not supplied

An Automated Medical Inventory System (AMIS) to Enable Earth-Independent Medical Operations

BACKGROUND: Inventory of medical consumables and durables (medications, treatment aids, diagnostic equipment, etc.) aboard the International Space Station is a manual process whereby crewmembers reach out to their flight surgeon to relay when items are used. Performing a full medical system inventory is time intensive. However, as exploration progresses to long duration missions with little to no resupply or evacuation capabilities, maintaining an accurate account of inventory and location for medical systems across the mission will become increasingly critical. A new system must be developed for future exploration missions to meet the need for a crew-facing, real time method of managing medical inventory. OVERVIEW: NASA’s Exploration Medical Integrated Product Team (XMIPT) is funding the AMIS project to mature the technology readiness level and to conduct a flight demonstration of a medical inventory capability. AMIS will leverage lessons learned from a Medical Consumables Tracking project previously demonstrated aboard the ISS in 2016 and 2017. Key components of AMIS include a database, supporting hardware and software, and interfaces to power, communications, or other vehicle or medical systems. Some medical inventory capability may be provided by the vehicle inventory management system which relies upon RFID-based technology and can track larger items such as medical kits or medical hardware. AMIS will augment these capabilities to enable tracking of individual medical kit contents. Efforts are underway to characterize the optimal solution trade space by comparing system specifications (e.g. mass and volume, etc.) across maintenance and operational use cases (e.g. crew time saved, total inventory automated, etc). DISCUSSION: The contents of a Mars Medical System have not been fully defined which poses challenges to defining an inventory system and requires assumptions regarding medical kit contents and medical system design. Other important considerations include minimizing crew time required, avoiding access restrictions to medical inventory in the event of an emergency, and ensuring that data is accessible to other medical system elements to enable crew autonomy in provision of medical care.

Automated Medical Inventory System↗
NASA NTRSDate not supplied

Transformation of the NASA Life Sciences Portal to a FAIR Data Point

The FAIR principles emphasize optimizing metadata, the vast majority of which are textual in nature, and often organized into attribute name-value pairs. This uniformity has led to the development of guidelines and best practices for providing programmatic access to scientific data through their metadata, yielding the first iteration of the FAIR Data Point Specifications (FDPS). A key feature of the FDPS is its support for automated agents seeking and fetching data without first needing to learn a plethora of different application programming interfaces. These software agents can interrogate metadata catalogs that adhere to FDPS in a uniform manner because each catalog describes itself and its metadata schema consistently. This approach enhances the sustainability of data retrieval support, allowing systems to refine and update their metadata schemas as needed and without requiring data-seeking software agents to change how they interrogate FDPS catalogs. An essential aspect of the FDPS is the standardization of data catalog semantics, which formalizes concepts such as “metadata” and “metadata service” and links them to other concepts specifications including the Data Catalog Vocabulary (DCAT), a W3C standard that is also the basis of NASA-STD-2831 “Metadata Standard for Data Discoverability,” authored by NASA’s Office of the Chief Information Officer. The FDPS references DCAT (version 2) elements which focus on the distribution of datasets and support the goal of stream-lined catalog integration across repositories for improved data discovery. Additionally, the FDPS also prescribe the use of Linked Data Platform elements for data catalog-metadata record containment descriptions, allowing users to ascertain which data and metadata belong to which catalogs. NASA’s Life Sciences Portal is implementing the FDPS while formalizing its metadata schema to support the accelerated synthesis of knowledge from space life sciences investigations.

platform↗
DOE OSTI2025

Enhancing ICARUS and REDTOP Software and Hardware: Event Generator Interface Development and Calorimeter Tile Prototype

ICARUS (Imaging Cosmic And Rare Underground Signals) is a liquid argon time projection chamber (LArTPC) detector that pursues the sterile neutrino, which relies on accurate simulations of neutrino-argon interactions. REDTOP (Rare Eta Decays To Observe new Physics) is a proposed low-energy, high-intensity meson factory designed to explore rare $\eta$/$\eta'$ meson decays and probe physics beyond the Standard Model. As a next-generation experiment, this requires both accurate simulations and innovative detector technologies. This project contributes to both ICARUS, from a simulation perspective, and REDTOP, from both a simulation and detection perspective, through the event generation of lepton-nucleon interactions and the physical enhancement of the calorimeter technology within the REDTOP detector. We developed an interface between ACHILLES (A CHIcago Land Lepton Event Simulator), a theory-driven lepton-level event generator, and GENIE, a robust event generator framework used for neutrino physics. By incorporating the precise theoretical cross-section calculations of ACHILLES into the experimental realism of GENIE, the interface allows for improved accuracy of neutrino-nucleon simulations, which can be adapted for the proton beam specifications of the REDTOP meson factory as well as for the ICARUS experiment. In parallel, we developed an improved prototype for the ADRIANO2 (A Dual Readout Integrally Active Non-segmented Option) dual-readout calorimeter tiles for the REDTOP detector. To improve the efficiency of the lead-glass tiles trapping Cherenkov light for energy reconstruction and particle identification, we optimized the application of a highly reflective coating. Through viscosity and thickness control, masking, and a custom spray technique, we refined the coating process to reduce surface defects and improve light yield. Together, these efforts strengthen the ICARUS neutrino program and REDTOP's capability of detecting rare decay events.

Visser, Erin [Michigan State U.] (ORCID:0009000184↗
NASA NTRS2009

Interface Generation and Compositional Verification in JavaPathfinder

We present a novel algorithm for interface generation of software components. Given a component, our algorithm uses learning techniques to compute a permissive interface representing legal usage of the component. Unlike our previous work, this algorithm does not require knowledge about the component s environment. Furthermore, in contrast to other related approaches, our algorithm computes permissive interfaces even in the presence of non-determinism in the component. Our algorithm is implemented in the JavaPathfinder model checking framework for UML statechart components. We have also added support for automated assume-guarantee style compositional verification in JavaPathfinder, using component interfaces. We report on the application of the presented approach to the generation of interfaces for flight software components.

Giannakopoulou, Dimitra↗
NASA NTRS2003

Increasing software testability with standard access and control interfaces

Testing is the most common method of determining whether a software system satisfies its requirements. Traditionally, testing starts with the detailed examination of individual functions or methods, progresses through the integration of functions or methods into subsystems, and ends with testing the functionality and behavior of the completely integrated system. At each stage of testing, the amount of functionality and behavior of the artifact being tested is increasingly limited. One reason for this is that it becomes impossible to test all paths through the system within a reasonable amount of time. However, another reason for this progressive decrease of test coverage has to do with increasingly limited control of and visibility into the state of the artifact being tested. During unit test, it is rather simple to control the inputs of individual functions or methods or view their internal state - modem development environments provide adequate facilities for doing so. However, these facilities do not scale up to the testing of partially or completely integrated systems. Control of and visibility into the system's state is then limited to the input and output facilities provided by the software itself as well as the hardware on which the software is hosted during the test. These facilities are usually insufficient to precisely control the state of individual components or sets of components of the system; they are also inadequate to the task of displaying on demand the state of specific components. We describe an approach to improving the testability of complex software systems with software constructs modeled after the hardware JTAG bus, used to provide visibility and controllability in testing digital circuits.

Tamir, Yuval↗
NASA NTRS1992

ASV3 dial-in interface recommendation for the Repository Based Software Engineering (RBSE) program

The purpose of this report is to provide insight into the approach and design of the Cooperative User Interface (CUI). The CUI is being developed based on Hypercard technology and will provide the same look and feel as is provided by the NASA Electronic Library System (NELS) X-Window interface. The interaction between the user and ASCII-LIB is presented as well as the set of Hypercard Cards with which the user will work.

Source record↗