Search NASA⌕ Search

SEARCH · Search NASA

Results for “Organization metric”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Global and Regional Temperature-change Potentials for Near-term Climate Forcers

We examine the climate effects of the emissions of near-term climate forcers (NTCFs) from 4 continental regions (East Asia, Europe, North America and South Asia) using results from the Task Force on Hemispheric Transport of Air Pollution Source-Receptor global chemical transport model simulations. We address 3 aerosol species (sulphate, particulate organic matter and black carbon) and 4 ozone precursors (methane, reactive nitrogen oxides (NOx), volatile organic compounds and carbon monoxide). We calculate the global climate metrics: global warming potentials (GWPs) and global temperature change potentials (GTPs). For the aerosols these metrics are simply time-dependent scalings of the equilibrium radiative forcings. The GTPs decrease more rapidly with time than the GWPs. The aerosol forcings and hence climate metrics have only a modest dependence on emission region. The metrics for ozone precursors include the effects on the methane lifetime. The impacts via methane are particularly important for the 20 yr GTPs. Emissions of NOx and VOCs from South Asia have GWPs and GTPs of higher magnitude than from the other Northern Hemisphere regions. The analysis is further extended by examining the temperature-change impacts in 4 latitude bands, and calculating absolute regional temperature-change potentials (ARTPs). The latitudinal pattern of the temperature response does not directly follow the pattern of the diagnosed radiative forcing. We find that temperatures in the Arctic latitudes appear to be particularly sensitive to BC emissions from South Asia. The northern mid-latitude temperature response to northern mid-latitude emissions is approximately twice as large as the global average response for aerosol emission, and about 20-30% larger than the global average for methane, VOC and CO emissions.

North America↗
NASA NTRS2021

Technology Readiness Level as the Foundation of Human Readiness Level

Communication of the maturity of technology through the program/product life cycles helps enhance risk management from the beginning and support decision-making strategies for research, development, and allocation of resources. Currently, many organizations use the technology readiness level (TRL) as a simple metric to indicate the maturity of the technology. This article will discuss the TRL history, define the TRL levels, show how the TRL relates to the technology life cycle, and how the TRL framework contributes to the human readiness level (HRL) structure. Through the TRL advantages and disadvantages, this article will show how the TRL falls short in numerous areas of engineering, including the integration readiness of system/subsystem components and assessment of the readiness of the technology to operate within the human capabilities and limitations. Yet the article also shows how the TRL serves as the foundation for HRL.

George Salazar↗
NASA NTRS2004

Software Quality Assurance Metrics

Software Quality Assurance (SQA) is a planned and systematic set of activities that ensures conformance of software life cycle processes and products conform to requirements, standards and procedures. In software development, software quality means meeting requirements and a degree of excellence and refinement of a project or product. Software Quality is a set of attributes of a software product by which its quality is described and evaluated. The set of attributes includes functionality, reliability, usability, efficiency, maintainability, and portability. Software Metrics help us understand the technical process that is used to develop a product. The process is measured to improve it and the product is measured to increase quality throughout the life cycle of software. Software Metrics are measurements of the quality of software. Software is measured to indicate the quality of the product, to assess the productivity of the people who produce the product, to assess the benefits derived from new software engineering methods and tools, to form a baseline for estimation, and to help justify requests for new tools or additional training. Any part of the software development can be measured. If Software Metrics are implemented in software development, it can save time, money, and allow the organization to identify the caused of defects which have the greatest effect on software development. The summer of 2004, I worked with Cynthia Calhoun and Frank Robinson in the Software Assurance/Risk Management department. My task was to research and collect, compile, and analyze SQA Metrics that have been used in other projects that are not currently being used by the SA team and report them to the Software Assurance team to see if any metrics can be implemented in their software assurance life cycle process.

McRae, Kalindra A.↗
NASA NTRS2014

Benefits Analysis of Wind-Optimal Operations For Trans-Atlantic Flights

North Atlantic Tracks are trans-Atlantic routes across the busiest oceanic airspace in the world. This study analyzes and compares current flight-plan routes to wind-optimal routes for trans-Atlantic flights in terms of aircraft fuel burn, emissions and the associated climate impact. The historical flight track data recorded by EUROCONTROL's Central Flow Management Unit is merged with data from FAA's Enhanced Traffic Management System to provide an accurate flight movement database containing the highest available flight path resolution in both systems. The combined database is adopted for airspace simulation integrated with aircraft fuel burn and emissions models, contrail models, simplified climate response models, and a common climate metric to assess the climate impact of flight routes within the Organized Track System (OTS). The fuel burn and emissions for the tracks in the OTS are compared with the corresponding quantities for the wind-optimized routes to evaluate the potential environmental benefits of flying wind-optimal routes in North Atlantic Airspace. The potential fuel savings and reduction in emissions depend on existing inefficiencies in current flight plans, atmospheric conditions and location of the city-pairs. The potential benefits are scaled by comparing them with actual flight tests that have been conducted since 2010 between a few city-pairs in the transatlantic and trans-pacific region to improve fuel consumption and reduce the environmental impact of aviation.

air traffic optimization↗
NASA NTRS2009

Distributed Trajectory Flexibility Preservation for Traffic Complexity Mitigation

The growing demand for air travel is increasing the need for mitigation of air traffic congestion and complexity problems, which are already at high levels. At the same time new information and automation technologies are enabling the distribution of tasks and decisions from the service providers to the users of the air traffic system, with potential capacity and cost benefits. This distribution of tasks and decisions raises the concern that independent user actions will decrease the predictability and increase the complexity of the traffic system, hence inhibiting and possibly reversing any potential benefits. In answer to this concern, the authors propose the introduction of decision-making metrics for preserving user trajectory flexibility. The hypothesis is that such metrics will make user actions naturally mitigate traffic complexity. In this paper, the impact of using these metrics on traffic complexity is investigated. The scenarios analyzed include aircraft in en route airspace with each aircraft meeting a required time of arrival in a one-hour time horizon while mitigating the risk of loss of separation with the other aircraft, thus preserving its trajectory flexibility. The experiments showed promising results in that the individual trajectory flexibility preservation induced self-separation and self-organization effects in the overall traffic situation. The effects were quantified using traffic complexity metrics based on Lyapunov exponents and traffic proximity.

Idris, Husni↗
NASA NTRS2009

Analysis of Trajectory Flexibility Preservation Impact on Traffic Complexity

The growing demand for air travel is increasing the need for mitigation of air traffic congestion and complexity problems, which are already at high levels. At the same time new information and automation technologies are enabling the distribution of tasks and decisions from the service providers to the users of the air traffic system, with potential capacity and cost benefits. This distribution of tasks and decisions raises the concern that independent user actions will decrease the predictability and increase the complexity of the traffic system, hence inhibiting and possibly reversing any potential benefits. In answer to this concern, the authors proposed the introduction of decision-making metrics for preserving user trajectory flexibility. The hypothesis is that such metrics will make user actions naturally mitigate traffic complexity. In this paper, the impact of using these metrics on traffic complexity is investigated. The scenarios analyzed include aircraft in en route airspace with each aircraft meeting a required time of arrival in a one-hour time horizon while mitigating the risk of loss of separation with the other aircraft, thus preserving its trajectory flexibility. The experiments showed promising results in that the individual trajectory flexibility preservation induced self-separation and self-organization effects in the overall traffic situation. The effects were quantified using traffic complexity metrics, namely dynamic density indicators, which indicated that using the flexibility metrics reduced aircraft density and the potential of loss of separation.

Idris, Husni↗
NASA NTRSDate not supplied

Genetic Determinants of Microbial Survival in Space

Space flight agencies envision a future for humankind beyond Earth, including missions back to the Moon and to Mars in the coming decades. Sending humans into space inevitably includes their microbiomes as well, leading to trillions of bacteria being shed in their living areas. These bacteria shape the lives of their hosts as well as their environment; thus, it is crucial to understand the adaptations of these microbial spacefarers in spaceflight conditions. We aimed to elucidate the genetic determinants of microbial survival in space using a pan-genome analysis of 12 genera cultured from the International Space Station (ISS) from 2017 to 2018. Analysis was performed on each of the genera individually with terrestrial analogs to identify the core and accessory genomes of the spaceflight and terrestrial strains. We then compared the flight and terrestrial core and accessory genomes for each genera using a Bray-Curtis index and visualized the resulting dissimilarity using an Non-Metric Dimensional Scaling plot. The core proteins available in only the spaceflight organisms were then manually characterized for function and genomic location. In every core genome comparison in each genus, there was significant dissimilarity in the core of the spaceflight organisms when compared to the terrestrial organisms. This trend was present in some of the accessory genomes, but was not ubiquitous. Functional analysis of the core content of the ISS genomes showed the majority of genes unique to the core were clustered by location. These gene clusters suggested a set of genetic determinants confer survival in spacecraft-built environments, notably through the uptake of extracellular DNA such as bacteriophage and plasmids. The clear difference between spaceflight and terrestrial microorganisms shows that spaceflight conditions are selective, which has long term implications for their human hosts and environments.

