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.
Michael, Garp doesn't create local config directories, but you may have had a script wrapper for a case study or other use that set the environmental variable $GARP_PATH to be the user's or case studies own instead of that of the $NAWIPS/ tree. Steve Chiswell >From: Michael Brennan <address@hidden> >Organization: UCAR/Unidata >Keywords: 200501111946.j0BJkOv2005106 >Hi Steve, > >We have an older version of GEMPAK set up by someone else (on Solaris) >that when you first use it creates a "config" directory in that >particular user's home directory. This gives the user local control >over their Garp Defaults file, etc. However, in the later versions I've >installed on Linux, this doesn't occur, and the Garp Defaults file >everyone uses resides in the $GARPHOME/config directory, which is owned >by root. I'm unsure how to change this. Is there a way to give users >local control over their Garp configuration to view case studies for >research, etc.? > >Thanks, >Mike >-- >Michael J. Brennan >Graduate Research Assistant >Department of Marine, Earth and Atmospheric Sciences >North Carolina State University >Email: address@hidden >Phone: (919) 515-1447 > -- 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.