-
Notifications
You must be signed in to change notification settings - Fork 13
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 RDASApp submodules to match mpasjedi-v3.0.1 #194
Conversation
use the mpasout files
changes related with: invariant.nc, VEGPARM.TBL, mpasout
restart -> mpasout static.nc -> invariant.nc zero padding: 2 -> 3
update ioda-data, merge the latest develop and then match them to mpasjedi.v3.0.1
mpas-jedi test: 90% tests passed, 6 tests failed out of 59 Label Time Summary: Total Test time (real) = 112.89 sec The following tests FAILED: |
fv3-jedi test: 92% tests passed, 10 tests failed out of 127 Label Time Summary: Total Test time (real) = 155.42 sec The following tests FAILED: |
NOTE:
Fix file changes were sync'ed on Jet/Hera/Orion/Hercules and archived to HPSS |
@Junjun-NOAA For you failed mpas-jedi tests, I guess it may be related to the CRTM source code version. Could you try a test by update |
@Junjun-NOAA For the failed fv3-jedi cases, you can try the following steps:
Thanks! |
|
Not yet. Hera is very slow today. |
Thanks @Junjun-NOAA for running both RDASAPP mpasjedi tests and the mpas-bundle ctests. The test results are at the following two locations respectively: We compared all submodules and data directories under RDASApp and mpas-bundle-v3.0.1: |
Thanks @Junjun-NOAA and @guoqing-noaa for the additional testing. I think your analysis shows that this one small difference is pretty minor and not worth worrying about at the moment. But at least we have a record if we ever want to go back and figure out what is going on. |
PASSED on hera started build_and_test on hera at UTC time: Wed Oct 16 17:54:54 UTC 2024
workdir: /scratch1/NCEPDEV/fv3-cam/rrfsbot/PRs_RDASApp/194 |
ctest takes 35919.88 sec. Is it an issue related to HPC? |
Those ctest times include waiting time in the queue. Hera has been quite slow for me recently so I am guessing that is the problem. Typically the longest ctest is the GETKF solver which takes about ~20 minutes of actual runtime (it will be reduced to ~10 min after we can use |
Part of the increased wait time too is probably due to requesting 30 min for the mpas-jedi ctests. The increased wall time is really only needed for the GETKF solver so I plan to tune those a bit better whenever I update the OOPS hash (after this PR is merged). |
@ShunLiu-NOAA Yes, as @SamuelDegelia-NOAA mentioned, this was because Hera was known to have a very long job waiting time recently. The ctests themselves don't have any issues. |
Thanks for the thought. I don't think 10 minutes vs 30 minutes will make any evident differences in RDHPCS, :) |
I wouldn't think so, but 5 min vs 30 min is currently making a big difference. The fv3-jedi tests that request 5 min here are not waiting at all and run within a few minutes. But the mpas-jedi tests that request 30 min are waiting much much longer. |
Good to know. If it helps, you may go ahead to make the changes. Thanks. |
I plan to wait until we update the OOPS hash further. We'll need to do that first to get the lower run times for GETKF (via |
@hu5970 Do you get a chance to review this PR? |
@ShunLiu-NOAA @hu5970 Do we still lingering issues on this PR? Otherwise, we should consider merging this PR. Thanks! |
@guoqing-noaa I will ask the team on this PR tomorrow and try to arrange an order to merge the PRs. |
Shun and I talked about this review and the problem solved.
List of submodule changes. issue #193