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

Setting restart file frequency in WW3 #239

Open
anton-seaice opened this issue Oct 24, 2024 · 1 comment
Open

Setting restart file frequency in WW3 #239

anton-seaice opened this issue Oct 24, 2024 · 1 comment

Comments

@anton-seaice
Copy link
Contributor

In the reproducibility CI workflow, the runlength is set to three hours.

For access-om3-wav-configs ,this causes the run to fail, as WW3 doesn't write a restart file at the end of the three hours.

See

https://github.com/ACCESS-NRI/access-om3-wav-configs/actions/runs/11491825904/job/31984884825#step:4:181

The restart time can be changed through the date%restart%stride value in wav_in, so we could update the 'model-config-tests' to write this field. I think a better approach would be to update the nuopc drier for WW so the restart%stride is overwritten by the driver.

@anton-seaice
Copy link
Contributor Author

It looks like there is an option the use the nuopc stop times already:

logical                 :: user_restalarm = .false.      !< logical flag for user to set restart alarms
                                                           !! using ESMF. If restart_option is present as config
                                                           !! option, user_restalarm will be true and will be
                                                           !! set using restart_option, restart_n and restart_ymd

https://github.com/ESCOMP/WW3/blob/97740a1abb36b7ba6e52a7d6f7a37dd06f915633/model/src/wav_comp_nuopc.F90#L98

which is getting deprecated and becoming the default:

https://github.com/NOAA-EMC/WW3/pull/1303/files#diff-f6c6ab1c98f8ee8fc63fada01a56e5049cfef399b7eeb189f7c96a23c1be7e4f

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

1 participant