Search NASA⌕ Search

SEARCH · Search NASA

Results for “estimating guidelines”

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.

194 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS2022

Global Premature Mortality By Dust and Pollution PM 2.5 Estimated From Aerosol Reanalysis of the Modern-Era Retrospective Analysis for Research and Applications, Version 2

This study quantifies global premature deaths attributable to long-term exposure of ambient PM 2.5 , or PM 2.5 -attributable mortality, by dust and pollution sources. We used NASA’s Modern-Era Retrospective Analysis for Research and Applications, Version 2 (MERRA-2) aerosol reanalysis product for PM 2.5 and the cause-specific relative risk (RR) from the integrated exposure-response (IER) model to estimate global PM2.5-attributable mortality for five causes of deaths, namely ischaemic heart disease (IHD), cerebrovascular disease (CEV) or stroke, lung cancer (LC), chronic obstructive pulmonary disease (COPD), and acute lower respiratory infection (ALRI). The estimated yearly global PM 2.5 -attributable mortality in 2019 amounts to 2.89 (1.38–4.48) millions, which is composed of 1.19 (0.73–1.84) million from IHD, 1.01 (0.35–1.55) million from CEV, 0.29 (0.11–0.48) million from COPD, 0.23 (0.14–0.33) million from ALRI, and 0.17 (0.04–0.28) million from LC (the numbers in parentheses represent the estimated mortality range due corresponding to RR spread at the 95% confidence interval). The mortality counts vary with geopolitical regions substantially, with the highest number of deaths occurring in Asia. China and India account for 40% and 23% of the global PM 2.5 -attributable deaths, respectively. In terms of sources of PM 2.5 , about 22% of the global all-cause PM 2.5 -attributable deaths are caused by desert dust. The largest dust attribution is 37% for ALRI. The relative contributions of dust and pollution sources vary with the causes of deaths and geographical regions. Enforcing air pollution regulations to transfer areas from PM 2.5 nonattainment to PM2.5 attainment can have great health benefits. Being attainable with the United States air quality standard (AQS) of 15 μg/m 3 globally would have avoided nearly 40% or 1.2 million premature deaths. The most recent update of PM 2.5 guideline from 10 to 5 μg/m 3 by the World Health Organization (WHO) would potentially save additional one million lives. Our study highlights the importance of distinguishing aerodynamic size from geometric size in accurately assessing the global health burden of PM 2.5 and particularly for dust. A use of geometric size in diagnosing dust PM 2.5 from the model simulation, a common approach in current health burden assessment, could overestimate the PM 2.5 level in the dust belt by 40–170%, leading to an overestimate of global all-cause mortality by 1 million or 32%.

PM2.5↗
NASA NTRS2014

Pharmacokinetic Modeling of Intranasal Scopolamine in Plasma Saliva and Urine

An intranasal gel formulation of scopolamine (INSCOP) was developed for the treatment of Space Motion Sickness. The bioavailability and pharmacokinetics (PK) were evaluated under the Food and Drug Administration guidelines for clinical trials for an Investigative New Drug (IND). The aim of this project was to develop a PK model that can predict the relationship between plasma, saliva and urinary scopolamine concentrations using data collected from the IND clinical trial with INSCOP. METHODS: Twelve healthy human subjects were administered three dose levels (0.1, 0.2 and 0.4 mg) of INSCOP. Serial blood, saliva and urine samples were collected between 5 min to 24 h after dosing and scopolamine concentrations measured by using a validated LC-MS-MS assay. Pharmacokinetic Compartmental models, using actual dosing and sampling times, were built using Phoenix (version 1.2). Model discrimination was performed, by minimizing the Akaike Information Criteria (AIC), maximizing the coefficient of determination (r²) and by comparison of the quality of fit plots. RESULTS: The best structural model to describe scopolamine disposition after INSCOP administration (minimal AIC =907.2) consisted of one compartment for plasma, saliva and urine respectively that were inter-connected with different rate constants. The estimated values of PK parameters were compiled in Table 1. The model fitting exercises revealed a nonlinear PK for scopolamine between plasma and saliva compartments for K21, Vmax and Km. CONCLUSION: PK model for INSCOP was developed and for the first time it satisfactorily predicted the PK of scopolamine in plasma, saliva and urine after INSCOP administration. Using non-linear PK yielded the best structural model to describe scopolamine disposition between plasma and saliva compartments, and inclusion of non-linear PK resulted in a significant improved model fitting. The model can be utilized to predict scopolamine plasma concentration using saliva and/or urine data that allows non-invasive assessment of pharmacotherapeutics of scopolamine in space and other remote environments without requiring blood sampling.

Wu, L.↗
NASA NTRS2014

A Population Pharmacokinetic Model for Disposition in Plasma, Saliva and Urine of Scopolamine after Intranasal Administration to Healthy Human Subjects

An intranasal gel formulation of scopolamine (INSCOP) was developed for the treatment of Space Motion Sickness. The bioavailability and pharmacokinetics (PK) were evaluated under the Food and Drug Administration guidelines for clinical trials with an Investigative New Drug (IND) protocol. The aim of this project was to develop a PK model that can predict the relationship between plasma, saliva and urinary scopolamine concentrations using data collected from the IND clinical trials with INSCOP. Methods: Twelve healthy human subjects were administered three dose levels (0.1, 0.2 and 0.4 mg) of INSCOP. Serial blood, saliva and urine samples were collected between 5 min and 24 h after dosing and scopolamine concentrations were measured by using a validated LC‐MS‐MS assay. Pharmacokinetic Compartmental models, using actual dosing and sampling times, were built using Phoenix (version 1.2). Model selection was based on the likelihood ratio test on the difference of criteria (‐2LL) and comparison of the quality of fit plots. Results: The best structural model for INSCOP (minimal ‐2LL= 502.8) was established. It consisted of one compartment each for plasma, saliva and urine, respectively, which were connected with linear transport processes except the nonlinear PK process from plasma to saliva compartment. The best‐fit estimates of PK parameters from individual PK compartmental analysis and Population PK model analysis were shown in Tables 1 and 2, respectively. Conclusion: A population PK model that could predict population and individual PK of scopolamine in plasma, saliva and urine after dosing was developed and validated. Incorporating a non‐linear transfer from plasma to saliva compartments resulted in a significantly improved model fitting. The model could be used to predict scopolamine plasma concentrations from salivary and urinary drug levels, allowing non‐invasive therapeutic monitoring of scopolamine in space and other remote environments.

Wu, L.↗
NASA NTRS1999

A Comparison of Single-Cycle Versus Multiple-Cycle Proof Testing Strategies

Single-cycle and multiple-cycle proof testing (SCPT and MCPT) strategies for reusable aerospace propulsion system components are critically evaluated and compared from a rigorous elastic-plastic fracture mechanics perspective. Earlier MCPT studies are briefly reviewed. New J-integral estimation methods for semielliptical surface cracks and cracks at notches are derived and validated. Engineering methods are developed to characterize crack growth rates during elastic-plastic fatigue crack growth (FCG) and the tear-fatigue interaction near instability. Surface crack growth experiments are conducted with Inconel 718 to characterize tearing resistance, FCG under small-scale yielding and elastic-plastic conditions, and crack growth during simulated MCPT. Fractography and acoustic emission studies provide additional insight. The relative merits of SCPT and MCPT are directly compared using a probabilistic analysis linked with an elastic-plastic crack growth computer code. The conditional probability of failure in service is computed for a population of components that have survived a previous proof test, based on an assumed distribution of initial crack depths. Parameter studies investigate the influence of proof factor, tearing resistance, crack shape, initial crack depth distribution, and notches on the MCPT versus SCPT comparison. The parameter studies provide a rational basis to formulate conclusions about the relative advantages and disadvantages of SCPT and MCPT. Practical engineering guidelines are proposed to help select the optimum proof test protocol in a given application.

McClung, R. C.↗
NASA NTRS1996

A Comparison of Single-Cycle Versus Multiple-Cycle Proof Testing Strategies

Single-cycle and multiple-cycle proof testing (SCPT and MCPT) strategies for reusable aerospace propulsion system components are critically evaluated and compared from a rigorous elastic-plastic fracture mechanics perspective. Earlier MCPT studies are briefly reviewed. New J-integral estimation methods for semi-elliptical surface cracks and cracks at notches are derived and validated. Engineering methods are developed to characterize crack growth rates during elastic-plastic fatigue crack growth (FCG) and the tear-fatigue interaction near instability. Surface crack growth experiments are conducted with Inconel 718 to characterize tearing resistance, FCG under small-scale yielding and elastic-plastic conditions, and crack growth during simulated MCPT. Fractography and acoustic emission studies provide additional insight. The relative merits of SCPT and MCPT are directly compared using a probabilistic analysis linked with an elastic-plastic crack growth computer code. The conditional probability of failure in service is computed for a population of components that have survived a previous proof test, based on an assumed distribution of initial crack depths. Parameter studies investigate the influence of proof factor, tearing resistance, crack shape, initial crack depth distribution, and notches on the MCPT vs. SCPT comparison. The parameter studies provide a rational basis to formulate conclusions about the relative advantages and disadvantages of SCPT and MCPT. Practical engineering guidelines are proposed to help select the optimum proof test protocol in a given application.

McClung, R. C.↗
NASA NTRS1996

A Comparison of Single-Cycle Versus Multiple-Cycle Proof Testing Strategies

Single-cycle and multiple-cycle proof testing (SCPT and MCPT) strategies for reusable aerospace propulsion system components are critically evaluated and compared from a rigorous elastic-plastic fracture mechanics perspective. Earlier MCPT studies are briefly reviewed. New J-integral estimation methods for semi-elliptical surface cracks and cracks at notches are derived and validated. Engineering methods are developed to characterize crack growth rates during elastic-plastic fatigue crack growth (FCG) and the tear-fatigue interaction near instability. Surface crack growth experiments are conducted with Inconel 718 to characterize tearing resistance, FCG under small-scale yielding and elastic-plastic conditions, and crack growth during simulated MCPT. Fractography and acoustic emission studies provide additional insight. The relative merits of SCPT and MCPT are directly compared using a probabilistic analysis linked with an elastic-plastic crack growth computer code. The conditional probability of failure in service is computed for a population of components that have survived a previous proof test, based on an assumed distribution of initial crack depths. Parameter studies investigate the influence of proof factor, tearing resistance, crack shape, initial crack depth distribution, and notches on the MCPT vs. SCPT comparison. The parameter studies provide a rational basis to formulate conclusions about the relative advantages and disadvantages of SCPT and MCPT. Practical engineering guidelines are proposed to help select the optimum proof test protocol in a given application.

McClung, R. C.↗
NASA NTRSDate not supplied

VSLAM and Vision-based Approach and Landing for Advanced Air Mobility

Advanced Air Mobility (AAM) aircraft have many challenges in landing accurately and safely in urban, suburban, and rural environments. Localization in large and open rural environments could utilize GPS, but AAM aircraft in urban environments will encounter GPS degradation. Another challenge involves flight operation time, i.e., flying during the day or at night. There are different guidelines, landmarks, and landing light configurations at runways, heliports, and vertiports for daytime and nighttime applications. Tailoring feature detection methods for AAM approach and landing during the day and night pose different issues and challenges. It is easier to detect edges, lines, and other runway markers during the day than at night. Conversely, it is easier to see landing light configurations and patterns at nighttime than daytime. Consequently, utilizing the same feature detector for daytime and nighttime operations may not be feasible. This paper focuses on a vision-based precision approach and landing (PAL) by comparing ORB SLAM 2, a Vision Simultaneous Localization and Mapping (VSLAM) algorithm, and a novel EKF that combines onboard IMU measurements with coplanar pose from orthography and scaling with iterations (COPOSIT). Conducting unmanned aerial system (UAS) flight tests at NASA Armstrong Flight Research Center (AFRC) with landmarks and fiducials distributed around the landing zone provides a simulated AAM approach and landing data to test vision-based PAL methods to provide Alternative Position, Navigation, and Timing (APNT) solutions for AAM PAL applications. The novel vision-based PAL EKF with IMU and COPOSIT provides accurate state estimation when distributed landmarks and fiducials are in the field of view.

distributed sensing↗
NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗
NASA NTRSDate not supplied

Virtual Fit Assessment: Validation using Historical Spacesuit Fit Data

Virtual fit tests using 3D body scans have provided a cost-effective means to predictively assess spacesuit fit for the current and future astronaut population. However, fit is a complex issue influenced by physical interferences, subjective preference, and many other factors. Fit can substantially differ between the type of hardware, environmental conditions, and tasks being performed. Namely, fit changes across different contexts, such as 3D printed mockup evaluations, pressurized one-g suited test events, neutral buoyancy and other training events, and flight extravehicular activities (EVA). These challenges make it difficult to validate virtual fit frameworks to physical suit sizing. This study proposes a new method of validation using the wealth of historically archived suit fit data. Physically Assessed Fit (PAF) data was assessed from astronauts and test volunteers who wore the legacy Extravehicular Mobility Unit (EMU). The data was collected during the past decades at NASA and considered to be most reliable and dependable. Each participant was 3D scanned for body shape and spacesuit-critical dimensions were measured per NASA guidelines. The participants’ size preference for hard upper torso (HUT) assembly was retrieved from their pressurized suit fit check records. Fit assessments were also updated after one-g EVA training, neutral buoyancy training, and EVA flights. Virtually Assessed Fit (VAF) was done by overlaying the CAD model of a HUT with the 3D body scans of the PAF participants. Each body scan was iteratively adjusted for the position inside the HUT to minimize the suit-to-body contact interference while satisfying a set of prescribed requirements. Then the residual contact area, depth, and volume were quantified as VAF metrics. This process was repeated for the different HUT sizes, including medium, large, and extra-large. Statistical modeling is currently in progress and will be presented at the conference. A statistical classifier will be developed to predict a fit probability for different HUT sizes as a function of the corresponding person’s VAF metrics. The HUT size with the highest fit probability will constitute the most likely size selection for the person, and the prediction will be compared against the corresponding PAF data. The participant data will be randomly pre-grouped into either a model development or validation subset. While the model development subset will be used to build the probability model, the validation subset will be used to assess the model accuracy. Also, the locations and magnitudes of suit-body-contacts will be estimated from VAF. This information can identify the critical suit geometry and body shape features that influence suit fit. The variations found in PAF size selections by subjects with similar VAF metrics will allow for investigations into subjective preferences, for example, tight versus loose fit. Overall, this study is expected to provide a structured validation of a virtual suit fit framework, which has not been possible in the past. The outcome can also provide useful insights and potential limitations for interpreting virtual fit tests for future spacesuit designs and population accommodation.

Han Kim↗
NASA NTRS2014

The Affording Mars Workshop: Background and Recommendations

A human mission to Mars is the stated "ultimate" goal for NASA and is widely believed by the public to be the most compelling destination for America's space program. However, widely cited enormous costs - perhaps as much as a trillion dollars for a many-decade campaign - seem to be an impossible hurdle, although political and budget instability over many years may be equally challenging. More recently, a handful of increasingly detailed architectures for initial Mars missions have been developed by commercial companies that have estimated costs much less than widely believed and roughly comparable with previous major human space flight programs: the Apollo Program, the International Space Station, and the space shuttle. Several of these studies are listed in the bibliography to the workshop report. As a consequence of these new scenarios, beginning in spring, 2013 a multiinstitutional planning team began developing the content and invitee list for a winter workshop that would critically assess concepts, initiatives, technology priorities, and programmatic options to reduce significantly the costs of human exploration of Mars. The output of the workshop - findings and recommendations - would be presented in a number of forums and discussed with national leaders in human space flight. It would also be made available to potential international partners. This workshop was planned from the start to be the first in a series. Subsequent meetings, conferences, and symposia will concentrate on topics not able to be covered in December. In addition, to make progress in short meeting, a handful of ground rules were adopted by the planning team and agreed to by the participants. Perhaps the two most notable such ground rules were (1) the Space Launch System (SLS) and Orion would be available during the time frame considered by the participants and (2) the International Space Station (ISS) would remain the early linchpin in preparing for Mars exploration over the coming decade. The workshop was organized around three topical breakout sessions: 1. The ISS and the path to Mars: The critical coming decade 2. Affordability and sustainability: what does it mean and what are its implications within guidelines established at the start of the workshop? 3. Notional sequence(s) of cost-achievable missions for the 2020s to 2030s, including capability objectives at each stage and opportunities for coordinated robotic partnerships.

background↗
NASA NTRS1994

(abstract) A Low-Cost Mission to 2060 Chiron Based on the Pluto Fast Flyby

The Pluto Fast Flyby-based mission to Chiron described in this paper is a low cost, scientifically rewarding, focused mission in the outer solar system. The proposed mission will make a flyby of 2060 Chiron, an active 'comet' with over 10(sup 4) times the mass of Halley, and an eccentric, Saturn-crossing orbit which ranges from 8.5 to 19 AU. This mission concept achieves the flyby 4.2 years after launch on a direct trajectory from Earth, is independent of Jupiter launch windows, and fits within Discovery cost guidelines. This mission offers the scientific opportunity to examine a class of object left unsampled by the trail-blazing Mariners, Pioneers, Voyagers, and missions to Halley. Spacecraft reconnaissance of Chiron addresses unique objectives relating to cometary science, other small bodies, the structure of quasi-bound atmospheres on modest-sized bodies, and the origin of primitive bodies and the giant planets. Owing to Chiron's large size (180<D<370 km), unique nature, and unusual orbit, this mission is likely to draw significant public interest. As described by COMPLEX, the SSEC, and later the SSES, flybys are the appropriate scale missions for initial reconnaissance missions. Carrying three sophisticated instruments, the proposed flyby will return critical data about Chiron's size, shape, polar obliquity, atmosphere, surface morphology, surface composition, internal structure, surface activity (including the nature of Chiron's outbursts), and origin. Engineering analysis indicates that the spacecraft is capable of navigating to and encountering Chiron at close approach distances of less than 5 000 km, well inside the 50 000 to 150 000 km coma, and perhaps within the collisional chemistry zone of the coma. The low cost of the proposed Chiron mission is based on the opportunity to use the planned Pluto Flyby spare spacecraft and a Proton Expendable Launch Vehicle (ELV) (the pluto spacecraft is being designed to be compatible with a Proton launch). Backup launch opportunities on Delta II and Atlas ELVs are available. The Pluto Fast Flyby mission plans to develop a low cost ($150M), lightweight (<150 kg) outer planet spacecraft which is well suited to flyby reconnaissance in the outer solar system. This Chiron flyby mission is designed to leverage SSED's Pluto spacecraft investment into a scientifically valuable successor mission within the Discovery cost cap. Taking advantage of the spare spacecraft, we estimate the Discovery Chiron intercept mission can be launched for less than $100 M. We believe this makes a highly attractive proposal, which maintains US presence and leadership in the study of the outer solar system, and enables the first-time exploration of a wholly new class of planetary target, an outer solar system planetesimal.

2060 Chiron planetesimal flyby Pluto Fast Flyby sp↗
NASA NTRS1999

Boom Softening and Nacelle Integration on an Arrow-Wing High-Speed Civil Transport Concept

During the last cycle of concept design and wind-tunnel testing, the goal of the low-boom- shaped HSCT concepts (the B-935, the LB-16, and the LB- 1 8) was to meet mission requirements and generate shaped, ground-level pressure signatures with nose shock strengths of 1.0 psf or less. The wind-tunnel tests of these concepts produced results that were partially successful and encouraging although not fully up to expectations. In spite of this, however, these conceptual designs were overly optimistic and not acceptable because: the wing planforms had excessive area; the wing structural aspect ratio was too high; one concept had aft-fuselage rather than under-the-wing engines; and the gross takeoff weights were unrealistically low because of engines that were early, high-tech versions of later, revised, more-realistic engines. The need for reducing the ground-level overpressure shock strengths still existed; a need to be met within more restrictive guidelines of mission performance and gross takeoff weight limitations. Therefore, it was decided that the next conceptual design cycle would focus on decreased nose shock strengths, "boom softening," in the signatures of the Boeing and the McDonnell Douglas baseline concepts rather than low-boom concepts with shaped-signature designs. Overly-optimistic results were not the only problem with these low-sonic-boom concepts. Papers given at the 1994 Sonic-Boom Workshop had demonstrated that the problem of successful nacelle integration on HSCT concepts had only been partially solved. Wind-tunnel pressure signature data, from the HSCT-11B (a.k.a. the LB-18) wind-tunnel model, showed that the Langley HSCT design and analysis method had been successful in reducing the nacelle-volume disturbances in the flow field. This was due.to the engine nacelles mounted behind the wing trailing-edge on the aft fuselage so that no nacelle-wing interference-lift flow-field disturbances were generated. While acceptable from a sonic-boom research point of view, this concept was unacceptable from several practical and structural considerations. Preliminary wind-tunnel pressure signature data from the LB-16 wind-tunnel model, which had the engine nacelles mounted under the wings (the usual location), indicated that the application of the Langley nacelle-integration method had been only partially successful in the reduction of the nacelle-volume with nacelle-wing interference-lift pressure disturbances. So, "boom softening" had to also address the task of successful integration of the engine nacelles, with the engines in the required under-the-wing location. Unless this problem was solved, low-sonic-boom and low-drag modifications to the wing planform, the airfoil shape, and the fuselage longitudinal area distribution could be nullified if the nacelle disturbances added increments to the nose-shock strengths that were removed through component tailoring. In this paper, an arrow-wing boom-softened HSC7 concept which incorporated modifications to a baseline McDonnell Douglas concept is discussed. The analysis of the concept's characteristics will include estimates of weight, center of gravity, takeoff field length, mission range, and predictions of its ground-level sonic-boom pressure signature. Additional modifications which enhanced the softened-boom performance of this concept are also described as well as estimates of the performance penalties induced by these modifications.

Mack, Robert J.↗
NASA NTRS2022

22” ADP Fan Rig Liners Design Report

A liner design study was conducted as part of a cooperative effort between five (5) government/industry teams that together seek to demonstrate the technology for designing and manufacturing acoustic liners that are twenty five percent (25%) more efficient than 1992 technology liners. The study emphasized teaming collaboration. The improved liners were designed by Pratt & Whitney and Boeing Airplane Company and built by Rohr Inc, and will be tested in the NASA/P& W 22-inch ADP fan rig at NASA Lewis Research Center's 9' x 15' wind tunnel. Design guidelines and decisions were made collectively during monthly design review telecons and at the formal final design review. The tools that were used to design the new improved liners were not new, but the process that was developed as part of this study that led into the evaluation and selection of the final and best liner designs is new. Until now, the liner design process as practiced by different industry teams varied greatly. Some procedures were based on empirical liner attenuation databases which could not adequately account for engine-to-engine hardwall fan noise spectral differences, while others were entirely theoretical. And regardless of which method one chose, the major difficulty was still the lack of understanding and knowledge of the actual hardwall fan source noise modal structure and farfield SPL spectra. The NASA-led effort to attempt actual measurements of the fan source noise modal structure by means of the rotating microphone array is expected to contribute significantly to the understanding of the nature of the fan tone noise modes, but the application to broadband noise is still a long way off. The new design process included consideration of the measured fan tone modes, but for the majority of the spectra a separate, systematic process was used. It is a common practice in the engine/nacelle industry that acoustic liners for new products are designed before actual measured hardwall engine far-field noise spectra are available. Target noise spectra are normally derived from existing engine noise databases with some adjustments to absolute SPLs and frequencies. This practice has been acceptable as long as the new engine was a derivative of the base engine. However, in the case of the ADP, the transition from a current engine base is too - great, and the adjustments could not adequately account for the quantum changes in SPL spectral differences. Examples were the 1992 single degree of freedom (SDOF) inlet and aft liners (designed by P&W) that would be used as the baseline liners against which the new improved liners' efficien¬cies would -be measured. As will be shown, these baseline liners have been found to be deeper than the desire optimum depths. The new liner design process begins with the selection of the target hard wall fan noise spectra. These spectra were obtained by scaling up (5.91 scale factor) the measured hardwall fan spectral data from the 22” ADP fan rig. Next, the modal energy contents for each 1/3-octave band center frequency of these hardwall fan noise spectra are estimated. (Within each 1/3-octave band center frequency, the model energy distribution approximation is for both tone and broadband noise). For the inlet noise, P&W uses a derivative of the NASA Lewis (Ed Rice's) method of classifying; and grouping propagating modes by their cutoff ratios. The next step is to assign energy level to each group of modes having the same cutoff ratio. In Ed Rice's model, the modes were grouped according to ten (10) cutoff ratio intervals with center values located at 1.026, 1.085, 1.155, 1.24, 1.35, 1.49, 1.69, 2.0, and 4.47 (with equal number of modes in each interval). The modes were assumed to have equal energy. P&W’s model expands the cutoff ratio-mode grouping into two hundred (200) smaller cutoff ratio intervals with center values located f1".'m 1.003 to 11.5 in 199 increasing incremental intervals. Next, P&W's model uses a "2-parameter" normal distribution as a template to assign energy levels to these 200 pre-determined cutoff ratio values (for each 1/3-octave band center frequency). In the past, P&W had conducted an extensive study to determine what "2-parameter" values are appropriate for fullscale inlet liners, and had developed a set of twenty-four (24) "2-pararneter" values (i.e. one for each 1/3-octave frequency band) that when used in Ed Rice's Inlet Attenuation Prediction Method produced predicted liner attenuations that closely matched measured liner attenuations from several P&W's engines. In the absence of actual measured tone and broadband modal data from the 22" ADP rig, the process will use P&W's proprietary set of "2-parameter" values for this liner design study. For the aft noise, Boeing uses a modal energy approximation that the "transport energy" of each propagating mode is equal. This approximation is almost the same as the equal energy per mode approximation, except for modes that are near cutoff. Boeing's model forces these modes to have lower energy levels. Both P&W and Boeing agreed that the "transport energy" approximation should work well for the ADP aft fan noise which appears to be dominated by broadband noise. The design process then proceeds to calculate the optimum liner impedances for each frequency in both the inlet and the aft. These optimum impedances represent the target impedances that the designed liners should have. Liners with impedances matching the optimum impedances at all frequencies are "ideal" liners. These ideal liners are theoretically the best liners. Unfortunately, it has been showed that it is impossible to design and build such ideal liners. The next best liners are ones that have impedances matching the optimum impedances over some frequency range (not all frequencies as for the ideal). This is accomplished by the use of "frequency weightings". Several of P&W's and Boeing's existing computer decks were used for optimizing and matching the designed liner impedances to the target optimum values (with the various frequency weightings specified). The optimization produces liner candidates with predicted liner impedances and descriptions of their physical liner characteristics. These candidate liner impedances are then used to predict their spectral attenuation characteristics which are then used together with the target hardwall fan noise spectra to determine the resulting treated noise spectra and PNLT values. Further optimization around the selected candidate designs yield final designs that are best in PNLT attenuations. Use of the optimization decks allowed a large number of liner candidates to be screened in a relatively short period of time. This design process is systematic and is efficient. The new inlet SDOF liner design obtained from the improved process was predicted to be 34% more effective (per unit area) than the 1992 baseline inlet liner. This inlet liner design is a 112 rayl wovenwiremesh facesheet over a 0.312-inch deep honeycomb core. The new aft SDOF liner design was predicted to be 52% more efficient than the aft baseline liner. The new aft SDOF liner is "segmented" with a shallower liner on the core cowl (inner duct wall) and a deeper liner on the fan cowl (outer duct wall). The shallower liner is a 70.6 rayl woven-wiremesh facesheet over a 0.141-inch deep honeycomb core. The deeper liner is a 68 rayl woven-wiremesh facesheet over a 0.309-inch deep honeycomb core. All liner dimensions are for the 22-inch model-scale ADP fan rig liners. The selected advanced liners are "segmented" double-layer (DDOF) liners for the inlet and aft locations. Also, for the inlet, a bulk liner with ceramic foam for wider broadband noise absorption was also selected. Triple-layer liner designs were not considered since the model scaled liners ( 1/5. 91) were dimensionally too small to be built correctly, and irrin earlier concept study, Boeing found a triple-layer to have only very small benefits over a double-layer. The inlet DDOF liner was predicted to be 83% more effective than the baseline. The inlet DDOF design is a 78 rayl facesheet over a 0.080 top cavity depth, a 68 rayl septum and a 0.227-inch bottom cavity depth. The inlet bulk liner is a 60 rayl facesheet over a 0.33-inch deep honeycomb filled with high temperature (HTP) ceramic foam with a density of 4.8 lb/cu.ft and a flow resistivity of 167 rayl/cm. The inlet bulk liner was predicted to be 83% more effective than the baseline liner. The aft DDOF liners are segmented with a shallower liner on the core cowl and a deeper liner on the fan cowl. The shallow DDOF liner is a 49.8 rayl facesheet over a 0.093-inch top cavity depth, a septum of 88.2 rayls over a 0.181-inch bottom cavity depth. The deep DDOF liner is a 12.9 rayl facesheet over a 0.140-inch top cavity depth, a septum of 53.1 ray ls over a 0.258-inch botom cavity depth. The segmented aft DDOF liners were predicted to be 86% more efficient than the baseline liner.

turbofan acoustic treatment↗
NASA NTRS2016

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