hafs_regional_storm_following_1nest_atm_ocn failed with debug test

[junwang-noaa]

Description

Hafs group reported that the hafs_regional_storm_following_1nest_atm_ocn test failed in debug mode. The error showed in the moving nest lat info in the module_wrt_grid_comp.F90.

To Reproduce:

From Biju:
I ran regression tests with "hafs_regional_storm_following_1nest_atm_ocn_wav" and "hafs_regional_storm_following_1nest_atm_ocn" with DEBUG flag on.

The first one (hafs_regional_storm_following_1nest_atm_ocn_wav) completed successfully, but the second one(hafs_regional_storm_following_1nest_atm_ocn) failed with the error:

forrtl: error (72): floating overflow
Image PC Routine Line Source
fv3.exe 000000000FDCDAAB Unknown Unknown Unknown
libpthread-2.31.s 000014EB7A0AF8C0 Unknown Unknown Unknown
fv3.exe 0000000005C1454B module_wrt_grid_c 759 module_wrt_grid_comp.F90

One difference I noticed between these two runs is that in the first one, the output_grid is (rotated_latlon,rotated_latlon), while in the second one, the output_grid is (regional_latlon, regional_latlon_moving).

Additional context

Output

[junwang-noaa]

The issue is in the initialization step where the moving nest domain does not have lat-lon information defined until the run step on the write grid component yet. So the assignment of output grid lat/lon should not be done until the run step.