-
Notifications
You must be signed in to change notification settings - Fork 146
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
cam6_4_033: Add updated ncdata and bnd_topo files for MPASv8 #1029
Conversation
The new IC files contain fields that are expected by routines in cam_dev (cam7) physics. The new topo files were regenerated due to changes in the NCAR/Topo software. These files are only used when 'phys="cam_dev"' to ensure previous compsets and/or tests aren't affected.
NOTE: This PR branch is based on cam6_3_148 for compatibility with EarthWorks. This can be updated at any time, in whatever way reviewers would prefer. Remaining work:
Footnotes
|
This commit addresses issues that were seen when using ncdata with longitudes in the [-pi, pi] range in cases with full physics. This would cause the atmosphere to become unphysical and runs to fail. This change is made just after the longitude values are read to ensure they are correct for the remainder of execution.
NOTE: this is before the 'aux_cam' tests have been run
Previous versions of the lonCell_arr adjustment used an explicit loop. Without this loop, the nCells variable and the routine to fetch it are no longer needed.
Makes code consistent with CAM coding standards: 'All variables of type real must have a specified kind, including literals.'
This commit also extends the comment that was with this code block, includes an if condition so valid values aren't modified, uses kinds and constants (pi) that are already used in the new file, and updates the ChangeLog so the correct file is referenced.
This aligns the files with changes in cam6_4_001 (PR ESCOMP#1028).
At this point 3.1 has been addressed by b608af1. I plan to proceed with step 3 and 4 once I have a tag number or directed otherwise. |
Conform to CAM Coding Standards: 'Use symbolic numerical comparison operators (e.g., ==, /=, <, >=) not old character versions (e.g., .eq.).'
The correct file for these physics schemes must include topography.
Enable no-topography, idealized test cases with the mpas dycore when running 58L or 93L on 480, 120, 60, and 30km grids.
NOTE: these files also support running with analytic_ic.
Duplicates an entry to ensure that the following two files are used together: - mpasa120_L32_topo_coords_c240508.nc - mpasa120_gmted2010_modis_bedmachine_nc3000_Laplace0100_noleak_20240507.nc Matches the physics specification on new real-data ICs, so the correct *_20240507.nc bnd_topo files are used with them.
@adamrher could you take a look at this and see if it matches the files you expect? I want to make sure before I try to get these added to the CESM data repo. This PR now:
Footnotes
|
This is my understanding with MPAS. We get horizontal grid info from meshes generated by code not in the main MPAS-Model repo. It's easy to add vertical levels to that. I don't think that it would be efficient to do the Voronoi tessellation online (especially for high resolution) to run MPAS from only a set of vertical levels. |
Dylan I think what @jtruesdal is referring to is that, for example with the se dycore, when you want to run a new grid and you don't have an inic file, you can add a new grid entry in ccs_config/ pointing to a new ESMF mesh file (meaning you're supplying the new grid, not generating it in a run), and then run with analytic_ic. For the se dycore (and all but mpasa, maybe), the ncdata file only needs to have vertical level information, and the analytic_ic's are generated in the horizontal using the supplied mesh file and analytic_ic code in src/dynamics/. That's why there are only three coordinate files in the analytic_ic section (L26, L30, L32); they work for any arbitrary horizontal grid/dycore. For no_topo mpasa, I think the zgrid is identical for every grid column. But I wouldn't be surprised if mpasa requires analytic_ic to have a ncdata file on the horizontal grid, which is indicated by the comments in the mpasa analytic_ic section of namelists_defaults.xml. |
The MPAS vertical coordinate is height based so does have a dependence on the height of each ncol. The mpass coords files are very useful for aquaplanet cases where there is no topo. As you mentioned then we only need one coord file for each supported vertical resolution. I've also generated quick initial condition files from the aquaplanet runs that I've also used for non-aquaplanet cases. |
Thanks for explaining, my understanding of CAM/CESM was off. It seems to me the reason is:
|
Remove old L32 real-data files and all physics specififiers from new real-data files. The old mpasa bnd_topo is similarly replaced. One entry with the old mpasa120 bnd_topo file remains, it is still used by the mpas120km.waccm_fulltopo_c220818.nc ncdata. Specifiers are used to match these entries.
After pushing 939a92d, 9afb3cd, and 24012df. The remaining work seems to be:
|
The mpasa120km.waccm_fulltopo_c220818.nc was the last file using mpas_120_nc3000_Co060_Fi001_MulG_PF_Nsw042_c200921.nc, allowing it to be removed.
@adamrher @jtruesdal @cacraigucar, I'm looking for another round of reviews or comments on this. Once any changes are made and this PR approved, I will ask for help getting the files below added to CESM data. Files to add to atm/cam/inic/mpas (12):
Files to add to atm/waccm/ic (1):
Accessible on Derecho, within sub-dirs of: "/glade/derecho/scratch/gdicker/2024Jun04_CAMMPASv8Grids_2/files_for_cesmdata3" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great Dylan, thanks for doing this!
ESCOMP#1095) These changes address run-time failures that were seen when using MPAS ncdata with longitudes in the [-pi, pi] range in cases with non-simple physics. The atmospheric state would become unphysical and fail.
Part of catching up to cam_development
Catch PR branch up to current head of cam_development
Disregard this comment, EarthWorksOrg/CAM is actually based on cam6_4_019 |
These files currently can't be added to the CESM data repository due to size. Interested users may find these files within the CESM inputdata directory on Derecho and/or GLADE.
…w-develop (PR #33) Add updated ncdata and bnd_topo files for MPASv8. This PR brings in a feature branch that was contributed to ESCOMP/CAM ESCOMP#1029 (tagged cam6_4_033) and adds a few extra EarthWorks-specific files on top.
Merge pull request ESCOMP#1029 from gdicker1/add_v8mpasfiles cam6_4_033: Add updated ncdata and bnd_topo files for MPASv8 ESCOMP commit: fa94177
Merge pull request ESCOMP#1029 from gdicker1/add_v8mpasfiles cam6_4_033: Add updated ncdata and bnd_topo files for MPASv8 ESCOMP commit: fa94177
Merge pull request ESCOMP#1029 from gdicker1/add_v8mpasfiles cam6_4_033: Add updated ncdata and bnd_topo files for MPASv8 ESCOMP commit: fa94177
The new initial condition files contain fields that are expected by routines in cam_dev (cam7) physics. The new topo files were regenerated due to changes in the NCAR/Topo software. These files are only used when
phys="cam_dev"
to ensure previous compsets and/or tests aren't affected.These files were checked for NaNs and runs were attempted for the
F2000dev
compset before making this PR.Fixes #995 and #1094