Search NASA⌕ Search

SEARCH · Search NASA

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 253 records · Page 14

NASA’s SLS (Space Launch System) Rocket Ready for Artemis II Lunar Mission

In early 2026, NASA will launch the Artemis II mission, an approximately 10-day long lunar mission that will fly three NASA astronauts and one CSA (Canadian Space Agency) astronaut on a free-return trajectory around the Moon, following a one-day checkout of their Orion spacecraft in Earth orbit. The mission will be the first to launch astronauts aboard NASA’s Orion spacecraft and on top of the agency’s SLS (Space Launch System) rocket. The mission will also deploy four 12U CubeSats as secondary payloads from the Orion stage adapter, following Orion separation and departure. The payloads, developed by four of NASA’s international partners, will perform a variety of science and technology investigations. The SLS and Orion for the mission are currently stacked in the Vehicle Assembly Building (VAB) at NASA’s Kennedy Space Center in Florida and are undergoing final preparations to rollout to Launch Pad 39B for a tanking test before launch. In addition to preparations for the Artemis II mission, significant progress is being made on the SLS for the Artemis III mission, which is targeted to return astronauts to the lunar surface no later than 2029. Major components of the core stage and solid rocket boosters are already at NASA Kennedy undergoing build-up for the mission. Data from the Artemis II launch and mission, as well as progress to subsequent missions, as available, will be presented.

Bruce R Askins↗

NASA’s SLS (Space Launch System) Rocket Ready for Artemis II Lunar Mission

In early 2026, NASA will launch the Artemis II mission, an approximately 10-day long lunar mission that will fly three NASA astronauts and one CSA (Canadian Space Agency) astronaut on a free-return trajectory around the Moon, following a one-day checkout of their Orion spacecraft in Earth orbit. The mission will be the first to launch astronauts aboard NASA’s Orion spacecraft and on top of the agency’s SLS (Space Launch System) rocket. The mission will also deploy four 12U CubeSats as secondary payloads from the Orion stage adapter, following Orion separation and departure. The payloads, developed by four of NASA’s international partners, will perform a variety of science and technology investigations. The SLS and Orion for the mission are currently stacked in the Vehicle Assembly Building (VAB) at NASA’s Kennedy Space Center in Florida and are undergoing final preparations to rollout to Launch Pad 39B for a tanking test before launch. In addition to preparations for the Artemis II mission, significant progress is being made on the SLS for the Artemis III mission, which is targeted to return astronauts to the lunar surface no later than 2029. Major components of the core stage and solid rocket boosters are already at NASA Kennedy undergoing build-up for the mission. Data from the Artemis II launch and mission, as well as progress to subsequent missions, as available, will be presented.

Bruce Askins↗

High-Performance Data Analysis Tools for Sun-Earth Connection Missions

The data analysis tool of choice for many Sun-Earth Connection missions is the Interactive Data Language (IDL) by ITT VIS. The increasing amount of data produced by these missions and the increasing complexity of image processing algorithms requires access to higher computing power. Parallel computing is a cost-effective way to increase the speed of computation, but algorithms oftentimes have to be modified to take advantage of parallel systems. Enhancing IDL to work on clusters gives scientists access to increased performance in a familiar programming environment. The goal of this project was to enable IDL applications to benefit from both computing clusters as well as graphics processing units (GPUs) for accelerating data analysis tasks. The tool suite developed in this project enables scientists now to solve demanding data analysis problems in IDL that previously required specialized software, and it allows them to be solved orders of magnitude faster than on conventional PCs. The tool suite consists of three components: (1) TaskDL, a software tool that simplifies the creation and management of task farms, collections of tasks that can be processed independently and require only small amounts of data communication; (2) mpiDL, a tool that allows IDL developers to use the Message Passing Interface (MPI) inside IDL for problems that require large amounts of data to be exchanged among multiple processors; and (3) GPULib, a tool that simplifies the use of GPUs as mathematical coprocessors from within IDL. mpiDL is unique in its support for the full MPI standard and its support of a broad range of MPI implementations. GPULib is unique in enabling users to take advantage of an inexpensive piece of hardware, possibly already installed in their computer, and achieve orders of magnitude faster execution time for numerically complex algorithms. TaskDL enables the simple setup and management of task farms on compute clusters. The products developed in this project have the potential to interact, so one can build a cluster of PCs, each equipped with a GPU, and use mpiDL to communicate between the nodes and GPULib to accelerate the computations on each node.

