ViSiElse (version 1.0.1)

ViSiElse: ViSiElse: A visual tool for behaviour analysis

Description

VisiElse is a graphical tool designed to visualize and to give an overview of behavioural observations realized on individuals or groups. For example, ViSiElse allows visualization of raw data during experimental observations of the realization of a procedure like a medical algorithm. It graphically presents an overview of individuals and group actions usually acquired from timestamps during video recorded sessions. Options of the package allow adding graphical information as statistical indicators (mean, standard deviation, quantiles or statistical tests) but also for each action green or black zones providing visual information about the accuracy of the realized actions.

Principal

ViSiElse concerns behavioural processes that, like a simulated healthcare procedure, can be decomposed in actions. We define two different types of actions in ViSiElse: punctual and long. The actions called punctual are brief actions defined as a time points. They does not last enough to be measured on the chosen time scale. The actions called long are the ones defined by duration. They are characterized by both a beginning punctual action and an ending one. In order to model a procedure, there is a need to sort actions in the way they are supposed to be realized as defined for example by medical consensus and/or algorithms for a medical procedure. This structure is stored in a S4-class object ViSibook, it can be modified, printed or plotted.

S4-methods

This Package contains two S4class of object: ViSibook and ViSigrid. Basically a ViSibook object will store information on a process like a health care procedure, then a ViSigrid object is built with observations of this procedure and the procedure ViSibook, and finally the graphic is optained by plotting this ViSigrid object.

ViSibook-class

The minimum stucture for a ViSibook must give for each action its name (without special characters but"_"), its label, and its type (punctual or long). For a long action, in addition it is necessary to provide the two specific actions that defined its starting and ending. The order by which actions are supposed to happen is also required. It is possible to not attribute a rank order at some actions, but not all. This is useful in the case of a procedure focuses on a long action but does not on punctual actions defining its end or beginning thus those two punctual actions can have an order not set. Beyond the minimum structure green zones or/and black zones can be defined to help to visualize if a behaviour is realized on time. Black zones can be defined on both punctual and long action but green zones can only be defined on punctual actions. To get the details see the definition of the class ViSibook.

ViSiGrid-class

A ViSigrid object is built using the function buildViSiGrid with at least :

• The procedure structure: It is stored in a ViSibook object.
• Observations : Dataset which stores individuals realisation times for each punctal action.

Options can be add like group, indicator,... see buildViSiGrid and ViSigrid to get more details explanations. At the end the plot of a ViSigrid object provides a graphics of the realisation of a process.