Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Missions Data”

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 991 records · Page 55

Extending the Licklider Transmission Protocol to Multi-Band Links

Most deep space missions return data to Earth using links operating at a single frequency band. Indeed, their data requirements are low enough that bandwidth regulations do not constrain the system. In contrast, spacecraft such as Kepler or Europa Clipper are transitioning to a new operational paradigm where engineering and science data are transmitted through simultaneous links operating at different frequency bands (henceforth termed multi-band links). This ensures, for instance, that critical data is correctly received using a well characterized X-band link, while science data at a much larger data rate can be returned efficiently (both in terms of bandwidth and energy) through a Ka-band link.Having a spacecraft establish two simultaneous links with a ground station opens a large span of potential improvements for space communications and mission operations. In this paper, we consider the problem of running a Licklider Transmission Protocol (LTP) session over a multi-band link. LTP is an implementation of a selective Automatic Repeat reQuest (ARQ) protocol, i.e. it ensures correct delivery of data over an error prone link with potentially long propagation delays. To maximize its efficiency in deep space environments, LTP operates in deferred-ACK mode and is typically included as one of the core protocols in the Delay Tolerant Networking (DTN) suite.The contributions of this paper are as follows: First, we propose an extension to LTP for multi-band links (denoted MBLTP) and sketch how it can be implemented without modifying the current definition of LTP data units. Next, we develop bounds on the performance of MBLTP when transmitting a single data file over a multi-band link. Three metrics are considered, file expected delivery time, total energy spent and bundle jitter. The results of the analytic model are first benchmarked against simulations to ensure validity, and then compared against the performance of both traditional LTP and Parallel LTP (PLTP).We demonstrate that MBLTP can significantly reduce the latency and jitter with which data products are delivered to destination over a deep space link compared to LTP at moderate energy cost. Similarly, we also demonstrate that MBLTP outperforms PLTP in all considered metrics.

Sanchez Net, Marc↗

Program manual for HILTOP, a heliocentric interplanetary low thrust trajectory optimization program. Part 1: User's guide

A performance-analysis computer program, that was developed explicitly to generate optimum electric propulsion trajectory data for missions of interest in the exploration of the solar system is presented. The program was primarily designed to evaluate the performance capabilities of electric propulsion systems, and in the simulation of a wide variety of interplanetary missions. A numerical integration of the two-body, three-dimensional equations of motion and the Euler-Lagrange equations was used in the program. Transversality conditions which permit the rapid generation of converged maximum-payload trajectory data, and the optimization of numerous other performance indices for which no transversality conditions exist are included. The ability to simulate constrained optimum solutions, including trajectories having specified propulsion time and constant thrust cone angle, is also in the program. The program was designed to handle multiple-target missions with various types of encounters, such as rendezvous, stopover, orbital capture, and flyby. Performance requirements for a variety of launch vehicles can be determined.

Mann, F. I.↗

Selecting Approaches for Enabling Enterprise Data Search: NASA’s Science Mission Directorate (SMD) Catalog

NASA’s Science Mission Directorate (SMD) is working to build an open-source science infrastructure to accelerate open, collaborative and interdisciplinary science. One key component in the open-source science infrastructure is the SMD data catalog. In this paper, we present our process for selecting a technical approach to building a NASA SMD enterprise-wide integrated search capability for science users across multiple science disciplines to support discovery and access to complex scientific data.

Kaylin Bugbee↗

Antarctic Space Analog Program

The primary aim of this project was to examine group dynamics and individual performance in extreme, isolated environments and identify human factors requirements for long-duration space missions using data collected in an analog environment. Specifically, we wished to determine: 1) the characteristics of social relations in small groups of individuals living and working together in extreme, isolated environments, and 2) the environmental, social and psychological determinants of performance effectiveness in such groups. These two issues were examined in six interrelated studies using data collected in small, isolated research stations in Antarctica from 1963 to the present. Results from these six studies indicated that behavior and performance on long-duration space flights is likely to be seasonal or cyclical, situational, social, and salutogenic in nature. The project responded to two NASA program emphases for FY 1997 as described in the NRA: 1) the primary emphasis of the Behavior and Performance Program on determining long-term individual and group performance responses to space, identifying critical factors affecting those responses and understanding underlying mechanisms involved in behavior and performance, and developing and using ground-based models and analogs for studying space-related behavior and performance; and 2) the emphasis of the Data Analysis Program on extended data analysis. Results from the study were used to develop recommendations for the design and development of pre-flight crew training and in-flight psychological countermeasures for long-duration manned space missions.

Palinkas, Lawrence A↗

A Galactic Binary Detection Pipeline

The Galaxy is suspected to contain hundreds of millions of binary white dwarf systems, a large fraction of which will have sufficiently small orbital period to emit gravitational radiation in band for space-based gravitational wave detectors such as the Laser Interferometer Space Antenna (LISA). LISA's main science goal is the detection of cosmological events (supermassive black hole mergers, etc.) however the gravitational signal from the galaxy will be the dominant contribution to the data - including instrumental noise over approximately two decades in frequency. The catalogue of detectable binary systems will serve as an unparalleled means of studying the Galaxy. Furthermore, to maximize the scientific return from the mission, the data must be "cleansed" of the galactic foreground. We will present an algorithm that can accurately resolve and subtract 2:: 10000 of these sources from simulated data supplied by the Mock LISA Data Challenge Task Force. Using the time evolution of the gravitational wave frequency, we will reconstruct the position of the recovered binaries and show how LISA will sample the entire compact binary population in the Galaxy.

Littenberg, Tyson B.↗

A Detection Pipeline for Galactic Binaries in LISA Data

The Galaxy is suspected to contain hundreds of millions of binary white dwarf systems, a large fraction of which will have sufficiently small orbital period to emit gravitational radiation in band for space-based gravitational wave detectors such as the Laser Interferometer Space Antenna (LISA). LISA's main science goal is the detection of cosmological events (supermassive black hole mergers) etc.) however the gravitational signal from the galaxy will be the dominant contribution to the data - including instrumental noise - over approximately two decades in frequency. The catalogue of detectable binary systems will serve as an unparalleled means of studying the Galaxy. Furthermore, to maximize the scientific return from the mission, the data must be "cleansed" of the galactic foreground. We will present an algorithm that can accurately resolve and subtract greater than or equal to 10000 of these sources from simulated data supplied by the Mock LISA Data Challenge Task Force. Using the time evolution of the gravitational wave frequency, we will reconstruct the position of the recovered binaries and show how LISA will sample the entire compact binary population in the Galaxy.

Littenberg, Tyson B.↗

Internet Data Delivery for Future Space Missions

Ongoing work at National Aeronautics and Space Administration Goddard Space Flight Center (NASA/GSFC), seeks to apply standard Internet applications and protocols to meet the technology challenge of future satellite missions. Internet protocols and technologies are under study as a future means to provide seamless dynamic communication among heterogeneous instruments, spacecraft, ground stations, constellations of spacecraft, and science investigators. The primary objective is to design and demonstrate in the laboratory the automated end-to-end transport of files in a simulated dynamic space environment using off-the-shelf, low-cost, commodity-level standard applications and protocols. The demonstrated functions and capabilities will become increasingly significant in the years to come as both earth and space science missions fly more sensors and as the need increases for more network-oriented mission operations. Another element of increasing significance will be the increased cost effectiveness of designing, building, integrating, and operating instruments and spacecraft that will come to the fore as more missions take up the approach of using commodity-level standard communications technologies. This paper describes how an IP (Internet Protocol)-based communication architecture can support all existing operations concepts and how it will enable some new and complex communication and science concepts. The authors identify specific end-to-end data flows from the instruments to the control centers and scientists, and then describe how each data flow can be supported using standard Internet protocols and applications. The scenarios include normal data downlink and command uplink as well as recovery scenarios for both onboard and ground failures. The scenarios are based on an Earth orbiting spacecraft with downlink data rates from 300 Kbps to 4 Mbps. Included examples are based on designs currently being investigated for potential use by the Global Precipitation Measurement (GPM) mission.

Rash, James↗

PDS Lunar Data Node Restoration of Apollo In-Situ Surface Data

The Apollo missions between 1969 and 1972 deployed scientific instruments on the Moon's surface which made in-situ measurements of the lunar environment. Apollo II had the short-term Early Apollo Surface Experiments Package (EASEP) and Apollos 12, 14, 15, 16, and 17 each set up an Apollo Lunar Surface Experiments Package (ALSEP). Each ALSEP package contained a different suite of instruments which took measurements and radioed the results back to Earth over periods from 5 to 7 years until they were turned off on 30 September 1977. To this day the ALSEP data remain the only long-term in-situ information on the Moon's surface environment. The Lunar Data Node (LDN) has been formed under the auspices of the Planetary Data System (PDS) Geosciences Node to put relevant, scientifically important Apollo data into accessible digital form for use by researchers and mission planners. We will report on progress made since last year and plans for future data restorations.

Williams, David R.↗

Prediction of Lunar Reconnaissance Orbiter Reaction Wheel Assembly Angular Momentum Using Regression Analysis

This study determines the feasibility of creating a tool that can accurately predict Lunar Reconnaissance Orbiter (LRO) reaction wheel assembly (RWA) angular momentum, weeks or even months into the future. LRO is a three-axis stabilized spacecraft that was launched on June 18, 2009. While typically nadir-pointing, LRO conducts many types of slews to enable novel science collection. Momentum unloads have historically been performed approximately once every two weeks with the goal of maintaining system total angular momentum below 70 Nms; however flight experience shows the models developed before launch are overly conservative, with many momentum unloads being performed before system angular momentum surpasses 50 Nms. A more accurate model of RWA angular momentum growth would improve momentum unload scheduling and decrease the frequency of these unloads. Since some LRO instruments must be deactivated during momentum unloads and in the case of one instrument, decontaminated for 24 hours there after a decrease in the frequency of unloads increases science collection. This study develops a new model to predict LRO RWA angular momentum. Regression analysis of data from October 2014 to October 2015 was used to develop relationships between solar beta angle, slew specifications, and RWA angular momentum growth. The resulting model predicts RWA angular momentum using input solar beta angle and mission schedule data. This model was used to predict RWA angular momentum from October 2013 to October 2014. Predictions agree well with telemetry; of the 23 momentum unloads performed from October 2013 to October 2014, the mean and median magnitude of the RWA total angular momentum prediction error at the time of the momentum unloads were 3.7 and 2.7 Nms, respectively. The magnitude of the largest RWA total angular momentum prediction error was 10.6 Nms. Development of a tool that uses the models presented herein is currently underway.

LRO↗

Space station commonality analysis

This study was conducted on the basis of a modification to Contract NAS8-36413, Space Station Commonality Analysis, which was initiated in December, 1987 and completed in July, 1988. The objective was to investigate the commonality aspects of subsystems and mission support hardware while technology experiments are accommodated on board the Space Station in the mid-to-late 1990s. Two types of mission are considered: (1) Advanced solar arrays and their storage; and (2) Satellite servicing. The point of departure for definition of the technology development missions was a set of missions described in the Space Station Mission Requirements Data Base. (MRDB): TDMX 2151 Solar Array/Energy Storage Technology; TDMX 2561 Satellite Servicing and Refurbishment; TDMX 2562 Satellite Maintenance and Repair; TDMX 2563 Materials Resupply (to a free-flyer materials processing platform); TDMX 2564 Coatings Maintenance Technology; and TDMX 2565 Thermal Interface Technology. Issues to be addressed according to the Statement of Work included modularity of programs, data base analysis interactions, user interfaces, and commonality. The study was to consider State-of-the-art advances through the 1990s and to select an appropriate scale for the technology experiments, considering hardware commonality, user interfaces, and mission support requirements. The study was to develop evolutionary plans for the technology advancement missions.

Source record↗

Data catalog series for space science and applications flight missions. Volume 1A: Descriptions of planetary and heliocentric spacecraft and investigations, second edition

