Batch Processing - Revision history

Abinash: Redirected page to BESA Research Batch Processing

2021-05-05T15:46:57Z

Redirected page to BESA Research Batch Processing

Abinash at 14:02, 5 May 2021

2021-05-05T14:02:39Z

Jaehyun at 13:16, 24 May 2017

2017-05-24T13:16:46Z

Harald at 14:52, 8 April 2016

2016-04-08T14:52:24Z

Harald at 14:49, 8 April 2016

2016-04-08T14:49:09Z

Harald at 14:40, 8 April 2016

2016-04-08T14:40:23Z

Harald: Created page with "{{BESAInfobox |title = Module information |module = BESA Research Basic or higher |version = 5.2 or higher }} == BESA batches allow you to automate nearly all analysis steps..."

2016-04-08T14:26:45Z

Created page with "{{BESAInfobox |title = Module information |module = BESA Research Basic or higher |version = 5.2 or higher }} == BESA batches allow you to automate nearly all analysis steps..."

New page

{{BESAInfobox
|title = Module information
|module = BESA Research Basic or higher
|version = 5.2 or higher
}}

== 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
[[File:BatchMenu.jpg|none|left]]
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:
[[File:BatchExample.png|none|left]]
To add any command, e.g. “Average”, select the command from the list of commands and check the options dialog that appears:
[[File:BatchExampleAv.png|700px|thumb|left|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. An example is shown below. 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.

← Older revision		Revision as of 15:46, 5 May 2021
Line 1:		Line 1:
		+	#REDIRECT [[BESA Research Batch Processing]]
		+
	{{BESAInfobox		{{BESAInfobox
	\|title = Module information		\|title = Module information

@@ Line 2: / Line 2: @@
 |title = Module information
 |module = BESA Research Basic or higher
-|version = 5.2 or higher
+|version = BESA Research 5.2 or higher
 }}
@@ Line 72: / Line 73: @@
 Of course, many more options are available – check it out! For example, segments can automatically be sent to Source Analysis to perform automated imaging and export these results for further analysis, too.
 [[Category:ERP/ERF]]

@@ Line 14: / Line 14: @@
 *commands for distributed source analysis
 *time-frequency commands
 [[File:BatchMenu.jpg|none|left]]
 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
@@ Line 22: / Line 26: @@
 In batch code, this will look like the following:
 [[File:BatchExample.png|none|left]]
 To add any command, e.g. “Average”, select the command from the list of commands and check the options dialog that appears:
 [[File:BatchExampleAv.png|700px|none|left]]
 Left side: First click the "Add Command" button. Then 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:
-<tt>
+<pre>
 Paradigm(%Scripts%\Paradigm\Auditory\AEP_Intensity.PDG)
 ArtifactScan(Wait)
-</tt>
+</pre>
 [[File:BatchArtScan.png|500px|none|left]]
 The next command will average over the conditions:
-<tt>
+<pre>
 Average(%basename%_av, %Examples%\ERP-Auditory-Intensity\Averages\, NoDefaultName,OverwriteTarget, NoCorrect)
-</tt>
+</pre>
 [[File:BatchExampleAv2.png|500px|none|left]]
 The next commands will loop over the first 5 segments (condition averages) and export them to different ASCII files to be used in further processing in BESA Statistics or other programs:
 GENFor(segm, 1, 5, 1, 1)
 MAINMarkBlock(WholeSegment,-,%segm%)
 MAINExport(%basename%-export%segm%, \, Segment, ASCvec, Original, FiltOff, NoResample, Replace, -, )
 GENEndFor()
-</tt>
+</pre>
 [[File:BatchExampleAv3.png|500px|none|left]]
 Of course, many more options are available – check it out! For example, segments can automatically be sent to Source Analysis to perform automated imaging and export these results for further analysis, too.

@@ Line 36: / Line 36: @@
 ArtifactScan(Wait)
 </tt>
-[[File:BatchArtScan.png|500px|left]]
+[[File:BatchArtScan.png|500px|none|left]]
 The next command will average over the conditions:
@@ Line 42: / Line 42: @@
 Average(%basename%_av, %Examples%\ERP-Auditory-Intensity\Averages\, NoDefaultName,OverwriteTarget, NoCorrect)
 </tt>
-[[File:BatchExampleAv2.png|500px|left]]
+[[File:BatchExampleAv2.png|500px|none|left]]
 The next commands will loop over the first 5 segments (condition averages) and export them to different ASCII files to be used in further processing in BESA Statistics or other programs:
@@ Line 56: / Line 56: @@
 GENEndFor()
 </tt>
-[[File:BatchExampleAv3.png|500px|left]]
+[[File:BatchExampleAv3.png|500px|none|left]]
 Of course, many more options are available – check it out! For example, segments can automatically be sent to Source Analysis to perform automated imaging and export these results for further analysis, too.
 More information on how to create batches can be found on our web site in [ftp://www.besa.de/be/besa.de/demonstrations_and_tutorials/BESA%20Research%20Tutorial%203%20-%20Batch%20Scripts%20-%20Multiple%20Subjects+Conditions%20-%20MATLAB%20interface.pdf Tutorial on Batch Scripts] – browse to section B.

@@ Line 24: / Line 24: @@
 [[File:BatchExample.png|none|left]]
 To add any command, e.g. “Average”, select the command from the list of commands and check the options dialog that appears:
-[[File:BatchExampleAv.png|700px|thumb|left|Left side: Select a command from the list. Right side: AFter selecting, a dialog opens where command options can be defined.]]
+[[File:BatchExampleAv.png|700px|none|left]]
 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:
 <tt>
 Paradigm(%Scripts%\Paradigm\Auditory\AEP_Intensity.PDG)
 ArtifactScan(Wait)
 </tt>
-[[File:BatchArtScan.png|none|left]]
+[[File:BatchArtScan.png|500px|left]]
 The next command will average over the conditions:
 <tt>
 Average(%basename%_av, %Examples%\ERP-Auditory-Intensity\Averages\, NoDefaultName,OverwriteTarget, NoCorrect)
 </tt>
-[[File:BatchExampleAv2.png|none|left]]
+[[File:BatchExampleAv2.png|500px|left]]

← Older revision		Revision as of 14:40, 8 April 2016
Line 26:		Line 26:
	[[File:BatchExampleAv.png\|700px\|thumb\|left\|Left side: Select a command from the list. Right side: AFter selecting, a dialog opens where command options can be defined.]]		[[File:BatchExampleAv.png\|700px\|thumb\|left\|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~~. An example is shown below~~. 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.	+	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:
		+	<tt>
		+	Paradigm(%Scripts%\Paradigm\Auditory\AEP_Intensity.PDG)
		+	ArtifactScan(Wait)
		+	</tt>
		+	[[File:BatchArtScan.png\|none\|left]]
		+	The next command will average over the conditions:
		+	<tt>
		+	Average(%basename%_av, %Examples%\ERP-Auditory-Intensity\Averages\, NoDefaultName,OverwriteTarget, NoCorrect)
		+	</tt>
		+	[[File:BatchExampleAv2.png\|none\|left]]