Differences in Performance of Naturally and Artificially Propagated Sockeye Salmon Migrant Fry, as Measured with Swimming and Predation Tests

1967 ◽  
Vol 24 (5) ◽  
pp. 1117-1153 ◽  
Author(s):  
R. A. Bams

Two methods of performance testing were developed to measure differences in stamina in four groups of sockeye migrant fry, all of the Lakelse Lake (Skeena River, B.C.) stock. The four groups differed only in methods of incubation: one group was naturally propagated, the other three artificially. The results of the swimming performance tests and the vulnerability to predation tests agree closely, and analysis shows that the key factor responsible for differences in performance is size of the fish. Ranked in decreasing order of performance these four groups rate as follows: naturally propagated fish, fish incubated in gravel from time of hatching, fish incubated in gravel only for the last few weeks as premigrants, and fish that spent their entire incubation period without gravel in hatchery baskets. Independent of size is the influence of condition (K-factor) of the fish, optimum performance occurring at the time of almost complete yolk absorption. Of the two methods the swimming performance test was found to be more sensitive and is recommended as a tool for comparative "quality testing" of fish stocks.

2019 ◽  
Vol 2 (3) ◽  
pp. 28
Author(s):  
Elena Markoska ◽  
Aslak Johansen ◽  
Mikkel Baun Kjærgaard ◽  
Sanja Lazarova-Molnar ◽  
Muhyiddine Jradi ◽  
...  

Performance testing of components and subsystems of buildings is a promising practice for increasing energy efficiency and closing gaps between intended and actual performance of buildings. A typical shortcoming of performance testing is the difficulty of linking a failing test to a faulty or underperforming component. Furthermore, a failing test can also be linked to a wrongly configured performance test. In this paper, we present Building Metadata Performance Testing (BuMPeT), a method that addresses this shortcoming by using building metadata models to extend performance testing with fault detection and diagnostics (FDD) capabilities. We present four different procedures that apply BuMPeT to different data sources and components. We have applied the proposed method to a case study building, located in Denmark, to test its capacity and benefits. Additionally, we use two real case scenarios to showcase examples of failing performance tests in the building, as well as discovery of causes of underperformance. Finally, to examine the limits to the benefits of the applied procedure, a detailed elaboration of a hypothetical scenario is presented. Our findings demonstrate that the method has potential and it can serve to increase the energy efficiency of a wide range of buildings.


2016 ◽  
Author(s):  
Philipp Leitner ◽  
Cor-Paul Bezemer

The usage of open source (OS) software is nowadays wide- spread across many industries and domains. While the functional quality of OS projects is considered to be up to par with that of closed-source software, much is unknown about the quality in terms of non-functional attributes, such as performance. One challenge for OS developers is that, unlike for functional testing, there is a lack of accepted best practices for performance testing. To reveal the state of practice of performance testing in OS projects, we conduct an exploratory study on 111 Java-based OS projects from GitHub. We study the performance tests of these projects from five perspectives: (1) the developers, (2) size, (3) organization and (4) types of performance tests and (5) the tooling used for performance testing. First, in a quantitative study we show that writing performance tests is not a popular task in OS projects: performance tests form only a small portion of the test suite, are rarely updated, and are usually maintained by a small group of core project developers. Second, we show through a qualitative study that even though many projects are aware that they need performance tests, developers appear to struggle implementing them. We argue that future performance testing frameworks should provider better support for low-friction testing, for instance via non-parameterized methods or performance test generation, as well as focus on a tight integration with standard continuous integration tooling.


Author(s):  
Douglas H. Harris

This study examined the effect of subdividing grading units on performance test reliability. That is, instead of increasing test length by adding grading units comparable to existing grading units, this experimental approach attempted to increase test length, and hence reliability, by subdividing existing grading units into comparable subunits. The effect of subdividing grading units was assessed empirically using a performance test of the ultrasonic detection of cracks in pipe welds. Five-hour performance tests involving the examination of 10 pipe-weld specimens were completed by each of 52 experienced ultrasonic operators as part of their qualification for performing tasks of this type in nuclear power plants. Subdivision of grading units was found to increase the reliability of the test from 0.28 to 0.92, to decrease the standard error of measurement of the test from 13.81 to 1.35, and to decrease the 90% confidence band around test scores from ± 22.60 to ±2.20. Moreover, the increased reliability was predicted by the Spearman-Brown Prophecy Formula, the method commonly employed for predicting the effect of increased length on test reliability.


