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 Jeff, re: > This is going to sound really stupid, but I thought that I did build > it from source. I followed the instructions at: > http://www.unidata.ucar.edu/software/gempak/help_and_documentation/Install_current.html If there is a lack of understanding at play, it is on my part! I did not realize that you built the 5.11.1 distribution from source. I thought that you, like most people, installed the 64-bit binary release that we make available. This is news that is unexpected. Why the dcacft, dcmetr and dcmsfc decoders were producing bad output files is now a bigger mystery than it was before. > The make.out and install.out files are still in the ~gempak/GEMPAK directory. > I > tailed the file as it was going and didn't see any errors go by, but I didn't > open > the file(s) and look through them afterwards. One of the things I don't like about the GEMPAK build process is that the build does not stop on errors (like it should). > Granted I'm used to the whole "configure, make, make install" cycle, but > assumed > that it was being combined here. Like I said early on - I know just enough > to be > dangerous! :-) My bad. I thought we were dealing with binary executables that had been built in our shop. The thinking was that there is an inconsistency (probably in the shared gcc library) between our system (Fedora 9) and yours (CentOS Enterprise 5). re: > That's not a problem. I've been using yum for awhile. I had to use that to > install the -devel libraries prior to the 5.11.1 install that I did a couple > of days ago. Very good. Well, now I am at a loss for good ideas on how to proceed. My casual and not completely informed observation is that things appear to be running at this point, but I have not tried running GEMPAK or GARP to see if there are the same kind of data "holes" as you originally reported. Can you exercise Garp and NMAP2 on whistler to see what (hopefully if anything) is missing/incorrect? We will pick-up from there after your testing. Last thing: McIDAS. Do you want to upgrade McIDAS to the latest distribution, v2008? 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: IZJ-689237 Department: Support IDD Priority: Normal Status: Closed