Terminology and Organization

An experiment is defined in EMGworks as a test configuration.  The test configuration includes the hardware used (including sensors, and A/D cards), any calibrations, and the experimental workflow for the experiment.  The protocol is specified as a series of customized task templates, where each template defines what sensors are used, how they are plotted for the operator and the subject, and any real time processing, as well as any task-specific settings.  Tasks can relate to each other, such as a MVC task which determines the normalization for subsequent tasks.

A given test configuration can be run many times.  Each test run is associated with two users: an operator and a subject.  As the tasks in the configuration are run, data is grouped in a set run for each task.  If the task is run repeatedly, this data will be groups in a rep run within the set.  It is possible to skip tasks in the protocol or repeat them while doing a test run.  In addition to the data, each set also contains additional information about normalization parameters and other task-specific information.

Some tasks, such as the signal quality test task, run in a preview mode where the data is automatically deleted from the disk soon after it is collected.  This is useful for viewing EMG signals to verify quality before performing an experiment.

Users have an identity which determines if they are operators or subjects.  Each user can also store general information about the person as well as a subject.