Search NASA⌕ Search

SEARCH · Search NASA

Results for “ORACLES”

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 145 records · Page 8

National launch strategy vehicle data management system

The national launch strategy vehicle data management system (NLS/VDMS) was developed as part of the 1990 NASA Summer Faculty Fellowship Program. The system was developed under the guidance of the Engineering Systems Branch of the Information Systems Office, and is intended for use within the Program Development Branch PD34. The NLS/VDMS is an on-line database system that permits the tracking of various launch vehicle configurations within the program development office. The system is designed to permit the definition of new launch vehicles, as well as the ability to display and edit existing launch vehicles. Vehicles can be grouped in logical architectures within the system. Reports generated from this package include vehicle data sheets, architecture data sheets, and vehicle flight rate reports. The topics covered include: (1) system overview; (2) initial system development; (3) supercard hypermedia authoring system; (4) the ORACLE database; and (5) system evaluation.

Cordes, David↗

Expert system decision support for low-cost launch vehicle operations

Progress in assessing the feasibility, benefits, and risks associated with AI expert systems applied to low cost expendable launch vehicle systems is described. Part one identified potential application areas in vehicle operations and on-board functions, assessed measures of cost benefit, and identified key technologies to aid in the implementation of decision support systems in this environment. Part two of the program began the development of prototypes to demonstrate real-time vehicle checkout with controller and diagnostic/analysis intelligent systems and to gather true measures of cost savings vs. conventional software, verification and validation requirements, and maintainability improvement. The main objective of the expert advanced development projects was to provide a robust intelligent system for control/analysis that must be performed within a specified real-time window in order to meet the demands of the given application. The efforts to develop the two prototypes are described. Prime emphasis was on a controller expert system to show real-time performance in a cryogenic propellant loading application and safety validation implementation of this system experimentally, using commercial-off-the-shelf software tools and object oriented programming techniques. This smart ground support equipment prototype is based in C with imbedded expert system rules written in the CLIPS protocol. The relational database, ORACLE, provides non-real-time data support. The second demonstration develops the vehicle/ground intelligent automation concept, from phase one, to show cooperation between multiple expert systems. This automated test conductor (ATC) prototype utilizes a knowledge-bus approach for intelligent information processing by use of virtual sensors and blackboards to solve complex problems. It incorporates distributed processing of real-time data and object-oriented techniques for command, configuration control, and auto-code generation.

Szatkowski, G. P.↗

Performance related issues in distributed database systems

The key elements of research performed during the year long effort of this project are: Investigate the effects of heterogeneity in distributed real time systems; Study the requirements to TRAC towards building a heterogeneous database system; Study the effects of performance modeling on distributed database performance; and Experiment with an ORACLE based heterogeneous system.

Mukkamala, Ravi↗

Heterogeneous distributed databases: A case study

Alternatives are reviewed for accessing distributed heterogeneous databases and a recommended solution is proposed. The current study is limited to the Automated Information Systems Center at the Naval Sea Combat Systems Engineering Station at Norfolk, VA. This center maintains two databases located on Digital Equipment Corporation's VAX computers running under the VMS operating system. The first data base, ICMS, resides on a VAX11/780 and has been implemented using VAX DBMS, a CODASYL based system. The second database, CSA, resides on a VAX 6460 and has been implemented using the ORACLE relational database management system (RDBMS). Both databases are used for configuration management within the U.S. Navy. Different customer bases are supported by each database. ICMS tracks U.S. Navy ships and major systems (anti-sub, sonar, etc.). Even though the major systems on ships and submarines have totally different functions, some of the equipment within the major systems are common to both ships and submarines.

Stewart, Tracy R.↗

Technical Requirements Analysis and Control Systems (TRACS) Initial Operating Capability (IOC) documentation

The Technical Requirements Analysis and Control Systems (TRACS) software package is described. TRACS offers supplemental tools for the analysis, control, and interchange of project requirements. This package provides the fundamental capability to analyze and control requirements, serves a focal point for project requirements, and integrates a system that supports efficient and consistent operations. TRACS uses relational data base technology (ORACLE) in a stand alone or in a distributed environment that can be used to coordinate the activities required to support a project through its entire life cycle. TRACS uses a set of keyword and mouse driven screens (HyperCard) which imposes adherence through a controlled user interface. The user interface provides an interactive capability to interrogate the data base and to display or print project requirement information. TRACS has a limited report capability, but can be extended with PostScript conventions.

Hammond, Dana P.↗

Space Station Freedom environmental database system (FEDS) for MSFC testing

The Water Recovery Test (WRT) at Marshall Space Flight Center (MSFC) is the first demonstration of integrated water recovery systems for potable and hygiene water reuse as envisioned for Space Station Freedom (SSF). In order to satisfy the safety and health requirements placed on the SSF program and facilitate test data assessment, an extensive laboratory analysis database was established to provide a central archive and data retrieval function. The database is required to store analysis results for physical, chemical, and microbial parameters measured from water, air and surface samples collected at various locations throughout the test facility. The Oracle Relational Database Management System (RDBMS) was utilized to implement a secured on-line information system with the ECLSS WRT program as the foundation for this system. The database is supported on a VAX/VMS 8810 series mainframe and is accessible from the Marshall Information Network System (MINS). This paper summarizes the database requirements, system design, interfaces, and future enhancements.

Story, Gail S.↗

Managing Information On Technical Requirements

Technical Requirements Analysis and Control Systems/Initial Operating Capability (TRACS/IOC) computer program provides supplemental software tools for analysis, control, and interchange of project requirements so qualified project members have access to pertinent project information, even if in different locations. Enables users to analyze and control requirements, serves as focal point for project requirements, and integrates system supporting efficient and consistent operations. TRACS/IOC is HyperCard stack for use on Macintosh computers running HyperCard 1.2 or later and Oracle 1.2 or later.

Mauldin, Lemuel E., III↗

Software Engineering Laboratory (SEL) database organization and user's guide, revision 2

The organization of the Software Engineering Laboratory (SEL) database is presented. Included are definitions and detailed descriptions of the database tables and views, the SEL data, and system support data. The mapping from the SEL and system support data to the base table is described. In addition, techniques for accessing the database through the Database Access Manager for the SEL (DAMSEL) system and via the ORACLE structured query language (SQL) are discussed.

Morusiewicz, Linda↗

RBSE: Product development team research activity deliverables

The GHG Functions and Extensions to be added to the NASA Electronic Library System (NELS) 1.1 product are described. These functions will implement the 'output request' capability within the Object Browser. The functions will be implemented in two parts. The first part is a code to be added to the Object Browser (X version) to implement menus allowing the user to request that objects be copied to specific media, or that objects be downloaded to the user's system following a specific protocol, or that the object be printed to one of the printers attached to the host system. The second part is shell scripts which support the various menu selections. Additional scripts to support functions within the GHG shell (X version) will also be created along with the X version of the GHG Shell as initial capability for the 27 Mar. prototype. The scripts will be composed of C shell routines that will accept parameters (primary file pathways). Certain limitations in functionality will invoke Mail instead of Oracle Mail since that has yet to be delivered and the NELS invocation will default to the X-Windows version instead of the ASCII version.

Source record↗

NASA Electronic Library System (NELS) optimization

This is a compilation of NELS (NASA Electronic Library System) Optimization progress/problem, interim, and final reports for all phases. The NELS database was examined, particularly in the memory, disk contention, and CPU, to discover bottlenecks. Methods to increase the speed of NELS code were investigated. The tasks included restructuring the existing code to interact with others more effectively. An error reporting code to help detect and remove bugs in the NELS was added. Report writing tools were recommended to integrate with the ASV3 system. The Oracle database management system and tools were to be installed on a Sun workstation, intended for demonstration purposes.

Pribyl, William L.↗

Queries for Bias Testing

Selecting a good bias prior to concept learning can be difficult. Therefore, dynamic bias adjustment is becoming increasingly popular. Current dynamic bias adjustment systems, however, are limited in their ability to identify erroneous assumptions about the relationship between the bias and the target concept. Without proper diagnosis, it is difficult to identify and then remedy faulty assumptions. We have developed an approach that makes these assumptions explicit, actively tests them with queries to an oracle, and adjusts the bias based on the test results.

Gordon, Diana F.↗

User's Manual for the Naval Interactive Data Analysis System-Climatologies (NIDAS-C), Version 2.0

This technical note provides the user's manual for the NIDAS-C system developed for the naval oceanographic office. NIDAS-C operates using numerous oceanographic data categories stored in an installed version of the Naval Environmental Operational Nowcast System (NEONS), a relational database management system (rdbms) which employs the ORACLE proprietary rdbms engine. Data management, configuration, and control functions for the supporting rdbms are performed externally. NIDAS-C stores and retrieves data to/from the rdbms but exercises no direct internal control over the rdbms or its configuration. Data is also ingested into the rdbms, for use by NIDAS-C, by external data acquisition processes. The data categories employed by NIDAS-C are as follows: Bathymetry - ocean depth at

USER M ANUALS↗

Prototype and Evaluation of AutoHelp: A Case-based, Web-accessible Help Desk System for EOSDIS

AutoHelp is a case-based, Web-accessible help desk for users of the EOSDIS. Its uses a combination of advanced computer and Web technologies, knowledge-based systems tools, and cognitive engineering to offload the current, person-intensive, help desk facilities at the DAACs. As a case-based system, AutoHelp starts with an organized database of previous help requests (questions and answers) indexed by a hierarchical category structure that facilitates recognition by persons seeking assistance. As an initial proof-of-concept demonstration, a month of email help requests to the Goddard DAAC were analyzed and partially organized into help request cases. These cases were then categorized to create a preliminary case indexing system, or category structure. This category structure allows potential users to identify or recognize categories of questions, responses, and sample cases similar to their needs. Year one of this research project focused on the development of a technology demonstration. User assistance 'cases' are stored in an Oracle database in a combination of tables linking prototypical questions with responses and detailed examples from the email help requests analyzed to date. When a potential user accesses the AutoHelp system, a Web server provides a Java applet that displays the category structure of the help case base organized by the needs of previous users. When the user identifies or requests a particular type of assistance, the applet uses Java database connectivity (JDBC) software to access the database and extract the relevant cases. The demonstration will include an on-line presentation of how AutoHelp is currently structured. We will show how a user might request assistance via the Web interface and how the AutoHelp case base provides assistance. The presentation will describe the DAAC data collection, case definition, and organization to date, as well as the AutoHelp architecture. It will conclude with the year 2 proposal to more fully develop the case base, the user interface (including the category structure), interface with the current DAAC Help System, the development of tools to add new cases, and user testing and evaluation at (perhaps) the Goddard DAAC.

Mitchell, Christine M.↗

The CEOS International Directory Network Progress and Plans: Spring, 1999

The Global Change Master Directory (GCMD) serves as the software development hub for the Committee on Earth Observation Satellites' (CEOS) International Directory Network (IDN). The GCMD has upgraded the software for the IDN nodes as Version 7 of the GCMD: MD7-Oracle and MD7-Isite, as well as three other MD7 experimental interfaces. The contribution by DLR representatives (Germany) of the DLR Thesaurus will be demonstrated as an educational tool for use with MD7-Isite. The software will be installed at twelve nodes around the world: Brazil, Argentina, the Netherlands, Canada, France, Germany, Italy, Japan, Australia, New Zealand, Switzerland, and several sites in the United States. Representing NASA for the International Directory Network and the CEOS Data Access Subgroup, NASA's contribution to this international interoperability effort will be updated. Discussion will include interoperability with the CEOS Interoperability Protocol (CIP), features of the latest version of the software, including upgraded capabilities for distributed input by the IDN nodes, installation logistics, "mirroring', population objectives, and future plans.

Olsen, Lola M.↗

The CEOS International Directory Network: Progress and Plans, Spring, 1999

The Global Change Master Directory (GCMD) serves as the software development hub for the Committee on Earth observation Satellites' (CEOS) International Directory Network (IDN). The GCMD has upgraded the software for the IDN nodes as Version 7 of the GCMD: MD7-Oracle and MD7-Isite, as well as three other MD7 experimental interfaces. The contribution by DLR representatives (Germany) of the DLR Thesaurus will be demonstrated as an educational tool for use with MD7-Isite. The software will be installed at twelve nodes around the world: Brazil, Argentina, the Netherlands, Canada, France, Germany, Italy, Japan, Australia, New Zealand, Switzerland, and several sites in the United States. Representing NASA for the International Directory Network and the CEOS Data Access Subgroup, NASA's contribution to this international interoperability effort will be updated. Discussion will include interoperability with the CEOS Interoperability Protocol (CIP), features of the latest version of the software, including upgraded capabilities for distributed input by the IDN nodes, installation logistics, "mirroring", population objectives, and future plans.

Olsen, Lola M.↗

TAL Performance and Mission Analysis in a CDL Capacitor Powered Direct-Drive Configuration

