Search NASA⌕ Search

SEARCH · Search NASA

Results for “database”

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
All sourcesNASA NTRSDOE OSTI
NASA NTRS1991

VIEWCACHE: An incremental database access method for autonomous interoperable databases

The objective is to illustrate the concept of incremental access to distributed databases. An experimental database management system, ADMS, which has been developed at the University of Maryland, in College Park, uses VIEWCACHE, a database access method based on incremental search. VIEWCACHE is a pointer-based access method that provides a uniform interface for accessing distributed databases and catalogues. The compactness of the pointer structures formed during database browsing and the incremental access method allow the user to search and do inter-database cross-referencing with no actual data movement between database sites. Once the search is complete, the set of collected pointers pointing to the desired data are dereferenced.

Roussopoulos, Nick↗
NASA NTRS2023

Exploration Medical Capability IMPACT Medical Database – Medical Item Database (MedID) Content Development Methods

The Informing Mission Planning via Analysis of Complex Tradespaces (IMPACT) project encompasses a suite of computational tools that are used to inform systematic trade study evaluations and research prioritizations regarding the optimization of spaceflight medical systems, including the provision of risk assessment metrics, for a given design reference mission (DRM). The IMPACT Medical Database (IMPACT-MD) is the component that virtually houses the clinical and engineering data for medical conditions, capabilities, and resources used to support these analyses. In addition, IMPACT-MD also provides data to the associated SysML model to support the Level 2, Level 3, and Level 4 requirements development needed for IMPACT. IMPACT-MD contains an internal Evidence Library (EL) sub-component that hosts the clinical evidence, treatment and outcome metric data, and incidence data for each medical condition identified for exploration-class missions. Furthermore, a separate Medical Item Database (MedID) sub-component hosts the engineering data and physical attributes (e.g., mass, volume, power, etc.) associated with each medical resource item identified to address the requisite medical conditions. The IMPACT project is conducted under the Exploration Medical Capability (ExMC) element of the Human Research Program (HRP) within NASA's Space Operations Mission Directorate (SOMD). The reader is referred to the documents in Appendix A for a more complete overview of the IMPACT tool suite and functionality as well as further detail on any associated aspects of the project. The primary purpose of this document is to describe the methods utilized in the collection and verification of engineering data content during the project development phase for the MedID sub-component of the IMPACT-MD project. Engineering content data (both existing and new/future) will be stored in IMPACT-MD for use by the IMPACT project. This document will detail the content development and data credibility for the engineering data housed within the MedID subcomponent of IMPACT-MD, which is used to inform the IMPACT 1.0 project deliverables.

Exploration Medical Capability↗
NASA NTRS1992

NASA STI Database, Aerospace Database and ARIN coverage of 'space law'

The space-law coverage provided by the NASA STI Database, the Aerospace Database, and ARIN is briefly described. Particular attention is given to the space law content of the two Databases and of ARIN, the NASA Thesauras space law terminology, space law publication forms, and the availability of the space law literature.

Buchan, Ronald L.↗
NASA NTRS1994

An incremental database access method for autonomous interoperable databases

We investigated a number of design and performance issues of interoperable database management systems (DBMS's). The major results of our investigation were obtained in the areas of client-server database architectures for heterogeneous DBMS's, incremental computation models, buffer management techniques, and query optimization. We finished a prototype of an advanced client-server workstation-based DBMS which allows access to multiple heterogeneous commercial DBMS's. Experiments and simulations were then run to compare its performance with the standard client-server architectures. The focus of this research was on adaptive optimization methods of heterogeneous database systems. Adaptive buffer management accounts for the random and object-oriented access methods for which no known characterization of the access patterns exists. Adaptive query optimization means that value distributions and selectives, which play the most significant role in query plan evaluation, are continuously refined to reflect the actual values as opposed to static ones that are computed off-line. Query feedback is a concept that was first introduced to the literature by our group. We employed query feedback for both adaptive buffer management and for computing value distributions and selectivities. For adaptive buffer management, we use the page faults of prior executions to achieve more 'informed' management decisions. For the estimation of the distributions of the selectivities, we use curve-fitting techniques, such as least squares and splines, for regressing on these values.

Roussopoulos, Nicholas↗
NASA NTRS1988

Resident database interfaces to the DAVID system, a heterogeneous distributed database management system

A methodology for building interfaces of resident database management systems to a heterogeneous distributed database management system under development at NASA, the DAVID system, was developed. The feasibility of that methodology was demonstrated by construction of the software necessary to perform the interface task. The interface terminology developed in the course of this research is presented. The work performed and the results are summarized.

Moroh, Marsha↗
NASA NTRS2001

'The surface management system' (SuMS) database: a surface-based database to aid cortical surface reconstruction, visualization and analysis

Surface reconstructions of the cerebral cortex are increasingly widely used in the analysis and visualization of cortical structure, function and connectivity. From a neuroinformatics perspective, dealing with surface-related data poses a number of challenges. These include the multiplicity of configurations in which surfaces are routinely viewed (e.g. inflated maps, spheres and flat maps), plus the diversity of experimental data that can be represented on any given surface. To address these challenges, we have developed a surface management system (SuMS) that allows automated storage and retrieval of complex surface-related datasets. SuMS provides a systematic framework for the classification, storage and retrieval of many types of surface-related data and associated volume data. Within this classification framework, it serves as a version-control system capable of handling large numbers of surface and volume datasets. With built-in database management system support, SuMS provides rapid search and retrieval capabilities across all the datasets, while also incorporating multiple security levels to regulate access. SuMS is implemented in Java and can be accessed via a Web interface (WebSuMS) or using downloaded client software. Thus, SuMS is well positioned to act as a multiplatform, multi-user 'surface request broker' for the neuroscience community.

NASA Discipline Neuroscience↗
NASA NTRS1986

Database interfaces on NASA's heterogeneous distributed database system

The purpose of the ORACLE interface is to enable the DAVID program to submit queries and transactions to databases running under the ORACLE DBMS. The interface package is made up of several modules. The progress of these modules is described below. The two approaches used in implementing the interface are also discussed. Detailed discussion of the design of the templates is shown and concluding remarks are presented.

Huang, S. H. S.↗
NASA NTRS1987

Database interfaces on NASA's heterogeneous distributed database system

The purpose of Distributed Access View Integrated Database (DAVID) interface module (Module 9: Resident Primitive Processing Package) is to provide data transfer between local DAVID systems and resident Data Base Management Systems (DBMSs). The result of current research is summarized. A detailed description of the interface module is provided. Several Pascal templates were constructed. The Resident Processor program was also developed. Even though it is designed for the Pascal templates, it can be modified for templates in other languages, such as C, without much difficulty. The Resident Processor itself can be written in any programming language. Since Module 5 routines are not ready yet, there is no way to test the interface module. However, simulation shows that the data base access programs produced by the Resident Processor do work according to the specifications.

Huang, Shou-Hsuan Stephen↗
NASA NTRS1988

The development of an Ada programming support environment database: SEAD (Software Engineering and Ada Database), user's manual

This is a manual for users of the Software Engineering and Ada Database (SEAD). SEAD was developed to provide an information resource to NASA and NASA contractors with respect to Ada-based resources and activities that are available or underway either in NASA or elsewhere in the worldwide Ada community. The sharing of such information will reduce the duplication of effort while improving quality in the development of future software systems. The manual describes the organization of the data in SEAD, the user interface from logging in to logging out, and concludes with a ten chapter tutorial on how to use the information in SEAD. Two appendices provide quick reference for logging into SEAD and using the keyboard of an IBM 3270 or VT100 computer terminal.

Liaw, Morris↗
NASA NTRS1988

Development of an Ada programming support environment database SEAD (Software Engineering and Ada Database) administration manual

Software Engineering and Ada Database (SEAD) was developed to provide an information resource to NASA and NASA contractors with respect to Ada-based resources and activities which are available or underway either in NASA or elsewhere in the worldwide Ada community. The sharing of such information will reduce duplication of effort while improving quality in the development of future software systems. SEAD data is organized into five major areas: information regarding education and training resources which are relevant to the life cycle of Ada-based software engineering projects such as those in the Space Station program; research publications relevant to NASA projects such as the Space Station Program and conferences relating to Ada technology; the latest progress reports on Ada projects completed or in progress both within NASA and throughout the free world; Ada compilers and other commercial products that support Ada software development; and reusable Ada components generated both within NASA and from elsewhere in the free world. This classified listing of reusable components shall include descriptions of tools, libraries, and other components of interest to NASA. Sources for the data include technical newletters and periodicals, conference proceedings, the Ada Information Clearinghouse, product vendors, and project sponsors and contractors.

Liaw, Morris↗
NASA NTRS1989

Database interfaces on NASA's heterogeneous distributed database system

The syntax and semantics of all commands used in the template are described. Template builders should consult this document for proper commands in the template. Previous documents (Semiannual reports) described other aspects of this project. Appendix 1 contains all substituting commands used in the system. Appendix 2 includes all repeating commands. Appendix 3 is a collection of DEFINE templates from eight different DBMS's.

Huang, Shou-Hsuan Stephen↗
NASA NTRS1992

Profile of a cell test database and a corresponding reliability database

The development of computerized control, and data retrieval for aerospace cell testing affords an excellent opportunity to incorporate three specific concepts to both manage the test area and to track product performance on a real-time basis. The adoption and incorporation of precepts fostered by this total quality management (TQM) initiative are critical to us for retaining control of our business while substantially reducing the separate quality control inspection activity. Test discrepancies are all 'equally bad' in cell acceptance testing because, for example, we presently do not discriminate between 1 or 25 mV for an overvoltage condition. We must take leadership in classifying such discrepancies in order to expedite their clearance and redirect our resources for prevention activities. The development and use of engineering alerts (or guardbanding) which more closely match our product capabilities and are toleranced tighter than the required customer specification are paramount to managing the test unit in order to remain both quality and cost effective.

Brearley, George R.↗
NASA NTRS2013

Elastic-Plastic J-Integral Solutions or Surface Cracks in Tension Using an Interpolation Methodology. Appendix C -- Finite Element Models Solution Database File, Appendix D -- Benchmark Finite Element Models Solution Database File

No closed form solutions exist for the elastic-plastic J-integral for surface cracks due to the nonlinear, three-dimensional nature of the problem. Traditionally, each surface crack must be analyzed with a unique and time-consuming nonlinear finite element analysis. To overcome this shortcoming, the authors have developed and analyzed an array of 600 3D nonlinear finite element models for surface cracks in flat plates under tension loading. The solution space covers a wide range of crack shapes and depths (shape: 0.2 less than or equal to a/c less than or equal to 1, depth: 0.2 less than or equal to a/B less than or equal to 0.8) and material flow properties (elastic modulus-to-yield ratio: 100 less than or equal to E/ys less than or equal to 1,000, and hardening: 3 less than or equal to n less than or equal to 20). The authors have developed a methodology for interpolating between the goemetric and material property variables that allows the user to reliably evaluate the full elastic-plastic J-integral and force versus crack mouth opening displacement solution; thus, a solution can be obtained very rapidly by users without elastic-plastic fracture mechanics modeling experience. Complete solutions for the 600 models and 25 additional benchmark models are provided in tabular format.

Allen, Phillip A.↗
NASA NTRS2017

Mars Phoenix Scout Thermal Evolved Gas Analyzer (TEGA) Database: Thermal Database Development and Analysis

The Mars Phoenix Scout Lander mission in 2008 examined the history of water, searched for organics, and evaluated the potential for past/present microbial habitability in a martian arctic ice-rich soil [1]. The Thermal Evolved Gas Analyzer (TEGA) instrument measured the isotopic composition of atmospheric CO2 and detected volatile bearing mineralogy (perchlorate, carbonate, hydrated mineral phases) in the martian soil [2-7]. The TEGA data are archived at the Planetary Data System (PDS) Geosciences Node but are reported in forms that require further processing to be of use to the non-TEGA expert. The soil and blank TEGA thermal data are reported as duty cycle and must be converted to differential power (mW) to allow for enthalpy calculations of exothermic/endothermic transitions. The exothermic/endothermic temperatures are also used to determine what phases (inorganic/organic) are present in the sample. The objectives of this work are to: 1) Describe how interpretable thermal data can be created from TEGA data sets on the PDS and 2) Provide additional thermal data interpretation of two Phoenix soils (Baby Bear, Wicked Witch) and include interpretations from three unreported soils (Rosy Red 1, 2, and Burning Coals).

Sutter, B.↗
NASA NTRS2003

XML: James Webb Space Telescope Database Issues, Lessons, and Status

This paper will present the current concept using extensible Markup Language (XML) as the underlying structure for the James Webb Space Telescope (JWST) database. The purpose of using XML is to provide a JWST database, independent of any portion of the ground system, yet still compatible with the various systems using a variety of different structures. The testing of the JWST Flight Software (FSW) started in 2002, yet the launch is scheduled for 2011 with a planned 5-year mission and a 5-year follow on option. The initial database and ground system elements, including the commands, telemetry, and ground system tools will be used for 19 years, plus post mission activities. During the Integration and Test (I&T) phases of the JWST development, 24 distinct laboratories, each geographically dispersed, will have local database tools with an XML database. Each of these laboratories database tools will be used for the exporting and importing of data both locally and to a central database system, inputting data to the database certification process, and providing various reports. A centralized certified database repository will be maintained by the Space Telescope Science Institute (STScI), in Baltimore, Maryland, USA. One of the challenges for the database is to be flexible enough to allow for the upgrade, addition or changing of individual items without effecting the entire ground system. Also, using XML should allow for the altering of the import and export formats needed by the various elements, tracking the verification/validation of each database item, allow many organizations to provide database inputs, and the merging of the many existing database processes into one central database structure throughout the JWST program. Many National Aeronautics and Space Administration (NASA) projects have attempted to take advantage of open source and commercial technology. Often this causes a greater reliance on the use of Commercial-Off-The-Shelf (COTS), which is often limiting. In our review of the database requirements and the COTS software available, only very expensive COTS software will meet 90% of requirements. Even with the high projected initial cost of COTS, the development and support for custom code over the 19-year mission period was forecasted to be higher than the total licensing costs. A group did look at reusing existing database tools and formats. If the JWST database was already in a mature state, the reuse made sense, but with the database still needing to handing the addition of different types of command and telemetry structures, defining new spacecraft systems, accept input and export to systems which has not been defined yet, XML provided the flexibility desired. It remains to be determined whether the XML database will reduce the over all cost for the JWST mission.

Detter, Ryan↗
NASA NTRS2005

James Webb Space Telescope XML Database: From the Beginning to Today

The James Webb Space Telescope (JWST) Project has been defining, developing, and exercising the use of a common eXtensible Markup Language (XML) for the command and telemetry (C&T) database structure. JWST is the first large NASA space mission to use XML for databases. The JWST project started developing the concepts for the C&T database in 2002. The database will need to last at least 20 years since it will be used beginning with flight software development, continuing through Observatory integration and test (I&T) and through operations. Also, a database tool kit has been provided to the 18 various flight software development laboratories located in the United States, Europe, and Canada that allows the local users to create their own databases. Recently the JWST Project has been working with the Jet Propulsion Laboratory (JPL) and Object Management Group (OMG) XML Telemetry and Command Exchange (XTCE) personnel to provide all the information needed by JWST and JPL for exchanging database information using a XML standard structure. The lack of standardization requires custom ingest scripts for each ground system segment, increasing the cost of the total system. Providing a non-proprietary standard of the telemetry and command database definition formation will allow dissimilar systems to communicate without the need for expensive mission specific database tools and testing of the systems after the database translation. The various ground system components that would benefit from a standardized database are the telemetry and command systems, archives, simulators, and trending tools. JWST has exchanged the XML database with the Eclipse, EPOCH, ASIST ground systems, Portable spacecraft simulator (PSS), a front-end system, and Integrated Trending and Plotting System (ITPS) successfully. This paper will discuss how JWST decided to use XML, the barriers to a new concept, experiences utilizing the XML structure, exchanging databases with other users, and issues that have been experienced in creating databases for the C&T system.

Gal-Edd, Jonathan↗