UFS-dev PR#27 #81
UFS-dev PR#27 #81
Conversation
* adding hr_ave_chem_v1 * aqm diag_table changes Co-authored-by: Brian Curtis <brian.curtis@noaa.gov> Co-authored-by: JONG KIM <jong.kim@noaa.gov>
* removed control_2dwrtdecomp, control_fhzero, control_2threads_debug
…unity#1514) * Update Jenkinsfile * Update ci.test * add a mixed-mode test Co-authored-by: zach1221 <99902696+zach1221@users.noreply.github.com> Co-authored-by: JONG KIM <jong.kim@noaa.gov> Co-authored-by: Rahul Mahajan <aerorahul@users.noreply.github.com> Co-authored-by: Brian Curtis <brian.curtis@noaa.gov> Co-authored-by: jkbk2004 <jkbk2004@gmail.com>
…munity#1518) * Performance optimization of moving nest. * Turn on HAFS RTs on WCOSS2 and switch to use the netcdf (instead of netcdf_parallel) write_grid_component option for HAFS RTs. * Update submodule FV3, which points to latest UPP develop branch. * Update submodule FV3, which will only call atmosphere_fill_nest_cpl at the cap driver time steps (coupling time steps) * Adding upoff as a namelist parameter * Update submodule HYCOM after the momentum flux fix for HAFS FV3ATM-HYCOM coupling. * Update submodule FV3 and rename HAFS_V0 CCPP physics suites into HAFS_V1. * Cleanup of CMakefile for moving nest, and added fv_timers namelist option Co-authored-by: William Ramstrom <William.Ramstrom@noaa.gov> Co-authored-by: Biju Thomas <biju.thomas@noaa.gov> Co-authored-by: Brian Curtis <brian.curtis@noaa.gov> Co-authored-by: jkbk2004 <jong.kim@noaa.gov>
|
Contains changes from #79 and #80 until those are merged. Also ufs-community#1505, ufs-community#1513, ufs-community#1525, ufs-community#1514 (all not related to CCPP) |
|
New baselines needed for HAFS-related RTs. |
|
Baselines also changed in ufs-community#1513 |
|
ufs-community#1514 adds a new RT too |
dustinswales
removed
cheyenne-gnu-RT
hera-gnu-RT
cheyenne-intel-RT
hera-intel-RT
labels
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
|
@dustinswales It looks like the expected RTs fail (HAFS, mixed-mode, and atmaq tests). I'll change BL_DATE in rt.ncar.sh and add the BL labels. |
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
on-behalf-of @NCAR <dswales@ucar.edu>
|
Automated RT Failure Notification |
|
FYI, @dustinswales I'm trying something new. To get around the failed BL creation, I changed the BL_DATE in rt.ncar.sh to 20221230a rather than 20221230 so that it will create a different folder and not error about the dir already existing. This is a workaround for me not being able to delete files in your space manually. If this works, you'll just need to manually copy the new BLs from the 20221230a directory to the 20221230 directory and I'll revert the BL_DATE back to 20221230 when I revert the WLCLK changes. |
|
Automated RT Failure Notification |
@grantfirl Sorry, I thought I changed the permissions for you to be able to write (I'll check on this) But this seems like a good idea. |
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
|
@grantfirl Looks like that "a" suffix causes problems: We're almost there... All the tests pass except Cheyenne Intel. I cleaned up that directory (/glade/scratch/epicufsrt/GMTB/ufs-weather-model/RT/NCAR/main-20221230/INTEL). Whenever you get a chance revert the BL_DATE change and kick off a new cheyenne-intel-BL. |
on-behalf-of @NCAR <dswales@ucar.edu>
|
Automated RT Failure Notification |
|
@grantfirl It looks like the test worked, but also failed? |
Ya, it's been spitting out error messages to GitHub even after successful RTs. I don't know how it could detect failure on removing the label, because that was successful too. I think that we should be good to go ahead and merge this and try to figure out the failure messages afterward? If you agree, please approve this and the fv3atm PR so that we can merge. |
Identical to ufs-community#1518