It sounds like you are encountering challenges with plotting simulation results from Simulink and have identified a workaround that involves restarting the Python engine between the simulation and the MATLAB plotting script. To address the issue of the Python process detaching after running the simulation script, I have a couple of suggestions that could streamline your workflow.
Ensuring smooth communication between the simulation completion in Simulink and subsequent MATLAB processes for plotting is your main concern. To facilitate this communication, consider utilizing a shared file as a signalling mechanism. This approach involves writing to a text file at the end of your simulation to signal completion, which can then be checked by other MATLAB processes.
At the end of your Simulink simulation, use the “writelines” function to write a specific line or flag to a text file indicating that the simulation has finished. More details on this can be found here:
In your MATLAB script responsible for plotting, use the “fileread” function to check this file for the completion flag before proceeding with plotting. Further information on this function is available here:
Instead of using the “sim” function, which halts the MATLAB script until the simulation is complete, you can use “set_param” with your loaded system to start the simulation in a non-blocking manner:
set_param(gcs, SimulinkCommand=”start”)
To check the status of the simulation, utilize:
get_param(gcs, “SimulationStatus”)
This method allows your MATLAB script to continue executing while the simulation runs. You can learn more about managing simulations programmatically here:
Hope this helps.
