Open BenWilliams-NOAA opened 9 months ago
I'm OK with this approach; I think I opted for it since I wasn't loving maintenance/pushes to two separate packages. I know @careymcgilliard had talked about sitting down to develop generalized SS3 munging scripts but not sure where she is at with respect to this package vs gapindex
(vs overall bandwidth).
In any case, I don't plan on adding any further SS3-style scripts to this package. So, if you feel strongly about migrating it to afscassess
just let me know.
https://github.com/afsc-assessments/afscdata/blob/54852bea4dae5a404b7559854a9cc3c37b7075d7/R/utils.R#L222
@mkapur-noaa I'm leaning toward this type of function not being in
afscdata
, but placing it inafscassess
. Couple of reasons:clean_catch
function inafscassess
, I think having aclean_catch_ss
function orage_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