You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is to document the halo file inconsistency issue between JEDI and HAFS.
Using Default C512_mosaic.nc file generated from HAFS will create inconsistency of the increments between GSI and JEDI output. The JEDI increments are shifted away from the observation location.
Issues are found in the halo files linked.
In HAFS, the default C512_mosaic.nc file uses C512_grid.tile7.halo4.nc, but the JEDI by default wants C512_grid.tile7.halo3.nc.
To fix the issue, modify the C512_mosaic.nc and link halo3.nc in the INPUT and DataFix/input_hafs.nml.
Example command to create mosaic.nc with halo3 file:
/scratch2/NCEPDEV/hwrf/save/Xu.Lu/hafsv2_merge_JEDI4D/exec/hafs_utils_make_solo_mosaic.x --num_tiles 1 --dir /scratch2/NCEPDEV/hwrf/scrub/Xu.Lu/JEDI_Fix/grid --mosaic C512_mosaic --tile_file C512_grid.tile7.halo3.nc
Now JEDI increment can be consistent with the GSI:
The text was updated successfully, but these errors were encountered:
This is to document the halo file inconsistency issue between JEDI and HAFS.
Using Default C512_mosaic.nc file generated from HAFS will create inconsistency of the increments between GSI and JEDI output. The JEDI increments are shifted away from the observation location.
Issues are found in the halo files linked.
In HAFS, the default C512_mosaic.nc file uses C512_grid.tile7.halo4.nc, but the JEDI by default wants C512_grid.tile7.halo3.nc.
To fix the issue, modify the C512_mosaic.nc and link halo3.nc in the INPUT and DataFix/input_hafs.nml.
Example command to create mosaic.nc with halo3 file:
/scratch2/NCEPDEV/hwrf/save/Xu.Lu/hafsv2_merge_JEDI4D/exec/hafs_utils_make_solo_mosaic.x --num_tiles 1 --dir /scratch2/NCEPDEV/hwrf/scrub/Xu.Lu/JEDI_Fix/grid --mosaic C512_mosaic --tile_file C512_grid.tile7.halo3.nc
Now JEDI increment can be consistent with the GSI:
The text was updated successfully, but these errors were encountered: