Discrepancy between GUI and Commandline.mlx results

21 views
Skip to first unread message

weic liu

unread,
May 27, 2025, 5:20:51 AMMay 27
to PIVlab
Hi William and PIVlab users! 

I’m batch-processing a set of experiments under identical conditions using Commandline.mlx (with r{1,2}=r{2,2}=0.0451), but when I compare the output to the GUI results (with 1 px/frame = 0.0451 m/s) I see a clear order-of-magnitude difference (igure 1 and 2). 

I’ve tried adjusting the calibration index r{1,2} and r{2,2} to values like 1 or 0.5, yet the computed velocities never change. I’m unsure whether I’ve misunderstood how these parameters work or if there’s an issue in my modified script.

For reference, I’ve attached the .mlx file I’m using (it includes a few Chinese comments but should be self-explanatory) and .jpg files. Could you please advise on the correct role of these coefficients or point out anything I might be missing?  

Thanks,
LIUFigure-1-GUI.pngFigure-2-results-from-commandline.png
frame_00192.jpg
frame_00193.jpg
frame_00191.jpg
frame_00187.jpg
Commandline.mlx
frame_00188.jpg
frame_00189.jpg
frame_00190.jpg

William

unread,
May 27, 2025, 6:23:31 AMMay 27
to PIVlab
Hi, the  numbers in r{1,2} and r{2,2} report the conversion factors to the validation algorithms. But they do not change the data. After validation, you need to multiply the result (u and v) with your calibration factors.
Reply all
Reply to author
Forward
0 new messages