Skip to content

Comments

separate annual timeseries from spr series; improve mean_age reporting#609

Merged
Rick-Methot-NOAA merged 5 commits intomainfrom
607-revise-spr_series-in-reportsso-to-clarify
Aug 5, 2024
Merged

separate annual timeseries from spr series; improve mean_age reporting#609
Rick-Methot-NOAA merged 5 commits intomainfrom
607-revise-spr_series-in-reportsso-to-clarify

Conversation

@Rick-Methot-NOAA
Copy link
Collaborator

resolves #607

Information is in the issue.
The annual_time_series table has been separated from the SPR_series table such that only per-recruit values are in the SPR table.
update and check the mean age values
add more notes on each table

Testing can be done with any model.

needs work with r4ss

SS2out << "#_NOTE:_Y/R_unit_is_Dead_Biomass" << endl;
SS2out << "#_NOTE:_gentime_is_mean_age_of_female_spawners_weighted_by_reproductive_value-at-age_(fec(g))" << endl;

SS2out << "Yr Era Bio_all_eq Bio_Smry_eq SSB_unfished_eq SSBfished_eq SSBfished/R SPR Y/R GenTime" << endl;
Copy link
Collaborator

@e-perl-NOAA e-perl-NOAA Jul 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason for the change from YPR to Y/R? It seems like YPR is used most other places.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, but I was striving for consistency with SSB/R. Looked at other instances and agrtee with you, so will change back.

SS2out << "#_NOTE: F_report_basis: " << F_reporting << " # " << F_report_label << endl;
SS2out << "#_NOTE: SPR_report_basis: " << SPR_reporting << " # " << SPR_report_label << endl;
SS2out << "year Era Bio_all_an Bio_Smry_an Num_Smry_an SSB recruits sel_catch_B_an dead_catch_B_an retain_catch_B_an sel_catch_N_an dead_catch_N_an retain_catch_N_an" <<
" dead_catch_B/bio_smry sum_fleet_F F=Z-M M mn_age_SSB mn_age_smry mn_age_catch SPR_std Depletion_std F_std" << endl;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is sum_fleet_F the same as Tot_Exploit?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

different. But that raises topic, which I m considering:
a. should I add a note to describe every cryptic column header?
b. what is preferred format of such notes:

  1. before or after the table
  2. special code to denote that the next line will be start of a table
  3. text uses spaces, or spaces all filled with a character like "_"

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would help. I think before the table perhaps but I'll let @iantaylor-NOAA chime in here. R doesn't love spaces in text or special characters other than "_" or "." so I would avoid those 2 things when it comes to easy compatibility with r4ss.

Is Tot_Exploit under a different column header or is it no longer reported? It's used in r4ss in the get_SIS_info() which is why I am asking.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tot_Exploit got renamed to: dead_catch_B/bio_smry.
I can switch back to Tot_Exploit and put dead_catch_B/bio_smry into a note.

Delimiters: I already was using _ and will continue to do so.

Probably useful to look through the report file and describe all the different formats for notes that exist already. I am especially interested in making it easy for r4ss to know that a line of text is a string of headers.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, great. It's fine the way it is, I just was trying to figure out what it had become.

Copy link
Contributor

@iantaylor-NOAA iantaylor-NOAA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I think having a separate table of annual quantities will be really useful for assessment reports in the future.

One question: the columns labeled SPR_std and F_std in the new table were called SPR_report and F_report in the old table. It looks like the new names match the code, but if there's not a compelling reason for the change, I would switch back to the old names which I think are better aligned with "SPR_report_basis" and "F_report_basis" as well as requiring fewer changes in the r4ss code.

@Rick-Methot-NOAA
Copy link
Collaborator Author

@iantaylor-NOAA - regarding F_report vs. F_std. They refer to the same quantity and both terms are used in various places through the report file, with more for F_std. I will consolidate all usage to F_std which is the name of the array. The term's history is that it is the F quantity for which the standard deviation (std) is produced and reported.

@iantaylor-NOAA
Copy link
Contributor

Makes sense, thank you. Easy enough to adapt.

@Rick-Methot-NOAA Rick-Methot-NOAA merged commit b192b1b into main Aug 5, 2024
@Rick-Methot-NOAA Rick-Methot-NOAA deleted the 607-revise-spr_series-in-reportsso-to-clarify branch August 5, 2024 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

revise SPR_SERIES in Report.sso to separate the per recruit equilibrium quantities into separate table

3 participants