z-logo
Premium
Robust Regression Approach to Estimating Fish Mortality Rates with a Cohort‐Based Model
Author(s) -
Chen Y.,
Paloheimo J. E.
Publication year - 1994
Publication title -
transactions of the american fisheries society
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.696
H-Index - 86
eISSN - 1548-8659
pISSN - 0002-8487
DOI - 10.1577/1548-8659(1994)123<0508:rratef>2.3.co;2
Subject(s) - statistics , mathematics , outlier , robust regression , pairwise comparison , mean squared error , least trimmed squares , least squares function approximation , weighting , linear regression , generalized least squares , regression , ordinary least squares , total least squares , estimator , medicine , radiology
Natural mortality rate ( M ) and fishing catchability coefficient ( q ) were estimated by using the Paloheimo pairwise linear regression model with simulated and real catch–effort data. The four estimation methods used were least squares (LS), least absolute value (LAV), least median of squares (LMS), and LMS‐based reweighted least squares (RLS). When catch or effort data or both contained homogeneous error variances, mean squared errors (MSE) of LS and RLS were significantly smaller than those of LAV and LMS. However, there was no significant difference in MSE between LS and RLS. When catch–effort data contained variances inconsistent among years, MSEs of the robust methods were much smaller than those of LS. Reweighted least squares substantially reduced the variances in the LS‐estimated q and M , and it had the smallest MSE among the four estimation methods. We suggest using the following procedures in estimating q and M based on the Paloheimo pairwise regression model: (1) applying LMS to the model to identify outliers in the data; and (2) weighting the defined outliers by a factor of 0 and normal data points by a factor of 1 and applying LS to the model to estimate q and M and their associated variances.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here