Development and Validation of 2D Finite Difference Modeling of Heat Transfer, Degree of Healing, and Stress Development in FFF Printing
Explore the source record for details and available documents.
Eric Gilmer↗
SEARCH · Engineering Papers
Results for “Development”
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.
Huntsville Urban Development: Utilizing NASA Earth Observations to Evaluate Urban Tree Canopy and Land Surface Temperature for Green Infrastructure Development and Urban Heat Mitigation in Huntsville, AL
Huntsville, Alabama’s population has grown by approximately 11% since 2010, due in part to the city’s advancing engineering industry. Rapid urban growth negatively impacts the environment by decreasing tree canopy cover and increasing impervious surface cover, which can intensify the urban heat island effect. To examine the impacts of this urban growth on the environment, the team partnered with the City of Huntsville to utilize Landsat 5 Thematic Mapper (TM), Landsat 8 Operational Land Imager (OLI) and Thermal Infrared Sensor (TIRS), Terra Moderate Resolution Imaging Spectroradiometer (MODIS) and the International Space Station’s Global Ecosystems Dynamic Investigation (GEDI) and ECOsystem Spaceborne Thermal Radiometer Experiment on Space Station (ECOSTRESS). The team utilized these Earth observations in combination with ancillary datasets to create a suite of end products to assist in mitigating the effects of extreme heat due to urban expansion and tree canopy loss. Annual land surface temperature (LST) was calculated and land cover classes were derived through supervised and threshold classification methods to distinguish trees, other vegetation types, impervious surfaces, and water. From 2010 to 2019, LST increased approximately 4 °F for all census tracts within the city and the total amount of tree cover increased by approximately 3%. The findings will aid the city in future decision-making processes by indicating areas that would benefit from increased green infrastructure.
Greta Paris↗
Huntsville Urban Development: Utilizing NASA Earth Observations to Evaluate Urban Tree Canopy and Land Surface Temperature for Green Infrastructure Development and Urban Heat Mitigation in Huntsville, Alabama
Huntsville, Alabama’s population has grown by approximately 11% since 2010, due in part to the city’s advancing engineering industry. Rapid urban growth negatively impacts the environment by decreasing tree canopy cover and increasing impervious surface cover, which can intensify the urban heat island effect. To examine the impacts of this urban growth on the environment, the team partnered with the City of Huntsville to utilize Landsat 5 Thematic Mapper (TM), Landsat 8 Operational Land Imager (OLI) and Thermal Infrared Sensor (TIRS), Terra Moderate Resolution Imaging Spectroradiometer (MODIS) and the International Space Station’s Global Ecosystems Dynamic Investigation (GEDI) and ECOsystem Spaceborne Thermal Radiometer Experiment on Space Station (ECOSTRESS). The team utilized these Earth observations in combination with ancillary datasets to create a suite of end products to assist in mitigating the effects of extreme heat due to urban expansion and tree canopy loss. Annual land surface temperature (LST) was calculated and land cover classes were derived through supervised and threshold classification methods to distinguish trees, other vegetation types, impervious surfaces, and water. From 2010 to 2019, LST increased approximately 4 °F for all census tracts within the city and the total amount of tree cover increased by approximately 3%. The findings will aid the city in future decision-making processes by indicating areas that would benefit from increased green infrastructure.
Greta Paris↗
Development of Low Earth Orbit (LEO) Space-based Research and Development (R&D) Across the Federal Government Research Community
Explore the source record for details and available documents.
Commercial LEO↗
Development of a Cyber-Physical Model and Emulation of an Oil and Gas Compressor Station for Cybersecurity Research and Development
Explore the source record for details and available documents.
Beauchaine, Adam James↗
Development of a Downhole Piston Motor Power Section for Improved Directional Drilling, Part II - Motor Development and Testing
Explore the source record for details and available documents.
Raymond, David W. [Sandia National Laboratories (S↗
Hardware Development Process for Human Research Facility Applications
The simple goal of the Human Research Facility (HRF) is to conduct human research experiments on the International Space Station (ISS) astronauts during long-duration missions. This is accomplished by providing integration and operation of the necessary hardware and software capabilities. A typical hardware development flow consists of five stages: functional inputs and requirements definition, market research, design life cycle through hardware delivery, crew training, and mission support. The purpose of this presentation is to guide the audience through the early hardware development process: requirement definition through selecting a development path. Specific HRF equipment is used to illustrate the hardware development paths. The source of hardware requirements is the science community and HRF program. The HRF Science Working Group, consisting of SCientists from various medical disciplines, defined a basic set of equipment with functional requirements. This established the performance requirements of the hardware. HRF program requirements focus on making the hardware safe and operational in a space environment. This includes structural, thermal, human factors, and material requirements. Science and HRF program requirements are defined in a hardware requirements document which includes verification methods. Once the hardware is fabricated, requirements are verified by inspection, test, analysis, or demonstration. All data is compiled and reviewed to certify the hardware for flight. Obviously, the basis for all hardware development activities is requirement definition. Full and complete requirement definition is ideal prior to initiating the hardware development. However, this is generally not the case, but the hardware team typically has functional inputs as a guide. The first step is for engineers to conduct market research based on the functional inputs provided by scientists. CommerCially available products are evaluated against the science requirements as well as modifications needed to meet program requirements. Options are consolidated and the hardware development team reaches a hardware development decision point. Within budget and schedule constraints, the team must decide whether or not to complete the hardware as an in-house, subcontract with vendor, or commercial-off-the-shelf (COTS) development. An in-house development indicates NASA personnel or a contractor builds the hardware at a NASA site. A subcontract development is completed off-site by a commercial company. A COTS item is a vendor product available by ordering a specific part number. The team evaluates the pros and cons of each development path. For example, in-bouse developments utilize existing corporate knowledge regarding bow to build equipment for use in space. However, technical expertise would be required to fully understand the medical equipment capabilities, such as for an ultrasound system. It may require additional time and funding to gain the expertise that commercially exists. The major benefit of subcontracting a hardware development is the product is delivered as an end-item and commercial expertise is utilized. On the other hand, NASA has limited control over schedule delays. The final option of COTS or modified COTS equipment is a compromise between in-house and subcontracts. A vendor product may exist that meets all functional requirements but req uires in-house modifications for successful operation in a space environment. The HRF utilizes equipment developed using all of the paths described: inhouse, subcontract, and modified COTS.
Bauer, Liz↗
Psyche Early Project Verification & Validation Planning Development
The Psyche mission to the asteroid (16) Psyche was selected as the fourteenth mission in the Discovery program in January 2017. The Psyche mission will determine if (16) Psyche is the core of a larger differentiated body. As part of the development of this mission a Verification and Validation (V&V) engineer was assigned early in the project’s design Phase B. This paper will discuss some of the strategies that the Psyche team is using to take full advantage of the early planning for V&V on flight projects and specifically how the Psyche mission is approaching these tasks. This paper will discuss the effects of having a V&V mindset on: 1) The Psyche requirements development process, and how focusing not only on how the team will verify these requirements but also on developing the tools necessary to track and monitor that verification feeds back into the requirement development process. 2) The Psyche testbed development, and how using a verification mindset is useful for identifying holes in the testbed development process, including the required testbed speed and how to think about testbed certification early in the process while encouraging trades and developing relationships with the testbed team. 3) Developing new V&V Tools for Psyche, and how developing tools early in the project development process means that they can influence the development of other requirement and scheduling tools. 4) Verification Activity Planning, which is typically done to a preliminary level during Phase B of the project, and is important for understanding the major testing that is needed to ensure that the system as built represents the design. On Psyche we are not only focused on bringing this planning to a preliminary level, we are also developing a V&V focused schedule to help us de-conflict V&V activities that may require similar resources early on in the program’s development. 5) Validation Planning, for which we are working with the testbed and model development teams to ensure that their models can be effectively validated and that the plans to do so are in place. In this paper we will describe how the Psyche mission is approaching each of these V&V areas and identify lessons that can be taken by other space missions trying to decide how much effort should be put into V&V early in the project lifecycle.
Solish, Benjamin↗
Traffic Management Advisor: Iterative Field Development and Assessment at Multiple Sites
Previous studies have demonstrated the necessity of involving users in the development of automation aids, especially for complex domains such as air traffic control (ATC). Traditional development only demanded a single field test to validate a completed system, but a more iterative combination of development and assessment ensures that the technology meets the requirements of its application domain. Exposure across an adequate spectrum of field users is also required during development, and the use of multiple development sites provides an opportunity to consider individual facility cultures as they relate to implementation strategies. The development of the Center/TRACON Automation System (CTAS) Traffic Management Advisor (TMA) at the Denver and Dallas ATC facilities demonstrates successful iterative development and assessment at multiple field sites. The use of field development changes the nature of assessment. As development progresses, periodic assessments are required to validate that system development is progressing along an appropriate track. In the development of the TMA, assessments were performed based on software in the field, and input from traffic managers was analyzed and incorporated into subsequent releases of the TMA, to be reassessed in the field. This has led to a tool with operational suitability and broad user acceptance. Assessment at multiple sites provides a more generalizable perspective that allows the production of a system that is both generic enough to be used at different sites and tailored enough to be of use at any site. In addition to providing a better understanding of specific facility requirements, the use of multiple assessment sites in the development of TMA has provided an opportunity to consider individual facility operations, procedures and cultures as they relate to development and implementation strategies.
Sanford, Beverly D.↗
A Roadmap for Using Agile Development in a Traditional Environment
One of the newer classes of software engineering techniques is called 'Agile Development'. In Agile Development software engineers take small implementation steps and, in some cases they program in pairs. In addition, they develop automatic tests prior to implementing their small functional piece. Agile Development focuses on rapid turnaround, incremental planning, customer involvement and continuous integration. Agile Development is not the traditional waterfall method or even a rapid prototyping method (although this methodology is closer to Agile Development). At Jet Propulsion Laboratory (JPL) a few groups have begun Agile Development software implementations. The difficulty with this approach becomes apparent when Agile Development is used in an organization that has specific criteria and requirements handed down for how software development is to be performed. The work at the JPL is performed for the National Aeronautics and Space Agency (NASA). Both organizations have specific requirements, rules and procedure for developing software. This paper will discuss the some of the initial uses of the Agile Development methodology, the spread of this method and the current status of the successful incorporation into the current JPL development policies.
Agile Development↗
A Roadmap for Using Agile Development in a Traditional Environment
One of the newer classes of software engineering techniques is called 'Agile Development'. In Agile Development software engineers take small implementation steps and, in some cases, they program in pairs. In addition, they develop automatic tests prior to implementing their small functional piece. Agile Development focuses on rapid turnaround, incremental planning, customer involvement and continuous integration. Agile Development is not the traditional waterfall method or even a rapid prototyping method (although this methodology is closer to Agile Development). At the Jet Propulsion Laboratory (JPL) a few groups have begun Agile Development software implementations. The difficulty with this approach becomes apparent when Agile Development is used in an organization that has specific criteria and requirements handed down for how software development is to be performed. The work at the JPL is performed for the National Aeronautics and Space Agency (NASA). Both organizations have specific requirements, rules and processes for developing software. This paper will discuss some of the initial uses of the Agile Development methodology, the spread of this method and the current status of the successful incorporation into the current JPL development policies and processes.
software methodology↗
Software development in Ada
Ada will soon become a part of systems developed for the US Department of Defense. NASA must determine whether it will become part of its environment and particularly whether it will become a part fo the space station development. However, there are several issues about Ada which should be considered before this decision is made. One means of considering these issues is the examination of other developments in Ada. Unfortunately, few full scale developments have been completed or made publicly available for observation. Therefore, it will probably be necessary to study an Ada development in a NASA environment. Another means related to the first is the development of Ada metrics which can be used to characterize and evaluate Ada developments. These metrics need not be confined to full scale developments and could be used to evaluate on going projects as well. An early development in Ada, some observations from that development, metrics which were developed for use with Ada, and future directions for research into the use of Ada in software development in general and in the NASA Goddard environment in particular are described.
Basili, V. R.↗
Hot Structure Control Surface Progress for X-37 Technology Development Program
The NASA Marshall Space Flight Center (MSFC) has been leading the development of technologies that will enable the development, fabrication, and flight of the automated X-37 Orbital Vehicle (OV). With the Administration s recent announcement of the Vision for Space Exploration, NASA placed the X-37 OV design on hold while developing detailed requirements for a Crew Exploration Vehicle, but has continued funding the development of high-risk, critical technologies for potential future space exploration vehicle applications. Hot Structure Control Surfaces (HSCS) technology development is one of the high-priority areas being funded at this time. The goal of HSCS research is to mitigate risk by qualifying the lightest possible components that meet the stringent X-37 OV weight and performance requirements, including Shuttle-type reen- try environments with peak temperatures of 2800 OF. The small size of the X-37 OV (25.7-feet long and 14.9-foot wingspan) drives the need for advanced HSCS because the vehicle's two primary aerodynamic surfaces, the flaperons and ruddervators, have thicknesses ranging from approximately 5 in. down to 1 in. Traditional metallic or polymer-matrix composites covered with tile or blanket thermal protection system (TPS) materials cannot be used as there is insufficient volume to fabricate such multi-component structures. Therefore, carbon-carbon (C-C) and carbodsilicon-carbide (C-SiC) composite HSCS structures are being developed in parallel by two teams supporting the X-37 prime contractor (The Boeing Company). The Science Applications International Coy. (SAIC) and Carbon-Carbon Advanced Technologies, Inc. (C-CAT) team is developing the C-C HSCS, while the General Electric Energy Power Systems Composites (GE-PSC) and Materials Research and Design (MRD) team is developing the C-SiC HSCS. These two teams were selected to reduce the high level of risk associated with developing advanced control surface components. They have continued HSCS development work as part of the X-37 critical technology development contract. The SAIC/C-CAT team is using Advanced Carbon-Carbon (ACC) because its fabrication is very similar to the process used for Space Shuttle Reinforced Carbon-Carbon fabrication, including the Sic-based pack cementation conversion coating systems using with both materials. ACC was selected over RCC because it has much higher tension and compressions strengths, and because T-300 fiber is readily available, whereas RCC rayon fiber is no longer manufactured. The GE-PSC/MRD team is using a T-300 fiber-reinforced Sic matrix composite material densified by chemical vapor infiltration. The C-Sic material has an Sic-based environmental barrier coating. Major accomplishments have been made over the past year by both HSCS teams. C-C and C- SiC flaperon subcomponents, which are truncated full-scale versions of flight hardware, have been fabricated and are undergoing testing at the NASA Dryden Flight Research Center, NASA Langley Research Center, and U.S. Air Force Research Laboratory. By the end of 2004, ruddervator subcomponents also will be delivered and tested. As NASA moves forward in realizing the Vision for Space Exploration, it will continue to invest in advanced research and development aimed at making new generations of spacecraft safer, more reliable, and more affordable. The X-37 HSCS effort ultimately will benefit the Agency's vision and mission.
Valentine, P. G.↗
YAM- A Framework for Rapid Software Development
YAM is a software development framework with tools for facilitating the rapid development and integration of software in a concurrent software development environment. YAM provides solutions for thorny development challenges associated with software reuse, managing multiple software configurations, the development of software product-lines, multiple platform development and build management. YAM uses release-early, release-often development cycles to allow developers to incrementally integrate their changes into the system on a continual basis. YAM facilitates the creation and merging of branches to support the isolated development of immature software to avoid impacting the stability of the development effort. YAM uses modules and packages to organize and share software across multiple software products. It uses the concepts of link and work modules to reduce sandbox setup times even when the code-base is large. One side-benefit is the enforcement of a strong module-level encapsulation of a module s functionality and interface. This increases design transparency, system stability as well as software reuse. YAM is in use by several mid-size software development teams including ones developing mission-critical software.
simulations↗
Advanced Lithium-Ion Cell Development for NASA's Constellation Missions
The Energy Storage Project of NASA s Exploration Technology Development Program is developing advanced lithium-ion batteries to meet the requirements for specific Constellation missions. NASA GRC, in conjunction with JPL and JSC, is leading efforts to develop High Energy and Ultra High Energy cells for three primary Constellation customers: Altair, Extravehicular Activities (EVA), and Lunar Surface Systems. The objective of the High Energy cell development is to enable a battery system that can operationally deliver approximately 150 Wh/kg for 2000 cycles. The Ultra High Energy cell development will enable a battery system that can operationally deliver 220 Wh/kg for 200 cycles. To accomplish these goals, cathode, electrolyte, separator, and safety components are being developed for High Energy Cells. The Ultra High Energy cell development adds lithium alloy anodes to the component development portfolio to enable much higher cell-level specific energy. The Ultra High Energy cell development is targeted for the ascent stage of Altair, which is the Lunar Lander, and for power for the Portable Life support System of the EVA Lunar spacesuit. For these missions, mass is highly critical, but only a limited number of cycles are required. The High Energy cell development is primarily targeted for Mobility Systems (rovers) for Lunar Surface Systems, however, due to the high risk nature of the Ultra High Energy cell development, the High Energy cell will also serve as a backup technology for Altair and EVA. This paper will discuss mission requirements and the goals of the material, component, and cell development efforts in further detail.
Reid, Concha M.↗
Digital Prototyping Methods to Enable Product Development Analysis Cycle Compression in Aerospace Systems
Historically, the product development life cycle (spanning from origination of a systems concept to initial delivery or fielding) for large-scale aerospace systems is 10-25 years. Examples of recent programs exhibiting this timeline are the Space Shuttle (13 years), , International Space Station (18 years), NASA Hubble telescope (16 years), USAF F-35 Strike Fighter (22 years), Missile Defense Agency THAAD (21 years), USAF V-22 Osprey (26 years), USAF B-2 Spirt (19 years), US Army RAH-66 Comanche (22 years, cancelled prior to fielding), James Webb Space Telescope (25 years), Space Launch System (10 years). This list illustrates the challenges of developing and fielding a modern integrated multi-disciplinary aerospace system. These development timelines are often preceded by significant research and development programs and followed by multiple increments, blocks, or spirals to reach planned operational capability. In the modern era of aerospace system acquisition, there is significant pressure to reduce system development timelines to meet system objectives and enable competitiveness in the current industry and landscape. Across the aerospace industry, a range of rapid acquisition and prototyping programs are seeking to achieve system development within timelines considerably less than 10 years. Notably, in September of 2019, NASA issued a solicitation for the development and demonstration of a Human Landing System (HLS) to deliver humans to the lunar surface by 2024 (5 years) and for the development and demonstration of a more sustainable HLS by 2026 (7 years). Lengthy product development cycle timelines are a product of multiple factors ranging from programmatic, sociological, technical, and systems engineering issues. New approaches in systems engineering provide new ways to enable these compressed development timelines. These approaches employ expanded application of advanced systems engineering methods and cross-cutting digital tools to accelerate system development, utilizing digital prototyping to connect maturing sub-system or component technologies into system or system-of-systems hardware prototypes. Approaches such as the use of system integrating physics relationships to reduce the number of design analysis cycle iterations and state analysis modeling to reduce necessary software testing (and improving coverage of system execution scenarios) represent steps forward in reducing the engineering time needed to field new systems. In addition to cost, schedule and performance benefits, expanded digital exploration and demonstration reduce risk in live system test and demonstration. This incremental demonstration approach, where digital prototyping and demonstration leads and informs full system test and demonstration, could be more important for space applications because of the increased difficulty of test and demonstration of space systems and architectures. The Advanced Concepts Office (ACO) at Marshall Space Flight Center merges traditional multi-disciplinary concept definition methods with modern, cross-cutting systems engineering concepts to enable iterative design and analysis of space architectures and systems through coordinated, strategic management of human capital, technical processes, and technology. This paper provides an overview of that approach, including recent examples and a strategic path forward to enabling continued reduction of aerospace system product development life cycles.
Michael D Watson↗
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↗
Under-capacitated and over-powered? Rural austerity and asymmetrical negotiating relationships in US wind energy development
Though rural local governments are central actors in renewable energy development, local governments in the United States (US) remain systematically under-funded. This paper considers what the manifestations of austerity in local governments broadly and rural localities specifically mean for renewable energy development and for energy transitions. Drawing on a survey of 262 elected county officials with experience with wind energy in eight US states, this paper asks how local officials understand the impacts of wind development, how local governments are involved in wind energy negotiations, how the resources and expertise needed to navigate negotiations are distributed among counties, and analyze the relationship between local capacity, access to resources, and involvement in negotiations. We find that local officials express simultaneously affective and material concerns with the impacts of wind development and see negotiations with the developer as central to realizing local benefits. However, the expertise and staffing needed to negotiate with developers is less accessible to poorer or sparsely populated counties, and counties with lower overall revenues have narrower scopes of negotiation, and counties incre. Our results suggest that uneven rural capacity heightens an already asymmetrical relationship between localities and developers. In analyzing how infrastructure developments are shaped by relationships between localities and developers that are conditioned by austerity and (under)capacity, this paper contributes to and bridges scholarly discussions on rural austerity, rescaling, and renewable energy transitions. These results challenge conventional wisdoms around centralizing energy siting processes, contextualize popular and academic debates about opposition to renewable energy development, and highlight the need for rural reinvestment to realize meaningfully participatory energy developments.
Elmallah, Salma↗