Incorrect Location/Naming Convention for $snoprv in gfssfcanl and gdassfcanl jobs #978
Description
This bug was reported by @RussTreadon-NOAA in #905.
Expected behavior
For a particular cycle, say 2022060200, and for gfssfcanl
snoprv=$DMPDIR/gdas.20220601/18/atmos/gdas.t18z.snogrb_t1534.3072.1536
or perhaps
snoprv=$DMPDIR/gfs.20220601/18/atmos/gfs.t18z.snogrb_t1534.3072.1536
The way the script is written presently suggests gdas data should be used regardless of whether this is a GFS or GDAS task. I'm not sure of the intent.
Current behavior
snoprv=$DMPDIR/gfs.20220602/00/atmos/gfs.t18z.snogrb_t1534.3072.1536
This causes CYCLVARS=FSNOL=-2., when it should be CYCLVARS=FSNOL=99999.,FSNOS=99999.,.
Machines affected
At least S4 and Orion.
To Reproduce
Run a gfssfcanl or gdassfcanl job.
Context
Detailed Description
See Russ's post for more details.
Additional Information
Possible Implementation