-
Notifications
You must be signed in to change notification settings - Fork 26
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
Enable On-the-Fly Generation of WW3 Binary Files #440
Comments
Is there an option to make WW3 abort if it receives an unrecognised namelist parameter, as we do in MOM6? |
WW3 will only recognize parameters associated with switches it's compiled with. If a parameter in
If a user defines ST4 input parameters instead of ST6, WW3 will automatically abort. However, if a user adds additional parameters without compiling WW3 with the relevant switches, WW3 will simply ignore those parameters. |
After the meeting with Aidan, we have finalized a plan for generating the input file for WW3 on the fly. Here are the conclusions we arrived at:
I have made modifications to the Payu codebase, enabling us to generate However, after generating the binary file, Payu is failing while writing manifests/restart.yaml. The |
Description:
The WW3 model's workflow is intricate, involving the generation of binary files through the
ww3_grid
grid preprocessor. Currently, these binary files are created using predefined namelist parameters inww3_grid.nml
andnamelists_Global.nml
, alongside specific grid files (OM2_1.Lon
,OM2_1.Lat
,OM2_1.Dpt
,OM2_1.Mask
, andOM2_1.Obstr
).To improve user experience and workflow flexibility, we propose implementing a solution where the binary files (specifically
mod_def.ww3
) are dynamically generated during runtime. This approach would enable users to modify most input namelist parameters without needing to rebuildww3_grid
, thus providing greater control and understanding of the binary file's provenance.Proposed Solution:
mod_def.ww3
,restart.ww3
) within Payu.ww3_grid
orww3_strt
(for generating restart), except for major changes that necessitate modifying switches.PS: The challenge arises when users need to modify critical parameters such as propagation schemes, source schemes, attenuation and scattering models. While most changes can be accommodated within the namelists, certain adjustments necessitate modifying switches and rebuilding
ww3_grid
other wise modifications in the namelists will be ignored by WW3.The text was updated successfully, but these errors were encountered: