Back to the main page.
Bug 2683 - test tutorials for Birmingham workshop
Status | CLOSED FIXED |
Reported | 2014-09-12 10:30:00 +0200 |
Modified | 2019-08-10 12:28:49 +0200 |
Product: | FieldTrip |
Component: | documentation |
Version: | unspecified |
Hardware: | PC |
Operating System: | Mac OS |
Importance: | P5 normal |
Assigned to: | Tzvetan Popov |
URL: | |
Tags: | |
Depends on: | |
Blocks: | |
See also: |
Tzvetan Popov - 2014-09-12 10:30:48 +0200
Tzvetan Popov - 2014-09-12 10:44:00 +0200
I went true the up to the beamforming tutorial and all works smoothly. I am testing on the DCCN workstation with Win7 64bitOS and Matlab2011b 32bit. In the statistics tutorial the call to ft_timelockstatistics results in an error: Invalid MEX-file 'C:\Users\tzvpop\Desktop\tutorialUK\matlabtools\fieldtrip-20140910\private\combineClusters.mexw32': The specified module could not be found. There is quite some discussion on this both in the documenation and on the list but I couldn't find an appropriate solution yet. Any hints?
Tzvetan Popov - 2014-09-16 11:38:13 +0200
Update on Matlab 2013b solved the issue with the MEX-file.
Robert Oostenveld - 2014-09-16 11:48:22 +0200
(In reply to Tzvetan Popov from comment #1) I though it might be related to the execute permissions on the mex file, but they seem to be ok. A little bit of background: I recall (although cannot find it) that mex files on windows should be executable, at at least when accessed over the network. this is fieldtrip/private: mac011> ls -al *.mexw32 -rwxr-xr-x 1 roboos staff 13312 May 11 08:20 combineClusters.mexw32 -rwxr-xr-x 1 roboos staff 10240 May 11 08:20 lmoutr.mexw32 -rwxr-xr-x 1 roboos staff 6144 May 11 08:20 mxDeserialize_c.mexw32 -rwxr-xr-x 1 roboos staff 5632 May 11 08:20 mxSerialize_c.mexw32 -rwxr-xr-x 1 roboos staff 7168 May 11 08:20 plgndr.mexw32 -rwxr-xr-x 1 roboos staff 10752 May 11 08:20 ptriproj.mexw32 -rwxr-xr-x 1 roboos staff 10240 May 11 08:20 routlm.mexw32 -rwxr-xr-x 1 roboos staff 10752 May 11 08:20 solid_angle.mexw32
Tzvetan Popov - 2014-09-16 12:03:47 +0200
Oh could it be, me not having admin permission on the PC-station?