| Re: Read_grib under IDL 7.0 [message #63349 is a reply to message #63335] |
Wed, 05 November 2008 04:57   |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
ray.laymon064@gmail.com writes:
> I have been using the read_grib.pro scripts of Andy Pursch (over
> ittvis user community downloads). For the past year I didn't have
> problem running it under IDL 6.3. Since the read_grib package contains
> 5 scripts, I have been compiling each script via "resolve_routine"
> commend before calling "read_grib.pro" in my scripts.
Oh, dear. It always amazes me what contortions people
go through to run IDL programs. Believe me when I say
running RESOLVE_ROUTINE is *never* necessary. (At least
I've never used it in 20+ years of IDL programming.)
> So far, I didn't have any problem, but when I tried to run the same
> script under IDL7.0 I had an error saying
>
>
> Stat = IDL_GRIB(file, Count = LCount)
> ^
> % Syntax error.
> At: /home/usr/bin/read_grib.pro, Line 612
>
> Stat = IDL_GRIB(File, Image, Dump = GetRecords[I], $
> ^
> % Syntax error.
> At: /home/usr/bin/read_grib.pro, Line 631
> % Compiled module: READ_GRIB.
> % Attempt to call undefined procedure/function: 'READ_GRIB'.
> % Execution halted at: $MAIN$ 96 /home/usr/bin/
> read_the_grib_file.pro
>
>
> And when I run the same script under IDL 6.3, (without editing a dot),
> it runs without any problem.
> Could anyone possibly help me what would be the reason?
This is simply an IDL path problem. Here is what to do.
Right click on all of your IDL projects under IDL 7
and under Properties -> IDL Project Properties turn off
the button that offers to "Update IDL path when project
is opened or closed".
When you have gotten IDL out of the business of thinking
for you, find the Preferences button and go to IDL Preferences->
Paths and start to enter the directories where you keep your
IDL files. These could be files in your projects, or just IDL
files (such as the READ_GRIB) files that you just want to have
available to you.
That's it. That's all you have to do. All of those programs
should now be found without having to do one more single thing!
(Sometimes you have to rearrange the directories in your path,
if you have files with the same name, etc. But rearranging
your path to put your directories before IDL's is about
all I've ever found necessary.)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
