PIVlab_GUI>AnalyzeAll_Callback - analysis crashing when run in parallel

196 views
Skip to first unread message

Iain Fairley

unread,
Jun 1, 2022, 8:40:24 AM6/1/22
to PIVlab
Good morning,

I've recently been having an issue when trying to run PIVlab in parallel (Ver 2.57 but also had the same issue with previosu version).

The matlab error is: 

Error in PIVlab_GUI>DCC_and_DFT_analyze_all (line 5177)
                resultslist{1,i}=xlist{i};

Error in PIVlab_GUI>AnalyzeAll_Callback (line 5503)
    DCC_and_DFT_analyze_all
 
Error while evaluating UIControl Callback.

It seems that xlist is an empty variable.  I think that the issue started after I tried using the PIVlab_commandline script, so I'm not sure if that has changed something?

From what I can see, xlist(i) should be = x from pivFFTmulti (lines 5156 & 5157 of PIVlab_GUI, but it won't let me set a debug stop (because its in a parfor loop?)

I'm using MAtlab 2020a - I didnt have an issue before.  Any ideas?

Thanks,
Iain

William Thielicke

unread,
Jun 3, 2022, 11:24:58 AM6/3/22
to PIVlab
Hi, can Ou send me the necessary files and settings to reproduce this problem?

Iain Fairley

unread,
Jun 7, 2022, 4:46:34 AM6/7/22
to PIVlab
Thanks,

I'm using time-resolved image spacing, with all image pre-processing turned off (we preprocess ouitside of PIVlab),  PIV analysis settings are default (FFT window deformation, 64/32 px IAs, Gauss 2x3 point estimator, standard correlation robustness), If I 'analyse current frame'  in the PIV settings I don't have a problem, likewise if i dont use parrallel processing there isnt a problem.  I've attached a few images in a zip folder, but I've tried different images with the same problem.

Iain
frames.zip

Iain Fairley

unread,
Jun 8, 2022, 11:43:43 AM6/8/22
to PIVlab
Just to follow up on this, I've tried re-installing MATLAB (now using R2022a) and have tried going back to PIVlab ver 2.54, I'm still getting the same error.

Any help greatly appreciated

Thanks,

Iain

William Thielicke

unread,
Jun 8, 2022, 11:45:07 AM6/8/22
to PIVlab
I currently don't have a computer to test. What happens if you don't disable all preprocessing?

Iain Fairley

unread,
Jun 8, 2022, 12:49:50 PM6/8/22
to PIVlab

I've found issue.  The location of the problem is in lines 5066 - 5070 of PIVlab_GUI:
               if exist('cancel_piv','file')
                   %disp('cancelled')
                   close(hbar);
                   continue
               end

I found if I comment these lines out the parfor loop from 5064 - 5128 works correctly, xlist etc are populated and so resultslist is populated on line 5140.  I then checked and realised that there was a 'cancel_piv' file in another directory that was in my matlab path from some previous PIVlab analysis, and so that was making the if exist ... statement true. That was then cancelling the parfor loop and causing the error. Having deleted that file, I'm not having the issue. Strangely, I can't seem to replicate the error.

Thanks,

Iain

Pande Putu Hadi Wiguna

unread,
Aug 20, 2024, 11:43:44 PM8/20/24
to PIVlab
Error using PIVlab_preproc
Index in position 1 exceeds array bounds. Index must not exceed 656.

Error in PIVlab_GUI>DCC_and_DFT_analyze_all (line 5442)
parfor i=1:size(slicedfilepath1,2)

Error in PIVlab_GUI>AnalyzeAll_Callback (line 5847)

DCC_and_DFT_analyze_all
 
Error while evaluating UIControl Callback.

I have a similar problem. The error occurred when I did the analysis at once. But when I did analysis on the current image, no error occurred at all. However, this will of course be more troublesome if you analyze the images one by one. Please help me

William

unread,
Aug 28, 2024, 3:28:41 AM8/28/24
to PIVlab
Have you done what Iain has proposed as solution in his last post...?
Reply all
Reply to author
Forward
0 new messages