Open kkingstoun opened 4 hours ago
idk, I can do it but it will be a much worse version than just running as a bash command ... I can't think of a single advantage tbh
I would say it maight be useful solution, especially for simplifying the workflow when swapping simulations using templates. For instance, if we're using tools for swapping simulations, having everything inside the mumax script makes things easier, because everything will be contained in one place and visible in the log.
Right now, I do have bash script for this, but if this functionality were integrated into mumax itself, the process would be even more streamlined.
I propose adding functionality to automatically trigger Python scripts for postprocessing directly after a simulation completes in amumax. This would streamline the simulation workflow, allowing users to automatically process data without needing to manually run additional scripts after each simulation.
We can add a new function to the mumax3 scripting API, called runPython(), that allows users to specify a Python script (and optionally, arguments) to be executed automatically once the mumax3 simulation is complete.