Hello everyone,
Over the past few months, I have noticed an issue over at the College of
DuPage, and at a company I work for on the side. In our ldmd.logs, on our
NOAAport satellite ingesters only, we see something like this every 15 or 30
minutes:
Jun 6 15:46:57 sat noaaportIngester[5561] WARN: Gap in packet
sequence: 29680041 to 29680050 [skipped 8]
Jun 6 15:46:57 sat noaaportIngester[5561] WARN: Gap in packet
sequence: 29680041 to 29680050 [skipped 8]
Jun 6 15:46:57 sat noaaportIngester[5561] ERROR: Missing GOES fragment
in sequence, last 37/169677 this 46/169677
Jun 6 15:46:57 sat noaaportIngester[5561] ERROR: Missing GOES fragment
in sequence, last 37/169677 this 46/169677
Jun 6 15:46:57 sat noaaportIngester[5561] WARN: Gap in packet
sequence: 29680050 to 29680055 [skipped 4]
Jun 6 15:46:57 sat noaaportIngester[5561] WARN: Gap in packet
sequence: 29680050 to 29680055 [skipped 4]
It only happens with satellite imagery, as I see no other data losses in
both receiver's logs. This happens on LDM 6.12.6, and also on 6.12.13. It
is not consistent; that is, quite a few times the images will come in
fine. On both sites, the C/N is above 17, and signal strength is
excellent, around -37 to -39 dB. Is anyone else seeing this? I wish when
this happens, and if it's possible to parse it, we would be able to see
the WMO headers of the offending data to track this down better.
Gilbert
*******************************************************************************
Gilbert Sebenste ********
(My opinions only!) ******
Staff Meteorologist, Northern Illinois University ****
E-mail: sebenste@xxxxxxxxxxxxxxxxxxxxx ***
web: http://weather.admin.niu.edu **
Twitter: http://www.twitter.com/NIU_Weather **
Facebook: http://www.facebook.com/niu.weather *
*******************************************************************************
