Search NASA⌕ Search

SEARCH · Search NASA

Results for “data legacy”

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 163 records · Page 9

Impact of Future Low-Emissions Combustor Technology on Acoustic Scaling Laws

A first-of-its-kind examination of broadband noise associated with a far-term advanced low-emission aero-combustor concept is presented. Due to design trends and expected cycle changes for future aircraft propulsion systems, noise generated by sources in the combustor are expected to become of increasing significance for airport-community noise. The paper assesses the impact on legacy semi-empirical noise-prediction methods from the expected radical departures from current combustor operating conditions and designs, such as fuel-air distribution and flame anchoring techniques. Such methods are essential in system-level noise assessments at the preliminary design stage for advanced air transports to assure that overall environmental goals are met. Detailed unsteady pressure measurements, obtained in a fundamental combustion noise experiment utilizing a combustor rig at relevant pressures and temperatures, are analyzed. In addition to an advanced far-term low-emissions concept, a reference configuration with the test section arranged to model a modern combustor sector was also studied. For the test rig in the current-generation configuration, the measured broadband acoustic data are reasonably well described by the acoustic-power scaling laws used in legacy semi-empirical noise-prediction methods. For the future-advanced configuration, the legacy scaling laws, with some notable exceptions, provide correct trends, but with much less accuracy

aeroacoustics↗

Controlling Infrastructure Costs: Right-Sizing the Mission Control Facility

Johnson Space Center's Mission Control Center is a space vehicle, space program agnostic facility. The current operational design is essentially identical to the original facility architecture that was developed and deployed in the mid-90's. In an effort to streamline the support costs of the mission critical facility, the Mission Operations Division (MOD) of Johnson Space Center (JSC) has sponsored an exploratory project to evaluate and inject current state-of-the-practice Information Technology (IT) tools, processes and technology into legacy operations. The general push in the IT industry has been trending towards a data-centric computer infrastructure for the past several years. Organizations facing challenges with facility operations costs are turning to creative solutions combining hardware consolidation, virtualization and remote access to meet and exceed performance, security, and availability requirements. The Operations Technology Facility (OTF) organization at the Johnson Space Center has been chartered to build and evaluate a parallel Mission Control infrastructure, replacing the existing, thick-client distributed computing model and network architecture with a data center model utilizing virtualization to provide the MCC Infrastructure as a Service. The OTF will design a replacement architecture for the Mission Control Facility, leveraging hardware consolidation through the use of blade servers, increasing utilization rates for compute platforms through virtualization while expanding connectivity options through the deployment of secure remote access. The architecture demonstrates the maturity of the technologies generally available in industry today and the ability to successfully abstract the tightly coupled relationship between thick-client software and legacy hardware into a hardware agnostic "Infrastructure as a Service" capability that can scale to meet future requirements of new space programs and spacecraft. This paper discusses the benefits and difficulties that a migration to cloud-based computing philosophies has uncovered when compared to the legacy Mission Control Center architecture. The team consists of system and software engineers with extensive experience with the MCC infrastructure and software currently used to support the International Space Station (ISS) and Space Shuttle program (SSP).

Martin, Keith↗

Product Engineering Class in the Software Safety Risk Taxonomy for Building Safety-Critical Systems

When software safety requirements are imposed on legacy safety-critical systems, retrospective safety cases need to be formulated as part of recertifying the systems for further use and risks must be documented and managed to give confidence for reusing the systems. The SEJ Software Development Risk Taxonomy [4] focuses on general software development issues. It does not, however, cover all the safety risks. The Software Safety Risk Taxonomy [8] was developed which provides a construct for eliciting and categorizing software safety risks in a straightforward manner. In this paper, we present extended work on the taxonomy for safety that incorporates the additional issues inherent in the development and maintenance of safety-critical systems with software. An instrument called a Software Safety Risk Taxonomy Based Questionnaire (TBQ) is generated containing questions addressing each safety attribute in the Software Safety Risk Taxonomy. Software safety risks are surfaced using the new TBQ and then analyzed. In this paper we give the definitions for the specialized Product Engineering Class within the Software Safety Risk Taxonomy. At the end of the paper, we present the tool known as the 'Legacy Systems Risk Database Tool' that is used to collect and analyze the data required to show traceability to a particular safety standard

Hill, Janice↗

An Analysis of Peak Wind Speed Data from Collocated Mechanical and Ultrasonic Anemometers

This study compared peak wind speeds reported by mechanical and ultrasonic anemometers at Cape Canaveral Air Force Station and Kennedy Space Center (CCAFS/KSC) on the east central coast of Florida and Vandenberg Air Force Base (VAFB) on the central coast of California. Launch Weather Officers, forecasters, and Range Safety analysts need to understand the performance of wind sensors at CCAFS/KSC and VAFB for weather warnings, watches, advisories, special ground processing operations, launch pad exposure forecasts, user Launch Commit Criteria (LCC) forecasts and evaluations, and toxic dispersion support. The legacy CCAFS/KSC and VAFB weather tower wind instruments are being changed from propeller-and-vane (CCAFS/KSC) and cup-and-vane (VAFB) sensors to ultrasonic sensors under the Range Standardization and Automation (RSA) program. Mechanical and ultrasonic wind measuring techniques are known to cause differences in the statistics of peak wind speed as shown in previous studies. The 45th Weather Squadron (45 WS) and the 30th Weather Squadron (30 WS) requested the Applied Meteorology Unit (AMU) to compare data between the RSA ultrasonic and legacy mechanical sensors to determine if there are significant differences. Note that the instruments were sited outdoors under naturally varying conditions and that this comparison was not designed to verify either technology. Approximately 3 weeks of mechanical and ultrasonic wind data from each range from May and June 2005 were used in this study. The CCAFS/KSC data spanned the full diurnal cycle, while the VAFB data were confined to 1000-1600 local time. The sample of 1-minute data from numerous levels on five different towers on each range totaled more than 500,000 minutes of data (482,979 minutes of data after quality control). The ten towers were instrumented at several levels, ranging from 12 ft to 492 ft above ground level. The ultrasonic sensors were collocated at the same vertical levels as the mechanical sensors and typically within 15 ft horizontally of each another. Data from a total of 53 RSA ultrasonic sensors, collocated with mechanical sensors were compared. The 1- minute average wind speed/direction and the 1-second peak wind speed/direction were compared.

Short, David A.↗

What are the Progenitors of Compace, Massive, Quiescent Galaxies at z (equals) 2.3? The Population of Massive Galaxies at z (greater than) 3 From NMBS AND CANDELS

Using public data from the NEWFIRM Medium-Band Survey (NMBS) and the Cosmic Assembly Near-Infrared Deep Extragalactic Legacy Survey (CANDELS), we investigate the population of massive galaxies at z > 3. The main aim of this work is to identify the potential progenitors of z ∼ 2 compact, massive, quiescent galaxies (CMQGs), furthering our understanding of the onset and evolution of massive galaxies. Our work is enabled by high-resolution images from CANDELS data and accurate photometric redshifts, stellar masses, and star formation rates (SFRs) from 37-band NMBS photometry. The total number of massive galaxies at z > 3 is consistent with the number of massive, quiescent galaxies (MQGs) at z ∼ 2, implying that the SFRs for all of these galaxies must be much lower by z ∼ 2. We discover four CMQGs at z > 3, pushing back the time for which such galaxies have been observed. However, the volume density for these galaxies is significantly less than that of galaxies at z < 2 with similar masses, SFRs, and sizes, implying that additional CMQGs must be created in the intervening ∼1 Gyr between z = 3 and z = 2. We find five star-forming galaxies at z ∼ 3 that are compact (Re < 1.4 kpc) and have stellar mass M∗ > 1010.6M; these galaxies are likely to become members of the massive, quiescent, compact galaxy population at z ∼ 2. We evolve the stellar masses and SFRs of each individual z > 3 galaxy adopting five different star formation histories (SFHs) and studying the resulting population of massive galaxies at z = 2.3. We find that declining or truncated SFHs are necessary to match the observed number density of MQGs at z ∼ 2, whereas a constant delayed-exponential SFH would result in a number density significantly smaller than observed. All of our assumed SFHs imply number densities of CMQGs at z ∼ 2 that are consistent with the observed number density. Better agreement with the observed number density of CMQGs at z ∼ 2 is obtained if merging is included in the analysis and better still if star formation quenching is assumed to shortly follow the merging event, as implied by recent models of the formation of MQGs.

Massive↗

DSN Beowulf Cluster-Based VLBI Correlator

The NASA Deep Space Network (DSN) requires a broadband VLBI (very long baseline interferometry) correlator to process data routinely taken as part of the VLBI source Catalogue Maintenance and Enhancement task (CAT M&E) and the Time and Earth Motion Precision Observations task (TEMPO). The data provided by these measurements are a crucial ingredient in the formation of precision deep-space navigation models. In addition, a VLBI correlator is needed to provide support for other VLBI related activities for both internal and external customers. The JPL VLBI Correlator (JVC) was designed, developed, and delivered to the DSN as a successor to the legacy Block II Correlator. The JVC is a full-capability VLBI correlator that uses software processes running on multiple computers to cross-correlate two-antenna broadband noise data. Components of this new system (see Figure 1) consist of Linux PCs integrated into a Beowulf Cluster, an existing Mark5 data storage system, a RAID array, an existing software correlator package (SoftC) originally developed for Delta DOR Navigation processing, and various custom- developed software processes and scripts. Parallel processing on the JVC is achieved by assigning slave nodes of the Beowulf cluster to process separate scans in parallel until all scans have been processed. Due to the single stream sequential playback of the Mark5 data, some ramp-up time is required before all nodes can have access to required scan data. Core functions of each processing step are accomplished using optimized C programs. The coordination and execution of these programs across the cluster is accomplished using Pearl scripts, PostgreSQL commands, and a handful of miscellaneous system utilities. Mark5 data modules are loaded on Mark5 Data systems playback units, one per station. Data processing is started when the operator scans the Mark5 systems and runs a script that reads various configuration files and then creates an experiment-dependent status database used to delegate parallel tasks between nodes and storage areas (see Figure 2). This script forks into three processes: extract, translate, and correlate. Each of these processes iterates on available scan data and updates the status database as the work for each scan is completed. The extract process coordinates and monitors the transfer of data from each of the Mark5s to the Beowulf RAID storage systems. The translate process monitors and executes the data conversion processes on available scan files, and writes the translated files to the slave nodes. The correlate process monitors the execution of SoftC correlation processes on the slave nodes for scans that have completed translation. A comparison of the JVC and the legacy Block II correlator outputs reveals they are well within a formal error, and that the data are comparable with respect to their use in flight navigation. The processing speed of the JVC is improved over the Block II correlator by a factor of 4, largely due to the elimination of the reel-to-reel tape drives used in the Block II correlator.

Rogstad, Stephen P.↗

Implementing Legacy-C Algorithms in FPGA Co-Processors for Performance Accelerated Smart Payloads

Accurate, on-board classification of instrument data is used to increase science return by autonomously identifying regions of interest for priority transmission or generating summary products to conserve transmission bandwidth. Due to on-board processing constraints, such classification has been limited to using the simplest functions on a small subset of the full instrument data. FPGA co-processor designs for SVM1 classifiers will lead to significant improvement in on-board classification capability and accuracy.

co-processor↗

Computer-Aided Parallelizer and Optimizer

The Computer-Aided Parallelizer and Optimizer (CAPO) automates the insertion of compiler directives (see figure) to facilitate parallel processing on Shared Memory Parallel (SMP) machines. While CAPO currently is integrated seamlessly into CAPTools (developed at the University of Greenwich, now marketed as ParaWise), CAPO was independently developed at Ames Research Center as one of the components for the Legacy Code Modernization (LCM) project. The current version takes serial FORTRAN programs, performs interprocedural data dependence analysis, and generates OpenMP directives. Due to the widely supported OpenMP standard, the generated OpenMP codes have the potential to run on a wide range of SMP machines. CAPO relies on accurate interprocedural data dependence information currently provided by CAPTools. Compiler directives are generated through identification of parallel loops in the outermost level, construction of parallel regions around parallel loops and optimization of parallel regions, and insertion of directives with automatic identification of private, reduction, induction, and shared variables. Attempts also have been made to identify potential pipeline parallelism (implemented with point-to-point synchronization). Although directives are generated automatically, user interaction with the tool is still important for producing good parallel codes. A comprehensive graphical user interface is included for users to interact with the parallelization process.

Jin, Haoqiang↗

Modifying the Heliophysics Data Policy to Better Enable Heliophysics Research

The Heliophysics (HP) Science Data Management Policy, adopted by HP in June 2007, has helped to provide a structure for the HP data lifecycle. It provides guidelines for Project Data Management Plans and related documents, initiates Resident Archives to maintain data services after a mission ends, and outlines a route to the unification of data finding, access, and distribution through Virtual observatories. Recently we have filled in missing pieces that assure more coherence and a home for the VxOs (through the 'Heliophsyics Data and Model Consortium'), and provide greater clarity with respect to long term archiving. In particular, the new policy which has been vetted with many community members, details the 'Final Archives' that are to provide long-term data access. These are distinguished from RAs in that they provide little additional service beyond servicing data, but critical to their success is that the final archival materials include calibrated data in useful formats such as one finds in CDAWeb and various ASCII or FITS archives. Having a clear goal for legacy products, to be detailed as part of the Mission Archives Plans presented at Senior Reviews, will help to avoid the situation so common in the past of having archival products that preserve bits well but not readily usable information. We hope to avoid the need for the large numbers of 'data upgrade' projects that have been necessary in recent years.

Hayes, Jeffrey↗

Biological Insights at the Interface of Multiple Arabidopsis Legacy Datasets

The NASA GeneLab database includes an open-access collection of datasets yielded by space biology experiments. Six Gene Lab Data Sets (GLDS’s) performed in Arabidopsis were selected for analysis (7/17/44/121/205/213), all of which included transcriptome data from spaceflight and ground control environments. Hardware, ecotype, environmental conditions, and other experimental conditions varied, allowing the observations of overarching gene expression impacts of microgravity on plant life without focusing on effects of specific experimental conditions. Using GeneLab pre-processed datasets as the basis for the study, RNA microarray data were analyzed to identify genes that showed altered expression in microgravity when compared to control samples for each individual GLDS. All differentially expressed genes were compared to locate differentially expressed genes common between spaceflight experiments. The most noteworthy result is that not one gene shared differential expression among the six GLDS’s. However, gene expression was not influenced randomly by the microgravity environment, as there were several gene ontology terms that were significantly enriched across all experiments. These included 20 significantly enriched biological processes, and although the genes which enriched each term varied, there were many cases of specific genes common to clusters of multiple GLDS’s. Gene expression such as NAC92 and ERF011 or membrane structural element FFP6 provide insight and direction toward understanding the plant response to spaceflight. Characterizing these common processes and the shared differentially expressed genes has demonstrated potential targets for further study to understand and modulate the biological response of plants in microgravity. Life on Earth has never been subjected to the absence of gravity as a selective pressure, so observing how life forms react to a microgravity environment could provide insight to our shared fundamental biological processes. It is also feasible that the genetic modification of specific genes linked to the microgravity response could improve health and yield of space crops.

Joseph Emhof↗

LISA Framework for Enhancing Gravitational Wave Signal Extraction Techniques

This paper describes the development of a Framework for benchmarking and comparing signal-extraction and noise-interference-removal methods that are applicable to interferometric Gravitational Wave detector systems. The primary use is towards comparing signal and noise extraction techniques at LISA frequencies from multiple (possibly confused) ,gravitational wave sources. The Framework includes extensive hybrid learning/classification algorithms, as well as post-processing regularization methods, and is based on a unique plug-and-play (component) architecture. Published methods for signal extraction and interference removal at LISA Frequencies are being encoded, as well as multiple source noise models, so that the stiffness of GW Sensitivity Space can be explored under each combination of methods. Furthermore, synthetic datasets and source models can be created and imported into the Framework, and specific degraded numerical experiments can be run to test the flexibility of the analysis methods. The Framework also supports use of full current LISA Testbeds, Synthetic data systems, and Simulators already in existence through plug-ins and wrappers, thus preserving those legacy codes and systems in tact. Because of the component-based architecture, all selected procedures can be registered or de-registered at run-time, and are completely reusable, reconfigurable, and modular.

Thompson, David E.↗

Dare Mighty Things

Winston Churchill once said, “To improve is to change; to be perfect is to change often.” JPL’s Property Accountability objective is to provide superior services related to property accountability, reutilization, and disposition. JPL must report property reutilized and disposed through either sales, donation, or scrap. Implementing the JPL designed and built Property Information Reporting System (PIRS), opened a new perspective with our data and what are we reporting to NASA. With this new depth of visibility, we self-implemented as assessment to validate the fiduciary and stewardship responsibilities of what is being reporting to NASA. JPL strives to perform at a level beyond the basic primary expectations of our NASA requirements. JPL developed the PIRS - which rolled out in 2018 - to simplify the delivery of JPL’s Personal Property and Equipment (PP&E) reporting: PIRS takes the raw data from Oracle to generate the NASA Form (NF) 1018 and Contractor Held Asset Reporting System (CHATS) Reports, and to meet the requirements established for AS9100 compliance. The data presented from PIRS is exportable and used to analyze our property records. JPL is also embarking on an effort to define the JPL of the future with “Enterprise 2.0”. Enterprise 2.0 is the driving force of JPL’s strategy to digitally transform the Laboratory from the current legacy processes and systems to a modern, integrated, information-driven highway of business transactions. This should include automation of routine processes and data-related tasks, integration of data and systems, advanced search and analytics, and improved information sharing and collaboration. As JPL’s evolving landscape of digital technologies advance to meet the future, JPL Property Accountability is making strides to surpass these expectations. For every cause there is an effect: a revealing of something that aids in the further development and transformation of JPL best business practices.

Sucher, Jay M↗

Performance Analysis of TCP Enhancements in Satellite Data Networks

This research examines two proposed enhancements to the well-known Transport Control Protocol (TCP) in the presence of noisy communication links. The Multiple Pipes protocol is an application-level adaptation of the standard TCP protocol, where several TCP links cooperate to transfer data. The Space Communication Protocol Standard - Transport Protocol (SCPS-TP) modifies TCP to optimize performance in a satellite environment. While SCPS-TP has inherent advantages that allow it to deliver data more rapidly than Multiple Pipes, the protocol, when optimized for operation in a high-error environment, is not compatible with legacy TCP systems, and requires changes to the TCP specification. This investigation determines the level of improvement offered by SCPS-TP's Corruption Mode, which will help determine if migration to the protocol is appropriate in different environments. As the percentage of corrupted packets approaches 5 %, Multiple Pipes can take over five times longer than SCPS-TP to deliver data. At high error rates, SCPS-TP's advantage is primarily caused by Multiple Pipes' use of congestion control algorithms. The lack of congestion control, however, limits the systems in which SCPS-TP can be effectively used.

Broyles, Ren H.↗

The InSAR Scientific Computing Environment

We have developed a flexible and extensible Interferometric SAR (InSAR) Scientific Computing Environment (ISCE) for geodetic image processing. ISCE was designed from the ground up as a geophysics community tool for generating stacks of interferograms that lend themselves to various forms of time-series analysis, with attention paid to accuracy, extensibility, and modularity. The framework is python-based, with code elements rigorously componentized by separating input/output operations from the processing engines. This allows greater flexibility and extensibility in the data models, and creates algorithmic code that is less susceptible to unnecessary modification when new data types and sensors are available. In addition, the components support provenance and checkpointing to facilitate reprocessing and algorithm exploration. The algorithms, based on legacy processing codes, have been adapted to assume a common reference track approach for all images acquired from nearby orbits, simplifying and systematizing the geometry for time-series analysis. The framework is designed to easily allow user contributions, and is distributed for free use by researchers. ISCE can process data from the ALOS, ERS, EnviSAT, Cosmo-SkyMed, RadarSAT-1, RadarSAT-2, and TerraSAR-X platforms, starting from Level-0 or Level 1 as provided from the data source, and going as far as Level 3 geocoded deformation products. With its flexible design, it can be extended with raw/meta data parsers to enable it to work with radar data from other platforms

geodetic imaging↗

Imaging for Hypersonic Experimental Aeroheating Testing (IHEAT) Version 4.0: User Manual

The IHEAT v4.0 software is a data reduction code for global thermography data acquired in the NASA Langley Aerothermodynamics Laboratory (LAL) hypersonic wind tunnels. IHEAT uses red and green color-intensity data from two-dimensional images of wind tunnel models to compute temperatures and heat-transfer rates using a semi-infinite, one-dimensional heat transfer approximation at each image pixel. Multiple automated tools in IHEAT v4.0 decrease the time required to reduce the data from a phosphor thermography wind tunnel run. Data at one or all of the image pixel locations can be exported to computer files for further analysis. The prior version of IHEAT, v3.2, was written in PV-WAVE® (now owned by Rogue Wave® Software) in 1994 and was limited in functionality to fit within the memory constraints of the available computers at the time. IHEAT v4.0 is written in MATLAB® by MathWorks® and contains several new features that leverage the increase in available memory of the current computers. A Piecewise tool permits the user to extract data along a segmented line cut that can follow interesting features in the image better than the single, straight line cuts that were possible with the legacy Length and Profile tools. The new Load Run and Batch tools facilitate batch processing by loading in all of the input files and images for a run at the same time. Load Run permits the user to process the available run images manually, while Batch automatically saves heat transfer data from all of the images based on the analysis previously performed on a single frame. IHEAT v4.0 also can automatically calculate the temporal collapse of reference line cuts from the time history heating data for a run to indicate the appropriate frame to reduce for each run. The IHEAT v4.0 source code was compiled into a standalone executable file that can be accessed remotely from several computers with different operating systems, simultaneously. The software is run through the MATLAB® Compiler Runtime engine, and therefore, IHEAT does not require a software license to run. Any software commands executed in the IHEAT v4.0 code will not affect other similar applications running on the same machine. Similarly, changes to the parent software do not affect a compiled code. These features of IHEAT v4.0 are improvements over the legacy v3.2 code, which required regular maintenance to avoid losing functionality as the PVWAVE ® programming language was upgraded.

Mason, Michelle L.↗

Smartfiles: An OO approach to data file interoperability

Data files for scientific and engineering codes typically consist of a series of raw data values whose descriptions are buried in the programs that interact with these files. In this situation, making even minor changes in the file structure or sharing files between programs (interoperability) can only be done after careful examination of the data file and the I/O statement of the programs interacting with this file. In short, scientific data files lack self-description, and other self-describing data techniques are not always appropriate or useful for scientific data files. By applying an object-oriented methodology to data files, we can add the intelligence required to improve data interoperability and provide an elegant mechanism for supporting complex, evolving, or multidisciplinary applications, while still supporting legacy codes. As a result, scientists and engineers should be able to share datasets with far greater ease, simplifying multidisciplinary applications and greatly facilitating remote collaboration between scientists.

Haines, Matthew↗

An Upgrade of the Imaging for Hypersonic Experimental Aeroheating Testing (IHEAT) Software

The Imaging for Hypersonic Experimental Aeroheating Testing (IHEAT) code is used at NASA Langley Research Center to analyze global aeroheating data on wind tunnel models tested in the Langley Aerothermodynamics Laboratory. One-dimensional, semi-infinite heating data derived from IHEAT are used to design thermal protection systems to mitigate the risks due to the aeroheating loads on hypersonic vehicles, such as re-entry vehicles during descent and landing procedures. This code was originally written in the PV-WAVE programming language to analyze phosphor thermography data from the two-color, relativeintensity system developed at Langley. To increase the efficiency, functionality, and reliability of IHEAT, the code was migrated to MATLAB syntax and compiled as a stand-alone executable file labeled version 4.0. New features of IHEAT 4.0 include the options to batch process all of the data from a wind tunnel run, to map the two-dimensional heating distribution to a three-dimensional computer-aided design model of the vehicle to be viewed in Tecplot, and to extract data from a segmented line that follows an interesting feature in the data. Results from IHEAT 4.0 were compared on a pixel level to the output images from the legacy code to validate the program. The differences between the two codes were on the order of 10-5 to 10-7. IHEAT 4.0 replaces the PV-WAVE version as the production code for aeroheating experiments conducted in the hypersonic facilities at NASA Langley.

Mason, Michelle L.↗

Yuma 2022 Rotorcraft Acoustic Flight Test

A cooperative flight test campaign between U.S. Navy, Army, Marine Corps, and NASA was performed at Marine Corps Air Station (MCAS) Yuma from 19 January to 15 February 2022. The primary purpose of testing military vehicles was to characterize the acoustic signature of the MV-22 rotorcraft and Stalker unmanned aerial system for typical mission gross weight, configuration, and for a range of typical mission operating conditions. Additionally, a civilian MD530 vehicle was tested to characterize the acoustic emissions for both legacy blades and S411 main rotor blades. This report provides an overview of the test, documents the data acquired, and describes the formats of the stored data.

Acoustics↗