LoginSign Up
← Back to all sparks
Q

qcTAF

ANALYTICS
Velocity0.0

TAF Checks

github.com/ices-tools-prod/qcTAF ↗

qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time

rreproducibilityfisheriesquality controlicestaf
◆Current state
qcTAF performs quality control on TAF (Transparent Assessment Framework) analyses, the workflow standard used for ICES fisheries stock assessments. It launched in February 2026 with eight checking functions and a README listing ten criteria that define a complete TAF analysis. Three releases followed within four months, all adding checks or tightening existing ones.
◆Where it's heading
Each release converts more of the informal completeness checklist into executable checks. February added relative-path and script-existence checks; late February added data and software declaration checks plus two new completeness criteria covering initial-versus-boot data identity and DATA.bib declarations; May added qc.any.scripts.exist() and made qc.only.relative.paths() treat /home/ as absolute. Function naming is being revised as the set grows, with renames in every release so far.
◆Prediction
With the naming churn ongoing and criteria still being added, the next release most likely continues both. The package appears to be tracking a moving definition of TAF completeness rather than a fixed spec.

◆Recent moves

  1. 2mo ago

    qc.any.scripts.exist() added; /home/ now treated as an absolute path

    Adds qc.any.scripts.exist() alongside the existing all-scripts check, renaming two functions to make the all-versus-any distinction explicit. The path checker now flags /home/ as absolute, closing a gap where a hardcoded home directory passed as relative — exactly the kind of non-portable path TAF quality control exists to catch.

    View source ↗
  2. 5mo ago

    Data and software declaration checks; two new completeness criteria

    Adds qc.data.declared(), qc.software.declared() and qc.initial.data(), plus two criteria for TAF completeness: initial data and boot data must be identical, and files in boot/data must be declared in DATA.bib. Renames two bib functions from 'entries' to 'processed'. The criteria list itself is growing, not just the checks against it.

    View source ↗
  3. 5mo ago

    Relative path and script existence checks

    Adds qc.relative.paths() and qc.scripts.exist(), the first checks to look at the analysis's file layout rather than its bibliography. Both were renamed three months later as the naming scheme settled.

    View source ↗
  4. 5mo ago

    Initial release with eight TAF quality-control checks

    The package's first release, with eight functions checking for boot directories and the existence, validity and entries of DATA.bib and SOFTWARE.bib. The README's ten criteria for a complete TAF analysis set the roadmap that every release since has been working through.

    View source ↗