checkJumpDistance | R Documentation |
Check if tags are jumping over arrays
checkJumpDistance(
movements,
tag,
bio,
detections,
spatial,
arrays,
dotmat,
paths,
jump.warning,
jump.error,
GUI,
save.tables.locally,
n
)
movements |
The movements table for a specific tag. |
tag |
The tag being analysed. |
bio |
A table with the tags and biometrics of the studied animals. |
detections |
The detections data.frame for a specific tag. |
spatial |
A list of spatial objects in the study area. |
arrays |
a list containing information for each array. |
dotmat |
The matrix of distances between arrays. |
jump.warning |
If a tag crosses a number of arrays equal or greater
than |
jump.error |
If a tag crosses a number of arrays equal or greater than
|
GUI |
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". |
save.tables.locally |
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? |
n |
A string indicating the overall progress. |
A list of movements with updated 'Valid' columns
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.