| Re: New Colorbar Missing? [message #72683] |
Mon, 27 September 2010 18:14  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Paulo Penteado writes:
> Maybe these naming conflicts were causing your troubles with Catalyst
> on IDL 8?
It's entirely possible. I haven't noticed any problems
so far today. :-)
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.")
|
|
|
|
|
|
| Re: New Colorbar Missing? [message #72688 is a reply to message #72685] |
Mon, 27 September 2010 11:35  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
David Fanning writes:
> I start a new IDL session and type this:
>
> IDL> graphic = colorbar(rgb_table=5)
> % Compiled module: COLORBAR.
> % Attempt to call undefined procedure/function: 'COLORBAR'.
> % Execution halted at: $MAIN$
> IDL> Print, !version
> { x86_64 Win32 Windows Microsoft Windows 8.0 Jun 17 2010 64 64}
>
> Any ideas!? This is a complete mystery to me. :-(
Thanks to Paulo and others for pointing out the naming
conflicts IDL 8 introduced. Two Coyote Library routines,
in particular, were causing problems for me: COLORBAR,
a direct graphics color bar program and (I suspect)
widely used since it was written in 1996; and
COLORBAR__DEFINE, the object equivalent of COLORBAR
and probably not used much.
I have renamed these two routines in the Coyote Library
to FSC_COLORBAR and FSC_COLORBAR__DEFINE, respectively.
I have retained the original COLORBAR routine in a new
"obsolete" sub-directory of the Coyote directory for
people who want to use it. (Perhaps you haven't updated
to IDL 8 yet.)
I have also written an article that explains the name
conflicts with the Coyote and NASA Astronomy libraries
in detail and suggests several possible solutions to the
problem. (None completely satisfactory, by the way.)
http://www.dfanning.com/ng_tips/idl8_name_conflicts.html
I have gone through my web page with a fine-toothed comb and
changed all the references to COLORBAR to FSC_COLORBAR. I have
done the same thing with the Coyote and Catalyst Libraries.
In all some dozen or so programs were changed.
In light of this, it might be a good time to upgrade your
own libraries. You can either do this via zip files:
http://www.dfanning.com/programs/coyoteprograms.zip
http://www.dfanning.com/programs/catalyst.zip
(Be sure to delete colorbar.pro and colorbar__define.pro from
your old library folders if you update on top of an existing
directory. I recommend you start with fresh, empty folders.)
Or from the new idl-coyote open source project:
http://idl-coyote.googlecode.com
No doubt we haven't heard the end of this, but maybe in
a couple of years it will have sorted itself out and we
can all laugh about it. :-)
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.")
|
|
|
|
| Re: New Colorbar Missing? [message #72701 is a reply to message #72688] |
Sun, 26 September 2010 09:03 |
Jeremy Bailin
Messages: 618
Registered: April 2008
|
Senior Member |
|
|
On Sep 25, 2:14 pm, "R.G. Stockwell" <noem...@please.com> wrote:
> "David Fanning" <n...@dfanning.com> wrote in message
>
> news:MPG.2707af52e7d3fd069897f3@news.giganews.com...
>
>
>
>
>
>> Folks,
>
>> I start a new IDL session and type this:
>
>> IDL> graphic = colorbar(rgb_table=5)
>> % Compiled module: COLORBAR.
>> % Attempt to call undefined procedure/function: 'COLORBAR'.
>> % Execution halted at: $MAIN$
>> IDL> Print, !version
>> { x86_64 Win32 Windows Microsoft Windows 8.0 Jun 17 2010 64 64}
>
>> Any ideas!? This is a complete mystery to me. :-(
>
>> I have a COLORBAR *procedure* in the Coyote Library, and
>> that is on the path ahead of the <DEFAULT> IDL libraries,
>> but IDL has always been able to tell the difference between
>> a procedure and a function.
>
>> Clearly that procedure got compiled:
>
>> IDL> Help, /source
>> Compiled Procedures:
>> $MAIN$
>> COLORBAR C:\IDL\coyote\colorbar.pro
>
>> Compiled Functions:
>> FSC_COLOR C:\IDL\coyote\fsc_color.pro
>> FSC_COLOR_COLOR24 C:\IDL\coyote\fsc_color.pro
>> FSC_COLOR_COUNT_ROWS C:\IDL\coyote\fsc_color.pro
>
>> Why is IDL getting confused here? Am I going to have
>> to rename most of the routines in my Coyote Library?
>
>> 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.")
>
> I don't know if this is relevant, but I have noticed that any text after the
> "end" statement
> in a pro file, causes this error message exactly.
>
> I run into that all the time, debuging some code, or just doing some data
> exploration, where
> I have a main level script that reads data, analyzes data makes some plots.
>
> I often want to just stop the code at a point, and examine a data product.
> It used to be
> very convenient to just drop an end in the middle of the code, to end the
> program and return
> to the main level. alas, no more.
>
> cheers,
> bob
>
> PS even if everything is commented out after the 'end', it still causes that
> error
You could use stop and then do a return as soon as it quits to get
back to the main level.
-Jeremy.
|
|
|
|
| Re: New Colorbar Missing? [message #72703 is a reply to message #72701] |
Sat, 25 September 2010 11:14 |
R.G.Stockwell
Messages: 163
Registered: October 2004
|
Senior Member |
|
|
"David Fanning" <news@dfanning.com> wrote in message
news:MPG.2707af52e7d3fd069897f3@news.giganews.com...
> Folks,
>
> I start a new IDL session and type this:
>
> IDL> graphic = colorbar(rgb_table=5)
> % Compiled module: COLORBAR.
> % Attempt to call undefined procedure/function: 'COLORBAR'.
> % Execution halted at: $MAIN$
> IDL> Print, !version
> { x86_64 Win32 Windows Microsoft Windows 8.0 Jun 17 2010 64 64}
>
> Any ideas!? This is a complete mystery to me. :-(
>
> I have a COLORBAR *procedure* in the Coyote Library, and
> that is on the path ahead of the <DEFAULT> IDL libraries,
> but IDL has always been able to tell the difference between
> a procedure and a function.
>
> Clearly that procedure got compiled:
>
> IDL> Help, /source
> Compiled Procedures:
> $MAIN$
> COLORBAR C:\IDL\coyote\colorbar.pro
>
> Compiled Functions:
> FSC_COLOR C:\IDL\coyote\fsc_color.pro
> FSC_COLOR_COLOR24 C:\IDL\coyote\fsc_color.pro
> FSC_COLOR_COUNT_ROWS C:\IDL\coyote\fsc_color.pro
>
> Why is IDL getting confused here? Am I going to have
> to rename most of the routines in my Coyote Library?
>
> 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.")
I don't know if this is relevant, but I have noticed that any text after the
"end" statement
in a pro file, causes this error message exactly.
I run into that all the time, debuging some code, or just doing some data
exploration, where
I have a main level script that reads data, analyzes data makes some plots.
I often want to just stop the code at a point, and examine a data product.
It used to be
very convenient to just drop an end in the middle of the code, to end the
program and return
to the main level. alas, no more.
cheers,
bob
PS even if everything is commented out after the 'end', it still causes that
error
|
|
|
|
|
|
|
|
|
|
| Re: New Colorbar Missing? [message #72713 is a reply to message #72688] |
Mon, 04 October 2010 09:00 |
vasily
Messages: 2
Registered: March 2010
|
Junior Member |
|
|
On Sep 27, 7:35 pm, David Fanning <n...@dfanning.com> wrote:
> David Fanning writes:
>> I start a new IDL session and type this:
>
>> IDL> graphic =colorbar(rgb_table=5)
>> % Compiled module:COLORBAR.
>> % Attempt to call undefined procedure/function: 'COLORBAR'.
>> % Execution halted at: $MAIN$
>> IDL> Print, !version
>> { x86_64 Win32 Windows Microsoft Windows 8.0 Jun 17 2010 64 64}
>
>> Any ideas!? This is a complete mystery to me. :-(
>
> Thanks to Paulo and others for pointing out the naming
> conflicts IDL 8 introduced. Two Coyote Library routines,
> in particular, were causing problems for me:COLORBAR,
> a direct graphics color bar program and (I suspect)
> widely used since it was written in 1996; and
> COLORBAR__DEFINE, the object equivalent ofCOLORBAR
> and probably not used much.
>
> I have renamed these two routines in the Coyote Library
> to FSC_COLORBAR and FSC_COLORBAR__DEFINE, respectively.
> I have retained the originalCOLORBARroutine in a new
> "obsolete" sub-directory of the Coyote directory for
> people who want to use it. (Perhaps you haven't updated
> to IDL 8 yet.)
>
> I have also written an article that explains the name
> conflicts with the Coyote and NASA Astronomy libraries
> in detail and suggests several possible solutions to the
> problem. (None completely satisfactory, by the way.)
>
> http://www.dfanning.com/ng_tips/idl8_name_conflicts.html
>
> I have gone through my web page with a fine-toothed comb and
> changed all the references toCOLORBARto FSC_COLORBAR. I have
> done the same thing with the Coyote and Catalyst Libraries.
> In all some dozen or so programs were changed.
>
> In light of this, it might be a good time to upgrade your
> own libraries. You can either do this via zip files:
>
> http://www.dfanning.com/programs/coyoteprograms.zip
> http://www.dfanning.com/programs/catalyst.zip
>
> (Be sure to deletecolorbar.pro and colorbar__define.pro from
> your old library folders if you update on top of an existing
> directory. I recommend you start with fresh, empty folders.)
>
> Or from the new idl-coyote open source project:
>
> http://idl-coyote.googlecode.com
>
> No doubt we haven't heard the end of this, but maybe in
> a couple of years it will have sorted itself out and we
> can all laugh about it. :-)
>
> 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.")
Dear David,
Thanks for the update, but it seems that you have removed HIST_ND from
the current version of the library. Is there a reason for that?
Thanks,
Vasily
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