Author(s):  
Philipp Leitner ◽  
Cor-Paul Bezemer

The usage of open source (OS) software is nowadays wide- spread across many industries and domains. While the functional quality of OS projects is considered to be up to par with that of closed-source software, much is unknown about the quality in terms of non-functional attributes, such as performance. One challenge for OS developers is that, unlike for functional testing, there is a lack of accepted best practices for performance testing. To reveal the state of practice of performance testing in OS projects, we conduct an exploratory study on 111 Java-based OS projects from GitHub. We study the performance tests of these projects from five perspectives: (1) the developers, (2) size, (3) organization and (4) types of performance tests and (5) the tooling used for performance testing. First, in a quantitative study we show that writing performance tests is not a popular task in OS projects: performance tests form only a small portion of the test suite, are rarely updated, and are usually maintained by a small group of core project developers. Second, we show through a qualitative study that even though many projects are aware that they need performance tests, developers appear to struggle implementing them. We argue that future performance testing frameworks should provider better support for low-friction testing, for instance via non-parameterized methods or performance test generation, as well as focus on a tight integration with standard continuous integration tooling.


2016 ◽  
Author(s):  
Philipp Leitner ◽  
Cor-Paul Bezemer

The usage of open source (OS) software is nowadays wide- spread across many industries and domains. While the functional quality of OS projects is considered to be up to par with that of closed-source software, much is unknown about the quality in terms of non-functional attributes, such as performance. One challenge for OS developers is that, unlike for functional testing, there is a lack of accepted best practices for performance testing. To reveal the state of practice of performance testing in OS projects, we conduct an exploratory study on 111 Java-based OS projects from GitHub. We study the performance tests of these projects from five perspectives: (1) the developers, (2) size, (3) organization and (4) types of performance tests and (5) the tooling used for performance testing. First, in a quantitative study we show that writing performance tests is not a popular task in OS projects: performance tests form only a small portion of the test suite, are rarely updated, and are usually maintained by a small group of core project developers. Second, we show through a qualitative study that even though many projects are aware that they need performance tests, developers appear to struggle implementing them. We argue that future performance testing frameworks should provider better support for low-friction testing, for instance via non-parameterized methods or performance test generation, as well as focus on a tight integration with standard continuous integration tooling.


Materials ◽  
2021 ◽  
Vol 14 (3) ◽  
pp. 474
Author(s):  
Huaqiao Liu ◽  
Yiren Pan ◽  
Huiguang Bian ◽  
Chuansheng Wang

In this study, the two key factors affecting the thermal performance of the insert rubber and stress distribution on the tire sidewall were analyzed extensively through various performance tests and simulations to promote the development of run-flat tires. Four compounds and two structures of insert rubber were designed to investigate the effects of heat accumulation and stress distribution on durability testing at zero pressure. It was concluded that the rigidity and tensile strength of the compound were negatively correlated with temperature. The deformation was a key factor that affects energy loss, which could not be judged solely by the loss factor. The stress distribution, however, should be considered in order to avoid early damage of the tire caused by stress concentration. On the whole, the careful balance of mechanical strength, energy loss, and structural rigidity was the key to the optimal development of run-flat tires. More importantly, the successful implementation of the simulations in the study provided important and useful guidance for run-flat tire development.


Author(s):  
Amir Golalipour ◽  
Varun Veginati ◽  
David J. Mensching

In the asphalt materials community, the most critical research need is centered around a paradigm shift in mixture design from the volumetric process of the previous 20-plus years to an optimization procedure based on laboratory-measured mechanical properties that should lead to an increase in long-term pavement performance. This study is focused on advancing the state of understanding with respect to the value of intermediate temperature cracking tests, which may be included in a balanced mix design. The materials included are plant-mixed, laboratory-compacted specimens reheated from the 2013 Federal Highway Administration’s (FHWA’s) Accelerated Loading Facility (ALF) study on reclaimed asphalt pavement/reclaimed asphalt shingle (RAP/RAS) materials. Six commonly discussed intermediate temperature (cracking and durability) performance testing (i.e., Asphalt Mixture Performance Tester [AMPT] Cyclic Fatigue, Cantabro, Illinois Flexibility Index Test [I-FIT], Indirect Tensile Cracking [ITC, also known as IDEAL-CT], Indirect Tensile Nflex, and Texas Overlay Test) were selected for use in this study based on input from stakeholders. Test results were analyzed to compare differences between the cracking tests. In addition, statistical analyses were conducted to assess the separation among materials (lanes) for each performance test. Cyclic fatigue and IDEAL-CT tests showed the most promising results. The ranking from these two tests’ index parameters matched closely with ALF field performance. Furthermore, both showed reasonable variability of test data and they were successful in differentiating between different materials.


Author(s):  
Shane E. Powers ◽  
William C. Wood

With the renewed interest in the construction of coal-fired power plants in the United States, there has also been an increased interest in the methodology used to calculate/determine the overall performance of a coal fired power plant. This methodology is detailed in the ASME PTC 46 (1996) Code, which provides an excellent framework for determining the power output and heat rate of coal fired power plants. Unfortunately, the power industry has been slow to adopt this methodology, in part because of the lack of some details in the Code regarding the planning needed to design a performance test program for the determination of coal fired power plant performance. This paper will expand on the ASME PTC 46 (1996) Code by discussing key concepts that need to be addressed when planning an overall plant performance test of a coal fired power plant. The most difficult aspect of calculating coal fired power plant performance is integrating the calculation of boiler performance with the calculation of turbine cycle performance and other balance of plant aspects. If proper planning of the performance test is not performed, the integration of boiler and turbine data will result in a test result that does not accurately reflect the true performance of the overall plant. This planning must start very early in the development of the test program, and be implemented in all stages of the test program design. This paper will address the necessary planning of the test program, including: • Determination of Actual Plant Performance. • Selection of a Test Goal. • Development of the Basic Correction Algorithm. • Designing a Plant Model. • Development of Correction Curves. • Operation of the Power Plant during the Test. All nomenclature in this paper utilizes the ASME PTC 46 definitions for the calculation and correction of plant performance.


Author(s):  
Tomas Gro¨nstedt ◽  
Markus Wallin

Recent work on gas turbine diagnostics based on optimisation techniques advocates two different approaches: 1) Stochastic optimisation, including Genetic Algorithm techniques, for its robustness when optimising objective functions with many local optima and 2) Gradient based methods mainly for their computational efficiency. For smooth and single optimum functions, gradient methods are known to provide superior numerical performance. This paper addresses the key issue for method selection, i.e. whether multiple local optima may occur when the optimisation approach is applied to real engine testing. Two performance test data sets for the RM12 low bypass ratio turbofan engine, powering the Swedish Fighter Gripen, have been analysed. One set of data was recorded during performance testing of a highly degraded engine. This engine has been subjected to Accelerated Mission Testing (AMT) cycles corresponding to more than 4000 hours of run time. The other data set was recorded for a development engine with less than 200 hours of operation. The search for multiple optima was performed starting from more than 100 extreme points. Not a single case of multi-modality was encountered, i.e. one unique solution for each of the two data sets was consistently obtained. The RM12 engine cycle is typical for a modern fighter engine, implying that the obtained results can be transferred to, at least, most low bypass ratio turbofan engines. The paper goes on to describe the numerical difficulties that had to be resolved to obtain efficient and robust performance by the gradient solvers. Ill conditioning and noise may, as illustrated on a model problem, introduce local optima without a correspondence in the gas turbine physics. Numerical methods exploiting the special problem structure represented by a non-linear least squares formulation is given special attention. Finally, a mixed norm allowing for both robustness and numerical efficiency is suggested.


Sign in / Sign up

Export Citation Format

Share Document