X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 18 Jun 2004 08:58 AM by  anon
Another contour problem
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
18 Jun 2004 08:58 AM
    Hello all, The section of code that follows appears to work fine right up until it gets to the contour command where the program hangs. No errors are given and IDL must be shutdown from task manager and restarted. The only thing I've changed from some working code I have is the SPH_SCAT commands used to be calls to a custom krigging function. Any ideas what may be causing this to happen? Any suggestions are welcome, Jeff arrX = SPH_SCAT(arrLon, arrLat, arrXValue, BOUNDS=[1.,0.,360., 89.], GS=[2.,1.], BOUT=bout) arrY = SPH_SCAT(arrLon, arrLat, arrYValue, BOUNDS=[1.,0.,360., 89.], GS=[2.,1.], BOUT=bout) FOR j = 0.0, 89.0, 1.0 DO BEGIN FOR i = 0.0, 360.0, 2.0 DO BEGIN pro_ConvMagGeo, 89.0 - j, i - dblShift + 1, geo_lat, geo_lon IF j EQ 0.0 AND i EQ 0.0 THEN BEGIN arrGLat = [geo_lat] arrGLon = [geo_lon] ENDIF ELSE BEGIN arrGLat = [arrGLat, geo_lat] arrGLon = [arrGLon, geo_lon] ENDELSE ENDFOR ENDFOR sngH = SQRT(((arrX)^2) + ((arrY)^2)) MAP_SET, intLat, intLon, 0, /SATELLITE, SCALE=(intZoom * 1E6), /ISOTROPIC, /HORIZON, E_HORIZON={FILL:0, COLOR:'000000'xL}, XMARGIN=[0,17], YMARGIN=[0,0], /NOERASE hexTextCol = 'CCCCCC'xL ; gray text CONTOUR, sngH, arrGLon, arrGLat, /IRREGULAR, /ISOTROPIC, /CLOSED, /CELL_FILL, /OVERPLOT,LEVELS=[ 20, 40, 60, 80, 100, 120, 140, 160, 180, 200, 220, 240, 260, 280, 300, 320, 340, 360, 380, 400, 420, 440, 460, 480, 500, 520, 540, 560, 580, 600, 620, 640, 660, 680, 700, 720, 740, 760, 780, 800, 820, 840, 860, 880, 900, 920, 940, 960, 980, 1000]

    Deleted User



    New Member


    Posts:
    New Member


    --
    29 Jun 2004 03:12 PM
    Replying to 504: Another contour problem : Not really my area, but just looking at the MAP_SET requirements, there should be a SAT_P keyword with appropriate values in the vector. This is supposedly required. As a guess, I'd say that there was some necessary value that defaults, unfortunately, to zero. Hard to say without the rest of the code or data. Another problem is that there are occaisionally glitches when mapping at or near the poles. I'd suggest trying plots up to 80N, etc.
    You are not authorized to post a reply.