Skip to content

Add NOAA cloud platforms to SRW#689

Merged
mark-a-potts merged 18 commits into
ufs-community:developfrom
NOAA-EPIC:feature/noaacloud
Mar 8, 2022
Merged

Add NOAA cloud platforms to SRW#689
mark-a-potts merged 18 commits into
ufs-community:developfrom
NOAA-EPIC:feature/noaacloud

Conversation

@mark-a-potts
Copy link
Copy Markdown
Collaborator

DESCRIPTION OF CHANGES:

Adds all three NOAA cloud platforms to the SRW application with both Intel and GCC compilers pre-configured.

TESTS CONDUCTED:

The full workflow based on a modified GST has been successfully completed using Intel compilers on both AWS and Azure platforms.
The full workflow currently fails when using GNU compilers due to a bug in (most likely) the UPP.

DEPENDENCIES:

None

DOCUMENTATION:

WIP

Copy link
Copy Markdown
Contributor

@christinaholtNOAA christinaholtNOAA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mark-a-potts Thanks for adding the files and example on how this is done! My apologies for using your PRs as a "big picture" question forum.

Reviewers -- please see my comments in the corresponding SRW PR about how we might best support new platforms.

Copy link
Copy Markdown
Contributor

@christinaholtNOAA christinaholtNOAA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After our conversation in the EPIC Sprint Review this morning, I am less concerned about this not being a traditionally "supported" platform. Just one quick requested change from me.

Comment thread ush/machine/noaacloud.sh Outdated
gsketefian added a commit that referenced this pull request Mar 8, 2022
## DESCRIPTION OF CHANGES: 
Cleaning up bugs in the machine files.  The first bug prompted this PR, and the rest were found subsequently.  The bugs (and their fixes) are as follows:

1) A space is missing after the `print_info_msg` and `print_err_msg_exit` function calls in the `file_location` functions.  Inserting a space gets passed this bug, but subsequent issues were found as described below.

**For machine files that call the `print_info_msg` function in `file_location` (`cheyenne.sh`, `hera.sh`, `jet.sh`, and `orion.sh`):**
Fixing this bug leads to other failures because when the "*" stanza is encountered in the `file_location` function, 
the `EXTRN_MDL_SYSBASEDIR_ICS|LBCS` variable gets set to the message that `file_location` returns.  Since that message contains spaces, it leads to other failures in downstream scripts (the ex-scripts).  Simply removing the printing out of the message (thus causing `EXTRN_MDL_SYSBASEDIR_ICS|LBCS` to be set to a null string) fixes the failures, so this was the fix implemented.  If desired, a message for an empty value for `EXTRN_MDL_SYSBASEDIR_ICS|LBCS` can be placed in another script (where those variables are used).

**For machine files that use `print_err_msg_exit` in `file_location` (`stampede.sh` and `wcoss_dell_p3.sh`):**
These should not exit if the file location is not available since the experiment can still complete successfully.  So just removing the `print_err_msg_exit` call should work (and make the behavior of these machine files consistent with the set above).

2) In all the machine files, the variable `FV3GFS_FILE_FMT_ICS` should be changed to `FV3GFS_FILE_FMT_LBCS` in the definition of `EXTRN_MDL_SYSBASEDIR_LBCS`.  This was fixed in all the files.

3) In `stampede.sh`, a variable named `SYSBASEDIR_ICS` is defined.  This is a typo.  Modify to `EXTRN_MDL_SYSBASEDIR_ICS`.

## TESTS CONDUCTED: 
Ran the WE2E test `grid_RRFS_CONUS_25km_ics_HRRR_lbcs_RAP_suite_GSD_SAR` on:
* Hera -- successful
* Jet -- successful except for UPP tasks
* Cheyenne -- successful except for UPP tasks

The UPP task failures are new and being experienced by other PRs as well (e.g. #689).  The original issue with machine files seems resolved.

## CONTRIBUTORS (optional): 
@JeffBeck-NOAA encountered and reported the original error.
@mark-a-potts mark-a-potts merged commit a83142f into ufs-community:develop Mar 8, 2022
@gsketefian gsketefian mentioned this pull request Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants