Dear Kambiz,
checkmeeg messages usually do not indicate a problem. checkmeeg is a
routine that checks the internal consistency of the header and makes
corrections if necessary. In this case what happens is that the
original file was continuous and its header was copied to the epoched
file but did not fit the data any more.checkmeeg detected this, fixed
the file type and printed out a message to let you know about it.
When there are serious errors the code usually crashes with red error
messages.
Several checkmeeg messages usually appear at the end of conversion
because the conversion routine does not fill all the header fields and
leaves it to checkmeeg to fill the missing information.
Best,
Vladimir
On Mon, Oct 12, 2009 at 10:13 PM, Kambiz Tavabi <[log in to unmask]> wrote:
> Dear SPMers,
> While trying to epoch data that has already been downsampled and filtered I
> get the following message:
> PM8: spm_eeg_epochs (v3250) 17:03:42 - 12/10/2009
> ========================================================================
>
> SPM8: spm_eeg_definetrial (v2902) 17:03:42 - 12/10/2009
> ----------------------------------------------------------------
> checkmeeg: data type is missing or incorrect, assigning default
>
> I have not encountered the checkmeeg message prior to this step, and I not
> sure why data is missing or incorrect. Visually the epoched data looks as it
> should with correct number of trials, trial labels and gradiometer data in
> units pT (i.e. x.xxxxe-12). Any ideas why this message suddenly pops up now?
> I am epoching using the attached routine. I am not sure how S.timeonset is
> defined?
>
> Kambiz
>
>
>
|