Conversation
Added NRT template
Added place holder sections.
added ArgosQC config details - start
made small updates to the preamble and corrected some typos.
jdpye
left a comment
There was a problem hiding this comment.
I think we should add a section more focused on 'What the data manager does with the software' but the optimal format for that can come from the DACs who review this lesson
jdpye
left a comment
There was a problem hiding this comment.
ready for review by DAC folks I believe.
|
Had a read through, v cool work. Immediate thoughts:
|
| ## NRT data and NRT data sources | ||
| 1. Near Real-Time data are transmitted by satellite-linked electronic tags, when animals are at the ocean surface, via the Argos satellite constellation. | ||
|
|
||
| 2. Currently, the ArgosQC R package can access & download NRT data from two animal tag manufacturers - SMRU (Sea Mammal Research Unit, St Andrews, UK) and Wildlife Computers. Typically, NRT data are downloaded & QC'd once every 24 hours until tag deployments have ended (e.g., due to tag battery failure, or animal recapture). SMRU tag data are made available on a [server with a Web Application Firewall](https://www.smru.st-andrews.ac.uk/protected/technical.html), which requires a user ID and password (provided to the tag owner) to access the tag data files (stored in a `.mdb` file). Once a node manager has access to a tag owner's user ID and password, SMRU tag `.mdb` files can be download via ArgosQC. Wildlife Computers tag data are accessed via a [Data Portal](https://my.wildlifecomputers.com/), which requires both a user account (with user ID and password) to access the Portal AND explicit consent by tag owner(s) to share their tag data (set up by the tag owner on the Data Portal). Details on accessing tag data via the Wildlife Computers Portal are [here](https://static.wildlifecomputers.com/Portal-and-Tag-Agent-User-Guide-2.pdf). Once a user account is set up by the node manager and explicit data sharing is set up by the tag owner, data can be downloaded by ArgosQC via the Wildlife Computers API. |
There was a problem hiding this comment.
spelling error: Once a node manager has access to a tag owner's user ID and password, SMRU tag .mdb files can be download via ArgosQC. make it downloaded
|
|
||
| ## ArgosQC workflow and features | ||
| 1. ArgosQC workflows are intended to be run automatically via a scheduler and require minimal supervision. Separate workflows are provided for SMRU and Wildlife Computers tags. Both require the node manager to set up a JSON configuration file that specifies all required project information and QC parameters. In general, both workflows do the following: | ||
| - Downloads specified tag data from the tag Manufacturer |
There was a problem hiding this comment.
why is Manufacturer capitalized
| - Downloads specified tag data from the tag Manufacturer | ||
| - Acquires any available deployment metadata from the tag Manufacturer & builds an operational deployment metadata file, or ingests a specified metadata file (CSV). | ||
| - Prepares tag location data for state-space model (SSM) fitting | ||
| - Fits the SSM in 2 passes to each tag location dataset. SSM fitting to multiple tag datasets is conducted in parallel across n available processors. |
There was a problem hiding this comment.
across n available processors.
- what is supposed to be where it says n
There was a problem hiding this comment.
n is meant to represent a number, but in text we could instead be saying 'across a number of available processors'
There was a problem hiding this comment.
fixed with the suggested, 'across a number of available processors'
|
The gang says: "I think this is the why, the lesson, which is really important, but the how isn't covered yet. It's important context, but now we need the reference on how to do the work, with task lists, what do we do first, next, to the end." broadly - How do we:
|
No description provided.