Messmer, Peter↗

Practical Application of Model-based Programming and State-based Architecture to Space Missions

Innovative systems and software engineering solutions are required to meet the increasingly challenging demands of deep-space robotic missions. While recent advances in the development of an integrated systems and software engineering approach have begun to address some of these issues, they are still at the core highly manual and, therefore, error-prone. This paper describes a task aimed at infusing MIT's model-based executive, Titan, into JPL's Mission Data System (MDS), a unified state-based architecture, systems engineering process, and supporting software framework. Results of the task are presented, including a discussion of the benefits and challenges associated with integrating mature model-based programming techniques and technologies into a rigorously-defined domain specific architecture.

state analysis↗

WEDDS: The WITS Encrypted Data Delivery System

WEDDS, the WITS Encrypted Data Delivery System, is a framework for supporting distributed mission operations by automatically transferring sensitive mission data in a secure and efficient manner to and from remote mission participants over the internet.

public key cryptography encryption authentication ↗

Physical Oceanography Distributed Active Archive Center

This new TOPEX/POSEIDON product provides the full mission data set in a new format with many data quality improvements brought about by the work of many scientists during the mission. It is a revised form to the MGDR-A CD-ROM set which covered data from the beginning of the mission, Septermber 22, 1992 to April 23, 1996.

TOPEX/POSEIDON Oceanography↗

Science Archives in the 21st Century: A NASA LAMBDA Report

Lambda is a thematic data center that focuses on serving the cosmic microwave background (CMB) research community. LAMBDA is an active archive for NASA's Cosmic Background Explorer (COBE) and Wilkinson Microwave Anisotropy Probe (WMAP) mission data sets. In addition, LAMBDA provides analysis software, on-line tools, relevant ancillary data and important web links. LAMBDA also tries to preserve the most important ground-based and suborbital CMB data sets. CMB data is unlike other astrophysical data, consisting of intrinsically diffuse surface brightness photometry with a signal contrast of the order 1 part in 100,000 relative to the uniform background. Because of the extremely faint signal levels, the signal-to-noise ratio is relatively low and detailed instrument-specific knowledge of the data is essential. While the number of data sets being produced is not especially large, those data sets are becoming large and complex. That tendency will increase when the many polarization experiments currently being deployed begin producing data. The LAMBDA experience supports many aspects of the NASA data archive model developed informally over the last ten years-that small focused data centers are often more effective than larger more ambitious collections, for example; that data centers are usually best run by active scientists; that it can be particularly advantageous if those scientists are leaders in the use of the archived data sets; etc. LAMBDA has done some things so well that they might provide lessons for other archives. A lot of effort has been devoted to developing a simple and consistent interface to data sets, for example; and serving all the documentation required via simple 'more' pages and longer explanatory supplements. Many of the problems faced by LAMBDA will also not surprise anyone trying to manage other space science data. These range from persuading mission scientists to provide their data as quickly as possible, to dealing with a high volume of nuisance (spam) messages. Because so many data center problems and solutions are common across individual data centers and disciplines it would be very valuable to establish some new systems of communication - such as informal email lists for administrators and developers. But resources are very limited, so new timeconsuming and inefficient mechanisms - like too-frequent and too-structured meetingsshould be avoided. Although there are great advantages to being small, agile and independent, there are also some areas where science data centers within and without NASA could be better coordinated - for the assignment of persistent identifiers; to encourage the early adoption of useful standards and technologies; etc. Some super-structure to facilitate such coordination might be beneficial as long as it doesn't begin to control the other work of the archives, and become a "methodology police". In this respect the CCSDS "Reference Model for an Open Archive Information System" is a little worrying. It may be that the closer a data center gets to following such a detailed prescription, the less effective it will become. It is much better to have an informal coordination process than a bureaucratic straight-jacket.

Butterworth, P.↗

Practical Application of Model-based Programming and State-based Architecture to Space Missions

A viewgraph presentation to develop models from systems engineers that accomplish mission objectives and manage the health of the system is shown. The topics include: 1) Overview; 2) Motivation; 3) Objective/Vision; 4) Approach; 5) Background: The Mission Data System; 6) Background: State-based Control Architecture System; 7) Background: State Analysis; 8) Overview of State Analysis; 9) Background: MDS Software Frameworks; 10) Background: Model-based Programming; 10) Background: Titan Model-based Executive; 11) Model-based Execution Architecture; 12) Compatibility Analysis of MDS and Titan Architectures; 13) Integrating Model-based Programming and Execution into the Architecture; 14) State Analysis and Modeling; 15) IMU Subsystem State Effects Diagram; 16) Titan Subsystem Model: IMU Health; 17) Integrating Model-based Programming and Execution into the Software IMU; 18) Testing Program; 19) Computationally Tractable State Estimation & Fault Diagnosis; 20) Diagnostic Algorithm Performance; 21) Integration and Test Issues; 22) Demonstrated Benefits; and 23) Next Steps

Mission Data System (MDS)↗

Some examples of the utility of HCMM data in geologic remote sensing

Examples of HCMM (Heat Capacity Mapping Mission) data in geologic remote sensing are presented, and the data set is composed of HCMM and aircraft digital scanner data and ground truth data from four western U.S. test sites. Data are used in the thermal model to test thermal data effectiveness, and changes in temperature with depth and time for dry soils are described by the model. It is found that the HCMM thermal inertia image is useful in the separability of bedrock and alluvium in Death Valley, and aa and pahoehoe flows in the Pisgah basalt flow. In a color composite of HCMM day temperature, night temperature, and day visible images of the Pisgah Crater test site, it is possible to distinguish alluvium, playa, aa and pahoehoe basalt flow, rhyolite intrusives, and other elements. Ground checking of units at a few points will extend capabilities to large areas and assist in creating telegeologic maps.

Kahle, A. B.↗

The Seasat algorithm development facility at JPL

The Seasat-A spacecraft, scheduled for launch in May 1978, will produce a global ocean data set covering a one-year nominal mission. Because this is a proof-of-concept mission, data processing algorithms are expected to evolve as the data base grows. To support the evolution and evaluation of algorithms, and to experiment with various techniques for processing the data, an algorithm development facility (ADF) is being developing. The ADF will provide access to the data base and to highly modularized processing programs. The processing programs will be subject to easy and frequent modification by a remote user community of sensor managers and experiment teams, who will use this capability to evaluate the overall performance of the sensors and the algorithms using surface truth data. The ADF concepts of software standardization and interface control are expected to have general applicability for adaptive data processing systems.

Brown, J. W.↗

Canadian Attitude Sensing Experimental Package (CASEP)

The Canadian Attitude Sensing Experiment Package (CASEP) was designed to demonstrate and verify the operation of an attitude sensing subsystem prior to committing its use on an operational mission. Data telemetry/recording requirements, power and physical requirements, and mission requirements of the experiment package are defined.

Reynaud, A. H.↗

CCSDS - An approach to the definition of common standards for understanding space-related data

International cooperation for space data projects requires common data processing goals and unique data exchange mechanisms. The absence of standards has led to project unique interface definitions and special software on diverse systems. To address this problem, CCSDS Panel 2 is creating a set of standards to support self description of data using standard structures. The proposed standard data interchange mechanism - the Standard Formatted Data Unit (SFDU) - reduces information loss in data transfers, increases automated information exchange, and extends the lifetime of data. Data interchange structures, languages, and services are being developed with necessary control functions to provide these benefits. A set of recommendations for agency review has been issued this year to be the basis for future data exchange and to enhance access to older mission data sets. Space agencies and other space data handling facilities are being encouraged to implement the SFDU concept for ongoing and planned projects.

Drexler, Manfred↗

Towards Inner Magnetosphere Particle and Field Models

We report on the initial stages of an effort to construct comprehensive empirical models of the plasma and fields in the inner magnetosphere. The models are based not only on archival data (e.g., SCATHA) but also on current spacecraft mission data (e.g., POLAR). In this component of the effort, we incorporate the recently archived data provided by the SCATRA (Spacecraft Charging AT High Altitude) satellite. The SCAT14A satellite was in a near-geostationary orbit and was in operation for more than a decade. In this paper, we focus on the SCATRA plasma and magnetic field data from approximately the first two years of operation. The time-series data are binned according to spatial location and geomagnetic activity. Examples of statistical, empirical models from this initial effort are presented; even the simply-constructed preliminary models reveal such subtle features as the previously reported warm (greater than 100 eV) plasma density enhancement near the magnetic equator.

Spence, H. E.↗

Quantification of In-flight Physical Changes: Anthropometry and Neutral Body Posture

Currently, NASA does not have sufficient in-flight anthropometric data gathered to assess the impact of physical body shape and size changes on suit sizing. For developing future planetary and reduced gravity suits, NASA needs to quantify the impacts of microgravity on anthropometry, body posture, and neutral body postures (NBP) to ensure optimal crew performance, fit, and comfort. To obtain these impacts, anthropometric data, circumference, length, height, breadth, and depth for body segments (i.e. chest, waist, bicep, thigh, calf) from astronauts for pre, in-, and postflight conditions needs to be collected. Once this data has been collected, a comparison between pre, in-, and postflight anthropometric values will be analyzed, yielding microgravity factors. The NBP will be used to determined body posture (joint angle) changes between subjects throughout the duration of a mission. Data collection, starting with Increments 37/38, is still in progress with the completion of 3 out of 12 subjects. NASA suit engineers and NASA's Extravehicular Activity (EVA) Project Office have identified that suit fit in microgravity could become an issue. It has been noted that crewmembers often need to adjust their suit sizing once they are in orbit. This adjustment could be due to microgravity effects on anthropometry and postural changes, and is necessary to ensure optimal crew performance, fit, and comfort in space. To date, the only data collected to determine the effects of microgravity on physical human changes have been during Skylab, STS-57, and a recent HRP study on seated height changes due to spinal elongation (Spinal Elongation, Master Task List [MTL] #221). The Skylab and the STS-57 studies found that there is a distinct neutral body posture (NBP) based on photographs. The still photographs showed that there is a distinguishable posture with the arms raised and the shoulder abducted; and, in addition, the knees were flexed with noticeable hip flexion and the foot plantar flexed [1,2]. This is the one standard set of body joint angles for a NBP in microgravity. A recent simulated microgravity NBP study [3] has shown an individual variability and inconsistencies in defining NBP. This variation may be influenced by spinal growth, the type of suit fit, and other potential anthropometry factors such as spinal curvature, age, and gender. The variation aspect of this essential data is required for all kinds of space device designs (e.g. suits, habitat, mobility aids, etc.). The method proposed considers the dynamic nature of body movement and will use a measurement technique to continually monitor posture and develop a probability likelihood of the natural posture and how the NBP postures are affected by anthropometry. Additionally, Skylab studies found that crewmembers experienced a stature growth of up to 3%. The data included 3 crewmembers that showed that there is a bi-phasic stature growth once the crew enters into weightlessness. However, the Spinal Elongation study identified that the crewmembers could experience about a 6% growth in seated height and a 3% stature growth, when exposed to microgravity. The results prove that not all anthropometric measurements have the same microgravity percent growth factor. For EVA and suit engineers to properly update the sizing protocol for microgravity, they need additional anthropometric data from space missions. Hence, this study is aimed to gather additional in-flight anthropometric measurements, such as length, depth, breadth, and circumference, to determine the changes to body shape and size due to microgravity effects. It is anticipated that by recording the potential changes to body shape and size, a better suit sizing protocol will be developed for ISS and other space missions. In essence, this study will help NASA quantify the impacts of microgravity on anthropometry to ensure optimal crew performance, fit, and comfort. This study will use simplistic data collection techniques, 3D laser scanning, digital still, and video data, and perform photogrammetric analyses to determine the changes that occur to the body shape, size, and NBP when exposed to a microgravity environment.

Young, K. S.↗

Spacelab-3 low-g accelerometer data from the fluid experiments system (FES)

