_______________________________________________One more update - this change affects 0.5 and 0.25 deg GFS also, but because my pqact lines for those resolutions looked like
CONDUIT ^data/nccf/com/gfs/prod/gfs.20(..)(..)(..)/(..)/.*pgrb2.0p50.f(...)
the .* saved me and the data came through.
Just FYI
Pete
-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086 - address@hidden
From: Pete Pokrandt <address@hidden>
Sent: Monday, March 22, 2021 11:55 AM
To: address@hidden <address@hidden>; address@hidden <address@hidden>; Pete Pokrandt <address@hidden>
Subject: Re: Change to string to caputure 1 deg GFS after v16 upgradeOk, so I am an idiot and fixed it wrong, and sent it out before I tested it. That pqact entry below has the atmos in the wrong place.. It actually goes after the model run hour and right before the actual file name.
#CONDUIT data/nccf/com/gfs/prod/gfs.20([0-9][0-9])([0-9][0-9])([0-9][0-9])/../gfs.t(..)z.pgrb2.1p00.f(...)\ !grib2.*FILE /data/grib2/gblav.\1\2\3\4_F\5CONDUIT data/nccf/com/gfs/prod/gfs.20([0-9][0-9])([0-9][0-9])([0-9][0-9])/../atmos/gfs.t(..)z.pgrb2.1p00.f(...)\ !grib2.*FILE /data/grib2/gblav.\1\2\3\4_F\5
Here are some examples from ldmadmin watch from before and after the change:
OLD data/nccf/com/gfs/prod/gfs.20210320/12/gfs.t12z.pgrb2.1p00.f261 !grib2/ncep/GFS/#000/202103201200F261/CWTR/1 - HYBL!NEW data/nccf/com/gfs/prod/gfs.20210322/12/atmos/gfs.t12z.pgrb2.0p25.f207 !grib2/ncep/GFS/#000/202103221200F207/OZMR/1000 hPa PRES!
Sorry for the miscue..Pete
-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086 - address@hidden
From: conduit <address@hidden> on behalf of Pete Pokrandt via conduit <address@hidden>
Sent: Monday, March 22, 2021 11:41 AM
To: address@hidden <address@hidden>; address@hidden <address@hidden>
Subject: [conduit] Change to string to caputure 1 deg GFS after v16 upgradeAll,
I just noticed that we didn't get/save any of the 12 UTC GFS on the 1 degree grid starting with this morning's 12 UTC run. Thankfully I had an ldmadmin watch -f conduit going so I could see that the data was actually coming through, it was just that the file name strings that I was keying on had changed a bit. The new data have the string 'atmos' after 'prod'.
Here's an example of what the change looks like in my pqact, in case it helps anyone else.
#OLD pre-3/22/2021 12 UTC v15 GFSCONDUIT data/nccf/com/gfs/prod/gfs.20([0-9][0-9])([0-9][0-9])([0-9][0-9])/../gfs.t(..)z.pgrb2.1p00.f(...)\ !grib2.*FILE /data/grib2/gblav.\1\2\3\4_F\5
# NEW post 3/22/2021 12 UTC v16 GFSCONDUIT data/nccf/com/gfs/prod/atmos/gfs.20([0-9][0-9])([0-9][0-9])([0-9][0-9])/../gfs.t(..)z.pgrb2.1p00.f(...)\ !grib2.*FILE /data/grib2/gblav.\1\2\3\4_F\5#
Pete
-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086 - address@hidden
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web. Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.
conduit mailing list
address@hidden
For list information or to unsubscribe, visit: https://www.unidata.ucar.edu/mailing_lists/