Search NASA⌕ Search

SEARCH · Search NASA

Results for “Data archiving software”

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 343 records · Page 19
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Interoperability of Tools at the CCMC

The CCMC has a diverse set of tools in many languages that support utilization of simulation outputs accessible through CCMC interactive archives. Some model output post-processing and analysis tools are delivered to tCCMC by the community. One such model output post-processing/utilization tool developed by the CCMC is the open source Kamodo package. Kamodo is developed primarily in Python (with some C) and has already established strong interoperability with other Python libraries inside PyHC and out. While that interoperability is important, interoperability with other languages and tools is as important. Many models are written in Fortran or C, and their ability to pull in data from a Python tool or export directly to other analysis software in a different language will greatly increase scientific productivity. Interoperability within Python is important, but broader interoperability is just as important.

CCMC↗
NASA NTRS2003

Time Analyzer for Time Synchronization and Monitor of the Deep Space Network

A software package has been developed to measure, monitor, and archive the performance of timing signals distributed in the NASA Deep Space Network. Timing signals are generated from a central master clock and distributed to over 100 users at distances up to 30 kilometers. The time offset due to internal distribution delays and time jitter with respect to the central master clock are critical for successful spacecraft navigation, radio science, and very long baseline interferometry (VLBI) applications. The instrument controller and operator interface software is written in LabView and runs on the Linux operating system. The software controls a commercial multiplexer to switch 120 separate timing signals to measure offset and jitter with a time-interval counter referenced to the master clock. The offset of each channel is displayed in histogram form, and "out of specification" alarms are sent to a central complex monitor and control system. At any time, the measurement cycle of 120 signals can be interrupted for diagnostic tests on an individual channel. The instrument also routinely monitors and archives the long-term stability of all frequency standards or any other 1-pps source compared against the master clock. All data is stored and made available for

Cole, Steven↗
NASA NTRS2015

Airborne Doppler Wind Lidar Post Data Processing Software DAPS-LV

Systems, methods, and devices of the present invention enable post processing of airborne Doppler wind LIDAR data. In an embodiment, airborne Doppler wind LIDAR data software written in LabVIEW may be provided and may run two versions of different airborne wind profiling algorithms. A first algorithm may be the Airborne Wind Profiling Algorithm for Doppler Wind LIDAR ("APOLO") using airborne wind LIDAR data from two orthogonal directions to estimate wind parameters, and a second algorithm may be a five direction based method using pseudo inverse functions to estimate wind parameters. The various embodiments may enable wind profiles to be compared using different algorithms, may enable wind profile data for long haul color displays to be generated, may display long haul color displays, and/or may enable archiving of data at user-selectable altitudes over a long observation period for data distribution and population.

Beyon, Jeffrey Y.↗
NASA NTRS2012

Science Operations with the James Webb Space Telescope

The James Webb Space Telescope (JWST) will be a powerful space observatory whose four science instruments will deliver rich imaging and multiplexed spectroscopic datasets to the astronomical and planetary science communities. The ground segment for JWST, now being designed and built, will carry out JWST's science operations. The ground segment includes: (1) software that the scientific community will use to propose and specify new observations; (2) software that will schedule both science and calibration observations in a way that optimizes observing efficiency while managing the accumulation of momentum; (3) the infrastructure to regularly measure and maintain the telescope's wavefront; (4) orbit determination, ranging, and tracking; (5) communication via the Deep Space Network to command the observatory and retrieve scientific data; (6) onboard scripts that execute each observing program in an event-driven fashion, with occasional interruptions for targets of opportunity or time-critical observations; and (7) a system that processes and calibrates the data into science ready products, automatically recalibrates when calibrations improve, and archives the data for timely access by the principal investigator and later worldwide access by the scientific community. This ground system builds on experience from operating the Hubble Space Telescope, while solving challenges that are unique to the James Webb Space Telescope. In this paper, we describe the elements of the JWST ground system, how it will work operationally from the perspective of the observatory itself, and how a typical user will interact with the system to turn his/her idea into scientific discovery.

Rigby, Jane↗
NASA NTRS1994

Designing an autonomous environment for mission critical operation of the EUVE satellite

Since the launch of NASA's Extreme Ultraviolet Explorer (EUVE) satellite in 1992, there has only been a handful of occurrences that have warranted manual intervention in the EUVE Science Operations Center (ESOC). So, in an effort to reduce costs, the current environment is being redesigned to utilize a combination of off-the-shelf packages and recently developed artificial intelligence (AI) software to automate the monitoring of the science payload and ground systems. The successful implementation of systemic automation would allow the ESOC to evolve from a seven day/week, three shift operation, to a seven day/week one shift operation. First, it was necessary to identify all areas considered mission critical. These were defined as follows: (1) The telemetry stream must be monitored autonomously and anomalies identified. (2) Duty personnel must be automatically paged and informed of the occurrence of an anomaly. (3) The 'basic' state of the ground system must be assessed. (4) Monitors should check that the systems and processes needed to continue in a 'healthy' operational mode are working at all times. (5) Network loads should be monitored to ensure that they stay within established limits. (6) Connectivity to Goddard Space Flight Center (GSFC) systems should be monitored as well, not just for connectivity of the network itself but also for the ability to transfer files. (7) All necessary peripheral devices should be monitored. This would include the disks, routers, tape drives, printers, tape carousel, and power supplies. (8) System daemons such as the archival daemon, the Sybase server, the payload monitoring software, and any other necessary processes should be monitored to ensure that they are operational. (9) The monitoring system needs to be redundant so that the failure of a single machine will not paralyze the monitors. (10) Notification should be done by means of looking though a table of the pager numbers for current 'on call' personnel. The software should be capable of dialing out to notify, sending email, and producing error logs. (11) The system should have knowledge of when real-time passes and tape recorder dumps will occur and should know that these passes and data transmissions are successful. Once the design criteria were established, the design team split into two groups: one that addressed the tracking, commanding, and health and safety of the science payload and another group that addressed the ground systems and communications aspects of the overall system.

Abedini, Annadiana↗
NASA NTRS2001

Description of Selected Algorithms and Implementation Details of a Concept-Demonstration Aircraft VOrtex Spacing System (AVOSS)

A ground-based system has been developed to demonstrate the feasibility of automating the process of collecting relevant weather data, predicting wake vortex behavior from a data base of aircraft, prescribing safe wake vortex spacing criteria, estimating system benefit, and comparing predicted and observed wake vortex behavior. This report describes many of the system algorithms, features, limitations, and lessons learned, as well as suggested system improvements. The system has demonstrated concept feasibility and the potential for airport benefit. Significant opportunities exist however for improved system robustness and optimization. A condensed version of the development lab book is provided along with samples of key input and output file types. This report is intended to document the technical development process and system architecture, and to augment archived internal documents that provide detailed descriptions of software and file formats.

Hinton, David A.↗
NASA NTRS2006

Swift-BAT: The First Year of Gamma-Ray Burst Detections

The Burst Alert Telescope (BAT) on the Swift has been detecting gamma-ray bursts (GRBs) since Dec. 17,2004 and automated burst alerts have been distributed since Feb. 14,2005. Since commissioning the BAT has triggered on more than 100 GRBs, nearly all of which have been followed up by the narrow-field instruments on Swift through automatic repointing, and by ground and other satellite telescopes after rapid notification. Within seconds of a trigger the BAT produces and relays to the ground a position good to three arc minutes and a four channel light curve. A full ten minutes of event data follows on subsequent ground station passes. The burst archive has allowed us to determine ensemble burst parameters such as fluence, peak flux and duration. An overview of the properties of BAT bursts and BAT'S performance as a burst monitor will be presented in this talk. BAT is a coded aperture imaging system with a wide (approx.2 sr) field of view consisting of a large coded mask located 1 m above a 5200 cm2 array of 32.768 CdZnTe detectors. All electronics and other hardware systems on the BAT have been operating well since commissioning and there is no sign of any degradation on orbit. The flight and ground software have proven similarly robust and allow the real time localization of all bursts and the rapid derivation of burst light curves, spectra and spectral fits on the ground.

Krimm, Hans A.↗
NASA NTRS2011

Towards a Standard for Provenance and Context for Preservation of Data for Earth System Science

Long-term data sets with data from many missions are needed to study trends and validate model results that are typical in Earth System Science research. Data and derived products originate from multiple missions (spaceborne, airborne and/or in situ) and from multiple organizations. During the missions as well as well past their termination, it is essential to preserve the data and products to support future studies. Key aspects of preservation are: preserving bits and ensuring data are uncorrupted, preserving understandability with appropriate documentation, and preserving reproducibility of science with appropriate documentation and other artifacts. Computer technology provides adequate standards to ensure that, with proper engineering, bits are preserved as hardware evolves. However, to ensure understandability and reproducibility, it is essential to plan ahead to preserve all the relevant data and information. There are currently no standards to identify the content that needs to be preserved, leading to non-uniformity in content and users not being sure of whether preserved content is comprehensive. Each project, program or agency can specify the items to be preserved as a part of its data management requirements. However, broader community consensus that cuts across organizational or national boundaries would be needed to ensure comprehensiveness, uniformity and long-term utility of archived data. The Federation of Earth Science Information Partners (ESIP), a diverse network of scientists, data stewards and technology developers, has a forum for ESIP members to collaborate on data preservation issues. During early 2011, members discussed the importance of developing a Provenance and Context Content Standard (PCCS) and developed an initial list of content items. This list is based on the outcome of a NASA and NOAA meeting held in 1998 under the auspices of the USGCRP, documentation requirements from NOAA and our experience with some of the NASA Earth science missions. The items are categorized into the following 8 high level categories: Preflight/Pre-Operations, Products (Data), Product Documentation, Mission Calibration, Product Software, Algorithm Input, Validation, Software Tools.

Ramaprian, Hampapuram K.↗
NASA NTRS2011

Evaluating Cloud Computing in the Proposed NASA DESDynI Ground Data System

The proposed NASA Deformation, Ecosystem Structure and Dynamics of Ice (DESDynI) mission would be a first-of-breed endeavor that would fundamentally change the paradigm by which Earth Science data systems at NASA are built. DESDynI is evaluating a distributed architecture where expert science nodes around the country all engage in some form of mission processing and data archiving. This is compared to the traditional NASA Earth Science missions where the science processing is typically centralized. What's more, DESDynI is poised to profoundly increase the amount of data collection and processing well into the 5 terabyte/day and tens of thousands of job range, both of which comprise a tremendous challenge to DESDynI's proposed distributed data system architecture. In this paper, we report on a set of architectural trade studies and benchmarks meant to inform the DESDynI mission and the broader community of the impacts of these unprecedented requirements. In particular, we evaluate the benefits of cloud computing and its integration with our existing NASA ground data system software called Apache Object Oriented Data Technology (OODT). The preliminary conclusions of our study suggest that the use of the cloud and OODT together synergistically form an effective, efficient and extensible combination that could meet the challenges of NASA science missions requiring DESDynI-like data collection and processing volumes at reduced costs.

Benchmark↗
NASA NTRS1995

Development and analysis of SCR requirements tables for system scenarios

We describe the use of scenarios to develop and refine requirement tables for parts of the Earth Observing System Data and Information System (EOSDIS). The National Aeronautics and Space Administration (NASA) is developing EOSDIS as part of its Mission-To-Planet-Earth (MTPE) project to accept instrument/platform observation requests from end-user scientists, schedule and perform requested observations of the Earth from space, collect and process the observed data, and distribute data to scientists and archives. Current requirements for the system are managed with tools that allow developers to trace the relationships between requirements and other development artifacts, including other requirements. In addition, the user community (e.g., earth and atmospheric scientists), in conjunction with NASA, has generated scenarios describing the actions of EOSDIS subsystems in response to user requests and other system activities. As part of a research effort in verification and validation techniques, this paper describes our efforts to develop requirements tables from these scenarios for the EOSDIS Core System (ECS). The tables specify event-driven mode transitions based on techniques developed by the Naval Research Lab's (NRL) Software Cost Reduction (SCR) project. The SCR approach has proven effective in specifying requirements for large systems in an unambiguous, terse format that enhance identification of incomplete and inconsistent requirements. We describe development of SCR tables from user scenarios and identify the strengths and weaknesses of our approach in contrast to the requirements tracing approach. We also evaluate the capabilities of both approach to respond to the volatility of requirements in large, complex systems.

Callahan, John R.↗
NASA NTRS1993

Value added data archiving

Researchers in the Molecular Sciences Research Center (MSRC) of Pacific Northwest Laboratory (PNL) currently generate massive amounts of scientific data. The amount of data that will need to be managed by the turn of the century is expected to increase significantly. Automated tools that support the management, maintenance, and sharing of this data are minimal. Researchers typically manage their own data by physically moving datasets to and from long term storage devices and recording a dataset's historical information in a laboratory notebook. Even though it is not the most efficient use of resources, researchers have tolerated the process. The solution to this problem will evolve over the next three years in three phases. PNL plans to add sophistication to existing multilevel file system (MLFS) software by integrating it with an object database management system (ODBMS). The first phase in the evolution is currently underway. A prototype system of limited scale is being used to gather information that will feed into the next two phases. This paper describes the prototype system, identifies the successes and problems/complications experienced to date, and outlines PNL's long term goals and objectives in providing a permanent solution.

Berard, Peter R.↗
NASA NTRS2007

Pointing History Engine for the Spitzer Space Telescope

The Pointing History Engine (PHE) is a computer program that provides mathematical transformations needed to reconstruct, from downlinked telemetry data, the attitude of the Spitzer Space Telescope (formerly known as the Space Infrared Telescope Facility) as a function of time. The PHE also serves as an example for development of similar pointing reconstruction software for future space telescopes. The transformations implemented in the PHE take account of the unique geometry of the Spitzer telescope-pointing chain, including all data on relative alignments of components, and all information available from attitude-determination instruments. The PHE makes it possible to coordinate attitude data with observational data acquired at the same time, so that any observed astronomical object can be located for future reference and re-observation. The PHE is implemented as a subroutine used in conjunction with telemetry-formatting services of the Mission Image Processing Laboratory of NASA s Jet Propulsion Laboratory to generate the Boresight Pointing History File (BPHF). The BPHF is an archival database designed to serve as Spitzer s primary astronomical reference documenting where the telescope was pointed at any time during its mission.

Bayard, David↗
NASA NTRSDate not supplied

Trends in Small Satellite Presentations from 2017-2019

As the small satellite community expands and new technologies emerge, it is important to understand and interpret these changes over time. In doing so, we observe progress and aid future development within the field. During the summer of 2020 we compiled for assessment purposes, archived presentation data for years 2017-2019 from three primary sources: the CubeSat Developers Workshop, Interplanetary Small Satellite Conference, and the Small Satellite Conference. A few examples of the information we recorded and compiled were presenter names and affiliations, presentation topic, and mission progress status. Ultimately, we reviewed roughly 600 presentations between the three conferences and the data obtained therein form the basis of our trend assessment. The paper focuses on trends interpreted through the assessment of key elements available in the content of each presentation to include: SmallSat mission developers, subsystem developments and the expanded scope for small satellite destinations. Data was generalized using various forms of analysis depending on the type of information being assessed. In the end, we achieved our goal of reducing the content to its key points and major takeaways from the conference proceedings. In this presentation, the observed trends in data and our findings will be discussed. First, we will cover changes in presentation topics by categorizing them as either: science, technology, science/technology, or other. Our next topic will be about the agencies and organizations at the forefront of small satellite research and development. The following section will explain trends in subsystem developments for telecommunications, propulsion, power, and thermal management. Further discussion will highlight how the scope of interplanetary spaceflight has expanded since 2017 as new small spacecraft missions venture beyond low-Earth orbit into deep space exploration. And finally, we will observe what information was lacking in archived presentations which included but not limited to: mission’s funding source, presentation focus area, and software used.

Small Satellite↗
NASA NTRSDate not supplied

Trends in Small Satellite Presentations from 2017 - 2019

As the small satellite community expands and new technologies emerge, it is important to understand and interpret these changes over time. In doing so, we observe progress and aid future development within the field. During the summer of 2020 we compiled for assessment purposes, archived presentation data for years 2017-2019 from three primary sources: the CubeSat Developers Workshop, Interplanetary Small Satellite Conference, and the Small Satellite Conference. A few examples of the information we recorded and compiled were presenter names and affiliations, presentation topic, and mission progress status. Ultimately, we reviewed roughly 600 presentations between the three conferences and the data obtained therein form the basis of our trend assessment. The paper focuses on trends interpreted through the assessment of key elements available in the content of each presentation to include: SmallSat mission developers, subsystem developments and the expanded scope for small satellite destinations. Data was generalized using various forms of analysis depending on the type of information being assessed. In the end, we achieved our goal of reducing the content to its key points and major takeaways from the conference proceedings. In this presentation, the observed trends in data and our findings will be discussed. First, we will cover changes in presentation topics by categorizing them as either: science, technology, science/technology, or other. Our next topic will be about the agencies and organizations at the forefront of small satellite research and development. The following section will explain trends in subsystem developments for telecommunications, propulsion, power, and thermal management. Further discussion will highlight how the scope of interplanetary spaceflight has expanded since 2017 as new small spacecraft missions venture beyond low-Earth orbit into deep space exploration. And finally, we will observe what information was lacking in archived presentations which included but not limited to: mission’s funding source, presentation focus area, and software used.

Small Satellites↗
NASA NTRS2005

NASA GES DISC DAAC Satellite Data for GIS

NASA's Goddard Earth Science (GES) Data and Information Services Center (DISC) Distributed Active Archive Center (DAAC) makes available a large and continually growing collection of spatially continuous global satellite observations of environmental parameters. These products include those from the MODIS (Moderate Resolution Imaging Spectroradiometer) on both Terra and Aqua platforms, and the Tropical Rainfall Measuring Mission (TRMM). These data products are well suited for use within Geographic Information Systems (GIS), as both backdrops to cartographic products as well as spatial analysis. However, data format, file size, and other issues have limited their widespread use by traditional GIS users. To address these data usability issues, the GES DISC DAAC recently updated tools and improved documentation of conversion procedures. In addition, the GES DISC DAAC has also been working with a major GIS software vendor to incorporate the ability to read the native Hierarchial Data Format (HDF), the format in which most of the NASA data is stored. The result is the enabling of GIS users to realize the benefit of GES DISC DAAC data without a substantial expenditure in resources to incorporate these data into their GIS. Several documents regarding the potential uses of GES DISC DAAC satellite data in GIS have recently been created. These show the combinations of concurrent data from different satellite products with traditional GIS vector products for given geographic areas. These map products include satellite imagery of Hurricane Isabel and the California wildfires, and can be viewed at http://daac.gsfc.nasa.gov/MODIS/GIS/.

Nickless, Darryl↗
NASA NTRS2003

NASA's Scientific Visualization Studio

Since 1988, the Scientific Visualization Studio(SVS) at NASA Goddard Space Flight Center has produced scientific visualizations of NASA s scientific research and remote sensing data for public outreach. These visualizations take the form of images, animations, and end-to-end systems and have been used in many venues: from the network news to science programs such as NOVA, from museum exhibits at the Smithsonian to White House briefings. This presentation will give an overview of the major activities and accomplishments of the SVS, and some of the most interesting projects and systems developed at the SVS will be described. Particular emphasis will be given to the practices and procedures by which the SVS creates visualizations, from the hardware and software used to the structures and collaborations by which products are designed, developed, and delivered to customers. The web-based archival and delivery system for SVS visualizations at svs.gsfc.nasa.gov will also be described.

Mitchell, Horace G.↗
NASA NTRS2015

Attitude Design for the LADEE Mission

The Lunar Atmosphere and Dust Environment Explorer (LADEE) satellite successfully completed its 148-day science investigation in a low-altitude, near-equatorial lunar orbit on April 18, 2014. The LADEE spacecraft was built, managed and operated by NASA's Ames Research Center (ARC). The Mission Operations Center (MOC) was located at Ames and was responsible for activity planning, command sequencing, trajectory and attitude design, orbit determination, and spacecraft operations. The Science Operations Center (SOC) was located at Goddard Space Flight Center and was responsible for science planning, data archiving and distribution. This paper details attitude design and operations support for the LADEE mission. LADEE's attitude design was shaped by a wide range of instrument pointing requirements that necessitated regular excursions from the baseline one revolution per orbit "Ram" attitude. Such attitude excursions were constrained by a number of flight rules levied to protect instruments from the Sun, avoid geometries that would result in simultaneous occlusion of LADEE's two star tracker heads, and maintain the spacecraft within its thermal and power operating limits. To satisfy LADEE's many attitude requirements and constraints, a set of rules and conventions was adopted to manage the complexity of this design challenge and facilitate the automation of ground software that generated pointing commands spanning multiple days of operations at a time. The resulting LADEE Flight Dynamics System (FDS) that was developed used Visual Basic scripts that generated instructions to AGI's Satellite Tool Kit (STK) in order to derive quaternion commands at regular intervals that satisfied LADEE's pointing requirements. These scripts relied heavily on the powerful "align and constrain" capability of STK's attitude module to construct LADEE's attitude profiles and the slews to get there. A description of the scripts and the attitude modeling they embodied is provided. One particular challenge analysts faced was in the design of LADEE maneuver attitudes. A flight rule requiring pre-maneuver verification of in-flight maneuver conditions by ground operators prior to burn execution resulted in the need to accommodate long periods in the maneuver attitude. This in turn complicated efforts to satisfy star tracker interference and communication constraints in lunar orbit. In response to this challenge, a graphical method was developed and used to survey candidate rotation angles about the thrust vector. This survey method is described and an example of its use on a particular LADEE maneuver is discussed. Finally, the software and methodology used to satisfy LADEE's attitude requirements are also discussed in the context of LADEE's overall activity planning effort. In particular, the way in which strategic schedules of instrument and engineering activities were translated into actual attitude profiles at the tactical level, then converted into precise quaternion commands to achieve those pointing goals is explained. In order to reduce the risk of time-consuming re-planning efforts, this process included the generation of long-term projections of constraint violation predictions for individual attitude profiles that could be used to establish keep-out time-frames for particular attitude profiles. The challenges experienced and overall efficacy of both the overall LADEE ground system and the attitude components of the Flight Dynamics System in meeting LADEE's varied pointing requirements are discussed.

LADEE↗
NASA NTRS2003

Accessing and Understanding MODIS Data

The National Aeronautics and Space Administration (NASA) launched the Terra satellite in December 1999, as part of the Earth Science Enterprise promotion of interdisciplinary studies of the integrated Earth system. Aqua, the second satellite from the series of EOS constellation, was launched in May 2002. Both satellites carry the MODerate resolution Imaging Spectroradiometer (MODIS) instrument. MODIS data are processed at the Goddard Space Flight Center, Greenbelt, MD, and then archived and distributed by the Distributed Active Archive Centers (DAACs). Data products from the MODIS sensors present new challenges to remote sensing scientists due to specialized production level, data format, and map projection. MODIS data are distributed as calibrated radiances and as higher level products such as: surface reflectance, water-leaving radiances, ocean color and sea surface temperature, land surface kinetic temperature, vegetation indices, leaf area index, land cover, snow cover, sea ice extent, cloud mask, atmospheric profiles, aerosol properties, and many other geophysical parameters. MODIS data are stored in HDF- EOS format in both swath format and in several different map projections. This tutorial guides users through data set characteristics as well as search and order interfaces, data unpacking, data subsetting, and potential applications of the data. A CD-ROM with sample data sets, and software tools for working with the data will be provided to the course participants.

Leptoukh, Gregory↗