Presently, all application configuration files or parm files reside under parm/. There are mixed conventions used in identifying the applications and their associated sub-cycles; UPPERCASE, lowercase; e.g. GFS, gfs, GEFS, gefs. In some instances aerosol is used while in some other cases chem. These are just some examples. They are not exhaustive and are simply used to illustrate the point.
A proposal here is to create subdirectories under parm based on the modelname (gfs, gefs, rrfs, hafs, etc.) so that it makes it easier to locate, identify, and manage the versions of the various configuration files for these and upcoming applications.
Presently, all application configuration files or
parm
files reside under parm/. There are mixed conventions used in identifying the applications and their associated sub-cycles; UPPERCASE, lowercase; e.g. GFS, gfs, GEFS, gefs. In some instancesaerosol
is used while in some other caseschem
. These are just some examples. They are not exhaustive and are simply used to illustrate the point.A proposal here is to create subdirectories under parm based on the
modelname
(gfs, gefs, rrfs, hafs, etc.) so that it makes it easier to locate, identify, and manage the versions of the various configuration files for these and upcoming applications.