Search NASA⌕ Search

SEARCH · Search NASA

Results for “Building Component Library”

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 19 records

Discrete event simulation tool for analysis of qualitative models of continuous processing systems

An artificial intelligence design and qualitative modeling tool is disclosed for creating computer models and simulating continuous activities, functions, and/or behavior using developed discrete event techniques. Conveniently, the tool is organized in four modules: library design module, model construction module, simulation module, and experimentation and analysis. The library design module supports the building of library knowledge including component classes and elements pertinent to a particular domain of continuous activities, functions, and behavior being modeled. The continuous behavior is defined discretely with respect to invocation statements, effect statements, and time delays. The functionality of the components is defined in terms of variable cluster instances, independent processes, and modes, further defined in terms of mode transition processes and mode dependent processes. Model construction utilizes the hierarchy of libraries and connects them with appropriate relations. The simulation executes a specialized initialization routine and executes events in a manner that includes selective inherency of characteristics through a time and event schema until the event queue in the simulator is emptied. The experimentation and analysis module supports analysis through the generation of appropriate log files and graphics developments and includes the ability of log file comparisons.

Malin, Jane T.↗

SIMWEST - A simulation model for wind energy storage systems

This paper describes a comprehensive and efficient computer program for the modeling of wind energy systems with storage. The level of detail of SIMWEST (SImulation Model for Wind Energy STorage) is consistent with evaluating the economic feasibility as well as the general performance of wind energy systems with energy storage options. The software package consists of two basic programs and a library of system, environmental, and control components. The first program is a precompiler which allows the library components to be put together in building block form. The second program performs the technoeconomic system analysis with the required input/output, and the integration of system dynamics. An example of the application of the SIMWEST program to a current 100 kW wind energy storage system is given.

Edsinger, R. W.↗

Avionics System Architecture Tool

Avionics System Architecture Tool (ASAT) is a computer program intended for use during the avionics-system-architecture- design phase of the process of designing a spacecraft for a specific mission. ASAT enables simulation of the dynamics of the command-and-data-handling functions of the spacecraft avionics in the scenarios in which the spacecraft is expected to operate. ASAT is built upon I-Logix Statemate MAGNUM, providing a complement of dynamic system modeling tools, including a graphical user interface (GUI), modeling checking capabilities, and a simulation engine. ASAT augments this with a library of predefined avionics components and additional software to support building and analyzing avionics hardware architectures using these components.

Chau, Savio↗

Numerical Propulsion System Simulation (NPSS) Power Systems Library

This presentation covers the Numerical Propulsion System Simulation (NPSS) Power Systems Library being developed by NASA. This library is a set of components, models, and interfaces for the NPSS language to enable building electric power system models for electrified propulsion systems. The presentation is to be given at the 3rd annual RVLT Toolchain Workshop, where attendees from across the eVTOL industry will be informed of NASA’s tools for eVTOL conceptual design from the vehicle level down through subsystems including propulsion, noise, electrical power, and others. It covers where the NPSS Power System Library fits into NASA’s RVLT toolchain and RVLT work in general, and will inform the audience of how the tool can be useful in their own work.

Electric vertical takeoff and landing↗

Software packager user's guide

Software integration is a growing area of concern for many programmers and software managers because the need to build new programs quickly from existing components is greater than ever. This includes building versions of software products for multiple hardware platforms and operating systems, building programs from components written in different languages, and building systems from components that must execute on different machines in a distributed network. The goal of software integration is to make building new programs from existing components more seamless -- programmers should pay minimal attention to the underlying configuration issues involved. Libraries of reusable components and classes are important tools but only partial solutions to software development problems. Even though software components may have compatible interfaces, there may be other reasons, such as differences between execution environments, why they cannot be integrated. Often, components must be adapted or reimplemented to fit into another application because of implementation differences -- they are implemented in different programming languages, dependent on different operating system resources, or must execute on different physical machines. The software packager is a tool that allows programmers to deal with interfaces between software components and ignore complex integration details. The packager takes modular descriptions of the structure of a software system written in the package specification language and produces an integration program in the form of a makefile. If complex integration tools are needed to integrate a set of components, such as remote procedure call stubs, their use is implied by the packager automatically and stub generation tools are invoked in the corresponding makefile. The programmer deals only with the components themselves and not the details of how to build the system on any given platform.

Callahan, John R.↗

General Mission Analysis Tool (GMAT) Architectural Specification. Draft

Early in 2002, Goddard Space Flight Center (GSFC) began to identify requirements for the flight dynamics software needed to fly upcoming missions that use formations of spacecraft to collect data. These requirements ranged from low level modeling features to large scale interoperability requirements. In 2003 we began work on a system designed to meet these requirement; this system is GMAT. The General Mission Analysis Tool (GMAT) is a general purpose flight dynamics modeling tool built on open source principles. The GMAT code is written in C++, and uses modern C++ constructs extensively. GMAT can be run through either a fully functional Graphical User Interface (GUI) or as a command line program with minimal user feedback. The system is built and runs on Microsoft Windows, Linux, and Macintosh OS X platforms. The GMAT GUI is written using wxWidgets, a cross platform library of components that streamlines the development and extension of the user interface Flight dynamics modeling is performed in GMAT by building components that represent the players in the analysis problem that is being modeled. These components interact through the sequential execution of instructions, embodied in the GMAT Mission Sequence. A typical Mission Sequence will model the trajectories of a set of spacecraft evolving over time, calculating relevant parameters during this propagation, and maneuvering individual spacecraft to maintain a set of mission constraints as established by the mission analyst. All of the elements used in GMAT for mission analysis can be viewed in the GMAT GUI or through a custom scripting language. Analysis problems modeled in GMAT are saved as script files, and these files can be read into GMAT. When a script is read into the GMAT GUI, the corresponding user interface elements are constructed in the GMAT GUI. The GMAT system was developed from the ground up to run in a platform agnostic environment. The source code compiles on numerous different platforms, and is regularly exercised running on Windows, Linux and Macintosh computers by the development and analysis teams working on the project. The system can be run using either a graphical user interface, written using the open source wxWidgets framework, or from a text console. The GMAT source code was written using open source tools. GSFC has released the code using the NASA open source license.

Hughes, Steven P.↗

Session 6: Dynamic Modeling and Systems Analysis

These presentations cover some of the ongoing work in dynamic modeling and dynamic systems analysis. The first presentation discusses dynamic systems analysis and how to integrate dynamic performance information into the systems analysis. The ability to evaluate the dynamic performance of an engine design may allow tradeoffs between the dynamic performance and operability of a design resulting in a more efficient engine design. The second presentation discusses the Toolbox for Modeling and Analysis of Thermodynamic Systems (T-MATS). T-MATS is a Simulation system with a library containing the basic building blocks that can be used to create dynamic Thermodynamic Systems. Some of the key features include Turbo machinery components, such as turbines, compressors, etc., and basic control system blocks. T-MAT is written in the Matlab-Simulink environment and is open source software. The third presentation focuses on getting additional performance from the engine by allowing the limit regulators only to be active when a limit is danger of being violated. Typical aircraft engine control architecture is based on MINMAX scheme, which is designed to keep engine operating within prescribed mechanical/operational safety limits. Using a conditionally active min-max limit regulator scheme, additional performance can be gained by disabling non-relevant limit regulators

control↗

Transportable Payload Operations Control Center reusable software: Building blocks for quality ground data systems

The Mission Operations Division (MOD) at Goddard Space Flight Center builds Mission Operations Centers which are used by Flight Operations Teams to monitor and control satellites. Reducing system life cycle costs through software reuse has always been a priority of the MOD. The MOD's Transportable Payload Operations Control Center development team established an extensive library of 14 subsystems with over 100,000 delivered source instructions of reusable, generic software components. Nine TPOCC-based control centers to date support 11 satellites and achieved an average software reuse level of more than 75 percent. This paper shares experiences of how the TPOCC building blocks were developed and how building block developer's, mission development teams, and users are all part of the process.

Mahmot, Ron↗

Biomaterials Out of Thin Air: in Situ, On-Demand Printing of Advanced Biocomposites

Upmass is the single most significant limitation of our current space mission capability. Although biomaterials and biocomposites have mass, strength, flexibility, and self-healing properties that could significantly reduce upmass, their use is limited by the following drawbacks: Expensive, specific production. Many biomaterials can only be produced as part of significant support ecosystem; Inaccessible functional customization. The grain of wood, the porosity of bone, and so on are an integral part of the materials' desired mechanical properties, but are not deterministic when the material is naturally grown; Limited compositions. Most biomaterials (unlike metal, plastic, etc.) cannot be easily combined or modified to produce new materials. This project builds on recent advances in: Synthetic biology. Libraries of standardized genetic parts which can be used for controlled cellular material production, delivery, and binding; 3D printing. Commercial off-the-shelf components which can be used to make of a pico- to nanoliter cell deposition system; Tissue engineering. Proven cell-compatible support hydrogels and scaffolds can be modified to bind the deposited biomaterials of interest. Objectives: Feasibility and benefit analysis. Two mission contexts span the concept's scope (see below); Proof-of-concept demonstration. A simple grid of two proteins, fluorescent for easy detection, to validate the core technology concept; Proposed implementations for follow-on work. Avenues for future work on each core component (host cell, production control, material delivery, material binding, etc.); Complementary studies exploration. A survey of other emerging areas (in situ resource utilization, protein engineering, etc.) with the potential to multiply our technology's impact. Potential Impacts: This application could dramatically expand manufacturing capabilities on Earth and in space: In situ resource utilization. A far greater range of materials and products will be available from the limited palette offered by in situ resource extraction techniques; Reduced equipment and material upmass for off-Earth habitats. Ready- to-use highly specialized construction materials (radiation hardened, compressive/tensile, light or dense) from an extremely low starting mass; Structured biomaterial production. New ready-to-use macro, micro, and molecular manufacturing techniques for traditional biomaterials such as wood, bone and shell; New and novel biocomposite creation. The ability to create completely novel material composites from any base material that cells can be engineered to produce. Suggested Mission Contexts: ISS part manufacturing. A 'minimal working example' making a finished biomaterial part aboard the International Space Station; A long-term Mars habitat. 'Cradle-to-grave' use at a hypothetical Mars habitat, covering everything from tools to construction materials. Alternate Abstract: Imagine being able to print anything from tools and composite building materials to food and human tissues. Imagine being on Mars with the ability to replace any broken part, whether it's a part of your spacesuit, your habitat, or your own body. We propose a technique that would allow just that. By printing 3D arrays of cells engineered to secrete the necessary materials, the abundant in situ resources of atmosphere and regolith become organic, inorganic, or organic-inorganic composite materials. Such materials include novel, biologically derived materials not previously possible to fabricate.

habitats↗

Biomaterials Out of Thin Air: in Situ, On-demand Printing of Advanced Biocomposites

Upmass is the single most significant limitation of our current space mission capability. Although biomaterials and biocomposites have mass, strength, flexibility, and self-healing properties that could significantly reduce upmass, their use is limited by the following drawbacks: Expensive, specific production. Many biomaterials can only be produced as part of significant support ecosystem; Inaccessible functional customization. The grain of wood, the porosity of bone, and so on are an integral part of the materials' desired mechanical properties, but are not deterministic when the material is naturally grown; Limited compositions. Most biomaterials (unlike metal, plastic, etc.) cannot be easily combined or modified to produce new materials. This project builds on recent advances in: Synthetic biology. Libraries of standardized genetic parts which can be used for controlled cellular material production, delivery, and binding; 3D printing. Commercial off-the-shelf components which can be used to make of a pico- to nanoliter cell deposition system; Tissue engineering. Proven cell-compatible support hydrogels and scaffolds can be modified to bind the deposited biomaterials of interest. Objectives: Feasibility and benefit analysis. Two mission contexts span the concept's scope (see below); Proof-of-concept demonstration. A simple grid of two proteins, fluorescent for easy detection, to validate the core technology concept; Proposed implementations for follow-on work. Avenues for future work on each core component (host cell, production control, material delivery, material binding, etc.); Complementary studies exploration. A survey of other emerging areas (in situ resource utilization, protein engineering, etc.) with the potential to multiply our technology's impact. Potential Impacts: This application could dramatically expand manufacturing capabilities on Earth and in space: In situ resource utilization. A far greater range of materials and products will be available from the limited palette offered by in situ resource extraction techniques; Reduced equipment and material upmass for off-Earth habitats. Ready- to-use highly specialized construction materials (radiation hardened, compressive/tensile, light or dense) from an extremely low starting mass; Structured biomaterial production. New ready-to-use macro, micro, and molecular manufacturing techniques for traditional biomaterials such as wood, bone and shell; New and novel biocomposite creation. The ability to create completely novel material composites from any base material that cells can be engineered to produce. Suggested Mission Contexts: ISS part manufacturing. A 'minimal working example' making a finished biomaterial part aboard the International Space Station; A long-term Mars habitat. 'Cradle-to-grave' use at a hypothetical Mars habitat, covering everything from tools to construction materials. Alternate Abstract: Imagine being able to print anything from tools and composite building materials to food and human tissues. Imagine being on Mars with the ability to replace any broken part, whether it's a part of your spacesuit, your habitat, or your own body. We propose a technique that would allow just that. By printing 3D arrays of cells engineered to secrete the necessary materials, the abundant in situ resources of atmosphere and regolith become organic, inorganic, or organic-inorganic composite materials. Such materials include novel, biologically derived materials not previously possible to fabricate.

habitats↗

Open-systems architecture of a standardized command interface chip-set for switching and control of a spacecraft power bus

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.

flight computers↗

Earthdata User Interface (EUI) Library

As more remote sensing data moves to the cloud, the design tools we use to build user experiences and visualizations need to change and adapt to make the best use this new data reality. EUI 2.0, the next major iteration of the Earthdata User Interface Library, aims to make creating rich user experiences around NASA's Earth Observation System Data and Information System (EOSDIS) data easy and user-friendly. Building on a solid framework of design components, EUI 2.0 will be open source and have off-the-shelf integration with the Common Metadata Repository (CMR), basic mapping and visualization tools, a refreshed design toolkit for building apps and websites that fit the Earthdata design theme and guidelines. EUI 2.0 will allow for the rapid development of websites and applications based on EOSDIS tools and data holdings. It will also make use of cloud data availability to enable data visualization and analysis without the need to download and sync data.

Siarto, Jeff↗

Mission interactive scenarion studio for autonomous spacecraft

We propose building a Studio enabling the use of diverse existing mission activity and scenario patterns, the creation of new ones, and the modeling of their effects using existing modeling tools. The core of the Studio is a component-based Type Library, which captures years of mission adaptation patterns in various forms. The Studio works as a content server to capture the developed adaptation knowledge for reuse and provides bridging into different mission uplink implementations, including the Mission Data System [l] (MDS) state/goal machinery. Various activities can be coordinated, controlled, and reused through the Studio's component interface to establish and model a mission scenario. A special component Factory mechanism will be in place to facilitate the adaptation of projects into the Studio. The architecture of the Studio reflects and enforces a division of knowledge and actions into three parts: Model, Controller, Viewer. The Model contains information about (a proposed version of) the spacecraft and mission. The Controller contains logic for constructing scenarios of mission activities. The information in the Model and Controller is principally in the form of reusable patterns. A Viewer can be a simple or complex software system. For example, Apgen [2,3] is one possible viewer, MDS is another. A 3-tiered infrastructure is used for the Studio, reflecting the Model, Controller, Viewer architecture [4,5]. The Studio is useful in pre-phase A of a project by enabling spacecraft design options to be played against desired mission scenarios. In later design phases of a project, the construction and modeling of more detailed scenarios is supported by the Studio.

autonomous spacecraft↗

TRSkit: A Simple Digital Library Toolkit

This paper introduces TRSkit, a simple and effective toolkit for building digital libraries on the World Wide Web. The toolkit was developed for the creation of the Langley Technical Report Server and the NASA Technical Report Server, but is applicable to most simple distribution paradigms. TRSkit contains a handful of freely available software components designed to be run under the UNIX operating system and served via the World Wide Web. The intended customer is the person that must continuously and synchronously distribute anywhere from 100 - 100,000's of information units and does not have extensive resources to devote to the problem.

Nelson, Michael L.↗

Developing a Vision for Heliophysics Infrastructure: The LIKED Resource and the DIARieS Ecosystem

Heliophysics data and computational infrastracture are not equipped for 21st science, suffering from holes in the know-how to build better systems. Without a clear vision, efforts to improve the infrastructure have been incremental and incoherent. This poster presents both the vision and the technology required: an online LIbrary KnowledgE and Discovery (LIKED) resource for discovering and implementing knowledge, data, and infrastructure resources; and an online analysis ecosystem to simplify Discovery, Implementation, Analysis, Reproducibility, and Sharing (DIARieS) of scientific results and environments. The LIKED and DIARieS solutions adopt FAIR data principles and the best practices from the budding field of open science. The proposed new infrastructure components will close many of the current gaps in heliophysics’ infrastructure, such as the ability to search for data and knowledge by phenomenon across domains, and to find software and examples relevant to the desired data set (including model data). Further, these components will enable community members to more efficiently use the resources already present and improve upon the content via a community-curated and trusted library. Combining these solutions lowers the barriers to heliophysics resources for all, increasing the return on our investments. Finally, the structure behind these ideas are topic-agnostic, so they are fully extensible to other fields, leading to invaluable connections to other disciplines. Just as with the development and construction of a long-term satellite mission, we must work together as a community to build a vision of the infrastructure that will most benefit the community, and then collaborate to construct, assemble, and test all the necessary pieces individually and as a unit. Our purpose in presenting this work is to not only describe the proposed vision, but also to gather feedback from the community on this topic.

infrastructure↗

The AI Bus architecture for distributed knowledge-based systems

The AI Bus architecture is layered, distributed object oriented framework developed to support the requirements of advanced technology programs for an order of magnitude improvement in software costs. The consequent need for highly autonomous computer systems, adaptable to new technology advances over a long lifespan, led to the design of an open architecture and toolbox for building large scale, robust, production quality systems. The AI Bus accommodates a mix of knowledge based and conventional components, running on heterogeneous, distributed real world and testbed environment. The concepts and design is described of the AI Bus architecture and its current implementation status as a Unix C++ library or reusable objects. Each high level semiautonomous agent process consists of a number of knowledge sources together with interagent communication mechanisms based on shared blackboards and message passing acquaintances. Standard interfaces and protocols are followed for combining and validating subsystems. Dynamic probes or demons provide an event driven means for providing active objects with shared access to resources, and each other, while not violating their security.

Schultz, Roger D.↗

Containerized GEOS: Toward a Portable Climate Model

The NASA Goddard Earth Observing System (GEOS) is an Earth system model used for weather, climate, and other scientific applications. GEOS consists of linked components that can run in various configurations such as atmosphere-only and coupled atmosphere-ocean. Running this model on any new supercomputing system depends on operating systems, compilers, MPI stacks, and libraries being present and correctly configured. To remove that burden from users, our project explores building and running GEOS using Singularity containers – files containing all the needed software dependencies – on both NASA high-end computing systems and commercial cloud computing environments. Ultimately, the goal is for containerized GEOS to make it easier for users outside of NASA to deploy and run the model on any machine.

Matthew Thompson↗

Building distributed rule-based systems using the AI Bus

The AI Bus software architecture was designed to support the construction of large-scale, production-quality applications in areas of high technology flux, running heterogeneous distributed environments, utilizing a mix of knowledge-based and conventional components. These goals led to its current development as a layered, object-oriented library for cooperative systems. This paper describes the concepts and design of the AI Bus and its implementation status as a library of reusable and customizable objects, structured by layers from operating system interfaces up to high-level knowledge-based agents. Each agent is a semi-autonomous process with specialized expertise, and consists of a number of knowledge sources (a knowledge base and inference engine). Inter-agent communication mechanisms are based on blackboards and Actors-style acquaintances. As a conservative first implementation, we used C++ on top of Unix, and wrapped an embedded Clips with methods for the knowledge source class. This involved designing standard protocols for communication and functions which use these protocols in rules. Embedding several CLIPS objects within a single process was an unexpected problem because of global variables, whose solution involved constructing and recompiling a C++ version of CLIPS. We are currently working on a more radical approach to incorporating CLIPS, by separating out its pattern matcher, rule and fact representations and other components as true object oriented modules.

Schultz, Roger D.↗