[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

19991222: GEMPAK question regarding MMPARM in gemprm.HPUX

Jon,

When you recompiled all of GEMPAK- did you remove all of the gempak
libraries before recompiling? If not, the common blocks would
be all messed up. If not, make sure you blow them away first.

Steve Chiswell
Unidata User SUpport


On Tue, 21 Dec 1999, Jonathan Case wrote:

> Steve,
> 
> This is Jon Case at Cape Canaveral, FL with a question on increasing MMPARM
> for surface and sounding GEMPAK files.  I am converting error statistics
> into surface and sounding GEMPAK files to view with SFGRAM, SNPROF, etc.
> Here's the problem that I run into.  I modified the snmerg.pack file to
> include the parameters that I want to display.  The total number of
> parameters is 43, which exceeds the original MMPARM limit in the gemprm
> file.  So, we have increased this number to 80 and recompiled all of GEMPAK.
> 
> 
> Once this was done, I was able to create a surface/sounding file and
> successfully write my data into the file with iret = 0 for all subroutine
> calls.  Unfortunately, I received the following error message when I try to
> run SNLIST on the sounding file created:
> 
> [SNLIST -9] No stations reported at these times.  
> 
> I did not change anything else except increase the number of parameters in
> the .pack file.  The GEMPAK programs will run fine as long as the number of
> parms is under 40, despite the fact that we recompiled with a new MMPARM
> value.  
> 
> Any idea what may be causing this behavior?
> 
> Thanks!
> Jon
> 
> 
>  
> 
>