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

Figure of decision tables #1152

Open
kellijohnson-NOAA opened this issue Feb 17, 2024 · 2 comments
Open

Figure of decision tables #1152

kellijohnson-NOAA opened this issue Feb 17, 2024 · 2 comments

Comments

@kellijohnson-NOAA
Copy link
Collaborator

The U.S. JTC members were provided with a suggestion to show the results of the decision table in figure format as well as the current table to help people with interpolation between the forecasts.

... ways to display the projections as graphs. As you know, the interpolations between
the values you run through the model are tight fits. 2025 status on y axis and 2024 catch on x axis.

I suggested that we CANNOT run a GAM or other models to interpolate but we might be able to just use lines between the points in a figure that could be presented to the JMC. I suggested that it NOT go in the assessment document because we already have the information in a table. I am not sure what you all think about this.

@cgrandin
Copy link
Collaborator

I don't mind. But they will ask for it to go into the assessment once they get used to using it... you know that right :)

Notes for later: Here's the best way to do it I think, in case the table changes in the future -
Have the table_decisions() function generate a data frame with generalized names. It would then return a two-element list, element 1 being the kbl() output and element 2 being the data frame. Change calls to the function in ES and main tables section to insert list item 1 instead of the full object returned and pass list item 2 to the plotting function.

@andrew-edwards
Copy link
Collaborator

By 'status' they mean the range of relative spawning biomass yes?
So that is already shown in Figure j for some catch values, though not in the way they're asking. They can just interpolate from the table to get more 'exact' values.
Not totally against it, and I get how it might help, but I feel the info is already there. Also, they might want then ask for three figures (one for each future catch year).

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

No branches or pull requests

3 participants