ShunLiu-NOAA / regional_workflow

Other
0 stars 0 forks source link

change rrfs_p1 directory structure and file naming convention #84

Closed ShunLiu-NOAA closed 2 years ago

ShunLiu-NOAA commented 2 years ago

Hi Shun and Jacob,

[cc'ing Ben as well for any additional input]

I'm resending this since Jacob let me know emails sent around midday weren't being received.

Before I email the verification team about adding RRFS-P1 verification jobs, I want to be sure I'm pointing folks to the correct files.

Are these the correct files? /gpfs/dell1/ptmp/emc.campara/ptmp/com/RRFS_CONUS/para/RRFS_conus_3km.$PDY/[00/12]/hrrr_grid/RRFS_CONUS.tCCz.bgdawpfFFF.tm00.grib2

I remember the filenames being discussed during Monday's meeting with WPC, but I've never been able to keep all of the various NAM filenaming conventions straight.

Along those lines, if there are anticipated changes to filenames and/or directory structure in the near term, can those changes be made before we add our verification jobs? There are multiple people involved in the RRFS verification effort, and it's easiest if we limit the changes to filenames and directories once we start running our jobs.

I know the NAM-like filenames are up for being changed. I'm also wondering if we should just name some of these directories "RRFS" (instead of RRFS_CONUS) and only include CONUS in the filename - essentially like how files from the FV3LAM parallels are currently named and organized. Can we get these files and directories set up more like what we (currently) anticipate to have once RRFSv1 is in ops?

Thanks! Logan

ShunLiu-NOAA commented 2 years ago

Hi Jacob,

I'll check the 'nco' mode in the UFS SRW App with the nco standards and update the workflow if necessary next week. According to the nco standards (ver 11.0.0, 01/19/2022, pp 5-7),

  1. File names must not contain uppercase characters.
  2. Filename format for files in com:
    • non-ensemble: model.tHHz.var_info.f###.domain.format
    • ensemble: model.tHHz.ens_mem.var_info.f###.domain.format

The file name "RRFS_CONUS.tCCz.bgdawpfFFF.tm00.grib2" does not meet the above standards. It should be "rrfs.tHHz.[var_info].f###.[rrfs_conus or domain_number].grib2 I can't find whether or not it is correct to include the grid resolution in the domain name. I think it would not matter in the case that 'domain_number' is used. As far as I know, the domain number includes the grid resolution.

As you pointed out, the UPP output file names 'bgdawp' and 'bgrd3d' were changed to 'prslev' and 'natlev', respectively. Therefore, the above file name should be "rrfs_tHHz.prslev.f###.rrfs_conus_3km.grib2" or "rrfs_tHHz.prslev.3km.f###.rrfs_conus.grib2". Do you know who I should contact to confirm this? Is Rahul the right person?

Thanks, Chan-Hoo

ShunLiu-NOAA commented 2 years ago
  1. change directory structure to /gpfs/dell1/ptmp/emc.campara/ptmp/rrfsp1/para/rrfsp1.20220321/00
  2. change file name to a. rrfsp1 post product rrfs.t00z.natlev.f018.grib2 rrfs.t00z.prslev.f018.grib2 b. hrrr-grid product rrfs.t00z.natlev.f018.conus_3km.grib2 rrfs.t00z.prslev.f018.conus_3km.grib2