| Re: black window on fsc_surface & fsc_surface_log? [message #40550 is a reply to message #40470] |
Wed, 11 August 2004 12:16  |
u2s5thmember
Messages: 11
Registered: January 2004
|
Junior Member |
|
|
David, Your fsc_surface code is Great! I know it's me doing
something incorrectly. Here's what I did which was incompatible with
fsc_surface which produced the black window:
I usually put the word "stop" just before the word "end" in my code,
which allows me to examine or work with the variables after running my
code. If I take out the word "stop", idl doesn't seem to remember any
of the variables it just used, i.e. it says all my variables are now
undefined.
If I remove the word "stop" from my code (I just read I could type
".con" instead), fsc_surface loads correctly and produces a plot. I'm
not certain I have the correct plot yet though.
I do have a question re: GridData vs. Triangulate/TriGrid:
For some reason using Triangulate/TriGrid produces negative z axis
data, when it should range from 1e-3 to 1, so I'll *have* to figure
out GridData. Here's the problem with that:
TriGrid offers the [XGrid=variable], [YGrid=variable] options, so when
I run the above code and then call
fsc_surface, griddedData, xvector, yvector
the DATAX array size matches the Z data size. This part is good, but
if I do this instead:
griddedData=GridData(x, y, z, dimension=163
or
griddedData=GridData(x, y, z, dimension=163, $
/GRID, xout=x, yout=y)
and then:
fsc_surface, griddedData, x, y, position=[0,1,0,1,0,1]
or
fsc_surface, griddedData, position=[0,1,0,1,0,1]
I get either 1) an error message saying the x & y arrays don't match
griddedData or 2) fsc_surface plots the array indices on the x- and
y-axes and not my actual x & y data.
Do I need to TriGrid after calling GridData???
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
