g2gdf.pl in GrADS1.9

[Wesley Ebisuzaki]

Eric,

    Good point; the error message needs to include this possibility.

        Wesley

Eric Altshuler wrote:
> In my own experience, this problem can even occur on a Unix/Linux box if the root partition is full. Some time ago, I was using grib2ctl.pl with no problems on a linux machine and suddenly the script began reporting errors like 'Big problem: wgrib is not on your PATH', etc. I was flabbergasted, because wgrib was on my path and the GRIB file was fine. For some reason, I got the idea to check disk usage and I discovered that the root partition was at 100% usage. I then found that grib2ctl.pl uses /tmp as scratch space, and once I cleaned out some files from /tmp, the script worked fine again.
>
> Eric
>
> ----- Original Message -----
> From: "Arlindo da Silva" <dasilva at ALUM.MIT.EDU>
> To: GRADSUSR at LIST.CINECA.IT
> Sent: Thursday, April 10, 2008 9:21:52 PM GMT -05:00 US/Canada Eastern
> Subject: Re: g2gdf.pl in GrADS1.9
>
>
> On Thu, Apr 10, 2008 at 5:36 PM, Mark Sponsler < msponsler at comcast.net > wrote:
>
>
>
>
> Bingo!
> I renamed to old version of g2ctl.pl, then placed the new version in the win32 dir.�  Set my path and then tried to invoke it� with no options, and it started fine.�  Then I added the grib file name and the perl script found it and displayed the descriptor file to the screen. Finally I tried to get it to write out a control file but I don't think I understand the command sytanx.�  Either way, it looks like you found� whatever was causing the problem.�  Congratulations!.� � �
>
> �
>
>
> Thank Wes, what you just tried is his latest! (I've been corresponding off line with Wes regarding some Win32 specific issues wth g2ctl, and what I sent you was a patched version he sent me for testing).
>
>
> Wes: indeed, you were right, there are cases in which C:\ is write protected and using TEMP did the trick.
>
>
> � �  Arlindo
> --
> Arlindo da Silva
> dasilva at alum.mit.edu
>