Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development Prioritization: Tables #1

Open
1 of 17 tasks
Schiano-NOAA opened this issue Jul 9, 2024 · 0 comments
Open
1 of 17 tasks

Development Prioritization: Tables #1

Schiano-NOAA opened this issue Jul 9, 2024 · 0 comments
Assignees
Labels
development Documenting aspects that need to be added into the repo enhancement New feature or request

Comments

@Schiano-NOAA
Copy link
Collaborator

Schiano-NOAA commented Jul 9, 2024

Coding in Tables

Each of the proposed tables in the list below will be coded in as function in the R folder.

Determining Rank

The tables and figures proposed and reviewed by the steering committee were prioritized based on the number of votes they each table or figure received. The different between positive and negative votes determined rank. Objects with a difference above 3 were categorized as P1. Below 3 but equal to or greater than 0 were designated as P2, and anything below a zero was designated as parking lot. Objects ranked at 3 were decided either to be P1 or P2 depending on comments and the developers expertise. Objects within the rank were listed in descending order of difference and objects with the same value were placed in order based on developer expertise.

The proposed list of tables and figures can be found here.
*Note: Only NOAA internal employees can access this document.

Guide:

  • P1: revived the highest amount of votes from the steering committee and are incorporated into almost every stock assessment used for management advice. Will be added for first release
  • P2: medium priority items that are important but can pushed a little bit later in development. Aimed for being added at second release
  • “Parking lot”: lowest priority for development; will be coded eventually; received lowest amount of votes/negative votes

( ) = category
D = data
ES = executive summary
AM = assessment mode
P = projections

High Priority (P1)

  • Indices of abundance (D)
  • Projection time series (ES): From base model or avg of ensemble models; includes other metrics such as exploitation rate (u), B, SB, and recruitment R0
  • Derived quantities (AM): could include: Bcurr, Fcurr, MSST, MFMT, Ftarg, Btarg, M, Rcurr, R0, h, SB
  • Sensitivity runs (P): Future (5-10 years) for year, catch, biomass, SB, R, F, F/Fmsy proxy, and/or B/Bmsy proxy
  • Biomass/Abundance time series (AM): Estimated B, N, and C from model year start to terminal year

Medium Priority (P2)

  • Estimated parameters (AM): Could include: life history, catchability, selectivity; retention, spawning-recruitment, recruitment deviations
  • Landings (D): Stratified by fleet, gear type, sector (as applicable) with associated uncertainty (as input in assessment model)
  • Catch (D): Recorded by fleet, gear type, sector (as applicable)
  • Discards (D): Stratified by fleet, gear type, sector (as applicable) with associated uncertainty (as input in assessment model)
  • Life history parameters (AM): M, growth, M/K ratio, maturity, fecundity, W/L conversion, total length to fork length, discard mortality rate
  • F per fleet per year (AM)

Lowest Priority (parking lot)

  • Estimated parameters (AM): Could include: life history, catchability, selectivity; retention, spawning-recruitment, recruitment deviations
  • Landings (D): Stratified by fleet, gear type, sector (as applicable) with associated uncertainty (as input in assessment model)
  • Catch (D): Recorded by fleet, gear type, sector (as applicable)
  • Discards (D): Stratified by fleet, gear type, sector (as applicable) with associated uncertainty (as input in assessment model)
  • Life history parameters (AM): M, growth, M/K ratio, maturity, fecundity, W/L conversion, total length to fork length, discard mortality rate
  • F per fleet per year (AM)
@Schiano-NOAA Schiano-NOAA added enhancement New feature or request development Documenting aspects that need to be added into the repo labels Jul 9, 2024
@Schiano-NOAA Schiano-NOAA self-assigned this Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Documenting aspects that need to be added into the repo enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant