comp.lang.idl-pvwave archive: archive » Re: IDL Error GCPC data

Home » Public Forums » archive » Re: IDL Error GCPC data

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: IDL Error GCPC data [message #69251 is a reply to message #69250]

Thu, 24 December 2009 10:18

sampton
Messages: 8
Registered: December 2009

Junior Member

Thanks,
Yes I know that I'm missing a lot it's my first steeps with IDL ;)
As of the file name no I just want to mention that there is a binary
data file and the real name is: gpcp_v2.1_psg.1979
and the year extension changes from 1979 to 2009.
The command line I used are those contained in the pro file
(Instruction part) and yes I'll try your suggestion and see what I
get.
you suggested: .COMPILE do I have to include the file name in the
path or just the command ?
Thanks again.

On Dec 24, 12:38 pm, David Fanning <n...@dfanning.com> wrote:
> sampton writes:
>> What I use is:
>> - Type "idl" at the UNIX command prompt to start IDL.
>> - Type: .run read_v2_1_file.pro to compile the procedures.
>> - Type: read_V2_1, "Bin_DATA_FILE_NAME", "STRUC"
>> and I changed the file names inside the pro file accordingly. At the
>> end no output file is generated, I'm expecting to read a binary file
>> but no file is generated.
>> Did I miss something ?
>
> Quite a lot, actually. :-)
>
> You won't have to do step 2, with the .RUN if you
> move the read_V2_1 module to the bottom of the file and
> name the file "read_v2_1.pro".
>
> http://www.dfanning.com/tips/namefiles.html
>
> If you do include this step, .COMPILE would be a better choice,
> unless you always want to always see that printed help
> message, which I think contains inaccurate information.
>
> Then, on this command:
>
> IDL> read_V2_1, "Bin_DATA_FILE_NAME", "STRUC"
>
> Is that *really* the name of the file you want to open? That
> is an *extremely* weird name. Normally, on LINUX systems filenames
> will have all lowercase letters, unless there is some extraordinary
> reason for not doing so.
>
> In any case, you want "struct" to be a variable, not a string,
> so you don't want to put quotes around it. If that filename
> is a valid one, you probably want to call your program like this:
>
> IDL> read_V2_1, "Bin_DATA_FILE_NAME", struct
>
> This will pass the (undefined?) variable struct into the program
> in a pass-by-reference (rather than pass-by-value) way. When the
> program works, you *should* have struct defined as something that
> got read out of the file. Is that was you intend?
>
> 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.")

Report message to a moderator

[Message index]

		Re: IDL Error GCPC data By: David Fanning on Tue, 29 December 2009 11:35
		Re: IDL Error GCPC data By: sampton on Tue, 29 December 2009 11:28
		Re: IDL Error GCPC data By: sampton on Fri, 25 December 2009 09:38
		Re: IDL Error GCPC data By: David Fanning on Thu, 24 December 2009 20:21
		Re: IDL Error GCPC data By: sampton on Thu, 24 December 2009 18:29
		Re: IDL Error GCPC data By: David Fanning on Thu, 24 December 2009 11:07
		Re: IDL Error GCPC data By: sampton on Thu, 24 December 2009 10:18
		Re: IDL Error GCPC data By: David Fanning on Thu, 24 December 2009 09:38
		Re: IDL Error GCPC data By: sampton on Thu, 24 December 2009 08:57
		Re: IDL Error GCPC data By: Wout De Nolf on Thu, 24 December 2009 00:59
		Re: IDL Error GCPC data By: sampton on Mon, 04 January 2010 17:13

Previous Topic:	fitting contours with ellipse
Next Topic:	Re: Reducing a set of curves to a mean curve

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 11:48:47 PDT 2025

Total time taken to generate the page: 2.56046 seconds