Difference: DocsSectionsLoopTick (3 vs. 4)

Revision 410 Jan 2012 - Main.PhilipVanDenBroek

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Looptick functions

Changed:
<
<
In parallel mode, it is possible to use looptick functions. Looptick functions are while-loops running at a client. The advantage of looptick functions is that the behavior of the loop can be modified from the BrainStream side.
>
>
In parallel mode, it is possible to use looptick functions. Looptick functions will be put in a while-loop running at a client. The advantage of looptick functions is that the behavior of the loop can be modified from the BrainStream side.
 

Defining looptick functions

Structure of looptick functions

Line: 64 to 64
 On the client side, the user variables that were sent from BrainStream can be received with the function
varargout = bs_recv_user_brainstream(event, client_nickname)
Changed:
<
<
So, you can start each call to the looptick function with checking if there is new information from the BrainStream side. For example, if you do your classification on the BrainStream side, your classification function might send a variable 'classified' when it has made a reliable estimate about which stimulus a subject is attending to. If the looptick function receives this variable, it means that the stimulus presentation can be stopped, so the stoploop variable can be set to 1 and the looptick function will end. In this way, actions at a client can be influenced by information from the BrainStream side.
>
>
So, you can start each call to the looptick function with checking if there is new information from the BrainStream side. This way, stimulus presentation can adapt itself to the current classified results. For example, your classification function (running on the BrainStream side) might send information about which stimulus a subject is attending to. The looptick function might respond to it by shortening, changing or even end the stimulus presentation sequence. In the latter case, the stoploop variable can be set to 1 and the looptick function will end. In this way, actions at a client can be influenced by information from the BrainStream side.
 

Example

An example of a looptick function is described in Part 5 of the Visual Speller example.

 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback