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.
Hi Greg, re: > We are running this on sferic.eol.ucar.edu, also known as t2.eol.ucar.edu. > Prior to today I had not made any changes to the pqact_wmo.conf since around > 8/23. Any advice you could offer would be greatly appreciated. A comparison between t2.eol.ucar.edu and by idd.unidata.ucar.edu shows that the IDS|DDPLUS volumes received by each are identical. This should indicate that the problem is not in the datastream, but, rather, on your machine or in the LDM installation on your machine. re: > I'm attaching a directory listing of files we've been receiving for the > last month to illustrate what I'm talking about. We stabilized into a > routine setup around 8/23 collecting synoptic, ship and metar obs for our > upcoming DYNAMO support. For every hour starting around 8/23 there are 3 > files, a .METAR, .SHP and a .SYN . On Sept 1, the ship files stop at 02 Z > and the .SYN files get really small from 03 - 06 Z and then there is only > .METAR from 07 - 23 UTC. This pattern more or less repeats for every day > since. I've attached our ldmd.conf and our pqact_wmo.conf so you can see > what we're doing. The latter is a mess but the patterns that should govern > these files can be found in the first 10 lines of that file. > > If you look a little further down the pqact.conf (lines 18, 31, 32) > you'll also see that we are saving the .SYN and .SHP files in a different > directory. These do not show the data gaps seen in the dynamo directory. I'm > not sure why files show up in one directory and not the other. I know of no reason why two pattern-action entries that specify the exact same pattern, but FILE output to different directories should differ _unless_ there is something fundamentally different between the locations for the writes. Questions: - is data/dynamo on a different file system than data/weather/ddp? - if yes, is one on an NFS-mounted file system and the other is not? - is there a scouring action being run in the data/dynamo directory? re: > One example I > looked at was for the US research ship the Roger Revelle (KAOU) which is in > the Indian Ocean right now and reporting hourly. The header I saw in a file > that was saved in the weather/ddp directory for this ob was SNVE01 which > should have matched the pattern set up for the DYNAMO directory as well. Please verify that the following pairs of pattern-action entries illustrate your observation that the first one fails for certain hours and the second one always succeeds: WMO ^S[IMN][VW][ABCDEFJ].. .... ([0-3][0-9])([0-2][0-9]) FILE -close data/dynamo/(\1:yyyy)(\2:mm)\1\2.SHP WMO ^S.V.* .... ([0-3][[0-9])([0-2][0-9]) FILE -close data/weather/ddp/(\1:yyyy)(\1:mm)\1\2.SHP WMO ^S[IMN].... .... ([0-3][0-9])([0-2][0-9]) FILE -close data/dynamo/(\1:yyyy)(\2:mm)\1\2.SYN WMO ^S[IMN].... .... ([0-3][0-9])([0-2][0-9]) FILE -close data/weather/ddp/(\1:yyyy)(\2:mm)\1\2.SYN If/when you verify this, I will setup the exact same actions on my workstation here in the UPC and see if the same problem presents itself. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: YYT-234815 Department: Support IDD Priority: Normal Status: Open