I experienced a similar issue as issue #8 with my Windows 10 system, where the read serialized image had an other size than stated in header of the respective .dat file.
After several trials I have found out that mainly the executing of the docker command with Matlab's system() call in piRunCommand() function returns to early a good status before Docker was able to finish the simulation and saving the result in the .dat file.
This results later then in the incorrect sizes and throws the error in piReadDAT().
Is this issue only depending on the OS? Is there some other way to check if the Docker command ran successfully and the saving was completed?
Hello,
I experienced a similar issue as issue #8 with my Windows 10 system, where the read serialized image had an other size than stated in header of the respective .dat file.
After several trials I have found out that mainly the executing of the docker command with Matlab's
system()call inpiRunCommand()function returns to early a good status before Docker was able to finish the simulation and saving the result in the .dat file.This results later then in the incorrect sizes and throws the error in
piReadDAT().Is this issue only depending on the OS? Is there some other way to check if the Docker command ran successfully and the saving was completed?
Best regards, Florian