Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “multiple building systems”

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 397 records · Page 22

International Space Station as a Development Testbed for Advanced Environmental Control and Life Support Systems

Since the beginning of human spaceflight, mission durations have steadily increased. Current mission durations onboard the International Space Station are multiple months, but future exploration missions to cislunar space and beyond will require multiple year durations. In addition, missions to cislunar or deep space will encounter a much harsher environment than the current ISS low-earth orbit missions, with relation to radiation, isolation, and lack of timely available support from Earth. To meet the challenges of deep space, so-called "exploration missions" will require Environmental Control and Life Support systems with higher performance, lower mass and logistics requirements, and more endurance than are possible with current operational systems on board the International Space Station. As a currently operational human-occupied platform, the International Space Station presents a unique opportunity to act as a testbed for development of advanced next-generation Environmental Control and Life Support Systems, such that these systems may be tested, proven, and refined for eventual deployment on deep space human exploration missions. This paper will outline the history, progress to date, and future plans for efforts to design, select, build, test and fly Advanced Environmental Control and Life Support Systems on the ISS.

Shaw, Laura A.↗

Updated Orbital Monitoring and Dynamical Masses for Nearby M-dwarf Binaries

Young M-type binaries are particularly useful for precise isochronal dating by taking advantage of their extended pre-main sequence evolution. Orbital monitoring of these low-mass objects becomes essential in constraining their fundamental properties, as dynamical masses can be extracted from their Keplerian motion. Here, we present the combined efforts of the AstraLux Large Multiplicity Survey, together with a filler sub-programme from the SpHere INfrared Exoplanet (SHINE) project and previously unpublished data from the FastCam lucky imaging camera at the Nordical Optical Telescope (NOT) and the NaCo instrument at the Very Large Telescope (VLT). Building on previous work, we use archival and new astrometric data to constrain orbital parameters for 20 M-type binaries. We identify that eight of the binaries have strong Bayesian probabilities and belong to known young moving groups (YMGs). We provide a first attempt at constraining orbital parameters for 14 of the binaries in our sample, with the remaining six having previously fitted orbits for which we provide additional astrometric data and updated Gaia parallaxes. The substantial orbital information built up here for four of the binaries allows for direct comparison between individual dynamical masses and theoretical masses from stellar evolutionary model isochrones, with an additional three binary systems with tentative individual dynamical mass estimates likely to be improved in the near future. We attained an overall agreement between the dynamical masses and the theoretical masses from the isochrones based on the assumed YMG age of the respective binary pair. The two systems with the best orbital constrains for which we obtained individual dynamical masses, J0728 and J2317, display higher dynamical masses than predicted by evolutionary models.

Astrometry / binaries↗

NASA ACC High Energy Dynamic Impact Methodology and Outcomes

For High Energy Dynamic Impact (HEDI) events, testing to evaluate the structural response of primary aircraft structure for design and certification is both expensive and time consuming. This paper discusses current work seeking to assess, develop, and validate appropriate analytical models that accurately predict physical response, damage, and failure modes for large scale composite structures in HEDI events. Four state-of-the-art Progressive Damage Analysis (PDA) methods were employed for this phased project: LS-DYNA MAT162, LS-DYNA MAT261, Smoothed Particle Galerkin (SPG), and EMU Peridynamics. Multiple material systems were considered, namely T700/5208 textile-infusion triaxial braid, T800/AMD-825 textile-infusion triaxial braid, IM7/8552 uni-directional tape, and SPG 196-PW/8552 plain-weave fabric. Extensive ballistic impact testing was performed to support this activity and measured results were compared to predictive models for assessment using panel delamination, panel displacement, force at the load cells, and threshold velocity as measures. Ultimately, the work under this activity provided significant progress in advancing the state-of-the-art in the use of PDA for HEDI events. Each material model had favorable performance comparing to test in some parameters and needed improvement in others. With the lessons learned from this activity, significant progress was made in the ability to predict panel behavior for a more general case beyond the flat panel in a ballistic impact event. Subsequent Phase II of the NASA ACC HEDI effort will continue to build on the coupon testing, flat panel ballistic impact testing, and analysis performed to-date with application of the PDA methods for intended material selections to test articles with greater complexity of configuration, curvature, and scale. It is not the intention of this paper to present a full set of data, but rather to give an overview of the NASA HEDI effort and show a small representative subset of the test and analysis results.

Hunziker, Kenneth J.↗

The Ares I-1 Flight Test--Paving the Road for the Ares I Crew Launch Vehicle

