This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Art, This sounds like a previous problem with LDM 5.0.5 and earlier that was fixed long ago- but just in case, please check your LDM version. The previous problem was that for PIPE commands that handled small amounts of data (not surface, upperair etc), basically the PIPE would time out between messages and close the decoder down- but the LDM would not know that the PIPE was closed until the next time a write had to take place- at which point it would fail and start up a new pipe- but having already lost the bulletin that was trying to be written. Again, this is generally noticed in the decoders where data is sparse so that the PIPEs would be scoured by the LDM for other decoders. Since your FILE action is apparently catching all the data, we should verify that the above is not the case. Steve Chiswell Unidata User SUpport On Tue, 7 Dec 1999, Arthur A. Person wrote: > Hi... > > We are seeing intermittent incomplete decoded mrf mos reports in our > gempak files of late. The raw data seem to arrive okay... we can view > specific stations via "weather"... but not all those stations seem to > make it through the dcmmos decoder. Anyone else seeing this and/or have > any clues what might be going on? > Thanks. > > Art. > Arthur A. Person > Research Assistant, System Administrator > Penn State Department of Meteorology > email: address@hidden, phone: 814-863-1563 > >