-
Notifications
You must be signed in to change notification settings - Fork 7
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
0.25deg MOM6 parameters #126
Comments
What is the recommended approach for documenting the 025deg MOM parameters? Can I directly push my configuration as a new branch to https://github.com/COSIMA/MOM6-CICE6? Will this cause confusion when others review the repo? Additionally, how should I name the new branch to distinguish it from the existing025deg_jra55do_ryf? |
Hi @minghangli-uni, you should push to a new, uniquely-named branch as described in https://github.com/COSIMA/access-om3/wiki/Git-practices |
I think try to make one commit for each parameter and give it a really good commit message about why the choice was made for the change, (unless two parameter are intrinsically related). Ideally the model should run at every commit. |
We now have two examples of the MOM6 parameters currently being used by GFDL for OM5 at 0.25°: https://github.com/COSIMA/access-om3-doc/tree/main/configs/GFDL-OM5 Differences between these are tabulated here: https://github.com/COSIMA/access-om3-doc/blob/main/tables/MOM_input/GFDL-OM5_nml_diff.md And differences between GFDL OM4 and OM5 parameters are here https://github.com/COSIMA/access-om3-doc/blob/main/tables/MOM_input/GFDL-OM4-OM5_nml_diff.md |
To properly compare OM5 with our configs we'll need to start adding |
Just had a quick look at. It seems like they may have encountered bad values for their most recent parameters as well.
Also,
|
A PR, ACCESS-NRI/access-om3-configs#72, has been created for changes to the 0.25deg MOM6 parameters. MOM6 is the most time-consuming component of OM3, with the current 0.25 deg MOM6 parameters taking approximately 3-4 times longer than OM2. This increased runtime may be due to the parameters inherited from the 1 deg config, which includes more parameterisations that significantly impact the 0.25-degree configuration. Therefore, it is necessary to modify the MOM6 parameters based on our OM3 config differences and configuration discussion, along with relevant explanations. For comparison, all the following modifications reference a specific run configuration: 1344 ocean cores (concurrent), 96 ice cores, and 48 atmosphere and runoff cores (sequential), with the existing diagnostic outputs, a timestep of 1350 seconds and a run duration of 10 days (640 timesteps). |
Total runtime
Disable this parameter to prevent writing the initial conditions to the file specified by The runtime for |
In the 0.25deg configuration (intermediate scale) of OM4 from GFDL, mesoscale eddy features unresolved by the grid were not parameterised. This decision was based on comparison runs that showed the 0.25deg configuration provided better simulations without mesoscale eddy parameterisation. However, in OM5, mesoscale eddy parameters (MEKE) were reintroduced for all three parameter choices, including the configuration (
For 0.25deg OM2, mesoscale eddies were parameterised with an established GM and Redi parameterisations with simpler scaling methods. |
I/O optimisation is not part of the current MOM6 parameter tuning process. Therefore, only static grid diagnostics are included in the |
The current 0.25 deg MOM6 parameters have mostly been inherited from the 1 deg config. They will need some more changes for 0.25 deg, particularly in the sub-gridscale parameterisations.
Compare these differences in ACCESS-OM2 with our om3 config differences.
The 1 deg parameters also need updating, with these changes inherited at 0.25 deg as appropriate - see #83 and https://forum.access-hive.org.au/t/namelist-configuration-discussion-meeting/1917/9
The text was updated successfully, but these errors were encountered: