Mk10 (-AF) Programming Summary

Histogram Data

Histogram Data sampling interval
  ~ 10 seconds
Dive Maximum Depth (m)
  ~ 14 bins:    10;30;50;70;90;100;150;200;250;300;400;500;600;>600
Dive Duration (min)
  ~ 14 bins:    1;2;3;4;6;8;10;12;16;20;30;40;50;>50
Time-at-Temperature (C) 
  ~ disabled
Time-at-Depth (m)
  ~ 14 bins:    4;10;30;50;70;90;100;150;200;250;300;400;500;>500
20-min time-line
  ~ disabled
Hourly % time-line (low resolution)
  ~ enabled
Hourly % time-line (high resolution)
  ~ disabled
Light-level locations
  ~ disabled

Histogram Collection

Hours of data summarized in each histogram
  ~ 6
Histograms start at
  ~ GMT 03:00

Dive & Timeline Definition

Depth reading to determine start and end of dive
  ~ Wet/Dry (Mk10)
  ~ 2m (Mk20-A)
Ignore dives shallower than 
  ~ 4m
Ignore dives shorter than
  ~ 1 min
Depth threshold for timelines
  ~ Wet/Dry
Haulout Definition
  ~ A minute is "dry" if Wet/Dry sensor is dry for any **30** seconds in a minute
  ~ Enter haulout state after **5** consecutive dry minutes
  ~ Exit haulout state if wet for any **50** seconds in a minute

Argos Transmissions

Transmission Hours
  ~ 0-23
Transmission Days
  ~ All Days
Transmission Monhts
  ~ All Months
Daily Transmission Cap
  ~ 250 Transmissions

Fast-GPS Settings

Fast-GPS sampling interval
  ~ 360 minutes
Deployment Latitude
  ~ 66.75 degrees
Deployment Longitude
  ~ -163 degrees
Deployment Altitude
  ~ 0 m
Transmit hours
  ~ 0 - 23
Fast-GPS Collection Days
  ~ January 4, 8, 12, 16, 20, 24, 28
  ~ February    1, 5, 9, 13, 17, 21, 25
  ~ March   1, 5, 9, 13, 17, 21, 25, 29
  ~ April   2, 6, 10, 14, 18, 22, 26, 30
  ~ May 4, 8, 12, 16, 20, 24, 28
  ~ June    1, 5, 9, 10, 14, 18, 22, 26, 30
  ~ July    4, 8, 12, 16, 20, 24, 28
  ~ August  1, 5, 9, 13, 17, 21, 25, 29
  ~ September   2, 6, 10, 14, 18, 22, 26, 30
  ~ October 4, 8, 12, 16, 20, 24, 28
  ~ November    1, 5, 9, 13, 17, 21, 25, 29
  ~ December    3, 7, 11, 15, 19, 23, 27, 31

Fast-GPS Control

Maximum successful Fast-GPS attempts
  ~ 1 per hour; 4 per day
Maximum failed Fast-GPS attempts
  ~ 3 per hour
Overall maximum Fast-GPS attempts
  ~ 12 per day
Supress Fast-GPS after good haulout location
  ~ enabled

SPOT5 Programming Summary

Argos Transmissions

Unused transmissions will be added to the next day's allowance.
Maximum transmissions per day
  ~ 150
Transmit on these hours
  ~ 1 - 4, 20 - 23
  ~ Tag will transmit during all of the hours before midnight on the first day of deployment
Transmit on these days, using an absolute calendar
  ~ Jan: 1, 15, 
  ~ Feb: 1, 7, 13, 19, 25, 
  ~ Mar: 1, 7, 13, 19, 25, 31
  ~ Apr: 6, 12, 18, 24, 30
  ~ May: 6, 12, 18, 24, 30, 
  ~ Jun: 6, 12, 18, 24, 30
  ~ Jul: 6, 12, 18, 24, 30, 
  ~ Aug: 1, 15, 
  ~ Sep: 1, 15, 
  ~ Oct: 1, 15, 
  ~ Nov: 1, 15, 
  ~ Dec: 1, 15, 

Time at temperature histograms **are not collected**
Percent dry timelines **are being collected**

deployid

• An alphanumeric string that uniquely identifies the deployment.

  Since a deployment is a unqiue combination of animal and tag, the deployid is a concatenation of the animal id (speno) and the tag serial number (serialnum).

  By examining the deployid, one can discern several key details about the particular deployment. The first two characters in the deployid will specify the species of animal the tag was deployed on. These letters correspond to the genus and species (e.g. bearded seals (Erignathus barbatus) would be represented by EB). The next four characters represent the year the deployment started. The next section is separated by an underscore and is a unique number assigned to the animal. The first 11 characters in the deployid correspond to the speno for the deployment animal. The next section (also separated by an underscore) corresponds to the serial number for the tag.

ptt

• The Argos transmitter (PTT) identifier.

  It is important to understand that a PTT identifier can be assigned to different tags over the years. The PTT identifier should not be considered a unique identifier.

instr

• An alphanumeric string that identifies the make/model class of the tag

  [1] "Mk10" "SPOT"

  Mk10

  Argos location tags with additional sensors for recording depth/dive behavior, temperature, conductivity. For this project, Mk10 tags were adhered to the hair of the seal on the head.

  SPOT

  Argos location tags with conductivity. No pressure transducer for recording depth or dive behavior. For this project, SPOT tags were attached to the rear flipper.

date_time

• A POSIXct value representing the UTC time for the location estimate.

  [1] "2009-06-23 02:41:12 UTC" "2014-05-24 03:18:02 UTC"

  Due to the nature of Argos data that is still not fully understood, there can be more than one record with the the same date_time value for the same deployment. See unique_posix for an adjusted value with no duplicate times.

type

• An character string that specifies the location estimate is based on the Argos process

  [1] "Argos"

quality

• An alphanumeric value cooresponding to the Argos location quality.

  [1] "A" "B" "3" "1" "0" "2" "Z"

  Argos location estimates were traditionally classified with a quality value that provides general guidelines regarding the error associated with the location estimates. From better to worse, the possible values are 3, 2, 1,0,A,B, and Z. Z values should be removed from any analysis and are only included here for completeness.

  In recent years, Argos has provided better estimates of error using their Kalman filter algorithm. See error_radius, error_semimajor_axis, error_semiminor_axis, and error_ellipse_orientation.

latitude, longitude

• Coordinates (decimal degrees, datum=WGS84) of the location estimate

error_radius, error_semimajor_axis, error_semiminor_axis,error_ellipse_orientation

• Error parameters provided as part of the Kalman filter algorithm

unique_posix

• The same as date_time except duplicate values have been eliminated by increasing the value of one duplicate by 1 second.

deployid

• An alphanumeric string that uniquely identifies the deployment.

  Since a deployment is a unqiue combination of animal and tag, the deployid is a concatenation of the animal id (speno) and the tag serial number (serialnum).

  By examining the deployid, one can discern several key details about the particular deployment. The first two characters in the deployid will specify the species of animal the tag was deployed on. These letters correspond to the genus and species (e.g. bearded seals (Erignathus barbatus) would be represented by EB). The next four characters represent the year the deployment started. The next section is separated by an underscore and is a unique number assigned to the animal. The first 11 characters in the deployid correspond to the speno for the deployment animal. The next section (also separated by an underscore) corresponds to the serial number for the tag.

count

time_offset

locnumber

hauled_out

• a binary (1,0) indication whether the tag was in haul-out mode at the time the fastloc snapshot was captured

satellites

• total number of satellites captured in the snapshot. substract the number of bad_sats to get the total number of viable satellites

initlat, initlon

• Coordinates (decimal degrees, datum=WGS84) of the seed location used

inittime

• A POSIXct value representing the UTC time for the seed location used

inittype

• the source data for the seed coordinates: GPS, User or an letter corresponding to the Argos satellite

latitude, longitude

• Coordinates (decimal degrees, datum=WGS84) of the location estimate

bad_sats

• number of satellites with poor information in the snapshot and not usable

residual

time_error

date_time

• A POSIXct value representing the UTC time for the fastloc location estimate.

  [1] "2009-06-26 00:00:10 UTC" "2010-04-18 12:00:00 UTC"

deployid

• An alphanumeric string that uniquely identifies the deployment.

  Since a deployment is a unqiue combination of animal and tag, the deployid is a concatenation of the animal id (speno) and the tag serial number (serialnum).

  By examining the deployid, one can discern several key details about the particular deployment. The first two characters in the deployid will specify the species of animal the tag was deployed on. These letters correspond to the genus and species (e.g. bearded seals (Erignathus barbatus) would be represented by EB). The next four characters represent the year the deployment started. The next section is separated by an underscore and is a unique number assigned to the animal. The first 11 characters in the deployid correspond to the speno for the deployment animal. The next section (also separated by an underscore) corresponds to the serial number for the tag.

datadatetime

• A POSIXct value representing the UTC time for the start of the time bin.

  Dive behavior is summarized into user specified time bins. In this study, 6 hour bins were chosen.

num_dives

• The number of dives with a max depth that occured during the corresponding time period and within the corresponding depth bin. This value is capped at 255. Thus, in cases when the actual number of dives exceeds 255 some scaling occurs.

bin

• The bin label in the original data files provided by Wildlife Computers

limits

• The upper (numerically, not in the water column) limit of the depth bin in meters.

  The limits are determined from examining the data files provided from the Wildife Computers Data Portal. If the user has properly specified the programming schema for this deployment, those values are extracted and included in the data frame for easy reference.

deployid

• An alphanumeric string that uniquely identifies the deployment.

  Since a deployment is a unqiue combination of animal and tag, the deployid is a concatenation of the animal id (speno) and the tag serial number (serialnum).

  By examining the deployid, one can discern several key details about the particular deployment. The first two characters in the deployid will specify the species of animal the tag was deployed on. These letters correspond to the genus and species (e.g. bearded seals (Erignathus barbatus) would be represented by EB). The next four characters represent the year the deployment started. The next section is separated by an underscore and is a unique number assigned to the animal. The first 11 characters in the deployid correspond to the speno for the deployment animal. The next section (also separated by an underscore) corresponds to the serial number for the tag.

datadatetime

• A POSIXct value representing the UTC time for the start of the time bin.

  Dive behavior is summarized into user specified time bins. In this study, 6 hour bins were chosen.

num_dives

• The number of dives with a duration (seconds) that occured during the corresponding time period and within the corresponding duration bin. This value is capped at 255. Thus, in cases when the actual number of dives exceeds 255 some scaling occurs.

bin

• The bin label in the original data files provided by Wildlife Computers

limits

• The upper limit of the duration bin in seconds.

  The limits are determined from examining the data files provided from the Wildife Computers Data Portal. If the user has properly specified the programming schema for this deployment, those values are extracted and included in the data frame for easy reference.

deployid

• An alphanumeric string that uniquely identifies the deployment.

  Since a deployment is a unqiue combination of animal and tag, the deployid is a concatenation of the animal id (speno) and the tag serial number (serialnum).

  By examining the deployid, one can discern several key details about the particular deployment. The first two characters in the deployid will specify the species of animal the tag was deployed on. These letters correspond to the genus and species (e.g. bearded seals (Erignathus barbatus) would be represented by EB). The next four characters represent the year the deployment started. The next section is separated by an underscore and is a unique number assigned to the animal. The first 11 characters in the deployid correspond to the speno for the deployment animal. The next section (also separated by an underscore) corresponds to the serial number for the tag.

datadatetime

• A POSIXct value representing the UTC time for the start of the time bin.

  Dive behavior is summarized into user specified time bins. In this study, 6 hour bins were chosen.

pct_tad

• Percent time-at-depth represents the percentage of time the tag spent within the corresponding depth bin. Values across the depth bins for a given 6 hour time period should add to approximately 100.

bin

• The bin label in the original data files provided by Wildlife Computers

limits

• The upper (numerically, not in the water column) limit of the dive depth bin in meters

  The limits are determined from examining the data files provided from the Wildife Computers Data Portal. If the user has properly specified the programming schema for this deployment, those values are extracted and included in the data frame for easy reference.

deployid

• An alphanumeric string that uniquely identifies the deployment.

  Since a deployment is a unqiue combination of animal and tag, the deployid is a concatenation of the animal id (speno) and the tag serial number (serialnum).

  By examining the deployid, one can discern several key details about the particular deployment. The first two characters in the deployid will specify the species of animal the tag was deployed on. These letters correspond to the genus and species (e.g. bearded seals (Erignathus barbatus) would be represented by EB). The next four characters represent the year the deployment started. The next section is separated by an underscore and is a unique number assigned to the animal. The first 11 characters in the deployid correspond to the speno for the deployment animal. The next section (also separated by an underscore) corresponds to the serial number for the tag.

datadatetime

• A POSIXct value representing the UTC time for the start of the hour bin.

  Percent timeline data is summarized into hourly time bins.

percent_dry

• A percentage of the given hour the tag was dry (out of the water)

  Possible values include: 0,3,5,,10,20,30,40,50,60,70,80, 90,95,97, and 100