Kevin,
Thanks for the quick response. I recompiled setting MAXLVL0.
Hopefully, that takes care of it. However, I won't know for sure till
Katy tries gdvint again(it's only 8:10 AM on the West Coast).
James
----------------------------------------------
James Murakami
Staff Meteorologist/Student Affairs
Department of Atmospheric and Oceanic Sciences
University of California, Los Angeles
405 Hilgard Ave.
Los Angeles, CA 90095-1565
e-mail: tenki@xxxxxxxxxxxxxx
telephone: 310-825-2418
Fax: 310-206-5219
----------------------------------------------
Kevin R. Tyle wrote:
Hi James,
Oops, it is not vicmn.cmn, it is viprm.prm that sets the value of
MAXLVL :)
I think the simplest thing would just be to explicitly set the
numerical value of MAXLVL in that file--i.e., change it from 65 to a
higher value
(no higher than 500).
--Kevin
______________________________________________________________________
Kevin Tyle, Systems Administrator **********************
Dept. of Earth & Atmospheric Sciences ktyle@xxxxxxxxxxxxxxxx
University at Albany, ES-235 518-442-4578 (voice)
1400 Washington Avenue 518-442-5825 (fax)
Albany, NY 12222 **********************
______________________________________________________________________
On Tue, 19 Aug 2008, James Murakami wrote:
Hi Kevin,
I looked at $GEMPAK/source/programs/gd/gdvint/vicmn.cmn, and that
file placed no numerical value to MAXLVL (for me to alter). I did
find the value 500 for LLMXLV in $GEMPAK/include/GEMPRM.PRM, but I'm
unsure what value to change it to (have no experience with this sort
of thing). Can you please advise me with more specifics(we're using
GEMPAK5.11.1, by the way)? I don't want to recompile and find out
I've made things worse.
Thanks for offering to help Katy with this problem. I manage the
GEMPAK installation/care, but for years I've depended on Unidata(i.e.
Chiz) to help with any problems(my programming skills are virtually
nil).
James
