Thanks Mike and Dan.
I've fixed my NIDS ingest by broadening the match:
NEXRAD ^SDUS[235678]. ....
But my question was a bit of a headfake. I was more curious about why the
FNEXRAD NERXCOMP files coming from Unidata are blank, which I file with:
# png compressed 1km radar GINI format
FNEXRAD ^rad/NEXRCOMP/(...)/(...)_(........)_(....)
FILE -close nexrad/NEXRCOMP/\1/\2/\2_\3_\4
Unidata is now investigating the cause of this, as it may be related to the
NIDS product ID changes.
thanks,
-Mike
On Fri, Mar 4, 2022 at 7:17 AM Mike Zuranski <zuranski.wx@xxxxxxxxx> wrote:
> Hi Mike,
>
> First thing I would do is add 8 to your SDUS[] group, quite a few products
> are coming in under those headers. I would also check your REQUEST line to
> make sure it's not limited there either.
>
> Hope this helps,
> -Mike
>
> ======================
> Mike Zuranski
> Meteorology Support Analyst
> College of DuPage - Nexlab
> Weather.cod.edu <http://weather.cod.edu/>
> ======================
>
>
> On Fri, Mar 4, 2022 at 9:04 AM Mike Voss <mike.voss@xxxxxxxx> wrote:
>
>> Hi All,
>> For me at least, some of my NEXRAD products stopped filing correctly
>> yesterday at 18Z using this generic pattern match:
>>
>> NEXRAD ^SDUS[2357]. ....
>> ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...)
>> FILE -overwrite -close
>> nexrad/NIDS/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3
>>
>> as a test, when I changed to this:
>> NEXRAD ^SDUS66 ....
>>
>> I started getting my "N0Q" products for MUX station.
>>
>> Also, I stopped receiving the FNEXRAD NEXRCOMP products. Is it possible
>> these things are related such that the NEXRCOMP depends on the NIDS product
>> ID's and somehow a recent change (yesterday) cause this to break?
>>
>> thanks for any insights,
>> -MIke
>> _______________________________________________
>> 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.
>>
>>
>> ldm-users mailing list
>> ldm-users@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe, visit:
>> https://www.unidata.ucar.edu/mailing_lists/
>>
>
