hugomflavio / actel

Standardised analysis of acoustic telemetry data from fish moving through receiver arrays
https://hugomflavio.github.io/actel-website
26 stars 6 forks source link

Allow receiver re-deployment at different location #7

Closed hugomflavio closed 5 years ago

hugomflavio commented 5 years ago

Quick notes on tasks involved:

  1. Remove "Receiver" column from spatial.csv
  2. Add new input file with deployments, containing one row per receiver deployment/retrieval Tentative columns:
    • Serial - Same as Receiver
    • Station.Name - Must match between the deployments and spatial
    • Timestamp - Time of the action (will act similarly to start and end.timestamp)
    • Type - factor: "Deployed" or "Retrieved"
  3. Create a combined receiver-deployment name for receivers deployed at different stations
  4. Use the deployment date to search through the detection and replace the receiver name
  5. Internally formulate a new internal link between arrays and the receivers

From this point, actel should be able to resume the current workflow.

hugomflavio commented 5 years ago

Going for "Receiver", "Station.Name", "Start" and "Stop" as columns instead.

hugomflavio commented 5 years ago

New functions explore and migrate are now running with deployments. The 'actel' function is still active and disregards deployments. A new message is displayed urging users to change to the 'migration' function asap. An helper function was also introduced to automatically create deployments for old studies which have been previously analysed by actel: updateStudy()