|
Re: idl path issue [message #81471 is a reply to message #81469] |
Thu, 20 September 2012 10:04  |
Paul Van Delst[1]
Messages: 1157 Registered: April 2002
|
Senior Member |
|
|
The easy question first:
Is the file called
createSpecProFiles.pro
or
createspecprofiles.pro
?
For the IDL automatic-location-of-files-in-the-path to work, the
filename should be all lowercase (on linux at least... dunno if you have
a windows machine).
E.g.:
$ cat > aTest.pro
pro aTest
print, "hello world"
end
^D
$ idl
IDL Version 8.2 (linux x86 m32). (c) 2012, Exelis Visual Information
Solutions, Inc.
IDL> aTest
% Attempt to call undefined procedure/function: 'ATEST'.
% Execution halted at: $MAIN$
IDL> .compile aTest
% Compiled module: ATEST.
IDL> aTest
hello world
IDL> exit
$ mv aTest.pro atest.pro
$ idl
IDL Version 8.2 (linux x86 m32). (c) 2012, Exelis Visual Information
Solutions, Inc.
IDL> aTest
% Compiled module: ATEST.
hello world
cheers,
paulv
On 09/20/12 12:05, sdjohnson.mail@gmail.com wrote:
> Hi all,
>
> I am encountering a very strange problem with my idl path. I created
> a procedure and placed it in a directory that is in my path. When I
> open a new idl session and try to run the program, IDL throws an
> undefined procedure error. However, I can manually compile the
> procedure with a .compile and then run it just fine. The terminal
> session is pasted below. Also note that other procedures in my path
> seem to compile just fine automatically.
>
> In fact, I have this problem with *any* procedure that I write and
> place in my path. However, procedures written by others don't give me
> any trouble (coyote library, goddard astronomy library, xidl, etc).
> Has anyone else encountered a similar issue? Any tips would be
> greatly appreciated!
>
> Thanks,
>
> Sean
>
> IDL> createSpecProFiles % Attempt to call undefined
> procedure/function: 'CREATESPECPROFILES'. % Execution halted at:
> $MAIN$ IDL> .compile createSpecProFiles % Compiled module:
> FORMATSLITNUMBER. % Compiled module: CREATESPECPROFILES. IDL>
> createSpecProFiles % Compiled module: MRDFITS. % Compiled module:
> FXPOSIT. % Compiled module: MRD_HREAD. % Compiled module: SXPAR. %
> Compiled module: FXPAR. % Compiled module: GETTOK. % Compiled module:
> VALID_NUM. MRDFITS: Image array (2947,150,6) Type=Real*4 % Compiled
> module: MRD_SKIP. MRDFITS: Image array (2947,5020) Type=Real*4
> MRDFITS: Image array (2947,5020) Type=Real*4 NCOLUMNS LONG
> = 2947 % Compiled module: NUMBER_FORMATTER. % Compiled
> module: REPSTR. % Compiled module: MWRFITS. % Compiled module:
> FXADDPAR. % Compiled module: DETABIFY. % Compiled module: FXPARPOS. %
> Compiled module: SXADDHIST. % Compiled module: FAN. % Program caused
> arithmetic error: Floating divide by 0 IDL>
|
|
|
Re: idl path issue [message #81472 is a reply to message #81471] |
Thu, 20 September 2012 09:58  |
David Fanning
Messages: 11724 Registered: August 2001
|
Senior Member |
|
|
sdjohnson.mail@gmail.com writes:
> I am encountering a very strange problem with my idl path. I created a procedure and placed it in a directory that is in my path. When I open a new idl session and try to run the program, IDL throws an undefined procedure error. However, I can manually compile the procedure with a .compile and then run it just fine. The terminal session is pasted below. Also note that other procedures in my path seem to compile just fine automatically.
>
> In fact, I have this problem with *any* procedure that I write and place in my path. However, procedures written by others don't give me any trouble (coyote library, goddard astronomy library, xidl, etc). Has anyone else encountered a similar issue? Any tips would be greatly appreciated!
Has the file been saved in all lowercase characters?
http://www.idlcoyote.com/code_tips/mostcommon.html
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|