Search NASA⌕ Search

SEARCH · Search NASA

Results for “plug-in”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS2009

Lunar Module Wiring Design Considerations and Failure Modes

This slide presentation reviews the considerations for the design of wiring for the Lunar Module. Included are a review of the choice of conductors and insulations, the wire splicing (i.e., crimping, and soldering), the wire connectors, and the fabrication of the wire harnesses. The problems in fabrication include the wires being the wrong length, the damage due to the sharp edges, the requried use of temproary protective covers and inadequate training. The problems in the wire harness installation include damge from sharp eges, work on adjacent harnesses, connector damage, and breaking wires. Engineering suggestions from the Apollo-era in reference to the conductors that are reviewed include: the use of plated conductors, and the use of alloys for stronger wiring. In refernce to insulation, the suggestions from Apollo era include the use of polymer tape-wrap wire insulation due to the light weight, however, other types of modern insulation might be more cost-effective. In reference to wire splices and terminal boards the suggestions from the Apollo Era include the use of crimp splices as superior to solder splices, joining multiple wire to a common point using modular plug-ins might be more reliable, but are heavier than crimp splicing. For connectors, the lessons from the Apollo era indicate that a rear environmental seal that does not require additional potting is preferred, and pins should be crimped or welded to the incoming wires and be removable from the rear of the connector.

Interbartolo, Michael↗
NASA NTRS2009

MSLICE Science Activity Planner for the Mars Science Laboratory Mission

MSLICE (Mars Science Laboratory InterfaCE) is the tool used by scientists and engineers on the Mars Science Laboratory rover mission to visualize the data returned by the rover and collaboratively plan its activities. It enables users to efficiently and effectively search all mission data to find applicable products (e.g., images, targets, activity plans, sequences, etc.), view and plan the traverse of the rover in HiRISE (High Resolution Imaging Science Experiment) images, visualize data acquired by the rover, and develop, model, and validate the activities the rover will perform. MSLICE enables users to securely contribute to the mission s activity planning process from their home institutions using off-the-shelf laptop computers. This software has made use of several plug-ins (software components) developed for previous missions [e.g., Mars Exploration Rover (MER), Phoenix Mars Lander (PHX)] and other technology tasks. It has a simple, intuitive, and powerful search capability. For any given mission, there is a huge amount of data and associated metadata that is generated. To help users sort through this information, MSLICE s search interface is provided in a similar fashion as major Internet search engines. With regard to the HiRISE visualization of the rover s traverse, this view is a map of the mission that allows scientists to easily gauge where the rover has been and where it is likely to go. The map also provides the ability to correct or adjust the known position of the rover through the overlaying of images acquired from the rover on top of the HiRISE image. A user can then correct the rover s position by collocating the visible features in the overlays with the same features in the underlying HiRISE image. MSLICE users can also rapidly search all mission data for images that contain a point specified by the user in another image or panoramic mosaic. MSLICE allows the creation of targets, which provides a way for scientists to collaboratively name features on the surface of Mars. These targets can also be used to convey instrument-pointing information to the activity plan. The software allows users to develop a plan of what they would like the rover to accomplish for a given time period. When developing the plan, the user can input constraints between activities or groups of activities. MSLICE will enforce said constraints and ensure that all mission flight rules are satisfied.

Powell, Mark W.↗
NASA NTRS2009

Multi-Mission Automated Task Invocation Subsystem

Multi-Mission Automated Task Invocation Subsystem (MATIS) is software that establishes a distributed data-processing framework for automated generation of instrument data products from a spacecraft mission. Each mission may set up a set of MATIS servers for processing its data products. MATIS embodies lessons learned in experience with prior instrument- data-product-generation software. MATIS is an event-driven workflow manager that interprets project-specific, user-defined rules for managing processes. It executes programs in response to specific events under specific conditions according to the rules. Because requirements of different missions are too diverse to be satisfied by one program, MATIS accommodates plug-in programs. MATIS is flexible in that users can control such processing parameters as how many pipelines to run and on which computing machines to run them. MATIS has a fail-safe capability. At each step, MATIS captures and retains pertinent information needed to complete the step and start the next step. In the event of a restart, this information is retrieved so that processing can be resumed appropriately. At this writing, it is planned to develop a graphical user interface (GUI) for monitoring and controlling a product generation engine in MATIS. The GUI would enable users to schedule multiple processes and manage the data products produced in the processes. Although MATIS was initially designed for instrument data product generation,

Cheng, Cecilia S.↗
NASA NTRS2009

The 2nd Generation Real Time Mission Monitor (RTMM) Development

The NASA Real Time Mission Monitor (RTMM) is a visualization and information system that fuses multiple Earth science data sources, to enable real time decisionmaking for airborne and ground validation experiments. Developed at the National Aeronautics and Space Administration (NASA) Marshall Space Flight Center, RTMM is a situational awareness, decision-support system that integrates satellite imagery and orbit data, radar and other surface observations (e.g., lightning location network data), airborne navigation and instrument data sets, model output parameters, and other applicable Earth science data sets. The integration and delivery of this information is made possible using data acquisition systems, network communication links, network server resources, and visualizations through the Google Earth virtual globe application. In order to improve the usefulness and efficiency of the RTMM system, capabilities are being developed to allow the end-user to easily configure RTMM applications based on their mission-specific requirements and objectives. This second generation RTMM is being redesigned to take advantage of the Google plug-in capabilities to run multiple applications in a web browser rather than the original single application Google Earth approach. Currently RTMM employs a limited Service Oriented Architecture approach to enable discovery of mission specific resources. We are expanding the RTMM architecture such that it will more effectively utilize the Open Geospatial Consortium Sensor Web Enablement services and other new technology software tools and components. These modifications and extensions will result in a robust, versatile RTMM system that will greatly increase flexibility of the user to choose which science data sets and support applications to view and/or use. The improvements brought about by RTMM 2nd generation system will provide mission planners and airborne scientists with enhanced decision-making tools and capabilities to more efficiently plan, prepare and execute missions, as well as to playback and review past mission data. To paraphrase the old television commercial RTMM doesn t make the airborne science, it makes the airborne science easier.

Blakeslee, Richard↗
NASA NTRS2007

Simple, Script-Based Science Processing Archive

The Simple, Scalable, Script-based Science Processing (S4P) Archive (S4PA) is a disk-based archival system for remote sensing data. It is based on the data-driven framework of S4P and is used for data transfer, data preprocessing, metadata generation, data archive, and data distribution. New data are automatically detected by the system. S4P provides services such as data access control, data subscription, metadata publication, data replication, and data recovery. It comprises scripts that control the data flow. The system detects the availability of data on an FTP (file transfer protocol) server, initiates data transfer, preprocesses data if necessary, and archives it on readily available disk drives with FTP and HTTP (Hypertext Transfer Protocol) access, allowing instantaneous data access. There are options for plug-ins for data preprocessing before storage. Publication of metadata to external applications such as the Earth Observing System Clearinghouse (ECHO) is also supported. S4PA includes a graphical user interface for monitoring the system operation and a tool for deploying the system. To ensure reliability, S4P continuously checks stored data for integrity, Further reliability is provided by tape backups of disks made once a disk partition is full and closed. The system is designed for low maintenance, requiring minimal operator oversight.

Lynnes, Christopher↗
NASA NTRS2007

Online Remote Sensing Interface

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

Lawhead, Joel↗
NASA NTRS2006

Ground Processing of Data From the Mars Exploration Rovers

A computer program implements the Earth side of the protocol that governs the transfer of data files generated by the Mars Exploration Rovers. It also provides tools for viewing data in these files and integrating data-product files into automated and manual processes. It reconstitutes files from telemetry data packets. Even if only one packet is received, metadata provide enough information to enable this program to identify and use partial data products. This software can generate commands to acknowledge received files and retransmit missed parts of files, or it can feed a manual process to make decisions about retransmission. The software uses an Extensible Markup Language (XML) data dictionary to provide a generic capability for displaying files of basic types, and uses external "plug-in" application programs to provide more sophisticated displays. This program makes data products available with very low latency, and can trigger automated actions when complete or partial products are received. The software is easy to install and use. The only system requirement for installing the software is a Java J2SE 1.4 platform. Several instances of the software can be executed simultaneously on the same machine.

Wright, Jesse↗
NASA NTRS2006

Simulating Humans as Integral Parts of Spacecraft Missions

The Collaborative-Virtual Environment Simulation Tool (C-VEST) software was developed for use in a NASA project entitled "3-D Interactive Digital Virtual Human." The project is oriented toward the use of a comprehensive suite of advanced software tools in computational simulations for the purposes of human-centered design of spacecraft missions and of the spacecraft, space suits, and other equipment to be used on the missions. The C-VEST software affords an unprecedented suite of capabilities for three-dimensional virtual-environment simulations with plug-in interfaces for physiological data, haptic interfaces, plug-and-play software, realtime control, and/or playback control. Mathematical models of the mechanics of the human body and of the aforementioned equipment are implemented in software and integrated to simulate forces exerted on and by astronauts as they work. The computational results can then support the iterative processes of design, building, and testing in applied systems engineering and integration. The results of the simulations provide guidance for devising measures to counteract effects of microgravity on the human body and for the rapid development of virtual (that is, simulated) prototypes of advanced space suits, cockpits, and robots to enhance the productivity, comfort, and safety of astronauts. The unique ability to implement human-in-the-loop immersion also makes the C-VEST software potentially valuable for use in commercial and academic settings beyond the original space-mission setting.

Bruins, Anthony C.↗
NASA NTRS2009

Generating Code Review Documentation for Auto-Generated Mission-Critical Software

Model-based design and automated code generation are increasingly used at NASA to produce actual flight code, particularly in the Guidance, Navigation, and Control domain. However, since code generators are typically not qualified, there is no guarantee that their output is correct, and consequently auto-generated code still needs to be fully tested and certified. We have thus developed AUTOCERT, a generator-independent plug-in that supports the certification of auto-generated code. AUTOCERT takes a set of mission safety requirements, and formally verifies that the autogenerated code satisfies these requirements. It generates a natural language report that explains why and how the code complies with the specified requirements. The report is hyper-linked to both the program and the verification conditions and thus provides a high-level structured argument containing tracing information for use in code reviews.

Denney, Ewen↗
NASA NTRS2010

Lead-Free Electronics: Impact for Space Electronics

Pb is used as a constituent in solder alloys used to connect and attach electronic parts to printed wiring boards (PWBs). Similar Pbbearing alloys are electroplated or hot dipped onto the terminations of electronic parts to protect the terminations and make them solderable. Changing to Pb-free solders and termination finishes has introduced significant technical challenges into the supply chain. Tin/lead (Sn/Pb) alloys have been the solders of choice for electronics for more than 50 years. Pb-free solder alloys are available but there is not a plug-in replacement for 60/40 or 63/37 (Sn/Pb) alloys, which have been the industry workhorses.

Sampson, Michael J.↗
NASA NTRS2010

Kepler Science Operations Center Pipeline Framework

The Kepler mission is designed to continuously monitor up to 170,000 stars at a 30 minute cadence for 3.5 years searching for Earth-size planets. The data are processed at the Science Operations Center (SOC) at NASA Ames Research Center. Because of the large volume of data and the memory and CPU-intensive nature of the analysis, significant computing hardware is required. We have developed generic pipeline framework software that is used to distribute and synchronize the processing across a cluster of CPUs and to manage the resulting products. The framework is written in Java and is therefore platform-independent, and scales from a single, standalone workstation (for development and research on small data sets) to a full cluster of homogeneous or heterogeneous hardware with minimal configuration changes. A plug-in architecture provides customized control of the unit of work without the need to modify the framework itself. Distributed transaction services provide for atomic storage of pipeline products for a unit of work across a relational database and the custom Kepler DB. Generic parameter management and data accountability services are provided to record the parameter values, software versions, and other meta-data used for each pipeline execution. A graphical console allows for the configuration, execution, and monitoring of pipelines. An alert and metrics subsystem is used to monitor the health and performance of the pipeline. The framework was developed for the Kepler project based on Kepler requirements, but the framework itself is generic and could be used for a variety of applications where these features are needed.

Klaus, Todd C.↗
NASA NTRS2004

Advanced Infant Car Seat Would Increase Highway Safety

An advanced infant car seat has been proposed to increase highway safety by reducing the incidence of crying, fussy behavior, and other child-related distractions that divert an adult driver s attention from driving. In addition to a conventional infant car seat with safety restraints, the proposed advanced infant car seat would include a number of components and subsystems that would function together as a comprehensive infant-care system that would keep its occupant safe, comfortable, and entertained, and would enable the driver to monitor the baby without having to either stop the car or turn around to face the infant during driving. The system would include a vibrator with bulb switch to operate; the switch would double as a squeeze toy that would make its own specific sound. A music subsystem would include loudspeakers built into the seat plus digital and analog circuitry that would utilize plug-in memory modules to synthesize music or a variety of other sounds. The music subsystem would include a built-in sound generator that could synthesize white noise or a human heartbeat to calm the baby to sleep. A second bulb switch could be used to control the music subsystem and would double as a squeeze toy that would make a distinct sound. An anti-noise sound-suppression system would isolate the baby from potentially disturbing ambient external noises. This subsystem would include small microphones, placed near the baby s ears, to detect ambient noise. The outputs of the microphone would be amplified and fed to the loudspeakers at appropriate amplitude and in a phase opposite that of the detected ambient noise, such that the net ambient sound arriving at the baby s ears would be almost completely cancelled. A video-camera subsystem would enable the driver to monitor the baby visually while continuing to face forward. One or more portable miniature video cameras could be embedded in the side of the infant car seat (see figure) or in a flip-down handle. The outputs of the video cameras would be transmitted by radio or infrared to a portable, miniature receiver/video monitor unit that would be attached to the dashboard of the car. The video-camera subsystem can also be used within transmission/reception range when the seat was removed from the car. The system would include a biotelemetric and tracking subsystem, which would include a Global Positioning System receiver for measuring its location. This subsystem would transmit the location of the infant car seat (even if the seat were not in a car) along with such biometric data as the baby s heart rate, perspiration rate, urinary status, temperature, and rate of breathing. Upon detecting any anomalies in the biometric data, this subsystem would send a warning to a paging device installed in the car or carried by the driver, so that the driver could pull the car off the road to attend to the baby. A motion detector in this subsystem would send a warning if the infant car seat were to be moved or otherwise disturbed unexpectedly while the infant was seated in it: this warning function, in combination with the position- tracking function, could help in finding a baby who had been kidnapped with the seat. Removable rechargeable batteries would enable uninterrupted functioning of all parts of the system while transporting the baby to and from the car. The batteries could be recharged via the cigarette-lighter outlet in the car or by use of an external AC-powered charger.

Dabney, Richard↗
NASA NTRS2003

Software for Building Models of 3D Objects via the Internet

The Virtual EDF Builder (where EDF signifies Electronic Development Fixture) is a computer program that facilitates the use of the Internet for building and displaying digital models of three-dimensional (3D) objects that ordinarily comprise assemblies of solid models created previously by use of computer-aided-design (CAD) programs. The Virtual EDF Builder resides on a Unix-based server computer. It is used in conjunction with a commercially available Web-based plug-in viewer program that runs on a client computer. The Virtual EDF Builder acts as a translator between the viewer program and a database stored on the server. The translation function includes the provision of uniform resource locator (URL) links to other Web-based computer systems and databases. The Virtual EDF builder can be used in two ways: (1) If the client computer is Unix-based, then it can assemble a model locally; the computational load is transferred from the server to the client computer. (2) Alternatively, the server can be made to build the model, in which case the server bears the computational load and the results are downloaded to the client computer or workstation upon completion.

Schramer, Tim↗
DOE OSTI2026

Multi-Split Variable Refrigerant Flow (VRF) System Building Energy Simulations Using Performance Maps

Multi-split variable refrigerant flow (VRF) systems are highly energy-efficient HVAC (heating, ventilation and air conditioning) technologies that connect a single outdoor unit to multiple independent indoor terminal units using a common refrigerant circuit and a variable-speed compressor. Building energy simulations that incorporate VRF systems help model their unique operational characteristics and predict energy consumption in specific building designs. Traditionally, EnergyPlus models these systems by employing multiple sets of performance curves to characterize both individual terminal units and the outdoor unit. However, producing these curves is labor intensive and error prone, and they often do not capture all the key input and output variables. This paper introduces a novel approach that uses multi-dimensional performance maps to model VRF systems in building environments for space cooling. In this approach, performance maps are developed at the component level—separately for the outdoor unit and for each indoor terminal. The new modeling method is validated within EnergyPlus via a Python plug-in that contains a simple solver loop to coordinate the component-level, indoor, and outdoor unit maps. Furthermore, because performance maps can span more variables than traditional performance curves, they offer the opportunity to implement advanced controls, such as enhanced dehumidification and compressor modulation. A VRF air conditioner’s hardware system was modeled using the DOE/ORNL Heat Pump Design Model, which was automated to produce extensive performance maps for both the indoor and outdoor units.

Shen, Bo [ORNL] (ORCID:0000000336600393)↗
DOE OSTI2026

Community and Passenger Survey Responses for Bastrop, Texas Low-Speed Electric Vehicle Mobility Service Project

This document describes the contents of the following data products: 1. ALL-survey_results_NREL_LiveWire_04_14_2023 (Excel file with two worksheets) 2. eCab_DOE_NREL_LiveWire_04_14_2023_results_all_surveys_except_SP_csv (CSV file) 3. eCab_DOE_NREL_LiveWire_04_14_2023_SP_survey_results_only_csv (CSV file). These data products contain the results of the surveys conducted throughout the DOE-funded Electric First-/Last-Mile On-Demand Shuttle Service for Rural Communities in Central Texas project. The Excel file is the original database of all the survey results (contained in two worksheets). The CSV files are those two worksheets saved as individual CSV files.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
DOE OSTI2026

Cooperative Automated Cohort Driving on Connected Infrastructure, Arterial Roadways, and Highways: Final Project Demonstration and System-of-Systems Model Correlation

This project seeks to synergize vehicle automated driving and connectivity data to improve mobility and energy efficiency of groups of mixed vehicles operating in close proximity (vehicle cohort) on various infrastructure. A custom cellular communication network links vehicles operating as a cohort with infrastructure to a centralized system-of-systems digital twin with an AI-based optimal behavior planner. The data contained in this set are from final testing and technology demonstrations to U.S. Department of Energy staff at the American Center for Mobility. The data contain single-lane, single-light scenarios; multi-lane, multi-light arterial scenarios; and limited-access highway scenarios. All test cases were derived from simulations and replicated on the test track. The project employed two and four light-duty vehicles with connectivity and drive automation for the testing. The baseline scenario without connectivity was run under the control of the system-of-systems centralized planner but operating each vehicle with an intelligent driver model controlling the velocity, lane utilization, and vehicle gap. This was to ensure the highest compatibility with the simulation in terms of dynamic behavior. The connected cohort case utilized AI optimization to perform coordinated and cooperative control for energy, as well as safe, comfortable behavior for the cohort. The dataset is appropriately named with unconnected and connected designations, with comparisons sharing the same run index number. The included PowerPoint and PDF files describe the test setup and provide an overview of results from the project. ![image](de-EE0009209_March_2023_Data_Arterial_Scenario_Results.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
DOE OSTI2026

Energy Consumption, Performance, and Cost Estimates for Medium and Heavy-Duty Vehicles Based on 2022 Assumptions

Assumptions for this work was collected and the analysis was completed in FY22. This contains information for more than 20 types of medium and heavy duty vehicles. Vehicles with various levels of hybridization, electric and fuel cell powertrains are considered in this work. More details are available in the report published by Argonne accessible from https://vms.taps.anl.gov/research-highlights/u-s-doe-vto-hfto-r-d-benefits/. TechScape, a convenient data visualization tool is also provided by Argonne for this data, accessible from [TechScape Web](https://vms.taps.anl.gov/data/techscape-web-2023/).

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
DOE OSTI2025

Federal Workplace Charging Program Guide

The 2015 Fixing America's Surface Transportation (FAST) Act authorizes the installation, operation, and maintenance of electric vehicle supply equipment (EVSE) for the purpose of recharging employees' privately owned vehicles (POVs) under the custody or control of the General Services Administration (GSA) or a Federal agency. It requires the collection of fees to recover the costs of installing, operating, and maintaining this equipment and imposes reporting requirements. This program guide reviews those requirements, excerpts the relevant language in Appendix A, and describes when and how fees may be required to cover costs of electricity, network costs, EVSE units, and installations in various scenarios. This program guide is designed to support Federal agencies developing and refining workplace charging programs for employee POVs. While it provides guidance and best practices, it does not replace agencywide policies or agency-specific legal counsel. It contains a roadmap for agency workplace charging programs and defines roles and responsibilities. This guide explains how to determine the number of POVs likely to charge at a given site and contains a sample employee survey in Appendix B. It reviews EVSE planning, including unit selection and acquisition, charger location(s), accounting for available power capacity, using existing infrastructure, and funding an incentive program. It also discusses the costs associated with EVSE acquisition, installation, and network management. These costs inform the subsequently provided information, which describes how to amortize costs to determine appropriate fees for each charging session. The final two sections of this guide address aspects of ongoing program management that the facility coordinator should consider and the reporting requirements associated with the FAST Act. The insights in this guide are applicable to all agency-owned and GSA-leased buildings or facilities offering the use of EVSE or a 120-volt receptacle for the purpose of recharging an employee's POV. However, the FAST Act requirements typically do not apply to any building or facility operated and maintained by a third-party vendor offering the use of EVSE as part of a commercial building lease unless the agency is managing the station and/or energy on behalf of the building and collecting POV fees.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