13 Matching Annotations
  1. Last 7 days
    1. Expected fixes per tag: 2.2326^{4} locations over the deployment period Storage check: 2.2326^{4} fixes per tag, well within the 1,900,000 fix storage limi

      Unclear + error

    2. Beyond visually validating the residency assumption, we can infer the data with movement model selections to verify the assumption:

      Wrong place - Should be above the plots. Here should be: We infer the data with several model and run a model selection to see whether individuals are residential or vagrants

    3. Depending on our knowledge related to the species and its system, we might subjectively filter individuals.

      Wrong place - Should be just above the next code chunk

  2. Mar 2026
    1. 43.1

      For example, BTG has been detected 43.1% during diurnal high tide, overall at the array level.

      At Curlew point, the species has been detected 65.5% during diurnal high tide, overall at the station level.

      If we were wondering where the species is detected the most during nocturnal high tide, we would look at the highest value for the corresponding tide col. and find Tomago (78%)

    2. Detection per Tide Category (%)

      By getting the ratio to percentage, we get rid of the limitiaion brough by raw hours added to each other across stations, so we can compare proportions of detection vs. survey effort period accross stations.

    3. Hours per Tide Category

      These survey effort numbers (right side of the "/") can't be compared between each other because we are adding hours and hours of survey effort for the same dates accross stations.

    4. 508 / 72875 (0.7 %) 69 / 18152 (0.4 %) 198 / 18171 (1.1 %) 22 / 18252 (0.1 %) 219 / 18300 (1.2 %)

      Percentage values are not very helpful here because this hour additivity limitation, again.