Hope you are well! I had run preliminarily analysis (n=5) in Osprey and liked it very much! It’s so user-friendly! I intend to analyse a larger data set (n=21) now.
I am unable to run Osprey GUI. After adding path, I get errors regarding “pad” function on checking Matlab version, and Osprey GUI load fails (script attached). When I use the command line, I am able to load the job file but some error happens while adding the data.
I am using the most recent version of Osprey (2.8) and Matlab (2024b). I have all the toolboxes installed, for some reason the Widget toolbox is not listed upon version check, only the Widget Compatibility toolbox is listed.
I am unsure if this should be a separate thread. I was using older versions of Matlab (2024a and 2023a) with Osprey 2.8 and 2.7, however, the overview step was repeatedly failing with the following error (I am attaching the logfile):
Error using .
To assign to or create a variable in a table, the number of rows must match the
height of the table.
Error in OspreyOverview (line 591)
statFile.subject = subject’;
Lines 588-592 are:
if ~strcmp(name,‘subject’) % No subject names stored in the container
if length(subject)>1 && ~strcmp(subject{1},subject{2}) % Add names according to BIDS with subfolder
if ~strcmp(name,‘subject’)
statFile.subject = subject’;
end BoseA_Osprey_Overview_Error_Log.txt (3.3 KB)
None of the subjects had odd output in the preceding steps. I had switched to recent versions hoping to avoid this error.
I can’t quite make sense of the GUI error log you posted. It seems like it stopped working at subject 18 with an ‘invalid file identifier’ error, which suggests that the target file that was specified in the job file was not found on the drive (check for spelling errors). (I believe the pad error is a red herring likely caused by Osprey having a function called pad that’s shadowing a native MATLAB function with the same name which ver wants to use (@Helge I think pad needs to be renamed to prevent this)
Did you then run Quantify on the same (unfinished) container?
Matlab 2024b seems to be more strict with path definitions. However, the pad function is not used in Osprey itself (we are using op_pad instead to avoid using internal Matlab function names), so I just kept it as the original function of the external library. You can simply go ahead and delete it in the libraries/pad/ folder. I will also put this as a bugfix on GitHub.
Now, the other problem seems to be the Widgets Toolbox Compatibility Support. Can you check again after deleting the pad function and typing ver what your version is? It shows the same version as yours but R2023a instead of R2024b, even though I am using R2024b. Could you try reinstalling the Widgets Toolbox Compatibility Support Toolbox?
The pad error aside, I carefully checked my data set, a subject’s data (header file) was corrupted. Removing that subject worked. Data load and analysis ran until the Overview step (Matlab 2023b, Osprey 2.8).
Yes! I had. Is that an incorrect thing to do?
I repeated the analysis (Matlab 2024b, Osprey 2.8). There was a subject entry missing in my file_stat.csv file; I guess that was causing the issue. The analysis ran successfully. However, I got the following warning message (file attached):
Deleting the “pad.m” file from the osprey-develop\libraries\pad has resolved the GUI issue.
I uninstalled and re-installed the Widgets Toolbox Compatibility Support toolbox as well, and you are right about the version, it’s R2023a now.