Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with Matlab 2023B (Solved) #18

Open
evildna opened this issue Oct 11, 2023 · 5 comments
Open

Issues with Matlab 2023B (Solved) #18

evildna opened this issue Oct 11, 2023 · 5 comments

Comments

@evildna
Copy link

evildna commented Oct 11, 2023

I have downloaded and test run the code with Matlab 2023B(with the two tool boxed required).
The GUI looks fine and executed all the processing step, but no data file was saved. When I tried to visualize the results, a lot of error message showed up. @aelefebv

Is there anything I can do to make the code works in Matlab 2023B? Thank you.
These are some of the error messages,

Dot indexing is not supported for variables of this type.

Error in GUI2/ListBox_2ValueChanged (line 2217)
for i = 1:length(app.oneFileDynamics.speed)

Error in appdesigner.internal.service.AppManagementService/executeCallback (line 172)
callback(appOrUserComponent, event);

Error in matlab.apps.AppBase>@(source,event)executeCallback(ams,app,callback,requiresEventData,event) (line 62)
newCallback = @(source, event)executeCallback(ams, ...

Error using appdesservices.internal.interfaces.model.AbstractModel/executeUserCallback
Error while evaluating ListBox PrivateValueChangedFcn.

Dot indexing is not supported for variables of this type.

Error in GUI2/ListBox_2ValueChanged (line 2217)
for i = 1:length(app.oneFileDynamics.speed)

Error in appdesigner.internal.service.AppManagementService/executeCallback (line 172)
callback(appOrUserComponent, event);

Error in matlab.apps.AppBase>@(source,event)executeCallback(ams,app,callback,requiresEventData,event) (line 62)
newCallback = @(source, event)executeCallback(ams, ...

Error using appdesservices.internal.interfaces.model.AbstractModel/executeUserCallback
Error while evaluating ListBox PrivateValueChangedFcn.

Dot indexing is not supported for variables of this type.

Error in GUI2/ListBox_2ValueChanged (line 2217)
for i = 1:length(app.oneFileDynamics.speed)

Error in appdesigner.internal.service.AppManagementService/executeCallback (line 172)
callback(appOrUserComponent, event);

Error in matlab.apps.AppBase>@(source,event)executeCallback(ams,app,callback,requiresEventData,event) (line 62)
newCallback = @(source, event)executeCallback(ams, ...

Error using appdesservices.internal.interfaces.model.AbstractModel/executeUserCallback
Error while evaluating ListBox PrivateValueChangedFcn.

Dot indexing is not supported for variables of this type.

Error in GUI2/ListBox_2ValueChanged (line 2217)
for i = 1:length(app.oneFileDynamics.speed)

Error in appdesigner.internal.service.AppManagementService/executeCallback (line 172)
callback(appOrUserComponent, event);

Error in matlab.apps.AppBase>@(source,event)executeCallback(ams,app,callback,requiresEventData,event) (line 62)
newCallback = @(source, event)executeCallback(ams, ...

Error using appdesservices.internal.interfaces.model.AbstractModel/executeUserCallback
Error while evaluating ListBox PrivateValueChangedFcn.

@evildna
Copy link
Author

evildna commented Nov 8, 2023

Hi, A quick update. The issue has been solved, the Matlab support team has helped find out the problem that's causing it. It was due to my own operation issue. The app works both for Matlab 2020 and 2023.

@evildna evildna changed the title Issues with Matlab 2023B Issues with Matlab 2023B (Solved) Nov 8, 2023
@jaygamma
Copy link

Hi @evildna - I'm having the same issue, could you provide some detail as to how you resolved it? Everything I can find regarding the root error involves wrong variable types but I'm not sure how that can be happening when I haven't changed any of the code!

Thanks

@evildna
Copy link
Author

evildna commented Nov 17, 2023

@jaygamma Hi, I have attached the support letter from Rick from Matlab team in the base of this thread. I reproduced his steps and was able to get the app to work on both R2020 and R2023. The key step I missed in my previous operation was that I didn't click "select highlighted".

PS: I have later noticed that the app seems to have reduced ability to process large dataset. My test-run data set which was a small cropped region of a maximum intensity projection TIFF series works well. But once I switch to real data set(full frame size of Prime95B/Flash4.0 sCMOS, around 10 Z stacks, around 30 frames), the algorithm freeze and or not able to display the data processed. I have tested this both on laptop with relatively low processing power and specialised image processing workstation with sufficient processing power(GPU based), the issue persist.


Hi

I was not able to reproduce the issue in both MATLAB R2020b and MATLAB R2023b on Windows 10. Here is my workflow:

Download and extract the zip file from GitHub repo.
Go to APPS > Install App and select "Mitometer App.mlappinstall".
Run the app, import the test tif file, set the parameters as 2D data set, 0.2 micro per pixel, 5 sec per timepoint.
Click "Select highlighted".
Plots displayed in Segmentation and Tracks section. 

If the issue is related to toolbox upgrades, you may check installed toolboxes through Add-Ons > Manage Add-ons (on top right corner). Here is the version information for the related toolboxes on my machine.

MATLAB R2023b

image processing toolbox: version 23.2
statistics and machine learning toolbox: version 23.2 

MATLAB R2020b

image processing toolbox: version 11.2
statistics and machine learning toolbox: version 12.0 

Sincerely,
Rick Tu
MathWorks Technical Support

@jaygamma
Copy link

PS: I have later noticed that the app seems to have reduced ability to process large dataset. My test-run data set which was a small cropped region of a maximum intensity projection TIFF series works well. But once I switch to real data set(full frame size of Prime95B/Flash4.0 sCMOS, around 10 Z stacks, around 30 frames), the algorithm freeze and or not able to display the data processed. I have tested this both on laptop with relatively low processing power and specialised image processing workstation with sufficient processing power(GPU based), the issue persist.

I believe this is the issue - I was similarly able to get the program to function with smaller datasets (taking a single z-slice of my stack and running 2d analysis vs 3d) but cannot process the larger sets without encountering the quoted error.

Thanks for your response!

@Gavinwxy
Copy link

Switching to 2023a solved my problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants