Constructs the fixed-TAC and management-procedure update calendar together with the data years available to each CTP calculation.
Usage
project_ctp_schedule(
first_yr = 2022L,
last_yr = 2035L,
data_last_yr,
fixed_catch_n_years = 4L,
tac_schedule = 3L,
tac_calculation_lag = 2L,
catch_data_lag = 3L,
cpue_data_lag = 3L,
gt_data_lag = 4L,
ckmr_data_lag = 8L
)Arguments
- first_yr, last_yr
First and last projection years.
- data_last_yr
Final year in the historical assessment data.
- fixed_catch_n_years
Number of future years with fixed TAC before CTP.
- tac_schedule
Integer number of years between CTP TAC updates.
- tac_calculation_lag, catch_data_lag, cpue_data_lag, gt_data_lag, ckmr_data_lag
Integer data-availability lags used in the CTP TAC schedule.
Value
A tibble with one row per future TAC year and columns for the
TAC calculation year, data-availability years, and whether the CTP updates
the TAC in that year.
Details
Years, lags, and schedule lengths are expected to be finite
whole-number values with last_yr >= first_yr. The current helper
assumes this contract rather than validating every scalar itself.
See also
Other projection helpers:
extend_hsp_cohorts(),
project_rec_devs(),
project_selectivity(),
run_projections()
Other Cape Town procedure:
run_projections(),
sbt_ctp_controls()
Examples
project_ctp_schedule(
first_yr = 2022L,
last_yr = 2035L,
data_last_yr = 2025L,
fixed_catch_n_years = 4L,
tac_schedule = 3L
)
#> # A tibble: 10 × 8
#> year tac_change tac_calculation_year catch_data_year cpue_data_year
#> <int> <chr> <int> <int> <int>
#> 1 2026 hardwired 2022 NA NA
#> 2 2027 hardwired 2025 2024 2024
#> 3 2028 hardwired NA 2025 2025
#> 4 2029 hardwired NA 2026 2026
#> 5 2030 Yes 2028 2027 2027
#> 6 2031 No NA 2028 2028
#> 7 2032 No NA 2029 2029
#> 8 2033 Yes 2031 2030 2030
#> 9 2034 No NA 2031 2031
#> 10 2035 No NA 2032 2032
#> # ℹ 3 more variables: gt_data_year <int>, ckmr_data_year <int>,
#> # ctp_update <lgl>