In accordance with the U.S. Vision for Space Exploration and the nation's desire to again send humans to explore beyond Earth orbit, NASA has been tasked to send human beings to the moon, Mars, and beyond. It has been 30 years since the United States last designed and built a human-rated launch vehicle. NASA is now building the Ares I crew launch vehicle, which will loft the Orion crew exploration vehicle into orbit, and the Ares V cargo launch vehicle, which will launch the Lunar Surface Access Module and Earth departure stage to rendezvous Orion for missions to the moon. NASA has marshaled unique resources from the government and private sectors to perform the technically and programmatically complex work of delivering astronauts to orbit early next decade, followed by heavy cargo late next decade. Our experiences with Saturn and the Shuttle have taught us the value of adhering to sound systems engineering, such as the "test as you fly" principle, while applying aerospace best practices and lessons learned. If we are to fly humans safely aboard a launch vehicle, we must employ a variety of methodologies to reduce the technical, schedule, and cost risks inherent in the complex business of space transportation. During the Saturn development effort, NASA conducted multiple demonstration and verification flight tests to prove technology in its operating environment before relying upon it for human spaceflight. Less testing on the integrated Shuttle system did not reduce cost or schedule. NASA plans a progressive series of demonstration (ascent), verification (orbital), and mission flight tests to supplement ground research and high-altitude subsystem testing with real-world data, factoring the results of each test into the next one. In this way, sophisticated analytical models and tools, many of which were not available during Saturn and Shuttle, will be calibrated and we will gain confidence in their predictions, as we gain hands-on experience in operating the first of two new launch vehicle systems. The Ares I-1 flight test vehicle (FTV) will incorporate a mix of flight and mockup hardware, reflecting a configuration similar in mass, weight, and shape (outer mold line or OML) to the operational vehicle. It will be powered by a four-segment reusable solid rocket booster (RSRB), which is currently in Shuttle inventory, and will be modified to include a fifth, inert segment that makes it approximately the same size and weight as the five segment RSRB, which will be available for the second flight test in 2012. The Ares I-1 vehicle configuration is shown. Each test flight has specific objectives appropriate to the design analysis cycle in progress. The Ares I-1 demonstration test, slated for April 2009, gives NASA its first opportunity to gather critical data about the flight dynamics of the integrated launch vehicle stack, understand how to control its roll during flight, and other characterize the severe stage separation environment that the upper stage will experience during future operational flights. NASA also will begin the process of modifying the launch infrastructure and fine-tuning ground and mission operational scenarios, as NASA transitions from the Shuttle to the Ares/Orion system.

Davis, Stephan R.↗

Desktop Application Program to Simulate Cargo-Air-Drop Tests

The DSS Application is a computer program comprising a Windows version of the UNIX-based Decelerator System Simulation (DSS) coupled with an Excel front end. The DSS is an executable code that simulates the dynamics of airdropped cargo from first motion in an aircraft through landing. The bare DSS is difficult to use; the front end makes it easy to use. All inputs to the DSS, control of execution of the DSS, and postprocessing and plotting of outputs are handled in the front end. The front end is graphics-intensive. The Excel software provides the graphical elements without need for additional programming. Categories of input parameters are divided into separate tabbed windows. Pop-up comments describe each parameter. An error-checking software component evaluates combinations of parameters and alerts the user if an error results. Case files can be created from inputs, making it possible to build cases from previous ones. Simulation output is plotted in 16 charts displayed on a separate worksheet, enabling plotting of multiple DSS cases with flight-test data. Variables assigned to each plot can be changed. Selected input parameters can be edited from the plot sheet for quick sensitivity studies.

Cuthbert, Peter↗

Monitoring Airspace Complexity and Determining Contributing Factors

The national airspace has evolved over many years to accommodate increased traffic demand [1] while simultaneously maintaining one of the safest forms of transportation [2], [3]. One of the reasons for this success is the ability of the system and the operators to adapt and accommodate to situations that routinely disrupt optimal operations. These situations may include: adverse weather, delays, early arrivals, equipment outages, and other factors that are outside the operators ability to control. These factors can lead to states where automation is unable to properly handle these issues and therefore air traffic controllers and pilots have to intervene, ultimately increasing communication between operators resulting in higher workload. As controller workload increases to handle sub-optimal operating conditions this can be viewed as an increase in complexity. The reasoning for this is because humans are now required to make tactical decisions in response to external factors, resulting in a departure from the strategic plan where operations would be more efficiently managed. Human operators control airspace complexity under rigid regulations that are constantly changing. The airspace is divided into sectors and the number of aircraft assigned to each controller is limited for safe handling. There has been past work that devised airspace complexity metrics in commercial aviation and related these metrics to controller workload (e.g., [4],[5]). The upper bounds on the system load are pre-determined. Such bounds on complexity make for a safe system, but the system cannot scale and adapt to autonomous, dense, and heterogeneous traffic, including the many types of Unmanned Aerial Vehicles (UAVs) envisioned to be added to the operations. We hypothesize that, as traffic density and heterogeneity grow, and other key metrics change, there will be phase transitions at which the way traffic should be managed changes significantly [6]. We offer a method for in-time detection of contributing factors that lead to phase transitions, characterized by increased complexity. To the best of our knowledge, there is no tool similar to our proposed effort that identifies such contributing factors or precursor patterns. To define the scope we are proposing to measure complexity from the viewpoint of the Terminal Radar Approach Control Facilities (TRACON) controller’s perspective. In particular we are analyzing arrivals into KSFO. With safety as the top concern for airspace operators, it is important to recognize that as density and heterogeneity grow, the focus of the system will change. Times of the day when the airspace has low density and heterogeneity, the flights will follow more efficient paths where the aircraft move on established routes that are more or less directly to the destination. However, when density and heterogeneity increases, the system will begin changing focus to avoiding conflicts and collisions and route the flights in a more flexible way. Higher flexibility requires more communication and coordination between controllers and pilots which the current automation is unable to handle. This paper proposes a novel approach that monitors airspace complexity at multiple scales, uses a Machine Learning-based tool that predicts when operations will transition to a regime of greater complexity, and identifies actions that can reduce the complexity while still maintaining efficient and safe operations. We demonstrate our proposed approach using data from multiple complementary sources. This includes, but is not limited to: historical aircraft surveillance data from NASA’s Sherlock Data Warehouse [7], METAR weather data, and airport configuration data from Aviation System Performance Metrics (ASPM). The surveillance data flight paths are sampled at a variable sample rate — increasing as the aircraft approaches the airport. This is due to how Sherlock manages flight track stitching between different radar facilities which have different sampling rates. The weather and performance data are logged at defined intervals throughout the day at a courser refresh rate. In addition to the logged data and metrics, we leverage pre-defined Standard Terminal Arrival Routes (STARs) procedures to characterize the path of each flight. Each flight files for one of these routes in the flight plan well before entering the terminal airspace, and approximately follows the route until it leaves the STAR, typically on the final fix of a runway transition. However, most flights do not always fly the full STAR procedure to completion [8], but the majority do adhere to the fixes within the common route of the procedure. Our approach leverages fixes in the common route of each of the STARs to build a reference path to the airport. This allows us to characterize the flight paths in what we are defining as the “maneuvering area” (the airspace between the STAR and before the flight is lined up on the runway’s final approach) to determine how off nominal the flights are to calculate its complexity score. Determining airspace complexity is a concept that does not have a concrete answer. In designing this metric, we consider what increases the workload for the air traffic controllers. Consequently more specialized vectoring maneuvers results in higher workload. Accordingly, we start with a theory: each flight has a direct path it takes from the STAR’s common route to the final approach’s outer marker fix for the flight’s landing runway. It is important to note that the direct path is only used as a reference. If the majority of the flights have a large consistent offset as compared to other routes it does not necessarily mean that those flights have higher complexity. We are merely building a distribution based on this direct path for that particular STAR and runway pair to determine the normal mode of operations for that route. Flights that are in the upper tail of these distributions will result in higher complexity scores and flights that fly in the median will represent the normal mode of operations and therefore will have lower complexity scores. Since flights following each STAR route take different paths to the airport, we have a different distribution for each STAR route and therefore can model these distributions to compute a complexity score from their respective normalized distributions. To evaluate the effectiveness of our proposed airspace complexity metric we will compare against an established approach based on trajectory clustering [9]. This unsupervised learning technique consists of the following steps: (1) identify the general maneuvering areas (waypoints) by performing $\kappa$-means or DBSCAN clustering on locations where aircraft frequently turn based on the surveillance radar track data, (2) map flight trajectories onto sequences of waypoints, and (3) cluster the sequences based on their common subsequences. From a high-level perspective, this baseline model learns nominal operations in the airspace through the sequence of waypoints that are representative of where aircraft change direction and defines deviations from the nominal operations as “complex.” Therefore, more deviations from the nominal operations correspond to higher complexity values. For our validation, we re-implemented this technique and tune model hyper-parameters to correctly detect waypoints for the arrival traffic into the San Francisco bay area. We will compute the complexity measure over a one-year period using our proposed technique as well as the baseline. Our validation will be based on each technique’s ability to detect a set of undesirable outcomes (e.g., go-arounds, holding patterns, average time in the airspace, etc.). Since our current complexity metric is derived from the offset from the direct reference path, it’s important to understand what causes these offsets. In many of the flights with high offset distance, flights performing holding patterns and S turns can be observed. These maneuvering tactics are utilized to add distance between the aircraft and the destination runway to prevent multiple flights from having conflicting arrival times. In order to predict a rise in complexity (or the precursor to complexity), it’s necessary to be able to identify these potential conflicts (which in turn, result in higher offsets). To do this, we define a “representative flight” for each STAR route and runway pair. This flight is approximately the path the flight would take if there was a clear path with no other flights in the airspace — including the time remaining to the airport. We first identify the flights for a given STAR runway pair using the offset to the reference path distributions that fall between the 44-55 percentiles. This yields the flights that conform to the most normal mode of operation. Each of these flights is partitioned based on the percent complete from the entry point into the maneuvering areas from 0\% – 100\% complete. Then for each percent “bin”, we take the median value of the flight’s latitude/longitude coordinates, airspeed, and (non causal) time remaining to the airport to construct a lookup table for each percent complete bin on a given route. As a flight enters the maneuvering area, we can find the estimated arrival time of a flight to the airport by finding the closest point to the representative path’s percent complete bin (relative to the flight’s current position at any snapshot in the airspace) and therefore retrieve the corresponding remaining time left on the “representative path”. We assume that the flight will follow the representative path to completion when deriving these estimates. We can then compare these estimated arrival times against other flights for the same snapshot in time to identify potential conflicts. If more flights are estimated to arrive within a tolerance window than there are runways available, then we have a potential conflict. We can use this derived measure along with other factors expected to add disruption to the operation such as weather and runway configuration changes as an input to machine learning tools to detect precursors that increases in our complexity measure. This novel method will assist in uncovering insights into the contributing factors that lead to increased complexity that may allow for in-time responses to avoid reaching a high complexity state in the airspace.

complexity↗

Work Term Assignment Spring 2017

My tour in the Engineering Robotics directorate exceeded my expectations. I learned lessons about Creo, manufacturing and assembly, collaboration, and troubleshooting. During my first tour, last spring, I used Creo on a smaller project, but had limited experience with it before starting in the Dynamic Systems Test branch this spring. I gained valuable experience learning assembly design, sheet metal design and designing with intent for manufacturing and assembly. These skills came from working both on the hatch and the floor. I also learned to understand the intent of other designers on models I worked with. While redesigning the floor, I was modifying an existing part and worked to understand what the previous designer had done to make it fit with the new model. Through working with the machine shop and in the mock-up, I learned much more about manufacturing and assembly. I used a Dremel, rivet gun, belt sander, and countersink for the first time. Through taking multiple safety training for different machine shops, I learned new machine shop safety skills specific to each one. This semester also gave me new collaborative opportunities. I collaborated with engineers within my branch as well as with Human Factors and the building 10 machine shop. This experience helped me learn how to design for functionality and assembly, not only for what would be easiest in my designs. In addition to these experiences, I learned many lessons in troubleshooting. I was the first person in my office to use a Windows 10 computer. This caused unexpected issues with NASA services and programs, such as the Digital Data Management Server (DDMS). Because of this, I gained experience finding solutions to lockout and freeze issues as well as Creo specific settings. These will be useful skills to have in the future and will be implemented in future rotations. This co-op tour has motivated me more to finish my degree and pursue my academic goals. I intend to take a machining Career Gateway Elective in the Fall to improve my skills in building as well as designing with manufacturing intent. I am also inspired to take more mechatronics CGE courses before I graduate to learn more about the crossover between mechanical and electrical engineering. This semester, I worked on multiple projects and had the opportunity to learn from engineers of different disciplines. I became proficient in Creo 2.0, a program I had not used significantly before. I finished modifying the hatch for 3D print and made sizeable modifications to the nose floor support design. I also gained hands-on experience that will be useful in my engineering career in the future. I would consider all of these major achievements from this spring semester. Lastly, I learned to ask more questions and to search for the right people to find answers which I know will be a valuable skill in the future. This summer, I will be completing my last rotation in the Flight Operations Directorate at Ellington Air Field. After this last tour, I will be returning to school for the Fall, Spring and Summer. I will graduate in August of 2018. I am looking forward to learning more about the different jobs available to engineers. This division works directly with many different types of aircrafts and I am excited to learn more about this focus of engineering. The Aircraft Operations Division values team work greatly and I intend to improve my interpersonal skills by working with them this summer.

Sico, Mallory↗

A Distributed Approach to High-Rate Delay Tolerant Networking Within a Virtualized Environment

The High-Rate Delay Tolerant Networking (HDTN) project has taken a distributed service-based approach to the development of a highly efficient delay tolerant networking (DTN) implementation. Through the analysis of many DTN implementations, system and mission requirements as well as the DTN protocol specifications, HDTN has worked to infuse modern computing technologies into the NASA approach to interplanetary networking. The initial use case of the HDTN software runs on a hypervisor representative of the International Space Station (ISS) DTN Gateway. In this scenario, multiple emulated payloads will send science data through HDTN to a mission operations center. HDTN will provide store and forward capability as well as network flow management. This paper discusses the infusion path of cognitive networking technologies in the NASA SCaN networks using the DTN architecture and protocols as the basis for cognitive routing and network management capabilities. HDTN has been developing the Bundle Protocol encoding and decoding mechanisms and messaging framework that can be used as the basis for integrating DTN with various learning and decision-making processes. The concepts of distributed computing, network virtualization, software defined networking and delay tolerant networking are basic building blocks which will further the development of cognitive networking. In addition to discussion of the HDTN software development and testing, this paper examines the role that each of these technologies play in the evolution of the current state of space networking into an intelligent network of networks.

Delay Tolerant Networking↗

Flight Software Dictionary Development for the Mars2020 Rover

The Mars2020 project, developed and operated by the Jet Propulsion Laboratory (JPL), successfully landed the Perseverance rover and its flying companion Ingenuity on the surface of Mars on February 18th 2021. Perseverance combines heritage and cutting-edge flight software and hardware to accomplish crucial mission requirements related to Martian surface sampling. The design, development, and operation of NASA’s large strategic science missions require the ability to communicate spacecraft capabilities to hundreds of engineers across multiple disciplines. The interaction between flight and ground software development, Verification and Validation (V&V), Assembly, Test, and Launch Operations (ATLO), and management each demand quick understanding of unique slices of information for each discipline. This information includes the current capabilities of the flight system as well as future capabilities and their status as they are developed and tested. Despite the fundamental and critical nature of this information, the flight software dictionaries used to track it are a stumbling block for many projects. These dictionaries provide the cornerstone for the interpretation of data sent from the spacecraft, allowing for quick comprehension by engineers on the ground. During both spacecraft development and operations, flight software dictionary management includes significant challenges due to the large number of interfacing systems and the subtle yet distinct needs of each.The engineering of flight software dictionaries for Mars2020 had numerous challenges, most-notably: parallel dictionary development to support simultaneous separate flight software build campaigns for each mission phase (cruise and surface), managing requests for operations-enabling information without perturbing the heritage interface with the rover, and the introduction of new tools by the dictionary stakeholders that forced the dictionary team to innovate and redesign the heritage tool chain. These challenges generated guiding principles for the dictionary development effort: emphasize coding best practices and unit testing in the dictionary code development tool chain, use institutionally provided COTS (commercial-off-the-shelf) tools whenever possible, and maintain the heritage flight-ground interface all while advancing operations-enabling information via a loosely coupled interface.Throughout development and operations, the Mars2020 dictionary toolchain included IBM DOORS Next Generation, GitHub, Microsoft Excel, Docker, Jenkins, and a significant custom-built Python codebase. Significant interfaces included JPL’s command and control software, heritage flight software team tools and processes, and the many cloud-based ground tools developed for the mission.This paper will discuss the requirements for the Mars2020 dictionary development, the development team’s response to those requirements, lessons learned throughout the process, steps taken towards automated deliveries and continuous integration of stakeholder inputs, potential toolchain improvements for Mars2020, and key takeaways that could be applied to future missions.

Pyrzak, Guy↗

Expressions Module for the Satellite Orbit Analysis Program

The Expressions Module is a software module that has been incorporated into the Satellite Orbit Analysis Program (SOAP). The module includes an expressions- parser submodule built on top of an analytical system, enabling the user to define logical and numerical variables and constants. The variables can capture output from SOAP orbital-prediction and geometric-engine computations. The module can combine variables and constants with built-in logical operators (such as Boolean AND, OR, and NOT), relational operators (such as >, <, or =), and mathematical operators (such as addition, subtraction, multiplication, division, modulus, exponentiation, differentiation, and integration). Parentheses can be used to specify precedence of operations. The module contains a library of mathematical functions and operations, including logarithms, trigonometric functions, Bessel functions, minimum/ maximum operations, and floating- point-to-integer conversions. The module supports combinations of time, distance, and angular units and has a dimensional- analysis component that checks for correct usage of units. A parser based on the Flex language and the Bison program looks for and indicates errors in syntax. SOAP expressions can be built using other expressions as arguments, thus enabling the user to build analytical trees. A graphical user interface facilitates use.

Edmonds, Karina↗

NASA’s Moon-to-Mars Planetary Autonomous Construction Technology Project: Overview and Status

NASA plans to land the first woman and next man on the Moon by 2025 through the initial Artemis missions. NASA and its international partners plan to establish a sustainable long-term presence on the lunar surface and build up infrastructure in the subsequent Artemis missions. The Lunar Surface Innovation Initiative (LSII), within NASA’s Space Technology Mission Directorate, aims to spur the creation of novel technologies needed for lunar surface exploration and accelerate the technology readiness of key systems and components. The primary thrust areas of LSII include sustainable power; dust mitigation; in-situ resource utilization; surface excavation, construction, and outfitting; and extreme access/extreme environments. The Moon-to-Mars Planetary Autonomous Construction Technology (MMPACT) projectwas initiated to address the lunar surface construction thrust area of LSII. The goal of the MMPACT project is to develop, deliver, and demonstrate on-demand capabilities to protect astronauts and create infrastructure on the lunar surface via construction of landing pads, habitats, shelters, roadways, berms and blast shields using lunar regolith-based materials. The MMPACT project is leveraging technology derived from NASA’s 3D Printed Mars Habitat Challenge along with contributions from other Government agencies, and multiple partners within industry and academia. The MMPACT project is comprised of three interrelated elements, construction hardware and process development; feedstock materials development; and microwave structure construction capabilities. These elements are working together to address the multiple challenges of infrastructure construction on the surface of the Moon including increased autonomy of operations, hardware operation and manufacturing under lunar environmental conditions, long-duration operation of mechanisms and parts, scale of construction activities, and material and construction requirements and standards. This presentation will summarize the status of development activities in each of the three elements, including testing of the various candidate materials, preliminary design concepts for future lunar infrastructure elements, and the vision for future technology demonstrations on the lunar surface. These demonstrations, targeting the mid-to-late 2020’s, are expected to enable landing pad construction and habitat construction resulting in commercial capabilities early in the next decade.

lunar infrastructure↗

Generating Vegetation Leaf Area Index Earth System Data Record from Multiple Sensors: Implementation, Analysis and Validation - Part 2

The evaluation of a new global monthly leaf area index (LAI) data set for the period July 1981 to December 2006 derived from AVHRR Normalized Difference Vegetation Index (NDVI) data is described. The physically based algorithm is detailed in the first of the two part series. Here, the implementation, production and evaluation of the data set are described. The data set is evaluated both by direct comparisons to ground data and indirectly through inter-comparisons with similar data sets. This indirect validation showed satisfactory agreement with existing LAI products, importantly MODIS, at a range of spatial scales, and significant correlations with key climate variables in areas where temperature and precipitation limit plant growth. The data set successfully reproduced well-documented spatio-temporal trends and inter-annual variations in vegetation activity in the northern latitudes and semi-arid tropics. Comparison with plot scale field measurements over homogeneous vegetation patches indicated a 7% underestimation when all major vegetation types are taken into account. The error in mean values obtained from distributions of AVHRR LAI and high-resolution field LAI maps for different biomes is within 0.5 LAI for six out of the ten selected sites. These validation exercises though limited by the amount of field data, and thus less than comprehensive, indicated satisfactory agreement between the LAI product and field measurements. Overall, the intercomparison with short-term LAI data sets, evaluation of long term trends with known variations in climate variables, and validation with field measurements together build confidence in the utility of this new 26 year LAI record for long term vegetation monitoring and modeling studies.

Ganguly, Sangram↗

NASA’s Moon-to-Mars Planetary Autonomous Construction Technology Project: Overview and Status

NASA plans to land the first woman and next man on the Moon by 2025 through the initial Artemis missions. NASA and its international partners plan to establish a sustainable long-term presence on the lunar surface and build up infrastructure in the subsequent Artemis missions. The Lunar Surface Innovation Initiative (LSII), within NASA’s Space Technology Mission Directorate, aims to spur the creation of novel technologies needed for lunar surface exploration and accelerate the technology readiness of key systems and components. The primary thrust areas of LSII include sustainable power; dust mitigation; in-situ resource utilization; surface excavation, construction, and outfitting; and extreme access/extreme environments. The Moon-to-Mars Planetary Autonomous Construction Technology (MMPACT) project was initiated to address the lunar surface construction thrust area of LSII. The goal of the MMPACT project is to develop, deliver, and demonstrate on-demand capabilities to protect astronauts and create infrastructure on the lunar surface via construction of landing pads, habitats, shelters, roadways, berms and blast shields using lunar regolith-based materials. The MMPACT project is leveraging technology derived from NASA’s 3D Printed Mars Habitat Challenge along with contributions from other Government agencies, and multiple partners within industry and academia. The MMPACT project is comprised of three interrelated elements, construction hardware and process development; feedstock materials development; and microwave structure construction capabilities. These elements are working together to address the multiple challenges of infrastructure construction on the surface of the Moon including increased autonomy of operations, hardware operation and manufacturing under lunar environmental conditions, long-duration operation of mechanisms and parts, scale of construction activities, and material and construction requirements and standards. This presentation will summarize the status of development activities in each of the three elements, including testing of the various candidate materials, preliminary design concepts for future lunar infrastructure elements, and the vision for future technology demonstrations on the lunar surface. These demonstrations, targeting the mid-to-late 2020’s, are expected to enable landing pad construction and habitat construction resulting in commercial capabilities early in the next decade.

Additive construction, regolith processing, lunar ↗

Overview of US AID-World Bank-NASA Collaboration to Address Water Management Issues in the MENA Region

