Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
I ICOADS R HOSTACE
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • brivas
  • ICOADS R HOSTACE
  • Wiki
    • Workflow
  • Quality control

Quality control · Changes

Page history
added links to technical report authored Jun 11, 2020 by bearecinos's avatar bearecinos
Show whitespace changes
Inline Side-by-side
Showing with 3 additions and 6 deletions
+3 -6
  • Workflow/Quality-control.md Workflow/Quality-control.md +3 -6
  • No files found.
Workflow/Quality-control.md
View page @ d88c54c9
......@@ -13,19 +13,16 @@ A precision criteria on selected variables is used to perform a
climatological quality control on the data.
The precision criteria for each key variable per `dck`,
year and/or `sid` can be found [here]() (**Need to add a link to the prec_file**).
year and/or `sid` can be found in Table 5 of the [technical report]().
Having a precision criteria not only preforms quality control on the data but helps to set tolerances when comparing variables from suspected duplicates.
A comparison of climatological variables allows for a match between reports in the duplicate identification procedure.
**(Needs liking to a script)**
A comparison of climatological variables allows for a match between reports in the [duplicate identification](Workflow/duplicate-indentification) procedure done by [`new_get_pairs.R`](https://git.noc.ac.uk/brecinosrivas/icoads-r-hostace/-/blob/master/rscripts/new_get_pairs.R).
**Met Office track check**
-----------------------------------
Several `dck` have `id`'s that indicate a logbook, sheet or other block of data that can be linked together to form ship tracks.
The linked `id`'s are checked using the Met Office Quality Control track check (MOQC track check from [IMMA](https://git.noc.ac.uk/brecinosrivas/icoads-r-hostace/-/wikis/How-to-install#install-dependencies-with-conda-all-platforms)) as well as for time duplicates.
Reports that fail the track check are flag as the worst duplicate. Where positions (lat, lon) are similar the best duplicate is select by `dck` priority and number of quality variables found by the climatological check.
\ No newline at end of file
Reports that fail the track check are flag as the worst duplicate. Where positions (lat, lon) are similar the best duplicate is select by `dck` priority and number of quality variables found by the climatological check. The track check is also perform in the same [`new_get_pairs.R`](https://git.noc.ac.uk/brecinosrivas/icoads-r-hostace/-/blob/master/rscripts/new_get_pairs.R) script.
\ No newline at end of file
Clone repository

Wiki pages

Home

Introduction
Installation
JASMIN tips

Workflow
- Data selection
- Processing of ID's
- Matching criteria
- Quality control
- Duplicate identification

API Reference

Releases

Examples