MoBE↗
NASA NTRS1999

Industrial Hygiene Issues

This breakout session is a traditional conference instrument used by the NASA industrial hygiene personnel as a method to convene personnel across the Agency with common interests. This particular session focused on two key topics, training systems and automation of industrial hygiene data. During the FY 98 NASA Occupational Health Benchmarking study, the training system under development by the U.S. Environmental Protection Agency (EPA) was deemed to represent a "best business practice." The EPA has invested extensively in the development of computer based training covering a broad range of safety, health and environmental topics. Currently, five compact disks have been developed covering the topics listed: Safety, Health and Environmental Management Training for Field Inspection Activities; EPA Basic Radiation Training Safety Course; The OSHA 600 Collateral Duty Safety and Health Course; and Key program topics in environmental compliance, health and safety. Mr. Chris Johnson presented an overview of the EPA compact disk-based training system and answered questions on its deployment and use across the EPA. This training system has also recently been broadly distributed across other Federal Agencies. The EPA training system is considered "public domain" and, as such, is available to NASA at no cost in its current form. Copies of the five CD set of training programs were distributed to each NASA Center represented in the breakout session. Mr. Brisbin requested that each NASA Center review the training materials and determine whether there is interest in using the materials as it is or requesting that EPA tailor the training modules to suit NASA's training program needs. The Safety, Health and Medical Services organization at Ames Research Center has completed automation of several key program areas. Mr. Patrick Hogan, Safety Program Manager for Ames Research Center, presented a demonstration of the automated systems, which are described by the following: (1) Safety, Health and Environmental Training. This system includes an assessment of training needs for every NASA Center organization, course descriptions, schedules and automated course scheduling, and presentation of training program metrics; (2) Safety and Health Inspection Information. This system documents the findings from each facility inspection, tracks abatement status on those findings and presents metrics on each department for senior management review; (3) Safety Performance Evaluation Profile. The survey system used by NASA to evaluate employee and supervisory perceptions of safety programs is automated in this system; and (4) Documentation Tracking System. Electronic archive and retrieval of all correspondence and technical reports generated by the Safety, Health and Medical Services Office are provided by this system.

Brisbin, Steven G.↗
NASA NTRS2003

Turbulence Detection and Mitigation Element

This paper presents viewgraphs on turbulence detection and mitigation technologies in weather accident prevention. The topics include: 1) Organization; 2) Scope of Turbulence Effort; 3) Background; 4) Turbulence Detection and Mitigation Program Metrics; 5) Approach; 6) Turbulence Team Relationships; 7) WBS Structure; 8) Deliverables; 9) TDAM Changes; 10) FY-01 Results/Accomplishments; 11) Out-year Plans; and 12) Element Status.

Bogue, Rod↗
NASA NTRS2016

Access to Archived Astronaut Data for Human Research Program Researchers: Update on Progress and Process Improvements

Since the 2010 NASA directive to make the Life Sciences Data Archive (LSDA) and Lifetime Surveillance of Astronaut Health (LSAH) data archives more accessible by the research and operational communities, demand for astronaut medical data has increased greatly. LSAH and LSDA personnel are working with Human Research Program on many fronts to improve data access and decrease lead time for release of data. Some examples include the following: Feasibility reviews for NASA Research Announcement (NRA) data mining proposals; Improved communication, support for researchers, and process improvements for retrospective Institutional Review Board (IRB) protocols; Supplemental data sharing for flight investigators versus purely retrospective studies; Work with the Multilateral Human Research Panel for Exploration (MHRPE) to develop acceptable data sharing and crew consent processes and to organize inter-agency data coordinators to facilitate requests for international crewmember data. Current metrics on data requests crew consenting will be presented, along with limitations on contacting crew to obtain consent. Categories of medical monitoring data available for request will be presented as well as flow diagrams detailing data request processing and approval steps.

Lee, L. R.↗
NASA NTRS2010

NASA Education Activities on the International Space Station: A National Laboratory for Inspiring, Engaging, Educating and Employing the Next Generation

The International Space Station (ISS) National Lab Education Project has been created as a part of the ISS National Lab effort mandated by the U.S. Congress The project seeks to expand ISS education of activities so that they reach a larger number of students with clear educational metrics of accomplishments. This paper provides an overview of several recent ISS educational payloads and activities. The expected outcomes of the project, consistent with those of the NASA Office of Education, are also described. NASA performs numerous education activities as part of its ISS program. These cover the gamut from formal to informal educational opportunities in grades Kindergarten to grade 12, Higher Education (undergraduate and graduate University) and informal educational venues (museums, science centers, exhibits). Projects within the portfolio consist of experiments performed onboard the ISS using onboard resources which require no upmass, payloads flown to ISS or integrated into ISS cargo vehicles, and ground based activities that follow or complement onboard activities. Examples include ground based control group experiments, flight or experiment following lesson plans, ground based activities involving direct interaction with ISS or ground based activities considering ISS resources in their solution set. These projects range from totally NASA funded to projects which partner with external entities. These external agencies can be: other federal, state or local government agencies, commercial entities, universities, professional organizations or non-profit organizations. This paper will describe the recent ISS education activities and discuss the approach, outcomes and metrics associated with the projects.

Severance, Mark T.↗
NASA NTRS2020

Increasing anthropogenic methane emissions arise equally from agricultural and fossil fuel sources

Climate stabilization remains elusive, with increased greenhouse gas concentrations already increasing global average surface temperatures 1.1°C above pre-industrial levels (World Meteorological Organization 2019). Carbon dioxide (CO2) emissions from fossil fuel use, deforestation, and other anthropogenic sources reached ~ 43 billion metric tonnes in 2019 (Friedlingstein et al 2019, Jackson et al 2019). Storms, floods, and other extreme weather events displaced a record 7 million people in the first half of 2019 (IDMC 2019). When global mean surface temperature four million years ago was 2°C–3°C warmer than today (a likely temperature increase before the end of the century), ice sheets in Greenland and West Antarctica melted and parts of East Antarctica’s ice retreated, causing sea levels to rise 10–20 m (World Meteorological Organization 2019). Methane (CH4) emissions have contributed almost one quarter of the cumulative radiative forcings for CO2, CH4, and N2O (nitrous oxide) combined since 1750 (Etminan et al 2016). Although methane is far less abundant in the atmosphere than CO2, it absorbs thermal infrared radiation much more efficiently and, in consequence, has a global warming potential (GWP) ~86 times stronger per unit mass than CO2 on a 20-year timescale and 28- times more powerful on a 100-year time scale (IPCC 2014). Global average methane concentrations in the atmosphere reached ~1875 parts per billion (ppb) at the end of 2019, more than two-and-a-half times preindustrial levels (Dlugokencky 2020). The largest methane sources include anthropogenic emissions from agriculture, waste, and the extraction and use of fossil fuels as well as natural emissions from wetlands, freshwater systems, and geological sources (Kirschke et al 2013, Saunois et al 2016a, Ganesan et al 2019). Here, we summarize new estimates of the global methane budget based on the analysis of Saunois et al (2020) for the year 2017, the last year of the new Global Methane Budget and the most recent year data are fully available. We compare these estimates to mean values for the reference ‘stabilization’ period of 2000–2006 when atmospheric CH4 concentrations were relatively stable. We present data for sources and sinks and provide insights for the geographical regions and economic sectors where emissions have changed the most over recent decades.

fossil fuel sources↗
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 NTRS2011

Complexity Management Using Metrics for Trajectory Flexibility Preservation and Constraint Minimization

