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 Jennie, Tom here... I just wanted to blast you a quick note to let you know that Chiz is currently putting on a GEMPAK training workshop, so he is not available to get back to you at the moment. re: > I have been running a very limited version of GEMPAK on a linux box here, > was just retrieving Conduit GFS grids from the host of idd.unidata.ucar.edu. > I don't really have to have those high resolution global grids right now, > but would like to try to configure GEMPAK to get the NAM along with > satellite imagery (MCIDAS feed?) and upper-air data, maybe radar and surface > data as well (I am not sure how much space this will chew up if I only keep > a day or so?). > Anyway, will I need to get a new upstream host for these > additional data streams or can I make these requests from the host I > currently point to? You can feed from either idd.unidata.ucar.edu or idd.cise-nsf.gov. Sometime in the not too distant future, we may be asking you to request your data feeds from Penn State. Just a heads-up... > I will be trying to figure out how to change the pqact > to appropriately direct these to the GARP defined locations, but the first > question is just getting the right data feeds set up. Chiz provides pqact.conf files with the GEMPAK distribution that process data in a way that is directly usable by GEMPAK routines. What you need to do to create the GEMPAK pqact.conf files is: <login as 'gempak'> cd ~gempak -- make sure that you have setup the necessary line in the ~gempak directory and defined any/all environment variables in your shell-specific configuration file (e.g., .cshrc for the C shell; .bash_profile for BASH; etc.) $NAWIPS/ldm/etc/gen_pqact.csh <- if you are using the C shell This process is explained in the GEMPAK page: Site Configuration for Products http://www.unidata.ucar.edu/software/gempak/GEMPAK/configuration.html The gen_pqact.csh script will ask you if you want all of the actions in one file. The best answer to this is NO. Let the script create multiple files and then follow the instructions on the screen that tell you the 'exec' actions you need to add to your ~ldm/etc/ldmd.conf file. The instructions also let you know that you need to copy the just generated pqact.conf files to the ~ldm/etc directory. Also, you will need to make sure that you copy all of the GEMPAK decoders to a directory that is in the PATH of your 'ldm' user. A "typical" setup is to copy the decoders to the ~ldm/decoders directory (create the directory if it does not already exist), and make sure that this directory is included in the PATH for the user 'ldm'. If you had to add the directory to the PATH definition for 'ldm', you will need to make sure that it is active. For C shell users, this means that you: - modify the PATH setting in .cshrc - 'source' the .cshrc file: source ~ldm/.cshrc Once your PATH is correct and complete, and after you have modified the ~ldm/etc/ldmd.conf file and copied the GEMPAK pqact.conf files to the ~ldm/etc directory, you will need to stop and start (restart) your LDM: <as 'ldm'> ldmadmin stop ldmadmin start -- or -- ldmadmin restart > I am still running > the ldm6.4.4, and there is a newer version out, but I would rather wait > until classes are over before I upgrade any software. The upgrade from LDM-6.4.4 to LDM-6.4.6 is painless. I would recommend doing the upgrade before the end of the semester since this distribution contains a bugfix that may be important to you. Here is an ABC for upgrading: <login as 'ldm'> cd ~ldm ftp ftp.unidata.ucar.edu <user> anonymous <pass> address@hidden cd pub/ldm binary get ldm-6.4.6.tar.Z quit zcat ldm-6.4.6.tar.Z | tar xvf - cd ldm-6.4.6/src ./configure make make install sudo make install_setuids <- last step needs to be done as root, hence the 'sudo'. If you don't have sudo installed simply 'su' (not 'su -' to root) cd ~ldm ldmadmin stop rm runtime ln -s ldm-6.4.6 runtime ln -s runtime/* . <- this step should not be needed, but it can't hurt ldmadmin start That's it. An LDM upgrade should take you no more than 15 minutes. > thanks for you help, I am going to close this ticket in anticipation that I fully answered your question(s). If you have further questions about the same topic, please include the Support ticket ID (HXL-206768) in your next email's Subject: line. The ticket will be automatically reopened, and Chiz will be able to jump in and provide expert advice. 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: HXL-206768 Department: Support GEMPAK Priority: Normal Status: Closed