Search NASA⌕ Search

SEARCH · Search NASA

Results for “Science Operations”

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 181 records · Page 10

Hybridized Agile Software Development of Flight Control Team Tools for International Space Station's Payload Operations Integration Center

Ground systems operations at the National Aeronautics and Space Administration's (NASA) Payload Operations and Integration Center (POIC) at Marshall Space Flight Center (MSFC) recently increased via a High Operations Tempo (HOT) initiative, in order to support more science activities with a fourth crew member on the International Space Station (ISS). The Flight Control Team's (FCT) need to support this increasing pace of payload science operations was the impetus for creating a series of new tools. While their need was clear, the full scope and user experience for each tool was not as well-understood, thus establishing a fixed set of initial requirements was not feasible. A hybridized Agile Software Development (ASD) paradigm was created to take advantage of this uncertainty, plan for it, permit the exploration of novel concepts, and also facilitate a rapid and flexible response to inevitably changing requirements. The POIC's hybridized ASD approach places preeminent focus on providing customer value through the delivery of high quality, customer-focused solutions in short timeframes. This has been successfully achieved through creating unprecedented modes of cooperation and collaboration between operations and software development teams, frequent user evaluations of the software with well-defined feedback mechanisms, increased human factors involvement, and a dedication to successful outcomes by the whole of the POIC. Since space science operations and software development are not typically so closely linked, this paper discusses an approach that offers an optimal way to provide an increased return on investment and a faster time-to-completion than traditional software development paradigms, while aiming at delivering high quality products and customer-driven value.

Albers, Cerese M.↗

Hybridized Agile Software Development of Flight Control Team Tools for International Space Station's Payload Operations Integration Center

Ground systems operations at the National Aeronautics and Space Administration's (NASA) Payload Operations and Integration Function (POIF) is increasing, via the High Operations Tempo (HOT) initiative, its ability to support more science activities with a fourth crew member on the International Space Station (ISS). The Flight Control Team's need to support this increased crew presence mandated the need for a series of software tools to better handle the increasing pace of payload science operations. The overall need was clear from the outset, but the full scope and user experience for each tool, were not as well understood, so establishing a fixed set of initial requirements was not feasible. An Agile Software Development (ASD) paradigm takes advantage of uncertainty, and plans for it, so it was deemed the most appropriate approach to create room for exploring novel concepts, and to mount a rapid and flexible response to inevitiably changing requirements. It facilitated the need for unprecedented collaboration between the Product Team (i.e. users from the Flight Control Team) and the Development Team (i.e. POIC systems engineers, developers, testers). This is a process shift in the development, test, and release of software from one that is prescriptive to one that is adaptive, which is necessary for these tools to have longevity. The application of ASD to the product development lifecycle permitted the timely incorporation of customer feedback, and, allowed for continuous quality improvements. This resulted in a suite of tools that are efficient, user-friendly, and enable POIF ground systems to support the increasing pace of payload science operations. ASD is not as much a set of prescriptive processes as it is a shift in mindset; one that moves from planning against change, to planning for change, thereby iteratively growing software towards user-defined value.

Albers, Cerese M.↗

Exploration Ground Data Systems (xGDS) Overview

xGDS supports rapid scientific decision making by synchronizing the time and mapped location of observation notes, instrument data, photos, video, samples and other data. xGDS is a suite of web tools, developed at NASA Ames Research Center to support remote science operations in analog missions and prototype new ideas for planetary exploration. During operations, xGDS displays science data in real-time with geographic context, supporting key decisions (e.g. sample site selection). Post-operations, xGDS enables efficient analysis of data by correlating data products in time and on the map. xGDS has been developed in close collaboration with science teams since 2009, and used enthusiastically by upwards of 100 scientists to support scientific field research and data analysis.

Ground Data System↗

NEEMO 20: Science Training, Operations, and Tool Development

