Please see the following proposal for defining standard outputs from a TAF analysis.
In order to identify standard outputs from stock assessments, we need to define a set of 'output types' and these should belong to a vocabulary
Proposal for new code type:
CodeType: TAFOutputTypes - standard outputs from TAF analyses
Codes:
SAG - file formatted for upload to SAG
ASD - file formatted for upload to ASD
FLStock - RData file containing a single FLStock object
Other potential codes (draft)
RDBESnational
RDBESsummary
An example of usage in a TAF analysis - the user creates a file called ARTIFACTS.json, this file contains an array of outputs, and the creation of the file will be supported by R functions in icesTAF package. The file contains an array of entries with three elements
Each output type will be decorated with metadata, depending on the output type different metadata will be required. We need to manage the definition of output types somewhere. The definition at its simplest can be:
output type definition:
Summary
Please see the following proposal for defining standard outputs from a TAF analysis.
In order to identify standard outputs from stock assessments, we need to define a set of 'output types' and these should belong to a vocabulary
Proposal for new code type: CodeType: TAFOutputTypes - standard outputs from TAF analyses
Codes:
Other potential codes (draft)
An example of usage in a TAF analysis - the user creates a file called ARTIFACTS.json, this file contains an array of outputs, and the creation of the file will be supported by R functions in icesTAF package. The file contains an array of entries with three elements
for example:
Each output type will be decorated with metadata, depending on the output type different metadata will be required. We need to manage the definition of output types somewhere. The definition at its simplest can be: output type definition:
We may also want to add to the definition: