tableInteraction

moves

fish

The message/warning that triggered the interaction

trigger

One of "needed", "always" or "never". If "needed", a new window is
opened to inspect the movements only if the movements table is too big to be
displayed in R's console. If "always", a graphical interface is always created
when the possibility to invalidate events emerges. If "never", a graphical
interface is never invoked. In this case, if the table to be displayed does
not fit in R's console, a temporary file will be saved and the user will be
prompted to open and examine that file. Defaults to "needed".

Logical: If TRUE, the user is moved directly to indicating which movements should be invalidated.

force

Handler for table interaction events

internal

Designed for studies where fish tagged with acoustic tags are expected
to move through receiver arrays. This package combines the advantages of automatic sorting and checking
of fish movements with the possibility for user intervention on tags that deviate from expected
behaviour. The three analysis functions (explore(), migration() and residency())
allow the users to analyse their data in a systematic way, making it easy to compare results from
different studies.
CJS calculations are based on Perry et al. (2012) <https://www.researchgate.net/publication/256443823_Using_mark-recapture_models_to_estimate_survival_from_telemetry_data>.

tableInteraction: Handler for table interaction events

Description

Usage

Arguments

Value