You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can work on developing the function for creating the catch table. I imagine that the landings and discards will be able to re-use most of the same code so I can probably add those on after the catch as well.
Catch (D): Recorded by fleet, gear type, sector (as applicable)
Landings (D): Stratified by fleet, gear type, sector (as applicable) with associated uncertainty (as input in assessment model)
Discards (D): Stratified by fleet, gear type, sector (as applicable) with associated uncertainty (as input in assessment model)
To clarify, @Schiano-NOAA when you say stratified by fleet/gear/sector/etc. does that just mean have columns with those variables or separate tables by each grouping?
The text was updated successfully, but these errors were encountered:
@MOshima-PIFSC This sounds great! In regards to the stratification, yes that's exactly what I was thinking. Here is an example from the SEFSC that I kind of thought it would be broken down (with landings and discards in their own tables):
I do want to make our slightly different, but this is kind of the inspo for these tables.
In case this information is useful, for west coast groundfish, in the past we have typically reported the commercial landings and recreational mortality at a finer level of stratification than the fleet structure in the model, such as in the first figure below from the 2021 lingcod north stock assessment report where the modeled fleets are aggregated across the three states:
On the other hand we've often provided less detail in tables on estimated discards than what's represented in the model (here discards are only included in the total catch column which aggregates discards from two commercial fleets, and only from the most recent years).
I think a table that provides landings and discards as represented in the model as suggested by @MOshima-PIFSC would be fine.
I can work on developing the function for creating the catch table. I imagine that the landings and discards will be able to re-use most of the same code so I can probably add those on after the catch as well.
To clarify, @Schiano-NOAA when you say stratified by fleet/gear/sector/etc. does that just mean have columns with those variables or separate tables by each grouping?
The text was updated successfully, but these errors were encountered: