Closed servoz closed 2 years ago
In my opinion we can stay with MATLAB MCR_R2018b, as long as it is maintained !
+1
if everyone agrees that it is urgent to do nothing, I propose to leave this ticket open for a while, that will leave us the joy of closing it on a sad day!
It seems modifying the matlab path using addpath() is not likely to be supported at any point after MATLAB MCR_R2018b.
I just tested Smooth brick from mia_processes with MCR_R2019b. The run fail with:
This is not observed with MATLAB MCR_R2018b. So the easy fix is to stick with R2018b.
However commenting the line with the addpath() command in the matlab script generated on the fly during the calculation run fixed the issue with MCR_R2019b:
So I don't know if this ticket is just an information for users so that they don't use a version above MATLAB MCR_R2018b, or if it's a ticket that asks for a real change in the codes. We could consider to modify the creation of the script by not using the addpath(). In mia, capsul, nypipe? This would require some work to determine exactly where it is done.
But above all, is it necessary to spend energy if it is enough to stay with MATLAB MCR_R2018b?