Print

Print


In the second paragraph try changing  'stadard' to 'standard'. I hope
this is it. I thought it was a bracket but maybe I was wrong.

Vladimir

On Thu, Mar 19, 2009 at 9:52 PM, Deryk Beal <[log in to unmask]> wrote:
> Hi Vladimir
>
> Thank you very much for the quick response. I have attached two .hc files
> for your information. One is from a continuous dataset and one from an
> epoched one. The files appear to be fine and I can not find a missing
> bracket or other obvious type of punctuation error. Any other suggestions
> for an easy fix?
>
> Cheers,
> Deryk
>
> Deryk Beal, M.HSc., S-LP(C), Reg. CASLPO
> Speech-Language Pathologist
> Doctoral Candidate
> 416-471-3411
> [log in to unmask]
> *************************************************************************
> This email may contain confidential and/or privileged information for the
> sole use of the intended recipient. Any review or distribution by others is
> strictly prohibited. If you have received this email in error, please
> contact the sender and delete all copies. Opinions, conclusions or other
> information expressed or contained in this email are not given or endorsed
> by the sender unless otherwise affirmed independently by the sender.
>
>
> On Thu, Mar 19, 2009 at 5:09 PM, Vladimir Litvak <[log in to unmask]>
> wrote:
>>
>> Dear Deryk,
>>
>> This problem sounds familiar. If I'm right this is a case of buggy
>> data rather than buggy SPM code. The problem comes down to some
>> missing closing bracket in the .hc files (these are ASCII files in
>> your .ds directory). I don't remember the details but perhaps if you
>> examine the files you'll figure it out yourself. This problem is
>> present in some CTF systems with some particular version of CTF
>> software. Since we used CTF toolbox that we prefer not modify and this
>> toolbox generates the error the solution is to fix your .hc file with
>> a text editor and then try again.
>>
>> If this is not enough for you to solve the problem, write again and
>> I'll try to find out more details about what you should fix.
>>
>> Best,
>>
>> Vladimir
>>
>>
>> On Thu, Mar 19, 2009 at 8:47 PM, Deryk Beal <[log in to unmask]> wrote:
>> >
>> > Hello
>> >
>> > I receive similar errors regardless of options entered when trying to
>> > convert MEG data from a CTF-151 unit using SPM8b. I have read the manual
>> > and
>> > I have tried various options within the convert gui but the error
>> > messages
>> > are usually similar to the example below (taken from the Just Read
>> > option).
>> > I am pointing the convert gui to the .meg4 file. The errors output are
>> > as
>> > follows:
>> >
>> > SPM8b: spm_eeg_convert_ui (v2850)                  16:41:02 - 19/03/2009
>> > ========================================================================
>> > readCPersist: Stop strings (EndOfParameters) do not balance start
>> > strings
>> > (WS1_).
>> >               (No. of start strings)-(No. of stop strings)=1.
>> > ??? Index exceeds matrix dimensions.
>> >
>> > Error in ==> C:\Program
>> > Files\MATLAB71\spm8b\external\ctf\readCTFds.p>readHc
>> > at 599
>> >
>> >
>> > Error in ==> C:\Program
>> > Files\MATLAB71\spm8b\external\ctf\readCTFds.p>readCTFds at 203
>> >
>> >
>> > Error in ==> fileio\private\read_header at 673
>> >     orig             = readCTFds(filename);
>> >
>> > Error in ==> fileio_read_header at 11
>> > [varargout{1:nargout}] = funhandle(varargin{:});
>> >
>> > Error in ==> spm_eeg_convert at 70
>> > hdr = fileio_read_header(S.dataset, 'fallback', 'biosig',
>> > 'headerformat',
>> > S.inputformat);
>> >
>> > Error in ==> spm_eeg_convert_ui at 89
>> > D = spm_eeg_convert(S);
>> >
>> > ??? Error while evaluating uicontrol Callback.
>> >
>> > Is there a solution? What am I doing wrong?
>> >
>> > Thanks & cheers,
>> >
>> > Deryk
>> >
>> >
>> > Deryk Beal, M.HSc., S-LP(C), Reg. CASLPO
>> > Speech-Language Pathologist
>> > Doctoral Candidate
>> > [log in to unmask]
>> >
>> > *************************************************************************
>> > This email may contain confidential and/or privileged information for
>> > the
>> > sole use of the intended recipient. Any review or distribution by others
>> > is
>> > strictly prohibited. If you have received this email in error, please
>> > contact the sender and delete all copies. Opinions, conclusions or other
>> > information expressed or contained in this email are not given or
>> > endorsed
>> > by the sender unless otherwise affirmed independently by the sender.
>> >
>
>