Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Process Mission Teams”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Decision Aid for Conjunction Risk Mitigation by Differential Drag

In the previous five years, the rate of conjunctions that the NASA Conjunction Assessment Risk Analysis (CARA) team processed and analyzed has more than tripled. (NASA CARA, 2024) New missions in the early development phases are now required to plan for dealing with conjunctions under the present space environment, and also projecting forward into a future likely with even further increased utilization of the space environment. Some missions are investigating the possibility of using differential drag to remediate conjunctions without expending limited fuel or for missions without propulsive capabilities. The NASA CARA team studied the historical record of conjunctions to evaluate the circumstances under which differential drag may be successfully applied and have developed a series of tables to use as a decision aid for missions considering differential drag. CARA records all conjunctions of their protected payloads, with historical records starting in 2005 (with significant conjunction events starting to occur on or after 2013). From this record, approximately 7,300 had a probability of collision (Pc) greater than 1 in 10,000, the nominal requirement for a risk mitigation maneuver (RMM) to be made per NASA Procedural Requirements (NPR) 8079.1 (NASA, 2023), at 3 days prior to the time of closest approach, the time analyzed for differential drag efficacy. CARA’s maneuver trade space tool (MTS) was used to prop-agate the primary satellite forward from that decision point with varying degrees of increase to ballistic coefficient (BC), and then recalculate the Pc to evaluate whether or not the conjunction was mitigated (Pc < 3E-6). These results were then binned and sorted along several axes, including altitude, amount of delta-BC, and (pre-maneuver) rate of energy dissipation, to identify underlying patterns. The altitude plot is shown in Figure 1. We found that differential drag was most successful for satellites with perigees below 560 km, and which could adopt an average delta-BC of 2 or greater (that is, increasing their ballistic coefficient by a factor of 3). However, this is a difficult threshold for a mission to clear; very few spacecraft are capable of adopting a high-drag configuration for 72 hours continuously. Planet’s Dove spacecraft use differential drag to remediate conjunctions (Griffith, et al., 2021), and they have a maximum delta-BC factor of 9, but in practice (with mission and charging constraints) they achieve a time-averaged delta-BC that is closer to 2 (Foster, et al., 2017). In contrast, a NASA mission in development reached out to CARA to evaluate the utility of differential drag to remediate potential conjunctions for a spacecraft which is capable of a similar high delta-BC, but with operational constraints that limit their time-averaged delta-BC to less than 1. CARA has developed tables that can be used as decision aids to advise missions-in-development about the best way to utilize their differential drag capabilities. For missions below 560 km with the operational flexibility to devote multiple days to holding a high-drag configuration (or a sufficiently high drag ratio to compensate for limitations on that time), they are able to successfully remediate high-risk conjunctions. Conversely, missions that do not meet these ex-acting criteria – most missions – can instead be advised to use on-board propulsion systems to perform RMMs or to turn their minimum-area face towards the approach vector, thereby reducing Pc at the moment of conjunction. (NASA, 2023)

risk mitigation↗
NASA NTRS2013

Dawn Orbit Determination Team : Trajectory Modeling and Reconstruction Processes at Vesta

The NASA Dawn spacecraft was launched on September 27, 2007 on a mission to study the asteroid belt's two largest objects, Vesta and Ceres. It is the first deep space orbiting mission to demonstrate solar-electric ion propulsion, providing the necessary delta-V to enable capture and escape from two extraterrestrial bodies. At this time, Dawn has completed its science campaign at Vesta and is currently on its journey to Ceres, where it will arrive in mid-2015. The spacecraft spent over a year in orbit around Vesta from July 2011 through August 2012, capturing science data during four dedicated orbit phases. In order to maintain the reference orbits necessary for science and enable the transfers between those orbits, precise and timely orbit determination was required. The constraints associated with low-thrust ion propulsion coupled with the relatively unknown a priori gravity and rotation models for Vesta presented unique challenges for the Dawn orbit determination team. While [1] discusses the prediction performance of the orbit determination products, this paper discusses the dynamics models, filter configuration, and data processing implemented to deliver a rapid orbit determination capability to the Dawn project.

Vesta↗
NASA NTRS2006

Multiuser Collaboration with Networked Mobile Devices

In this paper we describe a multiuser collaboration infrastructure that enables multiple mission scientists to remotely and collaboratively interact with visualization and planning software, using wireless networked personal digital assistants(PDAs) and other mobile devices. During ground operations of planetary rover and lander missions, scientists need to meet daily to review downlinked data and plan science activities. For example, scientists use the Science Activity Planner (SAP) in the Mars Exploration Rover (MER) mission to visualize downlinked data and plan rover activities during the science meetings [1]. Computer displays are projected onto large screens in the meeting room to enable the scientists to view and discuss downlinked images and data displayed by SAP and other software applications. However, only one person can interact with the software applications because input to the computer is limited to a single mouse and keyboard. As a result, the scientists have to verbally express their intentions, such as selecting a target at a particular location on the Mars terrain image, to that person in order to interact with the applications. This constrains communication and limits the returns of science planning. Furthermore, ground operations for Mars missions are fundamentally constrained by the short turnaround time for science and engineering teams to process and analyze data, plan the next uplink, generate command sequences, and transmit the uplink to the vehicle [2]. Therefore, improving ground operations is crucial to the success of Mars missions. The multiuser collaboration infrastructure enables users to control software applications remotely and collaboratively using mobile devices. The infrastructure includes (1) human-computer interaction techniques to provide natural, fast, and accurate inputs, (2) a communications protocol to ensure reliable and efficient coordination of the input devices and host computers, (3) an application-independent middleware that maintains the states, sessions, and interactions of individual users of the software applications, (4) an application programming interface to enable tight integration of applications and the middleware. The infrastructure is able to support any software applications running under the Windows or Unix platforms. The resulting technologies not only are applicable to NASA mission operations, but also useful in other situations such as design reviews, brainstorming sessions, and business meetings, as they can benefit from having the participants concurrently interact with the software applications (e.g., presentation applications and CAD design tools) to illustrate their ideas and provide inputs.

ground operations↗
NASA NTRS2016

NASA's Physics of the Cosmos and Cosmic Origins Technology Development Programs

The strategic astrophysics missions of the coming decades will help answer the questions "How did our universe begin and evolve?" and "How did galaxies, stars, and planets come to be?" Enabling these missions requires advances in key technologies far beyond the current state of the art. NASA's Physics of the Cosmos (PCOS) and Cosmic Origins (COR) Program Offices manage technology maturation projects funded through the Strategic Astrophysics Technology (SAT) program to accomplish such advances. The PCOS and COR Program Offices, residing at the NASA Goddard Space Flight Center (GSFC), were established in 2011, and serve as the implementation arm for the Astrophysics Division at NASA Headquarters. We present an overview of the Programs' technology development activities and the current technology investment portfolio of 23 technology advancements. We discuss the process for addressing community-provided technology gaps and Technology Management Board (TMB)-vetted prioritization and investment recommendations that inform the SAT program. The process improves the transparency and relevance of our technology investments, provides the community a voice in the process, and promotes targeted external technology investments by defining needs and identifying customers. The Programs' priorities are driven by strategic direction from the Astrophysics Division, which is informed by the National Research Council's (NRC) "New Worlds, New Horizons in Astronomy and Astrophysics" (NWNH) 2010 Decadal Survey report [1], the Astrophysics Implementation Plan (AIP) [2] as updated, and the Astrophysics Roadmap "Enduring Quests, Daring Visions" [3]. These priorities include technology development for missions to study dark energy, gravitational waves, X-ray and inflation probe science, and large far-infrared (IR) and ultraviolet (UV)/optical/IR telescopes to conduct imaging and spectroscopy studies. The SAT program is the Astrophysics Division's main investment method to mature technologies that will be identified by study teams set up to inform the 2020 Decadal Survey process on several large astrophysics mission concepts.

SPIE paper↗
NASA NTRS2011

Space Shuttle Ascent Flight Design Process: Evolution and Lessons Learned

The Space Shuttle Ascent Flight Design team is responsible for defining a launch to orbit trajectory profile that satisfies all programmatic mission objectives and defines the ground and onboard reconfiguration requirements for this high-speed and demanding flight phase. This design, verification and reconfiguration process ensures that all applicable mission scenarios are enveloped within integrated vehicle and spacecraft certification constraints and criteria, and includes the design of the nominal ascent profile and trajectory profiles for both uphill and ground-to-ground aborts. The team also develops a wide array of associated training, avionics flight software verification, onboard crew and operations facility products. These key ground and onboard products provide the ultimate users and operators the necessary insight and situational awareness for trajectory dynamics, performance and event sequences, abort mode boundaries and moding, flight performance and impact predictions for launch vehicle stages for use in range safety, and flight software performance. These products also provide the necessary insight to or reconfiguration of communications and tracking systems, launch collision avoidance requirements, and day of launch crew targeting and onboard guidance, navigation and flight control updates that incorporate the final vehicle configuration and environment conditions for the mission. Over the course of the Space Shuttle Program, ascent trajectory design and mission planning has evolved in order to improve program flexibility and reduce cost, while maintaining outstanding data quality. Along the way, the team has implemented innovative solutions and technologies in order to overcome significant challenges. A number of these solutions may have applicability to future human spaceflight programs.

Picka, Bret A.↗
NASA NTRS1993

Common front end systems for Space Shuttle and Space Station control centers at Johnson Space Center

In the beginning of the fiscal year 1992, the development organizations of Johnson Space Center (JSC) were poised to begin two major projects: the Space Station Control Center and the refurbishment of the telemetry processing area of the Space Shuttle Mission Control Center. A study team established that a common front end concept could be used and could reduce development costs for both projects. A standard processor was defined to support most of the front end functions of both control centers and supports a consolidation of control positions which effectively reduces operations cost. This paper defines that common concept and describes the progress that has been made in development of the Consolidated Communications Facility (CCF) during the past year.

Uljon, Linda↗
NASA NTRSDate not supplied

Science Objectives and Investigations for the Lunar GNSS Receiver Experiment (LuGRE)

In July 2020, NASA selected the Lunar GNSS Receiver Experiment (LuGRE) as the 10th payload of CLPS Task Order 19D. Firefly's Blue Ghost lander will deliver LuGRE and the other CLPS 19D payloads to the Moon's Mare Crisium. Developed jointly by NASA and the Italian Space Agency (ASI), LuGRE is intended to be the first demonstration of GNSS-based navigation beyond an altitude of 30 RE and the first to use GNSS on the lunar surface, expanding the proven reach of usable GNSS signals. Subsequent missions will be able to leverage LuGRE data and lessons learned to operationalize GNSS in the lunar regime, adding an existing, proven, real-time navigation source for spacecraft exploring the Moon. The primary goal of the LuGRE project is to extend GNSS-based navigation and timing to the Moon. LuGRE will fulfill this goal by gathering and processing GNSS data across several mission phases. The LuGRE Science Definition Team (SDT) was formed for the purpose of proposing science and technology investigations to be executed by the LuGRE project. A primary outcome of the work of the LuGRE SDT is a set of specific, high-value, achievable investigations to be performed as part of the science program. This paper provides a detailed description of the LuGRE science investigations and will present preliminary analyses that show how these investigations will be used to support the realization of lunar GNSS use in the future.

Lauren Konitzer↗
NASA NTRS2012

Concurrent Mission and Systems Design at NASA Glenn Research Center: The Origins of the COMPASS Team

Established at the NASA Glenn Research Center (GRC) in 2006 to meet the need for rapid mission analysis and multi-disciplinary systems design for in-space and human missions, the Collaborative Modeling for Parametric Assessment of Space Systems (COMPASS) team is a multidisciplinary, concurrent engineering group whose primary purpose is to perform integrated systems analysis, but it is also capable of designing any system that involves one or more of the disciplines present in the team. The authors were involved in the development of the COMPASS team and its design process, and are continuously making refinements and enhancements. The team was unofficially started in the early 2000s as part of the distributed team known as Team JIMO (Jupiter Icy Moons Orbiter) in support of the multi-center collaborative JIMO spacecraft design during Project Prometheus. This paper documents the origins of a concurrent mission and systems design team at GRC and how it evolved into the COMPASS team, including defining the process, gathering the team and tools, building the facility, and performing studies.

McGuire, Melissa L.↗
NASA NTRS2006

Achieving Operability via the Mission System Paradigm

In the past, flight and ground systems have been developed largely-independently, with the flight system taking the lead, and dominating the development process. Operability issues have been addressed poorly in planning, requirements, design, I&T, and system-contracting activities. In many cases, as documented in lessons-learned, this has resulted in significant avoidable increases in cost and risk. With complex missions and systems, operability is being recognized as an important end-to-end design issue. Never-the-less, lessons-learned and operability concepts remain, in many cases, poorly understood and sporadically applied. A key to effective application of operability concepts is adopting a 'mission system' paradigm. In this paradigm, flight and ground systems are treated, from an engineering and management perspective, as inter-related elements of a larger mission system. The mission system consists of flight hardware, flight software, telecom services, ground data system, testbeds, flight teams, science teams, flight operations processes, procedures, and facilities. The system is designed in functional layers, which span flight and ground. It is designed in response to project-level requirements, mission design and an operations concept, and is developed incrementally, with early and frequent integration of flight and ground components.

ground systems↗
NASA NTRS2003

Capabilities of the Materials Contamination Team at Marshall Space Flight Center

The Materials Contamination Team at the Marshall Space Flight Center (MSFC) has been recognized for its contributions supporting the National Aeronautics and Space Administration (NASA) spacecraft development programs. These programs include the Reusable Solid Rocket Motor (RSRM), Chandra X-Ray Observatory, and the International Space Station (ISS). The Environmental Effects Group, with the Materials Contamination Team and the Space Environmental Effects Team has been an integral part of NASA's success by the testing, evaluation, and qualification of materials, hardware, and processes. This paper focuses on the capabilities of the Materials Contamination Team. The Materials Contamination Team's realm of responsibility includes establishing contamination control during all phases of hardware development, including design, manufacturing, assembly, test, transportation, launch site processing, on-orbit exposure, return, and refurbishment. The team continues its mission of reducing the risk of equipment failure due to molecular or particulate contamination. Contamination is a concern in the Space Shuttle with sensitive bond-lines and reactive fluid (liquid oxygen) compatibility as well as for spacecraft with sensitive optics, such as Hubble Space Telescope and Chandra X-ray Observatory. The Materials Contamination Team has a variety of facilities and instrumentation capable of contaminant detection, identification, and monitoring. The team addresses material applications dealing with environments, including production facilities, clean rooms, and on-orbit exposure. The optically stimulated electron emission (OSEE) system, the Ultraviolet (UV) fluorescence (UVF) surface contamination detection, and the Surface Optics Corporation 400 (SOC 400) portable hand-held Fourier Transform Infrared (FTIR) spectrometer are state-of-the-art tools for in-process molecular contamination detection. The team of engineers and technicians also develop contamination calibration standards and evaluate new surface cleanliness inspection technologies. The team utilizes facilities for on-orbit simulation testing of materials for outgassing and molecular film deposition characteristics in the presence of space environmental effects, such as Atomic Oxygen (AO) and UV radiation exposure. The Materials Contamination Team maintains databases for process materials as well as outgassing and optical compatibility test results for specific environments.

Burns, Howard↗
NASA NTRS1994

Increases in efficiency and enhancements to the Mars Observer non-stored commanding process

The Mars Observer team was, until the untimely loss of the spacecraft on August 21, 1993, performing flight operations with greater efficiency and speed than any previous JPL mission of its size. This level of through-put was made possible by a mission operations system which was composed of skilled personnel using sophisticated sequencing and commanding tools. During cruise flight operations, however, it was realized by the project that this commanding level was not going to be sufficient to support the activities planned for mapping operations. The project had committed to providing the science instrument principle investigators with a much higher level of commanding during mapping. Thus, the project began taking steps to enhance the capabilities of the flight team. One mechanism used by project management was a tool available from total quality management (TQM). This tool is known as a process action team (PAT). The Mars Observer PAT was tasked to increase the capacity of the flight team's nonstored commanding process by fifty percent with no increase in staffing and a minimal increase in risk. The outcome of this effort was, in fact, to increase the capacity by a factor of 2.5 rather than the desired fifty percent and actually reduce risk. The majority of these improvements came from the automation of the existing command process. These results required very few changes to the existing mission operations system. Rather, the PAT was able to take advantage of automation capabilities inherent in the existing system and make changes to the existing flight team procedures.

Brooks, Robert N., Jr.↗
NASA NTRS2011

Remote Infrared Imaging of the Space Shuttle During Hypersonic Flight: HYTHIRM Mission Operations and Coordination

The Hypersonic Thermodynamic Infrared Measurements (HYTHIRM) project has been responsible for obtaining spatially resolved, scientifically calibrated in-flight thermal imagery of the Space Shuttle Orbiter during reentry. Starting with STS-119 in March of 2009 and continuing through to the majority of final flights of the Space Shuttle, the HYTHIRM team has to date deployed during seven Shuttle missions with a mix of airborne and ground based imaging platforms. Each deployment of the HYTHIRM team has resulted in obtaining imagery suitable for processing and comparison with computational models and wind tunnel data at Mach numbers ranging from over 18 to under Mach 5. This paper will discuss the detailed mission planning and coordination with the NASA Johnson Space Center Mission Control Center that the HYTHIRM team undergoes to prepare for and execute each mission.

Schwartz, Richard J.↗
NASA NTRS2007

Automatic Command Sequence Generation

Automatic Sequence Generator (Autogen) Version 3.0 software automatically generates command sequences for the Mars Reconnaissance Orbiter (MRO) and several other JPL spacecraft operated by the multi-mission support team. Autogen uses standard JPL sequencing tools like APGEN, ASP, SEQGEN, and the DOM database to automate the generation of uplink command products, Spacecraft Command Message Format (SCMF) files, and the corresponding ground command products, DSN Keywords Files (DKF). Autogen supports all the major multi-mission mission phases including the cruise, aerobraking, mapping/science, and relay mission phases. Autogen is a Perl script, which functions within the mission operations UNIX environment. It consists of two parts: a set of model files and the autogen Perl script. Autogen encodes the behaviors of the system into a model and encodes algorithms for context sensitive customizations of the modeled behaviors. The model includes knowledge of different mission phases and how the resultant command products must differ for these phases. The executable software portion of Autogen, automates the setup and use of APGEN for constructing a spacecraft activity sequence file (SASF). The setup includes file retrieval through the DOM (Distributed Object Manager), an object database used to store project files. This step retrieves all the needed input files for generating the command products. Depending on the mission phase, Autogen also uses the ASP (Automated Sequence Processor) and SEQGEN to generate the command product sent to the spacecraft. Autogen also provides the means for customizing sequences through the use of configuration files. By automating the majority of the sequencing generation process, Autogen eliminates many sequence generation errors commonly introduced by manually constructing spacecraft command sequences. Through the layering of commands into the sequence by a series of scheduling algorithms, users are able to rapidly and reliably construct the desired uplink command products. With the aid of Autogen, sequences may be produced in a matter of hours instead of weeks, with a significant reduction in the number of people on the sequence team. As a result, the uplink product generation process is significantly streamlined and mission risk is significantly reduced. Autogen is used for operations of MRO, Mars Global Surveyor (MGS), Mars Exploration Rover (MER), Mars Odyssey, and will be used for operations of Phoenix. Autogen Version 3.0 is the operational version of Autogen including the MRO adaptation for the cruise mission phase, and was also used for development of the aerobraking and mapping mission phases for MRO.

Fisher, Forest↗
NASA NTRS2014

SLS Trade Study 0058: Day of Launch (DOL) Wind Biasing

SLS heritage hardware and legacy designs have shown load exceedances at several locations during Design Analysis Cycles (DAC): MPCV Z bending moments; ICPS Electro-Mechanical Actuator (EMA) loads; Core Stage loads just downstream of Booster forward interface. SLS Buffet Loads Mitigation Task Team (BLMTT) tasked to study issue. Identified low frequency buffet load responses are a function of the vehicle's total angle of attack (AlphaTotal). SLS DOL Wind Biasing Trade team to analyze DOL wind biasing methods to limit maximum AlphaTotal in the M0.8 - 2.0 altitude region for EM-1 and EM-2 missions through investigating: Trajectory design process; Wind wavelength filtering options; Launch availability; DOL process to achieve shorter processing/uplink timeline. Trade Team consisted of personnel supporting SLS, MPCV, GSDO programs.

Decker, Ryan K.↗
NASA NTRS2013

Results from CrIS-ATMS Obtained Using the AIRS Science Team Retrieval Methodology

AIRS was launched on EOS Aqua in May 2002, together with AMSU-A and HSB (which subsequently failed early in the mission), to form a next generation polar orbiting infrared and microwave atmospheric sounding system. AIRS/AMSU had two primary objectives. The first objective was to provide real-time data products available for use by the operational Numerical Weather Prediction Centers in a data assimilation mode to improve the skill of their subsequent forecasts. The second objective was to provide accurate unbiased sounding products with good spatial coverage that are used to generate stable multi-year climate data sets to study the earth's interannual variability, climate processes, and possibly long-term trends. AIRS/AMSU data for all time periods are now being processed using the state of the art AIRS Science Team Version-6 retrieval methodology. The Suomi-NPP mission was launched in October 2011 as part of a sequence of Low Earth Orbiting satellite missions under the "Joint Polar Satellite System" (JPSS). NPP carries CrIS and ATMS, which are advanced infra-red and microwave atmospheric sounders that were designed as follow-ons to the AIRS and AMSU instruments. The main objective of this work is to assess whether CrIS/ATMS will be an adequate replacement for AIRS/AMSU from the perspective of the generation of accurate and consistent long term climate data records, or if improved instruments should be developed for future flight. It is critical for CrIS/ATMS to be processed using an algorithm similar to, or at least comparable to, AIRS Version-6 before such an assessment can be made. We have been conducting research to optimize products derived from CrIS/ATMS observations using a scientific approach analogous to the AIRS Version-6 retrieval algorithm. Our latest research uses Version-5.70 of the CrIS/ATMS retrieval algorithm, which is otherwise analogous to AIRS Version-6, but does not yet contain the benefit of use of a Neural-Net first guess start-up system which significantly improved results of AIRS Version-6. Version-5.70 CrIS/ATMS temperature profile and surface skin temperature retrievals are of very good quality, and are better than AIRS Version-5 retrievals, but are still significantly poorer than those of AIRS Version-6. CrIS/ATMS retrievals should improve when a Neural-Net start-up system is ready for use. We also examined CrIS/ATMS retrievals generated by NOAA using their NUCAPS retrieval algorithm, which is based on earlier versions of the AIRS Science Team retrieval algorithms. We show that the NUCAPS algorithm as currently configured is not well suited for climate monitoring purposes.

CrIS↗
NASA NTRS2006

Integrating International Engineering Organizations For Successful ISS Operations

The International Space Station (ISS) is a multinational orbiting space laboratory that is built in cooperation with 16 nations. The design and sustaining engineering expertise is spread worldwide. As the number of Partners with orbiting elements on the ISS grows, the challenge NASA is facing as the ISS integrator is to ensure that engineering expertise and data are accessible in a timely fashion to ensure ongoing operations and mission success. Integrating international engineering teams requires definition and agreement on common processes and responsibilities, joint training and the emergence of a unique engineering team culture. ISS engineers face daunting logistical and political challenges regarding data sharing requirements. To assure systematic information sharing and anomaly resolution of integrated anomalies, the ISS Partners are developing multi-lateral engineering interface procedures. Data sharing and individual responsibility are key aspects of this plan. This paper describes several examples of successful multilateral anomaly resolution. These successes were used to form the framework of the Partner to Partner engineering interface procedures, and this paper describes those currently documented multilateral engineering processes. Furthermore, it addresses the challenges experienced to date, and the forward work expected in establishing a successful working relationship with Partners as their hardware is launched.

Blome, Elizabeth↗
NASA NTRSDate not supplied

IMERG Multi-Satellite Products Across Two Decades

The Version 06 Global Precipitation Measurement (GPM) mission products were completed over the last year, capping five years of development since the launch of the GPM Core Observatory, and covering the joint Tropical Rainfall Measuring Mission (TRMM) and GPM eras with consistently processed algorithms. The U.S. GPM team’s Integrated Multi-satellitE Retrievals for GPM (IMERG) merged precipitation product enforces a consistent intercalibration for all precipitation products computed from individual satellites with the TRMM and GPM Core Observatory sensors as the TRMM- and GPM-era calibrators, respectively, and incorporates monthly surface gauge data in the Final (research) product. Mid-latitude calibrations during the TRMM era necessarily are more approximate because TRMM only covered the latitude band 35°N-S, while GPM covers 65°N-S. Starting in V06, IMERG employs precipitation motion vectors (used to drive the quasi-Lagrangian interpolation, or “morphing”) that are computed by tracking the vertically integrated vapor as analyzed in MERRA2 and GEOS FP. This approach covers the entire globe, expanding coverage beyond the 60°N-S latitude band provided by IR-based vectors in previous versions, although we choose to mask out microwave-based precipitation over snowy/icy surfaces as unreliable. We will provide examples of performance for the V06 IMERG products, including comparison with the long-term record of GPCP and TMPA, showing higher values by about 8% in the latitude band 50°N-S over oceans; diurnal cycle, demonstrating improvement over previous versions; and daily precipitation PDFs for the entire record, showing a shift at the TRMM/GPM boundary, as well as interannual variations. These analyses have important implications for the utility of V06 IMERG data for long-record calculations. Finally, we will review the retirement of the predecessor TMPA multi-satellite dataset.

George J. Huffman↗
NASA NTRS2018

Costing at the Speed of Light: How Your Concurrent Engineering Design Team can Bootstrap Your Organizations Programmatic Capabilities

What do you do when it is necessary to generate reasonable cost estimates at the earliest Concept Maturity Levels and you have never flown any similar missions before? This paper describes the current and future Team X cost processes and methods, how they are being used to expand our data frontiers and cost modelling capabilities, and how this enables the ability to estimate early and estimate often.

Ramirez, Matthew↗