Dear SPMers,
I have encountered an error when re-referencing my MEEG data object:
Invalid MEX-file
'C:\Users\Jessica\Documents\Codes\spm12\external\fieldtrip\fileio\private\ft_getopt.mexw64':
The specified procedure could not be found.
In file
"C:\Users\Jessica\Documents\Codes\spm12\external\fieldtrip\fileio\private\ft_senslabel.m"
(v10341), function "ft_senslabel" at line 85.
In file
"C:\Users\Jessica\Documents\Codes\spm12\external\fieldtrip\fileio\private\ft_senstype.m"
(v10421), function "ft_senstype" at line 301.
In file
"C:\Users\Jessica\Documents\Codes\spm12\external\fieldtrip\fileio\ft_chantype.m"
(v10197), function "ft_chantype" at line 94.
In file "C:\Users\Jessica\Documents\Codes\spm12\spm_eeg_prep.m" (v6437),
function "spm_eeg_prep" at line 62.
In file "C:\Users\Jessica\Documents\Codes\spm12\spm_eeg_montage.m"
(v6398), function "spm_eeg_montage" at line 279.
In file
"C:\Users\Jessica\Documents\Codes\spm12\config\spm_cfg_eeg_montage.m"
(v5377), function "eeg_montage" at line 145.
The following modules did not run:
Failed: Montage
Error using MATLABbatch system
Job execution failed. The full log of this run can be found in MATLAB
command window,
starting with the lines (look for the line showing the exact #job as
displayed in this error
message)
------------------
Running job #1
------------------
It seems that a mex file in fieldtrip is not compiled for Windows 10
(everything else works fine and all my paths should be fine as well as I
launched SPM). It doesn't affect the montage operation per se, but some
of the properties of the old file (like bad channels) cannot be copied
into the new file it seems.
On another note, one of my students had reported a bug with the
'Prepare' when playing with the 'scrambled faces' dataset (from the SPM8
tutorial, but using SPM12). I experienced the same error: my whole
computer just stopped responding and I had to power it off using the
power button (ctrl+alt+delete didn't even launch the task manager and no
other application/process was responsive). I tried twice and had the
same result twice. I don't see how we can provide an error message with
that, but I can say that it is when loading the sensor file and it
happened both on Matlab R2013b (on Mac) and on Matlab R2015a (Windows7).
I ended up skipping this step.
Can you please help?
Thanks!
Best,
Jessica
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
|