The main purpose of the data catalog series is to provide descriptive references to data generated by space science flight missions. The data sets described include all of the actual holdings of the Space Science Data Center (NSSDC), all data sets for which direct contact information is available, and some data collections held and serviced by foreign investigators, NASA and other U.S. government agencies. This volume contains narrative descriptions of planetary and heliocentric spacecraft and associated experiments. The following spacecraft series are included: Mariner, Pioneer, Pioneer Venus, Venera, Viking, Voyager, and Helios. Separate indexes to the planetary and interplanetary missions are also included.

Cameron, Winifred Sawtell↗

Voyager at Saturn

The spacecraft design and operations and mission results of the Voyager Project are reviewed with particular emphasis on the results of the Saturn encounters. The mission was undertaken by two spacecraft: Voyager 2, launched first on August 20, 1977 on a lower energy trajectory to Jupiter, Saturn, Uranus and Neptune; and Voyager 1, launched on September 5, 1977 on a higher energy trajectory to closer flybys of Jupiter and Saturn. The Voyager spacecraft make use of earlier Mariner and Viking Orbiter design concepts, with additional capabilities for solar independent power, long-range communications and autonomy as well as equipment for the 11 science investigations. The Voyager operations system consists of a ground data system, missions operations system, and support by the Mission Control and Computer Center and Deep Space Network. Among the results of the Jupiter encounter are data concerning the magnetospheric structure and atmospheric dynamics of the planet and the surface features of the Galilean satellites. The encounters with Saturn produced scientific data concerning wind speeds, auroral emissions, and radio emissions from the planet, the fine structure of the previously known and newly discovered rings, the surface features of the satellites and the atmospheric composition and conditions of Titan. Voyager 1 is presently making field and particle measurements on its flight into interstellar space, while Voyager 2 is headed for an encounter with Uranus in January 1986 and Neptune in August 1989.

Heacock, R. L.↗

A Whale of a Tale: Creating Spacecraft Telemetry Data Analysis Products for the Deep Impact Mission

A description of the Whale product generation utility and its means of analyzing project data for Deep Impact Missions is presented. The topics include: 1) Whale Definition; 2) Whale Overview; 3) Whale Challenges; 4) Network Configuration; 5) Network Diagram; 6) Whale Data Flow: Design Decisions; 7) Whale Data Flow Diagram; 8) Whale Data Flow; 9) Whale Team and Users; 10) Creeping Requirements; 11) Whale Competition; 12) Statistics: Processing Time; 13) CPU and Disk Usage; 14) The Ripple Effect of More Data; and 15) Data Validation and the Automation Challenge.

ground data systems↗

LDCM Preliminary Thermal Trades

The expected cost of adding thermal bands to the next generation Landsat Data Continuity Mission (LDCM) could be significant. This viewgraph presentation investigates both traditional cooled cross-track scanners and new architectures (cooled and uncooled) which could enable a low cost thermal capability. The presentation includes surveys of applications of Landsat thermal data and the architecture of thermal instruments. It also covers new thermal architecture sensor trades, ALI Architecture with Uncooled TIR Detectors, and simulated thermal imagery.

Ryan, Robert↗

Security Vulnerability Profiles of NASA Mission Software: Empirical Analysis of Security Related Bug Reports

