Add Hercules build capability to GDASApp#774
Conversation
CoryMartin-NOAA
left a comment
There was a problem hiding this comment.
Looks good, thanks @RussTreadon-NOAA !
|
Just a heads up that GSI-based cycling support in the global workflow has been ported to Hercules, with the exception of the GSI-monitor. |
|
Install Install The atm_jjob tests failed because driver scripts in The test_gdasapp_soca failures appear to be similar to the Hercules and Orion share the same filesets.
While it is necessary to add Tagging @guillaumevernieres for awareness. |
|
@RussTreadon-NOAA The directory I suggest using to differentiate the two is |
|
Thank you @DavidHuber-NOAA for sharing your experience. I see that g-w After the above correction Unfortunately, I see that g-w With this change The remaining failed The only exception is The GDASApp changes needed to get atm and soca ctests to run were committed to The following g-w changes have also been made The change to The above g-w changes remain local to my working copy of g-w on hercules. Look in Running |
|
@guillaumevernieres, @AndrewEichmann-NOAA, @CoryMartin-NOAA , and @DavidHuber-NOAA : this PR is ready for merger into
An additional change would be to update the hash for the |
|
The srun error is due to a mismatch between how the job is configured via Script whereas the srun command executed by Manually add the line It is not yet clear to me how to modify |
|
the download warning must mean that the home directories are not shared between orion and hercules. If you copy the shapefiles from ~/.local/cartopy on orion to the same path on hercules (or run cartopy once in a login shell), then it should pass |
|
Thank you @CoryMartin-NOAA . I rsync'd shapefiles from my Orion cartopy directory to Hercules. Does every user their own snapshot of the shapefiles? Can we have the shape files installed in single publicly shared location? I reran Line 135 of How do we fix this? |
|
I think there's an env var one can set, @ShastriPaturi did this on Hera I think for role.jedipara. |
Thanks, @CoryMartin-NOAA . Two questions
|
|
@RussTreadon-NOAA I've copied mine to |
@CoryMartin-NOAA suggested adding quotes around The rerun of As a test remove the quotes and rerun the VRFY test. Once again the test failed with the same error message as above. The Quotes must be removed in the process of combining various source yamls into @CoryMartin-NOAA and @guillaumevernieres , is there a way to construct |
|
I am fine with merging this PR into Most soca ctests failures can be resolved by updating global-workflow. Doing so requires a separate issue and PR in g-w. How best to resolve the yaml quote issue in the soca VRFY ctest can be addressed in a future GDASApp issue. |
|
I'm perplexed by this |
Out of curiosity I installed the current head of GDASApp A check of This prompted me to rerun all The following section of I can not explain the previous failure on Hercules apart from user (ie, me) error. |
MSU Hercules is available for use. This PR adds `hercules.lua` to GDASApp `modulefiles/GDAS`. Fixes #773 --------- Co-authored-by: Cory Martin <cory.r.martin@noaa.gov>
MSU Hercules is available for use. This PR adds
hercules.luato GDASAppmodulefiles/GDAS.Fixes #773