Cold starting from history files

[MarcusGDaniels]

Hi,

I'd like to create initial conditions for a run using like these..

https://nomads.ncep.noaa.gov/pub/data/nccf/com/gfs/v16.3/gdas.20230814/00/atmos/

https://nomads.ncep.noaa.gov/pub/data/nccf/com/gfs/v16.3/gdas.20230814/00/atmos/gdas.t00z.atmf006.nc
https://nomads.ncep.noaa.gov/pub/data/nccf/com/gfs/v16.3/gdas.20230814/00/atmos/gdas.t00z.sfcf006.nc

When I do this using a script like this..

export DATA=/lustre01/vol0/4553vn/workdir/gfs-rot/2023032700/output
rm -fr $DATA

export HOMEufs=/lustre01/vol0/4553vn/workdir/src/global-workflow/sorc/ufs_utils.fd
export CRES=384
export FIXfv3=${HOMEufs}/fix/fix_fv3/C384
export COMIN=/lustre01/vol0/4553vn/workdir/gfs-rot/2023032700/gdas.20230327/00/atmos/

export ATM_FILES_INPUT='gdas.t00z.atmf006.nc'
export SFC_FILES_INPUT='gdas.t00z.sfcf006.nc'
export VCOORD_FILE=${HOMEufs}/fix/fix_am/global_hyblev.l64.txt
export INPUT_TYPE='history'
export MOSAIC_FILE_INPUT_GRID="${FIXfv3}/C384_mosaic.nc"
export OROG_DIR_INPUT_GRID=${FIXfv3}
export OROG_FILES_INPUT_GRID='C384_oro_data.tile1.nc","C384_oro_data.tile2.nc","C384_oro_data.tile3.nc","C384_oro_data.tile4.nc","C384_oro_data.tile5.nc","C384_oro_data.tile6.nc'
export TRACERS_TARGET='"sphum","liq_wat","o3mr"'
export TRACERS_INPUT='"spfh","clwmr","o3mr"'

export CDATE=2023032700

export OMP_NUM_THREADS_CY=1

export APRUN="mpirun -np 6"

${HOMEufs}/ush/chgres_cube.sh

.. it runs for a while and then I get this error. I added the print statements with "..input:" to compare what it wanted with what I gave it.

 - READ INPUT ATMOS DATA FROM TILED HISTORY FILES.
 - READ INPUT ATMOS DATA FROM TILED HISTORY FILES.
 - READ INPUT ATMOS DATA FROM TILED HISTORY FILES.
 - READ INPUT ATMOS DATA FROM TILED HISTORY FILES.
 - READ INPUT ATMOS DATA FROM TILED HISTORY FILES.
 **idim_input:        1536 jdim_input:         768 i_input:         384 j_input:
         384**
 - FATAL ERROR: DIMENSION MISMATCH BETWEEN SFC AND OROG FILES.
 - IOSTAT IS:            2
 idim_input:        1536 jdim_input:         768 i_input:         384 j_input:

This seems to say that I need to generate new OROG files. Is that right, and is there any guidance on how to do this?

Thanks,

Marcus

[gspetro-NOAA]

Hi Marcus,

It looks like the DIMENSION MISMATCH error is occurring in atm_input_data.F90. You may need to use a different orog file, but we need to get in touch with a UFS_UTILS subject matter expert before we can provide further advice. We're looking into this though and hope to have a more actionable answer to you soon.

Best,
Gillian Petro

[MarcusGDaniels]

I found that what I really wanted was possible by getting the development branch of UFS_UTILS and using the gaussian_cdf input type. Another error that is possible is to use the wrong number of atmospheric levels. For example, forgetting that GFS switched from 64 to 128 levels.

[gspetro-NOAA]

Glad to hear you were able to figure it out on your own! It sounds from our SME like updating to the UFS_UTILS HEAD of develop and using gaussian_netcdf is indeed what you should do when your orography file is already the same resolution as the surface file you want to create. In cases where the orography file is not the same resolution as the surface file you want to create, you can run the make_hgrid utility to create a new orography file (docs here).