View source: R/user_interaction.R
invalidateEvents | R Documentation |
Allow the user to determine a given movement event invalid
invalidateEvents(
displayed.moves,
all.moves,
detections,
tag,
GUI,
save.tables.locally
)
displayed.moves |
The valid movements table for a specific tag. |
detections |
The detections data.frame for a specific tag. |
tag |
The tag being analysed. |
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? |
A data frame with the movement events for the target tag and an updated 'Valid' column.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.