NEFSC / READ-EDAB-neusAtlantis

https://github.com/NEFSC/READ-EDAB-neusAtlantis/wiki
https://github.com/NEFSC/READ-EDAB-neusAtlantis/wiki
Other
5 stars 0 forks source link

Parameterize Scallop fleet #246

Closed andybeet closed 2 months ago

andybeet commented 7 months ago

Test case: Parameterize Scallop fleet using effort whilst another single fleet usesforced catch

Forced effort

time series file similar to the total_catch.ts file

  1. How to integrate the two forcing file data? How does that work? Forced catch for some species, forced effort for others. Can you simply omit species from from the catch.ts file and add them to an effort ts file (as long as the meta data describes this)?

    • Yes, but better option is to zero out catch in forcing file for SCA and zero out all effort in effort file for all other fleets
    • Global effort.ts was not available as an option, only box specific effort ts files had been coded for. The branch AtlantisImposedEffort has been created off 6681 to allow for global effort

      The new parameter per fishery is XXXX_imposeeffort (Where XXXX is the fishery code)

      0 = No imposed effort 1 = Global effort (single time series file) 2 = Spatial effort (per box)

      You also need to add the parameter flagimpose_effort_hdistrib. This only has an effect if you pick impose global effort. 0 = CPUE based allocation (on day 1 only uses effort_hdistrib per fishery) 1 = Imposed effort uses effort_hdistrib per fishery to do the spatial allocation 2 = Imposed effort uses effort_hdistrib and the relative distribution of the biomass of the fishery’s target species

  2. Box specific forcing of effort by fleet. Requires 30 ts files all formatted similarly. Also need to include metadata in the forcing.prm file

    • Scripts made to create and manipulate these files
  3. Can you force catch, for Scallop, for part of the time, say first 20 yrs, then use effort after some time point? Would this just involve including Scallop in both files? If not then just have constant effort as part of the time series over initial period of the run.

    • Yes, i think so, Zero out effort in effort file for early years and zero out catch in latter years. Need to check this by looking at catch by fleet output. However to do this you'd need to double the number of fleets and define one to be effort based the other forced catch. Doubles effort. Better to just use constant effort over initial period, although no guarentee catch will be constant since it will depend on abundance and age structure +
  4. Alternatively use contant effort through time with seasonal scalars (parameters in the harvest flle, no forcing). This is limiting and prevents lookng at scenarios with changes in effort through time based on things like management or climate

NOTE:: Current state - we can not currently run the model with a single global forcing file (segmentation error) until we update the version with the code updates The model currently can not handle a single forced effort file (like catch), it has to be box specific effort. As an alternative we are resorting to constant total effort

Harvest equation (in atlantis terms)

Harvest = Effort YYY_sweptarea f(selcurve_YYY,sel_XXX) management_scalar (vertical overlap positional availability) g(habitat overlap, q_XXX) * Biomass (1-p(escapement) )

where escapement = h(flagesacpement_XXX, p_escape_XXX ,ka_escape_XXX ,kb_escape_XXX) Effort is a forced time series we supply, either total effort or box level effort (effortmodel=11) or Effort is fixed (effortmodel = 9) where catch is proportional to population density (biomass)

Parameter changes

Effort

Alternative: effortmodel =9. Fixed total effort

Catch

Selectivity & Catchability

NOTE: from 15.4 It might be easier to track the fishing outcomes if catchability or escapement are modified one at a time. So, for example, the catchability can be set to 1, but escapement can be set to a different age or length specific proportion. Alternatively, the user might want no escapement and modify the available biomass through catchability only. Finally, the simplest option would include no escapement and 100% catchability; then the available biomass of the target and bycatch species of fishery YYY, in the swept volume of the cell, would only be limited by the fishery’s gear selectivity.

Escapement

Currently, provisions made for escapement but all fisheries set to No escapement

Management scalars

With these settings the Harvest should collapse to something like:

Harvest = Effort 0.1 Biomass

Therefore included estimated Effort in forcing file Effort = 10*Harvest/Biomass

Calibration tips

  1. Estimate effort from data and keep fixed in box.ts files
  2. YYY_sweptarea to get in ball park
  3. q_XXX and sel_XXX to fine tune (using selcurve_YYY = 2 (logistic))
  4. Turn on fleet of interest, turn off others using YYY_tStart
andybeet commented 2 months ago

added most of this to atlantiscas vignette