diff --git a/docs/SS330_User_Manual_release.html b/docs/SS330_User_Manual_release.html index 98c9967b..b569595a 100644 --- a/docs/SS330_User_Manual_release.html +++ b/docs/SS330_User_Manual_release.html @@ -1642,209 +1642,204 @@

-1 = do abbreviated U.S. West Coast rebuilder output; and +1 = do abbreviated U.S. West Coast rebuilder output -2 = do extended U.S. West Coast rebuilder output. - - - - Rebuilder catch (Year Declared): Input line is required even if Rebuilder = 0, specified in the line above. - + >0 = year first catch should be set to zero; and - + -1 = set to 1999. - + 2004 Rebuilder start year (Year Initial): Input line is required even if Rebuilder = 0, specified two line above. - + >0 = year for current age structure; and - + -1 = set to end year +1. - + 1 Fleet Relative F: - + 1 = use first-last allocation year; and - + 2 = read season(row) x fleet (column) set below. - + 2 Basis for maximum forecast catch: The maximum basis for forecasted catch will be implemented for the for the "First year for caps and allocations" selected above. The maximum catch (biomass or numbers) by fleet is specified below on the "Maximum total forecast catch by fleet" line. - + 2 = total catch biomass; - + 3 = retained catch biomass; - + 5 = total catch numbers; and - + 6 = retained total numbers. - + COND 2: Conditional input for fleet relative F (Enter: Season, Fleet, Relative F) - + 1 1 0.6 Fleet allocation by relative F fraction. The fraction of the forecast F value. For a multiple area model user must define a fraction for each fleet and each area. The total fractions must sum to one over all fleets and areas. - + 1 2 0.4 - + -9999 0 0 Terminator line - + 1 50 Maximum total forecast catch by fleet (in units specified above total catch/numbers, retained catch/numbers) Enter fleet number and its maximum value. Last line of the entry must have fleet number = -9999. - + -9999 -1 - + -9999 -1 Maximum total catch by area Enter area number and its max. Last line of the entry must have area number = -9999. - + -1 = no maximum - + 1 1 Fleet assignment to allocation group Enter list of fleet number and its allocation group number if it is in a group. Last line of the entry must have fleet number = -9999. - + -9999 -1 - + COND: if N allocation groups is >0 Enter a year and the allocation fraction to each group for that year. SS3 will fill those values to the end of the forecast, then read another year from this list. Terminate with -9999 in year field. Annual values are rescaled to sum to 1.0. - + 2002 1 Allocation to each group for each year of the forecast - + -9999 1 - + -1 Basis for forecast catch: The dead or retained value in the forecast catch inputs will be interpreted in terms of numbers or biomass based on the units of the input catch for each fleet. - + -1 = Read basis with each observation, allows for a mixture of dead, retained, or F basis by different fleets for the fixed catches below; - + 2 = Dead catch (retained + discarded); - + 3 = Retained catch; and - + 99 = Input apical F (the apical F value for the model years can be found in the EXPLOITATION section in the Report file). - + COND: == -1 Forecasted catches - enter one line per number of fixed forecast year catch - + 2012 1 1 1200 2 Year & Season & Fleet & Catch or F value & Basis - + 2013 1 1 1400 3 Year & Season & Fleet & Catch or F value & Basis - + -9999 0 0 0 0 Indicates end of inputted catches to read - + - + COND: > 0 Forecasted catches - enter one line per number of fixed forecast year catch - + 2012 1 1 1200 Year & Season & Fleet & Catch or F value - + 2013 1 1 1200 Year & Season & Fleet & Catch or F value - + -9999 0 0 0 Indicates end of inputted catches to read - + 999 End of Input @@ -3822,7 +3817,9 @@

