Morning all,
On Wed, Oct 18, 2023 at 10:42 AM Pete Pokrandt <poker@xxxxxxxxxxxx> wrote:
> Daryl,
>
> I'm guessing he means to get the product info back into the metadata for
> most of the model data on the CONDUIT stream.
>
...
> If you rely on the variable or level info after that exclamation point, as
> I do for some of my product sorting, that all broke with this change.
>
> I would guess this change is to resolve that info. William, Mike, would
> you concur?
>
> Pete
>
I believe that is the intent, yes.
Best,
-Mike
*Mike Zuranski*
Data Engineer II
Unidata Program Center
University Corporation for Atmospheric Research
>
> Pete Pokrandt - System Engineer IV
> UW-Madison Dept of Atmospheric and Oceanic Sciences
> 608-262-3086 - poker@xxxxxxxxxxxx
> ------------------------------
> *From:* conduit <conduit-bounces@xxxxxxxxxxxxxxxx> on behalf of Herzmann,
> Daryl E [AGRON] <akrherz@xxxxxxxxxxx>
> *Sent:* Wednesday, October 18, 2023 10:25 AM
> *To:* CONDUIT Users List <conduit@xxxxxxxxxxxxxxxx>; William Boll - NOAA
> Federal <william.boll@xxxxxxxx>
> *Cc:* _NWS NCEP NCO Dataflow <nco.dataflow@xxxxxxxx>
> *Subject:* Re: [conduit] CONDUIT Insert Tables Update
>
> Hi William,
>
> Curiosity always kills my cat... Could you kindly and briefly further
> describe what this change means? "variables to be defined in the LDM
> queue" doesn't ring any bells for me as to what this change means.
> Modifying product names can certainly be very impactful to downstream users.
>
> daryl
>
> ________________________________________
> From: conduit <conduit-bounces@xxxxxxxxxxxxxxxx> on behalf of William
> Boll - NOAA Federal via conduit <conduit@xxxxxxxxxxxxxxxx>
> Sent: Wednesday, October 18, 2023 7:21 AM
> To: CONDUIT Users List
> Cc: _NWS NCEP NCO Dataflow
> Subject: [conduit] CONDUIT Insert Tables Update
>
> Attention CONDUIT Users,
>
> Beginning on October 23, 2023 at 1500z, NCO Dataflow will make an update
> to the LDM insert tables on our CONDUIT systems. This will allow for
> individual variables to be defined in the LDM queue for the data products .
> We are not expecting any impacts to downstream users. If however you do
> encounter issues, please report them to NCO Dataflow (
> ncep.pmb.dataflow@xxxxxxxx<mailto:ncep.pmb.dataflow@xxxxxxxx>) as soon as
> possible.
>
>
> Thank You,
> William
>
> --
> Dataflow Team Lead (Acting)
> NCEP Central Operations
> College Park, Maryland 20740
> (240)-736-8261
>
> _______________________________________________
> 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
> conduit@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> https://www.unidata.ucar.edu/mailing_lists/
>