NASA develops, runs, and maintains software systems for which security is of vital importance. Therefore, it is becoming an imperative to develop secure systems and extend the current software assurance capabilities to cover information assurance and cybersecurity concerns of NASA missions. The results presented in this report are based on the information provided in the issue tracking systems of one ground mission and one flight mission. The extracted data were used to create three datasets: Ground mission IVV issues, Flight mission IVV issues, and Flight mission Developers issues. In each dataset, we identified the software bugs that are security related and classified them in specific security classes. This information was then used to create the security vulnerability profiles (i.e., to determine how, why, where, and when the security vulnerabilities were introduced) and explore the existence of common trends. The main findings of our work include:- Code related security issues dominated both the Ground and Flight mission IVV security issues, with 95 and 92, respectively. Therefore, enforcing secure coding practices and verification and validation focused on coding errors would be cost effective ways to improve mission's security. (Flight mission Developers issues dataset did not contain data in the Issue Category.)- In both the Ground and Flight mission IVV issues datasets, the majority of security issues (i.e., 91 and 85, respectively) were introduced in the Implementation phase. In most cases, the phase in which the issues were found was the same as the phase in which they were introduced. The most security related issues of the Flight mission Developers issues dataset were found during Code Implementation, Build Integration, and Build Verification; the data on the phase in which these issues were introduced were not available for this dataset.- The location of security related issues, as the location of software issues in general, followed the Pareto principle. Specifically, for all three datasets, from 86 to 88 the security related issues were located in two to four subsystems.- The severity levels of most security issues were moderate, in all three datasets.- Out of 21 primary security classes, five dominated: Exception Management, Memory Access, Other, Risky Values, and Unused Entities. Together, these classes contributed from around 80 to 90 of all security issues in each dataset. This again proves the Pareto principle of uneven distribution of security issues, in this case across CWE classes, and supports the fact that addressing these dominant security classes provides the most cost efficient way to improve missions' security. The findings presented in this report uncovered the security vulnerability profiles and identified the common trends and dominant classes of security issues, which in turn can be used to select the most efficient secure design and coding best practices compiled by the part of the SARP project team associated with the NASA's Johnson Space Center. In addition, these findings provide valuable input to the NASA IVV initiative aimed at identification of the two 25 CWEs of ground and flight missions.

vulnerability↗

Mitigating Headward Fluid Shifts with Venoconstrictive Thigh Cuffs during Spaceflight

Venoconstrictive thigh cuffs (VTC) are a mechanical countermeasure capable of attenuating the spaceflight induced headward fluid shift, and thus may be a viable spaceflight associated neuro-ocular syndrome (SANS) countermeasure. Crewmembers can use VTC to mitigate the headward fluid shift to aid in adapting to spaceflight. However, data are needed to determine if VTC affect ocular structures. PURPOSE The purpose of this study is to determine the efficacy of long duration use of VTC application to mitigate the spaceflight-induced headward fluid shift. We hypothesize that a VTC countermeasure will temporarily reverse the headward fluid shift and attenuate spaceflight-induced changes of internal jugular vein (IJV) cross-sectional area, IJV pressure, stroke volume, cardiac output, intraocular pressure (IOP), and optic nerve head and retinal morphology. METHODS This study will evaluate the effectiveness of VTC countermeasure application on the headward fluid shift, as well as cardiovascular and ocular variables. VTC during spaceflight will be worn for an extended duration (up to 6 hours) with data collected at three time points (30 minutes, 3 hours, and 6 hours) to characterize the temporal profile of key fluid shift outcome measures of the vascular fluid shift, IOP, and ocular structure changes. Ten astronauts will be recruited to participate and will be studied before and during approximately 180-day International Space Station (ISS) spaceflight missions. Baseline data collection will occur approximately 90-days before launch (Figure). Preflight, each leg of the crewmember will be measured to determine the VTC cuff size and a cuff fit check session will occur prior to the preflight baseline ground imaging to verify the appropriate fit measured via a surface contact pressure. Prior to donning the VTC, baseline measures without VTC will be collected seated, supine, and supine followed by data collection with the VTC. The baseline data collection will include ultrasound (IJV area and pressure, stroke volume and cardiac output), brachial blood pressure and heart rate, optical coherence tomography (OCT) imaging (total retinal thickness and choroid thickness), and IOP. An inflight cuff fit check session, same as the preflight fit check, will occur prior to VTC use on ISS. The inflight VTC experiment will be conducted early (FD45) and late (R-45) to determine if mission duration affects VTC fit and the efficacy of fluid redistribution. A system usability scale comfort questionnaire will be included in each VTC session to capture feedback from crewmembers regarding the comfort and usability of the VTC. SCIENTIFIC & MISSION IMPACT Results will narrow knowledge gaps described in the Human Research Roadmap to mitigate the headward fluid shift during spaceflight and help NASA to 1) determine the efficacy of extended use VTC application to mitigate the spaceflight-induced headward fluid shift and 2) further the understanding of the use of VTC on vascular fluid shifts, IOP, and ocular structure during spaceflight. Supported by NASA Human Research Program Directed Research. Figure. Detailed Testing Schedule. Baseline data collection at L-90 will be performed in a randomized order of position.

J V Jasien↗