7.20.

  • The transition matrix can depend upon weight-at-length which differs between sexes and can vary seasonally. Thus, the transition matrix is calculated internally for each sex and each season.

    • 7.21 Tag-Recapture Data

    -

    The ability to analyze tag-recapture data is available with SS3. Each released tag group is characterized by an area, time, sex and age at release. Each recapture event is characterized by a time and fleet. Fleets operate in only one area so it is not necessary to record the area of recapture. Fleets with tagging data needed to be specified as fishing fleets (e.g., fleet type 1 or 2)). Inside the model, the tagged cohort is apportioned across all growth patterns in a given area at a given time (with options to apportion to only one sex or to both). The tag cohort by growth pattern then behaves according to the movement and mortality of the growth pattern. The number of tagged fish is modeled as a negligible fraction of the total population. This means that a tagging event does not move fish from an untagged group to a tagged group. Instead, it acts as if the tags are seeded into the population with no impact at all on the total population abundance or mortality. The choice to require assignment of a predominant age at release for each tag group is a pragmatic coding and model efficiency choice. By assigning a tag group to a single age, rather than distributing it across all possible ages according to the size composition of the release group, it can be tracked as a single diagonal cohort through the age x time matrix with minimal overhead to the rest of the model. Tags are assumed to be released at the beginning of a season and recaptures follow the timing of the fleet that made the recapture.

    +

    Each released tag group is characterized by an area, time, sex and age at release. Each recapture event is characterized by a time and fleet (since fleets operate in only one area, it is not necessary to specify the area of recapture). Fleets with tagging data must be fishing fleets (e.g., fleet type 1 or 2).

    +

    Inside the model, the tagged cohort is apportioned across all growth patterns in a given area at a given time (with options to apportion to only one sex or to both). The tag cohort by growth pattern then behaves according to the movement and mortality of the growth pattern. The number of tagged fish is modeled as a negligible fraction of the total population, so a tagging event does not move fish from an untagged group to a tagged group. Instead, tagged fish are seeded into the population with no impact at all on the total population abundance or mortality.

    +

    Predominant age at release for each tag group must be assigned; this requirement keeps SS3 efficient. By assigning a tag group to a single age rather than distributing it across all possible ages according to the size composition of the release group, the tag group can be tracked as a single cohort through the age by time matrix with minimal overhead to the rest of the model. Tags are released at the beginning of a season and recaptures follow the timing of the fleet that made the recapture.

    @@ -3834,41 +3831,59 @@

    - + - + + + + + + - + - + - + - + - + - + - + + + + + + + + + + + + + + @@ -4018,7 +4033,8 @@

    7.21.

    • The release data must be entered in tag group order.

    • <tfill> values are place holders and are replaced by program generated values for model time.

      • -

    • Analysis of the tag-recapture data has one negative log likelihood component for the distribution of recaptures across areas and another negative log likelihood component for the decay of tag recaptures from a group over time, hence informative about mortality. More on this is in the control file.

      • +

    • Analysis of the tag-recapture data has one negative log likelihood component for the distribution of recaptures across areas and another negative log likelihood component for the decay of tag recaptures from a group over time. Note the decay of tag recaptures from a group over time suggests information about mortality is available in the tag-recapture data. More on this is in the control file documentation.

      • +

    • Do tags option 2 adds an additional input compared to do tags option 1, minimum recaptures. Minimum recaptures allows the user to exclude tag groups that have few recaptures after the mixing period from the likelihood. This may be useful when few tags from a group have been recaptured as an alternative to manually removing the groups with these low numbers of recaptured tags from the tagging data.

    • Warning for earlier versions of SS3: A shortcoming in the recapture calculations when also using Pope’s F approach was identified and corrected in version 3.30.14.

    7.22 Stock (Morph) Composition Data

    @@ -8747,6 +8763,9 @@

    + +

    8.10 Tag Recapture Parameters

    Specify if tagging data are being used:

    1 Do tags - if this value is 0, then omit all entries below.Do tags - 0/1/2. If this value is 0, then omit all entries below.
    COND = 1 All subsequent tag-recapture entries must be omitted if "Do Tags" = 0If value is 2, read 1 additional input.
    COND > 0 All subsequent tag-recapture entries must be omitted if "Do Tags" = 0
    3 Number of tag groups
    7 Number of recapture events
    2Mixing latency period: N periods to delay before comparingMixing latency period: N periods to delay before comparing observed
    observed to expected recoveries (0 = release period)to expected recoveries (0 = release period).
    10 Max periods (seasons) to track recoveries, after which tags enter
    accumulator
    COND = 2
    2Minimum recaptures. The number of recaptures >= mixperiod must be
    >= min tags recaptured specified to include tag group in log likelihood
    Release Data