Difference between revisions of "Batch Processing"

Revision as of 16:40, 8 April 2016

BESA batches allow you to automate nearly all analysis steps in BESA

The batch functionality that you find under the “Process” menu has been around for a while. Over the past few years, the toolkit that is available there has grown to an impressive size, such that with BESA Research 6.0, virtually all analysis steps can be automated, and applied to a list of files. At any point in time, the batch can also be halted to make parameter adjustments, should this be necessary. A complete analysis from pre-filtering, artifact scanning, averaging, source analysis, and export of results for subsequent statistical analysis, can be summarized in few steps. For many recurring tasks, ready-made batches are available already – and batches can also be assigned to function keys for maximum ease of use.

The set of available commands is shown below – sub-divided into

• general commands which allow e.g. loops, error handling, or pausing the batch for user input
• commands affecting the main program including ERP management
• commands for discrete source analysis
• commands for distributed source analysis
• time-frequency commands

For example, to automate averaging and to prepare data for statistical analysis, using an experimental paradigm for a number of subjects, a batch could have the following elements:

• Load the paradigm
• Perform an artifact scan
• Average the conditions
• Export the data of each condition for further analysis with BESA Statistics

In batch code, this will look like the following:

To add any command, e.g. “Average”, select the command from the list of commands and check the options dialog that appears:

Left side: Select a command from the list. Right side: AFter selecting, a dialog opens where command options can be defined.

Once the batch is complete, it can run over all open files, over a user-defined file list (simply drag files into the list from Explorer), or just over the current file. Note that these batches are produced without entering any line of code by hand – it is all done using the graphical user interface of the Batch dialog.

An example batch for Averaging step by step

The first two commands will load the paradigm file and perform the artifact scan: Paradigm(%Scripts%\Paradigm\Auditory\AEP_Intensity.PDG) ArtifactScan(Wait)

The next command will average over the conditions: Average(%basename%_av, %Examples%\ERP-Auditory-Intensity\Averages\, NoDefaultName,OverwriteTarget, NoCorrect)