Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supressing restart files generation #640

Open
mrozowskamartaa opened this issue Aug 12, 2024 · 3 comments
Open

Supressing restart files generation #640

mrozowskamartaa opened this issue Aug 12, 2024 · 3 comments

Comments

@mrozowskamartaa
Copy link

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
Copy link
Collaborator

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
Copy link
Author

mrozowskamartaa commented Aug 12, 2024

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
Copy link
Collaborator

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 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants