z-logo
Premium
Tag Reporting Rate Estimation: 3. Use of Planted Tags in One Component of a Multiple‐Component Fishery
Author(s) -
Hearn William S.,
Hoenig John M.,
Pollock Kenneth H.,
Hepworth Daniel A.
Publication year - 2003
Publication title -
north american journal of fisheries management
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.587
H-Index - 72
eISSN - 1548-8675
pISSN - 0275-5947
DOI - 10.1577/1548-8675(2003)023<0066:trreuo>2.0.co;2
Subject(s) - component (thermodynamics) , fishing , fishery , estimation , fish <actinopterygii> , environmental science , statistics , econometrics , biology , mathematics , economics , physics , management , thermodynamics
Tag return models are used to estimate survival and tag recovery rates. With additional information on tag reporting rates, one can separate the survival rate into its fishing and natural mortality rate components. One method of estimating the tag reporting rate is to secretly plant tags in fishers' catches. However, if the fishery has more than one component, it may not be possible to plant tags in all components. Nevertheless, it is possible to estimate the reporting rates of all components in a multiple‐component fishery and the fishing and natural mortality rates, if at least one component has a known reporting rate and the catches are known for each component. We simulate a variety of tag return experiments in which tags are planted in one component of a multicomponent fishery. The simulations show that this method is most effective (i.e., provides good precision of parameter estimates) when a sufficient number of tagged fish are planted into a fishery component with a high reporting rate and with a high proportion of the total catch. It is also advantageous to encourage the reporting of tags in the fishery components without planted tags. We provide a method for testing various model assumptions when it is possible to plant tags in more than one component.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here