team-ocean / veros

The versatile ocean simulator, in pure Python, powered by JAX.
https://veros.readthedocs.io
MIT License
330 stars 55 forks source link

Supressing restart files generation #640

Open mrozowskamartaa opened 2 months ago

mrozowskamartaa commented 2 months ago

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.

dionhaefner commented 2 months ago

This is not possible. You can only suppress all output (even from diagnostics) by using veros run --diskless-mode.

Is there a specific reason why you want to prevent writing restart files?

mrozowskamartaa commented 2 months ago

Thanks, that was my impression.

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 :)

dionhaefner commented 2 months ago

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 😄