Manuel, > Don't worry, the faulty GRIB was not at encoding. Doug sent his version > of the field and it was correct (same as yours). > > Therefore, I have only two candidates for causing such corruption: > either LDM or the disk. Corruption could have happened when copying data > from the network into the LDM product queue or copying data from the LDM > product queue to disk. We scanned the logs but couldn't find any problem > with the disk subsystem... > > I did report the problem to Unidata support > (address@hidden), but have not heard anything from > them. I did not get the automatic e-mail that assigns a token for > incident reports. I copy them this e-mail again. The LDM relies on TCP to correctly transmit data: it doesn't do any error-detection or error-correction of its own. TCP is excellent in this regard, but it's not perfect: the probability of an incorrectly transmitted byte is extremely small -- but not zero. Can you put an upper bound on the error rate? Regards, Steve Emmerson Ticket Details =================== Ticket ID: UHK-328521 Department: Support IDD TIGGE Priority: Emergency Status: On Hold
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.