The 20th mission of the National Aeronautics and Space Administration (NASA) Extreme Environment Mission Operations (NEEMO) was a highly integrated evaluation of operational protocols and tools designed to enable future exploration beyond low-Earth orbit. NEEMO 20 was conducted from the Aquarius habitat off the coast of Key Largo, FL in July 2015. The habitat and its surroundings provide a convincing analog for space exploration. A crew of six (comprised of astronauts, engineers, and habitat technicians) lived and worked in and around the unique underwater laboratory over a mission duration of 14-days. Incorporated into NEEMO 20 was a diverse Science Team (ST) comprised of geoscientists from the Astromaterials Research and Exploration Science (ARES/XI) Division from the Johnson Space Center (JSC), as well as marine scientists from the Department of Biological Sciences at Florida International University (FIU). This team trained the crew on the science to be conducted, defined sampling techniques and operational procedures, and planned and coordinated the science focused Extra Vehicular Activities (EVAs). The primary science objectives of NEEMO 20 was to study planetary sampling techniques and tools in partial gravity environments under realistic mission communication time delays and operational pressures. To facilitate these objectives two types of science sites were employed 1) geoscience sites with available rocks and regolith for testing sampling procedures and tools and, 2) marine science sites dedicated to specific research focused on assessing the photosynthetic capability of corals and their genetic connectivity between deep and shallow reefs. These marine sites and associated research objectives included deployment of handheld instrumentation, context descriptions, imaging, and sampling; thus acted as a suitable proxy for planetary surface exploration activities. This abstract briefly summarizes the scientific training, scientific operations, and tool development conducted during NEEMO 20 with an emphasis on the primary lessons learned.

Graff, T.↗

Using Near Real-Time Mission Data for Education and Public Outreach: Strategies from the Life in the Atacama E/PO Effort

The EventScope educational telepresence project has been involved with education and public outreach for a number of NASA-sponsored missions including the Mars Exploration Rovers, the Odyssey Mission, and the Life in the Atacama project. However, during the second year of operations in the Atacama, a modified version of the EventScope public interface was used as the remote science operations interface. In addition, the EventScope lab hosted remote science operations. This intimate connection with the mission operations allowed the EventScope team to bring the experience of the mission to the public in near real-time. Playing to this strength, the lab developed strategies for releasing E/PO content as close to real-time as possible.

Myers, E.↗

Kepler: A Search for Terrestrial Planets - SOC 9.3 DR25 Pipeline Parameter Configuration Reports

This document describes the manner in which the pipeline and algorithm parameters for the Kepler Science Operations Center (SOC) science data processing pipeline were managed. This document is intended for scientists and software developers who wish to better understand the software design for the final Kepler codebase (SOC 9.3) and the effect of the software parameters on the Data Release (DR) 25 archival products.

exoplanet↗

Algorithm Science to Operations for the National Polar-orbiting Operational Environmental Satellite System (NPOESS) Visible/Infrared Imager/Radiometer Suite (VIIRS)

The VIIRS sensor provides measurements for 22 Environmental Data Records (EDRs) addressing the atmosphere, ocean surface temperature, ocean color, land parameters, aerosols, imaging for clouds and ice, and more. That is, the VIIRS collects visible and infrared radiometric data of the Earth's atmosphere, ocean, and land surfaces. Data types include atmospheric, clouds, Earth radiation budget, land/water and sea surface temperature, ocean color, and low light imagery. This wide scope of measurements calls for the preparation of a multiplicity of Algorithm Theoretical Basis Documents (ATBDs), and, additionally, for intermediate products such as cloud mask, et al. Furthermore, the VIIRS interacts with three or more other sensors. This paper addresses selected and crucial elements of the process being used to convert and test an immense volume of a maturing and changing science code to the initial operational source code in preparation for launch of NPP. The integrity of the original science code is maintained and enhanced via baseline comparisons when re-hosted, in addition to multiple planned code performance reviews.

NPOESS (NATIONAL POLAR-ORBITING OPERATIONAL ENVIRO↗

A Distributed Simulation Software System for Multi-Spacecraft Missions

The paper will provide an overview of the web-based distributed simulation software system developed for end-to-end, multi-spacecraft mission design, analysis, and test at the NASA Goddard Space Flight Center (GSFC). This software system was developed for an internal research and development (IR&D) activity at GSFC called the Distributed Space Systems (DSS) Distributed Synthesis Environment (DSE). The long-term goal of the DSS-DSE is to integrate existing GSFC stand-alone test beds, models, and simulation systems to create a "hands on", end-to-end simulation environment for mission design, trade studies and simulations. The short-term goal of the DSE was therefore to develop the system architecture, and then to prototype the core software simulation capability based on a distributed computing approach, with demonstrations of some key capabilities by the end of Fiscal Year 2002 (FY02). To achieve the DSS-DSE IR&D objective, the team adopted a reference model and mission upon which FY02 capabilities were developed. The software was prototyped according to the reference model, and demonstrations were conducted for the reference mission to validate interfaces, concepts, etc. The reference model, illustrated in Fig. 1, included both space and ground elements, with functional capabilities such as spacecraft dynamics and control, science data collection, space-to-space and space-to-ground communications, mission operations, science operations, and data processing, archival and distribution addressed.

Burns, Richard↗

An Internet Protocol-Based Software System for Real-Time, Closed-Loop, Multi-Spacecraft Mission Simulation Applications

The paper will provide an overview of the web-based distributed simulation software system developed for end-to-end, multi-spacecraft mission design, analysis, and test at the NASA Goddard Space Flight Center (GSFC). This software system was developed for an internal research and development (IR&D) activity at GSFC called the Distributed Space Systems (DSS) Distributed Synthesis Environment (DSE). The long-term goal of the DSS-DSE is to integrate existing GSFC stand-alone test beds, models, and simulation systems to create a "hands on", end-to-end simulation environment for mission design, trade studies and simulations. The short-term goal of the DSE was therefore to develop the system architecture, and then to prototype the core software simulation capability based on a distributed computing approach, with demonstrations of some key capabilities by the end of Fiscal Year 2002 (FY02). To achieve the DSS-DSE IR&D objective, the team adopted a reference model and mission upon which FY02 capabilities were developed. The software was prototyped according to the reference model, and demonstrations were conducted for the reference mission to validate interfaces, concepts, etc. The reference model, illustrated in Fig. 1, included both space and ground elements, with functional capabilities such as spacecraft dynamics and control, science data collection, space-to-space and space-to-ground communications, mission operations, science operations, and data processing, archival and distribution addressed.

Davis, George↗

In-Flight Operation of the Dawn Ion Propulsion System Through Survey Science Orbit at Ceres

The Dawn mission, part of NASA's Discovery Program, has as its goal the scientific exploration of the two most massive main-belt objects, Vesta and Ceres. The Dawn spacecraft was launched from the Cape Canaveral Air Force Station on September 27, 2007 on a Delta-II 7925H- 9.5 (Delta-II Heavy) rocket that placed the 1218-kg spacecraft onto an Earth-escape trajectory. On-board the spacecraft is an ion propulsion system (IPS) developed at the Jet Propulsion Laboratory which will provide a total delta V of 11 km/s for the heliocentric transfer to Vesta, orbit capture at Vesta, transfer between Vesta science orbits, departure and escape from Vesta, heliocentric transfer to Ceres, orbit capture at Ceres, and transfer between Ceres science orbits. Full-power thrusting from December 2007 through October 2008 was used to successfully target a Mars gravity assist flyby in February 2009 that provided an additional delta V of 2.6 km/s. Deterministic thrusting for the heliocentric transfer to Vesta resumed in June 2009 and concluded with orbit capture at Vesta on July 16, 2011. From July 2011 through September 2012 the IPS was used to transfer to all the different science orbits at Vesta and to escape from Vesta orbit. Cruise for a rendezvous with Ceres began in September 2012 and concluded with the start of the approach to Ceres phase on December 26, 2015, leading to orbit capture on March 6, 2015. Deterministic thrusting continued during approach to place the spacecraft in its first science orbit, called RC3, which was achieved on April 23, 2015. Following science operations at RC3 ion thrusting was resumed for twenty-five days leading to arrival to the next science orbit, called survey orbit, on June 3, 2015. The IPS will be used for all subsequent orbit transfers and trajectory correction maneuvers until completion of the primary mission in approximately June 2016. To date the IPS has been operated for over 46,774 hours, consumed approximately 393 kg of xenon, and provided a delta V of over 10.8 km/s to the spacecraft. The IPS performance characteristics are very close to the expected performance based on analysis and testing performed pre-launch. This paper provides an overview of Dawn's mission objectives and the results of Dawn IPS mission operations through arrival at the second science orbit at Ceres.

Garner, Charles E.↗

Spitzer Space Telescope in-orbit checkout and science verification operations

Spitzer Space Telescope, the fourth and final of NASA's great observatories, and the first mission in NASA's Origins Program was launched 25 August 2003 into an Earth-trailing solar orbit. The observatory was designed to probe and explore the universe in the infrared. Before science data could be acquired, however, the observatory had to be initialized, characterized, calibrated, and commissioned. A two phased operations approach was defined to complete this work. These phases were identified as In-Orbit Checkout (IOC) and Science Verification (SV). Because the observatory lifetime is cryogen-limited these operations had to be highly efficient. The IOC/SV operations design accommodated a pre-defined distributed organizational structure and a complex, cryogenic flight system. Many checkout activities were inter-dependent, and therefore the operations concept and ground data system had to provide the flexibility required for a 'short turn-around' environment. This paper describes the adaptive operations system design and evolution, implementation, and lessons-learned from the completion of IOC/SV.

space verification↗

Hubble Space Telescope Star Tracker ad Two-Gyro Control Law Design, Implementation, and On-Orbit Performance

The Hubble Space Telescope (HST) normally requires three gyroscopes for three-axis rate control. The loss of the Space Shuttle Columbia on STS-107 resulted in the cancellation of a shuttle-based HST Servicing Mission 4. Therefore, HST must operate using the on-board hardware until an alternate means of servicing can be accomplished. The probability of gyro failure indicates that fewer than three gyros will be operable before any servicing mission can be performe& To mitigate this, and to extend the HST life expectancy, a rate estimation and control algorithm was developed that requires two gyros to measure rate about two axes, with the remaining axis rate estimated using one of three alternate sensors. Three-axis magnetometers (MSS) are used for coarse rate estimation during large maneuvers and during occultations of other sensors. Fixed-Head Star Trackers (FHSTs) are used for rate estimation during safe mode recovery and during transition to science operations. Fine rate estimation during science operations is performed using the Fine Guidance Sensors (FGSs). The FHST mode (T2G) relies on star vectors as measured by the FHSTs to estimate vehicle rate about the axis not measured by the gyros. Since the FHSTs were not designed to estimate body rate, this method involves a unique set of problems that had to be overcome in the final design, such as the effect of FHST break tracks and moving targets on rate estimation. The solutions to these problems, as well as a detailed description of the design and implementation of the rate estimation are presented Also included are the time domain and frequency domain analysis of the T2G control law. A high fidelity HST simulator (HSTSIM) was used to verify T2G performance prior to on-orbit use. Results of these simulations are also presented. Finally, analysis of actual T2G on-orbit test results is presented for design validation.

VanArsdall, John C.↗

On-Orbit Performance of the TES Pulse Tube Cryocooler System and the Instrument - Six Years in Space

The Tropospheric Emission Spectrometer (TES) instrument pulse tube cryocoolers began operation 36 days after launch of the NASA Earth Observing System (EOS) Aura spacecraft on July 15, 2004. TES is designed with four infrared Mercury Cadmium Telluride focal plane arrays in two separate housings cooled by a pair of Northrup Grumman Aerospace Systems (NGAS) single-stage pulse tube cryocoolers. The instrument also makes use of a two-stage passive cooler to cool the optical bench. The instrument is a high-resolution infrared imaging Fourier transform spectrometer with 3.3-15.4 micron spectral coverage. After four weeks of outgassing, the instrument optical bench and focal planes were cooled to their operating temperatures to begin science operations. During the early months of the mission, ice contamination of the cryogenic surfaces including the focal planes led to increased cryocooler loads and the need for periodic decontamination cycles. After a highly successful 5 years of continuous in-space operations, TES was granted a 2 year extension. This paper reports on the TES cryogenic system performance including the two-stage passive cooler. After a brief overview of the cryogenic design, the paper presents detailed data on the highly successful space operation of the pulse tube cryocoolers and instrument thermal design over the past six years since the original turn-on in 2004. The data shows the cryogenic contamination decreased substantially to where decontamination cycles are now performed every six months. The cooler stroke required for constant-temperature operation has not increased indicating near-constant cooler efficiency and the instrument's thermal design has also provided a nearly constant heat rejection sink. At this time TES continues to operate in space providing important Earth science data.

cryocoolercraft↗

The Kepler DB, a Database Management System for Arrays, Sparse Arrays and Binary Data

The Kepler Science Operations Center stores pixel values on approximately six million pixels collected every 30-minutes, as well as data products that are generated as a result of running the Kepler science processing pipeline. The Kepler Database (Kepler DB) management system was created to act as the repository of this information. After one year of ight usage, Kepler DB is managing 3 TiB of data and is expected to grow to over 10 TiB over the course of the mission. Kepler DB is a non-relational, transactional database where data are represented as one dimensional arrays, sparse arrays or binary large objects. We will discuss Kepler DB's APIs, implementation, usage and deployment at the Kepler Science Operations Center.

McCauliff, Sean↗

(abstract) The Evolving Spaceborne Radar Data Support to Earth Science and Operations at the Alaska SAR Facility

The Alaska SAR Facility (ASF) has been receiving, processing, archiving, and distributing data for Earth scientists and operations since it began receiving data in 1991. Four radar satellites are now being handled. Recent developments have served to increase the level of services of ASF to the Earth science community considerably. These developments are discussed.

mapping radar interferometry Alaska topography ant↗