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

Workflow · Changes

Page history
fixing diagram authored Sep 15, 2020 by Beatriz Recinos's avatar Beatriz Recinos
Hide whitespace changes
Inline Side-by-side
Showing with 3 additions and 3 deletions
+3 -3
  • Workflow.md Workflow.md +3 -3
  • No files found.
Workflow.md
View page @ 713d1177
......@@ -50,11 +50,11 @@ A1[rscripts]
id4 --> id5[(ICOADS SHIP data)]
id5 --> |process_ships.R|id6[Reformat selected ship IDs to homogenize <br> information between DCKs. <br> Uses IDs from Pub. 47 metadata <br> in ID prioritisation. <br> Corrects dates & times.]
id6 --> |get_pairs.R|id7[Groups ship reports as potential duplicates <br> if the contents match within tolerance]
id7 --> |get_dups.R|id8[Assesses the groups of potential duplicates, <br> accepting those where the ID match is appropriate. <br> Reports from DCK that are of lower quality, <br>or that are less complete, or that fail the <br> track check are flagged as the worst.]
id7 --> |get_dups.R|id8[Assesses the groups of potential duplicates, <br> accepting those where the ID match is appropriate.<br> Reports from DCK that are of lower quality, <br> or that are less complete, or that fail the <br> track check are flagged as the worst.]
id8 --> |merge_ids_year.R|id9[Assesses IDs that have been associated <br> in previous processing to decide whether to replace <br> all IDs in the associated group with the preferred ID.]
id9 --> |nrt_dup.R|id10[Process near-real-time data collected after 2014.]
id10 --> |clean_data.R|id11[Runs track checking on data to produce <br>clean tracks for all IDs.]
id11 --> |clean2track.R|id12[Selects data for ship-tracking software <br>Carella et al. 2017,<br> choosing only data with missing or generic IDs.]
id10 --> |clean_data.R|id11[Runs track checking on data to produce <br> clean tracks for all IDs.]
id11 --> |clean2track.R|id12[Selects data for ship-tracking software Carella et al. 2017,<br> choosing only data with missing or generic IDs.]
id12 --> id13[(Output data)]
classDef pre-processing fill:#fcc679,stroke:#333,stroke-width:1px,font-size:16px,font-weight:100,text-align:center
......
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