The issues with NOAAPort Volumes have not ceased... According to Carissa, it's a WFO requesting retransmits..
Fortunately while I'm on vacation, I have scripts that automatically inspect various model data, to ensure all necessary fields are present before runs commence... what is happening is fairly weird.. With RAP for example, files can look 'close' to normal size, yet all fields are not present... So the script does a head -2 | tail -1 .. then a head -3 and a head -4 etc.. and sometimes we have to go back 5 runs to find files that contain all the parms!
Here is the latest NOAAPort volume chart.. the right side is new, and notice this peak at around 6.15pm or so (central) today, and 00.15 central sunday, and so forth.. so there is a discernible trend of nefarious activity.
Hopefully someone is working on the problem somewhere?
Merry Christmas!
------ Original Message ------
Sent: 12/15/2016 10:15:16 AM
Subject: NAM Kerfluffle
Rather serious errors transpired with NOAAPort NAM over the evening, and continues into this morning... this graphic contains 2 columns of nam directory listings... note that bot 12z and 06z runs contain errors.. what is interesting is that some hours report as 0 bytes (yet they still report), however other hours contain... well, several hour's worth of runs?
this box has redundant independent direct noaaport feeds (2 dishes, 2 novras, both feeding etc..)
worried! .... :)
--patrick
_______________________________________________
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:
http://www.unidata.ucar.edu/mailing_lists/
