add Report.sso files to repo?

[iantaylor-NOAA]

The discussion with @Schiano-NOAA at nmfs-ost/stockplotr#185 makes me think that it would be helpful to add the Report.sso files for all of the test models in this repo so that they could be read directly by stockplotr (or r4ss) without having to be run locally or in a github action.

The drawback would be that the files would take up more space, and changes across versions might take more work to explore. If we continue to exclude the CompReport.sso and covar.sso files the file sizes won't grow too much, and it's possible that seeing the differences between Report.sso files when we update to a new version might be helpful in some cases.

@e-perl-NOAA, what do you think?

[Rick-Methot-NOAA]

There are some rather useless tables in report.sso that could be excluded using the custom report feature.

[e-perl-NOAA]

Yeah, I'm fine adding the report file! Does stockplotr (and r4ss) need every table in the report file or is it fine to remove some of the tables that aren't used?

[iantaylor-NOAA]

@e-perl-NOAA and @Rick-Methot-NOAA, good points about being able to reduce the tables.
However, I think it's probably safer to just output the full set of tables rather than try to figure out which ones could be omitted without missing useful information. The average user isn't likely to have custom output so it's probably better to train our output processing tools on the full report as well.

[e-perl-NOAA]

@iantaylor-NOAA, honestly that's what I thought. Also, in terms of the test models, there is a whole comparison that goes on with values in the summary.sso file between versions. Do either of you think that there are values in the report file that aren't in the sumarry.sso file that need to go through a similar comparison?

[Rick-Methot-NOAA]

The basic report file already omits many tables as shown in the section: #_KeyWords_of_tables_available_in_report_sso

There may already be an issue for making adjustments to what goes into the basic report. I agree that it may already be good enough to include all that is there.

ss_summary.sso does not contain everything that messes up r4ss and the tests that use it do not compare everything, so having whole report files available does seem useful. However, when debugging, I just grab the old exe and reproduce the old report files anyway.