SEARCH · Search NASA

Results for “Engine Ground Testing”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 1,549 records · Page 86

All sources NASA NTRS DOE OSTI

NASA NTRS2014

Lessons Learned in the First Year Operating Software Defined Radios in Space

Operating three unique software defined radios (SDRs) in a space environment aboard the Space Communications and Navigation (SCaN) Testbed for over one year has provided an opportunity to gather knowledge useful for future missions considering using software defined radios. This paper provides recommendations for the development and use of SDRs, and it considers the details of each SDRs approach to software upgrades and operation. After one year, the SCaN Testbed SDRs have operated for over 1000 hours. During this time, the waveforms launched with the SDR were tested on-orbit to assure that they operated in space at the same performance level as on the ground prior to launch to obtain an initial on-orbit performance baseline. A new waveform for each SDR has been developed, implemented, uploaded to the flight system, and tested in the flight environment. Recommendations for SDR-based missions have been gathered from early development through operations. These recommendations will aid future missions to reduce the cost, schedule, and risk of operating SDRs in a space environment. This paper considers the lessons learned as they apply to SDR pre-launch checkout, purchasing space-rated hardware, flexibility in command and telemetry methods, on-orbit diagnostics, use of engineering models to aid future development, and third-party software. Each SDR implements the SCaN Testbed flight computer command and telemetry interface uniquely, allowing comparisons to be drawn. The paper discusses the lessons learned from these three unique implementations, with suggestions on the preferred approach. Also, results are presented showing that it is important to have full system performance knowledge prior to launch to establish better performance baselines in space, requiring additional test applications to be developed pre-launch. Finally, the paper presents the issues encountered with the operation and implementation of new waveforms on each SDR and proposes recommendations to avoid these issues.

radio equipment↗

NASA NTRS2014

Lessons Learned in the First Year Operating Software Defined Radios in Space

Operating three unique software defined radios (SDRs) in a space environment aboard the Space Communications and Navigation (SCaN) Testbed for over one year has provided an opportunity to gather knowledge useful for future missions considering using software defined radios. This paper provides recommendations for the development and use of SDRs, and it considers the details of each SDR's approach to software upgrades and operation. After one year, the SCaN Testbed SDRs have operated for over 1000 hours. During this time, the waveforms launched with the SDR were tested on-orbit to assure that they operated in space at the same performance level as on the ground prior to launch to obtain an initial on-orbit performance baseline. A new waveform for each SDR has been developed, implemented, uploaded to the flight system, and tested in the flight environment. Recommendations for SDR-based missions have been gathered from early development through operations. These recommendations will aid future missions to reduce the cost, schedule, and risk of operating SDRs in a space environment. This paper considers the lessons learned as they apply to SDR pre-launch checkout, purchasing space-rated hardware, flexibility in command and telemetry methods, on-orbit diagnostics, use of engineering models to aid future development, and third-party software. Each SDR implements the SCaN Testbed flight computer command and telemetry interface uniquely, allowing comparisons to be drawn. The paper discusses the lessons learned from these three unique implementations, with suggestions on the preferred approach. Also, results are presented showing that it is important to have full system performance knowledge prior to launch to establish better performance baselines in space, requiring additional test applications to be developed pre-launch. Finally, the paper presents the issues encountered with the operation and implementation of new waveforms on each SDR and proposes recommendations to avoid these issues.

space communication↗

NASA NTRS2021

An Innovative Approach to Modeling VIPER Rover Software Life Cycle Cost

NASA’s “Volatiles Investigating Polar Exploration Rover” (VIPER) will be the first robotic mission to prospect for water ice near the south pole of the Moon in late 2023 on a 100-Earth-day mission. The information that the VIPER rover provides will help improve understanding of the composition, distribution, and accessibility of Lunar polar volatiles and will help determine how the Moon’s resources can support future human space exploration. VIPER, however, represents a radical departure from the way that NASA has traditionally developed planetary robotic missions. A key consequence of these differences is that estimating the cost of VIPER’s rover software is challenging and complex.For example, VIPER is being developed using management procedures typically applied to NASA research and technology projects, rather than space flight programs. In addition, key portions of the rover’s software are being designed as ground software to run on mission control computers (rather than on-board the rover as flight software as with prior planetary missions) taking advantage of continuous, interactive data communications between the Moon and Earth and higher performance computing available on the ground. Moreover, the rover’s software is being engineered using Agile software development practices and incorporates a significant amount of open-source, rather than following traditional (spiral, waterfall, etc.) development methods and in-house code. In this paper, we present an innovative process to estimate the life cycle cost of VIPER’s rover software. We first describe how we modeled the architecture and code counts for three software elements: Rover Flight Software (RFSW), Rover Ground Software (RGSW), and Rover Simulation Software (RSIM). We then discuss key challenges and unique aspects of our approach, such as the lack of Lunar rover analogies, the need to integrate and test large open source software, and the strategies developed to account for use of non-space flight management practices and the impact of the COVID-19 pandemic. We conclude with a summary of our results, including cumulative distribution, nearest neighbors and cluster analysis, as well as heuristics used to confirm the reasonableness of the cost estimate.

