-
Notifications
You must be signed in to change notification settings - Fork 258
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
Update links and version numbers from 1.0.0 to 1.1.0 #187
Update links and version numbers from 1.0.0 to 1.1.0 #187
Conversation
Both html and latex builds succeed.
@@ -28,13 +28,13 @@ If developers would like to get their code committed back to the original reposi | |||
|
|||
4. Merging code from PRs with submodules requires coordination with the person making the PRs. From the "innermost" nested PR up to the top-level PR, the PRs need to be merged as-is. After each merge, the person creating the PRs has to update his/her local code to check out the merged version, revert the change to .gitmodules, and push this to GitHub to update the PR. And so on and so forth. | |||
|
|||
5. Checking out the code ufs_release_1.0 should always be as follows: | |||
5. Checking out the code for this v1.1.0 release should be as follows: |
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.
While the instructions here are technically correct, developers should not be working from the tag. They need to check out and contribute to the develop branch. I will discuss this with @JulieSchramm for a possible follow up PR. For this PR, this is okay.
|
||
As noted in the file names, these namelists are for the operational (v15p2) and developmental (v16beta) | ||
GFS suites. Each of these namelists are relevant to the suites with and without the SST prediction scheme, that is, | ||
they are relevant for the suite that employs NSST and for the suite that employs the simple ocean | ||
model (`no_nsst`). The only difference in the namelist regarding how SST prediction is | ||
addressed is variable `nstf_name`. For more information about this variable and for information about | ||
namelist options for higher resolution configurations, please consult the | ||
`CCPP v4 Scientific Documentation <https://dtcenter.org/GMTB/v4.0/sci_doc/>`_. | ||
`CCPP v4.1 Scientific Documentation <https://dtcenter.org/GMTB/v4.1/sci_doc/>`_. |
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.
`CCPP v4.1 Scientific Documentation <https://dtcenter.org/GMTB/v4.1/sci_doc/>`_. | |
`CCPP v4.1.0 Scientific Documentation <https://dtcenter.org/GMTB/v4.1.0/sci_doc/>`_. |
|
||
The four CCPP suites for the UFS MR Weather App release are supported in four grid resolutions: | ||
C96, C192, C384, and C768, with 64 vertical levels. | ||
|
||
An in depth description of the namelist settings, SDFs, and parameterizations used | ||
in all supported suites can be found in the `CCPP v4 Scientific Documentation <https://dtcenter.org/GMTB/v4.0/sci_doc/>`_. | ||
in all supported suites can be found in the `CCPP v4.1 Scientific Documentation <https://dtcenter.org/GMTB/v4.1/sci_doc/>`_. |
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.
in all supported suites can be found in the `CCPP v4.1 Scientific Documentation <https://dtcenter.org/GMTB/v4.1/sci_doc/>`_. | |
in all supported suites can be found in the `CCPP v4.1.0 Scientific Documentation <https://dtcenter.org/GMTB/v4.1.0/sci_doc/>`_. |
@@ -18,7 +18,7 @@ https://dtcenter.org/GMTB/v4.0/sci_doc/CCPPsuite_nml_desp.html | |||
|
|||
The following link describes the stochastic physics namelist records: | |||
|
|||
https://stochastic-physics.readthedocs.io/en/ufs-v1.0.0/namelist_options.html | |||
https://stochastic-physics.readthedocs.io/en/release-ufs-v1.1.0/namelist_options.html |
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.
Two lines above there is a link to https://dtcenter.org/GMTB/v4.0/sci_doc/CCPPsuite_nml_desp.html that needs to be updated to v4.1.1
|
||
The four CCPP suites for the UFS MR Weather App release are supported in four grid resolutions: | ||
C96, C192, C384, and C768, with 64 vertical levels. | ||
|
||
An in depth description of the namelist settings, SDFs, and parameterizations used | ||
in all supported suites can be found in the `CCPP v4.1 Scientific Documentation <https://dtcenter.org/GMTB/v4.1/sci_doc/>`_. | ||
in all supported suites can be found in the `CCPP v4.1 Scientific Documentation <https://dtcenter.org/GMTB/v4.1.0/sci_doc/>`_. |
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.
in all supported suites can be found in the `CCPP v4.1 Scientific Documentation <https://dtcenter.org/GMTB/v4.1.0/sci_doc/>`_. | |
in all supported suites can be found in the `CCPP v4.1.0 Scientific Documentation <https://dtcenter.org/GMTB/v4.1.0/sci_doc/>`_. |
@@ -24,13 +24,13 @@ they are relevant for the suite that employs NSST and for the suite that employs | |||
model (`no_nsst`). The only difference in the namelist regarding how SST prediction is | |||
addressed is variable `nstf_name`. For more information about this variable and for information about | |||
namelist options for higher resolution configurations, please consult the | |||
`CCPP v4.1 Scientific Documentation <https://dtcenter.org/GMTB/v4.1/sci_doc/>`_. | |||
`CCPP v4.1 Scientific Documentation <https://dtcenter.org/GMTB/v4.1.0/sci_doc/>`_. |
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.
`CCPP v4.1 Scientific Documentation <https://dtcenter.org/GMTB/v4.1.0/sci_doc/>`_. | |
`CCPP v4.1.0 Scientific Documentation <https://dtcenter.org/GMTB/v4.1.0/sci_doc/>`_. |
@JulieSchramm I would like to request one more change wrt links. In Chapter 4 (Inputs and Outputs), please replace this link https://www.gfdl.noaa.gov/wp-content/uploads/2017/09/fv3_namelist_Feb2017.pdf with this one https://noaa-emc.github.io/FV3_Dycore_ufs-v1.1.0/html/index.html. The HTML in github.io has additional information beyond what is in the PDF (Valbona worked with GFDL to augment it). The v1.1.0 is not ready yet (it will be a broken link). But soon it shoudl be stood up and look similar to the existing https://noaa-emc.github.io/FV3_Dycore_ufs-v1.0.0/html/index.html. |
Replace link to GFDL dycore. Both html and latex builds succeed.
- Contributing development content is in the UFS WM wiki page. - Add links wiki page and remove mention of Chapter 6. - Remove RT from Acronyms - Minor corrections to Introduction Both html and latex builds succeed.
…, updates to other GSL physics (ufs-community#202) This PR updates the GSL physics and does a few other things: *add --debug to ccpp_prebuild.py call when model is compiled in DEBUG mode, and pretty print the output in the build log (fixes ufs-community#187 and ufs-community#135) *add unified gravity wave drag (called unified ugwp) that combines the UGWP v1 with the GSL drag suite *add suite definition file for GFS v16beta for coupled model *move static array zs (depth of soil layer), dimensioned as 1:lsoil_lsm from Sfcprop to Model (since this is a model configuration and only needs to be stored once, not for each block) Co-authored-by: DomHeinzeller <58610420+DomHeinzeller@users.noreply.github.com> Co-authored-by: samuel.trahan <Samuel.Trahan@noaa.gov> Co-authored-by: hannah barnes <hannah.barnes@noaa.gov> Co-authored-by: tanyasmirnova <tanya.smirnova@noaa.gov> Co-authored-by: Joseph Olson <Joseph.B.Olson@noaa.gov> Co-authored-by: Michael Toy <michael.toy@noaa.gov>
Description
Update links and version numbers for v1.1 release
Issue(s) addressed
No issues.
Testing
Only the documentation was modified, both html and latex builds succeed.
Dependencies
None.