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.
>From: John Merrill <address@hidden> >Organization: UCAR/Unidata >Keywords: 200106041817.f54IHUp17276 >Hello, > In trying to get started with nmap2 I got further than expected. We are >using gempak 5.6a, and I was able to use ntl to launch nmap. (I used nmap, >not nmap2, inadvertently.) Loaded some metar data and tried "product >generation," which I accomplished with very ham-handed results. I quit and >went home. When next I tried this I go the message that "product >generation is already in use or a pre-existing nmap error needs to be >cleared." There is no evidence that there is a process in use, and the >clearing command, cleanvgf, is not found on our system or in the archive >of gempak messages. Suggestions will be welcomed. I could not find a >window other than the unix command window in which the ntl session was >running in which to type. Perhaps there is a window as part of the nmap >system which has escaped by glance... John > > >John Merrill Telephone: 401-874-6715 >Graduate School of Oceanography, URI Fax: 401-874-6898 > > > > John, The $NAWIPS/bin/scripts/cleanvgf script is below: [283]chiz on flip --> cat $NAWIPS/bin/scripts/cleanvgf #!/bin/csh # # CLEANVGF # # This script removes the working VGF file from the current directory. # ## # Log: # S. Jacobs/NCEP 4/98 # rm -f .DEFAULT.vgf .UNDO.vgf All it does is remove the 2 hidden files from your directory. You should then be able to launch the product generation. The files allow you to retrieve work in progress and undo the last action performed. Usually they aren't a problem, but they can get corrupted- and then have to be removed. The Gemenviron script does add the $NAWIPS/bin/scripts/ directory to you path. If you set you path later after sourcing the Gemenviron script, then you can add that directory as well. I searched the 5.6.A tarfile to make sure that the scripts directory is there: gunzip -c ~gbuddy/nawips-5.6/gempak_upc5.6.a.tar.gz | tar tvf - bin/scripts rwxr-sr-x 500/2000 dir Nov 8 13:03 2000 bin/scripts/ rwxr-xr-- 500/2000 1518 Oct 17 15:02 2000 bin/scripts/cleanup rwxr-xr-x 500/2000 165 Oct 18 11:11 2000 bin/scripts/cleanvgf rwxr-xr-x 500/2000 57 Nov 8 13:02 2000 bin/scripts/find_nowrite rwxr-xr-x 500/2000 554 Feb 8 11:09 1999 bin/scripts/get.csh rwxr-xr-- 500/2000 520 Oct 18 11:09 2000 bin/scripts/killx rwxr-xr-x 500/2000 36 Sep 23 10:40 1994 bin/scripts/rmnfs rwxr-xr-x 500/2000 723 Jan 5 13:42 2001 bin/scripts/rmque rwxr-xr-x 500/2000 2773 Sep 23 06:58 1994 bin/scripts/search rwxr-xr-x 500/2000 10557 Jul 14 14:14 2000 bin/scripts/searcher rwxr-xr-x 500/2000 10557 Oct 16 15:07 2000 bin/scripts/searcher_sol rwxr-xr-x 500/2000 377 Dec 6 14:34 2000 bin/scripts/chmod_noread If you are missing the script, then just clip out the above lines and save to cleanvgf and set the appropriate executable modes. Steve Chiswell