Utz, Hans↗

NASA NTRS2015

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The development of the Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large complex systems engineering challenge being addressed in part by focusing on the specific subsystems handling of off-nominal mission and fault tolerance. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML), the Mission and Fault Management (M&FM) algorithms are crafted and vetted in specialized Integrated Development Teams composed of multiple development disciplines. NASA also has formed an M&FM team for addressing fault management early in the development lifecycle. This team has developed a dedicated Vehicle Management End-to-End Testbed (VMET) that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. The flexibility of VMET enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the algorithms utilizing actual subsystem models. The intent is to validate the algorithms and substantiate them with performance baselines for each of the vehicle subsystems in an independent platform exterior to flight software test processes. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test processes. Risk reduction is addressed by working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and detection and responses that can be tested in VMET and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM. The plan for VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗

NASA NTRS2009

Review of Alpha-Ketoglutaric Acid (AKGA) Hydrazine and Monomethylhydrazine (MMH) Neutralizing Compound

The Johnson Space Center (JSC) White Sands Test Facility (WSTF) and NASA Engineering and Safety Center (NESC) were requested by NASA Associate Administrator for Space Operations to perform an evaluation of a proposed hydrazine/monomethylhydrazine (MMH) fuel treatment method using alpha-ketoglutaric acid (AKGA). This evaluation request was prompted by preliminary tests at the Kennedy Space Center (KSC), suggesting cost and operational benefits to NASA for the Space Shuttle Program (SSP) and other hardware decontamination and decommissioning, in addition to hydrazine and MMH waste treatment activities. This paper provides the team's position on the current KSC and New Mexico Highlands University (NMHU) efforts toward implementing the AKGA treatment technology with flight hardware, ground support equipment (GSE), hydrazine and MMH spills, and vapor control. This evaluation is current to the last data examined (approximately September 2008).

Dibbern, Andreas W.↗

NASA NTRS2010

Evaluation of the NASA Arc Jet Capabilities to Support Mission Requirements

NASA accomplishes its strategic goals through human and robotic exploration missions. Many of these missions require launching and landing or returning spacecraft with human or return samples through Earth's and other planetary atmospheres. Spacecraft entering an atmosphere are subjected to extreme aerothermal loads. Protecting against these extreme loads is a critical element of spacecraft design. The safety and success of the planned mission is a prime concern for the Agency, and risk mitigation requires the knowledgeable use of thermal protection systems to successfully withstand the high-energy states imposed on the vehicle. Arc jets provide ground-based testing for development and flight validation of re-entry vehicle thermal protection materials and are a critical capability and core competency of NASA. The Agency's primary hypersonic thermal testing capability resides at the Ames Research Center and the Johnson Space Center and was developed and built in the 1960s and 1970s. This capability was critical to the success of Apollo, Shuttle, Pioneer, Galileo, Mars Pathfinder, and Orion. But the capability and the infrastructure are beyond their design lives. The complexes urgently need strategic attention and investment to meet the future needs of the Agency. The Office of Chief Engineer (OCE) chartered the Arc Jet Evaluation Working Group (AJEWG), a team of experienced individuals from across the Nation, to capture perspectives and requirements from the arc jet user community and from the community that operates and maintains this capability and capacity. This report offers the AJEWG's findings and conclusions that are intended to inform the discussion surrounding potential strategic technical and investment strategies. The AJEWG was directed to employ a 30-year Agency-level view so that near-term issues did not cloud the findings and conclusions and did not dominate or limit any of the strategic options.

Calomino, Anthony↗

NASA NTRS2017

USM3D Simulations for Second Sonic Boom Workshop

The NASA Tetrahedral Unstructured Software System with the USM3D flow solver was used to compute test cases for the Second AIAA Sonic Boom Prediction Workshop. The intent of this report is to document the USM3D results for SBPW2 test cases. The test cases included an axisymmetric equivalent area body, a JAXA wing body, a NASA low boom supersonic configuration modeled with flow through nacelles and engine boundary conditions. All simulations were conducted for a free stream Mach number of 1.6, zero degrees angle of attack, and a Reynolds number of 5.7 million per meter. Simulations were conducted on tetrahedral grids provided by the workshop committee, as well as a family of grids generated by an in-house approach for sonic boom analyses known as BoomGrid using current best practices. The near-field pressure signatures were extracted and propagated to the ground with the atmospheric propagation code, sBOOM. The USM3D near-field pressure signatures, corresponding sBOOM ground signatures, and loudness levels on the ground are compared with mean values from other workshop participants.

Elmiligui, Alaa↗

NASA NTRS1984

The role of scientists in developing Hubble Space Telescope

The objective of the Hubble Space Telescope Program is to build and operate a high-performance, fully-instrumented and long-lived optical observatory in earth orbit. Key Program elements are (1) a logistic strategy of Shuttle launch/maintenance and TDRSS communications, (2) overall responsibility at the MSFC Project for developing both the flight and ground systems, and (3) scientific participation in ST development and responsibility after launch for conducting the observing program. The ST Project is a management structure with a budget and schedule for delivering an ST system capable of achieving its established scientific objectives. The Project distributes through contracts the responsibility for supplying particular components, but retains the responsibility for system-level integrity. Scientists have set the performance objectives and now support the Project during the development stage by providing (1) PI management of the five Science Instruments, (2) continuing translations of scientific requirements into engineering specifications, (3) oversight of designs and performance tests, and (4) specific expertise on technical concerns.

Brown, R. A.↗

NASA NTRS1989

Investigation of difficult component effects on finite element model vibration prediction for the Bell AG-1G helicopter. Volume 2: Correlation results

Under the NASA-sponsored DAMVIBS (Design Analysis Methods for VIBrationS) program, a series of ground vibration tests and NASTRAN finite element model (FEM) correlations were conducted on the Bell AH-1G helicopter gunship to investigate the effects of difficult components on the vibration response of the airframe. Previous correlations of the AG-1G showed good agreement between NASTRAN and tests through 15 to 20 Hz, but poor agreement in the higher frequency range of 20 to 30 Hz. Thus, this effort emphasized the higher frequency airframe vibration response correlations and identified areas that need further R and T work. To conduct the investigations, selected difficult components (main rotor pylon, secondary structure, nonstructural doors/panels, landing gear, engine, furl, etc.) were systematically removed to quantify their effects on overall vibratory response of the airframe. The entire effort was planned and documented, and the results reviewed by NASA and industry experts in order to ensure scientific control of the testing, analysis, and correlation exercise. In particular, secondary structure and damping had significant effects on the frequency response of the airframe above 15 Hz. Also, the nonlinear effects of thrust stiffening and elastomer mounts were significant on the low frequency pylon modes below main rotor 1p (5.4 Hz). The results of the NASTRAN FEM correlations are given.

Dompka, R. V.↗

NASA NTRS1990

The Environmental Control and Life Support System (ECLSS) advanced automation project

The objective of the environmental control and life support system (ECLSS) Advanced Automation Project is to influence the design of the initial and evolutionary Space Station Freedom Program (SSFP) ECLSS toward a man-made closed environment in which minimal flight and ground manpower is needed. Another objective includes capturing ECLSS design and development knowledge future missions. Our approach has been to (1) analyze the SSFP ECLSS, (2) envision as our goal a fully automated evolutionary environmental control system - an augmentation of the baseline, and (3) document the advanced software systems, hooks, and scars which will be necessary to achieve this goal. From this analysis, prototype software is being developed, and will be tested using air and water recovery simulations and hardware subsystems. In addition, the advanced software is being designed, developed, and tested using automation software management plan and lifecycle tools. Automated knowledge acquisition, engineering, verification and testing tools are being used to develop the software. In this way, we can capture ECLSS development knowledge for future use develop more robust and complex software, provide feedback to the knowledge based system tool community, and ensure proper visibility of our efforts.

Dewberry, Brandon S.↗

NASA NTRS1994

Design Challenges Encountered in a Propulsion-Controlled Aircraft Flight Test Program

The NASA Dryden Flight Research Center conducted flight tests of a propulsion-controlled aircraft system on an F-15 airplane. This system was designed to explore the feasibility of providing safe emergency landing capability using only the engines to provide flight control in the event of a catastrophic loss of conventional flight controls. Control laws were designed to control the flightpath and bank angle using only commands to the throttles. Although the program was highly successful, this paper highlights some of the challenges associated with using engine thrust as a control effector. These challenges include slow engine response time, poorly modeled nonlinear engine dynamics, unmodeled inlet-airframe interactions, and difficulties with ground effect and gust rejection. Flight and simulation data illustrate these difficulties.

Maine, Trindel↗

NASA NTRS2001

A Space Based Internet Protocol System for Sub-Orbital Tracking and Control

Personnel from the Goddard Space Flight Center Wallops Flight Facility (GSFC/WFF) in Virginia are responsible for the overall management of the NASA Sounding Rocket Program. Payloads are generally in support of NASA's Space Science Enterprise's missions and return a variety of scientific data as well as providing a reasonably economical means of conducting engineering tests for instruments and devices used on satellites and other spacecraft. The fifteen types of sounding rockets used by NASA can carry payloads of various weights to altitudes from 50 km to more than 1,300 km. Launch activities are conducted not only from established missile ranges, but also from remote locations worldwide requiring mobile tracking and command equipment to be transported and set up at considerable expense. The advent of low earth orbit (LEO) commercial communications satellites provides an opportunity to dramatically reduce tracking and control costs of launch vehicles and Unpiloted Aerial Vehicles (UAVs) by reducing or eliminating this ground infrastructure. Additionally, since data transmission is by packetized Internet Protocol (IP), data can be received and commands initiated from practically any location. A low cost Commercial Off The Shelf (COTS) system is currently under development for sounding rockets which also has application to UAVs and scientific balloons. Due to relatively low data rate (9600 baud) currently available, the system will first be used to provide GPS data for tracking and vehicle recovery. Range safety requirements for launch vehicles usually stipulate at least two independent tracking sources. Most sounding rockets flown by NASA now carry GPS receivers that output position data via the payload telemetry system to the ground station. The Flight Modem can be configured as a completely separate link thereby eliminating requirement for tracking radar. The system architecture which integrates antennas, GPS receiver, commercial satellite packet data modem, and a single board computer with custom software is described along with the technical challenges and the plan for their resolution. These include antenna development, high Doppler rates, reliability, environmental ruggedness, hand over between satellites and data security. An aggressive test plan is included which in addition to environmental testing measures bit error rate, latency and antenna patterns. Actual flight tests are planned for the near future on aircraft, long duration balloons and sounding rockets and these results as well as the current status of the project are reported.

Bull, Barton↗

NASA NTRS2017

Autonomy Operating System for UAVs: Pilot-in-a-Box

The Autonomy Operating System (AOS) is an open flight software platform with Artificial Intelligence for smart UAVs. It is built to be extendable with new apps, similar to smartphones, to enable an expanding set of missions and capabilities. AOS has as its foundations NASAs core flight executive and core flight software (cFEcFS). Pilot-in-a-Box (PIB) is an expanding collection of interacting AOS apps that provide the knowledge and intelligence onboard a UAV to safely and autonomously fly in the National Air Space, eventually without a remote human ground crew. Longer-term, the goal of PIB is to provide the capability for pilotless air vehicles such as air taxis that will be key for new transportation concepts such as mobility-on-demand. PIB provides the procedural knowledge, situational awareness, and anticipatory planning (thinking ahead of the plane) that comprises pilot competencies. These competencies together with a natural language interface will enable Pilot-in-a-Box to dialogue directly with Air Traffic Management from takeoff through landing. This paper describes the overall AOS architecture, Artificial Intelligence reasoning engines, Pilot-in-a-box competencies, and selected experimental flight tests to date.

Lowry, Michael↗

NASA NTRS2023

Orbital Debris Shape Effect Investigations for Mitigating Risk

NASA’s Orbital Debris Program Office (ODPO) and Hypervelocity Impact Technology (HVIT) team have coordinated to better understand the risks to upper stages and spacecraft from non-spherical orbital debris. It is well understood that fragmentation (collision or explosion) events in orbit produce fragments of various materials, sizes, and shapes. To further characterize these parameters, the ODPO is developing the next-generation Orbital Debris Engineering Model (ORDEM) version 4.0 to include orbital debris shape distributions. Ground-based assets, such as radar and optical sensors, can provide size estimates and some insight into material based on radar return or optical filter photometry/spectroscopy, respectively. Characterizing an object’s shape requires more laboratory analyses to infer how shape affects these measurements. More importantly, in addition to size and material/density, the shape of fragments in orbit will alter the ballistic limit equations used in orbital debris risk assessments with NASA’s Bumper Code. The ODPO plans to release ORDEM 4.0 in the coming years. Performing ground-based laboratory impact tests on high-fidelity spacecraft mockups provides the means to directly measure size, mass, material/density, and shape of fragments, all key parameters needed to characterize real-world break up events. The DebriSat test, the results of which are provided, showcases the details of this type of experiment. The goal of this collaborative research between the ODPO and the HVIT team is to include a shape parameter in the environmental and breakup models used to assess risk for various space structures. This paper examines ground-based laboratory impact tests and the associated fragment shape categories. Provided these defined shapes, the approach is simplified by assuming a right circular cylinder (RCC) approximation with varying length-to-diameter ratios. Highlights of impact tests conducted by the HVIT team using non-spherical projectiles based on the RCC approximation are presented. Hydrocode simulations have also been performed to expand on the complexity of variations with non-spherical projectiles. Lastly, ray-tracing simulations of various RCCs of known material are provided to support the ongoing research on optical reflectance distributions with known shapes and to highlight how this may modify the current optical size estimation model. The status and plan forward are outlined for NASA's orbital debris shape effect investigation using a multidisciplinary approach by the ODPO and the HVIT team.