The World Bank, USAID and NASA have recently established a joint project to study multiple issues pertaining to water related applications in the Middle East North Africa (MENA) region. The main concentration of the project is on utilization of remote sensing data and hydrological models to address crop irrigation and mapping, flood mapping and forecasting, evapotranspiration and drought problems prevalent in this large geographic area. Additional emphases are placed on understanding the climate impact on these areas as well. Per IPCC 2007 report, by the end of this century MENA region is projected to experience an increase of 3 C to 5 C rise in mean temperatures and a 20% decline in precipitation. This poses a serious problem for this geographic zone especially when majority of the hydrological consumption is for the agriculture sector and the remaining amount is for domestic consumption. The remote sensing data from space is one of the best ways to study such complex issues and further feed into the decision support systems. NASA's fleet of Earth Observing satellites offer a great vantage point from space to look at the globe and provide vital signs necessary to maintain healthy and sustainable ecosystem. These observations generate multiple products such as soil moisture, global precipitation, aerosols, cloud cover, normalized difference vegetation index, land cover/use, ocean altimetry, ocean salinity, sea surface winds, sea surface temperature, ozone and atmospheric gases, ice and snow measurements, and many more. All of the data products, models and research results are distributed-via the Internet freely through out the world. This project will utilize several NASA models such as global Land Data Assimilation System (LDAS) to generate hydrological states and fluxes in near real time. These LDAS products will then be further compared with other NASA satellite observations (MODIS, VIIRS, TRMM, etc.) and other discrete models to compare and optimize evapotranspiration, soil moisture and crop irrigation, droUght assessment and water balance. The floods being a critical disaster in many of the MENA countries, NASA's global flood mapping and modeling framework (CREST) will be customized for country specific needs and delivered to the remote sensing organizations for their future use. Finally, capacity building is a critical part of this project and NASA will assist in this effort as well.

Habib, Shahid↗

A Distributed Approach to High-Rate Delay Tolerant Networking Within a Virtualized Environment

The High-Rate Delay Tolerant Networking (HDTN) project has taken a distributed service-based approach to the development of a highly efficient delay tolerant networking (DTN) implementation. Through the analysis of many DTN implementations, system and mission requirements as well as the DTN protocol specifications, HDTN has worked to infuse modern computing technologies into the NASA approach to interplanetary networking. The initial use case of the HDTN software runs on a hypervisor representative of the International Space Station (ISS) DTN Gateway. In this scenario, multiple emulated payloads will send science data through HDTN to a mission operations center. HDTN will provide store and forward capability as well as network flow management. This paper discusses the infusion path of cognitive networking technologies in the NASA Space Communications and Navigation (SCaN) networks using the DTN architecture and protocols as the basis for cognitive routing and network management capabilities. HDTN has been developing the Bundle Protocol encoding and decoding mechanisms and messaging framework that can be used as the basis for integrating DTN with various learning and decision-making processes. The concepts of distributed computing, network virtualization, software defined networking and delay tolerant networking are basic building blocks which will further the development of cognitive networking. In addition to discussion of the HDTN software development and testing, this paper examines the role that each of these technologies play in the evolution of the current state of space networking into an intelligent network of networks.

Rachel Mary Dudukovich↗

Standardizing Interfaces for External Access to Data and Processing for the NASA Ozone Product Evaluation and Test Element (PEATE)

NASA's traditional science data processing systems have focused on specific missions, and providing data access, processing and services to the funded science teams of those specific missions. Recently NASA has been modifying this stance, changing the focus from Missions to Measurements. Where a specific Mission has a discrete beginning and end, the Measurement considers long term data continuity across multiple missions. Total Column Ozone, a critical measurement of atmospheric composition, has been monitored for'decades on a series of Total Ozone Mapping Spectrometer (TOMS) instruments. Some important European missions also monitor ozone, including the Global Ozone Monitoring Experiment (GOME) and SCIAMACHY. With the U.S.IEuropean cooperative launch of the Dutch Ozone Monitoring Instrument (OMI) on NASA Aura satellite, and the GOME-2 instrumental on MetOp, the ozone monitoring record has been further extended. In conjunction with the U.S. Department of Defense (DoD) and the National Oceanic and Atmospheric Administration (NOAA), NASA is now preparing to evaluate data and algorithms for the next generation Ozone Mapping and Profiler Suite (OMPS) which will launch on the National Polar-orbiting Operational Environmental Satellite System (NPOESS) Preparatory Project (NPP) in 2010. NASA is constructing the Science Data Segment (SDS) which is comprised of several elements to evaluate the various NPP data products and algorithms. The NPP SDS Ozone Product Evaluation and Test Element (PEATE) will build on the heritage of the TOMS and OM1 mission based processing systems. The overall measurement based system that will encompass these efforts is the Atmospheric Composition Processing System (ACPS). We have extended the system to include access to publically available data sets from other instruments where feasible, including non-NASA missions as appropriate. The heritage system was largely monolithic providing a very controlled processing flow from data.ingest of satellite data to the ultimate archive of specific operational data products. The ACPS allows more open access with standard protocols including HTTP, SOAPIXML, RSS and various REST incarnations. External entities can be granted access to various modules within the system, including an extended data archive, metadata searching, production planning and processing. Data access is provided with very fine grained access control. It is possible to easily designate certain datasets as being available to the public, or restricted to groups of researchers, or limited strictly to the originator. This can be used, for example, to release one's best validated data to the public, but restrict the "new version" of data processed with a new, unproven algorithm until it is ready. Similarly, the system can provide access to algorithms, both as modifiable source code (where possible) and fully integrated executable Algorithm Plugin Packages (APPs). This enables researchers to download publically released versions of the processing algorithms and easily reproduce the processing remotely, while interacting with the ACPS. The algorithms can be modified allowing better experimentation and rapid improvement. The modified algorithms can be easily integrated back into the production system for large scale bulk processing to evaluate improvements. The system includes complete provenance tracking of algorithms, data and the entire processing environment. The origin of any data or algorithms is recorded and the entire history of the processing chains are stored such that a researcher can understand the entire data flow. Provenance is captured in a form suitable for the system to guarantee scientific reproducability of any data product it distributes even in cases where the physical data products themselves have been deleted due to space constraints. We are currently working on Semantic Web ontologies for representing the various provenance information. A new web site focusing on consolidating informaon about the measurement, processing system, and data access has been established to encourage interaction with the overall scientific community. We will describe the system, its data processing capabilities, and the methods the community can use to interact with the standard interfaces of the system.

Tilmes, Curt A.↗

DITDOS: A set of design specifications for distributed data inventories

The analysis of space science data often requires researchers to work with many different types of data. For instance, correlative analysis can require data from multiple instruments on a single spacecraft, multiple spacecraft, and ground-based data. Typically, data from each source are available in a different format and have been written on a different type of computer, and so much effort must be spent to read the data and convert it to the computer and format that the researchers use in their analysis. The large and ever-growing amount of data and the large investment by the scientific community in software that require a specific data format make using standard data formats impractical. A format-independent approach to accessing and analyzing disparate data is key to being able to deliver data to a diverse community in a timely fashion. The system in use at the Planetary Plasma Interactions (PPI) node of the NASA Planetary Data System (PDS) is based on the object-oriented Distributed Inventory Tracking and Data Ordering Specification (DITDOS), which describes data inventories in a storage independent way. The specifications have been designed to make it possible to build DITDOS compliant inventories that can exist on portable media such as CD-ROM's. The portable media can be moved within a system, or from system to system, and still be used without modification. Several applications have been developed to work with DITDOS compliant data holdings. One is a windows-based client/server application, which helps guide the user in the selection of data. A user can select a data base, then a data set, then a specific data file, and then either order the data and receive it immediately if it is online or request that it be brought online if it is not. A user can also view data by any of the supported methods. DITDOS makes it possible to use already existing applications for data-specific actions, and this is done whenever possible. Another application is a stand-alone tool to assist in the extraction of data from portable media, such as CD-ROM's. In addition to the applications, there is a set of libraries that can facilitate building new DITDOS compliant applications.

King, T. A.↗

HDU Deep Space Habitat (DSH) Overview

This paper gives an overview of the National Aeronautics and Space Administration (NASA) led multi-center Habitat Demonstration Unit (HDU) project Deep Space Habitat (DSH) analog that will be field-tested during the 2011 Desert Research and Technologies Studies (D-RATS) field tests. The HDU project is a technology pull project that integrates technologies and innovations from multiple NASA centers. This project will repurpose the HDU Pressurized Excursion Module (PEM) that was field tested in the 2010 D-RATS, adding habitation functionality to the prototype unit. The 2010 configuration of the HDU-PEM consisted of a lunar surface laboratory module that was used to bring over 20 habitation-related technologies together in a single platform that could be tested as an advanced habitation analog in the context of mission architectures and surface operations. The 2011 HDU-DSH configuration will build upon the PEM work, and emphasize validity of crew operations (habitation and living, etc), EVA operations, mission operations, logistics operations, and science operations that might be required in a deep space context for Near Earth Object (NEO) exploration mission architectures. The HDU project consists of a multi-center team brought together in a skunkworks approach to quickly build and validate hardware in analog environments. The HDU project is part of the strategic plan from the Exploration Systems Mission Directorate (ESMD) Directorate Integration Office (DIO) and the Exploration Mission Systems Office (EMSO) to test destination elements in analog environments. The 2011 analog field test will include Multi Mission Space Exploration Vehicles (MMSEV) and the DSH among other demonstration elements to be brought together in a mission architecture context. This paper will describe overall objectives, various habitat configurations, strategic plan, and technology integration as it pertains to the 2011 field tests.

Kennedy, Kriss J.↗