The growing demand for air travel is increasing the need for mitigating air traffic congestion and complexity problems, which are already at high levels. At the same time new surveillance, navigation, and communication technologies are enabling major transformations in the air traffic management system, including net-based information sharing and collaboration, performance-based access to airspace resources, and trajectory-based rather than clearance-based operations. The new system will feature different schemes for allocating tasks and responsibilities between the ground and airborne agents and between the human and automation, with potential capacity and cost benefits. Therefore, complexity management requires new metrics and methods that can support these new schemes. This paper presents metrics and methods for preserving trajectory flexibility that have been proposed to support a trajectory-based approach for complexity management by airborne or ground-based systems. It presents extensions to these metrics as well as to the initial research conducted to investigate the hypothesis that using these metrics to guide user and service provider actions will naturally mitigate traffic complexity. The analysis showed promising results in that: (1) Trajectory flexibility preservation mitigated traffic complexity as indicated by inducing self-organization in the traffic patterns and lowering traffic complexity indicators such as dynamic density and traffic entropy. (2)Trajectory flexibility preservation reduced the potential for secondary conflicts in separation assurance. (3) Trajectory flexibility metrics showed potential application to support user and service provider negotiations for minimizing the constraints imposed on trajectories without jeopardizing their objectives.

Idris, Husni↗
NASA NTRS2014

Frequency of Specific Categories of Aviation Accidents and Incidents During 2001-2010

The purpose of this study was to determine the types of accidents or incidents that are most important to the aviation safety risk. All accidents and incidents from 2001-2010 were assigned occurrence categories based on the taxonomy developed by the Commercial Aviation Safety Team/International Civil Aviation Organization (CAST/ICAO) Common Taxonomy Team (CICTT). The most frequently recorded categories were selected within each of five metrics: total accidents, fatal accidents, total injuries, fatal injuries and total incidents. This analysis was done separately for events within Part 121, Scheduled Part 135, Non-Scheduled Part 135 and Part 91. Combining those five sets of categories resulted in groups of between seven and eleven occurrence categories, depending on the flight operation. These groups represent 65-85% of all accidents and 68-81% of incidents.

Evans, Joni K.↗
NASA NTRS1994

A process improvement model for software verification and validation

We describe ongoing work at the NASA Independent Verification and Validation (IV&V) Facility to establish a process improvement model for software verification and validation (V&V) organizations. This model, similar to those used by some software development organizations, uses measurement-based techniques to identify problem areas and introduce incremental improvements. We seek to replicate this model for organizations involved in V&V on large-scale software development projects such as EOS and Space Station. At the IV&V Facility, a university research group and V&V contractors are working together to collect metrics across projects in order to determine the effectiveness of V&V and improve its application. Since V&V processes are intimately tied to development processes, this paper also examines the repercussions for development organizations in large-scale efforts.

Callahan, John↗
NASA NTRS1994

A process improvement model for software verification and validation

We describe ongoing work at the NASA Independent Verification and Validation (IV&V) Facility to establish a process improvement model for software verification and validation (V&V) organizations. This model, similar to those used by some software development organizations, uses measurement-based techniques to identify problem areas and introduce incremental improvements. We seek to replicate this model for organizations involved in V&V on large-scale software development projects such as EOS and space station. At the IV&V Facility, a university research group and V&V contractors are working together to collect metrics across projects in order to determine the effectiveness of V&V and improve its application. Since V&V processes are intimately tied to development processes, this paper also examines the repercussions for development organizations in large-scale efforts.

Callahan, John↗
NASA NTRS2000

Predictive Multiple Model Switching Control with the Self-Organizing Map

A predictive, multiple model control strategy is developed by extension of self-organizing map (SOM) local dynamic modeling of nonlinear autonomous systems to a control framework. Multiple SOMs collectively model the global response of a nonautonomous system to a finite set of representative prototype controls. Each SOM provides a codebook representation of the dynamics corresponding to a prototype control. Different dynamic regimes are organized into topological neighborhoods where the adjacent entries in the codebook represent the global minimization of a similarity metric. The SOM is additionally employed to identify the local dynamical regime, and consequently implements a switching scheme that selects the best available model for the applied control. SOM based linear models are used to predict the response to a larger family of control sequences which are clustered on the representative prototypes. The control sequence which corresponds to the prediction that best satisfies the requirements on the system output is applied as the external driving signal.

Motter, Mark A.↗