Heather Cowardin↗

NASA NTRS2023

Orbital Debris Shape Effect Investigations for Mitigating Risk

Heather Cowardin↗

DOE OSTI2020

EQSIM—A multidisciplinary framework for fault-to-structure earthquake simulations on exascale computers part I: Computational models and workflow

Computational simulations have become central to the seismic analysis and design of major infrastructure over the past several decades. Most major structures are now “proof tested” virtually through representative simulations of earthquake-induced response. More recently, with the advancement of high-performance computing (HPC) platforms and the associated massively parallel computational ecosystems, simulation is beginning to play a role in increased understanding and prediction of ground motions for earthquake hazard assessments. However, the computational requirements for regional-scale geophysics-based ground motion simulations are extreme, which has restricted the frequency resolution of direct simulations and limited the ability to perform the large number of simulations required to numerically explore the problem parametric space. In this article, recent developments toward an integrated, multidisciplinary earth science-engineering computational framework for the regional-scale simulation of both ground motions and resulting structural response are described with a particular emphasis on advancing simulations to frequencies relevant to engineered systems. This multidisciplinary computational development is being carried out as part of the US Department of Energy (DOE) Exascale Computing Project with the goal of achieving a computational framework poised to exploit emerging DOE exaflop computer platforms scheduled for the 2022–2023 timeframe.

58 GEOSCIENCES↗

NASA NTRS1999

Low-Boom SR-71 Modified Signature Demonstration Program

A flight program using the SR-71 airplane to validate sonic boom technologies for High-Speed Commercial Transport (HSCT) operation and potentially for low- or softened-boom design configurations is described. This program employs a shaped signature modification to the SR-71 airplane which is designed to demonstrate computational fluid dynamics (CFD) design technology at a full-scale HSCT operating condition of Mach 1.8 at 48,000 feet altitude. Test plans call for measurements in the near-field, at intermediate propagation altitudes, and through the more turbulent boundary layer near the Earth surface. The shaped signature modification to the airplane is comprised of added cross-section areas on the underside of the airplane forward of the wing and engine nacelles. Because the flight demonstration does not approach maximum SR-71 altitude or Mach number, the airplane provides more than adequate performance and maneuver margins for safe operation of the modified airplane. Probe airplane measurements in the near-field will use fast response pressure sensors. Far-field and ground-based boom measurements will use high response microphones or conventional sonic boom field recorders. Scope of the planned demonstration flights also includes ground level measurements during conditions which cause minimal signature distortion and conditions which cause high distortion of the signature.

David Lux↗

NASA NTRS2016

Topic Modeling of NASA Space System Problem Reports: Research in Practice

Problem reports at NASA are similar to bug reports: they capture defects found during test, post-launch operational anomalies, and document the investigation and corrective action of the issue. These artifacts are a rich source of lessons learned for NASA, but are expensive to analyze since problem reports are comprised primarily of natural language text. We apply topic modeling to a corpus of NASA problem reports to extract trends in testing and operational failures. We collected 16,669 problem reports from six NASA space flight missions and applied Latent Dirichlet Allocation topic modeling to the document corpus. We analyze the most popular topics within and across missions, and how popular topics changed over the lifetime of a mission. We find that hardware material and flight software issues are common during the integration and testing phase, while ground station software and equipment issues are more common during the operations phase. We identify a number of challenges in topic modeling for trend analysis: 1) that the process of selecting the topic modeling parameters lacks definitive guidance, 2) defining semantically-meaningful topic labels requires nontrivial effort and domain expertise, 3) topic models derived from the combined corpus of the six missions were biased toward the larger missions, and 4) topics must be semantically distinct as well as cohesive to be useful. Nonetheless,topic modeling can identify problem themes within missions and across mission lifetimes, providing useful feedback to engineers and project managers.

Data Mining↗