-
Notifications
You must be signed in to change notification settings - Fork 180
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
Add ufs_da to checkout, build, and link #529
Comments
Create feature/ufsda as a copy of develop at dd03ed0. |
Test b3e8156 on orion and hera as follows:
sorc/ufs_da.fd was created and populated by checkout.sh. build_all.sh executed build_ufs_da.sh which built applications in ufs_da.fd. Note that at present ufs_da.fd can only be built on orion and hera. UFS-DA modulefiles of machines will be added at a later date. It is unlikely modulefiles will be created for WCOSS_C or WCOSS_D since these machines will be decommissioned the summer of 2022. link_workflow.sh linked ufsda executables to the exec directory. There may be other files (e.g., parm, fix, yaml, scripts, etc) which should be linked or copied from ufsda.fd to specific workflow directions. If so, let me know what needs to be added. The fv3jedi executables in the exec directory were not tested. ctests may be run from the ufs_da.fd directory. This will be done and reported in a subsequent comment in this issue. |
UFS-DA ctests have been run on Orion and Hera. Some reminders regarding the user environment before running ctest
All ctests run on Orion passed
3 ctest failed on Hera. 1000 passed.
JEDI-T2O PR #5 reports similar findings from others developers on Orion and Hera. Interestingly, when ctests were previously run on Hera the following three tests failed
The first two ctest failures are identical from both runs. The last ctest failure differs between today's run and the previous run (12/2/2021). It would be worthwhile to dig a bit deeper into these failures. |
Cory noted that the 3 failures on Hera may be due to issues with the user environment, sample data, or test. Since all tests pass on Orion, it's not the best investment of time at present to dig into the three Hera failures. A better use of time would be to understand the inputs and outputs needed to run FV3-JEDI 3DVar or hybrid-3DEnVar. Good advice! Doing so keeps this project moving foward. |
ufsda branch cleanup
|
#521 is already closed. I'll close this issue as well. New issues can be opened as needed. |
This issue is opened to document the addition of UFS-DA from NOAA-EMC/JEDI-T2O into NOAA-EMC/global-workflow. This addition is in support of the goals stated in the JEDI Prototype 3DVar Cycling Capability project.
The text was updated successfully, but these errors were encountered: