Skip to content
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

Halo File Inconsistency Issue between JEDI and HAFS #11

Open
XuLu-NOAA opened this issue Jun 27, 2024 · 0 comments
Open

Halo File Inconsistency Issue between JEDI and HAFS #11

XuLu-NOAA opened this issue Jun 27, 2024 · 0 comments
Assignees

Comments

@XuLu-NOAA
Copy link
Collaborator

XuLu-NOAA commented Jun 27, 2024

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.
image

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:
image

@XuLu-NOAA XuLu-NOAA self-assigned this Jun 27, 2024
This was referenced Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant