Procedure to get an assessment into TAF

Well, unless you are the assessment coordinator :)

Files might be found in the Sharepoint Data folder.
Earlier WG reports can be found online.

Being able to run the assessment on a different computer is an important milestone in making the analysis reproducible.

This is a good time to open and view
(a) the input & output files, and
(b) the last WG report, especially the table section
Do the tables in (a) and (b) look similar?

What kinds of data are used in this assessment, perhaps more than one survey?
Are some data tables in the report not in the model input, or vice versa?
Are the model settings stored in a separate file?
Is it easy to find out which input files the model requires?

In general, TAF should only contain files that are absolutely necessary to run the final assessment.
- all other files are probably best stored outside of TAF
- data files should include all available years and ages, which can be truncated (e.g. in a plus group) in the data script
What is the smallest set of files required to run the final assessment on another computer?

The easiest way to import data into R depends on the data file format:
- simple text files can often be imported using base functions like read.table
- specific file formats can be imported using packages like stockassessment or FLCore

Some preprocessing of data often occurs before they are fed into a model:
- years or ages might be excluded from the analysis
- ages might be aggregated into a plus group
- survey indices might be combined, the current year’s weights predicted, etc.
The data should preferably start in disaggregated form (see ‘Mission Y’ below).

Data that are used in the assessment model should be written as TAF data files in the data folder.
- the icesTAF package provides the function write.taf for this purpose
- write both full datasets (all ages, all years) and truncated datasets, e.g. plus group in catch-at-age as catage_full.csv and catage.csv
Ideally, the TAF data files are the only files necessary for the input.R script, but sometimes it’s practical to write additional files in the data folder that are not in the TAF file format.

The model input is data in the format that the model requires, for example:
- text files such as input.dat with many tables, or
- input.RData with many R objects
Ideally, input.R should read the TAF data files created by data.R and create the model input from that, thus guaranteeing that the TAF data files are indeed the data that the model uses.
Sometimes it’s practical to have the input.R script read/copy/move files that are not in the TAF file format.
The input files, containing data in model-specific format, are written in the input folder, ready for the next step.

In TAF, stock assessment models are either run as:
- R packages, such as stockassessment and FLR, or
- executables, such as ADMB or Fortran applications
R package models return the results into the R session, and those results can be written out as results.RData inside the model folder.
Executable models can be run using the R function system and the output files are stored inside the model folder.
Model settings are sometimes stored in files, especially in the case of executable models.