SEARCH · Search NASA
Results for “databases”
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.
CamRegBase: a gene regulation database for the biofuel crop, Camelina sativa
Abstract Camelina is an annual oilseed plant from the Brassicaceae family that is gaining momentum as a biofuel winter cover crop. However, a significant limitation in further enhancing its utility as a producer of oils that can be used as biofuels, jet fuels or bio-based products is the absence of a repository for all the gene expression and regulatory information that is being rapidly generated by the community. Here, we provide CamRegBase (https://camregbase.org/) as a one-stop resource to access Camelina information on gene expression and co-expression, transcription factors, lipid associated genes and genome-wide orthologs in the close-relative reference plant Arabidopsis. We envision this as a resource of curated information for users, as well as a repository of new gene regulation information.
Demonstration of thermal control, microstructure control, defect mitigation and process parameter database generation for Ti-6Al-4V Direct Digital Manufacturing - Understanding defect mitigation and process parameter database generation for direct digital manufacturing
Researchers from Manufacturing Demonstration Facility (MDF) at Oak Ridge National Laboratory (ORNL) worked with Applied Optimization (AO) to understand and evaluate the propensity for defect formation in builds manufactured using DM3D-POM laser direct metal deposition. The main aim of this collaboration was to understand the character of powder jet behavior as a function of the nozzle parameters such as cover gas, carrier gas, and shaping gas. In order to evaluate the sensitivities of the parameters used in model, various experiments were performed with in-situ monitoring of the powder stream characteristics using a high speed camera. A wide variety of conditions while keeping the hopper motor rpm constant, including laser power and travel speed were explored. The cross sections of the deposits were characterized using optical microscopy.
Global Energy Storage Database (GESDB): Database Updates and New Features
Explore the source record for details and available documents.
Existing Hydropower Assets (EHA) Capacity Plant Database, 2005-2024
Existing Hydropower Asset (EHA) Annual Capacity is a geospatial point-level dataset containing annual capacity over the years (2005-2024) and key characteristics of operational U.S. hydropower plants with 1 megawatt or greater of nameplate capacity. EIA form 860 and EHA are the primary sources of the derived data.
Existing Hydropower Assets (EHA) Capacity Factor Plant Database, 2005-2024
Existing Hydropower Asset (EHA) Annual Capacity Factor is a geospatial point-level dataset containing annual capacity factors over the years (2005-2024) and key characteristics of operational U.S. hydropower plants with 1 megawatt or greater of nameplate capacity. EIA form 860 and EHA are the primary sources of the derived data. Pumped storage and hybrid plants are excluded.
Existing Hydropower Assets (EHA) Net Generation Plant Database, 2003-2026
Explore the source record for details and available documents.
Comprehensive Database of Environmental Mitigations Extracted from FERC-Licensed Hydropower Projects Using Artificial Intelligence Techniques, 1998-2023
This dataset provides a comprehensive inventory of environmental mitigation measures required by Federal Energy Regulatory Commission (FERC) licensed hydropower facilities from 461 licenses that were issued from 1998 to 2023. These licenses constitute 446 of the 1015 FERC projects that were active at the end of 2023. 17,612 mentions of environmental mitigations were identified and categorized in 128 unique categories. Mitigations were identified using a Natural Language Processing (NLP) approach, specifically with a Bidirectional Encoder Representations from Transformer (BERT) model. Model-derived results were then reviewed and updated by a subject matter expert as needed. This dataset introduces important enhancements to previous efforts to inventory environmental mitigations, such as including associated license text for each mitigation, tracking the number of instances a mitigation was identified within a license, and providing improved location information. These enhancements significantly expand the dataset's utility, offering greater analytical capabilities and ensuring reproducibility. The dataset is downloadable as a zip file containing the metadata and dataset files.
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.
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.
CHSIR Anthropometric Database, CHSIR Truncated Anthropometric Database, and Boundary Manikins
The NASA crew anthropometric dimensions that the Commercial Transportation System (CTS) must accommodate are listed in CCT-REQ-1130 Draft 3.0, with the specific critical anthropometric dimensions for use in vehicle design (and suit design in the event that a pressure suit is part of the commercial partner s design solution).
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.
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).
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.
An Overview of the Database Framework for GEM Detector under CMS Experiment at CERN
In this paper, we give an overview of the database framework which we have developed for the Gas Electron Multiplier (GEM) Detector at CERN. The GEM constitutes a powerful addition to the family of fast radiation detectors; originally developed for particle physics experiments, and has spawned a large number of developments and applications. The GEM database framework comprises four components. The first component is the database itself. There are three instances of the database which have been deployed. One is for the development purpose which contains test data, other one is for the integration purposes while the last one is for the production purpose which contains real data. The database further comprises various schemas and each schema consists of different tables in it. We use separate schemas for various types of tables. The second component of the database framework is called DB Loader. The DB Loader is used to load data into database. The data is prepared in the predefined format which is in the XML form. Then the xml file is copied into a spool area of the server in which DB loader is running. Once the file is copied, the DB Loader loads the file into the database. The loader returns appropriate status codes after performing database insertion/update operation. The status of the database operations is checked against the status code which is returned by the loader. The third component of the database framework comprises graphical user interface (GUI). This is a web-based interface which can be accessed from the internet. This interface is basically used for the detector construction and to perform various quality control tests on the detector and its components. The last component of the database framework is called online monitoring system (OMS). The OMS is data visualization framework for the various detectors of the CMS experiment at CERN. It is also used to display data for the GEM. It enables users to view and retrieve database contents without having to learn database specifics.
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.
Integrating a local database into the StarView distributed user interface
A distributed user interface to the Space Telescope Data Archive and Distribution Service (DADS) known as StarView is being developed. The DADS architecture consists of the data archive as well as a relational database catalog describing the archive. StarView is a client/server system in which the user interface is the front-end client to the DADS catalog and archive servers. Users query the DADS catalog from the StarView interface. Query commands are transmitted via a network and evaluated by the database. The results are returned via the network and are displayed on StarView forms. Based on the results, users decide which data sets to retrieve from the DADS archive. Archive requests are packaged by StarView and sent to DADS, which returns the requested data sets to the users. The advantages of distributed client/server user interfaces over traditional one-machine systems are well known. Since users run software on machines separate from the database, the overall client response time is much faster. Also, since the server is free to process only database requests, the database response time is much faster. Disadvantages inherent in this architecture are slow overall database access time due to the network delays, lack of a 'get previous row' command, and that refinements of a previously issued query must be submitted to the database server, even though the domain of values have already been returned by the previous query. This architecture also does not allow users to cross correlate DADS catalog data with other catalogs. Clearly, a distributed user interface would be more powerful if it overcame these disadvantages. A local database is being integrated into StarView to overcome these disadvantages. When a query is made through a StarView form, which is often composed of fields from multiple tables, it is translated to an SQL query and issued to the DADS catalog. At the same time, a local database table is created to contain the resulting rows of the query. The returned rows are displayed on the form as well as inserted into the local database table. Identical results are produced by reissuing the query to either the DADS catalog or to the local table. Relational databases do not provide a 'get previous row' function because of the inherent complexity of retrieving previous rows of multiple-table joins. However, since this function is easily implemented on a single table, StarView uses the local table to retrieve the previous row. Also, StarView issues subsequent query refinements to the local table instead of the DADS catalog, eliminating the network transmission overhead. Finally, other catalogs can be imported into the local database for cross correlation with local tables. Overall, it is believe that this is a more powerful architecture for distributed, database user interfaces.
Web Exploration Tools for a Fast Federated Optical Survey Database
We implemented several new web-based tools to improve the efficiency and versatility of access to the APS Catalog of the POSS I (Palomar Observatory-National Geographic Sky Survey) and its associated image database. The most important addition was a federated database system to link the APS Catalog and image database into one Internet-accessible database. With the FDBS, the queries and transactions on the integrated database are performed as if it were a single database. We installed Myriad the FDBS developed by Professor Jaideep Srivastava and members of his group in the University of Minnesota Computer Science Department. It is the first system to provide schema integration, query processing and optimization, and transaction management capabilities in a single framework. The attached figure illustrates the Myriad architecture. The FDBS permits horizontal access to the data, not just vertical. For example, for the APS, queries can be made not only by sky position, but also by any parameter present in either of the databases. APS users will be able to produce an image of all the blue galaxies and stellar sources for comparison with x-ray source error ellipses from AXAF (X Ray Astrophysics Facility) (Chandra) for example. The FDBS is now available as a beta release with the appropriate query forms at our web site. While much of our time was occupied with adapting Myriad to the APS environment, we also made major changes in Star Base, our DBMS for the Catalog, at the web interface to improve its efficiency for issuing and processing queries. Star Base is now three times faster for large queries. Improvements were also made at the web end of the image database for faster access; although work still needs to be done to the image database itself for more efficient return with the FDBS. During the past few years, we made several improvements to the database pipeline that creates the individual plate databases queries by StarBase. The changes include improved positions especially for galaxies, using a new median centroider and integrated magnitudes for galaxies with an improved density-to-intensity calibration with a "sky" background subtraction. In the original version of StarBase the object classification fainter than 19.5-20.0 mag., was an extrapolation of the networks trained on brighter objects. We have used a new catalog of galaxies at the NGP to train a neural network on objects fainter than 20th mag. This improved classification is used in the new version of StarBase. We have also added a FITS table option for the returned data from queries on the object catalog. The APS image database includes images in both colors so we have added a tool for querying the image database in both colors simultaneously. The images can be displayed in parallel or blinked for comparison.