Error in block-reading function

[corscheid]

Hi goodshawn12,

I'm using the setup I posted in Issue #5 as a workaround for that Issue, and with no other modification of this REST repository. When running unmodified test_script.m, I see the Pipeline and then REST windows open, but the REST window does not function at all, nor show any data. I was wondering if this may have something to do with the fast stream of error messages that appear in the command window while test_script is running.

Command Window output:

...
Error in block-reading function:
 Too many input arguments.
 occurred in: 
   lslin/read_data: 27
   append_data: 86
   @(timer_handle,varargin)append_data(stream_name,stream_id,timer_handle,block_reader): 0
   timercb: 34
   timercb: 24

Error in block-reading function:
 Too many input arguments.
 occurred in: 
   lslin/read_data: 27
   append_data: 86
   @(timer_handle,varargin)append_data(stream_name,stream_id,timer_handle,block_reader): 0
   timercb: 34
   timercb: 24

Error in block-reading function:
 Too many input arguments.
 occurred in: 
   lslin/read_data: 27
   append_data: 86
   @(timer_handle,varargin)append_data(stream_name,stream_id,timer_handle,block_reader): 0
   timercb: 34
   timercb: 24

Error in block-reading function:
 Too many input arguments.
 occurred in: 
   lslin/read_data: 27
   append_data: 86
   @(timer_handle,varargin)append_data(stream_name,stream_id,timer_handle,block_reader): 0
   timercb: 34
   timercb: 24

Error in block-reading function:
 Too many input arguments.
 occurred in: 
   lslin/read_data: 27
   append_data: 86
   @(timer_handle,varargin)append_data(stream_name,stream_id,timer_handle,block_reader): 0
   timercb: 34
   timercb: 24
...

and it seems to repeat like this uncountable times.

Any ideas what is going on here?

[goodshawn12]

@corscheid This seems to be a LSL and/or BCILAB compatibility issue. I found the discussion of this issue here: sccn/BCILAB#7
The source of the problem could be that "lsl_inlet class has been updated at some point and this function now only requires a single argument". You can try his workaround solution.

[corscheid]

@goodshawn12 Thanks so much for this! I followed that suggestion by syedahmar in sccn/BCILAB#7 by going into REST/functions/lslin.m and changing line 27
from
data_clock = inlet.time_correction([], 'median', 30);
to
data_clock = inlet.time_correction();
and the test_script works beautifully now.

My next step is to use the Emotiv portion of the test_script to work with an Emotiv EPOCH headset on LSL.