Pes specification file wrong in README.case for case with a compset alias and --pesfile #1664
Assignees
Labels
Comments
Merged
jedwards4b
added a commit
that referenced
this issue
Jun 9, 2017
User compset fixes Main change is to have user-defined compsets still pick up a usermods directory under [primary_component]/cime_config/usermods_dirs/. Along with this, I have refactored where some other things are set that depend on primary component. A key aim here was to have various things set in the same place regardless of whether we're using a compset with or without an alias. I find this makes it easier to understand the code, and less likely to introduce discrepancies between user-defined and alias-defined compsets in the future. Test suite: scripts_regression_tests on yellowstone Also, manual testing: Compset with an alias: picks up PE settings and a usermods directory User compset picks up PE settings User compset picks up usermods directory, as in: ./create_newcase --case no_alias_0608d --compset 1850_DATM%GSWP3v1_CLM50%BGC-CROP_SICE_SOCN_RTM_CISM2%NOEVOLVE_SWAV --res f09_g16 --user-compset --user-mods-dir clm/clm5_OutputCrop Test baseline: N/A Test namelist changes: none Test status: bit for bit Fixes #1658 Fixes #1664 Fixes #1665 User interface changes?: none Code review:jedwards
ghost
removed
the
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you create a case with a compset alias using the
--pesfileargument, README.case says:rather than pointing to the
--pesfileyou gave.I'm fixing this in an upcoming PR.
The text was updated successfully, but these errors were encountered: