user_interaction_args

internal

Designed for studies where animals tagged with acoustic tags are expected
to move through receiver arrays. This package combines the advantages of automatic sorting and checking
of animal 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>.

Hugo Fl<c3><a1>vio

actel

Acoustic Telemetry Data Analysis

Hugo Flávio

user_interaction_args function

<dl><dt>tag</dt>
<dd>The tag being analysed.</dd>
<dt>detections</dt>
<dd>The detections data.frame for a specific tag.</dd>
<dt>force</dt>
<dd>Logical: If TRUE, the user is moved directly to indicating which movements should be invalidated.</dd>
<dt>trigger</dt>
<dd>The message/warning that triggered the interaction</dd>
<dt>moves, all.moves</dt>
<dd>The complete movements table for a specific tag.</dd>
<dt>displayed.moves</dt>
<dd>The valid movements table for a specific tag.</dd>
<dt>event</dt>
<dd>The event selected for expansion.</dd>
<dt>GUI</dt>
<dd>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".</dd>
<dt>save.tables.locally</dt>
<dd>Logical: If a table must be temporarily stored into a file
for user inspection, should it be saved in the current working directory, or
in R's temporary folder?</dd></dl>

Arguments

user_interaction.R arguments — user_interaction_args

<dl>

<dt>tag</dt>
<dd>The tag being analysed.</dd>


<dt>detections</dt>
<dd>The detections data.frame for a specific tag.</dd>


<dt>force</dt>
<dd>Logical: If TRUE, the user is moved directly to indicating which movements should be invalidated.</dd>


<dt>trigger</dt>
<dd>The message/warning that triggered the interaction</dd>


<dt>moves, all.moves</dt>
<dd>The complete movements table for a specific tag.</dd>


<dt>displayed.moves</dt>
<dd>The valid movements table for a specific tag.</dd>


<dt>event</dt>
<dd>The event selected for expansion.</dd>


<dt>GUI</dt>
<dd>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".</dd>


<dt>save.tables.locally</dt>
<dd>Logical: If a table must be temporarily stored into a file
for user inspection, should it be saved in the current working directory, or
in R's temporary folder?</dd>

</dl>

user_interaction_args: user_interaction.R arguments

Description

Arguments