The Fluids Experiment System (FES) flown aboard Spacelab 3 contained a Miniature Electrostatic Accelerometer (MESA). This accelerometer was purchased from Bell Aerospace, Textron and had three range (auto switching), bidirectional, three orthogonal axis capability. BGB, Inc. is in the process of examining the total mission data from this instrument. From these data, areas of interest are identified and related back to mission events. The basic format of the data for the total mission is root mean square (RMS), with two hours per plot.

Arnett, Gary↗

Horizontally Integrated Informatics to Support Science Operations in Human Spaceflight

Many systems will be designed and developed for the Artemis program. A subset of these systems will be relevant to scientific activities conducted during the program, but it is important to consider that these scientific activities will be conducted within the context of the larger program. Thinking about the program data holistically, and deliberately structuring its data products in a way that preserves the data’s mission context will enable new opportunities for real-time science support, and long-term analysis of the mission and its data for generations to come (see [1] for an example). Here, we show that horizontally integrated mission data products are valuable by describing the SSERVI RISE2 field program. Temporally contextualized data introduces relationships that do not need to be predefined. One field that greatly benefits from freeform relationship building between disparate datasets is anomaly investigation, where investigators need to follow lines of evidence that may not be a priori apparent. Building relationships between data enables accident investigators to react faster to time-sensitive incidents during EVA operation and other critical human spaceflight activities. Another advantage is the long-term data preservation that enables unplanned or yet-to-be conceived applications or study of this data many years in the future. As Artemis activities become more defined, having a horizontally integrated data management plan will be paramount to ensuring successful mission context is captured for generations to come.

B F Feist↗

Flight Results of the Chandra X-ray Observatory Inertial Upper Stage Space Mission

Under contract to NASA, a specially configured version of the Boeing developed Inertial Upper Stage (IUS) booster was provided by Boeing to deliver NASA's 1.5 billion dollar Chandra X-Ray Observatory satellite into a highly elliptical transfer orbit from a Shuttle provided circular park orbit. Subsequently, the final orbit of the Chandra satellite was to be achieved using the Chandra Integral Propulsion System (IPS) through a series of IPS burns. On 23 July 1999 the Shuttle Columbia (STS-93) was launched with the IUS/Chandra stack in the Shuttle payload bay. Unfortunately, the Shuttle Orbiter was unexpectantly inserted into an off-nominal park orbit due to a Shuttle propulsion anomaly occurring during ascent. Following the IUS/Chandra on-orbit deployment from the Shuttle, at seven hours from liftoff, the flight proven IUS GN&C system successfully injected Chandra into the targeted transfer orbit, in spite of the off-nominal park orbit. This paper describes the IUS GN&C system, discusses the specific IUS GN&C mission data load development, analyses and testing for the Chandra mission, and concludes with a summary of flight results for the IUS part of the Chandra mission.

Tillotson, R.↗

Lunar Solar Origins Exploration (LunaSOX)

The Moon offers a unique vantage point from which to investigate the Sun and its interaction via the solar wind magnetic fields, plasma, and energetic particles with the geospace system including the Moon itself. The lunar surface and exosphere provide in part a record of solar coronal plasma material input and resultant space weathering over billions of years. The structure and dynamics of solar wind interactions with the Moon provide an accessible near-Earth laboratory environment for study of general solar wind interactions with the vast multitude of airless asteroidal bodies of the inner solar system. Spacecraft in lunar orbit have the often simultaneous opportunity, except when in the Earth's magnetosphere, to make in-situ compositional measurements of the solar wind plasma and to carry out remote observations from the Moon of the solar corona, potentially enabled by lunar limb occultation of the solar disk. The LunaSOX project at NASA Goddard Space Flight Center is addressing these heliophysical science objectives from and of the Moon with support from NASA's Lunar Advanced Science and Exploration Research (LASER) program: (1) specify history of solar wind parameters at and sunward of the Moon through enhanced access (http://lunasox.gsfc.nasa.gov/) to legacy and operational mission data products from the Apollo era to the present, (2) model field and plasma interactions with the lunar surface, exosphere, and wake, as constrained by the available data, through hybrid kinetic code simulations, and (3) advance mission concepts for heliophysics from and of the Moon.

Cooper, John F.↗