Skip to content
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

[develop] Add analysis task. #643

Merged

Conversation

danielabdi-noaa
Copy link
Collaborator

@danielabdi-noaa danielabdi-noaa commented Mar 6, 2023

DESCRIPTION OF CHANGES:

Add gsi analysis task from RRFS_dev1.
Note that there is no workflow so this PR can not be run independently until then.
However, it did successfully run for both spinup/production cycles in PR #540.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

TESTS CONDUCTED:

DEPENDENCIES:

DOCUMENTATION:

ISSUE:

CHECKLIST

  • My code follows the style guidelines in the Contributor's Guide
  • I have performed a self-review of my own code using the Code Reviewer's Guide
  • I have commented my code, particularly in hard-to-understand areas
  • My changes need updates to the documentation. I have made corresponding changes to the documentation
  • My changes do not require updates to the documentation (explain).
  • My changes generate no new warnings
  • New and existing tests pass with my changes
  • Any dependent changes have been merged and published

LABELS (optional):

A Code Manager needs to add the following labels to this PR:

  • Work In Progress
  • bug
  • enhancement
  • documentation
  • release
  • high priority
  • run_ci
  • run_we2e_fundamental_tests
  • run_we2e_comprehensive_tests
  • Needs Cheyenne test
  • Needs Jet test
  • Needs Hera test
  • Needs Orion test
  • help wanted

CONTRIBUTORS (optional):

Copy link
Collaborator

@MichaelLueken MichaelLueken left a comment

Choose a reason for hiding this comment

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

@danielabdi-noaa These changes look good to me!

In scripts/exregional_run_anal.sh, I have noted a commented line that looks like it can be safely removed, and left a comment regarding the copying the analysis results to INPUT for model forecast.

scripts/exregional_run_anal.sh Outdated Show resolved Hide resolved
scripts/exregional_run_anal.sh Outdated Show resolved Hide resolved
@JeffBeck-NOAA
Copy link
Collaborator

@danielabdi-noaa, can we change the j-job and ex-script names to something like *_run_analysis? Thanks!

@BenjaminBlake-NOAA
Copy link
Collaborator

@JeffBeck-NOAA @danielabdi-noaa If possible could we go with either analysis or analysis_gsi? We should remove the run_* prefix (see issue #633 ) Thanks!

@danielabdi-noaa
Copy link
Collaborator Author

@JeffBeck-NOAA @BenjaminBlake-NOAA Ok I will make it "analysis_gsi".

@danielabdi-noaa danielabdi-noaa self-assigned this Apr 26, 2023
Copy link
Collaborator

@panll panll left a comment

Choose a reason for hiding this comment

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

It looks good to me!

Copy link
Collaborator

@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.

In general the code looks good.

Please replace all instances of anal with either analysis or anl.

Copy link
Collaborator

@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.

LGTM.

Copy link
Collaborator

@BenjaminBlake-NOAA BenjaminBlake-NOAA left a comment

Choose a reason for hiding this comment

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

@danielabdi-noaa Thanks for addressing my comment to rename the task to analysis_gsi and for addressing Christina's suggestions. Everything looks good to me!

@MichaelLueken MichaelLueken added the run_we2e_coverage_tests Run the coverage set of SRW end-to-end tests label May 1, 2023
@MichaelLueken
Copy link
Collaborator

@danielabdi-noaa The nco_grid_RRFS_CONUS_3km_ics_FV3GFS_lbcs_FV3GFS_suite_GFS_v15_thompson_mynn_lam3km test failed on Cheyenne GNU, the grid_RRFS_CONUS_25km_ics_NAM_lbcs_NAM_suite_GFS_v16 test failed on Cheyenne Intel, the get_from_NOMADS_ics_FV3GFS_lbcs_FV3GFS test failed on Hera GNU, and the grid_RRFS_CONUS_25km_ics_FV3GFS_lbcs_RAP_suite_HRRR test failed on Hera Intel. Finally, due to system issues on Orion, the automated testing failed to even initialize on the machine yesterday.

These are the tests that seem to constantly fail for those given platforms, so I have kicked off the Jenkins testing on Orion this morning (whatever was ailing Orion yesterday seems to be better now - the testing phase has already started), and once they complete, I will move forward with merging this work into develop.

@danielabdi-noaa
Copy link
Collaborator Author

@MichaelLueken Thanks for looking into the issues. Maybe we should remove these tests from the list at least until they become reliable enough to yield greens. I excluded some nco_* and get_HPSS tests from the original coverage list for this particular reason.

@MichaelLueken
Copy link
Collaborator

@MichaelLueken Thanks for looking into the issues. Maybe we should remove these tests from the list at least until they become reliable enough to yield greens. I excluded some nco_* and get_HPSS tests from the original coverage list for this particular reason.

@danielabdi-noaa This is a good idea.

Hopefully the two verification failures will be corrected by PR #683. The get_from_NOMADS test seems to fail depending on when the test is submitted (seems to have issues pulling the necessary ICs and LBCs from NOMADS). The nco_grid_RRFS_CONUS_3km_ics_FV3GFS_lbcs_FV3GFS_suite_GFS_v15_thompson_mynn_lam3km test is the one that isn't clear why it is failing. No useful information is added to the log, further complicating the issue.

@MichaelLueken
Copy link
Collaborator

@danielabdi-noaa All tests on Orion successfully passed. When the Jenkins tests were kicked off for Orion, it looks like it attempted to kick off Hera tests too, leading to the aborts. Will now merge this work.

@MichaelLueken MichaelLueken merged commit 49564ba into ufs-community:develop May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
run_we2e_coverage_tests Run the coverage set of SRW end-to-end tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add 3DEnVar analysis jobs/scripts/tasks
6 participants