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 Carol, re: > Ah ok! So just to clarify the bug. You can't plot archived GLM data because > you can't set the DAY and TIME keyword in the GLMDISP command? Sort of, but not exactly. re: > But if you're using TIME=IMA then it shouldn't matter. The actual problem is that GLMDISP is a front end to PTDISP, and the SELECT= keyword specifies multiple days to search. The current rule for archive datasets is that the data be stored by day, and one must specify a single day. Here is the kind of output that one sees when trying to plot archive GLM group data (this test invocation is not fully fleshed out, but it wouldn't matter if it was): GLMDISP X 2 DAY=310 DAT=GOESRALL/GLMGROUP Plotting GLM data from GOESRALL/GLMGROUP.ALL pipe read: Connection reset by peer PTDISP: When using archive data you must specify SELECT= with a single DAY value PTDISP: Failed at SERVER REQUEST step GLMDISP - done The two errors that are shown are: - pipe read: Connection reset by peer This is noted in the inquiry that is open for this problem. This is somewhat of a red herring. - PTDISP: When using archive data you must specify SELECT= with a single DAY value This is because GLMDISP is putting together a SELECT= keyword clause that specifies more than one day of data, and this violates the current design of archive datasets. Aside: I will be very interested to see what approach is taken to get around the second error! re: > Yes, I'm in Argentina for RELAMPAGO. It's been very hectic here the first > week of the campaign, but Greg's been here with me, so that's been really > helpful. I think things will calm done next week. I was lucky enough to participate in the PEP project in Spain in 1980 and 1981. We were on site in central Spain for 4 months (!) each year, so I got to know a lot about Spain and come to dearly love it. Hopefully, you have enough time to do some exploring in Argentina (Mendoza area?)! re: > Another random question.... do you think it would be possible for me to go > to the McIDAS meeting next year? Or are you the only person from NCAR that > goes to those meetings? More than one site representative can go to MUG meetings, so it may be possible. The final determination would depend on whether or not the MUG (probably Becky) considers the site Unidata or UCAR/NCAR. We have always considered the site to be UCAR/NCAR, but our view is just our opinion. We'll see when the time gets nearer. 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: CLA-376903 Department: Support McIDAS Priority: Normal Status: Closed =================== 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.