The goals of this research are (1) to prove the concept feasibility of a direct-drive electric propulsion system, and (2) to evaluate the performance and characteristics of a Russian TAL (Thruster with Anode Layer) operating in a long-pulse mode, powered by a capacitor-based power source developed at Space Power Institute. The TAL, designated D-55, is characterized by an external acceleration zone and is powered by a unique chemical double layer (CDL) capacitor bank with a capacitance of 4 F at a charge voltage of 400 V. Performance testing of this power supply on the TAL was conducted at NASA Lewis Research Center in Cleveland, OH. Direct thrust measurements of the TAL were obtained at CDL power levels ranging from 450 to 1750 W. The specific impulse encompassed a range from 1150 s to 2200 s, yielding thruster system efficiencies between 50 and 60%. Preliminary mission analysis of the CDL direct-drive concept and other electric propulsion options was performed for the ORACLE spacecraft in 6am/6pm and 12am/12pm, 300 km sun-synchronous orbits. The direct-drive option was competitive with the other systems by increasing available net mass between 5 and 42% and reducing two-year system wet mass between 18 and 63%. Overall, the electric propulsion power requirements for the satellite solar array were reduced between 57 and 91% depending oil the orbit evaluated The direct-drive, CDL capacitor-based concept in electric propulsion thus promises to be a highly-efficient, viable alternative for satellite operations in specific near-Earth missions.

Hrbud, Ivana↗

Development of a Portable, Ground-based Ozone Lidar Instrument for Tropospheric Ozone Research and Educational Training

The objective of this research project is to develop a portable, eye-safe, ground-based ozone lidar instrument specialized for ozone differential absorption lidar (DIAL) measurements in the troposphere. This research project directly supports the goal of NASA's Earth Science Enterprise to understand the distribution and budget of tropospheric ozone (objective 1.5 of the Earth Science Strategic Enterprise Plan, 1998-2002). It can participate in ground validation experiments for TES, a tropospheric ozone satellite mission due to be launched in 2002. It can also be utilized for correlative ground measurements in future GTE (Global Tropospheric Experiment) and space-based ozone lidar missions, such as ORACLE. Multiple ground-based ozone lidar systems would improve the data obtained through current ozone-sonde networks. This prototype instrument could to serve as the basic unit for these and other future monitoring projects requiring multi-instrument networks, such as that proposed for the Global Tropospheric Ozone Project (GTOP). GTOP is currently being formulated by a scientific panel of the International Global Atmospheric Chemistry Project to meet its goal to better understand the processes that control the global distribution of tropospheric ozone. In order for the lidar to be widely deployed in networks, it must be fairly easy to use and maintain as well as being cost-competitive with a ground station launching ozonesondes several times a day. A second 2-year grant to continue this effort with students participating in ground tests and system improvements has been awarded by the Office of Equal Employment Opportunities (OEOP). This project also supports existing NASA lidar missions through its development of advanced, compact lidar technology. Innovations in both transmitters and receivers have been made in this project. Finally, this system could be modified in the future to probe more deeply into the stratosphere. This could be accomplished by increasing the emitted energy or optimizing the wavelengths for this purpose. In addition to NASA, this system has applications to the EPA, NOAA, and the DOD. An AFOSR grant has been awarded based on the results of this effort to fund advanced transmitter development at medium (20-40 mJ) energies. A second proposal to the DOD with a letter of support from Air Force Research Laboratory, has been submitted to extend this uv laser technology to 100 mJ levels. Thus, this project has enabled students and faculty at Hampton University to begin to develop research efforts in support of the mission of the DOD. This instrument will be based at Hampton University (HU) to meet our educational goal to train students in lidar technology as well as atmospheric ozone data analysis and interpretation. It will be also available for off-site measurement campaigns and will serve as a test bed for further instrument development. Later development beyond this grant to extend the scientific usefulness of the instrument may include incorporation of an aerosol channel and upgrading the laser to make stratospheric ozone measurements. Seven undergraduates, three graduate students, and one postdoctoral. researcher (formerly an HU student) have been active participants in this research effort.

Chyba, Thomas↗

Java RMI Software Technology for the Payload Planning System of the International Space Station

The Payload Planning System is for experiment planning on the International Space Station. The planning process has a number of different aspects which need to be stored in a database which is then used to generate reports on the planning process in a variety of formats. This process is currently structured as a 3-tier client/server software architecture comprised of a Java applet at the front end, a Java server in the middle, and an Oracle database in the third tier. This system presently uses CGI, the Common Gateway Interface, to communicate between the user-interface and server tiers and Active Data Objects (ADO) to communicate between the server and database tiers. This project investigated other methods and tools for performing the communications between the three tiers of the current system so that both the system performance and software development time could be improved. We specifically found that for the hardware and software platforms that PPS is required to run on, the best solution is to use Java Remote Method Invocation (RMI) for communication between the client and server and SQLJ (Structured Query Language for Java) for server interaction with the database. Prototype implementations showed that RMI combined with SQLJ significantly improved performance and also greatly facilitated construction of the communication software.

Bryant, Barrett R.↗