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.
Mike, Ok, one simple way is to create a link from $GEMEXE/gf to $GEMEXE/gfalt and then, you can alternate between the drivers, as you mention like "ps", but still be able to get gif output. However, if you are trying to output the same gfunc for a range of times, say gdattim = f000-f048-006, then the gif driver will automatically create a different gif file for each frame, eg dev=gf will produce gempak.gif, gempak.gif.1, gempak.gif.2 etc. If all of your plotting is contained within one single program (eg you don't use sfmap to overlay the gdcntr), then you can compile a gdcntr_gf program where the gif driver is linked directly to the program. This elimiates having to establish the gplt session each time, though it does not solve the problem of having to read in your data set each time. Chiz On Fri, 29 Jan 1999, Mike Trexler wrote: > Chiz, > > Ok, this maybe be a complicated question, but her goes... > I'm trying to write a script that generates different plots (gif images) > from the same file. The script is now setup to generate the 1st > image by running gdcntr, exiting, and then running gpend, then to make > the next image it gets back into gdcntr and repeats the process. > Standard stuff, right? So I was looking for a more efficient way > to do this. It seems that it would save CPU time especially for > loading in data files if we could open gdcntr, generate the gif, > and the close the gf process without exiting gdcntr (not a big deal) > and running gpend which would be a big deal becasue it not > only closes the gif file, but purges the data from the memory when > I'm just going to turn around and reload the data into memory. > So the question is....is there someway around this, short of messing > with the source code. I've found that by changing the dev to, say > ps1, and rerunning that that will close the gif file, but this is an > expensive solution depending on the complexity of the plot. > Ideas? > > > Thanks > Mike > > -- > __________________________________________________ > ************************************************** > ****** C. Michael Trexler ****** > ****** N C State Univ. - Box 8208 ****** > ****** Dept. of Mar/Earth/Atmos. Sciences ****** > ****** Research III Rm. 100 ****** > ****** Raleigh, NC 27695-8208 ****** > ****** (919) 515-1447 Phone ****** > ****** (919) 515-1683 Fax ****** > ************************************************** > -------------------------------------------------- > ****** address@hidden ****** > __________________________________________________ > > > >