You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are running Veros on LUMI, which unfortunately doesn't provide a lot of disk space. The runs are generated using VerOpt, about 100 simulations per experiment, 100 years each. So far we are only running 4x4 horizontal resolution, but the plan is to extend to 1x1, thus significantly increasing output size. Our current strategy is to copy the Veros output to another machine after each optimisation step, but of course suppressing the generation of the restart files would be easier :)
I see. You could write a Python script (instead of using veros run) that calls Veros.setup() and Veros.step() in a loop, which wouldn't trigger the final restart files. Or, of course, adding rm *.restart.h5 to the script that calls veros run 😄
Is it possible to set up a Veros run where the restart files are not generated at the end of the simulation? I tried using:
VerosSettings.restart_frequency = None
but this did not work.
The text was updated successfully, but these errors were encountered: