Results for “library design” — Page 9

NASA NTRS1985

Executive control systems in the engineering design environment

An executive control system (ECS) is a software structure for unifying various applications codes into a comprehensive system. It provides a library of applications, a uniform access method through a cental user interface, and a data management facility. A survey of twenty-four executive control systems designed to unify various CAD/CAE applications for use in diverse engineering design environments within government and industry was conducted. The goals of this research were to establish system requirements to survey state-of-the-art architectural design approaches, and to provide an overview of the historical evolution of these systems. Foundations for design are presented and include environmental settings, system requirements, major architectural components, and a system classification scheme based on knowledge of the supported engineering domain(s). An overview of the design approaches used in developing the major architectural components of an ECS is presented with examples taken from the surveyed systems. Attention is drawn to four major areas of ECS development: interdisciplinary usage; standardization; knowledge utilization; and computer science technology transfer.

Hurst, P. W.↗

NASA NTRS1986

Automated software development workstation

Engineering software development was automated using an expert system (rule-based) approach. The use of this technology offers benefits not available from current software development and maintenance methodologies. A workstation was built with a library or program data base with methods for browsing the designs stored; a system for graphical specification of designs including a capability for hierarchical refinement and definition in a graphical design system; and an automated code generation capability in FORTRAN. The workstation was then used in a demonstration with examples from an attitude control subsystem design for the space station. Documentation and recommendations are presented.

Source record↗

NASA NTRS1988

Input/Output Subroutine Library Program

Efficient, easy-to-use program moved easily to different computers. Purpose of NAVIO, Input/Output Subroutine Library, provides input/output package of software for FORTRAN programs that is portable, efficient, and easy to use. Implemented as hierarchy of libraries. At bottom is very small library containing only non-portable routines called "I/O Kernel." Design makes NAVIO easy to move from one computer to another, by simply changing kernel. NAVIO appropriate for software system of almost any size wherein different programs communicate through files.

Collier, James B.↗

NASA NTRS1989

General-Purpose Electronic System Tests Aircraft

Versatile digital equipment supports research, development, and maintenance. Extended aircraft interrogation and display system is general-purpose assembly of digital electronic equipment on ground for testing of digital electronic systems on advanced aircraft. Many advanced features, including multiple 16-bit microprocessors, pipeline data-flow architecture, advanced operating system, and resident software-development tools. Basic collection of software includes program for handling many types of data and for displays in various formats. User easily extends basic software library. Hardware and software interfaces to subsystems provided by user designed for flexibility in configuration to meet user's requirements.

Glover, Richard D.↗

NASA NTRSDate not supplied

The State of Cryptolib – The Open-Source Satellite Cryptography Library

What state would the world be in if all internet traffic was unencrypted? Imagine an alternate universe where you can plug a packet sniffing device into your home internet and capture the web traffic of the entire world. It seems obvious that this scenario is less than desirable. If we would not allow this for the internet, why would we allow this in the space domain? With the advent of open-source ground stations, commercial off the shelf hardware, and ground stations as a service, the barrier to entry for space communications is rapidly lowering. New players enter the space realm everydayevery day, and the presence of tools to allow apprentice evildoers the ability to exploit satellite communications is on the horizon. Not only are legacy missions at risk, but future missions are as well - particularly lower budget science missions with more stringent sciencesize, weight, and power constraints. that may find it difficult to utilize hardware-based encryption solutions. In terms of Civilian Aerospace, NASA Standard 1006 generally directs that missions "shall protect the command stack with encryption that meets or exceeds Federal Information Processing Standards (FIPS) 140". Fortunately, the Consultative Committee for Space Data Systems (CCSDS) has published an international standard on Space Data Link Security. The combination of these two forces has resulted in CryptoLib - an open-source, C-based, encryption library that aims to be CCSDS SDLS compliant. CryptoLib is designed to support smaller missions on a tight budget that may be subject to the more stringent command link encryption requirements. Additionally, CryptoLib serves as an underpinning in JPL's Key Management & Cryptography (KMC) suite and is also designed to function as a 'drop-in' for smaller missions. CryptoLib is in active development and currently provides Telecommand (TC), Telemetry (TM), and Advanced Orbiting Systems (AOS) encryption and decryption capabilities with a variety of encryption and authentication schemes. This presentation will report the latest features, current status, and future plans for CryptoLib.

open-source encryption↗

NASA NTRSDate not supplied

The State of CryptoLib – The Open-Source Satellite Cryptography Library

What state would the world be in if all internet traffic was unencrypted? Imagine an alternate universe where you can plug a packet sniffing device into your home internet and capture the web traffic of the entire world. It seems obvious that this scenario is less than desirable. If we would not allow this for the internet, why would we allow this in the space domain? With the advent of open-source ground stations, commercial off the shelf hardware, and ground stations as a service, the barrier to entry for space communications is rapidly lowering. New players enter the space realm everydayevery day, and the presence of tools to allow apprentice evildoers the ability to exploit satellite communications is on the horizon. Not only are legacy missions at risk, but future missions are as well - particularly lower budget science missions with more stringent sciencesize, weight, and power constraints. that may find it difficult to utilize hardware-based encryption solutions. In terms of Civilian Aerospace, NASA Standard 1006 generally directs that missions "shall protect the command stack with encryption that meets or exceeds Federal Information Processing Standards (FIPS) 140". Fortunately, the Consultative Committee for Space Data Systems (CCSDS) has published an international standard on Space Data Link Security. The combination of these two forces has resulted in CryptoLib - an open-source, C-based, encryption library that aims to be CCSDS SDLS compliant. CryptoLib is designed to support smaller missions on a tight budget that may be subject to the more stringent command link encryption requirements. Additionally, CryptoLib serves as an underpinning in JPL's Key Management & Cryptography (KMC) suite and is also designed to function as a 'drop-in' for smaller missions. CryptoLib is in active development and currently provides Telecommand (TC), Telemetry (TM), and Advanced Orbiting Systems (AOS) encryption and decryption capabilities with a variety of encryption and authentication schemes. This presentation will report the latest features, current status, and future plans for CryptoLib.

open-source encryption↗

NASA NTRS1994

A high-speed linear algebra library with automatic parallelism

Parallel or distributed processing is key to getting highest performance workstations. However, designing and implementing efficient parallel algorithms is difficult and error-prone. It is even more difficult to write code that is both portable to and efficient on many different computers. Finally, it is harder still to satisfy the above requirements and include the reliability and ease of use required of commercial software intended for use in a production environment. As a result, the application of parallel processing technology to commercial software has been extremely small even though there are numerous computationally demanding programs that would significantly benefit from application of parallel processing. This paper describes DSSLIB, which is a library of subroutines that perform many of the time-consuming computations in engineering and scientific software. DSSLIB combines the high efficiency and speed of parallel computation with a serial programming model that eliminates many undesirable side-effects of typical parallel code. The result is a simple way to incorporate the power of parallel processing into commercial software without compromising maintainability, reliability, or ease of use. This gives significant advantages over less powerful non-parallel entries in the market.

Boucher, Michael L.↗

NASA NTRS1989

Knowledge-based reusable software synthesis system

The Eli system, a knowledge-based reusable software synthesis system, is being developed for NASA Langley under a Phase 2 SBIR contract. Named after Eli Whitney, the inventor of interchangeable parts, Eli assists engineers of large-scale software systems in reusing components while they are composing their software specifications or designs. Eli will identify reuse potential, search for components, select component variants, and synthesize components into the developer's specifications. The Eli project began as a Phase 1 SBIR to define a reusable software synthesis methodology that integrates reusabilityinto the top-down development process and to develop an approach for an expert system to promote and accomplish reuse. The objectives of the Eli Phase 2 work are to integrate advanced technologies to automate the development of reusable components within the context of large system developments, to integrate with user development methodologies without significant changes in method or learning of special languages, and to make reuse the easiest operation to perform. Eli will try to address a number of reuse problems including developing software with reusable components, managing reusable components, identifying reusable components, and transitioning reuse technology. Eli is both a library facility for classifying, storing, and retrieving reusable components and a design environment that emphasizes, encourages, and supports reuse.

Donaldson, Cammie↗

NASA NTRS2004

Specification, Design, and Analysis of Advanced HUMS Architectures

During the two-year project period, we have worked on several aspects of domain-specific architectures for HUMS. In particular, we looked at using scenario-based approach for the design and designed a language for describing such architectures. The language is now being used in all aspects of our HUMS design. In particular, we have made contributions in the following areas. 1) We have employed scenarios in the development of HUMS in three main areas. They are: (a) To improve reusability by using scenarios as a library indexing tool and as a domain analysis tool; (b) To improve maintainability by recording design rationales from two perspectives - problem domain and solution domain; (c) To evaluate the software architecture. 2) We have defined a new architectural language called HADL or HUMS Architectural Definition Language. It is a customized version of xArch/xADL. It is based on XML and, hence, is easily portable from domain to domain, application to application, and machine to machine. Specifications written in HADL can be easily read and parsed using the currently available XML parsers. Thus, there is no need to develop a plethora of software to support HADL. 3) We have developed an automated design process that involves two main techniques: (a) Selection of solutions from a large space of designs; (b) Synthesis of designs. However, the automation process is not an absolute Artificial Intelligence (AI) approach though it uses a knowledge-based system that epitomizes a specific HUMS domain. The process uses a database of solutions as an aid to solve the problems rather than creating a new design in the literal sense. Since searching is adopted as the main technique, the challenges involved are: (a) To minimize the effort in searching the database where a very large number of possibilities exist; (b) To develop representations that could conveniently allow us to depict design knowledge evolved over many years; (c) To capture the required information that aid the automation process.

Mukkamala, Ravi↗

NASA NTRS2011

MicroShell Minimalist Shell for Xilinx Microprocessors

MicroShell is a lightweight shell environment for engineers and software developers working with embedded microprocessors in Xilinx FPGAs. (MicroShell has also been successfully ported to run on ARM Cortex-M1 microprocessors in Actel ProASIC3 FPGAs, but without project-integration support.) Micro Shell decreases the time spent performing initial tests of field-programmable gate array (FPGA) designs, simplifies running customizable one-time-only experiments, and provides a familiar-feeling command-line interface. The program comes with a collection of useful functions and enables the designer to add an unlimited number of custom commands, which are callable from the command-line. The commands are parameterizable (using the C-based command-line parameter idiom), so the designer can use one function to exercise hardware with different values. Also, since many hardware peripherals instantiated in FPGAs have reasonably simple register-mapped I/O interfaces, the engineer can edit and view hardware parameter settings at any time without stopping the processor. MicroShell comes with a set of support scripts that interface seamlessly with Xilinx's EDK tool. Adding an instance of MicroShell to a project is as simple as marking a check box in a library configuration dialog box and specifying a software project directory. The support scripts then examine the hardware design, build design-specific functions, conditionally include processor-specific functions, and complete the compilation process. For code-size constrained designs, most of the stock functionality can be excluded from the compiled library. When all of the configurable options are removed from the binary, MicroShell has an unoptimized memory footprint of about 4.8 kB and a size-optimized footprint of about 2.3 kB. Since MicroShell allows unfettered access to all processor-accessible memory locations, it is possible to perform live patching on a running system. This can be useful, for instance, if a bug is discovered in a routine but the system cannot be rebooted: Shell allows a skilled operator to directly edit the binary executable in memory. With some forethought, MicroShell code can be located in a different memory location from custom code, permitting the custom functionality to be overwritten at any time without stopping the controlling shell.

Werne, Thomas A.↗

NASA NTRSDate not supplied

Quantifying Medical Risk on a Long Duration Lunar Mission: A Demonstration of NASA’s IMPACT Tradespace Analysis Tool

Background NASA’s human exploration spaceflight missions to the Moon and Mars present unprecedented challenges for in-mission medical care. The distance from Earth will mean increased mission durations, communication delays, limited to no resupply opportunities, and constraints on the medical evacuation of astronauts. Mass, volume, power, and data will be limited while higher demands will be placed on the crew to manage medical care. NASA’s Moon to Mars exploration strategy lays out increasingly complex Artemis missions both in terms of duration and operations. In these more challenging deep space missions, it is important to quantitatively estimate the human medical risk to inform a traditional heuristic approach to medical risk. Prior tools have been developed for missions in low Earth orbit, but a new tool is required to plan for future exploration missions. Methods IMPACT (Informing Mission Planning via Analysis of Complex Tradespaces) is a risk assessment tool developed by NASA to advance exploration mission medical system design by quantitatively estimating mission medical risk. IMPACT v1.0 includes a novel evidence library baselined to exploration environments; an expanded list of 119 medical conditions; the addition of medical resources; and the ability for rapid and iterative analysis. Medical system risk estimates include loss of crew life, consideration of the need for return to definitive care (medical evacuation), and an estimate of crew time affected due to medical conditions. A notional long duration lunar orbit and lunar surface design reference mission (DRM) was chosen with a 4-astronaut crew to represent a sustained exploration Artemis mission. Results/Discussion Overall, IMPACT successfully quantified medical risk and derived an optimized medical system to support crew on a long duration lunar mission. In this DRM, the calculated loss of crew life from a medical event was 0.008 events per mission, risk of potential need for evacuation was 0.30 events per mission, and cumulative crew time affected by medical conditions was 103 days. The medical conditions that most contributed to overall medical risk were decompression sickness, trauma conditions, and respiratory failure. The conditions that had the largest effects on crew performance included musculoskeletal injuries and lunar dust exposure. The IMPACT-generated medical system included resources that target the most common and highest risk conditions. This systematic analysis demonstrates the value of the IMPACT tool in medical system design for human exploration spaceflight missions.

Missions to Mars↗

NASA NTRS2024

Quantifying Medical Risk on a Long Duration Lunar Mission: A Demonstration of NASA’s IMPACT Tradespace Analysis Tool

Background NASA’s human exploration spaceflight missions to the Moon and Mars present unprecedented challenges for in-mission medical care. The distance from Earth will mean increased mission durations, communication delays, limited to no resupply opportunities, and constraints on the medical evacuation of astronauts. Mass, volume, power, and data will be limited while higher demands will be placed on the crew to manage medical care. NASA’s Moon to Mars exploration strategy lays out increasingly complex Artemis missions both in terms of duration and operations. In these more challenging deep space missions, it is important to quantitatively estimate the human medical risk to inform a traditional heuristic approach to medical risk. Prior tools have been developed for missions in low Earth orbit, but a new tool is required to plan for future exploration missions. Methods IMPACT (Informing Mission Planning via Analysis of Complex Tradespaces) is a risk assessment tool developed by NASA to advance exploration mission medical system design by quantitatively estimating mission medical risk. IMPACT v1.0 includes a novel evidence library baselined to exploration environments; an expanded list of 119 medical conditions; the addition of medical resources; and the ability for rapid and iterative analysis. Medical system risk estimates include loss of crew life, consideration of the need for return to definitive care (medical evacuation), and an estimate of crew time affected due to medical conditions. A notional long duration lunar orbit and lunar surface design reference mission (DRM) was chosen with a 4-astronaut crew to represent a sustained exploration Artemis mission. Results/Discussion Overall, IMPACT successfully quantified medical risk and derived an optimized medical system to support crew on a long duration lunar mission. In this DRM, the calculated loss of crew life from a medical event was 0.008 events per mission, risk of potential need for evacuation was 0.30 events per mission, and cumulative crew time affected by medical conditions was 103 days. The medical conditions that most contributed to overall medical risk were decompression sickness, trauma conditions, and respiratory failure. The conditions that had the largest effects on crew performance included musculoskeletal injuries and lunar dust exposure. The IMPACT-generated medical system included resources that target the most common and highest risk conditions. This systematic analysis demonstrates the value of the IMPACT tool in medical system design for human exploration spaceflight missions.

Missions to Mars↗

NASA NTRS1990

NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 5: Aerospace librarians and technical information specialists as information intermediaries: A report of phase 2 activities of the NASA/DOD Aerospace Knowledge Diffusion Research Project

The objective of the NASA/DOD Aerospace Knowledge Diffusion Research Project is to provide descriptive and analytical data regarding the flow of scientific and technical information (STI) at the individual, organizational, national, and international levels, placing emphasis on the systems used to diffuse the results of federally funded aerospace STI. An overview of project assumptions, objectives, and design is presented and preliminary results of the phase 2 aerospace library survey are summarized. Phase 2 addressed aerospace knowledge transfer and use within the larger social system and focused on the flow of aerospace STI in government and industry and the role of the information intermediary in knowledge transfer.

Pinelli, Thomas E.↗

NASA NTRS2000

Molecular cloning and characterization of a tomato cDNA encoding a systemically wound-inducible bZIP DNA-binding protein

Localized wounding of one leaf in intact tomato (Lycopersicon esculentum Mill.) plants triggers rapid systemic transcriptional responses that might be involved in defense. To better understand the mechanism(s) of intercellular signal transmission in wounded tomatoes, and to identify the array of genes systemically up-regulated by wounding, a subtractive cDNA library for wounded tomato leaves was constructed. A novel cDNA clone (designated LebZIP1) encoding a DNA-binding protein was isolated and identified. This clone appears to be encoded by a single gene, and belongs to the family of basic leucine zipper domain (bZIP) transcription factors shown to be up-regulated by cold and dark treatments. Analysis of the mRNA levels suggests that the transcript for LebZIP1 is both organ-specific and up-regulated by wounding. In wounded wild-type tomatoes, the LebZIP1 mRNA levels in distant tissue were maximally up-regulated within only 5 min following localized wounding. Exogenous abscisic acid (ABA) prevented the rapid wound-induced increase in LebZIP1 mRNA levels, while the basal levels of LebZIP1 transcripts were higher in the ABA mutants notabilis (not), sitiens (sit), and flacca (flc), and wound-induced increases were greater in the ABA-deficient mutants. Together, these results suggest that ABA acts to curtail the wound-induced synthesis of LebZIP1 mRNA.

Non-NASA Center↗

NASA NTRS2014

All-Digital Baseband 65nm PLL/FPLL Clock Multiplier using 10-cell Library

PLLs for clock generation are essential for modern circuits, to generate specialized frequencies for many interfaces and high frequencies for chip internal operation. These circuits depend on analog circuits and careful tailoring for each new process, and making them fault tolerant is an incompletely solved problem. Until now, all digital PLLs have been restricted to sampled data DSP techniques and not available for the highest frequency baseband applications. This paper presents the design and preliminary evaluation of an all-digital baseband technique built entirely with an easily portable 10-cell digital library. The library is also described, as it aids in research and low volume design porting to new processes. The advantages of the digital approach are the wide variety of techniques available to give varying degrees of fault tolerance, and the simplicity of porting the design to new processes, even to exotic processes that may not have analog capability. The only tuning parameter is digital gate delay. An all-digital approach presents unique problems and standard analog loop stability design criteria cannot be directly used. Because of the quantization of frequency, there is effectively infinite gain for very small loop error feedback. The numerically controlled oscillator (NCO) based on a tapped delay line cannot be reliably updated while a pulse is active in the delay line, and ordinarily does not have enough frequency resolution for a low-jitter output.

Shuler, Robert L., Jr.↗

NASA NTRS2014

ALL-Digital Baseband 65nm PLL/FPLL Clock Multiplier Using 10-Cell Library

PLLs for clock generation are essential for modern circuits, to generate specialized frequencies for many interfaces and high frequencies for chip internal operation. These circuits depend on analog circuits and careful tailoring for each new process, and making them fault tolerant is an incompletely solved problem. Until now, all digital PLLs have been restricted to sampled data DSP techniques and not available for the highest frequency baseband applications. This paper presents the design and preliminary evaluation of an all-digital baseband technique built entirely with an easily portable 10-cell digital library. The library is also described, as it aids in research and low volume design porting to new processes. The advantages of the digital approach are the wide variety of techniques available to give varying degrees of fault tolerance, and the simplicity of porting the design to new processes, even to exotic processes that may not have analog capability. The only tuning parameter is digital gate delay. An all-digital approach presents unique problems and standard analog loop stability design criteria cannot be directly used. Because of the quantization of frequency, there is effectively infinite gain for very small loop error feedback. The numerically controlled oscillator (NCO) based on a tapped delay line cannot be reliably updated while a pulse is active in the delay line, and ordinarily does not have enough frequency resolution for a low-jitter output.

Schuler, Robert L., Jr.↗

NASA NTRS2005

Range Process Simulation Tool

Range Process Simulation Tool (RPST) is a computer program that assists managers in rapidly predicting and quantitatively assessing the operational effects of proposed technological additions to, and/or upgrades of, complex facilities and engineering systems such as the Eastern Test Range. Originally designed for application to space transportation systems, RPST is also suitable for assessing effects of proposed changes in industrial facilities and large organizations. RPST follows a model-based approach that includes finite-capacity schedule analysis and discrete-event process simulation. A component-based, scalable, open architecture makes RPST easily and rapidly tailorable for diverse applications. Specific RPST functions include: (1) definition of analysis objectives and performance metrics; (2) selection of process templates from a processtemplate library; (3) configuration of process models for detailed simulation and schedule analysis; (4) design of operations- analysis experiments; (5) schedule and simulation-based process analysis; and (6) optimization of performance by use of genetic algorithms and simulated annealing. The main benefits afforded by RPST are provision of information that can be used to reduce costs of operation and maintenance, and the capability for affordable, accurate, and reliable prediction and exploration of the consequences of many alternative proposed decisions.

Phillips, Dave↗

NASA NTRS1997

Fundamental Hardware Design in PVS

The development of Programmable Logic Devices (PLDs) has introduced programming as a primary tool in the development of digital circuits. This work attempts to create a generic verification environment in which designs can be specified and verified using the Prototype Verification System (PVS). This is accomplished by providing library support for general hardware constructs. The environment is intended for use with any PLD and any PLD programming language. The goal of the environment is to allow the easy translation of digital designs to PVS and provide sufficient support to make verification possible without a great deal of effort.

Leathrum, James F., Jr.↗