| Re: oplot problem [message #17796] |
Fri, 05 November 1999 00:00 |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
Kristine Hensel (kdhensel@earthlink.net) writes:
> I'm running IDL version 5.1.1 under Solaris, and I'm having problems
> with flaky behavior of oplot.
>
> For example, when I run the following ...
>
> !p.multi = [0,1,2]
>
> loadct, 39 ; Load Rainbow color table
>
> ; Plot to n/2; higher indices contain
> ; aliased frequencies:
> plot, abs(fft_padded_bz[0:n/2]), charsize=2, ticklen=-0.02 ; Plot 1
> oplot, abs(no_peak_fft[0:n/2]), color=30
>
> plot, time_vector, bz, charsize=2 ; Plot 2
> oplot, flat_bz, color=35
> oplot, inverse_fft, color=60
>
> ... the first plot has 2 signals and the second plot has only 1. I've
> run into invisible oplots before, and never figured it out.
>
> Is there an obvious reason for this problem?
I'm just going to guess that the values of flat_bz
and inverse_fft lie outside the bounds of the plot
set up in the PLOT command. That is just about the
*only* reason you won't see anything on your plot. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: davidf@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
|
|
|
|
| Re: oplot problem [message #17800 is a reply to message #17796] |
Fri, 05 November 1999 00:00  |
Joe Means
Messages: 44
Registered: November 1996
|
Member |
|
|
Kristine Hensel wrote:
> Hi,
>
> I'm running IDL version 5.1.1 under Solaris, and I'm having problems
> with flaky behavior of oplot.
>
> For example, when I run the following ...
>
> !p.multi = [0,1,2]
>
> loadct, 39 ; Load Rainbow color table
>
> ; Plot to n/2; higher indices contain
> ; aliased frequencies:
> plot, abs(fft_padded_bz[0:n/2]), charsize=2, ticklen=-0.02 ; Plot 1
> oplot, abs(no_peak_fft[0:n/2]), color=30
>
> plot, time_vector, bz, charsize=2 ; Plot 2
> oplot, flat_bz, color=35
> oplot, inverse_fft, color=60
>
> ... the first plot has 2 signals and the second plot has only 1. I've
> run into invisible oplots before, and never figured it out.
>
> Is there an obvious reason for this problem?
>
> Thanks,
> Kristine
>
> Kristine Hensel Phone: (303) 497-1539
> High Altitude Observatory/NCAR E-mail: hensel@ucar.edu
> P.O. Box 3000 Office: FL2 3070
> Boulder, CO 80307-3000
Howdy, How about looking at the values you are trying to plot. Perhaps
with something like:
print, bz[0:10]
print, flat_bz[0:10]
print, inverse_fft[0:10]
The values in bz set the limits on the Y axis. Perhaps flat_bz[0:10] and
inverse_fft[0:10] are outside these values?
Joe Means
-
Attachment: means.vcf
(Size: 0.26KB, Downloaded 71 times)
|
|
|
|
| Re: oplot problem [message #17804 is a reply to message #17796] |
Fri, 05 November 1999 00:00 |
Kristine Hensel
Messages: 26
Registered: June 1999
|
Junior Member |
|
|
William Thompson wrote:
>
> Hmmm, should the oplot command be
>
> oplot, time_vector, flat_bz, color=35
> ^^^^^^^^^^^
The x argument is optional for oplot - in fact, I'd kind of convinced
myself that it wasn't allowed.
Anyway, I tried putting in the x argument, and the oplots were still
invisible. >:(
Thanks anyway!
Kristine
|
|
|
|
| Re: oplot problem [message #17806 is a reply to message #17796] |
Fri, 05 November 1999 00:00 |
thompson
Messages: 584
Registered: August 1991
|
Senior Member |
|
|
Kristine Hensel <kdhensel@earthlink.net> writes:
> Hi,
> I'm running IDL version 5.1.1 under Solaris, and I'm having problems
> with flaky behavior of oplot.
> For example, when I run the following ...
> !p.multi = [0,1,2]
>
> loadct, 39 ; Load Rainbow color table
>
> ; Plot to n/2; higher indices contain
> ; aliased frequencies:
> plot, abs(fft_padded_bz[0:n/2]), charsize=2, ticklen=-0.02 ; Plot 1
> oplot, abs(no_peak_fft[0:n/2]), color=30
> plot, time_vector, bz, charsize=2 ; Plot 2
> oplot, flat_bz, color=35
> oplot, inverse_fft, color=60
> ... the first plot has 2 signals and the second plot has only 1. I've
> run into invisible oplots before, and never figured it out.
> Is there an obvious reason for this problem?
Hmmm, should the oplot command be
oplot, time_vector, flat_bz, color=35
^^^^^^^^^^^
I've often made the same mistake myself. :^)
William Thompson
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
