Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “developers”

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 1,243 records · Page 69

Constraints and Opportunities in GCM Model Development

Over the past 30 years climate models have evolved from relatively simple representations of a few atmospheric processes to complex multi-disciplinary system models which incorporate physics from bottom of the ocean to the mesopause and are used for seasonal to multi-million year timescales. Computer infrastructure over that period has gone from punchcard mainframes to modern parallel clusters. Constraints of working within an ever evolving research code mean that most software changes must be incremental so as not to disrupt scientific throughput. Unfortunately, programming methodologies have generally not kept pace with these challenges, and existing implementations now present a heavy and growing burden on further model development as well as limiting flexibility and reliability. Opportunely, advances in software engineering from other disciplines (e.g. the commercial software industry) as well as new generations of powerful development tools can be incorporated by the model developers to incrementally and systematically improve underlying implementations and reverse the long term trend of increasing development overhead. However, these methodologies cannot be applied blindly, but rather must be carefully tailored to the unique characteristics of scientific software development. We will discuss the need for close integration of software engineers and climate scientists to find the optimal processes for climate modeling.

Schmidt, Gavin↗

Airspace Systems Program: Next Generation Air Transportation System Concepts and Technology Development FY2010 Project Plan Version 3.0

This document describes the FY2010 plan for the management and execution of the Next Generation Air Transportation System (NextGen) Concepts and Technology Development (CTD) Project. The document was developed in response to guidance from the Airspace Systems Program (ASP), as approved by the Associate Administrator of the Aeronautics Research Mission Directorate (ARMD), and from guidelines in the Airspace Systems Program Plan. Congress established the multi-agency Joint Planning and Development Office (JPDO) in 2003 to develop a vision for the 2025 Next Generation Air Transportation System (NextGen) and to define the research required to enable it. NASA is one of seven agency partners contributing to the effort. Accordingly, NASA's ARMD realigned the Airspace Systems Program in 2007 to "directly address the fundamental research needs of the Next Generation Air Transportation System...in partnership with the member agencies of the JPDO." The Program subsequently established two new projects to meet this objective: the NextGen-Airspace Project and the NextGen-Airportal Project. Together, the projects will also focus NASA s technical expertise and world-class facilities to address the question of where, when, how and the extent to which automation can be applied to moving aircraft safely and efficiently through the NAS and technologies that address optimal allocation of ground and air technologies necessary for NextGen. Additionally, the roles and responsibilities of humans and automation influence in the NAS will be addressed by both projects. Foundational concept and technology research and development begun under the NextGen-Airspace and NextGen-Airportal projects will continue. There will be no change in NASA Research Announcement (NRA) strategy, nor will there be any change to NASA interfaces with the JPDO, Federal Aviation Administration (FAA), Research Transition Teams (RTTs), or other stakeholders

Kopardekar, Parimal H.↗

The Development of a CO2 Test Capability in the NASA JSC ARCJet for Mars Reentry Simulation

The Atmospheric Reentry Materials and Structures Evaluation Facility (ARMSEF) located at NASA Johnson Space Center is used for simulating the extreme environment experienced upon reentry for the development and certification of thermal protection systems (TPS). The facility supports a large variety of programs and was heavily leveraged for the certification and operational support of the TPS for the Orbiter and, more recently, the development of the heat shield for CEV. This paper will provide more detail into the heritage of the facility. Unique attributes of the facility include a modular aerodynamically stabilized arc heater and independently controlled O2 and N2 for the test gases. When combining the O2 and N2 in a 23:77 mass ratio respectively the Earth s atmosphere is accurately simulated and via modification of this ratio the investigation of the effects of atomic oxygen on a material s response is possible. In the summer of 2010 a development effort was started to add CO2 as a third independently controlled test gas such that, when combined with N2, opens up the possibility of accurately simulating a Martian reentry environment. This paper will discuss the test facility, especially the arc heater, in more detail. Initial testing involved relatively low concentrations of CO2 combined with N2 for the primary purpose of gathering data to answer two pressing safety concerns. The first being the rate of production of carbon monoxide (CO) within the ejector vacuum system. The main concern was that CO can be flammable and possibly explosive at high enough concentrations and pressures. The hazard control during the development phase involved the use of injecting N2 inside the test chamber diffuser to dilute and reduce the concentration of any and all CO present. A residual gas analyzer (RGA) was used to determine the relative amount of CO in the exhaust gas and provide a conversion rate of CO2 to CO. This paper will discuss in more detail the results of the RGA data and the calculated conversion rate. The second safety concern addressed is the possible formation of hydrogen cyanide (HCN) and cyanide (CN). HCN would primarily be present in the cooling water while the CN would most probably condense onto the interior surfaces of the test chamber. Water samples and wipes of the test chamber surfaces were analyzed by an industrial hygienist for the presence of HCN and CN. His paper will discuss these results in more detail. Throughout this development effort measurements of the CO2:N2 flowfield were made with heat flux and pressure probes and with laser induced fluorescence (LIF) of the atomic oxygen. This paper will discuss these results

DelPapa, Steven V.↗

An Overview of STS-132 MRM1 Cargo Element Thermal Model Development and Analyses

STS-132 was launched in May 2010 and delivered the Russian Mini Research Module 1 (MRM1) cargo element to the International Space Station as part of the ULF-4 assembly flight. The cargo element consisted of the module outfitted with externally mounted Multi-purpose Laboratory Module (MLM) Airlock, MLM radiator, Portable Work Platform (PWP), and a European Robotic Arm (ERA) spare elbow. Prior to every Shuttle flight, hardware developers are required to determine compatibility of their hardware to thermal environments experienced during the Shuttle mission and once the element is integrated with the ISS. Thermal models are provided to the Shuttle program to determine the impact of the payload on the Orbiter hardware, as well as the ISS program to determine impacts on other ISS payloads in the Orbiter. Historically the Russian International Partner (IP) develops models in formats not compatible with software used by Space Shuttle or ISS programs. This prompted NASA and Lockheed Martin to develop a unique set of thermal models for the MRM1 cargo element. Subsequent ULF-4 mission analyses performed with the models assessed the launch to activation response, identified operational criteria documented in flight rules, and ensured compliance with the mission timeline and no hazards to the crew, orbiter, or ISS. This presentation provides an overview of the work performed, depicts unique approaches in model development, discusses lessons learned, and issue resolution approaches. Though development and analysis efforts spanned over four years and presented various integration challenges it provided an example of successful collaboration with our International Partners.

Perez, Miguel Fernando↗

Developing Standards to Qualify a Fine Water Mist Fire Extinguisher for Human Spaceflight

NASA is developing a Fine Water Mist Portable Fire Extinguisher for use on the International Space Station. The International Space Station presently uses two different types of fire extinguishers: a water foam extinguisher in the Russian Segment, and a carbon dioxide extinguisher in the US Segment and Columbus and Kibo pressurized elements. Changes in emergency breathing equipment make Fine Water Mist operationally preferable. Supplied oxygen breathing systems allow for safe discharge of a carbon dioxide fire extinguisher, without concerns of the crew inhaling unsafe levels of carbon dioxide. But the Portable Breathing Apparatus offers no more than 15 minutes of capability, and continued use of hose based supplied oxygen systems increases the oxygen content in a fire situation. NASA has developed a filtering respirator cartridge for use in a fire environment. It is qualified to provide up to 90 minutes of capability, and because it is a filtering respirator it does not add oxygen to the environment. The fire response respirator cartridge does not filter carbon dioxide, so a crew member discharging a CO2 fire extinguisher while wearing this filtering respirator would be at risk of inhaling unsafe levels of CO2. Fine Water Mist extinguishes a fire without creating a large volume of air with reduced oxygen and elevated CO2. Compared to the carbon dioxide based Portable Fire Extinguisher, the flight qualification of Fine Water Mist systems requires special care. Qualification of the CO2 based Portable Fire Extinguisher began with the assumption that any fire on ISS would be extinguished if the air in the fire environment reached a critical concentration of CO2. Qualification of a CO2 based system requires the developers to make assertions and assumptions about vehicle geometry and the ability of the extinguisher to deliver CO2 in different geometric configurations, but the developers did not need to make assertions or assumptions about the size of the fire, the temperature, or the heat generation rate. Fine Water Mist systems extinguish a fire predominantly by removing heat -- so qualification standards must evaluate geometry, but also temperature, heat transfer, and heat generation rate. This paper outlines and describes the methods used to develop standards used to qualify Fine Water Mist systems for a human spaceflight environment.

Graf, John↗

Extravehicular Activity Technology Development Status and Forecast

The goal of NASA s current EVA technology effort is to further develop technologies that will be used to demonstrate a robust EVA system that has application for a variety of future missions including microgravity and surface EVA. Overall the objectives will be to reduce system mass, reduce consumables and maintenance, increase EVA hardware robustness and life, increase crew member efficiency and autonomy, and enable rapid vehicle egress and ingress. Over the past several years, NASA realized a tremendous increase in EVA system development as part of the Exploration Technology Development Program and the Constellation Program. The evident demand for efficient and reliable EVA technologies, particularly regenerable technologies was apparent under these former programs and will continue to be needed as future mission opportunities arise. The technological need for EVA in space has been realized over the last several decades by the Gemini, Apollo, Skylab, Space Shuttle, and the International Space Station (ISS) programs. EVAs were critical to the success of these programs. Now with the ISS extension to 2028 in conjunction with a current forecasted need of at least eight EVAs per year, the EVA hardware life and limited availability of the Extravehicular Mobility Units (EMUs) will eventually become a critical issue. The current EMU has successfully served EVA demands by performing critical operations to assemble the ISS and provide repairs of satellites such as the Hubble Space Telescope. However, as the life of ISS and the vision for future mission opportunities are realized, a new EVA systems capability will be needed and the current architectures and technologies under development offer significant improvements over the current flight systems. In addition to ISS, potential mission applications include EVAs for missions to Near Earth Objects (NEO), Phobos, or future surface missions. Surface missions could include either exploration of the Moon or Mars. Providing an EVA capability for these types of missions enables in-space construction of complex vehicles or satellites, hands on exploration of new parts of our solar system, and engages the public through the inspiration of knowing that humans are exploring places that they have never been before. This paper offers insight into what is currently being developed and what the potential opportunities are in the forecast.

Chullen, Cinda↗

Cryogenic Propellant Feed System Analytical Tool Development

The Propulsion Systems Branch at NASA s Lyndon B. Johnson Space Center (JSC) has developed a parametric analytical tool to address the need to rapidly predict heat leak into propellant distribution lines based on insulation type, installation technique, line supports, penetrations, and instrumentation. The Propellant Feed System Analytical Tool (PFSAT) will also determine the optimum orifice diameter for an optional thermodynamic vent system (TVS) to counteract heat leak into the feed line and ensure temperature constraints at the end of the feed line are met. PFSAT was developed primarily using Fortran 90 code because of its number crunching power and the capability to directly access real fluid property subroutines in the Reference Fluid Thermodynamic and Transport Properties (REFPROP) Database developed by NIST. A Microsoft Excel front end user interface was implemented to provide convenient portability of PFSAT among a wide variety of potential users and its ability to utilize a user-friendly graphical user interface (GUI) developed in Visual Basic for Applications (VBA). The focus of PFSAT is on-orbit reaction control systems and orbital maneuvering systems, but it may be used to predict heat leak into ground-based transfer lines as well. PFSAT is expected to be used for rapid initial design of cryogenic propellant distribution lines and thermodynamic vent systems. Once validated, PFSAT will support concept trades for a variety of cryogenic fluid transfer systems on spacecraft, including planetary landers, transfer vehicles, and propellant depots, as well as surface-based transfer systems. The details of the development of PFSAT, its user interface, and the program structure will be presented.

Lusby, Brian S.↗

Autonomous Aerobraking: Thermal Analysis and Response Surface Development

A high-fidelity thermal model of the Mars Reconnaissance Orbiter was developed for use in an autonomous aerobraking simulation study. Response surface equations were derived from the high-fidelity thermal model and integrated into the autonomous aerobraking simulation software. The high-fidelity thermal model was developed using the Thermal Desktop software and used in all phases of the analysis. The use of Thermal Desktop exclusively, represented a change from previously developed aerobraking thermal analysis methodologies. Comparisons were made between the Thermal Desktop solutions and those developed for the previous aerobraking thermal analyses performed on the Mars Reconnaissance Orbiter during aerobraking operations. A variable sensitivity screening study was performed to reduce the number of variables carried in the response surface equations. Thermal analysis and response surface equation development were performed for autonomous aerobraking missions at Mars and Venus.

Dec, John A.↗

Recent Developments in the Design, Capabilities and Autonomous Operations of a Lightweight Surface Manipulation System and Test-bed

The first generation of a versatile high performance device for performing payload handling and assembly operations on planetary surfaces, the Lightweight Surface Manipulation System (LSMS), has been designed and built. Over the course of its development, conventional crane type payload handling configurations and operations have been successfully demonstrated and the range of motion, types of operations and the versatility greatly expanded. This enhanced set of 1st generation LSMS hardware is now serving as a laboratory test-bed allowing the continuing development of end effectors, operational techniques and remotely controlled and automated operations. This paper describes the most recent LSMS and test-bed development activities, that have focused on two major efforts. The first effort was to complete a preliminary design of the 2nd generation LSMS that has the capability for limited mobility and can reposition itself between lander decks, mobility chassis, and fixed base locations. A major portion of this effort involved conducting a study to establish the feasibility of, and define, the specifications for a lightweight cable-drive waist joint. The second effort was to continue expanding the versatility and autonomy of large planetary surface manipulators using the 1st generation LSMS as a test-bed. This has been accomplished by increasing manipulator capabilities and efficiencies through both design changes and tool and end effector development. A software development effort has expanded the operational capabilities of the LSMS test-bed to include; autonomous operations based on stored paths, use of a vision system for target acquisition and tracking, and remote command and control over a communications bridge.

Dorsey, John T.↗

Lunar Surface Systems Supportability Technology Development Roadmap

The Lunar Surface Systems Supportability Technology Development Roadmap is a guide for developing the technologies needed to enable the supportable, sustainable, and affordable exploration of the Moon and other destinations beyond Earth. Supportability is defined in terms of space maintenance, repair, and related logistics. This report considers the supportability lessons learned from NASA and the Department of Defense. Lunar Outpost supportability needs are summarized, and a supportability technology strategy is established to make the transition from high logistics dependence to logistics independence. This strategy will enable flight crews to act effectively to respond to problems and exploit opportunities in an environment of extreme resource scarcity and isolation. The supportability roadmap defines the general technology selection criteria. Technologies are organized into three categories: diagnostics, test, and verification; maintenance and repair; and scavenge and recycle. Furthermore, "embedded technologies" and "process technologies" are used to designate distinct technology types with different development cycles. The roadmap examines the current technology readiness level and lays out a four-phase incremental development schedule with selection decision gates. The supportability technology roadmap is intended to develop technologies with the widest possible capability and utility while minimizing the impact on crew time and training and remaining within the time and cost constraints of the program.

Oeftering, Richard C.↗

Multi Purpose Crew Vehicle Environmental Control and Life Support Development Status

The Orion Multi Purpose Crew Vehicle (MPCV) is the first crew transport vehicle to be developed by the National Aeronautics and Space Administration (NASA) in the last thirty years. Orion is currently being developed to transport the crew safely from the Earth beyond Earth orbit. This year, the vehicle focused on building the Orion Flight Test 1 (OFT1) vehicle to be launched in 2013. The development of the Orion Environmental Control and Life Support (ECLS) System, focused on the components which are on OFT1 which includes pressure control and active thermal control systems, is progressing through the design stage into manufacturing. Additional development work was done to keep the remaining component progressing towards implementation for a flight test in 2017. This paper covers the Orion ECLS development from April 2011 to April 2012.

Lewis, John F.↗

The Application of Lean Thinking Principles and Kaizen Practices for the Successful Development and Implementation of the Ares I-X Flight Test Rocket and Mission

On October 28, 2009 the Ares I-X flight test rocket launched from Kennedy Space Center and flew its suborbital trajectory as designed. The mission was successfully completed as data from the test, and associated development activities were analyzed, transferred to stakeholders, and well documented. Positive lessons learned from Ares I-X were that the application of lean thinking principles and kaizen practices are effective in streamlining development activities. Ares I-X, like other historical rocket development projects, was hampered by technical, cost, and schedule challenges and if not addressed boldly could have resulted in cancellation of the test. The mission management team conducted nine major meetings, referred to as lean events, across its elements to assess plans, procedures, processes, requirements, controls, culture, organization, use of resources, and anything that could be changed to optimize schedule or reduce risk. The preeminent aspect of the lean events was the focus on value added activities and the removal or at least reduction in non-value activities. Trained Lean Six Sigma facilitators assisted the Ares I-X developers in conducting the lean events. They indirectly helped formulate the mission s own unique methodology for assessing schedule. A core team was selected to lead the events and report to the mission manager. Each activity leveraged specialized participants to analyze the subject matter and its related processes and then recommended alternatives and solutions. Stakeholders were the event champions. They empowered and encouraged the team to succeed. The keys to success were thorough preparation, honest dialog, small groups, adherence to the Ares I-X ground rules, and accountability through disciplined reporting and tracking of actions. This lean event formula was game-changing as demonstrated by the success of Ares I-X. It is highly recommended as a management tool to help develop other complex systems efficiently. The key benefits for Ares I-X were obtaining unambiguous schedule margin, defining enabling options for risk reduction, and most importantly a stronger more unified team.

Askins, B. R.↗

The Application of Lean Thinking Principles and Kaizen Practices for the Successful Development and Implementation of the Ares I-X Flight Test Rocket and Mission

On October 28, 2009 the Ares I-X flight test rocket launched from Kennedy Space Center and flew its suborbital trajectory as designed. The mission was successfully completed as data from the test, and associated development activities were analyzed, transferred to stakeholders, and well documented. A positive lesson learned from Ares I-X was that the application of lean thinking principles and kaizen practices was very effective in streamlining development activities. Ares I-X, like other historical rocket development projects, was hampered by technical, cost, and schedule challenges and if not addressed boldly could have resulted in cancellation of the test. The mission management team conducted nine major meetings, referred to as lean events, across its elements to assess plans, procedures, processes, requirements, controls, culture, organization, use of resources, and anything that could be changed to optimize schedule or reduce risk. The preeminent aspect of the lean events was the focus on value added activities and the removal or at least reduction in non-value added activities. Trained Lean Six Sigma facilitators assisted the Ares I-X developers in conducting the lean events. They indirectly helped formulate the mission s own unique methodology for assessing schedule. A core team was selected to lead the events and report to the mission manager. Each activity leveraged specialized participants to analyze the subject matter and its related processes and then recommended alternatives and solutions. Stakeholders were the event champions. They empowered and encouraged the team to succeed. The keys to success were thorough preparation, honest dialog, small groups, adherence to the Ares I-X ground rules, and accountability through disciplined reporting and tracking of actions. This lean event formula was game-changing as demonstrated by Ares I-X. It is highly recommended as a management tool to help develop other complex systems efficiently. The key benefits for Ares I-X were obtaining unambiguous schedule margin, defining enabling options for risk reduction, and most importantly a stronger more unified team.

Askins, B. R.↗

A Proposed Strategy for the U.S. to Develop and Maintain a Mainstream Capability Suite ("Warehouse") for Automated/Autonomous Rendezvous and Docking in Low Earth Orbit and Beyond

The ability of space assets to rendezvous and dock/capture/berth is a fundamental enabler for numerous classes of NASA fs missions, and is therefore an essential capability for the future of NASA. Mission classes include: ISS crew rotation, crewed exploration beyond low-Earth-orbit (LEO), on-orbit assembly, ISS cargo supply, crewed satellite servicing, robotic satellite servicing / debris mitigation, robotic sample return, and robotic small body (e.g. near-Earth object, NEO) proximity operations. For a variety of reasons to be described, NASA programs requiring Automated/Autonomous Rendezvous and Docking/Capture/Berthing (AR&D) capabilities are currently spending an order-of-magnitude more than necessary and taking twice as long as necessary to achieve their AR&D capability, "reinventing the wheel" for each program, and have fallen behind all of our foreign counterparts in AR&D technology (especially autonomy) in the process. To ensure future missions' reliability and crew safety (when applicable), to achieve the noted cost and schedule savings by eliminate costs of continually "reinventing the wheel ", the NASA AR&D Community of Practice (CoP) recommends NASA develop an AR&D Warehouse, detailed herein, which does not exist today. The term "warehouse" is used herein to refer to a toolbox or capability suite that has pre-integrated selectable supply-chain hardware and reusable software components that are considered ready-to-fly, low-risk, reliable, versatile, scalable, cost-effective, architecture and destination independent, that can be confidently utilized operationally on human spaceflight and robotic vehicles over a variety of mission classes and design reference missions, especially beyond LEO. The CoP also believes that it is imperative that NASA coordinate and integrate all current and proposed technology development activities into a cohesive cross-Agency strategy to produce and utilize this AR&D warehouse. An initial estimate indicates that if NASA strategically coordinates the development of a robust AR&D capability across the Agency, the cost of implementing AR&D on a spacecraft could be reduced from roughly $70M per mission to as low as $7M per mission, and the associated development time could be reduced from 4 years to 2 years, after the warehouse is completely developed. Table 1 shows the clear long-term benefits to the Agency in term of costs and schedules for various missions. (The methods used to arrive at the Table 1 numbers is presented in Appendices A and B.)

Krishnakumar, Kalmanje S.↗

Progress Made in Lunar In-Situ Resource Utilization Under NASA's Exploration Technology and Development Program

Incorporation of In-Situ Resource Utilization (ISRU) and the production of mission critical consumables for 9 propulsion, power, and life support into mission architectures can greatly reduce the mass, cost, and risk of missions 10 leading to a sustainable and affordable approach to human exploration beyond Earth. ISRU and its products can 11 also greatly affect how other exploration systems are developed, including determining which technologies are 12 important or enabling. While the concept of lunar ISRU has existed for over 40 years, the technologies and systems 13 had not progressed much past simple laboratory proof-of-concept tests. With the release of the Vision for Space 14 Exploration in 2004 with the goal of harnessing the Moon.s resources, NASA initiated the ISRU Project in the 15 Exploration Technology Development Program (ETDP) to develop the technologies and systems needed to meet 16 this goal. In the five years of work in the ISRU Project, significant advancements and accomplishments occurred in 17 several important areas of lunar ISRU. Also, two analog field tests held in Hawaii in 2008 and 2010 demonstrated 18 all the steps in ISRU capabilities required along with the integration of ISRU products and hardware with 19 propulsion, power, and cryogenic storage systems. This paper will review the scope of the ISRU Project in the 20 ETDP, ISRU incorporation and development strategies utilized by the ISRU Project, and ISRU development and 21 test accomplishments over the five years of funded project activity.

Sanders, Gerald B.↗

Orion Multi Purpose Crew Vehicle Environmental Control and Life Support Development Status

The Orion Multi Purpose Crew Vehicle (MPCV) is the first crew transport vehicle to be developed by the National Aeronautics and Space Administration (NASA) in the last thirty years. Orion is currently being developed to transport the crew safely from the Earth beyond Earth orbit. This year, the vehicle focused on building the Exploration Flight Test 1 (EFT1) vehicle to be launched in 2014. The development of the Orion Environmental Control and Life Support (ECLS) System, focused on the components which are on EFT1 which includes pressure control and active thermal control systems, is progressing through the design stage into manufacturing. Additional development work was done to keep the remaining component progressing towards implementation for a flight tests in 2017 and in 2020. This paper covers the Orion ECLS development from April 2011 to April 2012.

Lewis, John F.↗

The NASA Soil Moisture Active Passive (SMAP) Mission - Science and Data Product Development Status

The Soil Moisture Active Passive (SMAP) mission, planned for launch in late 2014, has the objective of frequent, global mapping of near-surface soil moisture and its freeze-thaw state. The SMAP measurement system utilizes an L-band radar and radiometer sharing a rotating 6-meter mesh reflector antenna. The instruments will operate on a spacecraft in a 685 km polar orbit with 6am/6pm nodal crossings, viewing the surface at a constant 40-degree incidence angle with a 1000-km swath width, providing 3-day global coverage. Data from the instruments will yield global maps of soil moisture and freeze/thaw state at 10 km and 3 km resolutions, respectively, every two to three days. The 10-km soil moisture product will be generated using a combined radar and radiometer retrieval algorithm. SMAP will also provide a radiometer-only soil moisture product at 40-km spatial resolution and a radar-only soil moisture product at 3-km resolution. The relative accuracies of these products will vary regionally and will depend on surface characteristics such as vegetation water content, vegetation type, surface roughness, and landscape heterogeneity. The SMAP soil moisture and freeze/thaw measurements will enable significantly improved estimates of the fluxes of water, energy and carbon between the land and atmosphere. Soil moisture and freeze/thaw controls of these fluxes are key factors in the performance of models used for weather and climate predictions and for quantifYing the global carbon balance. Soil moisture measurements are also of importance in modeling and predicting extreme events such as floods and droughts. The algorithms and data products for SMAP are being developed in the SMAP Science Data System (SDS) Testbed. In the Testbed algorithms are developed and evaluated using simulated SMAP observations as well as observational data from current airborne and spaceborne L-band sensors including data from the SMOS and Aquarius missions. We report here on the development status of the SMAP data products. The Testbed simulations are designed to capture various sources of errors in the products including environment effects, instrument effects (nonideal aspects of the measurement system), and retrieval algorithm errors. The SMAP project has developed a Calibration and Validation (Cal/Val) Plan that is designed to support algorithm development (pre-launch) and data product validation (post-launch). A key component of the Cal/Val Plan is the identification, characterization, and instrumentation of sites that can be used to calibrate and validate the sensor data (Level l) and derived geophysical products (Level 2 and higher).

Nloku, E.↗

Spacecraft Avionics Software Development Then and Now: Different but the Same

NASA has always been in the business of balancing new technologies and techniques to achieve human space travel objectives. NASA s historic Software Production Facility (SPF) was developed to serve complex avionics software solutions during an era dominated by mainframes, tape drives, and lower level programming languages. These systems have proven themselves resilient enough to serve the Shuttle Orbiter Avionics life cycle for decades. The SPF and its predecessor the Software Development Lab (SDL) at NASA s Johnson Space Center (JSC) hosted flight software (FSW) engineering, development, simulation, and test. It was active from the beginning of Shuttle Orbiter development in 1972 through the end of the shuttle program in the summer of 2011 almost 40 years. NASA s Kedalion engineering analysis lab is on the forefront of validating and using many contemporary avionics HW/SW development and integration techniques, which represent new paradigms to NASA s heritage culture in avionics software engineering. Kedalion has validated many of the Orion project s HW/SW engineering techniques borrowed from the adjacent commercial aircraft avionics environment, inserting new techniques and skills into the Multi-Purpose Crew Vehicle (MPCV) Orion program. Using contemporary agile techniques, COTS products, early rapid prototyping, in-house expertise and tools, and customer collaboration, NASA has adopted a cost effective paradigm that is currently serving Orion effectively. This paper will explore and contrast differences in technology employed over the years of NASA s space program, due largely to technological advances in hardware and software systems, while acknowledging that the basic software engineering and integration paradigms share many similarities.

Mangieri, Mark L.↗