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

WKREF1 propose all TAF stock assessment repos produce an FLStock object #55

Open
colinpmillar opened this issue Nov 5, 2021 · 5 comments
Assignees
Labels
level: TAF-team detailed day to day issues Priority: High

Comments

@colinpmillar
Copy link
Contributor

colinpmillar commented Nov 5, 2021

Including reference points.

@Milldaz
Copy link

Milldaz commented Jan 28, 2022

Full recommendation:
Within TAF, it is recommended to generate FLStock objects of all final assessments with the attributes that were provided by WKREF1. In cases where probabilistic statements are already included in the advice, the FLR object should also contain the associated uncertainty. This could also be used to test the impact of assessment uncertainty on e.g. estimates of FP.05, and potentially to include it in its estimation.

@nilsolav
Copy link
Collaborator

Dave will get in touch with the WKREF and see what code are available for this task.

@iagomosqueira
Copy link
Collaborator

For any assessment being run in FLR (FLSAM, FLXSA, FLa4a) the FLStock object is already there. For SS3 there is an FLR package (https://github.com/flr/ss3om) to load output and create an FLStock.

I have just coded a function to do it directly from SAM output and input. Not sure where this could go.

What other methods are we missing?

@iagomosqueira
Copy link
Collaborator

For the attributes, we will be adding them to an extended class soon, so we will prioritize this.

@iagomosqueira
Copy link
Collaborator

Need to get a list of models being used that do not yet have an specific function to output to FLStock. Probably to do so via a data.frame output

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level: TAF-team detailed day to day issues Priority: High
Projects
Status: To Be Organised
Status: No status
Development

No branches or pull requests

5 participants