Skip to content

location for ss3 items #46

Description

@BenWilliams-NOAA

catch_to_ss3 <- function(year, se = 0.01, season = 7, fleet=1, yld_rat = NULL){

@mkapur-noaa I'm leaning toward this type of function not being in afscdata, but placing it in afscassess.
Couple of reasons:

  1. The data query function should produce the same data for every assessment, if this gets implemented at the start then data format will start off different between different assessments,
  2. There is a clean_catch function in afscassess, I think having a clean_catch_ss function or age_comp_ss, etc. would be a method for maintaining consistent code structures
    Thoughts?

Edit: looking at this function further, I would strongly suggest not using this method to include/not include the proj catch data that produces the same output file name - it seems to inevitably get messed up in the plotting/report arenas

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions